Welcome! » Log In » Create A New Profile

rsnapshot directory naming

Posted by Anonymous 
rsnapshot directory naming
June 20, 2005 12:58AM
Hi Joel,

Well, if try the method I mentioned earlier (and use seperate config
files and lock files), there's no reason more than one rsnapshot
instance can't be running. You would just have each snapshot_root be
something like /.snapshots/hostname/.

As for multiple simultaneous backups running from one instance of
rsnapshot, we may add this someday in the future. Under this (future)
scenario, rsnapshot would fork off x number of processes which would
each call rsync. If anyone wants to write this I would welcome their
contributions smiling smiley

Quote

My vote would [obviously] be for hostname/time. Any reason why multiple sessions couldn't be successfully run in parallel?
-Nathan

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. [ads.osdn.com]
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
[lists.sourceforge.net]
rsnapshot directory naming
June 15, 2005 02:22PM
I'm currently running rsnapshot in an few isolated setups, but I would
like to be able to pull multiple backups from different servers into the
same directory hierarchy, but be able to allocate disk space per server
(multiple mounts under snapshot_root). I can't seem to see a way to do
this, but I'm hoping I've just missed it. Is there a way to get
rsnapshot to create directories as below?

snapshot_root
|
+ server1
| |
| + daily.0
| + daily.1
| + daily.2
|
+ server2
| |
| + daily.0
| + daily.1
| + daily.2
|
+ server3
| |
| + daily.0
| + daily.1
| + daily.2

Is the best way to do this to have separate cron entries for each
machine, each referencing a different config file? Some other way? I
suppose with multiple config files and each server in it's own
directory, they could all run simultaneously with their own lock file.

--
Joel Johnson

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. [ads.osdn.com]
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
[lists.sourceforge.net]
rsnapshot directory naming
June 19, 2005 11:27PM
My vote would [obviously] be for hostname/time. Any reason why multiple sessions couldn't be successfully run in parallel?

Joel Johnson

-----Original Message-----
From: Nathan Rosenquist [mailto]
Sent: Fri 6/17/2005 8:30 PM
To: Joel Johnson
Cc: rsnapshot-discuss < at > lists.sourceforge.net
Subject: Re: [rsnapshot-discuss] rsnapshot directory naming

Hi Joel,

Others have expressed interest in this configuration as well. I wonder
how people would side if the issue was put to a vote (hostname/daily.0
vs daily.0/hostname).

Right now, the best method is probably seperate cron entries with
seperate config files. Anyone else on the list have anything else to add
to this?

Thanks,
-Nathan

Joel Johnson wrote:
Quote

I'm currently running rsnapshot in an few isolated setups, but I would
like to be able to pull multiple backups from different servers into the
same directory hierarchy, but be able to allocate disk space per server
(multiple mounts under snapshot_root). I can't seem to see a way to do
this, but I'm hoping I've just missed it. Is there a way to get
rsnapshot to create directories as below?

snapshot_root
|
+ server1
| |
| + daily.0
| + daily.1
| + daily.2
|
+ server2
| |
| + daily.0
| + daily.1
| + daily.2
|
+ server3
| |
| + daily.0
| + daily.1
| + daily.2

Is the best way to do this to have separate cron entries for each
machine, each referencing a different config file? Some other way? I
suppose with multiple config files and each server in it's own
directory, they could all run simultaneously with their own lock file.
rsnapshot directory naming
June 17, 2005 08:29PM
Hi Joel,

Others have expressed interest in this configuration as well. I wonder
how people would side if the issue was put to a vote (hostname/daily.0
vs daily.0/hostname).

Right now, the best method is probably seperate cron entries with
seperate config files. Anyone else on the list have anything else to add
to this?

Thanks,
-Nathan

Joel Johnson wrote:
Quote

I'm currently running rsnapshot in an few isolated setups, but I would
like to be able to pull multiple backups from different servers into the
same directory hierarchy, but be able to allocate disk space per server
(multiple mounts under snapshot_root). I can't seem to see a way to do
this, but I'm hoping I've just missed it. Is there a way to get
rsnapshot to create directories as below?

snapshot_root
|
+ server1
| |
| + daily.0
| + daily.1
| + daily.2
|
+ server2
| |
| + daily.0
| + daily.1
| + daily.2
|
+ server3
| |
| + daily.0
| + daily.1
| + daily.2

Is the best way to do this to have separate cron entries for each
machine, each referencing a different config file? Some other way? I
suppose with multiple config files and each server in it's own
directory, they could all run simultaneously with their own lock file.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. [ads.osdn.com]
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
[lists.sourceforge.net]
Sorry, only registered users may post in this forum.

Click here to login


Parse error: syntax error, unexpected 'GoogleAnalyticsObject' (T_STRING), expecting ']' in /tmp/tpl-lightweight_blue-footer-bc9d4c1f6d5e5fdfdcbff526fb7bae92.php-stage2 on line 6