On Sun, 13 Dec 2009, Andy Feldman wrote: > You don't specify them directly. From the howto: > > "Dirvish determines what is a vault and what is not based on the presence of a > dirvish/ subdirectory containing a file named default.conf. For example, you > might have the following, with /snapshot defined as a bank and host-root > defined > as a vault. > > /snapshot/host-root/dirvish/default.conf > > There is no configuration option to define a vault. The presence of the > dirvish/default.conf structure implicitly makes it a vault. Without it, it's > just another unimportant directory."
Andy, I read that but missed the full implication. > In your example, if you wanted to call your two HDs jim and joe, and then > label their partitions with numbers, you could create the following > dirs/files: > > /media/hd0/backup/dirvish/server/jim1/dirvish/default.conf > /media/hd0/backup/dirvish/server/jim2/dirvish/default.conf > /media/hd0/backup/dirvish/server/jim3/dirvish/default.conf > /media/hd0/backup/dirvish/server/joe1/dirvish/default.conf > /media/hd0/backup/dirvish/server/joe2/dirvish/default.conf > [etc.] Ah, so! Repeating the dirvish/default.conf in _each_ vault is what I didn't appreciate. > In this case, you now automatically have vaults named jim1, jim2, jim3, joe1, > etc. Each of those default.conf files should have a different "tree:" > directive, > pointing the the root of the appropriate partition that you want to be > associated with that vault. > > To run the initial backup for each vault, you'd call something like: > dirvish --vault joe1 --init > > You don't need to specify the bank, because vault names should be unique. > Dirvish simply searches within each bank for a vault with the specified name. > > If you want them all to run when using dirvish-runall, then you'd put into > your master.conf: > > runall: > jim1 > jim2 > jim3 > joe1 > [etc.] This detail I did not get from my reading. Thank you. > Some other tips that you might have already figured out but might help: > If you don't need different setting per-vault, then you should leave lines > like > "xdev: 0" and "index: bz2" out of the vault-specific default.conf. The values > of those lines in master.conf will be applied to every vault. All I have in my > default.conf files is "tree: [/path/to/my/files]". > > Since it sounds like you're having each partition get its own vault (a > sensible choice), you'll probably want "xdev: 1" in master.conf to make sure > each one never crosses a filesystem boundary in case you have one mountpoint > inside another. This will also automatically prevent it from going into /proc > and similar special filesystems that you might not want included. > > Hope that helps, It certainly does! Your expanded explanation ought to be copied to the wiki as it clarifies all the points I found ambiguous or missing despite my reading. Very much appreciated, Andy! Rich _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
