> The reason for this, I supposed, is that this
> would require SDs to transfer data over the wire between themselves
> while normally data only flows between FDs and SDs.
>
That is correct. Storage Daemons do not currently communicate.
John
---
On Mon, 10 Oct 2011 14:13:26 +0200
René Moser wrote:
[...]
> SD = Storage Device, I guess. I can not migrate between a file storage
> device, to a tape storage device?
[...]
SD stands for Storage Daemon--it's a program which manages one or more
storage devices available on the host a particular
On Fri, 2011-09-30 at 18:08 -0400, Dan Langille wrote:
> On Sep 27, 2011, at 12:42 PM, René Moser wrote:
>
> > On Tue, 2011-09-27 at 16:51 +0100, Gavin McCullagh wrote:
> >
> >> It sounds like what you're looking for could be implemented as:
> >>
> >> 1. A normal Full/Differential/Incremental j
On Sep 27, 2011, at 12:42 PM, René Moser wrote:
> On Tue, 2011-09-27 at 16:51 +0100, Gavin McCullagh wrote:
>
>> It sounds like what you're looking for could be implemented as:
>>
>> 1. A normal Full/Differential/Incremental job to a disk-based storage
>> device to happen during the day.
>> 2.
Hi,
On Tue, 27 Sep 2011, René Moser wrote:
> Okay, it is not _really_ during day it is more like backups over night
> to disk and backup to tape should be finished in the morning. But this
> is just a detail. We did not have (yet) really (big) problems about
> consistency. But as you say these sy
On Tue, 27 Sep 2011, René Moser wrote:
> On Tue, 2011-09-27 at 16:51 +0100, Gavin McCullagh wrote:
> > 2. It is apparently not possible to backup all 100 hosts straight to
> >tape, so you write them to disk first. Why is that? It sounds like
> >you're manually doing "Spooling", which Ba
On Tue, 2011-09-27 at 16:51 +0100, Gavin McCullagh wrote:
> 2. It is apparently not possible to backup all 100 hosts straight to
>tape, so you write them to disk first. Why is that? It sounds like
>you're manually doing "Spooling", which Bacula has transparent support
>for. You coul
On Tue, 2011-09-27 at 16:51 +0100, Gavin McCullagh wrote:
> It sounds like what you're looking for could be implemented as:
>
> 1. A normal Full/Differential/Incremental job to a disk-based storage
>device to happen during the day.
> 2. A Migrate job to tape from disk to happen during the nig
On Tue, 2011-09-27 at 16:41 +0100, Alan Brown wrote:
> > We are currently using a proprietary backup solution,
>
> Which proprietary backup system?
BRU Backup Server
> > We have some >100 hosts to backup up. The current "work flow" is like:
>
> Are these hosts PCs? What do they do? How much c
On Tue, 27 Sep 2011, René Moser wrote:
> We are currently using a proprietary backup solution, and we evaluation
> bacula to replace it.
>
> We have some >100 hosts to backup up. The current "work flow" is like:
>
> 1. backup server backups host files over working time to a disk volume
> on ba
René Moser wrote:
> Hi
>
> We are currently using a proprietary backup solution,
Which proprietary backup system?
> and we evaluation
> bacula to replace it.
>
> We have some >100 hosts to backup up. The current "work flow" is like:
Are these hosts PCs? What do they do? How much changes on t
Hi
We are currently using a proprietary backup solution, and we evaluation
bacula to replace it.
We have some >100 hosts to backup up. The current "work flow" is like:
1. backup server backups host files over working time to a disk volume
on backup server.
2. During night, the disk volume is
12 matches
Mail list logo
