Re: [BackupPC-users] BPC 4 very slow
2016-01-18 14:09:16
On 18.01.16 21:33, Les Mikesell wrote:
> On Mon, Jan 18, 2016 at 12:25 PM, Alexander Moisseev
> <moiseev AT mezonplus DOT ru> wrote:
>> On 18.01.16 19:53, Les Mikesell wrote:
>>> Does anyone understand the docs at
>>> http://backuppc.sourceforge.net/BackupPC-4.0.0alpha3_doc.html
>>> for $Conf{FillCycle} ? It looks like expiring is really based on
>>> 'filled' backups, not necessarily full backups as in v3. The part I
>>> don't get is that it says the most recent backup is always filled
>>> whether it is full or incremental. If the most recent is filled, how
>>> would any ever be unfilled?
>>>
>>
>> In v4 full/incremental related to backup transfer only, filled/unfilled
>> related to storage.
>>
>> Here is a short explanation:
>> http://backuppc.sourceforge.net/BackupPC-4.0.0alpha3_doc.html#BackupPC-4.0
>>
>> "Backups are stored as "reverse deltas" - the most recent backup is always
>> filled and older backups are reconstitued by merging all the deltas starting
>> with the nearest future filled backup and wworking backwards.
>>
>> This is the opposite of V3 where incrementals are stored as "forward deltas"
>> to a prior backup (typically the last full backup or prior lower-level
>> incremental backup, or the last full in the case of rsync)."
>>
>>
>> So, the latest backup should always be filled, i.e. it actually contains all
>> files. After the last backup will be taken, files that latest backup
>> contains will be removed from backups between the last backup and previous
>> filled backup recursively. Until the last backup was taken, previous backup
>> was filled, but now it is just "reverse delta".
>
> OK, but then how does that relate to the expiring part - which it says
> is really based on the filled status?
>
v3: 'full' shouldn't be expired while there is at least one 'incremental'
that depends on it
v4: 'filled' shouldn't be expired while there is at least one 'unfilled'
that depends on it
Full/incremental doesn't matter for v4 expiration algorithm since it doesn't
affect ability to restore particular backup.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [BackupPC-users] BPC 4 very slow, Adam Goryachev
- Re: [BackupPC-users] BPC 4 very slow, Gandalf Corvotempesta
- Re: [BackupPC-users] BPC 4 very slow, Gandalf Corvotempesta
- Re: [BackupPC-users] BPC 4 very slow, Les Mikesell
- Re: [BackupPC-users] BPC 4 very slow, Gandalf Corvotempesta
- Re: [BackupPC-users] BPC 4 very slow, Les Mikesell
- Re: [BackupPC-users] BPC 4 very slow, Gandalf Corvotempesta
- Re: [BackupPC-users] BPC 4 very slow, Gandalf Corvotempesta
- Re: [BackupPC-users] BPC 4 very slow, Gandalf Corvotempesta
- Re: [BackupPC-users] BPC 4 very slow, Gandalf Corvotempesta
- Re: [BackupPC-users] BPC 4 very slow, Adam Goryachev
|
|
|