Backup and restore issues, Backing up and restoring vcem – HP Virtual Connect Enterprise Manager Software User Manual
Page 106
5.
Click the VC Domains tab, for each VC Domain with "Configuration Mismatch" status, click VC Domain
Maintenance
. To confirm the resynchronization of the selected VC Domain with the VC Domain Group
configuration, click OK.
6.
Repeat steps 1 and 2 for the VC Domain where the changes were made.
7.
In the Virtual Connect Manager user interface, create the Ethernet networks (VLANs tagged) in the
desired shared uplink set.
8.
Go back to VCEM and complete VC Domain Maintenance by clicking Complete VC Domain
Maintenance
.
Backup and Restore issues
This section details backup and restore issues.
Backing up and restoring VCEM
In the event of catastrophic and complete VCEM failure, all server blades continue to operate, and the
integrity of the server application and data are not compromised.
VCEM can be restored to an operational state after complete loss of the VCEM Application or Database.
While it is possible to restore VCEM to its state before the loss, minor or major configuration loss might
occur, depending on the availability of a database backup. If no database backup is available, then a large
amount of information can be reconstructed from the contents of the Virtual Connect modules.
It is important that you understand what information is stored in the database, and can be lost without proper
backup practices.
Figure 13-1 Backing up and restoring VCEM
The Domain Network and SAN Configuration and assigned Server Profiles can be recovered from the Virtual
Connect modules. The VC Domain Group definitions, MAC and WWN custom ranges, and MAC and
WWN address exclusions are stored only on the Management Server.
For more information on performing backups and restoring VCEM, see “Backing up and restoring HP Systems
Insight Manager 5.3 data files in a Windows environment” at the HP SIM Information Library at
VCEM database is inaccessible or irretrievable with no backup, or VCEM file systems are corrupt
with no backup
Without a backup, the VCEM cannot restore to the original point. But the network and SAN configuration
and assigned server profiles can be recovered from the Virtual Connect modules. Reinstall the VCEM to a
fresh system, ensuring that the backup is well prepared on VCEM and its database on the new VCEM. For
more information, see
To resolve this issue:
106 Troubleshooting VCEM