Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing OSS Files
Open System Services Management and Operations Guide—527191-002
6-17
Backing Up User Files
-v
writes archive member pathnames to the standard error file.
-f archive_name
specifies the pathname of the output archive, overriding the default standard output
file. Guardian tape devices can be specified with the /G naming convention (for
example, /G/tape).
If the -a flag is also specified and a disk archive medium is used, files are
appended to the end of the archive.
-b blocksize
records an archive as a series of fixed-size blocks to make physical output more
efficient. Blocking is automatically determined on input.
The blocksize argument can have values no greater than 32,256 for disk
archives and 28,672 for tape archives.
The blocksize argument can be specified as a series of digits (0 through 9)
followed by a flag letter, “b” or “k”. If “b” is used, the blocksize value is multiplied
by 512. If “k” is used, the blocksize value is multiplied by 1024. For example,
“10b” translates to a blocksize value of 5120 bytes (10 * 512).
The default blocksize value for cpio archive format is 10b (5120 bytes). The
last group of blocks is always at the full size.
The default blocksize value for ustar archive format is 20b (10240 bytes). You
specify the blocksize argument as a multiple of 512 bytes.
.
specifies the current directory.
Backing Up OSS File Hierarchies Using Backup and
Restore 2.0
You can specify part or all of multiple directory hierarchies and selectively backup files
from within them using Backup and Restore 2.0. For example, if you enter the following
at a Backup and Restore 2.0 BR> prompt:
BACKUP =MYTAPE, OSS ((/user/bin, /home/sv/myfile,
/usr/local/bin) WHERE (EOF > 20000 AND OWNER = dev.user2),
(/etc/rc, /var/x) WHERE MODTIME AFTER JAN 17 1999),
TAPEDISPOSITION NOREWIND, VERIFYTAPE ON;