[OpenAFS] shadow volumes and 'vos syncvldb'

[Arne Wiebalck]

Not a creation time. But as they're meant for disaster recovery you
should be able to make them appear at some point, no?=20

And I (and the manpage) thought syncvldb is the way to do that.

Cheers,
 Arne

On Dec 3, 2012, at 9:45 PM, Steve Simmons <scs@umich.edu> wrote:

> Shadow volumes by their very definition never enter the vldb.
>=20
> Steve
>=20
> On Nov 15, 2012, at 12:26 PM, Arne Wiebalck wrote:
>=20
>> Dear all,
>>=20
>> If detecting shadow volumes, does 'vos syncvldb' really update VLDB entr=
ies=20
>> to point to the shadow location instead of the location of the R/W sourc=
e volume=20
>> as stated in the man page? (Some simple tests and a quick check in the c=
ode=20
>> seem to indicate that at least in 1.4 this is not the case).
>>=20
>> Would I need to run 'vos delentry' on all volumes before running 'vos sy=
ncvldb'=20
>> on the shadow server or is there something else I should do?
>>=20
>> I assume that in a disaster recovery situation where the source server i=
s not=20
>> reachable I probably need to delete the entries anyway as=20
>> - 'vos syncvldb' will need a macroscopic timeout for each volume on the=
=20
>> unreachable server, and
>> - it will not even update VLDB in the end if communication fails. Correc=
t?
>>=20
>> TIA,
>> Arne
>>=20
>> --
>> Arne Wiebalck
>> CERN IT/DSS
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> OpenAFS-info mailing list
>> OpenAFS-info@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20