Description
The mds_backup
backs up binaries and data from a Multi-Domain Server to a user specified working directory. You then copy the backup files from the working directory to external storage. This command requires Multi-Domain Superuser privileges.
The mds_backup
runs the gtar
and dump
commands to back up all databases. The collected information is stored in one *
.tar
file. The file name is a combination of the backup date and time and is saved in the current working directory. For example: 13Sep2019-141437.mdsbk.tar
Important - Starting from Take 76 of R80.30 Jumbo Hotfix Accumulator (PMTR-36614), the mds_backup
command generates a file with the *.tar
extension (<timestamp>mdsbk.tar
) instead of the *.tgz
extension (<timestamp>mdsbk.tgz
).
To back up a Multi-Domain Server:
mds_backup
command from a location outside the product directory tree to be backed up. This becomes the working directory.*.tar
file, together with the mds_restore
, gtar
and gzip
binary files, to your external backup location.Important notes about backing up and restoring in Management High Availability environment:
For more information:
Syntax
|
|
Parameters
Parameter |
Description |
---|---|
|
Shows help text. |
|
Executes without prompting to disconnect GUI clients. |
|
Batch mode - executes without asking anything (-g is implied). |
|
Specifies the output directory. If not specified explicitly, the backup file is saved to the current directory. You cannot save the backup file to the root directory. |
|
Stop Multi-Domain processes before the backup starts. |
|
"Dry run" - Show all files to be backed up, but does not perform the backup operation. |
|
Exclude logs from the backup. |
Notes:
mds_backup
from directories that will be backed up. For example, when backing up a Multi-Domain Server, do not run the mds_backup
from the /opt/CPmds-<current_release>/
directory, because it is a circular reference (backing up directory that you need to write into).mds_backup
does not collect the active Security log files (*.log
) and Audit log files (*.adtlog
). This is necessary to prevent inconsistencies during the read-write operations.Best Practice - We recommend that you do a log switch before you start the backup procedure.
$MDSDIR/conf/mds_exclude.da
t configuration file:log/*