Home > Storage > Data Storage Essentials > AppSync > Dell AppSync Integration with Microsoft SQL Server > Mounting copies from multiple production hosts to a single mount host
Multiple SQL Server instances across hosts can be subscribed to the same service plan. When the service plan runs, it groups the database instances by host, and creates copies for all such groups. The database copies are grouped by hosts. These groups may further get divided based on the load on each instance (see the Efficiency section for more details). A single mount host may be chosen for mounting, and optionally recovering, all such copies. Be sure to avoid any conflicting mount points or database names across hosts.
To avoid conflicting mount paths, choose the Mapped Path as the mount option, and provide different mount paths for each file system by setting the Path Settings. Mount Copy Overrides are not available with the Mapped Path option. Alternatively, choose the host level mount overrides to specify a different mount path for all databases that are protected on that host.
To avoid conflicting database names on the mount host in case production database names are the same across hosts, choose to rename the suffix for all databases that are protected on a production host. A database name conflict can only occur when intending to recover the database's post mount.
Failure to avoid such conflicts may result in partially mounted or recovered copies. Choosing separate mount hosts, one for each of the involved production hosts, helps to avoid any conflicts. This result can be achieved by overriding the mount host / recovery SQL Server Instance for each of the production hosts. For details on configuring mount overrides, see the Overriding mount settings in a service plan section in the AppSync User and Administration Guide.