Or you can copy whole pool and move the selected pc/machines folders.
The unused files in the pool will be deleted by the backuppc_nightly
process and the space will be freed (on both servers).
Frantisek.
Dne 10.11.2015 v 18:59 Carl Wilhelm Soderstrom napsal(a):
> On 11/10 10:21 , Russell Poyne
On 11/10 10:21 , Russell Poyner wrote:
> I have a single BackupPC 3.3 backing up 110 machines. We are in the
> process of getting a second server and I'm wondering if it's possible to
> split the pool to move machines to the new server without losing their
> backup history.
Not really. By far t
I have a single BackupPC 3.3 backing up 110 machines. We are in the
process of getting a second server and I'm wondering if it's possible to
split the pool to move machines to the new server without losing their
backup history.
Thanks
Russ Poyner
---
Christian,
If you can resign yourself to staying on ext4, dumping and restoring the
filesystem may be your best bet. You can resize it after (and/or before if
needed) to the desired size.
If that's not possible, the second best solution is to stand up the new
server from scratch with no data
Hi Holger,
thank you very much for you detailed answer.
I launched restore through web interface (and it completed well without
issue).
During restore, I see this file:
$TopDir/pc/myserver/RestoreInfo.2
content is:
%RestoreReq = (
'fileList' => [
'/account/mail/account.it/username'
],
