14.1.1 Resources Saved when the Backup Command is Executed

This section explains the definition information and the configuration information that is saved when the backup command is executed.

Resources saved when the backup command is executed are shown below.

Table 14.1 Overview of types of resources backed up on each server
Resource type	Resource overview	Master server		Development server	Collaboration server
Resource type	Resource overview	Primary	Secondary	Development server	Collaboration server
OS configuration- related information	Information configured separately for each server OS, such as the hosts file and bdpp.conf, which is the configuration file of this product.	Y	Y	Y	Y
Image file-related information	Image files such as slave server clone images and the related management information.	Y (*1)	N	N	N
DFS configuration information	Information relating to the configuration and definitions of the DFS, such as the DFS file system configuration information.	Y	Y	Y	Y
Configuration information for this product	Information relating to the configuration and definitions for systems that use this product, such as the slave server definitions file.	Y	Y	Y	N
Hadoop configuration information	Information relating to the configuration and definitions for Hadoop on this product, such as the definitions file for configuring Hadoop parameters.	Y	Y	Y	N

Y: Backed up

N: Not backed up

*1: Clone image backup on the primary master server can be skipped by executing the bdpp_backup command with the -q option specified. Note that the image file-related information is not backed up in a virtual environment.

Backup storage directory

When the bdpp_backup command is executed, a parent directory named FJSVbdpp-backup is created in the specified backup destination directory. The saved resources are then classified by type and stored in this parent directory.

The table below shows the types of resources (backup) stored in the directories that are created.

Table 14.2 Directories created under the FJSVbdpp-backup directory and the resources stored
Directory name	Stored resource type
SYS	OS-related information
ROR	Image file-related information
PDFS	DFS configuration information
BDPP	Configuration information for this product
Hadoop	Hadoop configuration information

Note

The structure of directories created under FJSVbdpp-backup varies for each server, because the resources to be backed up differ for the primary master server, the secondary master server, development servers, and collaboration servers.

Backup size

The table below provides an estimate of the size of resources saved at backup (the capacity of the FJSVbdpp-backup directory).

Check the available disk space on the relevant server before performing backup to prevent backup failure due to insufficient disk space.

Table 14.3 Disk space required on each server
Execution environment	Disk space (MB)	Remarks
Primary master server	10 + cloneImageFileSize	The approximate disk space required when creating a clone image file. If not creating a clone image file, use 10 MB as an estimate.
Secondary master server	10	-
Development server	10	-
Collaboration server	10	-

Note

When the bdpp_backup command is executed on the primary master server, separate disk space is required temporarily for tasks. Refer to "[Master Server]" in "3.2.3.2 Dynamic Disk Size" for information on the temporarily required disk space.

Information

Obtaining the clone image file size

This section explains how to obtain the clone image file size.

Log in to the master server.
Execute the bdpp_listimage command, and confirm the current storage location of the clone image file.
Specify the directory confirmed at Step 2, and execute the du command.
The following example shows /var/opt/FJSVscw-deploysv/depot as the storage area of the clone image file.
```
# du -hs /var/opt/FJSVscw-deploysv/depot <Enter>
```