>the operator didn't wait for the shutdown to finish before doing the IPL.
Then one would use SHUTDOWN REIPL
Note too that CP writes shutdown progress messages to its consoles; on
the HMC you can find them under Operating System Messages
2008/3/30, O'Brien, Dennis L :
> We've occasionally had to
We've occasionally had to FORCE start a system after a planned shutdown,
and we can't find any reason why the shutdown wouldn't have completed
successfully. We're thinking maybe the operator didn't wait for the
shutdown to finish before doing the IPL. We recently changed from 3174
console control
Marcy,
FILESERV GENERATE does a CMS FORMAT of all the server minidisks, one at
a time. If you want to speed it up, you could do the FILESERV GENERATE
with a minimum number of minidisks in your POOLDEF file. While that's
running, run several VM:Batch jobs in parallel to CMS FORMAT and RESERVE
all
>Part of a DR procedure is running an exec that regenerates all SFS
servers
How long does yours take?
Takes an annoyingly long time - nearly an hour - to regenerate an 90G
filepool.
If we didn't do disaster tests monthly, it wouldn't be so bad, but what
the heck could it be doing for an hour?! (z
On: Sat, Mar 29, 2008 at 12:57:26PM -0400,Jim Bohnsack Wrote:
} A point about VMBACKUP, however, is that while we don't use it for DR,
} we do use it. One day I was looking thru the VMBACKUP logs of what got
} dumped and to my surprise, found that the VMBACKUP 1B0 disk, the
} catalog, doesn't
A point about VMBACKUP, however, is that while we don't use it for DR,
we do use it. One day I was looking thru the VMBACKUP logs of what got
dumped and to my surprise, found that the VMBACKUP 1B0 disk, the
catalog, doesn't get dumped by VMBACKUP. I always knew that it would be
kind of a fuzz
On Friday, 03/28/2008 at 11:05 EDT, Colin Allinson
<[EMAIL PROTECTED]> wrote:
> What has happened is that most SFS servers start OK but the most active
one
> just dumps on startup.
>
> Is there any way to do a verification/clean process so that I can get it
> started with whatever is valid -
Thanks for all the feedback on this.
I was sort of hoping that the server might do some sort of integrity check
on startup and tell me that there are 'n' corrupt files giving me the
option of starting up without them - sort of like spool does.
Unfortunately, from the feedback, it appears there
One of our RxServer based serves uses DDR to take a daily backup of
key minidisks listed in a control file and count for the remainder on
the weekly & daily incremental backups taken with VMBACKUP. SFS thus
on VMBACKUP, nothing of SFS is on the DDR backup; the DDR must fit on
a single casette (as
