-
- It is possible to mount and recover both databases from stand-alone SQL Server instances and databases from a Clustered SQL Server instance as a clustered resource on an alternate Clustered SQL Server instance.
- To mount a copy from a production cluster to an alternate cluster, as a clustered resource, select Mount and recovery copy and then select a clustered SQL server instance of the alternate cluster under the Recovery Instance drop-down menu.
- Mounting to a mount point (example: I:\mountpoint, where I:\ is a clustered disk) on the clustered mount host is supported. Specify the alternate mount path in the Mount path options or specify different mount paths for each file system by selecting Mapped Path in Mount on Path option and setting Target path for each file system for Source Host in the Path Settings section. The root disk for the alternate mount point must be a clustered disk, and the SQL Server must have a dependency on that clustered disk.
- Multiple copies of the same database can be mounted to an alternate cluster simultaneously.
- All recovery types are supported.
- Manually disable automount by running diskpart at a command prompt, and entering automount disable at the Diskpart prompt.
- When performing, Mount and recover copy as a clustered resource to a clustered production server the below considerations must be noted. The clustered SQL instance requires briefly being stopped and started along with any other dependent service by AppSync. AppSync adds the newly introduced clustered disks as dependencies for the clustered SQL service while mounting, which requires it to offline the clustered SQL service, and any dependent service. This is required to ensure that the clustered disks are moved to the new node, along with clustered services, and are brought online before the services are brought online, in case failing over to another node is required.