Understand: BaaS Migration - Considerations & Limitations

Preface:

This Article contains important information relevant to the migration process to our new Cloud Connect Platform. In addition to this article please also read our Migration FAQ.

If you have any questions about these statements or an question not included here, please do not hesitate to contact us at support@anycloud.dk.

Considerations & Limitations:

When deciding to migrate your Cloud repositories to our newly offered platform, please be mindful of the following:

Currently the new Platform is a BaaS-Only offering. If you already have the Disaster recovery service activated, this cannot be implemented on the new platform. As such, we ask that you for now stay on the current platform.

As the newly offered Platform, is a entirely new Back-end, integration into our Web Portal (https://vac.revirt.global), unfortunately means that we will have to create new Companies in the Web Portal. This means that each end-customer will have to manage two companies while the end-customer is not fully migrated to the new platform.

As standard, the data location will be Germany.

The platform has a new separate Storage Back-end, which means improved performance. Agents & jobs, as standard, have the opportunity to send data directly to the storage back-end, without going through a gateway server. This may mean that permission is needed for this traffic.

Due to the new Cloud repository, the tenant must run one of the following Veeam products:

Veeam Backup & Replication 12 (or later)
Veeam Agent for Microsoft Windows 6.0 (or later)
Veeam Agent for Linux 6.0 (or later)
Veeam Agent for Mac 2.0 (or later)

The new platform does not (per default) support transaction log backup copy jobs (e.g. SQL Logs). If you currently use Copy Jobs with transaction logs, please reach out to us, for a different repository for this functionality.

The Insider Protection functionality (ITP) is not available. This is a vendor Software limitation.

Instead of ITP, we offer Immutability on customer Cloud Repositories. Immutable data becomes read-only in the Immutability period and protects against file deletion from both customer & Anycloud.The immutability period is the number of days that Customer Data is in read-only mode.

Regarding Immutability please note:

This feature can only be turned on, at the creation step of a cloud repository. If you wish to add this at a later stage, this will require that you get an additional repository. This is a Veeam Software limitation.

In the scenario where the customer chooses immutability on Cloud Backup repositories, the Customers VBR does not delete backups within a job session or by the background retention job until both the retention period and immutability period end for these backups. The tenant should be aware that their backups may remain in the cloud repository for a longer period than specified in the job settings, if not setup with this in mind.

As with all retention settings:

Changes made will only effect new backups as the retention mechanism in the Veeam software get set on each file when the file is created. As well, the deletion process of files exceeding the retention date runs at the end of each Job.

Please review the Veeam documentation to get a in-deep understanding of how retention works: Retention Policy for Backup Copy Jobs.

(Reseller Specific) Per default, we will create a end-customer specific repository. As such a reseller will not be able to resize the end-customer repository by using any Reseller-allocated repository in the Web Portal. Instead you will need to contact our support staff.

The reasoning for this approach is to enhance the security & privacy of each customer by making them entirely separate entities & security domains.