Specifying Backup Data on Open Enterprise Server Nodes
Last updated
Last updated
The following illustrates an OES Linux node in a backup source pane. VOLA: requires NSS file system on the OES Linux node.
VOL1: or SYS:
A locally attached volume. This disk can be expanded to the file level.
/ or /boot
or /mnt/opt1
A volume for traditional (non-NSS) Linux file system. This disk can be expanded to the file level.
eDirDB:
A disk on an OES node running eDirectory 8.7 or higher. DPX can perform both base and incremental backup jobs on eDirDB, but backups are supported at the disk level only. RBS needs to be installed and configured properly for an eDirectory backup. For additional information about eDirDB disks, see The following rules apply for Micro Focus eDirDB disks.
For information about backups and restores of GroupWise, see Chapter 56: Micro Focus GroupWise Interface.
DPX uses the Micro Focus DSBK tool (or eMBox in DPX 4.9.1 and earlier) to dump the database to a file that will be backed up. The file will be placed in the logs directory in the directory unless otherwise specified.
DPX can perform both base and incremental backup jobs on eDirDB, but backups are supported at the disk level only.
A base backup of eDirDB is named edDBSK (or ed with eMBox) . For incremental backups, the string _i_ will be added and followed by a unique number (for example: edDBSK_i_168866440 for DBSK or ed_i_3138 for eMBox).
By default, the files that are generated by the Micro Focus tool are deleted after they are backed up.
You can only restore eDirDB to a new location, not to its original location. When you restore to a new location, base backup and incremental files are restored. Using the Micro Focus DSBK or eMBox tool, restore the incremental files in the proper order by checking their timestamps.
(Applies to eMBox only) If eDirectory 8.7 or later was1 installed using a communication port other than the default (8030), use the --edirport option in SSEVTHND to alert DPX. SSEVTHND is an environment variable.
eDirectory Roll Forward logging is not enabled by default. If you want your backup to be disaster recoverable, you should enable Roll Forward Logging.
You can back up NDS via one or more servers in the eDirectory tree to take advantage of the Replicator Rings inherent in eDirectory environments and to add some level of redundancy to your backups.
Ensure to back up the NDS via the “DSMASTER” node as identified in iManager. That is, ensure TSAFS is loaded at the time of backup on DSMASTER node.
Take regular base and incremental backups of NDS through the eDirDB disk exposed to in addition to regular base backups of NDS through the tree and schema disks. Doing so provides redundant backup images to minimize media-corruption risks and provides object-level restore support, if needed, as well as full-tree disaster recovery capabilities. eDirDB disk backups should not replace TSANDS-based backup images.
