There are several limitations and known issues in the migration process using the Migration Portal
List of Issues
Microsoft Exchange Server and Microsoft SQL Server Clients
Microsoft Exchange Server and Microsoft SQL Server backup tasks require some manual effort to reprovide credentials before the migrated tasks will work. As a workaround, these tasks can be recreated manually. Another important thing to note is that Acronis Backup Cloud supports only Native SQL authentication, while BackupAgent supported both AD and Native authentication methods.
- For Exchange, see BackupAgent: Upgrading Microsoft Exchange Server Clients to Acronis Backup Cloud.
- Currently, an issue in automated SQL agent installation is under investigation. When it is fixed, the steps will be similar to those for Exchange (see above).
Windows XP and Windows Server 2003 Clients
Migration Portal transfers end user's data in 2 steps – account information and groups structure is transferred by server; backup plans are transferred by client. There is no BA client with transfer logic for Windows XP and Windows Server 2003 (due to .NET limitations). Therefore, non-attended part of migration process ends at account and groups transfer. After that the migration needs to be finalised manually by creating backup plans in Acronis Backup Cloud console, deploying Acronis Backup Cloud client software and performing backups.
In BackupAgent, encryption is mandatory and is set up during end user clients installtion. All backup plans use the encryption passphrase to encrypt / decrypt the backup data. Acronis Backup Cloud enables data encryption on backup plan level, meaning end user needs to specify the passphrase when creating the plan, however the setting is optional.
Solution: During migration of OS / environments, for which updated BA client software is available, transfer of backup plans is performed automatically, including the passphrase – as a result, end user's data is backed up by Acronis Backup Cloud and is encrypted with the passphrase end user initially set during account setup in BA. For new backup plans, however, encryption remains optional and the passphrase has to be set up explicitly in every new backup plan.
Acronis Backup Cloud Agent already installed
In case an Acronis agent is already installed, the upgrade will be interrupted and the machine will be listed in MigrationFailed mode.
Solution: The partner should either uninstall the Acronis agent or mark the computer as Excluded, then retry the upgrade.
Email Notification at the end of migration
At the end of the migration process, BackupAgent Client sends an email notification to the console users.
Example notification (clickable):
There are two issues with it:
- It contains a link to the non-customized console (https://baas.acronis.com). This may be a problem for partners that prefer branded console link.
- These notifications are in English only.
There is a special build of BackupAgent for Windows being prepared which will send no email notifications. However, Linux/Mac clients cannot be changed anymore.
Solution: Set expectations with the Partners on the above before the migration, so they warn their Customers that they may receive the above notification.
Backup Tasks with Inclusion Filters
Backups with certain inclusion filters cannot be migrated.
Solution: such tasks need to be recreated manually.
- BackupAgent: Migration to Acronis Backup Cloud
- BackupAgent: Using Migration Portal to Upgrade to Acronis Backup Cloud