vos_backup - Creates a backup volume for a single read/write volume
vos backup -id <volume name or ID> [-cell <cell name>] [-noauth] [-auth] [-localauth] [-encrypt [<yes|no>]] [-verbose] [-noresolve] [-config <configuration file>] [-help]
The vos backup command clones the indicated read/write volume to create a backup version. The backup version is a read-only snapshot of the read/write volume at the time the command is executed.
The backup version is stored on the same File Server and partition as the read/write volume.
The backup volume's name is the name of the read/write volume with the .backup extension appended.
Unlike .readonly sites created using the vos_addsite(1) command and populated with the vos_release(1) command,
the .backup version cannot be replicated and can only exist on the same partition as the read/write volume.
A .backup volume is useful for providing end users a self-service mechanism to recover accidentally deleted files and directories.
Use the fs_mkmount(1) command to create a mount point to the .backup volume where it can be accessed.
There are two common practices:
Add a mount point to .backup in the root directory of the read/write volume that the .backup is cloned from.
Common names for this mount point include OldFiles,
Backup,
and .backup.
Create a parallel directory hierarchy under the cell's root for .backup versions.
If the user home directory for user.smith is located at /afs/your-cell-name.com/user/smith then the .backup version is mounted at /afs/your-cell-name.com/backups/user/smith.
The .backup volume ID is allocated by the Location Service when the read/write volume is created with the vos_create(1) command.
If a backup version already exists when vos backup is executed,
the new clone replaces it.
To create a backup version of multiple volumes with a single command, use the vos_backupsys(1) command.
Specifies either the complete name or volume ID number of the source read/write volume.
Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1).
Assigns the unprivileged identity anonymous to the issuer.
Do not combine this flag with the -localauth flag.
For more details,
see vos(1).
Obtains an authentication token using the server encryption key with the highest key version number in the local /etc/yfs/server/KeyFileExt file. The resulting token never expires and has Super User privileges. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1).
Use the calling user's tokens from the kernel or as obtained using the active Kerberos ticket granting ticket to communicate with the Volume Server and Location Service. This is the default if neither -localauth nor -noauth is given.
Since this option is the default, it is usually not useful for running single command line operations. However, it can be useful when running commands via vos_interactive(1) or vos_source(1), since otherwise it would be impossible to switch from, for example, -localauth back to using regular tokens during a bulk operation.
Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear.
Enables or disables encrytion for the command so that the operation's results are not transmitted across the network in clear text.
Shows all servers as IP addresses instead of the reverse DNS lookup hostname.
-noresolve useful when troubleshooting no such volume and volume moved errors.
Set the location of the configuration file to be used. The default file is /etc/yfs/yfs-client.conf.
Prints the online help for this command. All other valid options are ignored.
The following message confirms that the command succeeded:
Created backup volume for I<volume name>
The following example creates a backup version of the volume user.smith.
% vos backup user.smith Created backup volume for user.smith
The issuer must be listed in the /etc/yfs/server/UserListExt file on the File Server specified by the -server argument and on each Location Server. If the -localauth flag is included, the issuer must instead be logged on to a server with an account capable of reading the /etc/yfs/server/KeyFileExt file.
fs_mkmount(1), vos(1), vos_addsite(1), vos_backupsys(1)
IBM Corporation 2000. http://www.ibm.com/ All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
"AFS" is a registered mark of International Business Machines Corporation, used under license. (USPTO Registration 1598389)
"OpenAFS" is a registered mark of International Business Machines Corporation. (USPTO Registration 4577045)
The "AuriStor" name, log 'S' brand mark, and icon are registered marks of AuriStor, Inc. (USPTO Registrations 4849419, 4849421, and 4928460) (EUIPO Registration 015539653).
"Your File System" is a registered mark of AuriStor, Inc. (USPTO Registrations 4801402 and 4849418).
"YFS" and "AuriStor File System" are trademarks of AuriStor, Inc.