Re: [OpenAFS] 'vos dump VOLUME.backup' locks VOLUME, not VOLUME.backup!
Turbo, One problem in your script is that you only "vos backup" the first time. The second time you try to dump a volume you do NOT "vos backup". That is a bug. You want to "vos backup" every time you run through the script! Otherwise you will never dump current data. The reason for my saying this is that the backup volume (created by vos backup or vos backupsys) is just a volume clone made at the time. As the user changes data, the backup volume will maintain the original state at the time of the backup. So, you want to freshen the backup volume before you dump it. Another bug in your script is that you shouldn't need the -server and -partition fields for the backup volume. You should be able to just use: vos dump "$volume".backup -file $BACKUPFILE This combination might be affecting you. -derek Turbo Fredriksson <[EMAIL PROTECTED]> writes: > > "Hartmut" == Hartmut Reuter <[EMAIL PROTECTED]> writes: > > >> It's a small volume (163Mb), but it locks for about 10 > >> minutes... Shouldn't the lock be ONLY for the number of > >> seconds it takes for 'vos backup' to finish? > > Hartmut> The being busy and locked ends when the command "vos > Hartmut> backup" has finished. > > Dang, that sucks! > > Hartmut> Are you sure you are dumping really the backup volume not > Hartmut> the RW-volume? > > Yes, have a look you self http://www.bayour.com/scripts/backup_afs.sh > > -- > 747 pits Kennedy jihad Panama quiche AK-47 radar Peking colonel > Serbian South Africa Marxist spy $400 million in gold bullion > [See http://www.aclu.org/echelonwatch/index.html for more about this] > ___ > OpenAFS-info mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-info -- Derek Atkins Computer and Internet Security Consultant [EMAIL PROTECTED] www.ihtfp.com ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] 'vos dump VOLUME.backup' locks VOLUME, not VOLUME.backup!
> "Hartmut" == Hartmut Reuter <[EMAIL PROTECTED]> writes: >> It's a small volume (163Mb), but it locks for about 10 >> minutes... Shouldn't the lock be ONLY for the number of >> seconds it takes for 'vos backup' to finish? Hartmut> The being busy and locked ends when the command "vos Hartmut> backup" has finished. Dang, that sucks! Hartmut> Are you sure you are dumping really the backup volume not Hartmut> the RW-volume? Yes, have a look you self http://www.bayour.com/scripts/backup_afs.sh -- 747 pits Kennedy jihad Panama quiche AK-47 radar Peking colonel Serbian South Africa Marxist spy $400 million in gold bullion [See http://www.aclu.org/echelonwatch/index.html for more about this] ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] 'vos dump VOLUME.backup' locks VOLUME, not VOLUME.backup!
Turbo Fredriksson wrote: > > > "Hartmut" == Hartmut Reuter <[EMAIL PROTECTED]> writes: > > Hartmut> In the first step namely cloning or recloning the backup > Hartmut> volume the RW volume is busy and cannot be accessed. > > It's a small volume (163Mb), but it locks for about 10 minutes... > Shouldn't the lock be ONLY for the number of seconds it takes for > 'vos backup' to finish? The being busy and locked ends when the command "vos backup" has finished. > > Hartmut> The second step namely dumping the backup volume lets the > Hartmut> RW-volume on-line, so access to the RW-volume should be > Hartmut> possible. > > That don't seem to happen on my system... OR, the lock while cloning > the volume isn't released when the volume is finished cloning... Are you sure you are dumping really the backup volume not the RW-volume? Hartmut - Hartmut Reuter e-mail [EMAIL PROTECTED] phone +49-89-3299-1328 RZG (Rechenzentrum Garching) fax +49-89-3299-1301 Computing Center of the Max-Planck-Gesellschaft (MPG) and the Institut fuer Plasmaphysik (IPP) - ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] 'vos dump VOLUME.backup' locks VOLUME, not VOLUME.backup!
> "Hartmut" == Hartmut Reuter <[EMAIL PROTECTED]> writes: Hartmut> In the first step namely cloning or recloning the backup Hartmut> volume the RW volume is busy and cannot be accessed. It's a small volume (163Mb), but it locks for about 10 minutes... Shouldn't the lock be ONLY for the number of seconds it takes for 'vos backup' to finish? Hartmut> The second step namely dumping the backup volume lets the Hartmut> RW-volume on-line, so access to the RW-volume should be Hartmut> possible. That don't seem to happen on my system... OR, the lock while cloning the volume isn't released when the volume is finished cloning... Hartmut> The lock of the volume during both operations Hartmut> (clone/reclone and dump) doesn't stop access to the RW Hartmut> volume. It is only necessary to prevent concurrent Hartmut> volserver activities on this volume group. Ah, so you can read (write?) on the volume, but it won't return until the dump is finished? Can this be surcumvented some how? When backing up the web volume, I won't be able to server documents for about 10-15 minutes! -- Iran South Africa Soviet DES cryptographic NORAD fissionable SDI spy Noriega bomb 747 radar supercomputer munitions [See http://www.aclu.org/echelonwatch/index.html for more about this] ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] 'vos dump VOLUME.backup' locks VOLUME, not VOLUME.backup!
Turbo Fredriksson wrote: > > I wrote a script to either backup a specific volume, or all > volumes. It create the backup volume 'VOLUME.backup', and mounts > that on 'MOUNTPOINT/OldFiles'. But it locks the VOLUME, not the > expected VOLUME.backup... And I can't seem to unlock it. > > 'vos unlock VOLUME' don't seem to work, and neither does 'vos unlockvldb'... > > The idea is to backup the user(s) volume, but still allowing rw access > to the volume (incase a user is logged in). This is something I got from > the 'manual', but it don't work as I had expected, what am I missing? > > It just released the lock, seems to be timed, took about 10 minutes or so... In the first step namely cloning or recloning the backup volume the RW volume is busy and cannot be accessed. The second step namely dumping the backup volume lets the RW-volume on-line, so access to the RW-volume should be possible. The lock of the volume during both operations (clone/reclone and dump) doesn't stop access to the RW volume. It is only necessary to prevent concurrent volserver activities on this volume group. Hartmut > -- > munitions Legion of Doom iodine North Korea Cocaine World Trade Center > fissionable bomb Khaddafi Cuba Serbian PLO explosion assassination > Waco, Texas > [See http://www.aclu.org/echelonwatch/index.html for more about this] > ___ > OpenAFS-info mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-info -- - Hartmut Reuter e-mail [EMAIL PROTECTED] phone +49-89-3299-1328 RZG (Rechenzentrum Garching) fax +49-89-3299-1301 Computing Center of the Max-Planck-Gesellschaft (MPG) and the Institut fuer Plasmaphysik (IPP) - ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] 'vos dump VOLUME.backup' locks VOLUME, not VOLUME.backup!
I wrote a script to either backup a specific volume, or all volumes. It create the backup volume 'VOLUME.backup', and mounts that on 'MOUNTPOINT/OldFiles'. But it locks the VOLUME, not the expected VOLUME.backup... And I can't seem to unlock it. 'vos unlock VOLUME' don't seem to work, and neither does 'vos unlockvldb'... The idea is to backup the user(s) volume, but still allowing rw access to the volume (incase a user is logged in). This is something I got from the 'manual', but it don't work as I had expected, what am I missing? It just released the lock, seems to be timed, took about 10 minutes or so... -- munitions Legion of Doom iodine North Korea Cocaine World Trade Center fissionable bomb Khaddafi Cuba Serbian PLO explosion assassination Waco, Texas [See http://www.aclu.org/echelonwatch/index.html for more about this] ___ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
