• Backup Destination
  To provide maximum data protection and flexible restore options for agent-based backup, it is recommended to configure:
  • At least one offsite or cloud destination
  • At least one local destination for fast recovery
• Temporary Directory Folder Location
  Temporary directory folder is used by the AhsayOBM for storing backup set index files and any incremental or differential backup files generated during a backup job. To ensure optimal backup/restoration performance, it is recommended that the temporary directory folder is set to a local drive.
• Performance Recommendations
  • Schedule backup jobs when system activity is low to achieve the best possible performance.
  • Perform test restores periodically to ensure your backup is set up and backed up properly. Performing recovery test can also help identify potential issues or gaps in your recovery plan. It is important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless, but to discover faults in your recovery plan. There might be flaws identified in the plan throughout the test and it is important to identify those flaws.
• Bucket Management for Enterprise Cloud Storage Providers
  If you have chosen to back up files from an enterprise cloud storage (e.g. Amazon S3, Wasabi, Microsoft Azure, Google Cloud Storage, etc.), you will have to select a bucket name during the creation of cloud file backup set. Each bucket has a single compartment and an access key is associated with a single bucket. Therefore, each backup set can back up one bucket.
  For account with multiple buckets, the backup should be organized into one bucket per backup set. For best practice, make sure to assign one bucket name per backup set so you can ensure that you are selecting the correct file(s) to back up.

1. It is currently not possible to select the entire contents of the Cloud drive. Existing top level folders and/or files must be selected individually. If you need to back up the contents of the entire Cloud drive, then all top level folders and/or files must be selected.

2. If there are any top level folders and/or files added to the Cloud drive after the backup set is created, they will not be added in the backup source automatically. The backup set will have to be manually updated to include the new top level folders and/or files before they can be backed up.

Example:

If the “Latest version” and “New updates” folders were created after the creation of the backup set, and the contents of these folders must be backed up, then you must manually select these folders to be included in the backup.

3. If there are any top level folders and/or files which have been deleted from the Cloud drive since the last backup job, they will not be removed from the backup source automatically. The backup set will have to be manually updated to unselect the deleted top level folders and/or files. Otherwise, the backup job will be completed with warnings.

Example:

The following files were backed up but subsequently deleted from the top level backup source of the Cloud drive: was_admin.png, vm_workstation_01.png, vSAN-hosts.png. The next backup job will encounter the following warnings until these deleted files are unselected from the backup source.

The deleted files are highlighted in red on the backup source to indicate that they no longer exist on the Cloud storage account

Backup log