Hello all,
Thanks to all that replied!
Bryan.Lavelle_at_digital.com, tpb_at_doctor.zk3.dec.com, bseymour_at_ns.encore.com,
francini_at_nashua.progress.com, alan_at_nabeth.cxo.dec.com ,
Dave.Vaughan_at_digital.com, ian_at_physics.uq.edu.au, wmills_at_WellsFargo.COM ,
Franz.Fischer_at_lpr.e-technik.tu-muenchen.de, rb237_at_phy.cam.ac.uk.
I did the upgrade last Friday night, and it went great. I ended up making
a 256m root, and 256m swap. Is that enough swap? A few people suggested to
just go with 256m root instead of 128 if i had the space, which i did.
After much headaches trying to figure out disklabel, i finally got it
right. Give me linux fdisk any day. :)
bseymour_at_ns.encore.com:
> Tom Blinn has mentioned that 256M is a better idea, just to be sure.
> If you've got a 9 gig to start, better a bit of waste in root
> than too little later.
Almost every suggested doing the dump/restore between the two drives
instead of going through tape, which i really wanted to do. But it didn't
work... :( alan_at_nabeth.cxo.dec.com warned me of this:
> If you have the slot for the new drive, you can do the
> backup without having to go through tape. The non-patched
> version of dump won't write to a tape, which you need to
> do this, but vdump will and can backup UFS. You could
> also try extracting the V4.0D dump from the distribution
> and use that. Or track down the appropriate patch. You
> will want to make the backup with the file systems quiet
> or unmounted where possible. Single-user is sufficient
> for this.
My dump didn't work, and i didn't feel like getting the patch, etc. We
knew a tape restore would work, so we just ordered some pizza's and
restored from tape. :)
BTW, the firmware upgrade went without incident also, which was another
thing i was worried about.
Thanks again,
Ray
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean ray_at_cs.selu.edu
rdejean_at_selu.edu
http://cs.selu.edu/~ray
Network Specialist 504-549-3420
Southeastern Louisiana University Administrative Computing Services
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Original message:
Date: Thu, 11 Feb 1999 09:14:28 -0600 (CST)
From: Ray DeJean <ray_at_selu.edu>
Followup-To: poster
Subject: Upgrade 4.0A to 4.0D
Hello all,
I'm about to upgrade the campus webserver (Alphaserver 1000, 1cpu, 96mb
ram) to 4.0D and had a few questions.
First off, my root partition is 64mb with about 7mb free. I don't think
this will be enough for the update, correct?
Also, the current sysadmin uses dump/restore, but i keep hearing
vdump/vrestore on this list. From what i gather, vdump can work on AdvFS
filesystems, dump can't? I only have UFS filesystems, any other
advantages to vdump?
This is my current plan of attack. If anyone has any other tips, or
pitfalls to beware of, i'd greatly appreciate it!
1) Make 2-3 backups of each filesystem. :)
2) Shutdown. Move 9gig drive into slot 0, move 2gig current root to slot3.
3) Partition new drive with 128meg root partition.
4) Restore all filesystems from tape. Hopefully now the system is
running exactly as it was before, but with a 128mb / partition.
5) Do pre-update stuff. Update firmware. Begin update install.
If anyone can think of anything i'm missing, please let me know. Thanks!
later!
Ray
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean ray_at_cs.selu.edu
rdejean_at_selu.edu
http://cs.selu.edu/~ray
Network Specialist 504-549-3420
Southeastern Louisiana University Administrative Computing Services
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Received on Fri Feb 19 1999 - 00:20:32 NZDT