Thank you for your insight tgmct. Indeed, we also moved both hardware and software on our side with very little outage.

But here, we are moving a system that we did not create, we are not moving hardware and we are reconfiguring the system to the new environment.

In an ideal world, you are absolutely right, the switch-over would be smoother; but, we are running our of time, and thus it is prudent to go to plan B, as we do not have extra time for the test before the move,

I crunch WCG only, and no other project. I have no interest in any other project for now. If WCG is down for a couple of months, it's of no critical importance to me. The upside of the downtime, is that I'm going to save lots of money on electricity

Whenever WCG comes back, I'll crunch. When it's down, I do not crunch. Simple as that.

Good luck with the Transition!

Comparing apples and oranges. Business systems that generate revenue or other critical activities in a business environment (payroll, manage safety systems, etc) cannot be down for days on end or even hours. WCG, on the other hand, is not a business critical environment contrary to the thoughts of many contributors. It could be down for several months and nobody, other than contributors, would care. I would bet the researchers probably welcome the outage to get caught up on the batches that have already been returned and to prepare for the next startup.

Here in Montréal he was called Murphé

I'm just wondering if WCG will not lose some volunteers as they drift somewhere else during that time.

I will be off to Rosetta during that time.

On the positive side will we be given a warning via email when the project will be about to start up again whether it is before or after the projected date?