Backup and Restore

Module specific instructions for each type of Backup Set across GUI and CLI platforms of AhsayOBM will be discussed individually. To navigate to a specific module, choose from the links below:

  • File

  • Cloudfile

  • MariaDB

  • Microsoft M365

  • Microsoft Exchange

  • Microsoft Hyper-V

  • Microsoft SQL

  • MySQL

  • Oracle

  • Vmware

  • Windows System

  • Linux Bare Metal

  • Tibero Database

Backup Process

To better help you understand what goes on during a backup process, here are the steps performed during a backup job:

backupprocess

Periodic Data Integrity Check (PDIC) Process

Specific to Step 3, the PDIC will run on the first backup job that falls on the corresponding day of the week from Monday to Friday.

To minimize the impact of the potential load of large number of PDIC jobs running at the same time on the AhsayCBS server, the schedule of a PDIC job for each backup set is automatically determined by the result of the following formula:


	PDIC schedule = $BackupSetID modulo 5
	or
	$BackupSetID mod 5

The calculated result will map to the corresponding day of the week (i.e., from Monday to Friday).

0 Monday
1 Tuesday
2 Wednesday
3 Thursday
4 Friday

You cannot change the PDIC schedule.

Example:

Backup set ID: 1594627447932

Calculation: 1594627447932 mod 5 = 2

2 Wednesday

In this example:

  • the PDIC will run on the first backup job that falls on Wednesday; or

  • if there are no active backup job(s) running from Monday to Friday, then the PDIC will run on the next available backup job.

Although according to the PDIC formula for determining the schedule, which is %BackupSetID% mod 5, this schedule only applies if the previous PDIC job was actually run more than 7 days prior.

Under certain conditions, the PDIC may not run strictly according to this formula. For example:

  • The PDIC job will run on the first backup job after upgrade to the latest client version from AhsayOBM v6, v7, or pre-8.3.6.0 version.

  • If backup jobs for a backup set are not run on a regular daily backup schedule (for example: on a weekly or monthly schedule), then the PDIC job will run if it detects that the previous PDIC job was run more than 7 days ago.

  • Every time a data integrity check (DIC) is run, the latest PDIC run date is reset, the next PDIC job will run after 7 days.

  • The PDIC job will not run if there are no files in both the data and Retention Areas. For example: a newly created backup set with no backup job history or a backup set where all the data has been deleted using the Delete Backup Data feature.

  • The PDIC job will not run on a backup set that contains any data which is still in v6 format. It will only run if all v6 data format on a backup set has undergone data migration to v9 block format.

pdic

Backup Set Index Handling Process

Specific to step 5 and step 12 (Start Backup Job and Completed Backup Job respectively), to minimize the possibility of index related issues affecting backups, each time index files are downloaded from and uploaded to backup destination(s); the file size, last modified date, and checksum is verified to ensure index file integrity.

Start Backup Job

sbj

Completed Backup Job

cbj

Data Validation Check Process

Specific to step 10, as an additional measure to ensure that all files transferred to the backup destination(s) arereceived and saved correctly, both the number of 32 or 64 MB data block files and the size of each block file are checked again after the files are transferred.

dvcp