In our case, the third party backup was suspect because of the corrupted catalog blocks. The SFS guru at the Support Center suggested that the UNLOAD/RELOAD after zapping the blocks in error was the only reliable way to recover. We agreed after discussing the situation with him.
Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, July 09, 2007 5:07 PM To: [email protected] Subject: Re: Philosophy on Tool Installations > And for those who say that SFS is so reliable that its being down is of > no concern, I say take off those rose colored glasses. Especially if you do not have a 3rd party backup utility and have to rely on FILESERV BACKUP as your SFS backup utility. Getting a truly clean backup of a SFS pool w/o 3rd party tooling is highly disruptive -- most CMS apps don't deal well with their disks suddenly going read-only without warning.
