EMC NW NMM to restore MS AG database
Following last article, how to restore MS AG database , that is in the following:

You see ? Cheer up , we will begin our trip now.
From EMC NW console, we can see backup status.
FULL BACKUP

Incr backup (TLOG backup)

AG different setting:

What interest thing is you see the different choose to make different behavour.
If we choose N4 backup source, we can see all database

If we choose N5 backup source, we have to select different group by different time.

or

Let us pick one database for an example:



Then all finished, we can see the result.

Here is restore log by EMC NW NMM
Recovering files of client 'LCXXXXXXNB51' from server 'LYYYYH-BACKUP' to client 'ONLINETEST01'.
43708:(pid 5456):Start time: Tue Jan 03 13:17:54 2017
43621:(pid 5456):Computer Name: ONLINETEST01 User Name: administrator
NSR_CLIENT: LCXXXXXXNB51.lgcnjad.net;
NSR_SERVER: LYYYYH-BACKUP;
37725:(pid 5456):Recovering database 'LKKKK.5.E.FOR' into 'LKKKK.5.E.FOR' ...
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR~1.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR~2.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR~3.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR~4.
37839:(pid 5456):Warning: Only 1 tape sessions will be used to restore 4 stripes.
29317:(pid 5456):Data will be restored using SQL removable pipes.
4690:(pid 5456):RESTORE database [LKKKK.5.E.FOR] FROM virtual_device='Legato#c6be8dbb-2e4c-4a85-b7da-1ba4882213b7' WITH move 'LKKKK.5.E.FOR' to 'M:\DATA2\LKKKK.5.E.FOR_LKKKK.5.E.FOR_676.mdf', move 'LKKKK.5.E.FOR_log' to 'M:\DATA2\LKKKK.5.E.FOR_LKKKK.5.E.FOR_log_676.ldf', replace, maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#e32caf9a-7120-4309-8c9e-0e6777355f6f' WITH maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#c01585c8-5fc2-4076-abcc-ed54bd8daa5a' WITH maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#5133eafd-79a9-4662-afa8-1c799b21242e' WITH maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#578eb90f-63de-4cdc-bd24-b6249b8fe975' WITH maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#c4e8e33a-17a1-436f-9a14-2ce4a05dea3e' WITH maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#7ec9679d-303b-47ee-8390-7c8829501391' WITH maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#d3fd0e9f-febf-4ed0-9b06-202eac29d724' WITH maxtransfersize = 4194304, norecovery
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
142468:(pid 5456):[3512]nsr/db_apps/bsmsql/rcstripes.c(222): Finding backup for saveset MSSQL:/LKKKK.5.E.FOR.
4690:(pid 5456):RESTORE log [LKKKK.5.E.FOR] FROM virtual_device='Legato#6b7874d9-e3b0-48e9-b1fc-853924ef5bfc' WITH maxtransfersize = 4194304
35866:(pid 5456):The restore of database 'LKKKK.5.E.FOR' completed successfully.
29310:(pid 5456):
Received 17 MB 9 item(s) from NSR server (size information for snapshot(s) is not available).
nsr/db_apps/bsmsql/rcovmain.cpp(442): Entering cleanUp().
nsr/db_apps/bsmsql/rcovmain.cpp(500): Exiting cleanUp().
43709:(pid 5456):Stop time: Tue Jan 03 13:25:31 2017
Restore completion time: Tue Jan 03 13:25:32 2017
Thanks,
Any question , please free to ask,
EMC NW NMM to restore MS AG database的更多相关文章
- EMC NW NMM to backup MS AG
To use EMC NW NMM to backup MS SQL always on database, that is a simple and safe way to protector da ...
- get your sqlserver database back by using EMC NW NMM
Dear all Yes ~ We can backup our sqlserver by EMC NW NMM. That is true and NW is a very very powerfu ...
- EMC networker nmm can restore and recover sqlserver as different name to different location
EMC networker nmm can restore and recover sqlserver as different name to different location That is ...
- How to setup backup by using EMC NW + EMC NMM for sqlserver failover cluster (not always on)
As we said, sqlsever fail over cluster is perviously version of always on. The HA was guarenteed by ...
- why NW NMM backup sqlserver failed and how to solve it
A NW NMM backup sqlserver failed. wow , I realze that maybe I put too many database backup together ...
- 转载:Restore SQL Server database and overwrite existing database
转载自:https://www.mssqltips.com/sqlservertutorial/121/restore-sql-server-database-and-overwrite-existi ...
- 错误1919,配置ODBC数据源MS Access Database时发生错误ODEC错误
WIN7 64位旗舰版安装OFFICE2003 提示:“错误1919,配置ODBC数据源MS Access Database时发生错误ODEC错误” 在64位系统上,32位软件的注册表的信息不是直接在 ...
- Oracle 12c: RMAN restore/recover pluggable database
查看数据库状态 运行在归档模式,可拔插数据库name=pdborcl SQL> archive log list; Database log mode Archive Mode Automati ...
- How to Baskup and Restore a MySQL database
If you're storing anything in MySQL databases that you do not want to lose, it is very important to ...
随机推荐
- java数据库学习路线和必学知识点!
java数据库必学知识点! 分享一下数据库的学习路线和必学的知识点! 掌握mysql,Oracle在各个平台上的安装及使用 Mysql数据库基础 mysql概述.优点.运行原理及内存结构 mysql数 ...
- UGUI源码之Selectable
Selectable是Button.InputField.Toggle.ScrollBar.Slider.Dropdown的基类. Selectable的继承的类与接口如下: public class ...
- flink编译支持CDH6.2.0(hadoop3.0.0)
准备工作 因为在编译时需要下载许多依赖包,在执行编译前最好先配置下代理仓库 <mirrors> <mirror> <id>nexus-aliyun</id&g ...
- Kubernetes concepts 系列
kubernetes concepts overview Pod overview Replication Controller Pod Liftcycle Termination Of Pod Re ...
- 我终于学会了使用python操作postgresql
一 前言 这篇文章不仅适合pgsql,更适合mysql,思路都是一致的,如果读者学会使用psycopg2操作pgsql,那么使用PyMySQL 操作mysql也是很简单:本篇文章涵盖内容广泛,提供的操 ...
- Miller-Rabin素数测试算法
\(Miller-Rabin\)素数测试 用途 判断整数\(n\)是否是质数,在\(n\)较小的情况下,可以使用试除法,时间复杂度为\(O(\sqrt n)\).但当\(n\)的值较大的时候,朴素的 ...
- IDEA新建maven项目没有webapp目录解决方法
转载地址:https://www.cnblogs.com/oldzhang1222/p/10429827.html 先创建的页面修改路径 修改路径如下 添加并完善路径\src\main\webapp ...
- 隐隐约约 听 RazorEngine 在 那里 据说 生成代码 很 美。
这只是 一个开始 ....
- Dynamics CRM Package Deployer 部署工具
CRM 部署工具非常有用 我们可以用部署工具来做迁移,部署 等等. Package Deployer可以同时部署多个solutions. 并且也可以勾选solution的plugin也同时部署. 三 ...
- AWS 入门使用
AWS官方参考文档:https://docs.aws.amazon.com/s3/index.html AWS基本介绍:https://docs.aws.amazon.com/zh_cn/Amazon ...