Table of ContentsView in Frames

Remote servers

Requirements for a remote administration server

An SQL Server instance that is running SnapManager can be remotely administered from another Windows system that is configured as a remote administration server:
Note: Some limitations apply to using SQL Server authentication as the security authentication method to be used to establish the connection to a remote administration server. For more information, see Connecting to an SQL Server instance.
Note: An SQL Server used for database verification can be a virtual SQL Server.

You can add servers that you want to use through the option "Add servers to be managed" in the Actions pane. For more information, see Connecting to an SQL Server instance.

Requirements for a remote verification server

SnapManager performs remote verification using the same mechanisms used for local verification, except that the verification is performed on a host that is different from the SQL Server that initiated the backup. This is the reason that you need SnapDrive and SnapManager installed on your remote verification server, in addition to connectivity to the storage system.

To run remote database consistency checks, your remote Windows system must meet the following requirements:

Note: Do not try to connect the SQL Server's LUNs to the remote SQL Server.
Note: If you cannot use a remote SQL Server instance or do not want to use a local SQL server instance, you can select not to perform database verification. Alternatively, you can select to verify only online databases before and after backup.
Note: Although it is possible to restore from an unverified backup, you should restore only from verified backups.
Note: You cannot use a remote physical server as the verification server for an SQL server that is running on a virtual machine.