> I'm just curious at what others are currently doing to back up huge
> amounts of data. eg. 2TB and onwards.
I'm using rdiff-backup and some scripting to backup ZFS
snapshots. Other than the use of the ZFS snapshots there's nothing
special about it. If your use case is suitable for rdiff-backup,
On Fri, Dec 19, 2008 at 6:04 PM, Wojciech Puchar <
woj...@wojtek.tensor.gdynia.pl> wrote:
> prohibitive)
>>> you don't require your backup target to have ZFS.
>>>
>>
>>
>> Quite wrong. If you want to use the zfs send | zfs receive along with zfs
>>
> quite right. i was NOT answering to z
prohibitive)
you don't require your backup target to have ZFS.
Quite wrong. If you want to use the zfs send | zfs receive along with zfs
quite right. i was NOT answering to zfs send/receive case!
___
freebsd-questions@freebsd.org mailing list
http
On Fri, Dec 19, 2008 at 1:52 PM, Wojciech Puchar <
woj...@wojtek.tensor.gdynia.pl> wrote:
> As ZFS is becoming more stable and approaching production ready, how
>> would one "Backup" ZFS? In terms of backing up to an external media or
>> storage rather than doing snapshots. In case the the server
I would suggest Bacula, a bit hard to config but very flexible
On Fri, 2008-12-19 at 12:52 +0100, Wojciech Puchar wrote:
> > As ZFS is becoming more stable and approaching production ready, how
> > would one "Backup" ZFS? In terms of backing up to an external media or
> > storage rather than doing
As ZFS is becoming more stable and approaching production ready, how
would one "Backup" ZFS? In terms of backing up to an external media or
storage rather than doing snapshots. In case the the server
spontaneously bursts into flames.
use tar it's filesystem independent if you have tape drives.
Hi,
As ZFS is becoming more stable and approaching production ready, how
would one "Backup" ZFS? In terms of backing up to an external media or
storage rather than doing snapshots. In case the the server
spontaneously bursts into flames.
Cost would be my main focus, so backing up to a HDD would b
