Hey Folks: This question pertains to Bacula's file/fileset locking mechanisms. Imagine a data set that you've defined to be be backed up via Bacula, across a network. The fileset is sufficiently large that it will take several hours to properly transmit and store on the storage server. What mechanisms have been put in place to prevent modification of the local data set while this transaction is underway? I can't seem to find reference to this in the dev/user documentation, so any insight or pointers to further information would be hugely appreciated.
Thanks so much for your time and help =) - John Quigley ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
