| Author |
Message |
|
|
Post subject: backup question
 Posted: Aug 08, 2006 - 10:56 PM
|
|
Joined: Dec 07, 2005
Posts: 369
Location: Port Angeles, Wa. USA
|
|
I currently have as a backup command:
rdiff-backup --exclude-globbing-filelist /root/globbing-list.txt / /media/hda5/backups
and it works great, (but)
I was wondering if I added a --force and --remove-older-than argument preceding what I have would be a good idea to save disk space on my backup partition. And, also if it can be done with a single session rather than having to run rdiff-backup twice. I read conflicting information about this in the man pages & tutorials. For example, if I did:
rdiff-backup --force --remove-older-than 2D (or whatever) --exclude-globbing-filelist /root/globbing-list.txt / /media/hda5/backups
I would think that this would be faster than running rdiff-backup twice, and since I haven't any experience yet in writing scripts, I want to ask it here, rather than make a mistake. I thought rdiff-backup did incremental backups by default, copying only what has changed, rather than overwriting everything each time. My desire is to save time & space. Right now when I run my backup, it seems to take longer than I expected.
Thanks for any assistance--kurt |
_________________
illegitimati non carborundum
|
| |
|
|
|
 |
|
|
|
Post subject: RE: backup question
Posted: Aug 09, 2006 - 12:05 AM
|
|
Joined: Mar 12, 2005
Posts: 1005
|
|
rdiff backup does only backup what has changed each time, as long as you back up to the same directories each time.
It compares the contents of the rdiff-backup files with the new stuff and backs up changed files only, it's basically an incremental backup after the first full one.
I think best idea is probably do this for maybe 1 or 2 months, then start a new backup from scratch at that point, you can use a different directory, I use two, so I have several months of incremental backups, which is really convenient if you mess up at some point in the past.
no -force, no remove older than, keep it simple |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Post subject: RE: backup question
Posted: Aug 09, 2006 - 01:27 AM
|
|
Joined: Dec 07, 2005
Posts: 369
Location: Port Angeles, Wa. USA
|
|
OK h2 that helps a lot--thanks buddy
kurt |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
|
Post subject: RE: backup question
Posted: Aug 09, 2006 - 02:47 AM
|
|
Joined: Mar 12, 2005
Posts: 1005
|
|
Here is one that is useful for backing up your root directory from within the OS as it's runing:
rdiff-backup --exclude-sockets --exclude-globbing-filelist.....
--exclude-sockets makes it so rdiff-backup does not attempt to backup things that can't be backed up technically, sockets are something that active services create for themselves, like apache, mysql, and so on.
That really should be a default, since you can't back these up anyway, and if you don't exclude them, you get an error for each socket it tries to backup. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Post subject: RE: backup question
Posted: Aug 09, 2006 - 05:31 AM
|
|
Joined: Dec 07, 2005
Posts: 369
Location: Port Angeles, Wa. USA
|
|
VERY interesting--I just received this error:
SpecialFileError var/run/xdmctl/dmctl/socket Socket error: AF_UNIX path too long
I wonder if that has anything to do with the fact that I backed up while the OS was running. I know the path isn't too long in my backup command. I will try including that parameter & see what happens. |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
|
Post subject: RE: backup question
Posted: Aug 09, 2006 - 05:43 AM
|
|
Joined: Dec 07, 2005
Posts: 369
Location: Port Angeles, Wa. USA
|
|
HEEHEE--Guess what? No socket error messages this time after including --exclude-sockets
Yer a genius LOL
thanks again |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
