Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.2.1 |  CUBRID 8.3.1 |  CUBRID 8.4.0 |  CUBRID 8.4.1 |  CUBRID 8.4.3 |  CUBRID 9.0.0 | 

Managing Backup Files

One or more backup files can be created in sequence based on the size of the database to be backed up. A unit number is given sequentially (000, 001-0xx) to the extension of each backup file based in the order of creation.

Managing Disk Capacity during the Backup

During the backup process, if there is not enough space on the disk to save the backup files, a message saying that the backup cannot continue appears on the screen. This message contains the name and path of the database to be backed up, the backup file name, the unit number of backup files and the backup level. To continue the backup process, the administrator can choose one of the following options:

  • Option 0 : An administrator enters 0 to discontinue the backup.
  • Option 1 : An administrator inserts a new disk into the current device and enters 1 to continue the backup.
  • Option 2 : An administrator changes the device or the path to the directory where backup files are saved and enters 2 to continue the backup.

******************************************************************

Backup destination is full, a new destination is required to continue:

Database Name: /local1/testing/demodb

     Volume Name: /dev/rst1

        Unit Num: 1

    Backup Level: 0 (FULL LEVEL)

Enter one of the following options:

Type

   -  0 to quit.

   -  1 to continue after the volume is mounted/loaded. (retry)

   -  2 to continue after changing the volume's directory or device.

******************************************************************