Forum Discussion

rlbcandw's avatar
rlbcandw
Level 3
14 years ago

Excluding a directory in OpenVMS

I need assistance with excluding the following directory and folder from an OpenVMS backup:  $1$DGA200:[USERS.YINK].  Currently I have the following selection in the policy for backup: $1$dga200:[000000...]/IGNORE=(NOBACKUP,INTERLOCK).

  • This is what worked:

    Make reference to a exclude file in the clients policy backup selections
    and have the exclude file on the client populated with exclusions.

    policy backup selections
    $1$dga200:[000000...]*.*;*/exclude=@NBU$DIR:exclude.lis/ignore=(interlock,nobackup)

    on client cub, make file NBU$DIR:exclude.lis
    and put in it $1$dga200:[users.yink...]*.*;*

7 Replies

  • Do you have the OpenVMS admin guide?

    You can download the pdf for your version here: ftp://ftp.emea.veritas.com/pub/support/Products/NetBackup_OpenVMS/

    I have just downloaded NB_VMS_6.5_PDF.zip

    p. 54 explains how to exclude under "The Backup /EXCLUDE qualifier" heading...

  • I have the OpenVMS admin guide and followed the instructions but it did not exclude that directory.  Here is the line I have in backup selections:  $1$dga200:[000000...]/IGNORE=(NOBACKUP,INTERLOCK) /EXCLUDE=$1$dga200:[USERS.YINK]

  • I am no OpenVMS expert blush... All I can suggest is that you remove the space before /EXCLUDE.

    If I look at the examples on p.8, there are no spaces.

    Also, looking at the same examples e.g:

    DKB100:/EXCLUDE=([ABC...]*.*;*,[XYZ...]*.*;*)

    try this:

    $1$dga200:[000000...]/IGNORE=(NOBACKUP,INTERLOCK)/EXCLUDE=[USERS.YINK]

  • If you change the switch to include a wildcard file specifier /EXCLUDE=[USERS.YINK]*.*;* this should work as expected. If not you've found a bug.

    Also a word of warning about INGORE=INTERLOCK from the online help:

    BACKUP

      /IGNORE
            /IGNORE=option
     
                                        NOTE
            File system interlocks are expressly designed to prevent
            data corruptions, and to allow applications to detect and
            report data access conflicts.
            Use of the INTERLOCK keyword overrides these file data
            integrity interlocks. The data that BACKUP subsequently
            transfers can then contain corrupted data for open files.
     
            Also, all cases in which these data corruptions can occur
            in the data that BACKUP transfers are not reliably reported
            to you; in other words, silent data corruptions are possible
            within the transferred data.
     
     
    Hth
     
  • The syntax is actually the same as what you would use for VMSbackup.

    Sign on to a VMS sytem and enter:

    $ HELP BACKUP/EXCLUDE

    I've been using the VMS client for over 7 years (and VMS for over 28 years) and the NetBackup client has been working fine although I don't think I've used the EXCLUDE qualifier yet.

  • Thank you Marianne, Brodders and Ed I am trying the backup again with the changes.

  • This is what worked:

    Make reference to a exclude file in the clients policy backup selections
    and have the exclude file on the client populated with exclusions.

    policy backup selections
    $1$dga200:[000000...]*.*;*/exclude=@NBU$DIR:exclude.lis/ignore=(interlock,nobackup)

    on client cub, make file NBU$DIR:exclude.lis
    and put in it $1$dga200:[users.yink...]*.*;*