56862: BackupAgent: Migration from BackupAgent APS Package to Acronis Backup Cloud APS Package

Translate to:

This article describes how to migrate from BackupAgent APS 1.2 package to Acronis Backup Cloud APS Package.

APS migration procedure should be used in conjunction with Acronis Backup Cloud migration procedure described in this article.

APS Migration Overview

APS migration procedure carries out the following tasks:

  • Switch BackupAgent OSA Customers subscriptions to Acronis Backup Cloud service
  • Synchronize accounts hierarchy in Acronis Backup Cloud with OSA
  • Map BackupAgent subscriptions and service users to Acronis Backup Cloud End User Customer groups and users
  • Synchronize resources usage and limits (included and additional) in OSA with Acronis Backup Cloud usage and quotas

Migration is designed in the way that minimizes impact towards Customers and end users. The following entities stay the same during the migration:

  • Customers
  • Subscriptions (existing BackupAgent subscriptions are re-used, no new subscriptions are created)
  • Service users (Acronis Backup Cloud is assigned to the existing BackupAgent service users)
  • Passwords (end users should use their existing OSA MyCP/BackupAgent passwords in order to access Acronis Backup Cloud Backup Console)

During the migration Acronis Backup Cloud APS limits and usage in OSA are synchronized with BackupAgent and Acronis Backup Cloud quotas and usage in the following way:

  1. Storage limit for Acronis Backup Cloud storage resource in the Customer’s subscription is set equal to the BackupAgent storage resource quota. In case Customer has purchased additional BackupAgent storage, an upgrade order for the additional amount is placed for corresponding Acronis resource. Resulting limit is propagated to Acronis Backup Cloud storage quota.
  2. Limits for servers, workstations and virtual machines in the Customer’s subscription are set equal to the actual usage in Acronis Backup Cloud at the moment when migration script is executed. BackupAgent subscription resource limits are not taken into account as they cannot be mapped to Acronis resources. In case actual usage exceeds the one included into service plan resources limits, an upgrade order for the additional amount is placed for corresponding Acronis resource. Resulting limit is propagated to Acronis Backup Cloud. So, it is important to have all Customers machines successfully migrated and registered in Acronis Backup Cloud prior to running the APS migration script.
In case you’d like to offer Acronis Backup Cloud service to new Customers during the migration, please use another service plan for this purpose. Service plan being migrated should not be available for purchasing, both in Online Store and in CCP.
Please note that both services (BackupAgent and Acronis Backup Cloud) should be available to Customers and users during the longest backup retention period. During the retention period Customers are supposed to use BackupAgent for getting access to their existing historical data, while Acronis Backup Cloud should be used for creating new backups.

Migration pre-condition

Odin Service Automation is upgraded to version 6.0.7 or higher.

BackupAgent APS package is upgraded to the latest version available (1.2-16), up and running.

Acronis Backup Cloud APS package is installed, configured, upgraded to the latest version available (2.0-1244 or higher), up and running.

Please note that resellers and accounts hierarchy will be created in Acronis Backup Cloud under the account which is configured in Acronis Backup Cloud APS instance. It will not be possible to move the hierarchy later, make sure to set the proper production account.

Migration steps overview

Preparation steps

  • Upgrade Acronis Backup Cloud APS Package to the latest version available (2.0-1244 or higher). Check Acronis Backup Cloud APS version and its status in OSA PCP to make sure the upgrade was successful.
  • Install Mcrypt module on Acronis Backup Cloud endpoint
  • Disable “Auto-provisioning” property for Acronis Backup Cloud tenant resource, hide Acronis CCP Home section, permit subscriptions quotas exceeding
  • Select BackupAgent service template which should be migrated. Rename Backup Storage resource to the default value "BA Counter". Add Acronis Backup Cloud APS resources to existing BackupAgent service template so that it contain both BackupAgent and Acronis Backup Cloud resources, configure Acronis Backup Cloud resource rates and synchronize the subscriptions.
  • Configure migration script on Acronis Backup Cloud endpoint.

