SnapManager for Virtual Infrastructure Best Practices

Detailed info of the following best practice round up can be found here.

General

  • The SMVI server component should be installed on the vCentre server
  • Transient data such as the guest operating system swap file, temp files and page files, should be moved to a separate virtual disk on a separate data store to prevent large snapshots due to high rate of change
  • Set vDisks that house temp/transient data to “Independent Persistent” to ensure SMVI does attempt to snap the volume that that vDisk resides on
  • Licences required for SMVI
    • SnapRestore
    • FlexClone
    • Any required NFS, iSCSI FC protocol licenses
    • When vCentre is installed on a VM the database associated with vCenter must not be installed on a virtual machine protected by SMVI to avoid time out issues. Where possible use a physical SQL server for vCenter
    • It is recommended to configure data store level backups instead of VM backups where possible to reduce admin overhead and increase restore options.

Backup/Restore

  • SMI .XML configuration files need to be on shared storage or backed up often to allow for recovery
  • Set the Startup of the SMVI to Manual if you do restore vCenter from an image level backup. Important because

“When the virtual machine running SnapManager for Virtual Infrastructure is backed up by SMVI, the current state of the SMVI backup workflow is captured within the Snapshot copies. Should the virtual machine be restored at a later date, SMVI within the virtual machine assumes that the host has failed in mid-workflow and attempts to resume backups at the point at which the Snapshot copy was taken. This can cause backups to run multiple times even if they were originally successful.”

  • After a restore of the SMVI vm remove the contents of the PROGRAMFILES%\NetApp\SMVI\server\crash directory and start the SMVI service
  • If Vmware In an environment experiencing heavy disk I/O this will greatly increase both the speed and success rate of backups. This will result in crash consistent backups only which is generally only an issue for databases or e-mail servers.
  • If a VM requires an RDM ( a requirement to use SnapDrive for SQL) it should be configured in physical mode. This will enabled the non RDM virtual disks (ie system partition) to be backed up using the vmware tool VSS integration.

Security

  • Create a separate storage admin account for SMVI to interact with the filer (don’t use the root account)
  • Enable and use SSL on the filer to ensure passwords are encrypted

References

http://www.vmware.com/pdf/vi3_vc_in_vm.pdf

http://media.netapp.com/documents/tr-3737.pdf

http://www.vmware.com/pdf/vsphere4/r40/vsp_vcb_15_u1_admin_guide.pdf

Advertisements
  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: