Planned downtime: Server move (2019-02-27 13:00 UTC)

[DPblH]

What happens to crops, curios etc. during the server move?
Will they stop growing and continue when the server is back, or will the downtime be counted as time when they would have been growing?

Server have its own globtime which is paused while it is 'sleeping'.

[Hrenli]

Server have its own globtime which is paused while it is 'sleeping'.

But it's not sleeping, it's moving!

[Feyfolken]

Server have its own globtime which is paused while it is 'sleeping'.

But it's not sleeping, it's moving!

But there are 2 different types of time - hardware time in BIOS and internal game time. Server is saved at XX:XX and then star from same XX:XX

[VDZ]

But there are 2 different types of time - hardware time in BIOS and internal game time. Server is saved at XX:XX and then star from same XX:XX

Actually, there are 4 different types of time:

[waga]

I start to have the shake , hurry up !

[shubla]

Obligatory image for the current situation.

[loftar]

As an update, the copy is about 85% complete, and the current ETA is about 30 minutes.

[mvgulik]

Crossing my fingers that the server won’t shit itself and die the moment it’s back up again.

Naa. If its up to Murphy it will be shortly after the source data is cleared.

[loftar]

Hum. The data copy is now complete, and the first problem has appeared. I made the bcache device to use 4k sectors (as that seemed like a reasonable fit with modern storage devices), but apparently the filesystem was formatted to use 512 byte sectors and doesn't support switching between the two. Unless I can change the bcache to use 512 byte sectors "behind the back" of the filesystem, I may have to do the data transfer again. :P

[VDZ]

Unless I can change the bcache to use 512 byte sectors "behind the back" of the filesystem, I may have to do the data transfer again.

I don't suppose making a local copy on the new system to save time would work in this case?