You Have Refreshed Protected Groups After Deleting Data or Log Files in SQL Server Database, but Storage Information About the Protected Groups Is Not Refreshed in the Topology

4

1.Use SQL Server enterprise manager to log in to the SQL Server Database.
2.Enter the SELECT * FROM [errorDB].[sys].[database_files] (errorDB indicates the database name) SQL statement or check the sys.database_files table of database errorDB in the enterprise manager to check whether the state_desc field of a file is OFFLINE.




If the state_desc field of a file is OFFLINE, contact database engineers to restore the file to ONLINE.
If the database file has been deleted, contact database engineers to delete the file.

3.After database engineers resolve the problem, refresh protected groups and check whether the topology is correct.

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 After the Database Is Stopped
Check whether the database is locked. If the database is locked, unlock it and clear its data again.

The Protected Group is Invalid After All Protection Objects Are Normal
1.On the menu bar, select Resources. 2.In the navigation tree, select the site where the network elements (storage devices, hosts, or VMs) reside and click . In the upper right corner of the main page, click , in Background Task, you can view details about the refreshing. 3.Refresh the protected groups.

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.

Introduction to protected groups of the OceanStor ReplicationDirector
Protected groups are service objects that are protected by the disaster recovery management system. Protected groups consist of protected objects and protection policies. You can create protected groups for various protected objects such as databases, local host file systems, LUNs, NAS file systems, and VMs. Select different protection policies to implement disaster recovery based on RPO/RTO requirements.

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