This section explains how to back up a server.
This section explains how to back up a primary or secondary master server, development server, or collaboration server.
To back up a server other than a slave server, execute the bdpp_backup command on the relevant server.
Note
Execution of the bdpp_backup command will not back up MapReduce applications developed on the development server, nor existing business systems or business data on the collaboration server. These must be backed up and saved separately by the user.
Backup procedure
Log in to the primary master server using root permissions.
Execute the bdpp_stop command to stop Hadoop.
Log in to the server to be backed up using root permissions.
Execute the bdpp_backup command.
Example
If storing the backup under /var/backup on the primary master server and not backing up the clone image:
# /opt/FJSVbdpp/bin/bdpp_backup -d /var/backup -q <Enter>
Note
If execution of the bdpp_backup command fails, refer to the output message and check its meaning and corrective action, or if required, refer to the backup log (/var/opt/FJSVbdpp/log/bdpp_backup.log) and remove the cause of the failure.
If a backup storage directory and subdirectories were created when the previous backup failed, delete them all and then re-execute the backup command.
If an option is not specified when the bdpp_backup command is executed on the primary master server, the backup will include clone images. Note that in this case, the time required for backup may increase in proportion to the file size of the clone image multiplied by the number of images, because copying the files (disk I/O) is time-consuming.
Use the bdpp_removeimage command to remove any unnecessary clone images prior to performing backup. If required, specify the -q option to skip the backup of clone images altogether.
Refer to "A.11 bdpp_removeimage" for details.
Archive the backup created by using the backup command, and save it on other media such as another server or on tape.
Information
Archiving backup
The following example shows how the tar command is used to archive the backup storage directory created under /var/backup, as well as its subdirectories.
# cd /var/backup <Enter> # tar cvf FJSVbdpp-backup-master1-20121010.tar FJSVbdpp-backup <Enter>
This section explains how to back up a slave server.
A slave server is backed up by creating a clone image of the slave server.
Create the clone image from a slave server that is already installed.
Refer to "6.3.1.4 Creating a Clone Image" for information on how to create a clone image.
Point
Backup is not required for slave servers installed in a virtual environment.
