On 03/11/16 09:41, Nick Bright wrote:
> On 11/2/2016 5:29 PM, Adam Goryachev wrote:
>> Can you describe your "failed pool migrations"? ie, in what way did
>> they fail?
> In only one case did the transference get far enough to actually to run
> backuppc.
>
> Several attempts, using an intermediary physical disk, resulted in an
> unmountable partition or took too long and were aborted (attempting to
> use rsync).
Don't use rsync, or anything else. If you can't mount the partition,
then it's not a BackupPC related issue, and is probably caused by
corruption during the copy process.
> Another attempt, using dd, did result in a mountable partition, which I
> converted to ext4. Backuppc simply couldn't see any backups in the pool,
> and wouldn't successfully complete any new backups.
>
> I posted to the list about that a few days ago on 10/24, but no one
> responded.
Sorry, I don't respond to every list mail, and I guess nobody else did
either. It happens sometimes. Let's start again and see if we can help
you get this fixed.
>> What did you do (exact commands would help)? What happened?
> The most successful copying method (in terms of both speed and resulting
> in a mountable partition) is using DD over Netcat:
>
> dd bs=1M in=/dev/src | nc }--network--{ nc | dd bs=1M of=/dev/dst
>
> This runs reasonably fast, taking only about 8 to 10 hours to copy the data.
Yes, I'd highly suggest it as one of the best methods...
>
>> What are the error messages?
> There were no discernible errors, BackupPC simply didn't work - it
> showed no backups for any hosts, and when trying to complete the backup
> would fail and not log the error - almost like it couldn't write to the
> pool, but I re-verified permissions at least a dozen times. I've
> reinstalled the OS since then, so any logs are lost.
OK, so one step at a time... What FS is the source? When you say you
"converted it to ext4" what exactly did you do? Did you run a fsck
afterwards?
Next, manually check permissions for backuppc:
su -s /bin/bash backuppc
cd /var/lib/backuppc
touch test
rm test
That will verify that you can at least write there. If that works, then
you could do the following:
chown -R backuppc.backuppc /var/lib/backuppc to ensure all the contents
are also the correct permissions
If you still have an issue, then please let us know whatever information
you can find...
eg, ps auxf (to see what userid backuppc is running as)
ls -la /var/lib/backuppc
ls -la /var/lib/backuppc/pc
ls -la /var/lib/backuppc/pool
check /var/log/messages (syslog and daemon.log etc) for any related
backuppc startup logs/etc.
Regards,
Adam
--
Adam Goryachev
Website Managers
P: +61 2 8304 0000 [email protected]
F: +61 2 8304 0001 www.websitemanagers.com.au
--
Adam Goryachev Website Managers www.websitemanagers.com.au
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
