Jim Leonard wrote:
> dan wrote:
>> One of the biggest concerns with backuppc that is constantly discussed
>> on this list is syncing the backup data between two or more servers.
>> Simply reducing the file count by eliminating the hardlinks would allow
>> rsync to be used reliably and effective
dan wrote:
> Once the metadata and config moves to a database, so many things
> become very easy. A single backuppc server could handle many more
> concurrent backups because multple data storage devices can seperate IO
> and relieve the pressure on the IO system of the OS.
It sounds like you
dan wrote:
> One of the biggest concerns with backuppc that is constantly discussed
> on this list is syncing the backup data between two or more servers.
> Simply reducing the file count by eliminating the hardlinks would allow
> rsync to be used reliably and effectively.
It's almost as if
Hi
On Sun, 30 Aug 2009 01:30:25 -0400, "Jeffrey J. Kosowsky"
wrote:
> >well, under normal conditions (ie: unix), i would say rsyncd is
> >faster, as doesnt have the ssh overhead...
> But if bandwidth is your limitation (which it frequently is on any
> decent system) then rsync+ssh may
Hello,
I just installed backuppc successfully on my server
and give each position are saved in / var / lib / backuppc / pc /.
but I would be worth its data automatically burn to DVD or DVD-rewritable, ie
the hen I start the backup from the web interface of backuppc, the burning will
start a
dan wrote:
> The hybrid system also has many other advantages including:
> - Allows Backuppc to work on OS's/FS's that don't support Unix-type
> hardlinks such as Windoze
>
> Here is an important point. Using SQL to store metadata opens up the
> platforms backuppc can run on. Consi
dan wrote:
> I was just thinking about syncing servers. What if we just made an
> effort to sync the pool/cpool directory and the config files and then
> for the rest of the files in the pc/ directory run a script on the
> backuppc side to discover all the hard links. They push that list to
>
>
> The hybrid system also has many other advantages including:
> - Allows Backuppc to work on OS's/FS's that don't support Unix-type
> hardlinks such as Windoze
Here is an important point. Using SQL to store metadata opens up the
platforms backuppc can run on. Considering that no filesystem is
dan wrote at about 13:58:10 -0600 on Sunday, August 30, 2009:
> I was just thinking about syncing servers. What if we just made an effort
> to sync the pool/cpool directory and the config files and then for the rest
> of the files in the pc/ directory run a script on the backuppc side to
> dis
dan wrote at about 14:00:43 -0600 on Sunday, August 30, 2009:
> I personally think that using ssh compression is the better method. I say
> this because running rsync through ssh encrypts the data and compresses
> it(optionally). Unless you plan to run rsync in the clear then the built in
> c
I personally think that using ssh compression is the better method. I say
this because running rsync through ssh encrypts the data and compresses
it(optionally). Unless you plan to run rsync in the clear then the built in
compression isnt needed.
On Sat, Aug 29, 2009 at 11:36 PM, Jeffrey J. Kos
I was just thinking about syncing servers. What if we just made an effort
to sync the pool/cpool directory and the config files and then for the rest
of the files in the pc/ directory run a script on the backuppc side to
discover all the hard links. They push that list to the copy and have the
co
Les Mikesell wrote at about 14:26:47 -0500 on Friday, August 28, 2009:
> Jim Wilcoxson wrote:
> > Michael - I have a new LInux/FreeBSD backup program, HashBackup, in
> > beta that I believe will handle a large backuppc server. In tests, it
> > will backup a single directory with 15M (empty) fi
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's ne
14 matches
Mail list logo