Migration

  • Migrate one or few BackupAgent Customer groups using Migration Portal.
  • Run APS migration script on the Acronis Backup Cloud endpoint for the Customer groups migrated on the previous step.
  • Check that Customers were migrated successfully.

Post-migration actions

  • Once migration is completed for all Customers using the service template chosen on the first step, please switch the pricing to Acronis Backup Cloud service and enable additional resources purchasing option for Acronis resource rates.
  • Return “auto-provision” property to the “Enabled” state, enable Acronis CCP Home section and switch pricing to Acronis Backup Cloud service (by setting resource rates prices and/or configuring external billing system). Make corresponding changes to the external billing systems, if necessary.
  • Once backup retention periods for all Customers using the service template chosen in the first step are over, remove BackupAgent resources from the service template.
Please note that BackupAgent client software should be removed by end users manually.

Please find detailed instructions below.

Preparation Steps

Install and upgrade Acronis Backup Cloud APS Package

Follow the instructions in documentation provided with Acronis Backup Cloud package 2.0 version. You can download the latest version available on apsstandard.org site https://dev.apsstandard.org/apps/2.0/Acronis/Acronis%20Backup%20Cloud/Acronis/. Upgrade and deployment instructions are available in OSA APS 2.0 Deployment Guide.

Install Mcrypt module on Acronis Backup Cloud endpoint

Login to Acronis Backup Cloud endpoint host via SSH under root user and execute the following commands:

wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarc...

rpm -ivh epel-release-6-8.noarch.rpm 

yum install php-mcrypt 

service httpd restart

Check that Mcrypt module has been successfully installed:

php -m | grep -i mcrypt

Expected output:

mcrypt

Disable tenant resource auto-provision property, hide Home section and permit subscription quotas exceeding

  1. Log in to OSA Provider Control Panel.
  2. Navigate to Backup Tenant (Acronis) resource -> Activation Parameters tab.
  3. Press the Edit button and disable Automatically provision service property. Please notice that this will affect all new subscriptions provisioning as well, so Acronis service plans should not be available for purchasing during migration process below. Another option is to create a new resource for Backup Tenant (Acronis) resource class, but in this case it will not be possible to switch Customers to the generic Acronis service plan after migration is completed.
  4. Navigate to OA -> Settings -> Customer CP Navigation, find APS Home Section: Acronis Backup Cloud element and disable it. This step hides Acronis APS home screen section until migration is complete:
  5. Navigate to OSA Provider Control Panel, Backup Profiles tab in Acronis Backup Cloud APS instance, select backup profile and allow setting user quotas exceeding subscription limits ("Do not allow to set user quotas exceeding subscription limits" option should be set to "No")

Configuring BackupAgent service template

  1. Log in to OSA Provider Control Panel. Select Products -> Service Templates. Select BackupAgent service template. Deactivate it by pressing Deactivate button:
  2. Make sure that BackupAgent atomic storage resource name has the default value “BA Counter”, in particular, when it is included into a composite resource (though, composite resource may have any name). Rename the atomic resource otherwise (this is required as the migration script performs the search via the resource name):
  3. Add resource related to Acronis package. Please note that composite Acronis resources are not supported by the migration script:
  4. Activate service template:
  5. Navigate to Business Automation (Billing) Provider Control Panel -> Service Plans. Select BackupAgent service plan and go to the Resource Rates tab.
  6. Add and configure resource rates for all Acronis package resources, following general Acronis Backup Cloud integration guide and the rules below:
    • Composite resources for Acronis Backup Cloud are not supported by the migration procedure (as their usage and limits can’t be calculated and set properly). In case you would like to use composite resources for Acronis Backup Cloud service plan, you can make these changes after completing migration.
    • Included amount of storage should be equal for both BackupAgent and for Acronis Backup Cloud service plans. In case BackupAgent service plan includes composite resources, the amount of included into service plan composite resources should be multiplied by the amount of atomic resources in the composite one.
    • Set all prices for Acronis Backup Cloud resource rates to zero, otherwise Customers will be charged for both resource sets at once (Acronis and BackupAgent). Switch pricing to Acronis Backup Cloud after the migration is completed.
    • Acronis resources should not be available for purchase neither in CCP nor in Online Store until the migration is finished.


  7. Go to the General tab and press Update Subscriptions:
  8. Select subscriptions that should be synchronized at once, enable Install new resources and Update limits options. Please note that in order to execute migration script for BackupAgent group, Customer’s subscription corresponding to this group should be synchronized. It is recommended to synchronize all subscriptions related to the service plan (at once or step-by-step, to stripe the load) before proceeding to the next step.
  9. In case this service plan is delegated to reseller(s),  please navigate to Reseller’s service plan, press Synchronize resellers, make sure that Create new Resources, Update Resource Prices and Update Resource Limits options are enabled and press Synchronize button.
  10. Navigate to subscriptions corresponding to the service plan modified. Make sure both Acronis and BackupAgent resources appear in the subscriptions.

