There are two types of backups: Derby Backup which only backs up the derby database (described below) and Full Backup which backs up database and UVMS (for full backup refer to section "unibackup").
Derby Backup:
Write access to the database will be blocked during the backup. The derby backup can be created:
From the CLI using the uniderbybackup command (refer to section "uniderbybackup". For example:
uniderbybackup [-h] [-s [-b <backup directory>]]
Periodically by enabling related UVMS settings in UVC:
Enabling derby backups: UVMS node settings-> Optional Services, and enable backup by changing the value of “Enable Online Backup” from No (default) to Yes
Configuring derby backups: UVMS node settings-> Backup (refer to section Periodic On-line Backup Configuration below)
When a backup is triggered, UVMS:
If a "File too large" error occurs during the backup procedure of the UVMS database, the UVMS node setting UXMAXFD should be increased.
Derby Restore:
There are two ways for restoring Derby Backups (both in the command mode, refer to section "uniderbyrestore":
A Snapshot restore mode: it restores the database at the time of backup, and any subsequent transactions will be lost when performing a derby restored. This solution is less secure but the copy is faster than a more secure mode called the rollforward mode. For example:
uniderbyrestore -h -s -b <derby backup directory>] -mode SNAPSHOT
A Roll-Forward restore mode: it could restore a damaged database to the most recent state before a failure occurred. Roll-forward logs should be enabled in UVMS node settings (UVMS node settings-> Backup). For example:
uniderbyrestore -h -s -b <derby backup directory>] -mode ROLLFORWARD
To restore a database by using roll-forward recovery, you must already have a backup copy of the database, all the archived logs since the backup was created, and the active log files.
To enable online backup, set: Administration mode > Nodes > Management Server Node Settings> Optional Services > Enable Online Backup for Derby=Yes. (Default value = No). This modification will only be taken into account when the UVMS is restarted.
The following parameters, concerning online backup management, are set in Administration mode > Nodes > Management Server Node Settings> Backup
Both the backup directory and the log directory should be kept in a separate fault-tolerant environment. They are critical to disaster recovery. The log file directory can be specified In the “derby.storage.logDeviceWhenBackedUp” variable in the <UVMS root>/data/data/uvmsdb/service.properties file.
When the process, launched by UVMS, finishes the new backup, the oldest backup is removed.
Refer to the Univiewer User Guide, section "Node Settings > Backup" for more details.
The uniderbybackup command backs up the UVMS Derby database while UVMS is running.
The uniderbybackup command can run either in silent mode or in interactive mode.
The uniderbybackup command is located in the univiewer_server\<nodename>\app\bin directory.
Syntax:
uniderbybackup [-h] [-s [-b <backup directory>]]
-s
Optional: Silent mode. When the silent option is not specified, the command line will ask the user for all the parameters that have not been provided in the command.
-b <val>
Optional: Full path of the backup directory
if -s is specified and the -b argument is not found, the value is loaded from the values.xml file.
If the path contains spaces, in silent mode you must enclose it with quotes. The directory will be created by the backup operation. If the directory already exists, the backup operation will fail.
-h
Optional: Displays the usage text
Example:
uniderbybackup –s -b D:\Backups\Derby
Back up the Derby UVMS database in the "D:\Backups\Derby" directory. The SNAPSHOT mode is used. The command creates a time-stamped sub-directory containing the database backup.
The uniderbyrestore command line enables you to restore a UVMS Derby database from a backup generated with the uniderbybackup command or with the UVMS embedded hot backup system (refer to the Univiewer User Guide, section “Nodes> Node Settings>Optional Services”).
All the content of the Derby database will be overwritten with the backup data.
Make sure UVMS is stopped before attempting to restore the database whatever the backup mode.
Carry out a full backup using the unibackup -l FULL command prior to running uniderbyrestore.
The uniderbyrestore command is located in the univiewer_server\<nodename>\app\bin directory.
Syntax:
uniderbyrestore [-h] [-s -b <backup directory>] -mode SNAPSHOT|ROLLFORWARD
-s
Optional. Silent mode
When the silent option is set, all the parameters must be provided in the command line. (-b mandatory)
When the silent option is not specified, the command line will ask the user all the parameters that have not been provided in the command.
-b <val>
Optional. Full path of the backup directory.
Mandatory with -s.
If the path contains spaces, in silent mode you must enclose it with quotes.
-mode <val>
Optional. Restoration mode: Two restoration modes are supported:
-h
Optional. Displays the usage text
Example:
uniderbyrestore –s -b D:\Backups\Derby -mode ROLLFORWARD
Restore the Derby UVMS database from the backup saved in the "D:\Backups\Derby" directory. Archive logs and active logs will be replayed to restore the database to its most recent state. Roll-forward restore can only be applied to a backup made in ROLLFORWARD mode.
As of version 6.10.41, documentation new updates are posted on the Broadcom Techdocs Portal.
Look for Dollar Universe.