5.2. Migrating Backups from Acronis Storage Gateway 1.6 and 1.7 (NFS)¶
Disable the firewall or explicitly open TCP port 44446 on the source Acronis Storage Gateway.
To disable the firewall, run
# systemctl stop firewalld
To open TCP port 44446 in the firewall, do the following:
Find out the zone where port 44445 is open:
# firewall-cmd --list-all-zones | grep active mix_eth0 (active)
Add the required port to the same zone:
# firewall-cmd --zone=mix_eth0 --permanent --add-port=44446/tcp # firewall-cmd --reload
In the WebCP of the ABGW node, proceed to STORAGE SERVICES > Backup > NODES, select the only node in the cluster, and click Migrate.
Select the source storage version and click NEXT.
Specify the connection details for the source storage and click NEXT.
Provide the credentials for the cloud management portal of the Acronis Backup Cloud installation that the source storage is registered in and click NEXT.
If the source storage is registered in Acronis Backup Cloud under an IP address, you will see the DNS configuration screen. On it, click RE-REGISTER WITH DNS and specify the source storage DNS name (recommended, see above). Or, if you want to keep using the IP address, click PROCEED WITH IP.
Important
- If you specified a DNS name, configure your DNS server according to the suggested example.
- Each time you change nodes in the Acronis Backup Gateway, adjust the DNS settings accordingly.
Select public cloud as a destination storage type to create a gateway to:
Make sure the network interface that is connected to a network with the ABGW private traffic type is selected in the drop-down list. The corresponding interface that is connected to a network with the ABGW public traffic type will be selected automatically. Click NEXT.
Note
If necessary, click the cogwheel icon and assign Acronis Backup Gateway roles on the Network Configuration screen.
Configure the destination storage backend: select Amazon S3 as public cloud provider, specify credentials and bucket name.
Important
You must update Acronis Backup Agents to version 4492 (Windows/Mac) or 4470 (Linux). Otherwise agents’ attempts to place backups in the new storage backend will result in “Backup failed” errors.
Click NEXT.
Review the source and destination storages and click START MIGRATION.
Depending on data size, migration may take as long as several days.