Requirements for a remote administration server
SQL Server instance that is running SnapManager can be remotely
administered from another Windows system that is configured as a
remote administration server:
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
- You do not need to install
an iSCSI driver or an HBA driver on this system.
- SnapDrive does not need to be installed unless you want to use
the remote administration server to remotely administer SnapDrive.
- SnapManager must be installed.
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
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:
- The remote Windows system must have connectivity to the storage system.
Note: If you are using
iSCSI to connect to the storage system on the remote verification server,
an iSCSI connection must be created.
- For LUNs:
- When the SQL server is hosted on a virtual machine with VMDK
disks, the remote verification server must be a virtual machine.
The verification virtual machine should also reside on the
same vCenter as the SQL Server virtual machine.
- If you are running verification on a SnapMirror destination
volume, or cloning a database on SnapMirror destination volume,
the remote virtual machine should not reside on the same vCenter
as the original SQL Server virtual machine.
- SnapDrive must be installed.
Note: Do not try to connect
the SQL Server's LUNs to the remote SQL Server.
- The SnapManager
version and SnapDrive version on both the remote computer and host
computer must be same.
- Microsoft SQL Server must be installed.
The version of SQL Server installed on the remote verification server must be either the same version and patch level as the source SQL Server or a later SQL Server version. For example, the source server is SQL 2005 and the remote verification server is SQL 2008. SnapManager for Microsoft SQL Server does not support using a remote verification server with a SQL Server version lower than the source version.
- The SQL Server used for database verification can be a virtual
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.
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.