60088: Migration of existing Acronis Backup Cloud entities into Odin Automation

Translate to:

Applies to:

APS Migration Overview

APS migration procedure carries out the following tasks:

  • Map the existing Acronis Backup Cloud entities (groups and users) with Odin Automation entities (subscriptions and service users).
  • Synchronize accounts hierarchy in Acronis Backup Cloud with OSA.
  • Synchronize resources usage and limits (included and additional) in OSA with Acronis Backup Cloud usage and quotas.

Migration script uses a CSV file containing required OSA and Acronis Backup Cloud mapping as an input.

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

  1. Resources limits are propagated from OSA to Acronis Backup Cloud.
  2. In case a Customer should have additionally purchased resources, they can be specified in the input CSV file with the desired quantity; migration script will place corresponding Upgrade Order.
  3. Actual resource usage is taken from Acronis Backup Cloud and updated in OSA accordingly.

Migration precondition

Odin Service Automation is upgraded to version 6.0 or higher. All available OSA hotfixes should be installed.

Acronis Backup Cloud APS package with version 2.0-1925 or higher is installed, configured, and up and running.

Outgoing network connection from Acronis Backup Cloud endpoint host to BA Front End host (PBALINFE), default port 5224, should be enabled.

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 you set the proper production account.

Migration steps overview

Preparation steps

  • Enable outgoing network connection from Acronis Backup Cloud endpoint host to BA Front End host (PBALINFE), default port 5224.
  • Upgrade Acronis Backup Cloud APS Package to the latest version available (2.0-1925 or higher). Check Acronis Backup Cloud APS version and its status in OSA PCP to make sure the upgrade was successful.
  • Disable the “Auto-provisioning” property for Acronis Backup Cloud tenant resource, hide Acronis CCP Home section, permit subscriptions quotas exceeding in Acronis Backup Profile.

Migration

  • Prepare CSV file that will be used for migration based on the information from the Migration Report.
  • Run APS migration script on the Acronis Backup Cloud endpoint server, using CSV file created on the previous step.
  • Check that Customers have been migrated successfully.

Post-migration actions

  • Return the “Auto-provision” property of Acronis Backup Cloud tenant resource to the “Enabled” state.

Preparation Steps

Enable network connection from Acronis Backup Cloud APS endpoint to Business Automation

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

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.

Disable tenant resource auto-provision property

  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 after disabling this property the resource cannot be used for normal provisioning, so if you are offering Acronis service to new Customers please create a new resource for migration purposes.
  4. In Acronis Backup Cloud APS instance, navigate to OSA Provider Control Panel -> Backup Profiles tab, 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 migration script

  1. Log in to Acronis Backup Cloud endpoint host with root user using SSH protocol.
  2. Configure XML RPC API connection to Business Automation. Outgoing network connection from Acronis Backup Cloud endpoint host to BA Front End host (PBALINFE) should be enabled for this step. Depending on your Business Automation API authentication configuration, modify /var/www/html/backupservice/config/ba-api.ini config file in the following way:
     
    In case Business Automation does not require authentication (this is the default behaviour):
    port= <BA FE API port, by default 5224>
    path=RPC2
    auth=0
    secure= <1 for https, 0 for http>
    host=<BA FE host IP>
     
    In case Business Automation API 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>

Migration

Prepare CSV file

Migration script imports information about OSA and Acronis Backup Cloud entities that should be mapped from the CSV file.

It has the following format:

APS Instance ID: ID of Acronis Backup Cloud APS application instance, can be found in OSA Provider Control Panel; for example "11".

OSA Subscription ID: ID of existing OSA subscription which Acronis Backup Cloud group will be mapped to, can be found in OSA Provider Control Panel; for example "1000008". Leave it empty if you want to create a new subscription.

OSA Account ID: ID of OSA account which Acronis Backup Cloud service will be mapped to, can be found in OSA Provider Control Panel; for example "1000003".

Datacenter ID: ID of the data center configured in Acronis Backup Cloud APS instance, for example "1". Data center is basically a set of credentials used for accessing Acronis Backup Cloud. Please note that the account specified in the data center should be a parent for the group containing migrated BackupAgent Customers.

ABC Group ID: ID of Acronis Backup Customer group which should be mapped to OSA subscription specified earlier, for example "260539".

Users: array containing OSA and Acronis Backup Cloud users mapping:

     abc_login: user login in Acronis Backup Cloud, for example "acronis_test_user".

     osa_service_user_id: service user ID in OSA, for example "14". Service user should belong to the Customer specified earlier, but may be created from a different subscription.

     user_storage_quota: desired user storage quota that should be set in OSA and in Acronis Backup Cloud in Bytes, for example "10737418240" for 10 GB.

     privileged: boolean property enabling on disabling Administrator privilege for OSA service user, for example "true" or "false". Administrator privilege allows user to log in to Account Management console in Acronis Backup Cloud.

     activate: boolean property defining if it is required to activate Acronis Backup Cloud user with OSA service user password, for example "true" or "false". It is recommended to always use "true", as even if a user has been already activated, the script will synchronize its password with OSA, which is required for SSO.

An example of Users array:

[{"abc_login": "acronis_test_user", "osa_service_user_id": 14, "user_storage_quota": 10737418240, "privileged":true, "activate":true}]

Additional resources: array containing resources that should be purchased additionally for the subscription specified above. An Upgrade Order will be placed for these resources.

     resource_id: ID of the resource that should be included into Upgrade Order, for example "1000108". This may be either an atomic or a composite resource.

     additional_amount: amount of resources that should be purchased additionally, for example "4".

An example of Additional_resources_array:

[{"resource_id": 1000108, "additional_amount": 4}]

Plan ID: Set the Service Plan ID if you want to create a new subscription for the Acronis Backup Cloud group. Leave it empty if you set OSA Subscription ID.

Plan Period ID: Set the Plan Period ID if you want to create a new subscription for the Acronis Backup Cloud group. Leave it empty if you set OSA Subscription ID. Add to CSV file all OSA accounts and subscriptions that should be mapped with Acronis Backup Cloud.

An example of the CSV file is attached: migration_v6-1.zip

After preparing the CSV file, copy it to Acronis APS endpoint server (for example, to /tmp folder) and make sure that apache user has access to it (is able to read it). You may use the WinSCP application for copying the file via SCP protocol.

Run migration script

1. 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.

2. Run Migration.php script under root user for one or few Acronis Backup Cloud groups:
  
sudo -H -u apache bash -c 'php Migration.php -f file.csv >> /tmp/migration.log 2>&1 &'

-f <CSV file name>  is the full name of CSV file including OSA and Acronis Backup Cloud mapping.

For example,
sudo -H -u apache bash -c 'php Migration.php -f Migration_6-1.csv >> /tmp/migration.log 2>&1 &'

This command runs the migration script in background and sends output to the /tmp/migration.log file.

The status of the command execution can be checked by the following command:

jobs

Please note that for each resource specified in Additional_resources array in CSV file, Upgrade Orders for the amount of additional resources will be placed in Business Automation via BA XML RPC API. Assuming that Acronis resource rates were set to zero as requested in the 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

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

  • Acronis Backup Cloud management console: Storage and licenses quotas are set properly for the group.
  • 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 Backup 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).

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.
1 + 0 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.