On 02/06 08:51 , Adam Pribyl wrote:
> On Mon, 5 Feb 2018, Carl W. Soderstrom wrote:
>
> > On 02/04 07:48 , Raoul Bhatia wrote:
> > > What's the issue with using LVM? Unless you need to reinitialize
> > > the whole fs, i.e. increase EXT4 inode count or switch to another
> > > fs, believe this is a
On Mon, 5 Feb 2018, Carl W. Soderstrom wrote:
On 02/04 07:48 , Raoul Bhatia wrote:
What's the issue with using LVM? Unless you need to reinitialize the whole
fs, i.e. increase EXT4 inode count or switch to another fs, believe this is
a perfect example of where LVM shines.
I'd like to insert
On 02/04 07:48 , Raoul Bhatia wrote:
> What's the issue with using LVM? Unless you need to reinitialize the whole
> fs, i.e. increase EXT4 inode count or switch to another fs, believe this is a
> perfect example of where LVM shines.
I'd like to insert a word of caution based on experience. I do
tar -C /var/lib/backuppc --one-filesystem --acls --xattrs -cf - . | tar
-C /copy -xvf -
How does this deal with hardlinks?
Just to answer this question - this is how GNU tar handles hard links:
https://www.gnu.org/software/tar/manual/html_node/hard-links.html
---
Markus A. Iturriaga Woelfel
On 02/03 10:30 , Les Mikesell wrote:
> On Sat, Feb 3, 2018 at 5:50 AM, Adam Pribyl wrote:
> > On Fri, 2 Feb 2018, Iturriaga Woelfel, Markus wrote:
> >
> >
> > I am running short on ideas how to copy this.
>
> If you are copying to an identical disk you can use dd on the raw
> devices.The syst
On February 3, 2018 9:27:40 PM UTC, Adam Pribyl wrote:
>On Sat, 3 Feb 2018, Les Mikesell wrote:
>
>> On Sat, Feb 3, 2018 at 5:50 AM, Adam Pribyl
>wrote:
>>> On Fri, 2 Feb 2018, Iturriaga Woelfel, Markus wrote:
>>>
>>>
>>> I am running short on ideas how to copy this.
>>
>> If you are copying to a
On Sat, 3 Feb 2018, Les Mikesell wrote:
On Sat, Feb 3, 2018 at 5:50 AM, Adam Pribyl wrote:
On Fri, 2 Feb 2018, Iturriaga Woelfel, Markus wrote:
I am running short on ideas how to copy this.
If you are copying to an identical disk you can use dd on the raw
devices.The system may be conf
On Sat, Feb 3, 2018 at 5:50 AM, Adam Pribyl wrote:
> On Fri, 2 Feb 2018, Iturriaga Woelfel, Markus wrote:
>
>
> I am running short on ideas how to copy this.
If you are copying to an identical disk you can use dd on the raw
devices.The system may be confused by the identical UUID's if you
hav
Hi,
Adam Pribyl wrote on 2018-02-02 08:09:47 +0100 [[BackupPC-users] Best way to
copy backuppc data]:
> What is to best way to copy the BackupPC data?
> [...]
> Still its taking somewhat too long... should I use a different method?
BackupPC_copyPool ... I'll send it to you on Mon
On 2/3/2018 2:50 PM, Adam Pribyl wrote:
On Fri, 2 Feb 2018, Iturriaga Woelfel, Markus wrote:
I tried the "dump | restore" way,
dump -0 -f - /var/lib/backuppc | restore -r -f -
after few minutes:
restore: cannot write to file /tmp//rstdir1517604355: No space left on
device
DUMP: Broken pipe
On Fri, 2 Feb 2018, Iturriaga Woelfel, Markus wrote:
I used rsync to copy data including hard links:
rsync -avxHAX --progress /var/lib/backuppc /copy
Because of all the hard links, rsync gets incredibly slow and uses a
huge amount of space in /tmp when trying to copy BackupPC (v.3)
Yes th
I used rsync to copy data including hard links:
rsync -avxHAX --progress /var/lib/backuppc /copy
Because of all the hard links, rsync gets incredibly slow and uses a huge
amount of space in /tmp when trying to copy BackupPC (v.3) directories. Since
it looks like you're doing this on the same
What is to best way to copy the BackupPC data?
I used rsync to copy data including hard links:
rsync -avxHAX --progress /var/lib/backuppc /copy
on 200G backup data - it is running for 4 days, transfered 188G of 200G
and now spending whole day on copying the cpool hashes (probably hard
links?).
13 matches
Mail list logo