not a big secret of my hostnames :)
./BackupPC_migrateV3toV4 -a -m
BackupPC_migrateV3toV4: backup 0 for host alcpr already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host alcpr already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host alcsvr1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host alcsvr1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host alcsvr2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host alcsvr2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host alcsvr3 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host alcsvr3 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host alcsvr4 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host alcsvr4 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host backuppc already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host bamljp1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 64 for host bamljp1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host bamljp2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host bamljp2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 56 for host bamljp4 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 112 for host bamljp4 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host bamllse1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host bamllse1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host bamllse2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host bamllse2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host cmbsvr1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 107 for host cmbsvr1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host cmbsvr3 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 42 for host cmbsvr3 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 237 for host empire already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 286 for host empire already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 237 for host gwdc2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 279 for host gwdc2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 232 for host gwhk1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 288 for host gwhk1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host hksvr1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host hksvr1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host hksvr2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 105 for host hksvr2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host ltspc128 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 69 for host ltspc128 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 174 for host ltspc129 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 271 for host ltspc129 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 182 for host ltspc133 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 231 for host ltspc133 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 71 for host ltspc140 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 113 for host ltspc140 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host ltspc145 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 70 for host ltspc145 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 227 for host ltspc161 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 276 for host ltspc161 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host ltspc164 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 42 for host ltspc164 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 34 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 41 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 44 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 45 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 46 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 47 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 48 for host ltspc166 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 228 for host ltspc169 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 277 for host ltspc169 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 110 for host ltspc175 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 180 for host ltspc175 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 244 for host monitor already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 286 for host monitor already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host nodezero already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 48 for host nodezero already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host throne already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 106 for host throne already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host trade1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 106 for host trade1 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host trade2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 111 for host trade2 already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 0 for host vfsm already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 104 for host vfsm already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 241 for host warcraft already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: backup 290 for host warcraft already has a refCnt
directory; skipping this backup
BackupPC_migrateV3toV4: got 0 errors
On 2 June 2017 at 19:05, Alexander Moisseev <mois...@mezonplus.ru> wrote:
> On 6/2/2017 10:19 AM, Alexey Safonov wrote:
>
>> Here is mu output
>>
>>
>> General Server Information
>>
>> * The servers PID is 35143, on host backuppc.hk.kkc.net <
>> http://backuppc.hk.kkc.net>, version 4.1.2, started at 5/25 15:05.
>> * This status was generated at 6/2 15:17.
>> * The configuration was last loaded at 5/25 15:05.
>> * PCs will be next queued at 6/2 19:00.
>> * Other info:
>> o 0 pending backup requests from last scheduled wakeup,
>> o 0 pending user backup requests,
>> o 0 pending command requests,
>> o Pool is 99.27+6.12GiB comprising 1216909+165932 files and
>> 16512+4369 directories (as of 6/2 01:20),
>> o Pool hashing gives 0+23 repeated files with longest chain 0+5,
>> o Nightly cleanup removed 179717+0 files of size 11.25+0.00GiB
>> (around 6/2 01:20),
>> o Pool file system was recently at 4% (6/2 15:16), today's max is
>> 4% (6/2 01:00) and yesterday's max was 5%.
>>
>>
>> On 2 June 2017 at 15:17, Alexey Safonov <asafo...@kokomocapital.com
>> <mailto:asafo...@kokomocapital.com>> wrote:
>>
>> but how it's possible ? i run script with -a option
>> script ends with no error
>>
>> I guess something went wrong with migration. Your statistics clearly
> indicates there are files in v3 pool and the latest nightly cleanup removed
> none of them. It looks like these files still used by v3 backups.
>
> `BackupPC_migrateV3toV4 -a -m` should show leftover v3 backups.
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
