Incremental backup and restore support for Kubernetes
NetBackup Kubernetes versions 10.4 and later provide backup support for differential, cumulative, and automatic schedules.
Incremental backups reduce the backup window significantly in NetBackup. In this method, NetBackup backs up only the data that has been changed since the subsequent full backup.
Incremental backup supports only the file system type persistent volumes. The block type persistent volumes backups are always full backup irrespective of the schedule types.
Note:
Snapshot copy is always a full backup due to storage class limitation. Apart from snapshot copy, backup from snapshot, duplicate copies have incremental support.
Restore from a complete recovery point performs point in time restore. All the data till that recovery point is restored.
If the Complete field displays No, you cannot restore from that recovery point.
Image chain validation operation is performed for recovery point copies, the validation is reflected in the Complete field of recovery point of each backup copy.
The field is set to Yes when all the related images of the recovery points are present.
Note:
The field is marked as No (Complete = No) if the incremental backups chain is incomplete or if any image is missing from the image group.
Manually imported incremental images can be restored from a valid recovery point (Complete = Yes).
After manual import, if the recovery point is marked as Incomplete, then the image chain might be broken because of the images that were missed for the manual import operation.
To recreate an image chain for manual import operation
- Open the file
/usr/openv/netbackup/logs/bpdbm/root{dateformat}.logand find the lineprevious backup relationship. To restore the relationship, know which images are missed from the manual import operation. - Import the missed out images and run the following command to create a new image chain.
`bpimage -update -id <backupid> -previous_backupid <previous backup id>`
USE_CTIME_FOR_INCREMENTALS option for NetBackup clients:
The USE_CTIME_FOR_INCREMENTALS entry changes how NetBackup determines whether or not a file has changed. This entry causes the client software to use both modification time and inode change time during incremental backups to determine if a file has changed (mtime and ctime).
DO_NOT_RESET_FILE_ACCESS_TIME option for NetBackup clients:
The DO_NOT_RESET_FILE_ACCESS_TIME entry specifies that if a file is backed up, its access time (Atime) displays the time of the backup. By default, NetBackup preserves the access time. NetBackup resets the previous value of the backup.
To set the data mover properties: The user must set or update the flag in the NetBackup primary server-specific ConfigMap that is created under the NetBackupKOps namespace on the Kubernetes cluster.
Example:
apiVersion: v1 data: datamover.properties: | image=reg.domain.com/datamover/image:latest VERBOSE=5 VXMS_VERBOSE=5 USE_CTIME_FOR_INCREMENTALS=YES DO_NOT_RESET_FILE_ACCESS_TIME=YES version: "1" kind: ConfigMap metadata: name: backupserver.sample.domain.com namespace: <NetBackupKOps-Namespace>
Following the schedules are supported in NetBackup Kubernetes workload.
Automatic
Full
Differential Incremental
Cumulative Incremental
A protection plan with different schedules can be configured as follows.
To backup with different schedule types
- In a protection plan, select backup type (Full, Differential Incremental, Cumulative Incremental, Automatic).
- Under configure schedule for snapshot, provide values for recurrence and snapshot retention.
Provide values for Backup from snapshot retention period.
- In the start window tab, set a schedule time and then click Add.
- Under the Schedules and retention section, click Add schedule to add multiple schedules in the same protection plan (Differential Incremental, Cumulative Incremental).
- Select a storage and follow the remaining steps to run a backup job.
In the case of automatic type schedule, based on recurrence of snapshot schedule get resolved after creation of protection plan.
If recurrence is less than one week, then a single differential and full schedule is created.
Follow the recommendation for Retention values in a protection plan for incremental schedules.
To perform a restore from recovery point for any copies (snapshot, backup from snapshot, duplicate), it is recommended to keep the retention duration of the copy for a longer period.
For example, to restore from a backup copy the retention of Backup from Snapshot must be more than a Snapshot copy. Otherwise, the backup copy expires and the recovery point is marked as
COMPLETE = NO.In such cases, the warnings appear in the NetBackup web UI as follows:
It is recommended to set backup retention period more than snapshot retention period.It is recommended to set duplication retention period more than the backup retention period.
Always add a full backup schedule along with cumulative backup schedule. Otherwise, every Cumulative backup is performed as a Full backup.
By default, the Backup from Snapshot option is always enabled for incremental backup types.