VOS_SHADOW(1) | AFS Command Reference | VOS_SHADOW(1) |
vos_shadow - Creates a shadow copy of a volume on a different server/partition
vos shadow
[-id] <volume name or ID on source>
[-fromserver] <machine name on source>
[-frompartition] <partition name on source>
[-toserver] <machine name on destination>
[-topartition] <partition name on destination>
[-toname <volume name on destination>]
[-toid <volume ID on destination>]
[-offline] [-readonly] [-live] [-incremental]
[-cell <cell name>]
[-noauth] [-localauth]
[-verbose] [-encrypt] [-noresolve]
[-config <config directory>]
[-help]
vos sh
[-id] <volume name or ID on source>
[-froms] <machine name on source>
[-fromp] <partition name on source>
[-tos] <machine name on destination>
[-top] <partition name on destination>
[-ton <volume name on destination>]
[-toi <volume ID on destination>]
[-o] [-r] [-l] [-in]
[-c <cell name>]
[-noa] [-lo] [-v] [-e] [-nor]
[-co <config directory>]
[-h]
The vos shadow command creates a shadow copy of a volume on a different partition or server.
A shadow volume is a copy of a volume that does not normally appear in the volume location database (VLDB). It is a primitive operation that is meant to be used in backup or disaster recovery situations.
This command is not used during normal OpenAFS administration and may have adverse effects on the VLDB if not used properly! This command should only be used by an expert.
Using this command on a volume when the source volume is not the same as parent volume used to create the shadow will leave the destination volume in a unknown state.
Running vos syncserv or vos syncvldb on a fileserver containing shadow volumes will not update the VLDB with the shadowed Read/Write volumes as long as the entries for the source volumes still exist. In a disaster recovery situation the VLDB entries for the corresponding source volumes need hence to be deleted first.
Currently, the maximum quota for a volume is 2 terabytes (2^41 bytes). Note that this only affects the volume's quota; a volume may grow much larger if the volume quota is disabled. However, volumes over 2 terabytes in size may be impractical to move, and may have their size incorrectly reported by some tools, such as fs_listquota(1).
This command has no output unless "-verbose" is specified or there is an error.
The issuer must be listed in the /etc/openafs/server/UserList file on the machines specified with the -toserver and -fromserver arguments and on each database server machine. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root".
vos(1), vos_backup(1), vos_copy(1), vos_move(1)
<http://www.openafs.org/pipermail/openafs-info/2005-July/018469.html> discusses motivation for the creation of this command.
<http://workshop.openafs.org/afsbpw06/talks/drh.scs.html> discusses one possible use for it.
Copyright 2008 Jason Edgecombe <jason@rampaginggeek.com>
This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS.
2021-01-14 | OpenAFS |