Backing Up the LSMS Manually

Before beginning a manual backup:

Read Understanding How the LSMS Backs Up File Systems and Databases.
Check the GUI notification information and surveillance logs for database errors before beginning the manual backup procedure to ensure that the LSMS is functioning correctly.
Check whether servdi is running before starting the manual backup. If servdi is running, wait for it to complete before running the manual backup.

Note: Backups can also be performed via the platcfg menu. For more information, see Using Restore Procedures.

The following procedure explains how to start a backup manually. If a backup procedure fails, contact the My Oracle Support (MOS).

Perform the procedure described in “Checking for Running Backups” to ensure that no other backup (automatic or manual) is already running.
Ensure that none of the following processes are running.
All of these processes use temporary file space on the LSMS. If you attempt to start a backup, you may run out of file space.
- Starting a standby node (to change its state from UNINITIALIZED "INHIBITED" to STANDBY)
- An import command
- An lsmsdb quickaudit command
- A query server snapshot (lsmsdb snapshot)
Log into the active server as lsmsmgr.
(For more information, see “Logging In to LSMS Server Command Line”.)
View the backup log and ensure that the backup completed successfully.
Note: The backup log shows only the active server’s backup results.
For more information, see Daily Determination of Success or Failure of Backup.
From the Main Menu on the active server, select Maintenance > Backup and Restore > Network Backup.
The Select Backup Configuration Menu is displayed.
Select Backup Configuration Menu
- plat.xml is provided by TPD and is used to back up all platform files (such as log, pkg, and rcs files) from LSMS to NAS.
- plat-app.xml is provided by LSMS and is used to back up all platform files (such as log, pkg, and rcs files) from LSMS to NAS.
- lsmsdb.xml is used to back up the LSMS database on NAS.
- lsmslogs.xml is used to back up the LSMS logs on NAS.
- Exit returns control to the Backup and Restore menu.
Select plat.xml as shown.
Press Enter and the Select Action Menu is displayed.
Select Backup on Active Server
- Advanced Options enables specification of backup host details, the archive directory, the repository, and other options. For example:
```
Backup Host: backupserver
Backup Host user: root
Archive directory: /Volumes/LVstorage
Repository: logs (automatically selected based on the type of backup selected previously)
Depth: 5 (numerical value, use of 1-5 is suggested)
Prune: (*)Yes or ()No
```
- View Index Table of Contents lists the data to be backed up.
- Test Backup performs a test backup.
- Backup performs backup of LSMS data on NAS.
- Exit returns control to the Backup and Restore menu.
Select Backup as shown.
When the backup is complete, press any key to continue.

Backup Complete on Active Server
Log into the standby server as lsmsmgr.
(For information, see “Logging in from One Server to the Mate’s Command Line”.)
Note: If the standby server is not functional, perform the rest of the procedures on the active server.
Select plat.xml on the standby server, and press Enter.

Select plat.xml on Standby Server
Select Backup.

Select Backup on Standby Server

Performing Backup Screen
When the backup is complete, press any key to continue.

Backup Complete on Standby Server
Select lsmslogs.xml on the standby server, and press Enter.

Select lsmslogs.xml on Standby Server
Select Backup.

Select Backup on Standby Server
When the backup is complete, press any key to continue.

Backup Complete on Standby Server
Select lsmsdb.xml, and press Enter.

Select lsmsdb.xml on Standby Server
When the server has completed loading the Select Action Menu displays.

Select Action Menu
Select Backup, and press Enter.

Backup
When the backup completes, press any key to continue.
Backup Complete
You can now exit to the Main Menu, or choose another menu item.