How do we maintain schedules when migrating server or upgrading version?

How do we maintain existing job schedules and job histories when migrating server to a different machine or upgrading to a different version?

Job schedules, job history and all other information associated with jobs running on a server are maintained in the cluster database. The Build Cluster Database option resets the repository if it already exists, erasing all existing data.

To maintain this data while migrating the server to a different machine or a higher version, choose the option to ‘Upgrade Cluster Database’ in Server > Repository Settings instead of building a new database.

In case you are installing the same version on the different machine, this option does not make any changes to the repository, it only associates your existing repository with the new Server. In case of version upgrade, the option adds new tables and columns to your existing repository, making it compatible with the new version, keeping all your previous data intact. In both cases, migration and upgradation, with the Upgrade Cluster Database option, all the jobs scheduled in the existing server will appear in the new Server after the configuration.

As an added step to safeguard your repository data, create a backup of the cluster database before

Visit this link for step-by-step instructions for migrating from Astera 9 to Astera 10.