Storix Software SBAdmin Oracle VMServer for x86 Recovery Guide - Manual (Page 5)

Storix System Backup Administrator 5 Oracle VM Server for x86 Recovery Guide
Copyright © 2014 Storix, Inc.
Storix is a registered trademark of Storix, Inc in the USA. SBAdmin is a trademark of Storix, Inc in the USA and other countries
You should examine the /etc/ovs/repositories file on the server and verify that the UUID is referring to the
correct device name.
Oracle VM Server for x86 version 2.2
List the repositories using the following command:
/opt/ovs-agent-latest/utils/repos.py –l
You may see output similar to the following:
[ * ] 450c66f5-6e10-4ca8-b086-c1413236f1f2 => ERROR
[ ] c0e18fd7-c162-4183-836b-c883f9b1b41c => mickey:/ovm
The output indicates that the root storage repository is not configured properly. After inspecting the log
files in /var/log/ovs-agent, you will find that the device or UDEV UUID that the device links to does exist.
Typically, this is because the device name changed or the UDEV UUID changed.
To reconfigure the repositories you should re-add each device as a repository and specify which UUID is
the root storage repository. Note that the UUID for each repository will be the same as at the time of the
backup because the UUID is stored in a file in the repository filesystem and was restored as part of the
recovery process.
In our example, the repository which was configured on device /dev/sda3 at the time of the backup was
replaced with device /dev/hda3 during the recovery. Therefore, we need to redefine the repository with the
proper device name and specify it as the root storage repository. We will also redefine the NFS-based
repository:
/opt/ovs-agent-latest/utils/repos.py –n /dev/hda3
/opt/ovs-agent-latest/utils/repos.py –r 450c66f5-6e10-4ca8-b086-1413236f1f2
/opt/ovs-agent-latest/utils/repos.py –n mickey:/ovm
The next step, regardless of the version of Oracle VM Server in use, is to restore the server pool configuration
from the Oracle VM Manager. This can be accomplished through the Oracle VM Manager Web Interface by
selecting the Server Pools tab, selecting the appropriate Server Pool Name, and selecting Restore. Note that
when restoring a server pool, all the data on the server pool master will be deleted and synchronized with the
latest information found in the database on the Oracle VM Manager.
After the server pool restore completes, you should have access to the repositories and resources on the Oracle
VM Server you just recovered.
Migrating Storage Repositories (version 3)
With Oracle VM Server 3 migrating the service repositories after recovery is typically not necessary. However
the following considerations are specific to version 3.
Oracle VM Server SMBIOS UUID
Upon recovery of an Oracle VM Server you may see the following error in the Oracle VM Manager.
“The manager already has a server SERVERNAME, at this IP address,
with SMBIOS UUID: xx:xx:....”