Unregistering a vSnap server

Edit online

If required, you can unregister a vSnap server that is no longer used in your IBM Storage® Protect Plus environment.

Before you begin

When a vSnap server is unregistering, all recovery points that are associated with the vSnap server are purged from IBM Storage Protect Plus during the next maintenance job.
Attention: Unregistering of a vSnap server can result in loss of data.
Before you unregister a vSnap server, review the scenarios to determine whether unregistering is appropriate or whether other action must be taken.

Scenario 1: The vSnap server is temporarily down due to storage or network issues.

  • Do not unregister the vSnap server. If you unregister the vSnap server, recovery points that are associated with the server will be purged and backups will be rebased.
  • Complete the necessary storage or network maintenance to bring the vSnap server back online.

Scenario 2: The vSnap server is assigned a new host name or IP address.

  • Do not unregister the vSnap server. If you unregister the vSnap server, recovery points that are associated with the server will be purged and backups will be rebased.
  • Edit the settings for the vSnap server to specify the new host name or IP address. To edit the settings for a vSnap server, follow the instructions Editing settings for a vSnap server.

Scenario 3: The vSnap server is not in use, and there are no plans to reuse it.

  • Unregister the vSnap server and run a maintenance job to ensure that recovery points that are associated with the vSnap server are purged from IBM Storage Protect Plus.
    • Incremental backups of the data that was present on the vSnap server will no longer be possible.
    • Recovering data that was present on the vSnap server will no longer be possible.
  • Subsequent runs of backup jobs will automatically create new volumes on another vSnap server in the same site and will perform new base backups.

Scenario 4: The vSnap pool is lost and you want to build a new pool on the same vSnap server.

  1. Unregister the vSnap server and run a maintenance job to ensure that recovery points that are associated with the old vSnap pool are purged from IBM Storage Protect Plus.
    • Incremental backups of the data that was present in the old pool will no longer be possible.
    • Recovering data that was present in the old pool will no longer be possible.
  2. On the vSnap server, create a pool.
  3. Add the vSnap server back into IBM Storage Protect Plus. To add a vSnap server to IBM Storage Protect Plus, see Registering a vSnap server as a backup storage provider.
    • Subsequent runs of backup jobs will automatically create volumes on this or another vSnap server in the same site and will perform new base backups.

Scenario 5: The vSnap pool or server is lost and you intend to repair it. This can be achieved by replicating data from a vSnap replication server.

  • Do not unregister the vSnap server from IBM Storage Protect Plus. The deletion process will cause backups to be rebased.
  • Replace the vSnap server. For information about replacing a failed, primary vSnap server, see this section Troubleshooting vSnap servers.

Procedure

To unregister a vSnap server, complete the following steps:
  1. In the navigation panel, click System Configuration > Storage > vSnap servers.
  2. Select the vSnap server, and then click Delete device.
  3. Confirm removal of the vSnap server by entering the code in the text box. Click UNREGISTER to delete the server from IBM Storage Protect Plus.