| Ted,
My first guess would be to create a save request with 2
include specs. For the include spec, where you want the /since=backup
qualifier, to modify it and set the agent qualifiers. You can specify
there whatever VMS Backup allows you to specify.
Admit I have tested it though, but there's a fair chance that it will work.
Hans van Sluis
|
|
>Another customer wants to be able to do incremental backups on selected
>directory trees. In other words they do something like...
>
> backup disk1:[tree1...],disk2:[tree2...]/since=backup ...
ABS can do schedules on specified files. This is the equivalent of
the full/incremental backup. Specify the disk/directory path you
want backed up and use one of the schedules (Weekly full/Daily incremental,
LOG-2, LOG-3). Specify the data movement type as selective. This will
then do what you need.
Example:
ABS SAVE/selective -
/interval=log_2 -
disk$user:[apps...]*.*;*/object_type=vms_files
>Also, can you enlighten on what the /incremental, /full, and /selective
>qualifiers do for saves? Are they like the backup qualifiers? Don't
>think so cause adding /incremental doesn't show up on the backup command.
>Its for restores anyway. Thanks.
Full - Performs a full backup on a disk (vms) or path (unix/nt). For
vms, you can think of it as adding the /IMAGE qualifier.
Selective - Does a backup on a set of files (vms/unix/nt).
Incremental - Does an incremental backup (will add
/since=last_good_backup_date_stored_in_abs_catalog for VMS Clients)
of a full or selective save. Note that if there isn't a base operation
(previous full to rely on), the incremental will do a full as it's
first save.
The data movement type (FULL, SELECTIVE, INCREMENTAL) determines which
backup qualifiers to use. It also determines what environment the backup
engine needs to operate. All this is done with templates. If you take a
look in the abs_templates directory you will find the templates that
are used for full/selective/incremental backups.
Directory ABS$ROOT:[TEMPLATES]
VMS_BACKUP-2.FULL_ARCHIVE_TEMPLATE;66
VMS_BACKUP-2.FULL_RESTORE_TEMPLATE;66
VMS_BACKUP-2.INCREMENTAL_ARCHIVE_TEMPLATE;66
VMS_BACKUP-2.INCREMENTAL_RESTORE_TEMPLATE;66
VMS_BACKUP-2.SELECTIVE_ARCHIVE_TEMPLATE;66
VMS_BACKUP-2.SELECTIVE_RESTORE_TEMPLATE;66
Take a look at these template files if you like. ***CAUTION*** if you
modify these files, unpredictable results may occur. The coordinator
will checksum this file before running a save request. If the checksum
does not match the internal ABS stored checksum, an error will be output
in the save request log file. We do not support ABS save requests
that have had the template files modified.
Hope this helps.
Kim
|