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的更多相关文章

  1. 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 ...

  2. 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 ...

  3. 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 ...

  4. 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 ...

  5. 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 ...

  6. 转载:Restore SQL Server database and overwrite existing database

    转载自:https://www.mssqltips.com/sqlservertutorial/121/restore-sql-server-database-and-overwrite-existi ...

  7. 错误1919,配置ODBC数据源MS Access Database时发生错误ODEC错误

    WIN7 64位旗舰版安装OFFICE2003 提示:“错误1919,配置ODBC数据源MS Access Database时发生错误ODEC错误” 在64位系统上,32位软件的注册表的信息不是直接在 ...

  8. Oracle 12c: RMAN restore/recover pluggable database

    查看数据库状态 运行在归档模式,可拔插数据库name=pdborcl SQL> archive log list; Database log mode Archive Mode Automati ...

  9. 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 ...

随机推荐

  1. MongoDB高级用法

    MongoDB高级查询用法大全 转载 http://blog.163.com/lgh_2002/blog/static/440175262012052116455/ 详见官方的手册:http://ww ...

  2. C++ | C++ 基础知识 | 类型与声明

    一.类型 C++ 包含一整套基本类型,这些类型对应计算机最基本的存储单元并且展现 1.0 布尔值 一个布尔变量(bool)的取值或者是 true 或者是 false,布尔变量常用于表达逻辑运算结果. ...

  3. vue兄弟组件传值——事件总线

    1.创建一个js文件,例如msg.js,放到合适位置,例如components中,或者其他位置也行.然后在兄弟两个组件中分别引入msg.js文件 msg.js: import Vue from 'vu ...

  4. spring-boot内嵌三大容器https设置

    spring-boot内嵌三大容器https设置 spring-boot默认的内嵌容器为tomcat,除了tomcat之前还可以设置jetty和undertow. 1.设置https spring-b ...

  5. java通过word模板生成word文档

    介绍 上次公司项目需要一个生成word文档的功能,有固定的模板根据业务填充数据即可,由于从来没做过,项目也比较着急于是去网上找有没有合适的工具类,找了好几种,看到其中有freeMark模板生成比较靠谱 ...

  6. 深入理解es6中的Promise

    https://www.jianshu.com/p/9e4af5b77253 https://zhuanlan.zhihu.com/p/30797777 https://segmentfault.co ...

  7. Web测试中定位bug的方法

    在web测试过程中,经常会遇到页面中内容或数据显示错误,甚至不显示,第一反应就是BUG,没错,确实是BUG.进一步了解这个BUG的问题出在那里,是测试人员需要掌握的,可以简单的使用浏览器自带开发者工具 ...

  8. MySQL:如何查询出每个分组中的 top n 条记录?

    问题描述 需求: 查询出每月 order_amount(订单金额) 排行前3的记录. 例如对于2019-02,查询结果中就应该是这3条: 解决方法 MySQL 5.7 和 MySQL 8.0 有不同的 ...

  9. Android studio 报错Error:Internal error: (java.lang.ClassNotFoundException) com.google.wireless.android.sdk.stats.IntellijIndexingStats$Index

    Android studio运行make build报错 解决方法 在studio的File-->Settings-->Build, Execution, Deployment---> ...

  10. java8 stream自定义分组求和并排序

    public static void main(String[] args) { List<GroupDetailDTO> list = new ArrayList<>(); ...