Re: [Burp-users] How can I backup symlinks and empty directories?
Brought to you by:
grke
|
From: Graham K. <gr...@gr...> - 2015-03-03 21:34:10
|
My guess is that you are not using the client for lists/restores/verifies, and instead are assuming that the pseudo-mirror in the backup directories on the server side is an actual mirror (as you would get using, for example, rsync). Burp stores file data that it has backed up in the server storage directories. It doesn't make file system entries there if it does not need to. For example, an empty file doesn't need a file system entry. It just needs its meta data entered in the manifest file. A symlink doesn't need a file system entry on the server side, as it contains no file data. It just needs its meta data entered in the manifest file. A directory doesn't need a file system entry if it has no contents. It just needs its meta data entered in the manifest file. The same goes for permissions and ownerships. These are meta data that go in the manifest file. If you do what Ziirish suggests, you will see that the symlinks are listed. Use '-a L' instead of '-a l' to get a long list. To restore, use '-a r' instead of '-a l', and your symlinks and empty directories will come back. You might want to restore to a different directory with the '-d' option. On Wed, March 4, 2015 7:20 am, Benjamin Ziirish Sans wrote: > Hi, > > When you say symlink and empty dirs are not backed up, how do you notice > that? > > Are these files missing when you run a burp -a l -b <backup_number> ?Le 3 > mars 2015 17:28, Larsen <lar...@we...> a écrit : >> >> Hi, >> >> I am currently evaluating Burp and it looks very promising so far. >> Testing with Burp 1.3.48 from Debian Wheezy backports and with the >> latest >> 1.4.32 in a local VM. I would prefer to use the Debian version even >> when >> it´s older as long as I don´t miss out on functionality I need. >> >> In my test setup a directory containing some files and a symlink only >> stores the files but not the symlink in the backup. >> Though, I have read that symlinks should be stored so what am I doing >> wrong? Do you need the client config? >> >> Second problem is that empty directories are not stored. I assume this >> might be a general inconvenience as I know this behaviour from our >> current >> backup software. >> Is there a way to store empty directories with Burp? (without the >> workaround to create dummy files) >> >> >> Lars >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub >> for all >> things parallel software development, from weekly thought leadership >> blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> Burp-users mailing list >> Bur...@li... >> https://lists.sourceforge.net/lists/listinfo/burp-users > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for > all > things parallel software development, from weekly thought leadership blogs > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. > http://goparallel.sourceforge.net/_______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users > |