[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

2508.0. "Backup: Should SENDER and FETCHER be stopped?" by COPCLU::ELIN (Elin Christensen @DMO, DTN 857-2406) Thu Apr 01 1993 14:08

    
    A customer asks if he should stop SENDER and FETCHER during VMS backup
    of his ALL-IN-1 system.
    
    He has just had a disk crash, and when he restored ALL-IN-1, both
    PENDING.DAT and the SDAF were missing. The file names were present, but
    DIR/FULL showed only the file name and "No such file".
    I created a new PENDING.DAT and the customer found an older backup of
    the SDAF, restored it and ran TRM.
    
    Now I have adviced him to shutdown ALL-IN-1 before running backup.
    I found a STARS article that told how to include ALL-IN-1 shutdown into
    a DCL command procedure used for backing up a system.
    
    Is it secure to run BACKUP/IGNORE=INTERLOCK on an ALL-IN-1 system that
    has been closed down? Or do we have to stop SENDER and FETCHER and/or
    other jobs  in order to prevent these from updating ALL-IN-1 data files
    during backup?
    
    Elin

T.R	Title	User	Personal Name	Date	Lines
2508.1		BUSHIE::SETHI	Man from Downunder	`Fri Apr 02 1993 01:02`	20
	Elin, If I am reading your question correctly your customer wants to be absolutely sure he backs up everything and is able to restore without a problem. The only way you are going to be able to do that is to make sure no one is accessing that disk, including senders and fetchers. The "/IGNORE=INTERLOCK" as a qualifier to BACKUP just copies the file header and ignores the contents of the file. It's also best use "/VERIFY" to be sure that everything has been backed up correctly, it adds time to backups at least you are as sure as you can be that the backup "trustworthy". Also OpenVMS group will never guarantee that the BACKUP utility is 100% full proof. I hope that I have been of some help, regards, Sunil
2508.2	Don't Bother the Sender/Fetcher	ATLANA::SHERMAN	Debt Free!	`Fri Apr 02 1993 22:05`	15
	Hi Elin, Sunil's comments regarding BACKUP/IGNORE=INTERLOCK in .1 are correct. It is well known throughout ALL-IN-1derland that that _ONLY_ method to use to get a reliable, restorable BACKUP of the ALL-IN-1 disk is to be sure that ALL-IN-1 is shutdown and then do your BACKUP. As long as ALL-IN-1 is shutdown, both the Sender and the Fetcher batch jobs will continue to (start, determine that ALL-IN-1 is down, then resubmit themselves), all without opening any files on the disk your customer is trying to cleanly BACKUP. Hthy, Ron
2508.3	Thanks	COPCLU::ELIN	Elin Christensen @DMO, DTN 857-2406	`Tue Apr 06 1993 12:38`	8
	Thanks, I'll tell my customer not to worry about Sender and fetcher. As long as ALL-IN-1 is shut down I guess that it is OK to do BACKUP/IGNORE=INTERLOCK ? Elin
2508.4	BACKUP has problem ask for patch CSCPAT_1101015	BUSHIE::SETHI	Man from Downunder	`Wed Apr 07 1993 00:27`	20
	Hi All, Just thought that I would let you know of a problem with backup under OpenVMS 5.4 through 5.5-2. BACKUP/IMAGE/VOLUME may created unusable savesets and the only way to find out is to put a /VERIFY and a number of problems will be reported. In other words you won't that you have a corrupted saveset(s) and will not be able to restore your disk, unless you had /VERIFY which would confirm the problem. There is a CSC patch available it's called CSCPAT_1101015, please contact the local CSC for advise. There are several problems that have been addressed concerning BACKUP. Just thought that I would warn you all and Elin as she is advising a customer. By the way the customers will not be given this patch unless they request it !!!! Don't ask me why it's mind boggling. Regards, Sunil