Updating legacy scheduled jobs

When you upgrade from SnapManager 3.2 or 4.0, you must update the scheduled legacy jobs so that they are compatible with SnapManager 6.0.

About this task

In an Microsoft Cluster Services Cluster environment, the SnapManager upgrade tool shows all the nodes in a list. Although you can select a specific node to migrate a legacy job to that particular node, you should schedule the job on all nodes in the cluster, to achieve fault tolerance.

In SnapManager 3.2 and 4.0, the jobs that are scheduled to run against a server are not required to reside there. In SnapManager 6.0, the jobs must be scheduled and run in the same server.

By default, SnapManager enables the Delete legacy job and Replace the job if the job exists check boxes if the target server is different from the server on which the SnapManager 4.0 jobs exist or if the name of the specified job is different from the name of the SnapManager 4.0 job.

Note: When you upgrade from SnapManager 5.0 to SnapManager 6.0, you do not have to update the SnapManager 5.0 jobs as they are compatible with SnapManager 6.0.

Steps

Launch SMEUpgradeJobs.exe from the SnapManager Installation directory.
The Update SnapManager for Exchange legacy scheduled jobs window appears, listing all the SnapManager 3.2 and 4.0 jobs.
To see the jobs in a different server, click Browse to select a different server and then click Refresh.
SnapManager lists the 3.2 and 4.0 jobs for the selected server.
To update the SnapManager 3.2 and 4.0 jobs for SnapManager 6.0, click Update.
A Scheduling dialog box appears that you can use to migrate the 3.2 and 4.0 to 6.0 jobs.
If you do not want to use SnapManager 3.2 and 4.0 jobs for SnapManager 6.0, click Actions > Delete.