Running the OPBackup command (Oracle)

When you use the IBM OpenPages® application backup utility, run the OPBackup command in a command or shell window.

The OPBackup command does the following:

Stops all OpenPages services on the local application server before performing any backup operation
Backs up OpenPages application and environment files
Restarts the services on the local application server when the backup activities are complete

See Running a live backup (Oracle) if you want to perform a backup without stopping services.

Procedure

If global search is enabled, disable it:
1. Log in to OpenPages as an administrator.
2. Click Open Administration menu > System Configuration > Global Search and click Disable.
Shut down all non-admin application servers.
Open a command or shell window on the OpenPages admin application server.
Navigate to the <OP_Home>/aurora/bin directory.
Run the following backup command:
Windows
```
OPBackup <path-to-backup-location>
                        
```
Linux®
```
./OPBackup.sh <path-to-backup-location>
                        
```
Where <path-to-backup-location> is the full path of the directory where the backed up files are located on the OpenPages application server. If a file path is not specified, the OPBackup command uses the backup location that is specified in the BACKUP_LOCATION parameter of the <OP_HOME>|aurora|bin|op-backup-restore.env file.
You can use the following optional parameters:
- app-nodb: Back up everything except the OpenPages database.
- dbonly: Back up only the OpenPages database. (Applies to Oracle databases only.)
For example:
```
./OPBackup.sh <path-to-backup-location> app-nodb
```

Results

The backup process creates a log file in the <backup-directory-name> directory. Each time you run the OPBackup command, a separate log file is generated.