Re: [BackupPC-users] logout button

[Alexey Safonov via BackupPC-users]

we can add new link with

*$Conf{CgiNavBarLinks} and point it to clear sessionthanks,Alex*

On Wed, 19 Dec 2018 at 16:24, Daniel Berteaud 
wrote:

> Le 19/12/2018 à 08:39, Alexey Safonov via BackupPC-users a écrit :
>
> Hi guys
>
> is it possible to add logout button for backuppc interface?
>
>
> I don't think so, as BackupPC doesn't handle authentication itself (it
> just trust the webserver to do it). All that could be done is to add a
> button to redirect on a specific URL, which could be catched by your WebSSO
> system if you have one, and close the SSO session.
>
>
> ++
>
> --
>
> [image: Logo FWS]
> *Daniel Berteaud*
>
> FIREWALL-SERVICES SAS.
> Société de Services en Logiciels Libres
> Tel : 05 56 64 15 32
> Matrix: @dani:fws.fr
> *www.firewall-services.com <http://www.firewall-services.com>*
> ___
> 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/
>
___
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/

[BackupPC-users] logout button

[Alexey Safonov via BackupPC-users]

Hi guys

is it possible to add logout button for backuppc interface?

Alex


___
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/

[BackupPC-users] rsync backup no file in web interface

[Alexey Safonov]

Hi, i've recently add some extra directories to backup strategy

after backup i can't see them in web interface. according to log i can see
that rsync  successfully backup them. i also can see that folder in my nfs
share

but not in web interface

Alex
--
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/

[BackupPC-users] backupfilesonly

[Alexey Safonov]

Hi, Craig.

do you think it's a good idea to trim spaces on right side from file lists? :)


Alex

--
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/

[BackupPC-users] backup blackout question

[Alexey Safonov]

I want some of my servers to be backed up during weekends only. is it
correct synatax to dibasble weekdays backups ?

