Hmmmm.... CONTIGVOL will not reduce current fragmentation, but it might
gather some free space together so that future file builds may be
a little less fragmented.


How about:

STORE @[log in to unmask]@;;SHOW;FILESET=(*T1,*T2...)

Maybe Verify these tapes as time allows, could even do it while
other backup is going if you have multiple drives...if not,
consider buying an extra drive before doing all this!

{might do house keeping now, like purging old spoolfiles, Editor K files,
real old logfiles, and other obvious junk. MPEX is real handy for this.)

STORE @[log in to unmask]@[log in to unmask]@[log in to unmask]@[log in to unmask]@.SUPPORT;*T;PURGE

RESTORE *T;@[log in to unmask]@;KEEP;OLLDATE (using tape just made, without system files)

Don't forget the OLDDATE, or you will lose all your file creation dates.


I doubt the system files are all that fragmented, nor would it make a big
difference if you did unfragment them. Of course, you could run CONTIGVOL
after you do all the purging, is there is enough left on disc to warrant it.


-----Original Message-----
From: bArtoque [mailto:[log in to unmask]]
Sent: Monday, September 11, 2000 7:06 PM
To: [log in to unmask]
Subject: [HP3000-L] store/reload to get rid of disk fragmentation


Howdy,

I know it probably has been in the list a couple of times (understatement, I
think...), but (ther's always a but...) I'm gonna ask it anyway. We're
goiung to do a system reload, but have'nt done it EVER. My problem is that a
lot off people have a lot of opinions about what's good/better/best, but
what whould be a good STORE of all files on the sytem and a good
restore/reload procedure to get rid of disk fragmentation? Before the reload
(our client wants us to do it anyway, because they hope for performance
increase instead of bying a new machine) we wanna try "VOLUTIL > CONTIGVOL"
to get rid of a little bit of fragmenation (I now it's no real defrag and we
haven't done this before either ). Should or shouldn't I use buldjob or
other procedures? Has someone maybe put on paper a nice strategy of doing
the store/reload. S'thing like I found in the backissues:

0) Kick everyone off, and shut down networking (so no files will fail to
STORE because they are in use for writing.
 1) As MANAGER.SYS, :RUN BULDACCT;INFO="@"
2)     :FILE T;DEV=TAPE
         :STORE @[log in to unmask]@;*T;DIRECTORY;SHOW
3) VSTORE (or however you like to verify your tapes), on a different tape
drive, if possible.
4) If you have time, make a second backup (I don't trust tapes)
5) Go into SYSGEN, and make a new SLT

When you're ready to reload:
1) Boot from the SLT
2) Use VOLUTIL to add the rest of your disc drives
            :VOLUTIL
            volutil: NEWVOL volumesetname:membername LDEV=nn
3) :RESTORE *T;@[log in to unmask];CREATE;KEEP;OLDDATE;SHOW=OFFLINE
            :FILE T;DEV=TAPE
            :RESTORE *T;@[log in to unmask]@;KEEP;CREATE;OLDDATE;DIRECTORY
4) :STREAM BULDJOB1.PUB.SYS
5) :RESTORE *T;/;CREATE;KEEP;OLDDATE;SHOW=OFFLINE

What bothers me, is to actually make a reload, you have to purge EVERYTHING
from the system (maybe only not @.pub.sys or so, cause you probably won't
win that much defrag and still have the operating working system?!?).

Please try to spare a couple of moments of your valueble time to help me
(and probably others), cause I'm now at the point of calling HP for help,
for s'thing which should be a simple (but timeconsuming) system task.

Th@nx in advance,

bArtoque