-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Paul,
sorry for the late reply. On 28.04.2015 Paul Slootman wrote: > This is done using branches: e.g. first create a foo-YYYYMMDD > image, then branch that to bar and baz. This can be useful if > foo, bar and baz are largely similar: common files will be > hardlinked amongst the branches (initially). Actually, I just went ahead and wrote the following into the conf-file s: image-default: foo/%Y/%m/foo_%Y%m%d-%H%M%S This works, as the folder with the backup is created in the right path . BUT: 1. the whole path has to exist, otherwise there is an error 2. I am not sure, what happens if new files get added on more than one branch, which could be hardlinked. As I am not sure what to put into the reference right now, I just commented it out. These are for clients with only minimal backup sizes, as just configs are transferred. So I do not mind the space. But it would be nice to know how this should/could work. Also, creating the directories in the path should not be impossible for dirvish. Regards, Johannes -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlVFFmUACgkQzi3gQ/xETbIQzACgkbLCEPtu1tvssAqTH44F6S/t 8tIAn3rWTrhahOCnn2T8K4nQIDDycgRr =+WT2 -----END PGP SIGNATURE----- _______________________________________________ Dirvish mailing list Dirvish@dirvish.org http://www.dirvish.org/mailman/listinfo/dirvish
