home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pmafire!news.dell.com!swrinde!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!spool.mu.edu!umn.edu!msus1.msus.edu!stafford.winona.msus.edu!user
- Newsgroups: comp.os.vms
- Subject: Re: BACKUP Question
- Message-ID: <Stafford-101192092810@stafford.winona.msus.edu>
- From: Stafford@Vax2.Winona.MSUS.EDU (John Stafford)
- Date: 10 Nov 92 09:31:34 -0600
- Followup-To: comp.os.vms
- References: <9211062238.AA11641@hermann.barra.COM>
- Distribution: world
- Organization: MSUS
- Nntp-Posting-Host: stafford.winona.msus.edu
- Lines: 11
-
- In article <9211062238.AA11641@hermann.barra.COM>, louis@BARRA.COM (Louis
- Dunne) wrote:
-
- > Many people re-use old backup tapes, e.g. every two weeks or so
- > the incremental tapes "come back around" to the set you used two
- > weeks ago. Now this tape has data from two weeks ago on it. Of
- > course your sysop loads it into the drive, and goes home for the evening.
- > Then someone else *ANYONE* (can read it)
-
- How about having your backup job simply assign the device, read the clock
- and sleep (wait 'n') until it is time to start backup? Too simple?
-