The following list includes prerequisites and restrictions for this solution:
- The SQL Server database(s) must be online during the AppSync protection process. If several databases that are subscribed to a service plan are offline during the service plan run, protection does not fail. It creates copies only for the databases that are online. AppSync dynamically checks for the database status during the service plan run and protects all the databases that are online at the time of the run. The protection fails if all the databases that are subscribed to the service plan are offline during service plan run. It applies to SQL repurposing workflows too.
- System databases cannot be protected and are not listed post-discovery. The system databases must NOT reside on the same storage volume as user databases or logs. If a user database copy is restored, it might inadvertently get overwritten.
- The SQL Server database and its transaction logs must be on disks in the same storage array. AppSync can truncate transaction logs using log backups with log truncation that is enabled in SQL Server service plans. AppSync must have the Full SQL Server backup type selected in order to truncate transaction logs.
- Full-text catalogs, that are associated with a filegroup, are included as part of the copy. If the full-text catalogs are not on supported storage, protection fails. When using full-text catalogs, ensure that the storage device where the catalog is located does include data that is related to the database only.
- When a copy of a database mirror is created, the copy fails with an error indicating that the database is not in a valid state.
- In Hyper-V environments, AppSync requires the storage for SQL databases and log files to be on iSCSI direct attached devices, Virtual Fiber Channel (NPIV), or SCSI pass-through devices. SCSI Command Descriptor Block (CDB) filtering must be turned off in the parent partition for SCSI pass-through. It is turned on by default. It is true for SQL cluster servers as well.