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 ...
随机推荐
- docker 修改实例名称
docker 容器(服务)重命名只要一个命令就可以: docker rename 原容器名 新容器名 如:
- Spring注解:InitBinder
注解 InitBinder 是用来初始化绑定器Binder的,而Binder是用来绑定数据的,换句话说就是将请求参数转成数据对象. @InitBinder用于在@Controller中标注于方法,表示 ...
- Java和PHP加解密
PHP代码 <?php //DES加解密工具 class DesEncrypt { var $key; var $iv; function DesEncrypt($key, $iv=0) { $ ...
- 生成TFRecord文件完整代码实例
import os import json def get_annotation_dict(input_folder_path, word2number_dict): label_dict = {} ...
- hdu - 4990
Read the program below carefully then answer the question. #pragma comment(linker, "/STACK:1 ...
- Gitlab应用——系统管理
查看linux系统信息 查看日志 创建账号 选择regular,这是一个普通账号,点击“create user”账号创建完成 点击“User”,然后点击“New user”.使 ...
- 官方文档中文版!Spring Cloud Stream 快速入门
本文内容翻译自官方文档,spring-cloud-stream docs,对 Spring Cloud Stream的应用入门介绍. 一.Spring Cloud Stream 简介 官方定义 Spr ...
- Java入门 - 高级教程 - 09.文档注释
原文地址:http://www.work100.net/training/java-documentation.html 更多教程:光束云 - 免费课程 文档注释 序号 文内章节 视频 1 概述 2 ...
- 实用代码|Linux定时检查应用状态
有时候,我们挂在服务器上的应用会因为一些特殊情况挂掉,致使项目经理又对我们说:又挂了!赶紧去看看!于是又了以下脚本,使用shell编写,用于定时检查应用情况,挂掉则重启.这里以tomcat为例. 根据 ...
- Mac 查看端口占用情况及杀死进程
查看端口占用情况命令 sudo lsof -i :9000 冒号后面就是你需要查看的端口号. TheEternityZhang-MacBook:project zhtony$ sudo lsof -i ...