Home > Best Practices

    Export to PDF

    Best Practices

    Choose the BYOS subscription if the Azure assets to protect are based in a region different from the Cloud Backup instance

    If your Azure assets (Azure VMs or storage) are not hosted in the same or the paired data center as the Cloud Backup for IaaS + PaaS product instance that you will access, we strongly recommend that you choose the BYOS subscription with your Microsoft Azure Blob Storage. See the information in this for bandwidth pricing that may incur due to the data transferred out of Azure data centers.

    For example, you may register your AOS tenant in North Europe (Ireland) data center and want to use Cloud Backup for IaaS + PaaS to protect the Azure VMs in South Africa. In this case, purchasing the BYOS subscription and using your own Azure storage will be the most cost-effective way and will achieve the best performance. You can contact AvePoint support for more information.

    Azure VM Backup Settings

    Index generation for file-level data exportation

    When configuring backup scopes for Azure virtual machines, you can select the Generate index for file-level data export option if you want to perform file-level data export using the backup data. Note the following:

    - Enabling this option will extend the duration of the backup job due to index generation. - If file-level data export is not required, it is recommended to leave this option deselected to improve backup efficiency. - You can also generate index for specific disks or VMs in the **Restore** wizard.

    Retention policy

    When configuring backup scopes for Azure virtual machines, you can choose the number of the latest snapshots to retain or choose for how long the snapshots will be retained after generation. Here are the key points to consider:

    - **Rapid restoration** – Restore jobs involving snapshots can be finished within 15 minutes. If rapid restoration is a priority, it is recommended to retain snapshots. - **Number of snapshots** – You can choose the number of the latest snapshots to retain or choose for how long the snapshots will be retained after generation. - **Cost consideration** – Snapshots are stored in Microsoft Azure and will incur associated costs. The more snapshots you retain, the higher the cost will be. We recommend balancing your retention requirements with cost constraints.

    For details on how to create a new backup scope, refer to Create a New Backup Scope for Azure VM.

    How to choose a backup mode: SaaS infrastructure mode VS CAP Gateway mode

    The SaaS infrastructure mode and CAP Gateway mode are now available for Azure VM, Google VM instance, Amazon EC2, and Azure Storage services.

    The SaaS infrastructure mode delivers centralized management, automation, and comprehensive data protection, enabling secure collaboration and operational efficiency. SaaS Infrastructure Mode is ideal if you want a fully managed, cloud-to-cloud backup solution. In this mode, AvePoint hosts and manages all backup infrastructure, and scaling. You benefit from:

    - **Ease of Management** – No need to maintain servers or network configurations. - **Scalability** – The solution automatically scales as your data grows. - **Security** – Inherits AvePoint’s security certifications and practices, including encryption and compliance. - **Reduced Maintenance** – AvePoint handles updates, monitoring, and troubleshooting. - Choose **SaaS infrastructure mode** if you prefer a hands-off approach, want to minimize IT overhead, and need rapid deployment. - The **CAP Gateway** **mode** is a secure and efficient solution designed to enhance your cloud data protection while improving backup performance. Below are key scenarios where the CAP Gateway mode is required: - Restricted access resources: If your storage data have public access disabled, the SaaS infrastructure will be unavailable to access the data. In such cases, the CAP Gateway mode is necessary. - Google VM instances backup: If you want to back up your Google VM instances data, not just generating snapshots in your VM instances, but storing backup data to your storage location, the CAP Gateway mode is required. - CAP Gateway Mode is suitable if you require more control over your backup infrastructure, such as hosting within your own compute in your virtual network or meeting specific compliance requirements. In this mode: - **Self-Hosted Control** – You manage the installation, configuration, and scaling of backup servers. - **Custom Network Integration** – Ideal for organizations with strict network or data residency requirements. - **Manual Maintenance** – You are responsible for updates, monitoring, and troubleshooting. - **Flexible Deployment** – Can be tailored to unique infrastructure or compliance needs. - Choose CAP Gateway mode if you need to host backups within your own compute in your virtual network, have specific regulatory requirements, or want granular control over infrastructure and data flow.