User's Manual

8.4
Recovery
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide
3PAR Confidential
 Bring the database back online.
At this stage, the database is in the no_recovery mode and the DBA can now apply the
log backups that took place after the virtual copy backup was taken.
To perform a point-of-failure recovery:
1 Find the timestamp that has a consistent full backup, (such as 010106000000).
2 Find the server name (such as SQLserver01).
3 Find the SQL instance name (such as SQLInstan01).
4 Find the database name (such as northwind).
At the command prompt, type:
RMSql.exe restore -s SQLserver01 -i SQLInstan01 -d northwind -t 010106000000
After the command has finished, the DBA can apply the logs.
For example:
RESTORE log northwind from Disk='G:\log1.bak' with NO_recovery;
RESTORE log northwind from Disk='G:\log2.bak' with NO_recovery;
RESTORE log northwind from Disk='G:\log3.bak' with recovery; -stopat “Jun 28,
2006 5:44 PM”
8.1.3 SQL Instance Level File Copy Restore in an MSCS Environment
To perform a SQL instance level file copy restore in an MSCS environment:
1 From Failover Cluster Management on Windows 2008 or Cluster Administrator on
Windows 2003:
a Offline SQL Server Agent resource.
b Offline SQL Instance Service resource.
2 Run the
rmsql restore command with an instance level virtual copy.
3 From Failover Cluster Management on Windows 2008 or Cluster Administrator on
Windows 2003:
a Online SQL Server Agent resource.
b Online SQL Instance Service resource.