Closed Bug 576366 Opened 14 years ago Closed 14 years ago

archive xserves

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: phong, Assigned: phong)

References

Details

(Whiteboard: [needs deploystudio])

backup and archive to tape:
physical:
=========
bm-xserve01 (PPC G5 xserve; 2 x 2.3ghz cpu; 4gb ram)
bm-xserve05 (PPC G5 xserve; 2 x 2.3ghz cpu; 2gb ram)

physical
========
fx-mac-1.9-slave2 (which seems to be bm-xserve10, even though not in
inventory?)
bm-xserve08
bm-xserve20
Assignee: server-ops → phong
Flags: colo-trip+
...and also these other physical machines:
bm-xserve02
bm-xserve03
bm-xserve04
(In reply to comment #1)
> bm-xserve03
> bm-xserve04

Please don't format these machines.  They are active production machines.
(In reply to comment #2)
> (In reply to comment #1)
> > bm-xserve03
> > bm-xserve04
> 
> Please don't format these machines.  They are active production machines.

Thanks for catching that jhford. 

Phong: sorry, my bad. bm-xserve03, 04 are already in use with geriatric-master. I missed that when I commented in bug#575859.

However, bm-xserve02 and all the machines in comment#0 should be backed up and reimaged.
Severity: normal → enhancement
Depends on: 586327
Whiteboard: [needs deploystudio]
(In reply to comment #3)
> (In reply to comment #2)

> However, bm-xserve02 and all the machines in comment#0 should be backed up and
> reimaged.

Phong: any ETA on these backups? We'd like to recycle these machines for other build work.
Severity: enhancement → normal
currently taking an image of:
bm-xserve01
bm-xserve05
fx-mac-1.9-slave2

The progress says it will take over 200 minutes to finish.  I will wait for those to be completed and moved off before moving on to the next batch.  I don't think we have enough storage until then.
bm-xserve08 is backed up.  bm-xserve02 is still running.
There are all done.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.