Top
ServerView Resource Orchestrator Cloud Edition V3.0.0 Operation Guide

8.1 Mechanism of Backup and Restoration

This section describes the mechanism of backup and restoration, including environment requirements, points to note, and the restart position after restoration, in a system in which this product is installed.


Backup and restoration environment requirements

The following conditions must be satisfied in the environments to be backed up and restored:

Points to note at backup and restoration

This section describes the points to note when backup and restoration is being performed.

Resources managed by this product and timing of update

The resource files managed by Resource Orchestrator are as shown below: When an operation described in the 'timing of update column' has been performed, a backup should be made.

Table 8.1 Resources to be backed up and timing of update

Target Resources

When Backup is Necessary

Necessity of Stopping Managers

Remarks

Certificates

None

No

Session encryption keys

After password saving (after execution of the rcxlogin -save command)

No

System images and cloning images

After addition, deletion, and modification of Physical L-Server images

No

Backup of system images and cloning images of virtual L-Servers are performed as a part of virtual machine backup operations.
Perform backup operations of virtual machines using the corresponding functions of VM management software.

Configuration definition information

After creation, registration, modification, unregistration, and deletion of L-Servers and resources

No

Information related to image files

Physical L-Server registration, deletion, movement. usage changes, power operations, conversion, and reversion

After the registration and unregistration of VM hosts

No

Definition files

Modification of definition files

No (Note)

Note) If the following definition files are to be backed up, the Manager must be stopped and offline backup must be performed.
- Some L-Platform management settings
- Tenant management and account management settings
- Operational status server list settings
- CMDB agent event log output settings

Image management information

After rcxadm imagemgr command operations

No

Metering information

Creation, change, deletion, move, or power operation of an L-Platform or L-Server

No

Home window announcement information

Announcement change

Yes

License agreement when users are added

License agreement change

Yes

Dashboard information

As required

Yes

Because it is updated as needed, stop the Manager and take a backup as required.

Operational status information

As required

Yes

Because it is updated as needed, stop the Manager and take a backup as required.

Application information

Application to use, modify, or cancel an L-Platform, or approval, assessment, dismissal, or cancellation of application

Yes

Terms of use or terms of cancellation of L-Platform

Change to terms of use or terms of cancellation

Yes


Disk space necessary for the backup

Disk space necessary for the backup is as follows.

Table 8.2 Resource to be backed up and disk space necessary for the backup

Target Resources

Disk space necessary for the backup

Configuration definition information

The file size of backup files varies depending on the number of resources defined in the configuration definition information.
When the number of VM guests is 1000VM, collection information temporarily becomes about 150MB. It becomes less than 2MB by compressing it.
Please prepare the backup area referring to this size.

System image or cloning image

Every time, when backing up, it is necessary. Therefore, when the backup is executed three times for instance, the capacity of image save area is three times necessary.
Please refer to "1.4.2.5 dynamic disk space" in the "Setup Guide VE" for the capacity of image save area.

Certificates
Session cryptography key
Definition files
Image management information
Home window announcement information
License agreement when users are added
Terms of use or terms of cancellation of L-Platform

The size of the file backed up changes according to the number of files backed up.

Please prepare the backup area referring to this size to need only the area of less than 1MB even if these 100 files are stored by 10KB or less any file.

Metering information

[Offline backup]

The size increases and decreases to the file backed up in proportion to the increase and decrease at the number of resources of metering objects and the retention period of the metering log. (*1)

[Online backup]

1KB(*1)

Dashboard information

The size increases and decreases to the file backed up in proportion to the increase and decrease of the number of L-Server templates and the number of tenants.
Please prepare the backup area referring to the following formulas when the dicker is defined in the L-Server template.
When the number of tenants is 100, about 6.6GB is necessary.

disk space = (67.0 + (55.5 number of * tenants)) * 1.2 (MB)

Operational status information

The size increases and decreases to the file backed up in proportion to the increase and decrease of the number of hosts and the number of guests of VM.
Moreover, capacity is different according to the VM management product.
Please prepare the backup area referring to the following formulas. About 19.4GB(VMWare, 50 hosts, and 1000VM (20VM/host)) is necessary.
disk space =
((N1 * hosts) + (N2 * guests)) * 1.2(MB)

[VMware] N1 = 2.0, N2=7.0

[Hyper-V] N1 = 92.0, N2 = 26.0

[Xen/KVM] N1 = 102.0, N2 = 7.0

Application information

The size increases and decreases to the file backed up according to the operating environment. Please calculate the total of the amount of disk under the control of the following directories, and prepare the backup area of the amount.

[Windows]

  • C:\SWRBADB

  • Installation_folder\SWRBAM

  • Installation_folder\SWOMGR

[Linux]

  • /etc/opt/FJSVswrbam

  • /var/opt/FJSVswrbam

  • /var/opt/FJSVJMCMN/etc

  • /var/opt/FJSVjmcal

  • /var/opt/FJSVJOBSC

  • /var/opt/FJSVfwseo/config/JM

  • /opt/FJSVJOBSC/bin

  • /etc/mjes

  • /var/spool/mjes

