Change the path of a database or log file

  • Article

Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager

If a protected database or log files are moved to a volume that contains data that is protected by System Center 2012 – Data Protection Manager (DPM), protection continues. If a protected database or log files are moved to a volume that is not protected by DPM, DPM displays an alert and protection jobs will fail. To resolve the alert, in the alert details, click the Modify protection job link and then run a consistency check.

If a recovery point is created after the path changes, you cannot recover the storage group or recovery points from recovery points based on the old path. You can still recover data to a network folder.

If you recover a Microsoft Exchange 2003 storage group after the path for databases or log files has changed and the most recent recovery point was created before the path change, the recovery copies the files to the old path and tries to mount the databases. If the databases can be mounted, the recovery appears to succeed.

If this occurs, you can take one of the following actions:

  • Change the databases back to the original path and then recover the storage group again.

  • Recover the databases using the Copy to a network folder option. Specify the new location of the databases as the copy destination. Select the Bring database to a clean shutdown after copying the files option. Mount the database after recovery.

If you recover an Exchange 2007 storage group after the path for databases or log files has changed and the most recent recovery point was created before the path changed, DPM will recover the databases to the new location.

When you change the path of log files for a storage group that uses disk-to-tape backup and only incremental backups have been performed since the path change, recovery of a storage group using Latest as the recovery point will fail. To avoid this issue, perform one of the following actions:

  • Run a full backup and then retry the storage group recovery.

  • Recover individual databases, rather than the storage group.

  • Recover the storage group to a network folder as files.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----