Rsync + hard links backup strategy questions
I'm using several of Amazon's EC2 linux instances for a Deploy & Live MongoDB environment, and have been working on my backup strategy for a few days.
I've narrowed it down to using LVM snapshots to obtain a consistent data volume which I rsync to my backup server. I do this on an hourly basis from the backup server itself, using the following script: Code:
#!/bin/bash Code:
#!/bin/bash Finally, I run the following script once a week on a Saturday morning: Code:
#!/bin/bash Any input on this backup strategy? Any input on my scripts? Are they doing what I expect them to do? Just looking for general feedback.... Thanks! |
I would try the option --link-dest probably you can save a lot of time and space.
|
Thanks! But
Code:
cp -la current 1h |
No, I think you misunderstood. --link-dest will work file by file: if file changed it will be copied if file was not changed since the last backup it will be linked instead (that will save the time of copy and space too). You can give several --link-dest options to use several backups. For example: you will get every time a new backup, but the files not changed since the first backup will be stored only once.
Also you can try to read rsync forums there are a lot of discussion about how to use rsync for incremental backups and similar tasks, you may find usable ideas. |
All times are GMT -5. The time now is 07:36 PM. |