Backup Central

Rsnapthot is working fine, but when Windows users go to retrieve their Data files they are presented with the whole Linux directory tree and much drill down to the Linux folder holding their Data. Is there any way to reduce this?

Thank you very much for any suggestions.

Am 07.06.2012 17:23, schrieb OralDeckard:
Rsnapthot is working fine, but when Windows users go to retrieve their Data files they are presented with the whole Linux directory tree and much drill down to the Linux folder holding their Data. Is there any way to reduce this?

Thank you very much for any suggestions.

One way would be to remove "--relative" from rsync_long_args.

So if you have a rule

snapshot_root=/data/backup/
backup /var/www/ www/

* with --relative, /var/www/example.file will be backuped to
/data/backup/www/var/www/example.file
* without --relative, it will be backuped to /data/backup/www/example.file

So this means without the complete folder tree, just the content of the
folder to the backup destination.

Another way would be to offer a samba-share deeper into the folder tree?
Regards ROnny


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

One way would be to remove "--relative" from rsync_long_args.

So if you have a rule

snapshot_root=/data/backup/
backup /var/www/ www/

* with --relative, /var/www/example.file will be backuped to
/data/backup/www/var/www/example.file
* without --relative, it will be backuped to /data/backup/www/example.file

So this means without the complete folder tree, just the content of the
folder to the backup destination.

Another way would be to offer a samba-share deeper into the folder tree?
Regards ROnny

Thank you Ronny. But can you help me with that?

Earlier I found another thread that said the same thing, but always got errors when I tried it.

It sounds like there is a line with rsync_long_args that I should remove --relative from. But there is not. So I created it, with --relative removed, and got errors.

Here it is copied from my rsnapshot.conf file with the hash so I could keep it without it executing:
#rsync_long_args --numeric-ids --delete-excluded

Then I tried it again with --relative put back in. Still got errors and had to comment it out with the hash mark.

I found another example where it was added the the end of another line, and got errors again.

Can you tell me if it is supposed to be on a line by itself, or added to another line, or what is wrong with my line?

Thank you!

"
Another way would be to offer a samba-share deeper into the folder tree?
Regards ROnny "



Thank you Ronny!

I tried using a Samba share as the mount point and got this!

ERROR: snapshot_root smb://192.168.10.4/Full_Backups/
ERROR: /etc/rsnapshot.conf on line 204:
ERROR: backup /mnt/Test/ Drill_Down_to_Folders/ - snapshot_root needs to be \
defined before backup points

"
One way would be to remove "--relative" from rsync_long_args.
...
Regards, Ronny"

Thank you Ronny! I went back and reviewed the line you provided and found that I had left a space in it when I pasted it from your post. With all spaces gone and properly sporting tabs it works like a champ ! : )

Thank you very much !!!

"
One way would be to remove "--relative" from rsync_long_args.
...
Regards, Ronny"


One last note: After getting my long_args line right I managed to remove MOST of the tree, but STILL had one empty folder because I provided a destination, like this:
backup /mnt/DataDrive/Data/ /Full_Backup/

So I got:
/hourly.0/Full_Backup/Data

When I removed the destination /Full_Backup/ so it looked like this:
backup /mnt/DataDrive/Data/
I was scolded for not having a destination.

So I tired adding a tab after the line, so that it looks like this:
backup /mnt/DataDrive/Data/
(Yes, it looks exactly the same. The tab is invisible. )
and it worked perfectly, giving me a tree like this:
/hourly.0//Data

Now the directory tree is what I wanted, but the Data folder looks empty in the new snapshots, because it isn't hard linked to the data I gave up and backed up over the weekend, because the directory changed. Now all I have to do is delete all backups and start fresh.

: )

On Mon, Jun 18, 2012 at 11:32 AM, OralDeckard
<rsnaphshot-forum < at > backupcentral.com> wrote:
One last note:  After getting my long_args line right I managed
to remove MOST of the tree, but STILL had one empty folder
because I provided a destination, like this:
backup  /mnt/DataDrive/Data/     /Full_Backup/

So I got:
/hourly.0/Full_Backup/Data

When I removed the destination /Full_Backup/ so it looked like this:
backup  /mnt/DataDrive/Data/
I was scolded for not having a destination.

So I tired adding a tab after the line, so that it looks like this:
backup  /mnt/DataDrive/Data/
(Yes, it looks exactly the same.  The tab is invisible.  )
and it worked perfectly, giving me a tree like this:
/hourly.0//Data

Probably a cleaner way to accomplish what you're doing is to use "."
or "./" as the destination. Then you'll get /hourly.0/./Data or
something of that sort, and the backup line will be less prone to
accidental change.

-scott

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Am 18.06.2012 20:32, schrieb OralDeckard: "
One way would be to remove "--relative" from rsync_long_args.
...
Regards, Ronny"


One last note: After getting my long_args line right I managed to remove MOST of the tree, but STILL had one empty folder because I provided a destination, like this:
backup /mnt/DataDrive/Data/ /Full_Backup/

So I got:
/hourly.0/Full_Backup/Data

When I removed the destination /Full_Backup/ so it looked like this:
backup /mnt/DataDrive/Data/
I was scolded for not having a destination.

So I tired adding a tab after the line, so that it looks like this:
backup /mnt/DataDrive/Data/
(Yes, it looks exactly the same. The tab is invisible. )
and it worked perfectly, giving me a tree like this:
/hourly.0//Data
as i know rsync:

with
backup  /mnt/DataDrive/Data     /Data/
you get /path/to/snapshots/root/hourly.0/Data

but with
backup  /mnt/DataDrive/Data/     /Data/
you get /path/to/snapshots/root/hourly.0/Data/Data

the first one will backup the folder, as it doesn't end with a slash, while the second one will backup the content of the folder, because of the slash. It's a little confusing, but that's how rsync works.
Regards Ronny

"Probably a cleaner way to accomplish what you're doing is to use "."
or "./" as the destination. Then you'll get /hourly.0/./Data or
something of that sort, and the backup line will be less prone to
accidental change.

-scott "


Thank you Scott. The ./ worked as you said it would. And it is very preferable to an invisible character that may cause problems in the future.

"as i know rsync:

with
backup /mnt/DataDrive/Data /Data/
you get /path/to/snapshots/root/hourly.0/Data

but with
backup /mnt/DataDrive/Data/ /Data/
you get /path/to/snapshots/root/hourly.0/Data/Data "



Thank you Ronny. Yes, this is how rsync works, and I have now removed the trailing / so I can quit creating my own problem.