Configuring migration script

  1. Login to Acronis Backup Cloud endpoint host via root user using SSH protocol.
  2. Open /var/www/html/backupservice/app/Config.php file in a text editor.
  3. Edit the following sections and save the config file:

//BackupAgent Migration 
define('POA_API_URI', '<POA API URI>'); 
define('BACKUPAGENT_SERVER_DNS', '<BackupAgent Server Name>'); 
define('BACKUPAGENT_SERVER_ADMIN_LOGIN', '<BackupAgent Admin Login>'); 
define('BACKUPAGENT_SERVER_ADMIN_PASSWORD', '<BackupAgent Admin Password>'); 
define('BACKUPAGENT_SERVER_PROTOCOL', '<BackupAgent Server communications protocol, either http or https>');
// Script endpoint.sh adds the constant OPEN_API_URI during the package installation
define('OPEN_API_URI', '<OPEN API URI>');

For example:
//BackupAgent Migration 
define('POA_API_URI', 'a.backupagent.apsdemo.org'); 
define('BACKUPAGENT_SERVER_DNS', 'w2012r2-psn1.cloudapp.net'); 
define('BACKUPAGENT_SERVER_ADMIN_LOGIN', 'Administrator'); 
define('BACKUPAGENT_SERVER_ADMIN_PASSWORD', 'SECRET_PASS!@#123'); 
define('BACKUPAGENT_SERVER_PROTOCOL', 'http');
// Script endpoint.sh adds the constant OPEN_API_URI during the package installation
define('OPEN_API_URI', 'a.backupagent.apsdemo.org');

     4. Configure API connection to Business Automation

Enable outgoing network connection from Acronis Backup Cloud endpoint host to BA Front End host (PBALINFE), default port 5224

Depending on your Business Automation API authentication configuration, please modify /var/www/html/backupservice/config/ba-api.ini config file in the following way:

In case BA FE requires authentication:

port= <BA FE API port, by default 5224>

path=RPC2

auth=1

username=<username>

password=<password>

secure= <1 for https, 0 for http>

host=<BA FE host IP>

In case BA FE doesn't require authentication:

port= <BA FE API port, by default 5224>

path=RPC2

auth=0

secure= <1 for https, 0 for http>

host=<BA FE host IP>

 

Migration

Migrate Customers using Migration Portal

Please migrate one or few Customer groups using Migration Portal. Details on how to use the Migration Portal can be found in this article.

Proceed to the next step only after fully completing migration of these Customer groups (all users and machines have been migrated successfully). It is important for the proper resource limit and usage calculation on the next step.

It is highly recommended to use a separate Acronis Backup Cloud group (different from the account configured in Acronis Backup Cloud instance) for migration purposes, as it makes migration process more manageable.

