To perform ad-hoc backups, you need a content group that has the base content configured to run a full backup on it. The subsequent incremental backups on the content group can be triggered as ad-hoc backups by using REST APIs.
Before You Begin
-
To perform ad-hoc backups from the command line, you need a REST API file (run_ad_hoc_backup_object_storage.xml) which contains the parameter values for configuring the backup options.
-
You must create the following text file to specify where the content is located for ad-hoc backup jobs:
-
A directive file, which is a text file that defines the location of the data that you want to back up. The directive file must be available in the same cloud storage account on which backups will be run because the same authentication used for creating the source object storage will be used in accessing the directive file, reading its contents, and perform the backups.
-
Following is the format for entries in the directive file:
-
The entries in the file must contain UNIX-style path.
For example:
/container1/dir1/file1
/container2/dir2/ -
The entries in the file must be separated by a new line.
Only UNIX-style new line character '\n' is supported.On Windows, the new line character '\r' is supported.
If you are creating the file on Windows by using Notepad++ application, select Unix (LF) for line ending conversion.
-
To differentiate files from folders, add a trailing '/' character for folders.
-
-
Procedure
-
Disable schedule for the content group.
When you disable schedule for the content group, the scheduled incrementals are not triggered. Instead, an ad-hoc based incremental will be triggered via REST API on demand by the end user.