Troubleshooting guide

7 — 5620 SAM database management
7-14 Alcatel-Lucent 5620 Service Aware Manager
5620 SAM
System Administrator Guide
Procedure 7-11 To perform an immediate 5620 SAM database
backup using a CLI
Perform this procedure to initiate an on-demand 5620 SAM database backup using a CLI.
1 Log in as the Oracle management user on the database station.
2 Open a console window.
3 Enter the following to start the database backup:
bash$ path/install/config/samdb/SAMbackup.sh backup_directory ↵
where
path is the 5620 SAM database installation location, typically /opt/5620sam/samdb
backup_directory is the directory that is to contain the database backup file set
Depending on the database size, a backup may require several hours to complete.
4 When the backup is complete, close the console window.
Caution 1 — Ensure that there is sufficient disk space to store the
database backup file set. The backup directory must be at least five
times as large as the expected database backup size. For more
information, contact Alcatel-Lucent technical support, or see the
5620 SAM Planning Guide.
Caution 2 — The Oracle management user requires read and write
permissions on the backup directory that you specify.
Caution 3 — When you back up a 5620 SAM database, you must specify
a backup directory path that does not include the 5620 SAM database
installation directory, or data loss may occur. The typical 5620 SAM
database installation directory is /opt/5620sam/samdb.
Note 1 — You can perform only a full backup using a CLI script. To
perform a partial backup, see Procedure 7-10.
Note 2 — The 5620 SAM backs up the Oracle encryption wallet during a
database backup, and restores the wallet during a database restore. In
a redundant deployment, the 5620 SAM automatically replicates the
encryption wallet from the primary to the standby database after the
standby database reinstantiation.
Note 3 — During a database backup, the performance of GUI or OSS
operations may be affected. Alcatel-Lucent recommends performing a
database backup only during a period of low 5620 SAM activity.
Note — In a redundant 5620 SAM system, you must log in to the primary
database station.
Release 13.0 R2 | May 2015 | 3HE 09815 AAAB TQZZA Edition 01