What's the best possible name for a backup server in a development environment?

Question

Hi, I run an office network and we have many servers. We try to give them nice server names regarding their functions, avoiding stupid names like 'dev01' or stuff like that. For testing our server is named 'pandora'. For development (where all stupid things happens) is named 'homer'. The question is, what's the best possible name for a backup server?

Thanks you all!

ps: I post this question at stackoverflow as I consider server-naming part of development practices... sorry if considered dumb admin thing...

Answer 1

//BLACKHOLE................

Answer 2

Because somebody has to suggest it: \\BACKUP_SERVER comes to mind.

Oh boy, this thread is going to be fun! Unless it gets closed. Please don't.

(sitting back and waiting)

Answer 3

How about Gemini?

Answer 4

We named our backup infrastructure "Cantina". It is Italian for wine-cellar :)

Answer 5

I'd vote for Deep Thought. If it has the Answer to The Ultimate Question of Life, the Universe, and Everything, it must be suited for backups.

Answer 6

FalloutShelter, because if something's gone badly enough that you need to use the backup, you'd better hope it's been protected ;)

Answer 7

It's less fun, but simple functional names do have advantages. backup01, devbak02 sort of thing often makes diagrams easier to understand. But since you asked ...

Gringot

Smaug

Monte (and Carlo)

Thread (and Needle)

History (and Breathing)

ArkStore

Tower (and London)

Answer 8

My backup drive is called "The DeLorean"

Answer 9

Perhaps, cryo.

"Cryonics is the low-temperature preservation of humans and animals that can no longer be sustained by contemporary medicine until resuscitation may be possible in the future." (Wikipedia)

Answer 10

Lazarus seems appropriate ;)