Task order on a live transfer

[cPRex]

Are you asking for that temporary disable to happen inside Transfer Tool, maybe as part of that warning?

 

[jpenner]

Yes.

My reasoning is that if I was to start a transfer that took more than a couple of minutes, it's likely I might forget to come back and turn it back on, or I might not be able to get to it upon completion of the transfer (say it ends in the middle of the night).

That could cause issues if another user on the server made a DNS change. I can live with a short disconnection but forgetting it and dealing with a weird DNS support thing a couple of days later could be an issue.

 

[cPRex]

Alrighty - let me run this by the team and we'll go from there!

 

[cPRex]

I went ahead and created two improvement cases with our development team. One is to get a warning in the Transfer Tool that lets the admin know the Destination machine is connected to a DNS Cluster. The second is to explore the possibility of disabling the DNS Cluster connection while the transfer is running, but that will need some investigation as if we just sever the DNS Cluster connection it would cause DNS for all other domains not being transferred to stop working.

Since these are new features/improvements that we'd be adding, I don't have any type of timeframe as to when we might have something. If I do hear something I will try my best to update this post with the details.

 

[Esquio]

There we go - it's the cluster. Once the account gets created that change will get pushed to the cluster so it updates everywhere.

In general, it's best to disable the cluster for a bit while a migration happens or else you run into situations like this.

That's good to know, thank you so much.

 

[cPRex]

You're very welcome!