Home > Storage > Data Storage Essentials > AppSync > Integrating Dell PowerStore with AppSync > Restoring local and remote copies
AppSync can restore local and remote copies in asynchronous replication session scenarios. AppSync does not support synchronous replication with PowerStore currently. It may be supported in the future, so check the AppSync Support Matrix.
When restoring a local copy with asynchronous replication sessions, AppSync performs the following:
When restoring a remote copy (remote gold service plan copy, silver service plan copy, or first-generation remote repurposed copy) with asynchronous replication sessions, AppSync takes the following actions:
The following events or similar events are displayed in the AppSync UI as the restore process runs:
Initiating sync and failover on PowerStore replication session of Volume: <Volume Name> on the array <Service tag of the production appliance>. (Figure 9 shows a volume group in this example)
Failover operation is completed for all the PowerStore replication sessions on the array <Service tag of the production appliance>.
Restored PowerStore volume <Volume Name> using copy volume <AppSync_Snap-4425699d0d7d-4385-84fe-8ad207c32f512020-05-19T00:38:26.622784500Z> successfully on the array <Service tag of the remote appliance>.
Initiating sync and failback on PowerStore replication session of Volume: <Volume Name> on the array <Service tag of the remote appliance>.
Failover operation is completed for all the PowerStore replication sessions on the array <Service tag of the remote appliance>.
Figure 9 shows the events during a typical SQL Server Restore operation of a remote Microsoft SQL database copy.
If other databases share common storage with the production database that is being restored, and these are not protected together, AppSync displays a warning about them being affected entities (see Figure 10). Users must acknowledge this warning to continue with the restore operation. Acknowledging the affected entities warning allows the other objects that share common storage to also be restored. If those objects are processing I/O, such as an online database, the restore operation may fail. It is best to design your storage and database layout to avoid affected entities if possible. This often provides better performance for the database and gives you more flexibility when restoring.