Connecting an Additional Application Server to a new ASCS Server (Same system)

[daniel_piggott-genge]

Hello,

Basically we are in the process of migrating storage and, as part of that, moving from VM to Hyper-V servers. Also we're taking the opportunity to move from Win Server 2012 and SQL 2012 to Server 2016 and SQL 2016.

Anyway, we have the new servers ready to go and I am considering whether I can install the Additional Application Servers ahead of time, connecting to the existing servers and then, when we do the downtime migration to the new Hyper-V servers, change what server they point at for the ASCS instance which will still be the same system, SID etc., just a new hostname.

Has anyone tried this ? Also is it as simple as changing the SAPGLOBALHOST parameter in the profile for the instance? Or would I end up having to reinstall them all again? If so I'd obviously wait.

Hope that makes sense.

Thanks,

Daniel

[isaias_freitas · Accepted solution]

Hello Daniel,

How are you planning to migrate the system from the old to the new servers? Would you do a System Copy?

In any case, "technically speaking" it would be possible.

However, the manual changes also involve the Windows Service "SAP<SID>_XX", not only the profiles.

In addition, such procedure would not be supported by SAP.

Regards,

Isaías

[daniel_piggott-genge · Accepted solution]

Yes we are doing the process using System Copy and detach/attach method for the SQL DB.

Perhaps it would be worth waiting till the weekend to do the installs as we migrate, though the services file is on the list for the migration anyway as we're changing some ports due to the message server being split out where it hadn't been previously in some system's cases.

All good fun!

Thank you for your reply

Edit - Sorry, re-reading your comment I see you mean the Windows Service itself where it points to the profile location would need updating too. Thank you

[isaias_freitas · Accepted solution]

You are welcome! 🙂