Run migration script

  1. Navigate to OSA Provider Control Panel -> Applications page and note BackupAgent APS Application ID (123 in the example below):
  2. Log in to Acronis BackupCloud endpoint host as root user. Navigate to /var/www/html/backupservice/ folder. This step is important as otherwise the script fails to find all the necessary files.
  3. Run Migration.php script under root user for one or few BackupAgent Customer groups:
     
    sudo -H -u apache bash -c 'php Migration.php -i <APPLICATION_ID> -g <Group Name 1> -g <Group Name 2> -g <Group Name N> -r <Composite Resource ID> >> /tmp/migration.log &'

    -i <APPLICATION_ID> is Backup Agent APS Application ID (checked on the Step 1 of this section)
    -c, optional, successful status of upgrade (change) order, required in case of custom order flow only
    -t, optional, unsuccessful status of upgrade (change) order, required in case of custom order flow only
    -r, optional, ID of composite resource including BackupAgent storage resource (BA Counter) (if not specified, script will check each of the resources included into service plan what will generate additional API load and reduce script execution speed)
    -g, Customer group name in Backup Agent server. Can be looked up in the Migration Portal, Migration Report or in OSA CCP: BackupAgent->BackupAgent Group->Settings Tab

     
    For example,
    sudo -H -u apache bash -c 'php Migration.php -i 123 -r 100001 -g 12345migr1000007  >> /tmp/migration.log &'
    This command will run migration script in background and send output to /tmp/migration.log file
     
    The status of the command execution can be checked by the following command:
    jobs
    Please note that in case Acronis Backup Cloud current resource usage (storage or licenses) exceeds corresponding resource rate limits, Upgrade Orders for the amount of overused resources will be placed in Business Automation. Assuming that Acronis resource rates were set to zero as was requested in Preparation Steps section, these will be orders with zero value. Order will use default payment method. Orders are placed one-by-one (script will place next Upgrade Order only after the previous one has been completed successfully). In case any additional actions are required for their processing, these actions should be performed manually from BA Provider or Reseller Control Panel during the script execution (script monitors order status and waits for order completion before proceeding).

Check the migration results

In case the migration has been completed successfully, you should be able to observe the following:

  • Acronis Backup Cloud management console: Customer groups created during the first migration step via Migration Portal are migrated to the account used by Acronis Backup Cloud APS instance with the entire resellers hierarchy (in the same way Acronis APS performs regular provisioning). Storage and licenses quotas are set properly.
  • OSA Provider Control Panel: Acronis Backup Cloud APS resource limit and usage is in sync with Acronis Backup Cloud, upgrade orders were placed and completed when necessary.
  • Customer Control Panel, MyCP: Backup tab appeared, single sign-on to Acronis Backup Cloud management console is working normally, resource usage and limits are set properly.

Post-migration Actions

Return auto-provision property of tenant resource to initial state and switch the pricing to Acronis

When migration is completed and you would like to make service plan available for new purchases, return Acronis tenant resource “Auto-provision” property to the initial (“Enabled”) state. This is necessary to continue using Acronis package in normal mode (provisioning new subscriptions and tenants).

If you would like your Customers to see Acronis APS section on CCP Home screen, navigate to OA -> Settings -> Customer CP Navigation, find APS Home Section: Acronis Backup Cloud element and enable it.

In order to make purchasing of additional resources available to the existing and new Customers, set the proper pricing for Acronis Backup Cloud resource rates and set BackupAgent resources prices to zero (to avoid double charging), and make Acronis resources available for purchasing in CCP and (or) Online Store.

Post-migration actions: remove BackupAgent resources

BackupAgent resources should be kept in the service template not only during the migration process, but also during the longest Customer’s Backup Retention period. Customers should use BackupAgent for getting access to their historical data, while new backups should be created by Acronis Backup Cloud.

Once the migration is finished for all Customers using service template and the longest Customer’s Backup Retention period is over (retention periods can be checked in the Migration Report), BackupAgent resources can be removed from the service template.

Please note that BackupAgent client software will not be uninstalled when the resources are removed, Customers need to remove it manually.

Known Issues and Limitations

  1. In case Provider would like to offer Acronis Backup Cloud service to new Customers during the migration, a separate service plan(s) should be used for that. Customers can be switched to a single service plan after the migration is over.
  2. Composite resources are not supported for Acronis Backup Cloud APS, as it makes resources usage and limits calculation not possible.
  3. Acronis Backup Cloud CCP Home section is hidden on APS application level, so this change will affect all Customers, including those subscribed to another Acronis service plans

Tags: 

You are reporting a typo in the following text:
Simply click the "Send typo report" button to complete the report. You can also include a comment.
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
8 + 6 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.