Do backup of VMs and machines being mothballed

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
9 years ago
3 years ago

People

(Reporter: joduinn, Unassigned)

Tracking

Details

(Whiteboard: need backup dest)

These VMs were removed from production, and will be deleted. Before we delete them, we need a complete backup of each, in case we need to recreate in a rush:

> balsa-18branch
> bm-xserve03
> bm-xserve04
> production-pacifica-vm02
> production-prometheus-vm02



...just in case we are surprised, and suddenly need to recreate these machines.
(In reply to comment #0)
> > bm-xserve03
> > bm-xserve04

I doubt an Xserve is a VM...

Updated

9 years ago
Assignee: server-ops → phong

Updated

9 years ago
Assignee: phong → mrz

Comment 2

9 years ago
Aravind - where can I copy these off to?
(In reply to comment #1)
> (In reply to comment #0)
> > > bm-xserve03
> > > bm-xserve04
> 
> I doubt an Xserve is a VM...

Correct. However, these both do need to be backed up, so we can reformat and recycle them.
Summary: Do backup of VMs being mothballed → Do backup of VMs and machines being mothballed

Updated

9 years ago
Assignee: mrz → aravind
Whiteboard: need backup dest

Comment 4

9 years ago
I'm going to back up bm-xserve03/04.  These are PPC xserve.

Comment 5

9 years ago
The 2 xserves are backed up.
(In reply to comment #5)
> The 2 xserves are backed up.

Cool. 

What about the 3 VMs - are they backed up yet?

(John glances at his trusty axe and hopes)
Put them on dracula:/mnt/build.  That directory is already NFS exported.  Let me know once they are there and I can back them up from there.
Assignee: aravind → mrz

Comment 8

9 years ago
balsa-18branch -> eql01-bm06
production-pacifica-vm02 -> c-sata-build-002
production-prometheus-vm02 -> c-sata-build-002

Comment 9

9 years ago
VMs copied over to dracula and will get backed up in the next backup run.  Over the fence for you guys to delete.
Assignee: mrz → nobody
Component: Server Operations → Release Engineering
QA Contact: mrz → release
No need to reassign; we are already tracking our shutdown+deletion work in bug#487235.

Reassgining back, and closing. Thanks!
Assignee: nobody → server-ops
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Component: Release Engineering → Server Operations
QA Contact: release → mrz
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.