Home > Storage > Data Storage Essentials > AppSync > Dell AppSync Integration with Microsoft SQL Server > Affected entities during restore
An affected entity is data that resides along with data that must be protected, on the production host, which becomes part of the copy. In order to restore data items from a copy, a prompt appears to acknowledge other items to restore; besides the ones selected earlier.
Be careful while planning the data layout for databases, and ensure that only those databases that are closely related and can be restored together are protected within the same copy.
If there are affected entities in your underlying storage configuration, the Restore Wizard notifies you of these items. Restore cannot proceed further without you acknowledging the list of affected entities. If required, take the necessary steps to detach affected databases and then proceed with the restore.
The following scenarios produce affected entities that require you to acknowledge that additional items are restored:
If the affected entity is protected along with a database that is selected for restore, AppSync restores it. Any other database that is not protected, but is an affected entity, is also overwritten.
AppSync calculates affected entities for consistency groups and LUNs of databases that are selected for restore. If one or more affected databases partially resides on other consistency groups or LUNs, AppSync does not calculate affected entities on those consistency groups or LUNs. Depending on the type of affected entity, AppSync detaches the affected databases if they are protected in the same service plan as the service plan of the databases to be restored. For databases not protected in the same service plan as the databases to be restored, you must manually detach them from the SQL Server instance.
The following figure depicts the two types of affected entities that are seen during restore.
Affected entities are calculated only for the SQL Server instances where the credentials are configured. AppSync does a fresh database discovery for all these instances before calculating the affected entities. It is recommended not to share storage across databases that belong to different SQL Server Instances.