home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gossip.pyramid.com!olivea!charnel!rat!usc!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!casbah.acns.nwu.edu!jweiss
- From: jweiss@casbah.acns.nwu.edu (Jerry Weiss)
- Newsgroups: comp.os.vms
- Subject: Writeback Cache and other trivia
- Message-ID: <1992Dec22.220607.8221@news.acns.nwu.edu>
- Date: 22 Dec 92 22:06:07 GMT
- Sender: usenet@news.acns.nwu.edu (Usenet on news.acns)
- Organization: Northwestern University, Evanston Illinois.
- Lines: 29
- Nntp-Posting-Host: unseen1.acns.nwu.edu
-
- During a regular test of my backup procedures (ie: my system crashed and
- when it came back up a few things didn't work ;-( ) I discovered that I did
- not have a copy of jbsysqueue.dat on my daily incremental backups
- [backup/mod/since=backup....]. I pulled a slightly older copy off my full
- image backup and sat down and tried to understand why. Jbsysqueue.dat is
- one of those files that is always open and the modified field in the
- directory header is not updated.
-
- Is there a standard way to mark the file as modified so it gets picked
- up normally in this situation? I've RTFM but it doesn't give me any
- insight into this particular situation.
-
- Should I just make a copy before my daily backups ?
- [backup/ignore=(interlock) jbsysqueue.dat copy_of_jbsysqueue.dat]
-
- Does the mount/cache=writethrough option have any bearing on this problem?
- If so, how does one set this for the system disk?
-
- Any there other files in VMS (not counting 3rd party software) that
- require special attention?
-
- Thanks for any help, pointers or suggestions you may offer.
-
-
-
-
- --
- Jerry S. Weiss "If you can't stand the heat, stay out of the antimatter!"
- j-weiss@nwu.edu Dept. Medicine, Northwestern Univ. Medical School
-