Re: Replacing Shadowed Boot Drive
From: Chris (an.other_at_not_here.ca)
Date: 04/29/05
- Next message: Chris: "Re: FTP oddity for case sensitiveness"
- Previous message: Chris: "Re: Replacing Shadowed Boot Drive"
- In reply to: Chris: "Re: Replacing Shadowed Boot Drive"
- Next in thread: Shawn: "Re: Replacing Shadowed Boot Drive"
- Reply: Shawn: "Re: Replacing Shadowed Boot Drive"
- Reply: bill_at_wcschmidt.com: "Re: Replacing Shadowed Boot Drive"
- Reply: Meat Loaf: "Re: Replacing Shadowed Boot Drive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 29 Apr 2005 11:29:29 -0400
OK, I can't count --- step 9 should read "6. above" .....sigh
"Chris" <an.other@not_here.ca> wrote in message
news:Ensce.13866$gA5.778961@news20.bellglobal.com...
> You're going to a lot more trouble than I have in past situations:
> 1. Shutdown system normally
> 2. Remove the secondary shadow (physical) unit
> 3. Replace with larger unit
> 4. Boot from CD-ROM
> 5. Mount the primary shadow unit with /OVER=SHADOW
> 6. Perform image backup of primary shadow unit to new, larger unit
> 7. Shutdown system
> 8. Remove old (small) unit from primary slot
> 9. Replace with new (larger) unit just copied to in 5. above
> 10. Leave secondary slot empty
> 11. Reboot per normal from the primary physical unit
>
> (an Analyze/Disk/Repair ahead of any of this is assumed -- the AUTOGEN is
> purely your call as to whether you think the system needs tuning)
>
> In my experience, at boot, the Shadow Server will read the location of the
> shadow unit from the primary (I think that's how it works), try to mount
it,
> fail because it isn't there, and continue with nothing more than a
warning.
> Once the system is up, put your 2nd new drive in the secondary slot,
> initialize it (to be cautious), then mount it into the boot shadowset.
> Depending on how full the drive is, an hour or so later, it'll be up to
> snuff. This has worked in at least 3 instances in the past.
>
> CM
> "Shawn" <shawnm1964@sbcglobal.net> wrote in message
> news:1114781251.750555.105530@g14g2000cwa.googlegroups.com...
> > Hi All,
> >
> > I have a 1000A 5/400 Alpha Server running OpenVMS 7.2-1 which currently
> > utilizes Disk Shadowing on all the drives including the boot drives.
> >
> > The boot drive is made up of (2) 4.3GB shadowed disk drives. I am
> > going to replace both of these drives with (2) 9.1GB Disk Drives and
> > re-enable shadowing.
> >
> > I would like to list the steps I plan to follow and see if any of you
> > have any suggestions or corrections my plan. I have no extra drives to
> > copy the data from the system drives too, so I have to use a DLT Tape
> > Drive. The backup command I am going to use is backup and then restore
> > is my main concern.
> >
> > 1. Comment any scripts called from startup which mount any disks.
> > 2. Modify the modparams.dat file and set SHADOW_SYS_DISK to 0
> > 3. Run the following command autogen savparams setparams.
> > 4. Shutdown the application.
> > 5. Show device/files to ensure all files are closed.
> > 6. Run analyze/disk/repair to fix anything on the drive which could
> > cause a problem.
> > 7. Dismount a member of the shadow set.
> > 8. Shutdown the system
> > 9. Boot from an OpenVMS 7.2-1 CD and enter DCL mode.
> > ***** These next steps I would appreciate your comments on******
> > 10. Mount one of the system drives: mount/over=id dkb0:
> > 11. Backup the drive to tape as an image: back/image/log/ign=label
> > dkb0: mka500:dkb0.sav/save
> > 12. After the backup completes dismount the tape and disk drive: dism
> > mka500: dism dkb0:
> > 13. Shutdown the server and replace the drives.
> > 14. Boot again off the CD Drive.
> > 15. Mount the new drive to be restored too. mount/for dkb0:
> > 16. Restore Data from tape: back/image/ign=label/verify
> > mka500:dkb0.sav dkb0:
> > 17. After the restore has finished dismount tape and disk drives.
> > 18. Shutdown the system and then boot from dkb0:
> > 19. When server has come back up, modify startup scripts to mount
> > drives as usual.
> > 20. Modify modparams.dat file and set SHADOW_SYS_DISK = 1
> > 21. Run the following command autogen savparams setparams.
> > 22. Reboot the server.
> > 23. After the server comes back up and all drives are mounted complete
> > the final step of adding the 2nd drive to the shadow set.
> > mount/system/noassist DSA0:/shadow=($1$dkc0:) ALPHASYS
> >
> > Let me know if you see anything I need to change or modify
> >
> > Thanks in advance
> > Shawn
> >
>
>
- Next message: Chris: "Re: FTP oddity for case sensitiveness"
- Previous message: Chris: "Re: Replacing Shadowed Boot Drive"
- In reply to: Chris: "Re: Replacing Shadowed Boot Drive"
- Next in thread: Shawn: "Re: Replacing Shadowed Boot Drive"
- Reply: Shawn: "Re: Replacing Shadowed Boot Drive"
- Reply: bill_at_wcschmidt.com: "Re: Replacing Shadowed Boot Drive"
- Reply: Meat Loaf: "Re: Replacing Shadowed Boot Drive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|