Failed to Start the Database When a User Tests a Recovery Plan of an Exchange 2010 or Exchange 2013 Protected Group

18

1.Before performing the DR testing, ensure that the data file, log file, and name of the database that you want to restore are not used by any database on the DR end.
2.If any of them is in use, perform the following steps to prevent a protected group testing failure:

Delete the related database at the DR end.
Change the name, data file directory, or log file directory of the database that you want to restore based on site requirements.

Other related questions:
Databases Fail to Be Started After Paths of Protected Objects' Data Files and Logs Are Changed and Protected Groups (Oracle, IBM DB2, Microsoft SQL Server, and Microsoft Exchange Server) Are Refreshed
Change the paths of protected objects' data files and log files to the original paths to ensure that the environments on the production and DR ends are the same.

During the Data Clearance for a Recovery Plan of an SQL Server Protected Group, a Message Is Displayed Stating Failed to execute the script When the Database Is Stopped
Check whether the database is locked. If the database is locked, unlock it and clear its data again.

Starting or Shutting Down VMs Fails When You Execute a Recovery Plan for VMware VMs
1.If you want to recover a VM to an ESXi host, log in to vCenter through a vCenter client. Set the location for storing VM swap files on the ESXi host. You are advised to set the location on a dedicated datastore without affecting other VMs. The dedicated datastore must have adequate space. For details, see the VMware documentation. 2.If you want to recover a VM to an ESXi host cluster, ensure that VM swap files and the VM reside under the same directory to prevent the adverse impact on VM vMotion performance. Adjust the space of the datastore where the VM resides to ensure that the VM can correctly create swap files.

During the Data Clearance for a Recovery Plan of an SQL Server Protected Group, a Message Is Displayed Stating Failed to execute the script After the Database Is Stopped
Check whether the database is locked. If the database is locked, unlock it and clear its data again.

Introduction to recovery plan tests executed by the OceanStor ReplicationDirector
You can test a recovery plan to verify the availability of the data replicated to the disaster recovery site. During a test, the disaster recovery site generates test data using snapshots, which does not have any impact on the production site. After the test is complete, the test environment must be cleaned up. Before a failover or planned migration, at least one recovery plan test must be executed successfully. The test can be performed only in the disaster recovery management system at the disaster recovery site.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top