$Conf{BlackoutPeriods} = [
{
hourBegin =>  0.0,
hourEnd   => 23.5,
weekDays  => [1, 2, 3, 4, 5],
}

Alex

--
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/

[BackupPC-users] schedule templates

[Alexey Safonov]

Hi, Craig.

do you think it's a good idea if you can create schedules template?
with different blackout periods and/or available backup time?

reason is to apply to different group of servers in different timezones

Alex

--
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/

Re: [BackupPC-users] V4, Set port for SSH

[Alexey Safonov]

here is mine
$Conf{RsyncSshArgs} = [
  '-e',
  '$sshPath -q -x -l rbackup'
];


so try
$Conf{RsyncSshArgs} = [
  '-e',
  '$sshPath -p 2022'
];


On 11 August 2017 at 15:21, Pelle Hanses  wrote:
> Thanks, I guessed it. Unfortunately, I do not know what to enter there. I
> have tried many different syntax but nothing works. I guess that "-p 2022"
> should be the correct one but it does not work.
> The contents of config-fieln will then be:
> $ Conf {RsyncSshArgs} = [
>'-p 2022'
> ];
>
> I get the error code:
>
> rsync_bpc: -p 2022: unknown option
>
>
> /Pelle
>
>
> Den 2017-08-11 kl. 07:03, skrev Craig Barratt via BackupPC-users:
>
> Pelle,
>
> In 4.x you should use $Conf{RsyncSshArgs}.
>
> Craig
>
> On Thu, Aug 10, 2017 at 11:51 AM, Pelle Hanses  wrote:
>>
>> Hi,
>> I have upgraded to V4 (4.1.2) and everything seems to work except from
>> setting SSH port. How can I set the port SSH will connect to?
>> In version 3 I used "$Conf{RsyncClientCmd} = '$sshPath -q -x -l backuppc
>> -p 2022 $host sudo $rsyncPath $argList+';" but I can't find out how to set
>> -p 2022 in the new settings.
>>
>>
>>
>> /Pelle
>>
>>
>>
>> 
>>
>> Pelle Hanses
>> Sweden
>> E-post: pe...@masendata.com
>>
>>
>>
>> --
>> 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/
>
>
> --
>
> 
>
> Pelle Hanses
> Masen Data
> Bällsta 130, 832 93 Frösön
> Tel: +46 63-12 64 83, Mobil: +46 731-83 61 90
> E-post: pe...@masendata.com
>
>
> --
> 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/

Re: [BackupPC-users] Backing up the BackupPC pool

[Alexey Safonov]

you can use for example FreeNAS (ZFS based) which can sync snapshots.

On 10 August 2017 at 06:38, B  wrote:
> On Wed, 9 Aug 2017 16:29:49 -0600
> Ray Frush  wrote:
>
>> A snapshot of the BackupPC Filesystem does not protect from gross
>> hardware failure of the storage that destroys both the data and the
>> snapshots.
>
> I think he meant making a snapshot then convey it to he's 2nd site.
>
> JY
>
> --
> 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/

Re: [BackupPC-users] status graph

[Alexey Safonov]

Hi, Craig

finally i was able to detect and find hardlinks. it's not under pool,
but in archive folder (may be i was playing with archive
functionalty). What is correct way to clean archive?

Alex

On 25 July 2017 at 12:22, Alexey Safonov  wrote:
> Here is my findings. i can find some files in cpool, but not in pool
>
> first example:
> [root@backuppc cpool]# ls -li f/f/f/fff034be393e4f6c2007013e0e20812f
> 694558 -rw-r-. 11 nobody nobody 975 Jun 15  2016
> f/f/f/fff034be393e4f6c2007013e0e20812f
>
> [root@backuppc pc]# find . -type f -inum 694558 -print
> return nothing
>
> second example:
>
> [root@backuppc cpool]# ls -li f/f/f/fff33b3ff92969f322863a4363a15f7a
> 71819 -rw-r-. 3 nobody nobody 199706 Jun 16  2016
> f/f/f/fff33b3ff92969f322863a4363a15f7a
> [root@backuppc cpool]# cd -
> /mnt/backuppc/pc
> [root@backuppc pc]# find . -type f -inum 71819 -print
>
> what does it mean  ?
>
> Alex
>
>
> On 19 June 2017 at 01:54, Craig Barratt via BackupPC-users
>  wrote:
>> Without any more information, I can't suggest additional steps.
>>
>> So it's probably fine to just leave it as is.
>>
>> Craig
>>
>> On Thu, Jun 15, 2017 at 9:43 PM, Alexey Safonov 
>> wrote:
>>>
>>> Still can't find what is using V3 pool
>>>
>>> should i leave it as is ? or better to find solution and delete unused
>>> data?
>>>
>>> On 11 June 2017 at 13:00, Craig Barratt via BackupPC-users
>>>  wrote:
>>> > Alex,
>>> >
>>> > First you should check to see what's left in the v3 cpool, eg:
>>> >
>>> > cd /data/BackupPC/cpool
>>> > ls -lR [0-9a-f]
>>> > du -s ?/?/?
>>> >
>>> > Next you could pick a file and find its inode number and number of
>>> > links:
>>> >
>>> > ls -li 0/1/2/1234567890abcdef
>>> >
>>> > Are there any files with >1 links?  If so, you could try to find where
>>> > else
>>> > that file is hardlinked to, eg:
>>> >
>>> > cd /data/BackupPC/pc
>>> > find . -type f -inum inodeNumber -print
>>> >
>>> > Craig
>>> >
>>> > On Tue, Jun 6, 2017 at 6:20 PM, Alexey Safonov
>>> > 
>>> > wrote:
>>> >>
>>> >> My $Conf{PoolSizeNightlyUpdatePeriod} = 16; is 4
>>> >>
>>> >> and i already wait more than 2 weeks.
>>> >>
>>> >> i was trying to convert pool manually. process finished without any
>>> >> error.
>>> >> and i try nightly maintenance several times manually
>>> >>
>>> >> Alex
>>> >>
>>> >> On 6 June 2017 at 17:02, Alexander Moisseev via BackupPC-users
>>> >>  wrote:
>>> >>>
>>> >>> On 6/6/2017 4:24 AM, Alexey Safonov wrote:
>>> >>>>
>>> >>>> Alexander, Craig
>>> >>>>
>>> >>>> any ideas what can i check and how to find this V3 pool?
>>> >>>>
>>> >>> I don't know how exactly do this. I guess you need to find files with
>>> >>> hardlink count > 1 in the pool and cpool directories.
>>> >>>
>>> >>> Probably it's not necessary, you just need to wait.
>>> >>>
>>> >>> Make sure "$Conf{PoolV3Enabled} = 1;" until the last file deleted from
>>> >>> v3
>>> >>> pool.
>>> >>> By default "$Conf{PoolSizeNightlyUpdatePeriod} = 16;". This means you
>>> >>> need to wait 16 days while v3 pool will be emptied.
>>> >>>
>>> >>> See details in BackupPC_migrateV3toV4 section of
>>> >>>
>>> >>> https://backuppc.github.io/backuppc/BackupPC.html#Other-Command-Line-Utilities
>>> >>> BTW, This section says "You could do this manually". Craig, how'd you
>>> >>> suggest to find v3 files in pool and cpool?
>>> >>>
>>> >>> Since your pool is not big you can set
>>> >>> $Conf{PoolSizeNightlyUpdatePeriod}
>>> >>> = 1;
>>> >>>
>>> >>> Also it's not necessary to wait next BackupPC_nightly run. You can
>>> >>> start
>>> >>> it at any time.
>>> >>> # su -m backuppc -c 'BackupPC_serverMesg Backu

Re: [BackupPC-users] status graph

[Alexey Safonov]

Here is my findings. i can find some files in cpool, but not in pool

first example:
[root@backuppc cpool]# ls -li f/f/f/fff034be393e4f6c2007013e0e20812f
694558 -rw-r-. 11 nobody nobody 975 Jun 15  2016
f/f/f/fff034be393e4f6c2007013e0e20812f

[root@backuppc pc]# find . -type f -inum 694558 -print
return nothing

second example:

[root@backuppc cpool]# ls -li f/f/f/fff33b3ff92969f322863a4363a15f7a
71819 -rw-r-. 3 nobody nobody 199706 Jun 16  2016
f/f/f/fff33b3ff92969f322863a4363a15f7a
[root@backuppc cpool]# cd -
/mnt/backuppc/pc
[root@backuppc pc]# find . -type f -inum 71819 -print

what does it mean  ?

Alex


On 19 June 2017 at 01:54, Craig Barratt via BackupPC-users
 wrote:
> Without any more information, I can't suggest additional steps.
>
> So it's probably fine to just leave it as is.
>
> Craig
>
> On Thu, Jun 15, 2017 at 9:43 PM, Alexey Safonov 
> wrote:
>>
>> Still can't find what is using V3 pool
>>
>> should i leave it as is ? or better to find solution and delete unused
>> data?
>>
>> On 11 June 2017 at 13:00, Craig Barratt via BackupPC-users
>>  wrote:
>> > Alex,
>> >
>> > First you should check to see what's left in the v3 cpool, eg:
>> >
>> > cd /data/BackupPC/cpool
>> > ls -lR [0-9a-f]
>> > du -s ?/?/?
>> >
>> > Next you could pick a file and find its inode number and number of
>> > links:
>> >
>> > ls -li 0/1/2/1234567890abcdef
>> >
>> > Are there any files with >1 links?  If so, you could try to find where
>> > else
>> > that file is hardlinked to, eg:
>> >
>> > cd /data/BackupPC/pc
>> > find . -type f -inum inodeNumber -print
>> >
>> > Craig
>> >
>> > On Tue, Jun 6, 2017 at 6:20 PM, Alexey Safonov
>> > 
>> > wrote:
>> >>
>> >> My $Conf{PoolSizeNightlyUpdatePeriod} = 16; is 4
>> >>
>> >> and i already wait more than 2 weeks.
>> >>
>> >> i was trying to convert pool manually. process finished without any
>> >> error.
>> >> and i try nightly maintenance several times manually
>> >>
>> >> Alex
>> >>
>> >> On 6 June 2017 at 17:02, Alexander Moisseev via BackupPC-users
>> >>  wrote:
>> >>>
>> >>> On 6/6/2017 4:24 AM, Alexey Safonov wrote:
>> >>>>
>> >>>> Alexander, Craig
>> >>>>
>> >>>> any ideas what can i check and how to find this V3 pool?
>> >>>>
>> >>> I don't know how exactly do this. I guess you need to find files with
>> >>> hardlink count > 1 in the pool and cpool directories.
>> >>>
>> >>> Probably it's not necessary, you just need to wait.
>> >>>
>> >>> Make sure "$Conf{PoolV3Enabled} = 1;" until the last file deleted from
>> >>> v3
>> >>> pool.
>> >>> By default "$Conf{PoolSizeNightlyUpdatePeriod} = 16;". This means you
>> >>> need to wait 16 days while v3 pool will be emptied.
>> >>>
>> >>> See details in BackupPC_migrateV3toV4 section of
>> >>>
>> >>> https://backuppc.github.io/backuppc/BackupPC.html#Other-Command-Line-Utilities
>> >>> BTW, This section says "You could do this manually". Craig, how'd you
>> >>> suggest to find v3 files in pool and cpool?
>> >>>
>> >>> Since your pool is not big you can set
>> >>> $Conf{PoolSizeNightlyUpdatePeriod}
>> >>> = 1;
>> >>>
>> >>> Also it's not necessary to wait next BackupPC_nightly run. You can
>> >>> start
>> >>> it at any time.
>> >>> # su -m backuppc -c 'BackupPC_serverMesg BackupPC_nightly run'
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> 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/backupp

Re: [BackupPC-users] status graph

[Alexey Safonov]

Still can't find what is using V3 pool

should i leave it as is ? or better to find solution and delete unused data?

On 11 June 2017 at 13:00, Craig Barratt via BackupPC-users
 wrote:
> Alex,
>
> First you should check to see what's left in the v3 cpool, eg:
>
> cd /data/BackupPC/cpool
> ls -lR [0-9a-f]
> du -s ?/?/?
>
> Next you could pick a file and find its inode number and number of links:
>
> ls -li 0/1/2/1234567890abcdef
>
> Are there any files with >1 links?  If so, you could try to find where else
> that file is hardlinked to, eg:
>
> cd /data/BackupPC/pc
> find . -type f -inum inodeNumber -print
>
> Craig
>
> On Tue, Jun 6, 2017 at 6:20 PM, Alexey Safonov 
> wrote:
>>
>> My $Conf{PoolSizeNightlyUpdatePeriod} = 16; is 4
>>
>> and i already wait more than 2 weeks.
>>
>> i was trying to convert pool manually. process finished without any error.
>> and i try nightly maintenance several times manually
>>
>> Alex
>>
>> On 6 June 2017 at 17:02, Alexander Moisseev via BackupPC-users
>>  wrote:
>>>
>>> On 6/6/2017 4:24 AM, Alexey Safonov wrote:
>>>>
>>>> Alexander, Craig
>>>>
>>>> any ideas what can i check and how to find this V3 pool?
>>>>
>>> I don't know how exactly do this. I guess you need to find files with
>>> hardlink count > 1 in the pool and cpool directories.
>>>
>>> Probably it's not necessary, you just need to wait.
>>>
>>> Make sure "$Conf{PoolV3Enabled} = 1;" until the last file deleted from v3
>>> pool.
>>> By default "$Conf{PoolSizeNightlyUpdatePeriod} = 16;". This means you
>>> need to wait 16 days while v3 pool will be emptied.
>>>
>>> See details in BackupPC_migrateV3toV4 section of
>>> https://backuppc.github.io/backuppc/BackupPC.html#Other-Command-Line-Utilities
>>> BTW, This section says "You could do this manually". Craig, how'd you
>>> suggest to find v3 files in pool and cpool?
>>>
>>> Since your pool is not big you can set $Conf{PoolSizeNightlyUpdatePeriod}
>>> = 1;
>>>
>>> Also it's not necessary to wait next BackupPC_nightly run. You can start
>>> it at any time.
>>> # su -m backuppc -c 'BackupPC_serverMesg BackupPC_nightly run'
>>>
>>>
>>>
>>> --
>>> 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/
>>
>
>
> --
> 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/

Re: [BackupPC-users] status graph

[Alexey Safonov]

My $Conf{PoolSizeNightlyUpdatePeriod} = 16; is 4

and i already wait more than 2 weeks.

i was trying to convert pool manually. process finished without any error.
and i try nightly maintenance several times manually

Alex

On 6 June 2017 at 17:02, Alexander Moisseev via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:

> On 6/6/2017 4:24 AM, Alexey Safonov wrote:
>
>> Alexander, Craig
>>
>> any ideas what can i check and how to find this V3 pool?
>>
>> I don't know how exactly do this. I guess you need to find files with
> hardlink count > 1 in the pool and cpool directories.
>
> Probably it's not necessary, you just need to wait.
>
> Make sure "$Conf{PoolV3Enabled} = 1;" until the last file deleted from v3
> pool.
> By default "$Conf{PoolSizeNightlyUpdatePeriod} = 16;". This means you
> need to wait 16 days while v3 pool will be emptied.
>
> See details in BackupPC_migrateV3toV4 section of
> https://backuppc.github.io/backuppc/BackupPC.html#Other-Comm
> and-Line-Utilities
> BTW, This section says "You could do this manually". Craig, how'd you
> suggest to find v3 files in pool and cpool?
>
> Since your pool is not big you can set $Conf{PoolSizeNightlyUpdatePeriod}
> = 1;
>
> Also it's not necessary to wait next BackupPC_nightly run. You can start
> it at any time.
> # su -m backuppc -c 'BackupPC_serverMesg BackupPC_nightly run'
>
>
> 
> --
> 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/

Re: [BackupPC-users] status graph

[Alexey Safonov]

Alexander, Craig

any ideas what can i check and how to find this V3 pool?

Alex

On 2 June 2017 at 20:46, Alexey Safonov  wrote:

> 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 bac

Re: [BackupPC-users] BackupPC 4.1.3 released (plus new versions of backuppc-xs, rsync-bpc and cygwin-rscynd)

[Alexey Safonov]

Hi, Craig

inside of rsyn_bpc (configure.sh) 3.0.9.7 version is still 3.0.9.6

RSYNC_VERSION=3.0.9.6


On 5 June 2017 at 08:44, Craig Barratt 
wrote:

> BackupPC 4.1.3 
> has been released on Github.
>
> New versions of BackupPC-XS 0.55
> , rsync-bpc
> 3.0.9.7  and 
> cygwin-rsyncd
> 3.1.2.1 
> have also been released.
>
> There are several bug fixes; see below.  Upgrading is strongly recommended.
>
> Thanks to Matt Bedynek, Cody Jackson, Lano and Dieter Fauth helping track
> down some bugs.
>
> Enjoy!
>
> Craig
>
> * Merged pull requests: #109, #114
>
> * Fixed editing of compound menu variables (eg: BackupFilesOnly).
>
> * Made tarPipe in lib/BackupPC/Xfer/Tar.pm non-blocking to avoid a
> reported deadlock when BackupPC's select() returns ok for reading, but
> there are no bytes to read from the client tar's log/stdout output.  Thanks
> to Matt Bedynek for running various tests and providing debugging insights
> to track this down.
>
> * Better error checking when using $f->read() on pool files.  Thanks to
> Cody Jackson for tracking down this issue, related to reading corrupted
> compressed pool files.  There's also an additional fix in backuppc-xs
> (version 0.54).
>
> * Cleans up any orphan temporary pool writing files.
>
> * Fixed utf-8 output in SCGI.
>
> * Fixed a reference counting bug in BackupPC_tarExtract.
>
> * Fixed rsync restore transfer byte total, reported by Alexander Moisseev
>
> * Replaced logo href with https://backuppc.github.io/backuppc.
>
> * On a v3->v4 upgrade, remove the new --one-file-system flag from the new
> RsyncArgs if it wasn't there before.
>
> * Added /usr/local/bin to search path in configure.pl from Alexander
> Moisseev (#109).
>
> * Avoid missing or extra quotes when replacing misused undef or empty
> string values in configure.pl from Alexander Moisseev (#114).
>
> * Chasing down a still unsolved bug with help from Lano and Dieter Fauth
> where newly added pool files in uncompressed backups get removed by
> BackupPC_refCountUpdate during a long-running backup, or if
> BackupPC_migrateV3toV4 is running.  Two workarounds added in this release:
> BackupPC_migrateV3toV4 will now exit if BackupPC is running, and
> BackupPC_refCountUpdate only removes pool files that are more than a week
> old.
>
> 
> --
> 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/

Re: [BackupPC-users] status graph

[Alexey Safonov]

 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  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 > <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
> 

Re: [BackupPC-users] status graph

[Alexey Safonov]

Here is mu output

General Server Information

   - The servers PID is 35143, on host 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:
  - 0 pending backup requests from last scheduled wakeup,
  - 0 pending user backup requests,
  - 0 pending command requests,
  - Pool is 99.27+6.12GiB comprising 1216909+165932 files and
  16512+4369 directories (as of 6/2 01:20),
  - Pool hashing gives 0+23 repeated files with longest chain 0+5,
  - Nightly cleanup removed 179717+0 files of size 11.25+0.00GiB
  (around 6/2 01:20),
  - 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  wrote:

> but how it's possible ? i run script with -a option
> script ends with no error
>
> Alex
>
> On 1 June 2017 at 17:35, Alexander Moisseev  wrote:
>
>> On 6/1/2017 11:36 AM, Alexey Safonov wrote:
>>
>>> Hi, All
>>>
>>> do you know what is an update period for status graph ?
>>>
>>> i have
>>> $Conf{BackupPCNightlyPeriod} = 1;
>>> $Conf{PoolSizeNightlyUpdatePeriod} = 4;
>>> $Conf{RefCntFsck} = 1;
>>>
>>>
>>> and more than one week ago i converted all v3 pool to v4
>>>
>>> but status graph still show that i have 6gb of V3 pool
>>>
>>>
>>> Alex
>>>
>>> The graph should be updated every nightly run. Probably you still have
>> some files in V3 pool for some reason.
>> There are exact numbers (including time stamps) above the graph in
>> "General Server Information" section.
>>
>>
>>
>> 
>> --
>> 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/

Re: [BackupPC-users] status graph

[Alexey Safonov]

but how it's possible ? i run script with -a option
script ends with no error

Alex

On 1 June 2017 at 17:35, Alexander Moisseev  wrote:

> On 6/1/2017 11:36 AM, Alexey Safonov wrote:
>
>> Hi, All
>>
>> do you know what is an update period for status graph ?
>>
>> i have
>> $Conf{BackupPCNightlyPeriod} = 1;
>> $Conf{PoolSizeNightlyUpdatePeriod} = 4;
>> $Conf{RefCntFsck} = 1;
>>
>>
>> and more than one week ago i converted all v3 pool to v4
>>
>> but status graph still show that i have 6gb of V3 pool
>>
>>
>> Alex
>>
>> The graph should be updated every nightly run. Probably you still have
> some files in V3 pool for some reason.
> There are exact numbers (including time stamps) above the graph in
> "General Server Information" section.
>
>
>
> 
> --
> 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/

[BackupPC-users] status graph

[Alexey Safonov]

Hi, All

do you know what is an update period for status graph ?

i have
$Conf{BackupPCNightlyPeriod} = 1;
$Conf{PoolSizeNightlyUpdatePeriod} = 4;
$Conf{RefCntFsck} = 1;


and more than one week ago i converted all v3 pool to v4

but status graph still show that i have 6gb of V3 pool


Alex
--
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/

Re: [BackupPC-users] Help with the schedule config

[Alexey Safonov]

that's nice

is there any list of all commands available in BPC ?

Alex

On 25 May 2017 at 15:55, Vladislav Kurz  wrote:
> On 05/24/17 14:41, Yong Zhang wrote:
>> Hi, all
>>
>>
>>
>> I'm new to BackupPC, I installed v4.0 these days, but hard to understand
>> schedule settings, I have some queries here:
>>
>>
>>
>> 1) I want servers to be backed up daily, but full backup only runs on
>> Saturday, how?
>
> Hello,
>
> I use this line in crontab to enforce full backup on weekends:
>
> 55 19 * * 5 backuppc /usr/share/backuppc/bin/BackupPC_serverMesg backup
> HOSTIP HOST USER 1
>
> I usually put the time to run at 5 minutes before the end of blackout
> period to ensure that it will start earlier than normal backup run.
> Also I put FQDN for both HOST and HOSTIP. Number 1 at the end means full
> backup (0 would be incremental).
>
> --
> Best Regards
> Vladislav Kurz
>
> --
> 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/

Re: [BackupPC-users] delete backup

[Alexey Safonov]

delete some servers backup.
looks good

will wait for next maintenance.

thanks one more time Craig
nice product

Alex

On 22 May 2017 at 12:44, Alexey Safonov  wrote:

> ah... sorry.
>
> now i clearly understand. many thanks, Craig
>
> Alex
>
> On 22 May 2017 at 12:42, Craig Barratt 
> wrote:
>
>> Alex,
>>
>> You didn't answer my question.
>>
>> It should be ok to use BackupPC_backupDelete as Michael suggested, even
>> without taking a new full backup. I recommend using the -r option, which
>> will re-run BackupPC_refCountUpdate:
>>
>> su backuppcUser
>>
>> BackupPC_backupDelete -h HOST -n 134 -r
>>
>>
>> It will merge changes into the prior backup #133 so that viewing #133
>> will look the same.  But it should remove references to the additional
>> files since they are not present in #133 (if people want to know the
>> details, #133 has delete attributes for the new top-level directories in
>> 134, so the merging will not copy them).  After two nights of
>> BackupPC_nightly runs the extra pool files should be removed.
>>
>> BackupPC_backupDelete also supports the option of deleting just a portion
>> (ie: a list of directories) of a backup rather than the whole backup.  That
>> should also have the desired effect - the files shouldn't be merged into
>> the prior #133 since they weren't present in #133.
>>
>> Craig
>>
>>
>> On Sun, May 21, 2017 at 9:31 PM, Alexey Safonov <
>> asafo...@kokomocapital.com> wrote:
>>
>>> sorry? what do you mean?
>>>
>>> let me try full backup first and then wait for night maintenance. but
>>> i'm sure that pool size will be same as that not needed files was backed up
>>> and now will be in pool for history.
>>>
>>> for me it's not big problem as i have free size in pool and can wait 8
>>> weeks (our backup policy) until files will be deleted. but may be we need
>>> to find solution to help other users in future
>>>
>>> many thanks for your answers
>>> Alex
>>>
>>> On 22 May 2017 at 12:24, Michael Huntley  wrote:
>>>
>>>> Can we stick to the backups with #133, #134, #135?
>>>>
>>>> Cheers!
>>>>
>>>> mph
>>>>
>>>>
>>>>
>>>> On 2017-05-21 21:19, Alexey Safonov wrote:
>>>>
>>>> here is one real example
>>>>
>>>> 321 incr num of files  = 131074
>>>> 322 incr num of files = 774220 (because of error ib backupfilesonly)
>>>> 324 incr num of files 130946 (after applying hotfix)
>>>>
>>>>
>>>> and i can see graph on main page that show usage of pool ~3 times
>>>> higher than regular. so now i'm looking how to reduce size of pool.
>>>>
>>>> Alex
>>>>
>>>> On 22 May 2017 at 12:14, Craig Barratt 
>>>> wrote:
>>>>
>>>>> Is 134 large because it included additional directories or files that
>>>>> are not in 133 or 135?
>>>>>
>>>>> Is backup 133 filled?
>>>>>
>>>>> Craig
>>>>>
>>>>> On Sun, May 21, 2017 at 8:49 PM, Alexey Safonov <
>>>>> asafo...@kokomocapital.com> wrote:
>>>>>
>>>>>> but if i do full backup for example 135 it will copy existing 134 and
>>>>>> then do diff into 134
>>>>>> that's new in V4
>>>>>> so there are no way to delete data that was backup by mistake and
>>>>>> preserver history.
>>>>>>
>>>>>> V4 is good one but more complex according to V3.
>>>>>>
>>>>>> and now i have 500GB used on /mnt/backup (and regular was about
>>>>>> 100-1500GB :)
>>>>>>
>>>>>> Alex
>>>>>>
>>>>>> On 22 May 2017 at 11:45, Michael Huntley  wrote:
>>>>>>
>>>>>>> Ah, ok.  I would run a Full backup (now considered "Filled").
>>>>>>> That's the safest move prior to removing 134.  The most recent backup is
>>>>>>> always Filled, but were talking about important data so I don't see a
>>>>>>> problem with doing on more Full (Filled) backup to ensure safety.
>>>>>>>
>>>>>>> Craig - anything wrong with my logic here?
>>>

Re: [BackupPC-users] delete backup

[Alexey Safonov]

ah... sorry.

now i clearly understand. many thanks, Craig

Alex

On 22 May 2017 at 12:42, Craig Barratt 
wrote:

> Alex,
>
> You didn't answer my question.
>
> It should be ok to use BackupPC_backupDelete as Michael suggested, even
> without taking a new full backup. I recommend using the -r option, which
> will re-run BackupPC_refCountUpdate:
>
> su backuppcUser
>
> BackupPC_backupDelete -h HOST -n 134 -r
>
>
> It will merge changes into the prior backup #133 so that viewing #133 will
> look the same.  But it should remove references to the additional files
> since they are not present in #133 (if people want to know the details,
> #133 has delete attributes for the new top-level directories in 134, so the
> merging will not copy them).  After two nights of BackupPC_nightly runs the
> extra pool files should be removed.
>
> BackupPC_backupDelete also supports the option of deleting just a portion
> (ie: a list of directories) of a backup rather than the whole backup.  That
> should also have the desired effect - the files shouldn't be merged into
> the prior #133 since they weren't present in #133.
>
> Craig
>
>
> On Sun, May 21, 2017 at 9:31 PM, Alexey Safonov <
> asafo...@kokomocapital.com> wrote:
>
>> sorry? what do you mean?
>>
>> let me try full backup first and then wait for night maintenance. but i'm
>> sure that pool size will be same as that not needed files was backed up and
>> now will be in pool for history.
>>
>> for me it's not big problem as i have free size in pool and can wait 8
>> weeks (our backup policy) until files will be deleted. but may be we need
>> to find solution to help other users in future
>>
>> many thanks for your answers
>> Alex
>>
>> On 22 May 2017 at 12:24, Michael Huntley  wrote:
>>
>>> Can we stick to the backups with #133, #134, #135?
>>>
>>> Cheers!
>>>
>>> mph
>>>
>>>
>>>
>>> On 2017-05-21 21:19, Alexey Safonov wrote:
>>>
>>> here is one real example
>>>
>>> 321 incr num of files  = 131074
>>> 322 incr num of files = 774220 (because of error ib backupfilesonly)
>>> 324 incr num of files 130946 (after applying hotfix)
>>>
>>>
>>> and i can see graph on main page that show usage of pool ~3 times higher
>>> than regular. so now i'm looking how to reduce size of pool.
>>>
>>> Alex
>>>
>>> On 22 May 2017 at 12:14, Craig Barratt 
>>> wrote:
>>>
>>>> Is 134 large because it included additional directories or files that
>>>> are not in 133 or 135?
>>>>
>>>> Is backup 133 filled?
>>>>
>>>> Craig
>>>>
>>>> On Sun, May 21, 2017 at 8:49 PM, Alexey Safonov <
>>>> asafo...@kokomocapital.com> wrote:
>>>>
>>>>> but if i do full backup for example 135 it will copy existing 134 and
>>>>> then do diff into 134
>>>>> that's new in V4
>>>>> so there are no way to delete data that was backup by mistake and
>>>>> preserver history.
>>>>>
>>>>> V4 is good one but more complex according to V3.
>>>>>
>>>>> and now i have 500GB used on /mnt/backup (and regular was about
>>>>> 100-1500GB :)
>>>>>
>>>>> Alex
>>>>>
>>>>> On 22 May 2017 at 11:45, Michael Huntley  wrote:
>>>>>
>>>>>> Ah, ok.  I would run a Full backup (now considered "Filled").  That's
>>>>>> the safest move prior to removing 134.  The most recent backup is always
>>>>>> Filled, but were talking about important data so I don't see a problem 
>>>>>> with
>>>>>> doing on more Full (Filled) backup to ensure safety.
>>>>>>
>>>>>> Craig - anything wrong with my logic here?
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> mph
>>>>>>
>>>>>> On 2017-05-21 20:29, Alexey Safonov wrote:
>>>>>>
>>>>>> Thanks for quick reply.
>>>>>>
>>>>>> but as i understan in V4 full backup in last folder. My question is
>>>>>> related to bug in 4.1.2 (that is now fixed). But because of that bug i 
>>>>>> have
>>>>>> regular backup 133 , abnormal backup 134 (it's huge in size) an

Re: [BackupPC-users] delete backup

[Alexey Safonov]

sorry? what do you mean?

let me try full backup first and then wait for night maintenance. but i'm
sure that pool size will be same as that not needed files was backed up and
now will be in pool for history.

for me it's not big problem as i have free size in pool and can wait 8
weeks (our backup policy) until files will be deleted. but may be we need
to find solution to help other users in future

many thanks for your answers
Alex

On 22 May 2017 at 12:24, Michael Huntley  wrote:

> Can we stick to the backups with #133, #134, #135?
>
> Cheers!
>
> mph
>
>
>
> On 2017-05-21 21:19, Alexey Safonov wrote:
>
> here is one real example
>
> 321 incr num of files  = 131074
> 322 incr num of files = 774220 (because of error ib backupfilesonly)
> 324 incr num of files 130946 (after applying hotfix)
>
>
> and i can see graph on main page that show usage of pool ~3 times higher
> than regular. so now i'm looking how to reduce size of pool.
>
> Alex
>
> On 22 May 2017 at 12:14, Craig Barratt 
> wrote:
>
>> Is 134 large because it included additional directories or files that are
>> not in 133 or 135?
>>
>> Is backup 133 filled?
>>
>> Craig
>>
>> On Sun, May 21, 2017 at 8:49 PM, Alexey Safonov <
>> asafo...@kokomocapital.com> wrote:
>>
>>> but if i do full backup for example 135 it will copy existing 134 and
>>> then do diff into 134
>>> that's new in V4
>>> so there are no way to delete data that was backup by mistake and
>>> preserver history.
>>>
>>> V4 is good one but more complex according to V3.
>>>
>>> and now i have 500GB used on /mnt/backup (and regular was about
>>> 100-1500GB :)
>>>
>>> Alex
>>>
>>> On 22 May 2017 at 11:45, Michael Huntley  wrote:
>>>
>>>> Ah, ok.  I would run a Full backup (now considered "Filled").  That's
>>>> the safest move prior to removing 134.  The most recent backup is always
>>>> Filled, but were talking about important data so I don't see a problem with
>>>> doing on more Full (Filled) backup to ensure safety.
>>>>
>>>> Craig - anything wrong with my logic here?
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> mph
>>>>
>>>> On 2017-05-21 20:29, Alexey Safonov wrote:
>>>>
>>>> Thanks for quick reply.
>>>>
>>>> but as i understan in V4 full backup in last folder. My question is
>>>> related to bug in 4.1.2 (that is now fixed). But because of that bug i have
>>>> regular backup 133 , abnormal backup 134 (it's huge in size) and again
>>>> normal backup 135
>>>> i need to really cleanup my NFS storage. So if i delete 134 it will not
>>>> help? is it correct?
>>>>
>>>> Alex
>>>>
>>>> On 22 May 2017 at 11:26, Michael Huntley  wrote:
>>>>
>>>>> I would strongly suggest the use of BackupPC_backupDelete -n 134 to
>>>>> properly remove the backup.  It should be fine to remove.  You'll lose
>>>>> whatever changes occurred between 133 and 134.
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>>
>>>>> mph
>>>>>
>>>>>
>>>>>
>>>>> On 2017-05-21 19:36, Alexey Safonov wrote:
>>>>>
>>>>> Hi, All
>>>>>
>>>>> I'm usinv V4 backuppc. is it safe to delete one intermediate backup?
>>>>> for example we have in /pc/litspc123 dirs 133 135 and 135
>>>>>
>>>>> is it safe to delete backup 134 directly from nfs?
>>>>>
>>>>> Alex
>>>>>
>>>>> 
>>>>> --
>>>>> 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/
>>>>>
>>>>>
>>>>> 
>

Re: [BackupPC-users] delete backup

[Alexey Safonov]

here is one real example

321 incr num of files  = 131074
322 incr num of files = 774220 (because of error ib backupfilesonly)
324 incr num of files 130946 (after applying hotfix)


and i can see graph on main page that show usage of pool ~3 times higher
than regular. so now i'm looking how to reduce size of pool.

Alex

On 22 May 2017 at 12:14, Craig Barratt 
wrote:

> Is 134 large because it included additional directories or files that are
> not in 133 or 135?
>
> Is backup 133 filled?
>
> Craig
>
> On Sun, May 21, 2017 at 8:49 PM, Alexey Safonov <
> asafo...@kokomocapital.com> wrote:
>
>> but if i do full backup for example 135 it will copy existing 134 and
>> then do diff into 134
>> that's new in V4
>> so there are no way to delete data that was backup by mistake and
>> preserver history.
>>
>> V4 is good one but more complex according to V3.
>>
>> and now i have 500GB used on /mnt/backup (and regular was about
>> 100-1500GB :)
>>
>> Alex
>>
>> On 22 May 2017 at 11:45, Michael Huntley  wrote:
>>
>>> Ah, ok.  I would run a Full backup (now considered "Filled").  That's
>>> the safest move prior to removing 134.  The most recent backup is always
>>> Filled, but were talking about important data so I don't see a problem with
>>> doing on more Full (Filled) backup to ensure safety.
>>>
>>> Craig - anything wrong with my logic here?
>>>
>>>
>>> Cheers,
>>>
>>> mph
>>>
>>> On 2017-05-21 20:29, Alexey Safonov wrote:
>>>
>>> Thanks for quick reply.
>>>
>>> but as i understan in V4 full backup in last folder. My question is
>>> related to bug in 4.1.2 (that is now fixed). But because of that bug i have
>>> regular backup 133 , abnormal backup 134 (it's huge in size) and again
>>> normal backup 135
>>> i need to really cleanup my NFS storage. So if i delete 134 it will not
>>> help? is it correct?
>>>
>>> Alex
>>>
>>> On 22 May 2017 at 11:26, Michael Huntley  wrote:
>>>
>>>> I would strongly suggest the use of BackupPC_backupDelete -n 134 to
>>>> properly remove the backup.  It should be fine to remove.  You'll lose
>>>> whatever changes occurred between 133 and 134.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>>
>>>> mph
>>>>
>>>>
>>>>
>>>> On 2017-05-21 19:36, Alexey Safonov wrote:
>>>>
>>>> Hi, All
>>>>
>>>> I'm usinv V4 backuppc. is it safe to delete one intermediate backup?
>>>> for example we have in /pc/litspc123 dirs 133 135 and 135
>>>>
>>>> is it safe to delete backup 134 directly from nfs?
>>>>
>>>> Alex
>>>>
>>>> 
>>>> --
>>>> 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/
>>>>
>>>
>>> 
>>> --
>>> 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/li

Re: [BackupPC-users] delete backup

[Alexey Safonov]

but if i do full backup for example 135 it will copy existing 134 and then
do diff into 134
that's new in V4
so there are no way to delete data that was backup by mistake and preserver
history.

V4 is good one but more complex according to V3.

and now i have 500GB used on /mnt/backup (and regular was about 100-1500GB
:)

Alex

On 22 May 2017 at 11:45, Michael Huntley  wrote:

> Ah, ok.  I would run a Full backup (now considered "Filled").  That's the
> safest move prior to removing 134.  The most recent backup is always
> Filled, but were talking about important data so I don't see a problem with
> doing on more Full (Filled) backup to ensure safety.
>
> Craig - anything wrong with my logic here?
>
>
> Cheers,
>
> mph
>
> On 2017-05-21 20:29, Alexey Safonov wrote:
>
> Thanks for quick reply.
>
> but as i understan in V4 full backup in last folder. My question is
> related to bug in 4.1.2 (that is now fixed). But because of that bug i have
> regular backup 133 , abnormal backup 134 (it's huge in size) and again
> normal backup 135
> i need to really cleanup my NFS storage. So if i delete 134 it will not
> help? is it correct?
>
> Alex
>
> On 22 May 2017 at 11:26, Michael Huntley  wrote:
>
>> I would strongly suggest the use of BackupPC_backupDelete -n 134 to
>> properly remove the backup.  It should be fine to remove.  You'll lose
>> whatever changes occurred between 133 and 134.
>>
>>
>> Cheers,
>>
>>
>> mph
>>
>>
>>
>> On 2017-05-21 19:36, Alexey Safonov wrote:
>>
>> Hi, All
>>
>> I'm usinv V4 backuppc. is it safe to delete one intermediate backup? for
>> example we have in /pc/litspc123 dirs 133 135 and 135
>>
>> is it safe to delete backup 134 directly from nfs?
>>
>> Alex
>>
>> 
>> --
>> 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/
>>
>
> 
> --
> 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/
>
>
--
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/

Re: [BackupPC-users] delete backup

[Alexey Safonov]

Thanks for quick reply.

but as i understan in V4 full backup in last folder. My question is related
to bug in 4.1.2 (that is now fixed). But because of that bug i have regular
backup 133 , abnormal backup 134 (it's huge in size) and again normal
backup 135
i need to really cleanup my NFS storage. So if i delete 134 it will not
help? is it correct?

Alex

On 22 May 2017 at 11:26, Michael Huntley  wrote:

> I would strongly suggest the use of BackupPC_backupDelete -n 134 to
> properly remove the backup.  It should be fine to remove.  You'll lose
> whatever changes occurred between 133 and 134.
>
>
> Cheers,
>
>
> mph
>
>
>
> On 2017-05-21 19:36, Alexey Safonov wrote:
>
> Hi, All
>
> I'm usinv V4 backuppc. is it safe to delete one intermediate backup? for
> example we have in /pc/litspc123 dirs 133 135 and 135
>
> is it safe to delete backup 134 directly from nfs?
>
> Alex
>
> 
> --
> 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/
>
>
--
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/

[BackupPC-users] delete backup

[Alexey Safonov]

Hi, All

I'm usinv V4 backuppc. is it safe to delete one intermediate backup? for
example we have in /pc/litspc123 dirs 133 135 and 135

is it safe to delete backup 134 directly from nfs?

Alex
--
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/