Deciding where to run NetBackup Snapshot Manager
You can deploy NetBackup Snapshot Manager in the following ways:
Deploy NetBackup Snapshot Manager in a cloud and manage assets in that cloud.
Deploy NetBackup Snapshot Manager in a cloud and manage assets in multiple clouds.
Veritas recommends that you deploy NetBackup Snapshot Manager on a cloud to protect your cloud assets. If you want to protect assets in a cloud, deploy the NetBackup Snapshot Manager host instance in the same cloud environment.
Similarly, if you want to protect on-premise assets, deploy the NetBackup Snapshot Manager host in the same on-premise environment. For detailed information about the on-premise content, refer to the NetBackup Snapshot Manager for Data Center Administrator's Guide.
If you install NetBackup Snapshot Manager on multiple hosts, we recommend that each NetBackup Snapshot Manager instance manage separate resources. For example, two NetBackup Snapshot Manager instances should not manage the same AWS account or the same Azure subscription. The following scenario illustrates why having two NetBackup Snapshot Manager instances manage the same resources creates problems:
NetBackup Snapshot Manager instance A and NetBackup Snapshot Manager instance B both manage the assets of the same AWS account.
On NetBackup Snapshot Manager instance A, the administrator takes a snapshot of an AWS virtual machine. The database on NetBackup Snapshot Manager instance A stores the virtual machine's metadata. This metadata includes the virtual machine's storage size and its disk configuration.
Later, on NetBackup Snapshot Manager instance B, the administrator restores the virtual machine snapshot. NetBackup Snapshot Manager instance B does not have access to the virtual machine's metadata. It restores the snapshot, but it does not know the virtual machine's specific configuration. Instead, it substitutes the default values for the storage size configuration. The result is a restored virtual machine that does not match the original.
The above configuration ensures that NetBackup does not use shared memory for communicating between NetBackup data mover processes.