Anyone with a currently unused legacy license?

Strator

Verified User
Joined
Jan 19, 2011
Messages
283
Quick question: Is there a kind soul here who happens to have an unused legacy license who would borrow it to me for 1-3 weeks so I can migrate my own legacy license to a new server?

I desperately need to get this done but DA support effectively told me that I cannot migrate, as they aren't giving temporary licenses to legacy users anymore. Their suggestion is that I eighter buy another legacy license (where from they didn't say) or use the same license on the new server. The latter seems like they're pushing me off a cliff: It's been a while since I last migrated and not being able to compare the old setup with the new (to my knowledge this would mean that I lose DA access to my old server) is definitely asking for trouble.

Thanks!
 
Hi,

You don't need another legacy license to migrate your server. Here are some steps you can take:
1. Back up all accounts and server settings from your old server.
2. Install a new DA server with your current license (modify the IP address).
3. Restore accounts/settings to the new DA from the backup.
4. Check everything is OK.
5. Shut down the old server.
 
Hi,

You don't need another legacy license to migrate your server. Here are some steps you can take:
1. Back up all accounts and server settings from your old server.
2. Install a new DA server with your current license (modify the IP address).
3. Restore accounts/settings to the new DA from the backup.
4. Check everything is OK.
5. Shut down the old server.
To my knowledge, I will lose access to DA on the old server the moment I activate it on the new one. Like I pointed out, I don't do this too often, but I do remember that I typically need to go back because I forgot something or I need to compare some setting that didn't end up properly on the new server. Turning migration into a circus act that needs to be 100% perfect on the first try is a recipe for disaster.
 
@Strator Sorry for the confusion. The mention to use another license was meant to imply if your account had another licenses -- not to try and secure one from an outside source. It looks like @Harry Tang provided a suggestion but if that doesn't work for you, you can simply use the same key on both the old and new server (although DA will permit login on one server a a time).

This way, you can retain the old server and bring it back to life at any moment, with DA access, in case something was forgotten or missed during the migration. Our new license key system doesn't even require IP registration, so it's as simple as starting/restarting DA on the server you need access to.
 
Thanks for the reply. I'm not sure if Harry Tang's solution works for me or not. All I know is that the usual path via temp license has been removed, and that any other approach is uncharted territory (at least for me).

So to confirm, for the migration, I can use the same legacy lifetime license on both servers, and DA will remain available on both servers with the only downside that, when logging in on one server, it will log me out of the other?
 
Oh I just answered in the other thread before I've seen this one. I explained what will happen.
DA will remain available on both, just chances are that you can not use the GUI anymore on the original server once the new is installed.
So do GUI things before you install DA on the new server, like make backups first.
 
So to confirm, for the migration, I can use the same legacy lifetime license on both servers, and DA will remain available on both servers with the only downside that, when logging in on one server, it will log me out of the other?

Correct. Whichever server is started/restarted most recently will obtain the licensing, and as @Richard G pointed out, the GUI will deny login on the other server.

Therefore, not only can you use the same key for migration, you can keep your old server on hot-standby for as long as you wish, with DA service stopped, but also knowing you can start it again and access the DA GUI if needed.
 
Thanks for the quick replies, and thanks Richard for dedicating you spare time trying to help, as always. GUI is what I meant in this case - means that I won't be able to do side-by-side comparison if I need to. This can affect anything from stuff that may not be part of the typical backup or mistakes that I make to simply confirming that, if I run into problems, DA is *not* the issue.

Support finally replied to my ticket and hinted it would probably be enough to kill the DA service on one server in order to log into the GUI on the other, so no need to restart the entire server every time. Can that be confirmed?
 
DA licensing does not require a complete server reboot. A systemctl start/stop command is sufficient. Stop one DA, start the other, and you're good to go. You don't even have to edit the license IP these days. Leave it on auto-detect (NULL) and then both servers will obey the start/stop commands.
 
Back
Top