HP 9000 rp5405 Servers - Manual (Page 394)

Restoring application replicas
This module describes methods of restoring application replicas:
• Roll-forward versus point-in-time restores , page 394
• Restoring in units of information stores (Exchange 2003/2007) , page 396
• Restore application replica workflow , page 398
• About the Restore Replica Wizard , page 398
• Restoring the latest application replica (simple restore) , page 399
• Restoring an application replica from the Replica History , page 400
• Restoring an SQL Server replica to a remote site , page 401
• Using Database Availability Groups (DAGs) , page 403
Roll-forward versus point-in-time restores
An application replica can be restored in one of two modes:
• Roll-forward
• Point-in-time
When backup data on an Exchange Server or SQL Server database server is restored, the database
returns to the state at the point-in-time when the backup occurred. If the transaction logs from the time
when the backup was executed up until the restore are stored on the primary volume, the uncommitted
transactions can be applied using the roll-forward option. By applying the transaction logs after
backup, the database is restored to a state immediately before the error occurred. With a point-in-time
restore, the transaction log data is not used and the database returns to the state of the last complete
backup.
NOTE:
Roll-forward operations for SQL Server cannot be performed by Replication Manager. After restoring
a database, the actual roll-forward operation must be accomplished using the drmsqlrecovertool
command or SQL Management Studio. For information on drmsqlrecovertool, see the
HP P9000
Replication Manager Software Application Agent CLI User Guide.
Roll forward scenario (Exchange)
The roll-forward scenario for Exchange databases is described in the following figure.
NOTE:
Exchange 2010 does not use storage groups, so replica operations are performed on information
stores. See “
About storage groups and information stores ” on page 373 for more information.
Managing application replicas 394