Not a creation time. But as they're meant for disaster recovery you should be able to make them appear at some point, no?
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 <s...@umich.edu> wrote: > Shadow volumes by their very definition never enter the vldb. > > Steve > > On Nov 15, 2012, at 12:26 PM, Arne Wiebalck wrote: > >> Dear all, >> >> If detecting shadow volumes, does 'vos syncvldb' really update VLDB entries >> to point to the shadow location instead of the location of the R/W source >> volume >> as stated in the man page? (Some simple tests and a quick check in the code >> seem to indicate that at least in 1.4 this is not the case). >> >> Would I need to run 'vos delentry' on all volumes before running 'vos >> syncvldb' >> on the shadow server or is there something else I should do? >> >> I assume that in a disaster recovery situation where the source server is >> not >> reachable I probably need to delete the entries anyway as >> - 'vos syncvldb' will need a macroscopic timeout for each volume on the >> unreachable server, and >> - it will not even update VLDB in the end if communication fails. Correct? >> >> TIA, >> Arne >> >> -- >> Arne Wiebalck >> CERN IT/DSS >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> OpenAFS-info mailing list >> OpenAFS-info@openafs.org >> https://lists.openafs.org/mailman/listinfo/openafs-info > _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
