Block Storage Backup

This section describes the procedure for taking the backup of Session Monitor's Block Storage.

IMPORTANT: This section is applicable only if the node type is Mediation Engine.

It can take hours to complete the backup of Block Storage, depending on the size of Block Storage and the network bandwidth between the source and the target machine. In our testing in lab, it took ~1 day 21 hours to complete the backup procedure for Block Storage of size ~19 TB with an average network speed of ~123MB/sec.

Take a call on the task - if you want to copy the Block Storage data directly on the Target Machine (where Release 5.2 RPM will be installed) as part of Strategy-2.
First copy the Block Storage data onto some temporary network drive and then copy the Block Storage data from the temporary network drive to the Target Machine as part of Stragegy-1. If you select Strategy - 2, the total time taken to complete the procedure will be double.

Check the space availability on both Source and Target Machines.
1. Run this command to check the block storage size of your Session Monitor Server (Source Machine).
```
du -sh /opt/oracle/ocsm/var/vsi/storage/
```
2. Run the following command on the backup location of the Target Machine (Remote Server or Shared Drive) to get the available space:
```
df -kh --output=avail /path/to/copy/backup
```
3. Compare the output of the two commands, and ensure that the available space in the Target Machine is greater than the block storage size of the Source Machine.
Get the backupAndRestoreBlockStorage.sh script file present in the Session Monitor installation software RPM .zip file.
1. Copy the file backupAndRestoreBlockStorage.sh to the /root/ directory of your Session Monitor Server.
If the backup location is selected on a Remote Server (it could be either the Remote Server selected as part of Strategy-1 or the newly created Target machine as part of Strategy-2), make sure that you have enabled passwordless login by transferring SSH key to Remote Server. For more information, see Generate an SSH Key to authorize the Remote Server for passwordless SSH logins.
Execute the backupAndRestoreBlockStorage.sh script.
1. Run the following command to provide the necessary permissions for the script:
```
chmod +x backupAndRestoreBlockStorage.sh
```
2. To begin the backup of block storage, execute the script:
```
./backupAndRestoreBlockStorage.sh
```
  Select the location to copy the backup (Remote Server or Shared Drive) when prompted. The script prompts for the IP address and the path to store the backup based on your input.
  
  Note:
  If the Remote Server is the newly created Target Machine as part of Strategy 2, the block storage data must be directly copied to the location /opt/oracle/ocsm/var/vsi/storage/. Make sure Session Monitor services are stopped on the Target Machine before copying the block storage data.
  Example for Remote Server:
```
[root@localhost ~]# ./backupAndRestoreBlockStorage.sh
 
Starting Backup of Block Storage...
 
Where do you want to copy the Backup ?
     1. Remote Server (e.g. SAN, newly created OCSM as part of Strategy-2 etc.)
     2. Mounted Disk (e.g. NFS/NAS/DAS etc.)
Your Input is:
1
Remote Server's IP:
10.184.19.114
Remote Server's User (used to ssh):
root
Remote Server's Path to Store Backup:
/root/ocsmBackup/blockStorageBackup/ OR </opt/oracle/ocsm/var/vsi/storage/> (if Remote server is Target machine as part of Strategy-2)
 
Block storage backup copying in progress ! Please wait until finished...
```
  Example for Mounted Disk:
```
[root@kvm248-109-vm9 ~]# ./backupAndRestoreBlockStorage.sh
 
Starting Backup of Block Storage...
 
Where do you want to copy the Backup ?
     1. Remote Server (e.g. SAN, newly created OCSM as part of Strategy-2 etc.)
     2. Mounted Disk (e.g. NFS/NAS/DAS etc.)
Your Input is:
2
Backup Path of Mounted Disk:
/mnt/oracle/ocsmBackup/blockStorageBackup/
 
Block storage backup copying in progress ! Please wait until finished...
```
  Note:
  During the backup process, if copying of any backup files is interrupted due to any network connection issue, system restarts, and so on, run the script again to resume copying.