Restore Backup

1 Description

This instruction describes how to restore a backup.

2 Procedure

2.1 Restore Backup

Prerequisites

No documents are required.
No tools are required.
The following conditions must apply:
- No other backup operation is in progress.
- A backup to restore is available in the system.
- The name and path of the backup to restore is known.
- An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
- The user has root permission.

Steps

In certain cases, for example, node reinstantiation, the MAC addresses in the underlying infrastructure can be changed since the backup was created. Therefore, the restored backup does not work because the altered MAC addresses and additional steps are needed.

To restore a backup, choose one of the following options:
- Restore a backup when the MAC addresses have not been changed, see Section 2.2 Restore Backup When MAC Addresses Have Not Been Changed.
- Restore a backup when MAC addresses have been changed, see Section 2.3 Restore Backup When MAC Addresses Have Been Changed.

2.2 Restore Backup When MAC Addresses Have Not Been Changed

Steps

Navigate to the BrmBackupManager managed object, for example:
>dn ManagedElement=NODE06ST,SystemFunctions=1,BrM=1,BrmBackupManager=SYSTEM_DATA
Specify the backup to restore, for example:
(BrmBackupManager=SYSTEM_DATA)>BrmBackup=PERF_BACKUP_NAME1_20140428_175907
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.

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 (see View Progress Report) until the system reboot is triggered. After the system is rebooted, the progress report is reset to default values.

2.3 Restore Backup When MAC Addresses Have Been Changed

Note:: Only instantiate the node with the same HOT file.

Steps

On the instantiated Virtual Network Function (VNF), pull the MAC addresses section from cluster.conf /cluster/etc/cluster.conf.
Note:
To keep the original Payload (PL) numbering for a scaled out cluster, add a comment about the MAC addresses in each of the PL-<X>.conf files under the /cluster/etc/cluster.conf.d.
Decompress the exported backup.
The following is an example file structure of the decompressed backup:

backupinfo.xml backupinfo.xsd config.md5sum config.metadata config.tar.gz software.md5sum software.metadata software.tar.gz validate.md5
Decompress the config.tar.gz file.
Result:
The file is decompressed in the /tmp/backup_x/system/config/lotc-ana90139/etc/ directory.
In the decompressed cluster.conf file, replace the MAC addresses section with the pulled MAC addresses obtained in Step 1.
Note:
To keep the original PL numbering, restore the MAC addresses in each of the PL-<X>.conf files under the /tmp/backup_x/system/config/lotc-ana90139/etc/cluster.conf.d directory, with the addresses collected in Step 1.
Remove lde-config.xml in the /tmp/backup_x/system/config/lotc-ana90139/etc/ directory.
Recompress the modified content of the config.tar.gz
For example, tar -zcf config.tar.gz system
Calculate and save the new checksum values:
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
Recompress the backup file.
Import the modified backup to the system, see Import Backup.
Restore backup by following the instructions in Section 2.2 Restore Backup When MAC Addresses Have Not Been Changed.
Note:
The following cluster sizes apply to backups 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).

1	Description
2	Procedure
2.1	Restore Backup
2.2	Restore Backup When MAC Addresses Have Not Been Changed
2.3	Restore Backup When MAC Addresses Have Been Changed