Ad-hoc archiving operations are on-demand archive operations that allow subclient content to be specified as an external input when starting an archive operation. When you start an ad-hoc archive operation from the command line, you can specify the content in a directive file.
Data Scan
Ad-hoc job always runs a full scan operation. It will archive all the files in the directive file.
First Ad-Hoc Job
If the ad-hoc archive job is the first job on the subclient, then the job will run as a full backup. The subsequent ad-hoc archive jobs run as incremental jobs. Synthetic full backup jobs carry forward the ad-hoc backup data only if the data is not part of the subclient used to perform ad-hoc jobs.
Failed Items
- Failed items from regular jobs are picked by the next regular archive job and such items will not be handled by an ad-hoc job. Failed items from ad-hoc jobs are not picked up by either ad-hoc or regular job.
Unsupported Components
-
IntelliSnap backups.
-
The Delay stubbing until archived data is protected in another copy option is not honored.
Considerations
-
Supported on client computers that use indexing.
-
The latest browse operation shows items only for the current cycle. Once you run a full backup job on the subclient, the previous ad-hoc items will not be visible in the latest browse operation. Only point-in-time or time range browse operations show the ad-hoc items.
-
If the data in the ad-hoc job overlaps with that of the regular subclient, then the deleted items retention will apply for the ad-hoc data also.
-
The read-only stubs will be archived only if the Archive Read-Only Files option is selected in the Subclient Properties - Disk Cleanup tab.