[Info-vax] BACKUP/IMAGE/EXCLUDE...?

[AEF]

On Apr 2, 5:47 am, "R.A.Omond" <Roy.Om... at BlueBubble.UK.Com> wrote:
> Christoph Gartmann wrote:
> > In article <24cd2c91-4e09-404b-96f3-4b98921ba... at g19g2000yql.googlegroups.com>, AEF <spamsink2... at yahoo.com> writes:
>
> > [...]
> >>    Because all files on the input volume are processed, you cannot
> >> use input file-selection qualifiers in image copy or save operations.
> >> You can, however, restore files and directories selectively from an
> >> image save set.
>
> > Ok, then I'll describe the reason behind my question. I have a disk that
> > is backuped via BACKUP/IMAGE... in a genereal routine/cycle with all the
> > other disks, at repeating intervals, etc. . Next, there is an application that
> > produces huge files on this disk. These files are backuped separately and
> > deleted after they have been saved to tape (BACKUP/DELETE). The files appear
> > somewhat arbitrary and disappear. Now the regular backup of the disk shouldn't
> > copy these arbitrary files that are all in a separate directory. So I thought
> > /EXCLUDE=this_directory could achieve just that. Now that it does not, what
> > else is possible?
>
> Mark the files as /NoBackup.
>
> When you back them up in your separate job, don't forget to
> /Ignore=NoBackup.

Stupid machine! I somehow fat-fingered a post before I finished it.

Anyway,

Keep in mind that /IGNORE=NOBACKUP will cause BACKUP to save page and
swap files.

I think the best strategy is to change the app to write those big
files onto their own disk. If they're written to a disk (or disk
+directory-spec) referenced by a logical name that is used only by the
app, it should be rather easy to do this by simply redefining the
logical name. If you can't have the app changed and/or redefine a
logical name, then you'll have to use one of the workarounds suggested
here.

AEF

AEF