Skip to main content
Solved

Migration to new hardware using LiveSync?

  • 30 September 2021
  • 1 reply
  • 240 views

Working on hardware and OS refresh. My first shot was to attach new machine to LiveSync (already has active-passive configuration present) allow it to sync and make new one active one. Is it possible? Or better follow Commserve hardware migration procedure? 

Not sure if OS (Windows 2019 vs 2012)  and SQL (2012 vs 2016) version mismatch would allow me to do so? 

First attempt was not successful, as failover instance is not able to communicate with other nodes. Throwing  “Failed to get current active node from config file for node” errors. Don’t want to wast time for troubleshooting  as it may not te supported at all. 

In theory, it sounds like you have a valid idea, though the number of caveats are too high to consider it a valid path IMO, especially if Index Cache, DDBs, or MagLibs are involved.

I would just follow the Hardware Refresh guide.  It works every time and should cover any odd contingency that trying a live sync might not. 

Reply


Terms & ConditionsCookie settings