Renaming nodes on the IBM Storage Protect server

Edit online

Before you upgrade your environment from Data Protection for Microsoft Hyper-V version 8.1.2 or earlier to version 8.2.2, you and the IBM Storage Protect server administrator must rename the nodes on the server.

About this task

When you rename the exiting node names on the IBM Storage Protect, you must use the naming convention as described in Step 1 .

Restriction: If you use the configuration wizard to configure Data Protection for Microsoft Hyper-V, you must complete the configuration before you can restore older virtual machine (VM) backups that were created with Data Protection for Microsoft Hyper-V version 8.1.2 or earlier. Otherwise, you cannot restore older VM backups with the Data Protection for Microsoft Hyper-V Management Console.

If you manually configure Data Protection for Microsoft Hyper-V and use the data mover command line to restore VMs, the older node names are still operational until you run the configuration wizard.

Procedure

The IBM Storage Protect server administrator completes the following steps:

  1. Use the RENAME NODE server command to rename the existing Hyper-V node name (specified by the asnodename option) to a new target node name that conforms to the following naming conventions:
    • For a stand-alone Hyper-V host environment: hostname_HV_TGT
    • For a cluster environment: clustername_HV_TGT

    For example, for a cluster with cluster node name Cluster1, the new target node name becomes Cluster1_HV_TGT or prefix_Cluster1_HV_TGT_suffix.

    You can also add a prefix and a suffix to the default node name. For example, prefix_hostname_HV_TGT_suffix or prefix_clustername_HV_TGT_suffix.

    For instructions about adding a prefix and suffix to the node name, see Customizing node names.

    Restriction: You cannot use node names that do not conform to these naming conventions. When you run the Data Protection for Microsoft Hyper-V configuration wizard, the new target node and associated data mover nodes with the new naming conventions are automatically registered on the IBM Storage Protect server. The necessary Windows services are also configured on the local Windows host.
  2. Use the UPDATE SCHEDULE server command to update existing schedules with the following required parameters:
    • Include the ACTION=BACKUP and SUBACTION=VM parameters in the schedule definition.
    • Update the option string as follows:
      • For a stand-alone host name: options='-asnodename=hostname_HV_TGT -domain.vmfull="all-vm"' or options='-asnodename=prefix_hostname_HV_TGT_suffix -domain.vmfull="all-vm"'
      • For a cluster name: options='-asnodename=clustername_HV_TGT -domain.vmfull="all-vm"' or options='-asnodename=prefix_clustername_HV_TGT_suffix -domain.vmfull="all-vm"'

    For more information, see Managing backup schedules for a host or cluster machine.

  3. Optional: Update the node replication parameters by issuing the REPLICATE NODE command on the IBM Storage Protect server:
    • For a stand-alone host, replicate data on the hostname_HV_TGT or prefix_hostname_HV_TGT_suffix node.
    • For a cluster, replicate data on the clustername_HV_TGT or prefix_clustername_HV_TGT_suffix node.

Complete the following tasks on a Hyper-V host:

  1. Upgrade Data Protection for Microsoft Hyper-V to version 8.2.2 on a stand-alone host or on all hosts in a cluster.

    For instructions, see Running a typical installation of Data Protection for Microsoft Hyper-V.

  2. Run the configuration wizard on the Hyper-V host. For clusters, run the wizard on one of the hosts in the cluster, typically your local Windows host.

    For instructions, see Configuring Data Protection for Microsoft Hyper-V with the wizard.

  3. Associate a schedule with the new target node name by using the Backup Management window in the Data Protection for Microsoft Hyper-V Management Console.

    For instructions, see Managing backup schedules for a host or cluster machine.

  4. Verify your configuration by running backup and restore operations in the Data Protection for Microsoft Hyper-V Management Console.
    For instructions, see:
  5. Complete the following cleanup tasks after the configuration is verified:
    • The IBM Storage Protect server administrator deletes the old data mover nodes by using the REMOVE NODE server command.
    • The Hyper-V administrator removes the services that were created for the old cluster node and data mover nodes by running the dsmcutil remove command on the stand-alone host or each host in a cluster.

      For more information, see the REMove command in Dsmcutil commands: Required options and examples.

Results

You can protect your Hyper-V VMs with Data Protection for Microsoft Hyper-V.

Tips for viewing backup history: The backup history that occurred before the node update is no longer available. However, all backups can still be restored with the Restore wizard or the command line. After the node update, the backup history is available for the initial and subsequent backup operations.

Immediately after the node update in cluster configurations, you can view and restore VM backups only from the cluster view, not from the host view. The host view contains only the VMs that are owned by that host node. After the node update, the backups are not owned by the host node. After successful backups are run, the VMs can again be backed up and restored from the host view.

What to do next

In some situations, one or both of the following tasks might need to be completed:
  • The IBM Storage Protect server administrator verifies that the target node is granted proxy authority for the data mover node by issuing the QUERY PROXY NODE server command.
  • The Hyper-V administrator restarts the client acceptor service on the Hyper-V host.

The IBM Storage Protect server administrator runs the schedule so that backup reporting can be displayed correctly for the updated nodes.