[BackupPC-users] Import pool or clients

2022-08-03 Thread backuppc--- via BackupPC-users
Hi,

I pulled a V3 pool off an old hard disk that I had wrongly assumed was broken. 
Now I would like to import as much data as possible into my current V4 
installation. 

Merging or importing pools does not seem to be an option, so I am wondering 
what could be done with the existing tools? I am thinking that I could create a 
config.pl that would allow me to run at least 
BackupPC_archiveHost/BackupPC_archiveStart so that I could extract backups into 
an archive. But then there is no facility to import archives, or did I overlook 
anything? Any other suggestions?

Fabian


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


Re: [BackupPC-users] Import pool or clients

2022-08-03 Thread backuppc--- via BackupPC-users
Guillermo Rozas wrote:
> 
> I think there is a V3_to_V4 conversion tool (look for it in the manual), but 
> it works on data that BacupPC already knows.

I believe BackupPC 4.x can still read V3 pools?

> Maybe you could try to create a V3 pool for a ficticious client, add the old 
> data by hand into the folder structure, and then convert it to V4, but it 
> could be risky to your current pool.

Adding data is the part for which I have not found any guide so far.

BR,
Fabian


> On Wed, Aug 3, 2022 at 2:31 PM backuppc--- via BackupPC-users 
>  wrote:
> > Hi,
> >  
> >  I pulled a V3 pool off an old hard disk that I had wrongly assumed was 
> > broken. Now I would like to import as much data as possible into my current 
> > V4 installation. 
> >  
> >  Merging or importing pools does not seem to be an option, so I am 
> > wondering what could be done with the existing tools? I am thinking that I 
> > could create a config.pl (http://config.pl) that would allow me to run at 
> > least BackupPC_archiveHost/BackupPC_archiveStart so that I could extract 
> > backups into an archive. But then there is no facility to import archives, 
> > or did I overlook anything? Any other suggestions?
> >  
> >  Fabian


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


Re: [BackupPC-users] Import pool or clients

2022-08-04 Thread backuppc--- via BackupPC-users
Hi,

Thanks everyone for asking for clarifications. I clearly haven't been thinking 
enough about what I want to achieve ultimately.

Current situation:

- HDD with a complete BackupPC 3.x data directory (called __TOPDIR__ by the 
documentation), size 1.8 TB, that has not been used in three years. It should 
contain the backup data of about 8 clients if memory serves me right.

- BackupPC 4.x installation on Debian 11 that I started using 3 years ago. It 
is currently using some 1.x TB on a 4 TB RAID. Also has about 8 clients, 6 of 
which are the same hosts as on the old HDD, 2 are new hosts.

- The old HDD has backup data of 2 hosts that don't exist anymore.

Goals:

- Originally, I was thinking it would be real nice if I just could merge the 
two data directories, so I would end up with:
-- 6 clients that are the same in both installations and where backups from the 
old HDD would complement the backup history.
-- 2 clients that have only been in the new installation.
-- 2 clients that have only been in the old installation, so the backup history 
up to three years ago would be imported.

Obviously, the above goal is not achievable with reasonable efforts. So now I 
am thinking that the one thing that I really care about is this:
- Extract the three year old data of the two clients that are not known to the 
new installation.

Right now I am thinking that it would probably be easiest if I set up a Debian 
10 VM, which comes with BackupPC 3.3.2, point that at the old data directory 
and use it to extract the data I want. Then I store that on one of my backed up 
clients so that it goes to the  BackupPC installation that I actually use.

BR,
Fabian


> Dave Sherohman via BackupPC-users  hat 
> am 04.08.2022 10:01 EEST geschrieben:
> 
>  
> On 8/4/22 07:44, backu...@kosowsky.org wrote:
> 
> > On Wed, Aug 3, 2022 at 2:31 PM backuppc--- via BackupPC-users <
> > backuppc-users@lists.sourceforge.net> wrote:
> >> I pulled a V3 pool off an old hard disk that I had wrongly assumed was
> >> broken. Now I would like to import as much data as possible into my current
> >> V4 installation.
> > - What are you trying to accomplish?
> > - Do you only have the pool files or do you also have the pc backup
> >directories?
> >
> > Really hard to answer the "how" if you don't explain the "what" and
> > "why" that you are seeking to accomplish...
> 
> I have to agree here.  You didn't mention the age of the backups on this 
> "old" disk, but importing it into your current pool strikes me as 
> something which would be carry a very high risk, while providing very 
> little reward.
> 
> If the backups on the "old" disk are from three days ago and taking new 
> backups of that data would take over a week to complete, then importing 
> them (or at least making them temporarily available to restore in some 
> fashion) seems reasonable; if they're from three years ago, then there's 
> considerably less potential benefit.


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


Re: [BackupPC-users] Import pool or clients

2022-08-04 Thread backuppc--- via BackupPC-users
Les Mikesell wrote:
>  
> why not just leave it at having the VM set
> up with a version of backuppc that works with the old drive mounted?
> Then on the odd chance that you need something from it, just fire up
> that VM again.

Right, I guess I should have mentioned that I don't trust that old HDD anymore. 
Plus keeping backups of two old clients that only exist in BackupPC has been a 
bad idea because if my backups get corrupted or deleted, I don't have the 
original data to fall back to anymore.

kosowsky.org wrote:
> 
> You could actually do it -- and I have done similar but it requires
> some effort and manual work... and hence there are risks of making mistakes..
> The process goes something like this.

That is amazing. I think I will try that. At least for the two old clients that 
don't exist in the new BackupPC installation, the process looks not entirely 
horrible.

BR,
Fabian


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


Re: [BackupPC-users] Is it possible to backup on a remote storage instead of local fs?

2023-01-18 Thread backuppc--- via BackupPC-users
Marian Velez wrote:

> The question then is very straightforward: is it possible to hack a
> way to use a local backuppc installation us usual, but using a remote
> backend storage for /pc/ and /pool/, especifically rsync.net or any
> average sshfs/sftp backend?

That is what the archive function is meant for:
https://backuppc.github.io/backuppc/BackupPC.html#Archive-functions

Unfortunately, the documentation is not exactly extensive and you need
a bit of scripting but you should be able to find enough information
now that you know what to search for.

> I'm well aware that pool and pc have hardlinked files

BackupPC 4.0 is not using hardlinks anymore unless you still have a V3
pool that hasn't been converted completely. See
https://backuppc.github.io/backuppc/BackupPC.html#BackupPC-4.0 for a
bit more detail.

Fabian


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


[BackupPC-users] Full backup number got reset?

2023-04-15 Thread backuppc--- via BackupPC-users
Hi,

I realized that I have one host where I have a backup history going
back only 47 days while on all other hosts I have roughly 2 years. I am
using the following settings for all hosts:

FullPeriod=6.97 
FillCycle=0
FullKeepCnt=[3, 0, 3, 0, 6]
FullKeepCntMin=3
FullAgeMax=720

That should give me app. 3*1 weeks + 3*4 weeks + 6*16 weeks = 111 weeks
(a bit over two years).

On that host, the backup summary says:

37  incrfilled  level 1 age 0.4 
36  incrno  level 1 age 1.4 
35  fullfilled  level 0 age 2.7
33  incrno  level 1 age 4.2 
32  incrno  level 1 age 5.4 
31  incrno  level 1 age 6.4 
30  incrno  level 1 age 7.4
29  incrno  level 1 age 8.4
27  fullyes level 0 age 10.7
21  fullyes level 0 age 18.3
0   fullyes level 0 age 39.7

On all other hosts the backup numbers (first column above) are in the
hundreds.

The host logs say the following:

2023-02-26 14:44:59 full backup started for directory /
2023-02-26 14:46:02 full backup started for directory /home 
2023-02-26 16:34:32 full backup started for directory /usr/local
2023-02-26 16:34:37 full backup started for directory /var 
2023-02-26 16:50:30 full backup started for directory /boot 
2023-02-26 16:50:42 full backup started for directory /mnt/data
2023-02-26 17:26:37 Removing prior partial backup #591 
2023-02-26 17:26:37 BackupPC_backupDelete: removing #591 
2023-02-26 17:26:37 BackupPC_backupDelete: Merge into backup 590
2023-02-26 17:27:32 BackupPC_refCountUpdate: host serv got 0 errors
(took 42 secs) 
2023-02-26 17:27:32 Finished BackupPC_backupDelete, status = 0 (running
time: 55 sec) 
2023-02-26 17:27:33 full backup 592 complete, 552150 files,
324702757005 bytes, 3 xferErrs (0 bad files, 0 bad shares, 3 other)

Then there are a couple of incremental backups and then this:

2023-03-05 20:21:53 full backup started for directory /
2023-03-05 20:22:25 full backup started for directory /home
2023-03-06 00:34:46 full backup started for directory /usr/local
2023-03-06 00:34:52 full backup started for directory /var
2023-03-06 00:48:25 full backup started for directory /boot
2023-03-06 00:48:34 full backup started for directory /mnt/data
2023-03-06 01:30:16 Aborting backup up after signal TERM

2023-03-06 17:00:00 Removing unfilled backup 590
2023-03-06 17:00:00 BackupPC_backupDelete: removing #590
2023-03-06 17:00:00 BackupPC_backupDelete: No prior backup for merge
2023-03-06 17:16:38 BackupPC_refCountUpdate: serv #599 inodeLast set
to 2422703 (was 2422241) 
2023-03-06 18:00:02 full backup started for directory / 
2023-03-06 18:07:17 full backup started for directory /home 
2023-03-07 08:30:01 Renaming /var/lib/backuppc/pc/serv/XferLOG.0.z ->
/var/lib/backuppc/pc/serv/XferLOG.0.z.tmp 
2023-03-07 08:30:04 full backup started for directory / 
2023-03-07 08:35:37 full backup started for directory /home 
2023-03-07 11:57:12 full backup started for directory /usr/local
2023-03-07 11:57:24 full backup started for directory /var 
2023-03-07 12:13:53 full backup started for directory /boot 
2023-03-07 12:14:08 full backup started for directory /mnt/data
2023-03-07 13:50:18 full backup 0 complete, 555670 files, 335367981491
bytes, 3 xferErrs (0 bad files, 0 bad shares, 3 other)

So apparently BackupPC did not take the "Aborting backup up after signal
TERM" very well. This host is the backup server, backing up itself. But
I don't quite understand why it decided to throw away the entire backup
history and start over from 0? And more importantly, is there something
I could do to prevent this from happening again, other than avoiding
shutdowns in the middle of a backup?

Fabian


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


Re: [BackupPC-users] Backup Share Content

2023-07-29 Thread backuppc--- via BackupPC-users
jbk wrote:

> I'm wondering if I need to add a "delete" argument to the 
> rsync line but am not sure of the consequences.

Yes, you do need to add --delete. See e.g. here for the default rsync
parameters:
https://github.com/backuppc/backuppc/blob/master/conf/config.pl#L1288

BR,
Fabian


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


Re: [BackupPC-users] PingCmd no longer having effect

2024-04-05 Thread backuppc--- via BackupPC-users
Ian via BackupPC-users  wrote:

> the PingCmd field

The documentation suggests to alter PingPath rather than PingCmd:
https://backuppc.github.io/backuppc/BackupPC.html#_conf_pingpath_

Fabian


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/