> 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.
Makes sense to me. Anything that's doing that much looking around inside something as complicated as SFS is internally, would be suspect, especially in situations involving corrupted data. Much as I hate to say it, I really have a hard time recommending SFS for shops that don't have significant numbers of regular CMS users. With disk being cheaper than ever, a lot of the resource-conservation reasons for doing it are no longer valid, and since it's a relatively arcane black box (compared to minidisks), it's hard to explain to Linux-only users why something with that many moving parts is better. Has anyone experimented much with using the CMS NFS client and Linux guests to provide CMS file storage? I'd be interested to know how others have fared with it.