*1: The backup of metering information is gathered under the control of the directory specified by the rcxmgrbackup command at an off-line backup, and it is gathered in the area besides the specified directory at an online backup.
Please calculate a necessary amount of disk by backing up metering information referring to the following examples.
"Amount of disk necessary for the base backup" is necessary for an off-line backup.
It is necessary to total "Amount of disk necessary for the base backup" and "Amount of disk necessary for Difference backup" for an online backup.

In the following conditions, the amount of disk of about 12.6GB is necessary for about 1.3GB and online backups for an off-line backup.

Table 8.3 Condition necessary for backup of metering information

Items

Assumption value

Operating number of L-Platforms

1000

Number of resources per L-Platform

L-Server

1

Advanced Disk

1

Software

2

Operation Status

  • The following executions of every day

    • Return and disposition of ten L-Platforms

    • 1000 L-Server is started at start of work

    • When starting work, 1000 L-Server is stopped

  • A regular log is acquired every day

  • The metering log is maintained for one year

Frequency of online backup

  • The base backup for each of one month (the 30th) is executed.

  • Difference backup is executed every hour.

Table 8.4 Formula of log of metering each day
  • Standard of metering log capacity

    • Event log of L-Platform: 2.3 KB/time (A)

    • Event log against besides L-Platform : 0.6KB/time (B)

    • Regular log: 2.3 * number of L-Platform (KB) (C)

  • Log of metering each day

    (A) * Frequency of operation to L-Platform each day
    + (B) * Frequency of operation against besides L-Platform each day
    + (C) Number of L-Platform in which * is operated

    = 2.3KB * 20 + 0.6KB * 2000 + 2.3KB * 1000
    = 3.5MB

Table 8.5 Disk space formula necessary for base backup

Log of the metering each day * For one year

3.5MB * 365 = 1.3GB

Table 8.6 Disk space formula necessary for Difference backup

disk space per WAL file : 16MB

WAL file space frequency until acquiring base backup (30 days): 24 * 30

16MB * 24 * 30 = 11.3GB

Table 8.7 Disk space formula necessary for operation of online backup

Disk space formula necessary for operation of online backup

= Disk space formula necessary for base backup + Disk space formula necessary for Difference backup

= 1.3GB + 11.3GB

= 12.6GB


Storage destination for backing up resources

This section describes the storage destination for backing up Admin Server resources.

Use the rcxmgrbackup command to specify a storage destination folder, except in the case of metering information.

The folders described in the following table are automatically created in the storage destination folder in order to store the resources. When restoration is to be performed, restoration occurs from the information in the latest folder of each folder. Therefore, even if a folder is deleted due to the disk capacity status, this will not cause a problem because the information in the latest folder will remain.

When the rcxmgrbackup command is used with the -cleanup option specified, all information older than the latest information collected by the command will be deleted.

Table 8.8 Relationship between backup method and data collected

Folder

Offline backup

Online backup
(base backup)

Online backup
(differential backup)

CTMG_OFFyyyymmddhhmmss

Yes

No

No

CTMG_BASEyyyymmddhhmmss

No

Yes

No

CTMGyyyymmddhhmmss

No

No

Yes

CFMGyyyymmddhhmmss

Yes

Yes

Yes

RORyyyymmddhhmmss

Yes

Yes

Yes

RBAyyyymmddhhmmss

Yes

No

No

RORSCW

Yes

Yes

Yes

"yyyymmddhhmmss" is the date and time the command was executed.

Note

Backup files of the admin server should be stored on external storage media to prevent the backup data from being corrupted due to server failure.

Refer to "8.5 Online Backup Settings for Metering" for information on the storage destination for metering.

Standard at backup and restore processing time

Estimate the time that hangs to the backup restoration of the administrative server referring to the following command processing time.

The command processing time must be different according to customer's environment, and gather by the operational testing etc. in customer's environment, and decide the operation estimate time according to the value.

Example

  • Environment

    • CPU : 4CPU

    • Memory Size : 16GB

  • Command processing time

    • offline backup : 3 minutes

    • online backup (base backup) : 2 minutes

    • online backup (differential backup) : 2 minutes

    • restore : 4 minutes

System restart point after restoration

In the system operations flow used by this product, the restart point of the system will vary according to the timing of the backup of resources. Therefore, to ensure that the system can restart from the status it had before backup, operate the system in accordance with whether offline backup or online backup is used for backup, and perform restoration processing in accordance with each backup type.

Figure 8.1 Schedule for Backup and Restoration of Admin Servers (Example)

The flow of the preceding diagram is as follows:

  1. A problem occurs in the system (Example: Occurs at 12:35 on August 1, 2011)

  2. In order to restore the system, restoration is performed on the environment backed up offline and the environment backed up online.

    (Example: Restores at 14:00 on August 1, 2011)

    Refer to "Points to note at backup and restoration" for information on the restoration order.

  3. The latest differential backup files are dated (12:00 on August 1, 2011), so the restart point will be from that date and time.