# Migrating from Astera 7.x to Astera 10

Astera 10 is a major release and not a direct upgrade of Astera 7.6. This means that migrating from Astera 7.x to Astera 10 won’t require you to uninstall Astera 7 since Astera 10 can be installed side by side with Astera 7 on a system. Astera 10 is backward compatible, and therefore, most of the flows created on Astera 7 can run on Astera 10 without modifications. However, as with the most major release of any complex software, we recommend that you upgrade your lower level environment first, so you have an opportunity to test and verify any existing flows. This will make it possible to identify any migration issues you may encounter early on in the upgrade cycle. In this document, we will cover how you can migrate from Astera 7.x to the all-new Astera 10.

**Installing**

The installation package for Astera 10 (64-bit) contains two setup (.exe) files:

* Astera*DataIntegrator.exe* – for Astera client, and
* *IntegrationServer.exe* – for Astera Integration Server

The setup files for Astera 10 can be downloaded from the following location:

<https://www.astera.com/download-center/>

[Click here](https://documentation.astera.com/astera-data-stack-v10/setting-up/installing-client-and-server-applications) to learn how to install Astera 10 client and server.

**Licensing**

Unlike the previous releases of Astera, Astera 10 comes with a single licensing key (for server) rather than two separate keys for Astera server and client. The licensing key for Astera 10 has changed which means you cannot use your Astera 7 key to register Astera 10. The single licensing key for Astera 10 is used to register Astera server and it controls how many clients can connect to the server as well as the functionality available to the connected clients.

If you’re planning to migrate to Astera 10, please contact [sales@astera.com](mailto:sales%40astera.com) to get your new your Astera 10 license key.

**Cluster and Server Management in Server Explorer**

The Astera 10 client can be configured with multiple different servers, however, it can only connect with one server at a time. The jobs scheduled, queued or running on the other registered server will continue to run without interruption even if the client is not currently connected to the server.

All servers pointing to a single repository database will form a cluster of servers sharing the common workload of queued jobs. A cluster of v10 servers you configure will be up and running and processing jobs in a similar way to 7.6, despite the fact that the v10 client can only connect to and manage one v10 server at a time. You can see which server in the cluster has actually processed a job by right clicking the Cluster and opening *Server Jobs* window.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FwtPwhwzKfZKh7eIVbMGB%2F1.PNG?alt=media&#x26;token=a760cf9c-7a07-48f6-86e6-5eba67afeea9" alt=""><figcaption></figcaption></figure>

**Repository**

You need to set up a new repository to communicate with the Astera 10 server. While upgrading the previous releases of Astera 7, you would simply go to *Server* > *Upgrade Cluster Database*. However, while migrating to Astera 10, you need to set up a repository in a new database from scratch to communicate with the server(s) and store the record of server activity. To set up a repository in Astera 10, go to *Server menu > Configure > Build Repository Database and Configure Server*.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FZHLsjhyHQXqE9bsYpJrT%2F2.PNG?alt=media&#x26;token=7cfb26ac-766b-4bb6-9fc7-0146822b96e4" alt=""><figcaption></figcaption></figure>

Follow through the steps explained in [this article](https://documentation.astera.com/astera-data-stack-v10/setting-up/how-to-build-a-cluster-database-and-create-repository) to build a cluster database and set up a repository in Astera 10.

### **Manually Migrating Existing Jobs from Astera 7 to Astera 10**

Once you have built a cluster repository in Astera 10, the next step is to migrate the scheduled jobs you created in Astera 7.

1. For this, open the *Job Scheduler* in Astera 7 from *Server* > *Job Schedules*.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FkgESiXZ4urQG92oZ15Ao%2F3.PNG?alt=media&#x26;token=5c279727-1e54-4490-95d1-19899d1bb655" alt=""><figcaption></figcaption></figure>

2. You will see all the scheduled jobs listed in the Scheduler. Select the jobs you want to migrate.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FLQLudlzeS38IWNhv5jNM%2F4.PNG?alt=media&#x26;token=806d1323-7b04-49c0-a614-71013fcada9e" alt=""><figcaption></figcaption></figure>

3. Click *Export Schedule* button in the Scheduler toolbar.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FZ7t1Q2ZVel2LcdLY7GFi%2F5.PNG?alt=media&#x26;token=823fea6c-d3e2-4c36-b373-2587e3fcdaa8" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2F5QJ4W7UURbPK87P0dglD%2F6.PNG?alt=media&#x26;token=369fc684-5a66-4241-88ad-af8b14fc6bd2" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FMQjTIkbNc0ZAScYlcnsW%2F7.png?alt=media&#x26;token=92ad2874-2542-4c55-a683-bcc8846fe481" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FmpkfZioRLUE440TifaFj%2F8.png?alt=media&#x26;token=93b0fd8e-fcdb-426b-b62d-16160181d9e2" alt=""><figcaption></figcaption></figure>

6. Now you have to import the job files in Astera 10 to complete the migration process. For this, open Astera 10 client and go to *Server* > *Job Schedules*.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FSOw6sG9w04dCFsfyrHxx%2F9.png?alt=media&#x26;token=414dfd49-0308-4c7d-9ab2-54fcae65c443" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FpvjOFGAag88cQa39yizV%2F10.png?alt=media&#x26;token=2cd1d2c8-78ad-4063-a81b-befd9c2ed948" alt=""><figcaption></figcaption></figure>

8. 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*.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FW5mwT5lRMk5B5SstpIUf%2F12.png?alt=media&#x26;token=e0355018-f71f-4bb4-b4d0-022580dd7d3a" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2F9wgFV9Dt6dlbVyb90CSO%2F13.png?alt=media&#x26;token=2872b8ec-3e81-4a9e-8631-293c67289224" alt=""><figcaption></figcaption></figure>

### **Migrating Existing Jobs from** Astera **7 to** Astera **10 Using Pre-Designed Flows**

Prior to any upgrade, we strongly recommend that you take a full backup of your repository database. Also, upgrading 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 7 client, run the following dataflow to export existing schedules into a comma-delimited file.

{% hint style="info" %}
**Note:** Prior to running the dataflow, you will need to update the *Database Table Source* object to point to the database where the Astera repository resides.
{% endhint %}

Download the attached dataflow: [Dataflow\_ScheduleExport7.df](https://astera.zendesk.com/hc/en-us/article_attachments/360001710674/Dataflow_ScheduleExport71.df)

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2Ffu8dt3nAF23jge4ulvZq%2F14.png?alt=media&#x26;token=c2d4d5d5-670f-4518-8fbc-8360acb4c389" alt=""><figcaption></figcaption></figure>

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, and optionally, Server Profiles if a non-default profile was used prior to the upgrade.

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FbLkdRV5dF03CUynleazU%2F15.png?alt=media&#x26;token=dac08d36-276a-4eda-b963-401dfe1e8148" alt=""><figcaption></figcaption></figure>

Next, install Astera 10 client and server on your machine. You can read more on installing Astera 10 client and server in [this document](https://documentation.astera.com/astera-data-stack-v10/setting-up/installing-client-and-server-applications).

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

{% hint style="warning" %}
**Important Note:** This will reset the repository.
{% endhint %}

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FCGZKNkuGEl25jlK6AFQY%2F16.png?alt=media&#x26;token=fcb42f8f-b10f-4c9d-8986-4f9c21f3e32f" alt=""><figcaption></figcaption></figure>

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

Download the attached example dataflow: [Dataflow Schedule Import](https://www.astera.com/Downloads/Centerprise/dataflow/Dataflow_ScheduleImport10.df)

The dataflow will look like this:

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FujpQ0aWChLsvxQ4XARKB%2F17.png?alt=media&#x26;token=eb75a33b-81d7-4611-8970-022f2e4ec7cb" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** Prior to running the dataflow, in the properties of *Delimited File Source,* you must import the CSV file you created in v7 that has data of all the schedules. Also, you will need to change the configuration of the *Database Table Destination* object to point to the database where Astera 10 repository resides.
{% endhint %}

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

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FLAY2Z1QiGrAmlmYL7i1d%2F18.png?alt=media&#x26;token=07b6221a-5a3a-4494-bcf6-0950dcc3707a" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FIuQ1A6yqYpE140HeEHAJ%2F19.png?alt=media&#x26;token=35798f84-3cdb-4f47-853b-86ba0c74cc2e" alt=""><figcaption></figcaption></figure>

Now, restart the Astera server.

This completes the upgrade.

### **Migration Best Practices:**

* When you are starting the migration process, it is recommended to keep Astera 7 and Astera 10 servers running in parallel. This is to avoid any interruption in jobs that are currently running.
* We also recommend 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.
* A new feature in Astera 10 enables you to create an admin email to access the Astera server. As a result, you will also be able to use the “Forgot Password” option while logging in. Read [this article](https://documentation.astera.com/astera-data-stack-v10/setting-up/how-to-verify-admin-email) to learn how to verify the admin email in Astera 10.