Managing vSnap servers
Each vSnap server is a stand-alone appliance, which is deployed virtually
or installed physically on a system that meets the minimum requirements. Each vSnap server in the
environment must be registered in IBM Storage® Protect
Plus so
that the server is recognized.
Registering a vSnap server as a backup storage provider IBM Storage Protect Plus so that it can be recognized as a backup storage provider.Initializing the vSnap server Migrating onboard vSnap data to a stand-alone vSnap server IBM Storage Protect Plus Version 10.1.7, the onboard vSnap server is no longer included. If you upgrade your system to IBM Storage Protect Plus 10.1.7 or later, but data remains in an onboard vSnap server from a previous release prior to version 10.1.7, you must migrate the data to a new, stand-alone vSnap server.Expanding a vSnap storage pool IBM Storage Protect Plus reports that a vSnap server is reaching its storage capacity, the vSnap storage pool must be expanded. To expand a vSnap storage pool, you must first add virtual or physical disks on the vSnap server. To add disks, choose to either add virtual disks to the vSnap virtual machine or add physical disks to the vSnap physical server. Changing the throughput rate Replacing a failed vSnap server IBM Storage Protect Plus environment, the target vSnap server is the destination for backing up data. If the vSnap server becomes corrupted or fails to respond, you can replace the vSnap server with a new server and recover the stored data.Installing iSCSI initiator utilities vSnap server administration reference IBM Storage Protect Plus automatically manages its use as a backup target. Volumes and snapshots are created and managed automatically based on the SLA policies that are defined in IBM Storage Protect Plus .Troubleshooting vSnap servers