Migrating from Astera 10 to Astera 11

Astera 11 is a major release and is not a direct upgrade of Astera 10. This means that you do not need to uninstall Astera 10 before installing Astera 11, as both versions can coexist on the same system. Astera 11 maintains backward compatibility, so most of the dataflows created in Astera 10 will continue to work in Astera 11 without any changes.

However, deployment archives (*.car files) generated in earlier versions are not directly compatible with version 11. You will need to regenerate and redeploy all existing deployments using the latest version.

As with any major software upgrade, it is recommended to first upgrade your lower-level or non-production environments. This approach allows you to thoroughly test and validate your existing dataflows in Astera 11 and identify any potential issues early in the migration process.

Installation

The Astera 11 (64-bit) installation package includes two executable setup files:

• DataPipelineBuilder.exe and ReportMiner.exe for installing the Astera client

• IntegrationServer.exe for installing the Astera Integration Server

You can download the Astera 11 setup files from the following location: https://www.astera.com/download-center/

Click here to learn how to install Astera 11 client and server.

Licensing

Similar to versions 9 and 10, Astera 11 uses a single licensing key for the server, which also manages the number of client connections and available functionalities. Please note that the licensing key for Astera 11 is different from previous versions. You will not be able to use your Astera 10 license key to activate Astera 11.

To obtain a new license key for Astera 11, please contact: [email protected]

Cluster and Server Management in Server Explorer

The Astera 11 client can be configured to connect with multiple servers, although it can only connect to one server at a time. Jobs that are scheduled, running, or queued on other registered servers will continue to operate normally even if the client is not actively connected to those servers.

If multiple servers are configured to use the same repository database, they will function as a server cluster, distributing the workload of queued jobs. The clustering functionality in Astera 11 works similarly to version 10. To view which server processed a specific job, right-click on the DEFAULT node in the Server Explorer and select the Job Monitor option.

Repository

Creating a New Repository

If you wish to set up a new repository in Astera 11, go to Server menu > Configure > Build Repository Database and Configure Server.

Follow through with the rest of the steps explained in this article to build a cluster database and set up a repository in Astera 11.

Manually Migrating Existing Jobs from Astera 10 to Astera 11

In case you chose to build a new cluster repository in Astera 11, your next step is to import all the scheduled jobs created in Astera 10.

1. For this, open the scheduler in Astera 10 from Server > Job Schedules.

1. You will see all the scheduled jobs listed in the scheduler. Select the jobs you want to migrate.

1. Click on the Export Schedule icon in the Scheduler toolbar.

1. Point to the directory and folder where you want to save the scheduled jobs and click OK.

1. Now Astera will create a separate XML file with '.Sched' extension for each scheduled job and save it in the designated folder.

1. A message window will pop up to notify that your scheduled jobs have been exported successfully. Click OK.

1. Now you need to import the scheduled jobs in Astera 11 to complete the migration process. For this, open Astera 11 client and go to Server > Job Schedules.

1. This will open the Scheduler tab. To import the existing jobs, click the 'Import Schedule' button in the Scheduler toolbar.

1. Point the path to the directory where you have saved the schedule files. Select all the scheduled jobs you want to import and click 'Open.'

1. You can see that the existing jobs scheduled in Astera 10 have been successfully migrated to Astera 11 and a new Job ID has been assigned to each job.

Migrating Existing Jobs from Astera 10 to Astera 11 Using Pre-Designed Flows

After building a new cluster repository in Astera 11, an alternate way of shifting all the scheduled jobs from Astera 10 to Astera 11 is to use pre-designed flows.

Prior to any upgrade, we strongly recommend that you take a full backup of your repository database. Also, upgrading a lower-level environment first (such as QA, UAT, etc.) is recommended prior to upgrading the production environment. This will make it possible to sort out/resolve any issues before upgrading production.

Steps to Upgrade:

Using Astera 10 client, run the following dataflow to export existing schedules into a comma-delimited file.

Follow this link to download the dataflow: Dataflow Schedule Export

Next, open the downloaded file in Astera 10. The dataflow will look like this:

Once the objects have been configured, run the dataflow. This will create a CSV file containing data of all the schedules that existed in v10.

Next, take note of any existing Cluster Settings. You can check it by right clicking the cluster in the Server Explorer and selecting Cluster Settings in the context menu. These settings will need to be re-configured manually after the upgrade.

It may be helpful to take screenshots of those settings for later reference. The settings include Staging Directory, Purge Job Frequency Options, Email Notification Setup, etc.

Next, install Astera 11 client and server on your machine. You can read more on installing Astera 11 client and server in this document.

Open Astera 11 client. Go to Server > Manage > Build Cluster Database. Point it to the database hosting the Astera repository.

Use the dataflow below to import the schedules you exported previously in Astera 10.

Download attached example dataflow: Dataflow Schedule Import

The dataflow will look like this:

Once the objects are properly configured, save and run the dataflow.

Next, open Server Explorer, right-click on DEFAULT, and select Cluster Settings.

Now, manually re-configure the relevant settings. You can use the screenshots of Cluster Settings you previously took for reference in version 10. Optionally, you can manually reconfigure the Server Profile setting if a non-default profile was used prior to the upgrade.

Now, restart the Astera server.

This completes the upgrade.

You can download the flows by clicking on the links below:

• Dataflow Schedule Export (70 KB)

• Dataflow Schedule Import (60 KB)

Migration Best Practices:

• When you are starting the migration process, it is recommended to keep Astera 10 and Astera 11 servers running in parallel. This is to avoid any interruption in jobs that are currently running.

• We also recommend that you initiate the migration process with a lower-level, testing environment and then promote your deployment to a higher-level environment as needed. This will help ensure smooth migration process with any flow compatibility issues spotted early in the transition cycle.