Re: Request for feedback - BACKUP enhancement

From: Michael Unger (spam.to.unger_at_spamgourmet.com)
Date: 11/09/05 

Date: Wed, 09 Nov 2005 09:05:03 +0100

On 2005-11-09 04:51, "David J Dachtera" wrote:

> Antoniov wrote:
>>
>> The /IGNORE=INTERLOCK qualifier may be very dangeorus because you can
>> save a file while somebody is writing in it. After restore you couldn't
>> read data from file!
>> I agree this is dangerous so in my mind VMS should make a snapshot
>> before backup!
>
> Well, I trust you understand the ramifications of doing so: a huge file
> could take hours to write to tape, and where does VMS store the "deltas"
> while the "original" file is being read?
>
> [...]

Isn't that (very) similar to what is accomplished with "mini-merge" when
a (previous) shadow-set member is "re-integrated"?

Michael 

-- 
Real names enhance the probability of getting real answers.
My e-mail account at DECUS Munich is no longer valid.

Relevant Pages

  • Re: Why COBOL is losing the POWER struggle
    ... But I've seen some subtle errors in very concise ... probability of error, so eliminating them reduces the overall ... Rhetoric & Writing, Michigan State University ...
    (comp.lang.cobol)
  • Re: Cant open saved word document
    ... It's corrupt. ... Restore it from your last backup. ... that I have been writing). ...
    (microsoft.public.word.docmanagement)
  • Re: Request for feedback - BACKUP enhancement
    ... Antoniov wrote: ... > save a file while somebody is writing in it. ... And after restore, you won't be able to read data ... there's a chance you'll get a good copy. ...
    (comp.os.vms)
  • Problem processing partition
    ... enabled in writing. ... I process the cube ...
    (microsoft.public.sqlserver.olap)
  • Re: Removing Old System Restore Points
    ... is a probability you can cause damage. ... Why risk it? ... With system restore the probability is that old restore points may not be good. ...
    (microsoft.public.windowsxp.general)