Contents

1   Introduction

This document describes how to restore a backup.

1.1   Prerequisites

This section describes the prerequisites, which must be fulfilled before using the procedure.

1.1.1   Conditions

The following conditions must apply:

• No other backup operation is in progress
• The name and path of the backup to restore is known.
• A backup to restore is available in the system
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress

2   Procedure

In certain cases (for instance node re-instantiation) the MAC addresses in the underlying infrastructure can be changed since the backup was created. In this case, the restored backup will not work due to the altered MAC addresses and additional steps are needed, see Section 2.2 Restore Backup When MAC Addresses Have Been Changed. If MAC addresses are not changed since the backup created, see Section 2.1 Restore Backup When MAC Addresses Have Not Been Changed.

2.1   Restore Backup When MAC Addresses Have Not Been Changed

To restore a backup:

1. Navigate to the BrmBackupManager managed object, for example:

   >dn
   ManagedElement=NODE06ST,SystemFunctions=1,BrM=1,BrmBackupManager=SYSTEM_DATA

2. Specify the backup to restore, for example:

   (BrmBackupManager=SYSTEM_DATA)>BrmBackup=PERF_BACKUP_NAME1_20140428_175907

3. Start the restore operation:

   (BrmBackup=PERF_BACKUP_NAME1_20140428_175907)>restore

   The system returns output true or false.

   Attention!

   Risk of system malfunction or traffic disturbance.

   A cluster reboot is automatically triggered when restoring a System Data backup. The resulting In-Service Performance impact corresponds to the time required for a cluster to restart after reboot.

4. Verify that the backup was successfully restored, for example:

   (BrmBackup=PERF_BACKUP_NAME1_20140428_175907>)show -v

   The following is an example output:

   BrmBackup=PERF_BACKUP_NAME1_20140428_175907 [...] asyncActionProgress <read-only> actionId=3 <read-only> actionName="RESTORE" <read-only> additionalInfo=[] <empty> progressInfo="PERMIT_PHASE is completed" <read-only> progressPercentage=33 <read-only> result=NOT_AVAILABLE <read-only> resultInfo="" <read-only> state=RUNNING <read-only> timeActionCompleted="1970-01-01T05:00:00" <read-only> timeActionStarted="2014-09-08T10:55:54" <read-only> timeOfLastStatusUpdate="2014-09-08T10:55:55" <read-only> progressReport <read-only> actionId=3 <read-only> actionName="RESTORE" <read-only> additionalInfo=[] <empty> progressInfo="PERMIT_PHASE is completed" <read-only> progressPercentage=33 <read-only> result=NOT_AVAILABLE <read-only> resultInfo="" <read-only> state=RUNNING <read-only> timeActionCompleted="1970-01-01T05:00:00" <read-only> timeActionStarted="2014-09-08T10:55:54" <read-only> timeOfLastStatusUpdate="2014-09-08T10:55:55" <read-only> [...]

Note:  

When performing a System Data backup restore, the restore progress can be monitored (refer to View Progress Report) until the system reboot is triggered. After the system is rebooted, the progress report is reset to default values.

2.2   Restore Backup When MAC Addresses Have Been Changed

Update the backup file before restoring it on an instantiated VNF (the node is to be instantiated with the with same HOT):

1. On the instantiated VNF pull the MAC addresses section from cluster.conf /cluster/etc/cluster.conf
2. Untar the exported backup.

   Example file structure of the extracted backup:

   backupinfo.xml backupinfo.xsd config.md5sum config.metadata config.tar.gz software.md5sum software.metadata software.tar.gz validate.md5

3. Untar the config.tar.gz, replace the MAC addresses section with pulled MAC addresses obtained in Step 1, for example, after untar the cluster.conf can be found at

   /tmp/backup_x/system/config/lotc-ana90139/etc/cluster.conf

4. Remove lde-config.xml

   For example, after untar the lde-config.xml can be found at /tmp/backup_x/system/config/lotc-ana90139/etc/lde-config.xml

5. Re-tar the modified content of the config.tar.gz

   for example, tar -zcf config.tar.gz system

6. Calculate and save the new checksum values running:

   md5sum config.metadata config.tar.gz > config.md5sum

   md5sum backupinfo.xml backupinfo.xsd config.md5sum config.metadata config.tar.gz software.md5sum software.metadata software.tar.gz > validate.md5

7. Re-tar the backup file.
8. Import the modified backup to the system, for more details refer to Import Backup.
9. Restore backup by following the instructions in Section 2.1 Restore Backup When MAC Addresses Have Not Been Changed

   Note:  

   The following cluster sizes apply to backup created on a (2+N) VNF and restored on a (2+M) VNF:

   M>N: The result is (2+N)

   M≤N: The result is (2+M)