Skip to Content
0
Former Member
Jan 05, 2012 at 09:36 PM

Data Services 3.2 migration

39 Views

Good afternoon,

I am looking for a little guidance or opinions from fellow admins on my plans to migrate my SAP DataServices 3.2 application from an old server to a new server.

Important information:

Physical servers are changing

Servers are not clustered

The repository database is on a centralized database and will not be changing

(Both old and new servers will use the same repository location)

The Plan:

I am trying to use the same database/schemas for the upgrade and to my knowledge. I should be able to point the new server at the current database & schemas, then update executions to point to the new sever (if they have any local files to use) and then reschedule the re-occuring jobs on the new web console to use the new server.

Steps:

1) Deactivate (and record) all currently scheduled jobs on old data services web management console

2) On the new server's web management console, connect to the repository and begin to re-schedule the jobs, making sure that they're pointed to the new server and activate them.

3) Login to the Designer client on the new server and check through the executions for any object or reference to the previous server. If one is found, change them to the new server and save.

Thoughts?

Thank you all.

-Travis Dirmyer