Moved to a new server

[Scott Greczkowski]

This was unexpected... just got a note from our server company letting us know they had to move us to a different server. The move was already completed. I didn't know about this move until I got this email below. If you see anything strange let me know.

Dear Scott Greczkowski,

In order to ensure the continued stability of your system, it was urgently necessary to move your server v2202502254 to another host system.

We have done this to protect your data and to ensure the regular operation of your server. The migration has just been completed with the restart of your server.

We generally recommend removing snapshots if they are not needed. In general, this allows us to move your server live, so that no restart is necessary. In exceptional cases, however, it may be necessary for us to perform a reboot nevertheless, then we will of course inform you beforehand, as in this case.

Usually we also try to inform you about such a migration process with a necessary reboot in advance. Unfortunately, this was not possible in the current case due to the urgency.

Thank you for your understanding.

 

[Scott Greczkowski]

And looking at things it does appear they did move us and restart things. Showing the server has been up for 55 minutes.

 

[TRG]

Hmmm... That sounds ominous. That said, I haven't seen anything out of the ordinary.

 

[Scott Greczkowski]

I didn't notice any issues before they moved us, but who knows what the reason is they had to move us.

 

[FTA4PA]

Protect it from what? Data loss... or something worse...

 

[NYDutch]

I didn't notice any issues before they moved us, but who knows what the reason is they had to move us.

They may have been seeing signs of an imminent hardware failure. I recall making a similar move to a hot spare server when one of the RAID controllers started throwing high error correction numbers. My users never noticed a thing.

 

[navychop]

Velly Intellesting….

 

[Bobby]

Velly Intellesting….

I know nothing!

 

[Foxbat]

I would have thought everything would have been hosted in a VM environment where outages due to hardware failures are a thing of the past. Lose a Virtualization Host server, migrate the load to a different Virtualization Host. Depending on the platform, the VM may not even notice.

 

[harshness]

Sounds like you may have been stacking up quite a pile of snapshots.

 

[Scott Greczkowski]

Sounds like you may have been stacking up quite a pile of snapshots.

Our account only allows for two of them and we only have one. I do one snapshot a month.

We have a number of offsite backups as well so a snapshot is only needed to do a bare metal restore and then we can restore the rest and bring us back up to date rather easily.

 

[Jimbo]

Scott,
You weren't informed of this happening till After it was done ?

That seems really odd I would hope.

 

[NYDutch]

Scott,
You weren't informed of this happening till After it was done ?

That seems really odd I would hope.

Some times it's faster to fix the problem and then make the notifications.

 

[harshness]

Our account only allows for two of them and we only have one.

It seems odd that they would mention "stale" snapshots if you have only one.

 

[harshness]

Some times it's faster to fix the problem and then make the notifications.

Faster isn't always better (unless the problem is definitively identified as a hardware issue).

 

[NYDutch]

Faster isn't always better (unless the problem is definitively identified as a hardware issue).

I didn't say "always", but in this case I'll defer to the on scene tech(s) that presumably know what's best for the client.