HP OneView 1.05 User Guide

30.5 Using REST APIs to restore an appliance from a backup file
Prerequisites
Minimum required session ID privileges: Infrastructure administrator
You have uploaded a backup file to the appliance.
Restoring the appliance from a backup file using REST APIs
1. Initiate the restore process.
POST /rest/restores
The {restore URI} is returned.
2. List the status of the restore process.
GET /rest/restores
30.6 Creating a custom script to restore an appliance
If you prefer to write a script to restore an appliance from a backup file, see “Sample restore
script” (page 302) for a sample PowerShell script that you can customize for your environment.
30.7 Post-restoration tasks
During a restore operation, the appliance reconciles the data in the backup file with the current
state of the managed environment. There are some discrepancies that a restore operation cannot
resolve automatically, for example, if servers were added after the backup file was created. The
network configuration on these servers is unknown to the appliance after a restore and could result
in duplicate MAC addresses and World Wide Names (WWNs), as a result.
After a restore operation completes, you must manually resolve any remaining alerts and add these
servers back into the appliance to eliminate the risk of duplicate IDs. You must also perform manual
cleanup of hardware (servers, interconnects, and enclosures) if server profiles are forcibly unassigned
or the hardware is forcibly removed without first being unconfigured.
Preventing duplicate IDs on the network after a restore
1. After a restore operation is complete, re-add any enclosure or server hardware added since
the selected backup.
NOTE: For any enclosures added since the last backup that you decide not to re-add after
the restore, avoid duplicate IDs by running the Onboard Administrator SSH command clear
vcmode on these enclosures. Running this command ensures the virtual MACs and WWNs
on the server blades in the enclosure have been cleared.
2. For any server profile alerts about the profile not matching the server hardware:
a. Identify all server profiles with a mismatch-type of error message. Make a list of these
server profiles and the assigned server hardware.
b. Power off the server, and then unassign all of the server profiles individually. From the
Server Profiles screen, select ActionsEdit, and then select Unassign from the server
hardware drop down selector. Click OK.
c. Select ActionsEdit again, and then reassign all of the documented profiles to the
documented server hardware.
3. For any alerts about ID ranges, the Network administrator should examine the address and
identifier ranges and edit them, if needed.
4. Re-create any profiles for the servers in any enclosures that were added in step 1.
30.5 Using REST APIs to restore an appliance from a backup file 245