Re: [Users] Ploop Incremental backups strategy

2020-09-19 Thread tranxene50 

Hello Paulo!

Many thanks for your answer!

I was afraid to have "committed a serious faux pas".
(Google translate helped me to find correct words)

English is not an easy language and transposing/translating French jokes 
is a little complicated...


If you decide to publish your software on Github, I would like to 
translate the site to English, Portughese and Italian.


At the moment, I (really) do not plan to use Github because Microsoft is 
the owner.


But you are right, I should "liberate/deploy" the source code to any 
person willing to improve it.


I have no words to explain why Internet is so cool: many thanks for your 
proposal, it would be awesome if the final "survival guide" could be 
translated.


please, wait a few days/weeks and I will complete it.

Once it is done, let's get in touch! :)

Have a good night!

Le 18/09/2020 à 23:37, Paulo Coghi - Coghi IT a écrit :

No need to apologize, tranxene50! Everything is fine! :)

On Fri, Sep 18, 2020 at 6:13 PM tranxene50 
> wrote:


Hello all.

After a quick re-read of my last message, I realized that my "joke"
about being a "power user" was not funny at all.

I did not mean that some persons were "power user" while others
not, it
would have been incredibly disrespectful.

I would like to sincerely apologize if I have offended anyone.

I am truly sorry.

Le 18/09/2020 à 03:35, tranxene50 a écrit :
> Hello Jake!
>
> I do not know you but it seems that you are a "power user".
>
> => because doc was missing.
>
> Like I said before, openvz-diff-backups had no doc so I am
writing it
> on a daily basis (survival guide).
>
> Any feedback will be greatly appreciated!
>
> Good night!
>
> Le 09/09/2020 à 22:40, jjs - mainphrame a écrit :
>> Thank you tranxene50, I've installed openvz-diff-backups on my
ovz-7
>> hosts, and so far it looks very promising.
>>
>> Jake
>
> tranxene50
> tranxen...@openvz-diff-backups.fr

>
> ___
> Users mailing list
> Users@openvz.org 
> https://lists.openvz.org/mailman/listinfo/users

-- 
tranxene50

tranxen...@openvz-diff-backups.fr


___
Users mailing list
Users@openvz.org 
https://lists.openvz.org/mailman/listinfo/users


___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users


--
tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2020-09-18 Thread Paulo Coghi - Coghi IT 
No need to apologize, tranxene50! Everything is fine! :)

On Fri, Sep 18, 2020 at 6:13 PM tranxene50 <
tranxen...@openvz-diff-backups.fr> wrote:

> Hello all.
>
> After a quick re-read of my last message, I realized that my "joke"
> about being a "power user" was not funny at all.
>
> I did not mean that some persons were "power user" while others not, it
> would have been incredibly disrespectful.
>
> I would like to sincerely apologize if I have offended anyone.
>
> I am truly sorry.
>
> Le 18/09/2020 à 03:35, tranxene50 a écrit :
> > Hello Jake!
> >
> > I do not know you but it seems that you are a "power user".
> >
> > => because doc was missing.
> >
> > Like I said before, openvz-diff-backups had no doc so I am writing it
> > on a daily basis (survival guide).
> >
> > Any feedback will be greatly appreciated!
> >
> > Good night!
> >
> > Le 09/09/2020 à 22:40, jjs - mainphrame a écrit :
> >> Thank you tranxene50, I've installed openvz-diff-backups on my ovz-7
> >> hosts, and so far it looks very promising.
> >>
> >> Jake
> >
> > tranxene50
> > tranxen...@openvz-diff-backups.fr
> >
> > ___
> > Users mailing list
> > Users@openvz.org
> > https://lists.openvz.org/mailman/listinfo/users
>
> --
> tranxene50
> tranxen...@openvz-diff-backups.fr
>
> ___
> Users mailing list
> Users@openvz.org
> https://lists.openvz.org/mailman/listinfo/users
>
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2020-09-18 Thread tranxene50 

Hello all.

After a quick re-read of my last message, I realized that my "joke" 
about being a "power user" was not funny at all.


I did not mean that some persons were "power user" while others not, it 
would have been incredibly disrespectful.


I would like to sincerely apologize if I have offended anyone.

I am truly sorry.

Le 18/09/2020 à 03:35, tranxene50 a écrit :

Hello Jake!

I do not know you but it seems that you are a "power user".

=> because doc was missing.

Like I said before, openvz-diff-backups had no doc so I am writing it 
on a daily basis (survival guide).


Any feedback will be greatly appreciated!

Good night!

Le 09/09/2020 à 22:40, jjs - mainphrame a écrit :
Thank you tranxene50, I've installed openvz-diff-backups on my ovz-7 
hosts, and so far it looks very promising.


Jake


tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users


--
tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2020-09-17 Thread tranxene50 

Hello Jake!

I do not know you but it seems that you are a "power user".

=> because doc was missing.

Like I said before, openvz-diff-backups had no doc so I am writing it on 
a daily basis (survival guide).


Any feedback will be greatly appreciated!

Good night!

Le 09/09/2020 à 22:40, jjs - mainphrame a écrit :
Thank you tranxene50, I've installed openvz-diff-backups on my ovz-7 
hosts, and so far it looks very promising.


Jake


tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2020-09-16 Thread mailinglist 
Hello tranxene 50,

Thanxs again fort he update and the info
changing the master and remote fixe dit for me, only i had to remove "-o 
ControlPersist=3600"

i have one future request
openvz-diff-backups restore 1 auto   restores the latest version

openvz-diff-backups download 1 has no function to download the latest, that 
would be very nice if that one can be added
Now there is no way to know the date_time of the latest backup  if you iseing 
it on a clean file server, you cant use the list function for it

Chears

Steffan

-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens tranxene50
Verzonden: dinsdag 15 september 2020 17:25
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello Steffan.

In order to download backups, you must configure OVZDB as follow:

SOURCE => SSH keys 1 => MASTER (where backups will be downloaded) => SSH keys 2 
=> REMOTE (where the backups are saved)

For instance:

MASTER_SSH_PATH="root@localhost:/home/backup/openvz-diff-backups" 
(backups will downloaded to "localhost")

REMOTE_SSH_PATH="root@192.168.1.99:/home/backup/openvz-diff-backups" 
(the machine where backups are currently stored)

When you will download backups, OVZDB will first connects to "localhost" 
(to access MASTER "storage") and then will connect to 192.168.1.99 (to access 
REMOTE "storage").

I known this is counter intuitive but,

- when you make backups, OVZDB will store them on MASTER (ex: 192.168.1.99)

- when you download backups, the "previous" MASTER (192.168.1.99) must be 
configured as the REMOTE

Tonight I will try to post more infos.

Have a great day!

Le 15/09/2020 à 15:43, mailingl...@tikklik.nl a écrit :
> Hello tranxene 50,
>
> What i find out abouth the script is a strange (i think strange) loop
>
>  From my office i do a:
> openvz-diff-backups download 1 2020-09-15_03-42-51
>
> I see a SSH connection to the backupserver on the NOC but in the ssh 
> log of the backupserver i see; refused connect from 127.0.0.1 
> (127.0.0.1)
>
> So the script is trying to make a new connection back to the server at 
> my office, hat only will work if i give the server access to my office 
> But why is it setting up another connection, from the server back tot 
> he office
>
>
>
> -Oorspronkelijk bericht-
> Van: users-boun...@openvz.org  Namens 
> mailingl...@tikklik.nl
> Verzonden: dinsdag 15 september 2020 11:20
> Aan: 'OpenVZ users' 
> Onderwerp: Re: [Users] Ploop Incremental backups strategy
>
> So the backup function tot he master backupserver works great.
> But looks like there is a bug somewhere.
>
> If from the live server i do
> openvz-diff-backups restore 1 list
> im getting a list of backups
> 1 - *Latest* backup - mode: live_plop - date: 2020-09-15_03-42-51 - task: 
> backup - exit: success - keep: until it is deleted - host:
>
> But if i do:
> openvz-diff-backups download 1 2020-09-15_03-42-51
>
> im getting
> [2020-09-15 11:19:11] [ 1] *Error*- SSH error: connection failure 
> (host: "192.168.1.99" -> "127.0.0.1" - error: "255") - please check SSH 
> private/public keys
> [2020-09-15 11:19:11] [ 1] *Notice*   - SSH error: unable to close remote 
> SSH mux (host: "192.168.1.99" -> "127.0.0.1" - error: "255") - ignoring 
> (please, do not panic)
>
>
> -Oorspronkelijk bericht-
> Van: users-boun...@openvz.org  Namens 
> tranxene50
> Verzonden: zaterdag 12 september 2020 03:35
> Aan: users@openvz.org
> Onderwerp: Re: [Users] Ploop Incremental backups strategy
>
> Hello Steffan.
>
> To quickly answer your questions:
>
> 1) every successful backup is considered as a full backup, even if it 
> is an "incremental/differential/full" backup under the hood (I know, 
> this is counter intuitive)
>
> In short, you do not have to care about choosing which backup you want to 
> restore because there is no computation to "rebuild" a backup.
>
> 2) "openvz-diff-backups --help" will show you all options
>
> You are right, the doc is missing: I have spent 99% of my time working on the 
> code - and testing it - but only 1% to "build" a simple single website page 
> ...
>
> 3) there is no intrinsic performance differences between push or pull
> modes: it only depends of the hardware that your are using
>
> But your question was about "external" servers having access to your backup 
> server => use "pull" mode.
>
> This means that every client should save all backups on their own servers 
> and, once it is done, you can download them on your backup server.
>
> If this is not pos

Re: [Users] Ploop Incremental backups strategy

2020-09-15 Thread tranxene50 

Hello Steffan.

In order to download backups, you must configure OVZDB as follow:

SOURCE => SSH keys 1 => MASTER (where backups will be downloaded) => SSH 
keys 2 => REMOTE (where the backups are saved)


For instance:

MASTER_SSH_PATH="root@localhost:/home/backup/openvz-diff-backups" 
(backups will downloaded to "localhost")


REMOTE_SSH_PATH="root@192.168.1.99:/home/backup/openvz-diff-backups" 
(the machine where backups are currently stored)


When you will download backups, OVZDB will first connects to "localhost" 
(to access MASTER "storage") and then will connect to 192.168.1.99 (to 
access REMOTE "storage").


I known this is counter intuitive but,

- when you make backups, OVZDB will store them on MASTER (ex: 192.168.1.99)

- when you download backups, the "previous" MASTER (192.168.1.99) must 
be configured as the REMOTE


Tonight I will try to post more infos.

Have a great day!

Le 15/09/2020 à 15:43, mailingl...@tikklik.nl a écrit :

Hello tranxene 50,

What i find out abouth the script is a strange (i think strange) loop

 From my office i do a:
openvz-diff-backups download 1 2020-09-15_03-42-51

I see a SSH connection to the backupserver on the NOC
but in the ssh log of the backupserver i see;
refused connect from 127.0.0.1 (127.0.0.1)

So the script is trying to make a new connection back to the server at my 
office, hat only will work if i give the server access to my office
But why is it setting up another connection, from the server back tot he office



-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens 
mailingl...@tikklik.nl
Verzonden: dinsdag 15 september 2020 11:20
Aan: 'OpenVZ users' 
Onderwerp: Re: [Users] Ploop Incremental backups strategy

So the backup function tot he master backupserver works great.
But looks like there is a bug somewhere.

If from the live server i do
openvz-diff-backups restore 1 list
im getting a list of backups
1 - *Latest* backup - mode: live_plop - date: 2020-09-15_03-42-51 - task: 
backup - exit: success - keep: until it is deleted - host:

But if i do:
openvz-diff-backups download 1 2020-09-15_03-42-51

im getting
[2020-09-15 11:19:11] [ 1] *Error*- SSH error: connection failure (host: "192.168.1.99" -> 
"127.0.0.1" - error: "255") - please check SSH private/public keys
[2020-09-15 11:19:11] [ 1] *Notice*   - SSH error: unable to close remote SSH mux (host: 
"192.168.1.99" -> "127.0.0.1" - error: "255") - ignoring (please, do not panic)


-Oorspronkelijk bericht-----
Van: users-boun...@openvz.org  Namens tranxene50
Verzonden: zaterdag 12 september 2020 03:35
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello Steffan.

To quickly answer your questions:

1) every successful backup is considered as a full backup, even if it is an 
"incremental/differential/full" backup under the hood (I know, this is counter 
intuitive)

In short, you do not have to care about choosing which backup you want to restore because 
there is no computation to "rebuild" a backup.

2) "openvz-diff-backups --help" will show you all options

You are right, the doc is missing: I have spent 99% of my time working on the code - and 
testing it - but only 1% to "build" a simple single website page ...

3) there is no intrinsic performance differences between push or pull
modes: it only depends of the hardware that your are using

But your question was about "external" servers having access to your backup server => use 
"pull" mode.

This means that every client should save all backups on their own servers and, 
once it is done, you can download them on your backup server.

If this is not possible, create a container to accept their backups
(push) and another container to "pull" these backups.

*WARNING AGAIN*: never, ever, store OVZDB backups in a container using Ploop 
layout: please, use bindfs to mount a directory from the host into the container

Have a good night!

Le 11/09/2020 à 16:05, tranxene50 a écrit :

Hello Steffan.

I am writing a "survival" guide in English: please let me some time to
finish it. ;-)

Have a nice day!

Le 11/09/2020 à 15:53, mailingl...@tikklik.nl a écrit :

Thanx, im looking in to it, it looks very nice Im missing some
documentation so i have some quastions...

1)
So if you take live backups
Then the seccond backup is incremental any you can in case of
emergancy take the last incremental backup to restore the whole CT?

2) in your cron you use this, " -l 6 -q" can you explain what that does?

3)Push and pull
I miss documentation how to setup.
Have you any experiance in performance on push vs pull On my own
nodes i can install the script on the live node But i also have
clients with nodes i backup, but i dont want them to give access

Re: [Users] Ploop Incremental backups strategy

2020-09-15 Thread mailinglist 
Hello tranxene 50,

What i find out abouth the script is a strange (i think strange) loop

From my office i do a:
openvz-diff-backups download 1 2020-09-15_03-42-51

I see a SSH connection to the backupserver on the NOC
but in the ssh log of the backupserver i see;
refused connect from 127.0.0.1 (127.0.0.1)

So the script is trying to make a new connection back to the server at my 
office, hat only will work if i give the server access to my office
But why is it setting up another connection, from the server back tot he office



-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens 
mailingl...@tikklik.nl
Verzonden: dinsdag 15 september 2020 11:20
Aan: 'OpenVZ users' 
Onderwerp: Re: [Users] Ploop Incremental backups strategy

So the backup function tot he master backupserver works great.
But looks like there is a bug somewhere.

If from the live server i do
openvz-diff-backups restore 1 list
im getting a list of backups
1 - *Latest* backup - mode: live_plop - date: 2020-09-15_03-42-51 - task: 
backup - exit: success - keep: until it is deleted - host:

But if i do:
openvz-diff-backups download 1 2020-09-15_03-42-51

im getting
[2020-09-15 11:19:11] [ 1] *Error*- SSH error: connection failure 
(host: "192.168.1.99" -> "127.0.0.1" - error: "255") - please check SSH 
private/public keys
[2020-09-15 11:19:11] [ 1] *Notice*   - SSH error: unable to close remote 
SSH mux (host: "192.168.1.99" -> "127.0.0.1" - error: "255") - ignoring 
(please, do not panic)


-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens tranxene50
Verzonden: zaterdag 12 september 2020 03:35
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello Steffan.

To quickly answer your questions:

1) every successful backup is considered as a full backup, even if it is an 
"incremental/differential/full" backup under the hood (I know, this is counter 
intuitive)

In short, you do not have to care about choosing which backup you want to 
restore because there is no computation to "rebuild" a backup.

2) "openvz-diff-backups --help" will show you all options

You are right, the doc is missing: I have spent 99% of my time working on the 
code - and testing it - but only 1% to "build" a simple single website page ...

3) there is no intrinsic performance differences between push or pull
modes: it only depends of the hardware that your are using

But your question was about "external" servers having access to your backup 
server => use "pull" mode.

This means that every client should save all backups on their own servers and, 
once it is done, you can download them on your backup server.

If this is not possible, create a container to accept their backups
(push) and another container to "pull" these backups.

*WARNING AGAIN*: never, ever, store OVZDB backups in a container using Ploop 
layout: please, use bindfs to mount a directory from the host into the container

Have a good night!

Le 11/09/2020 à 16:05, tranxene50 a écrit :
> Hello Steffan.
>
> I am writing a "survival" guide in English: please let me some time to 
> finish it. ;-)
>
> Have a nice day!
>
> Le 11/09/2020 à 15:53, mailingl...@tikklik.nl a écrit :
>> Thanx, im looking in to it, it looks very nice Im missing some 
>> documentation so i have some quastions...
>>
>> 1)
>> So if you take live backups
>> Then the seccond backup is incremental any you can in case of 
>> emergancy take the last incremental backup to restore the whole CT?
>>
>> 2) in your cron you use this, " -l 6 -q" can you explain what that does?
>>
>> 3)Push and pull
>> I miss documentation how to setup.
>> Have you any experiance in performance on push vs pull On my own 
>> nodes i can install the script on the live node But i also have 
>> clients with nodes i backup, but i dont want them to give access 
>> directly tot he backup server.
>>
>> 4) at night i want to backup, from tha main backup server to a remote 
>> sitelocation
>>  In case of a big desaster 😊
>> what do i need tor sync?
>> Everything with a date file/map name?
>>and include the data dir?
>>
>> Mayby for the future the option to pull the last update to a remote 
>> server 😊
>>
>> Thanxs for the time.
>>
>> Steffan
>>
>> -Oorspronkelijk bericht-
>> Van: users-boun...@openvz.org  Namens
>> tranxene50
>> Verzonden: woensdag 9 september 2020 01:02
>> Aan: users@openvz.org
>> Onderwerp: Re: [Users] Ploop Incremental backups strategy
>>
>> Hello!
>>
>> Please forgive my bad English, I live in France.
>>
>> A

Re: [Users] Ploop Incremental backups strategy

2020-09-15 Thread mailinglist 
So the backup function tot he master backupserver works great.
But looks like there is a bug somewhere.

If from the live server i do
openvz-diff-backups restore 1 list
im getting a list of backups
1 - *Latest* backup - mode: live_plop - date: 2020-09-15_03-42-51 - task: 
backup - exit: success - keep: until it is deleted - host:

But if i do:
openvz-diff-backups download 1 2020-09-15_03-42-51

im getting
[2020-09-15 11:19:11] [ 1] *Error*- SSH error: connection failure 
(host: "192.168.1.99" -> "127.0.0.1" - error: "255") - please check SSH 
private/public keys
[2020-09-15 11:19:11] [ 1] *Notice*   - SSH error: unable to close remote 
SSH mux (host: "192.168.1.99" -> "127.0.0.1" - error: "255") - ignoring 
(please, do not panic)


-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens tranxene50
Verzonden: zaterdag 12 september 2020 03:35
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello Steffan.

To quickly answer your questions:

1) every successful backup is considered as a full backup, even if it is an 
"incremental/differential/full" backup under the hood (I know, this is counter 
intuitive)

In short, you do not have to care about choosing which backup you want to 
restore because there is no computation to "rebuild" a backup.

2) "openvz-diff-backups --help" will show you all options

You are right, the doc is missing: I have spent 99% of my time working on the 
code - and testing it - but only 1% to "build" a simple single website page ...

3) there is no intrinsic performance differences between push or pull
modes: it only depends of the hardware that your are using

But your question was about "external" servers having access to your backup 
server => use "pull" mode.

This means that every client should save all backups on their own servers and, 
once it is done, you can download them on your backup server.

If this is not possible, create a container to accept their backups
(push) and another container to "pull" these backups.

*WARNING AGAIN*: never, ever, store OVZDB backups in a container using Ploop 
layout: please, use bindfs to mount a directory from the host into the container

Have a good night!

Le 11/09/2020 à 16:05, tranxene50 a écrit :
> Hello Steffan.
>
> I am writing a "survival" guide in English: please let me some time to 
> finish it. ;-)
>
> Have a nice day!
>
> Le 11/09/2020 à 15:53, mailingl...@tikklik.nl a écrit :
>> Thanx, im looking in to it, it looks very nice Im missing some 
>> documentation so i have some quastions...
>>
>> 1)
>> So if you take live backups
>> Then the seccond backup is incremental any you can in case of 
>> emergancy take the last incremental backup to restore the whole CT?
>>
>> 2) in your cron you use this, " -l 6 -q" can you explain what that does?
>>
>> 3)Push and pull
>> I miss documentation how to setup.
>> Have you any experiance in performance on push vs pull On my own 
>> nodes i can install the script on the live node But i also have 
>> clients with nodes i backup, but i dont want them to give access 
>> directly tot he backup server.
>>
>> 4) at night i want to backup, from tha main backup server to a remote 
>> sitelocation
>>  In case of a big desaster 😊
>> what do i need tor sync?
>> Everything with a date file/map name?
>>and include the data dir?
>>
>> Mayby for the future the option to pull the last update to a remote 
>> server 😊
>>
>> Thanxs for the time.
>>
>> Steffan
>>
>> -Oorspronkelijk bericht-
>> Van: users-boun...@openvz.org  Namens
>> tranxene50
>> Verzonden: woensdag 9 september 2020 01:02
>> Aan: users@openvz.org
>> Onderwerp: Re: [Users] Ploop Incremental backups strategy
>>
>> Hello!
>>
>> Please forgive my bad English, I live in France.
>>
>> A few years ago, as a hobby in the beginning, I created a file based 
>> "incremental" backup tool (that heavily relies on rsync) :
>> https://www.openvz-diff-backups.fr
>>
>> It works flawlessly with OpenVZ 6 but only have been rapidly tested 
>> with OpenVZ 7.
>>
>> The main difference between OpenVZ 6 and 7 is that memory dump
>> (checkpoint) is now done using CRIU instead of OpenVZ "Legacy" kernel.
>>
>> But,  globally, the process is still the same: create a ploop 
>> snapshot, mount it, sync it (with rsync) and then create a "diff"
>> backup (using rsync again with --link-dest).
>>
>> As far as I know, this is one of the rarest GPL too

Re: [Users] Ploop Incremental backups strategy

2020-09-11 Thread tranxene50 

Hello Steffan.

To quickly answer your questions:

1) every successful backup is considered as a full backup, even if it is 
an "incremental/differential/full" backup under the hood (I know, this 
is counter intuitive)


In short, you do not have to care about choosing which backup you want 
to restore because there is no computation to "rebuild" a backup.


2) "openvz-diff-backups --help" will show you all options

You are right, the doc is missing: I have spent 99% of my time working 
on the code - and testing it - but only 1% to "build" a simple single 
website page ...


3) there is no intrinsic performance differences between push or pull 
modes: it only depends of the hardware that your are using


But your question was about "external" servers having access to your 
backup server => use "pull" mode.


This means that every client should save all backups on their own 
servers and, once it is done, you can download them on your backup server.


If this is not possible, create a container to accept their backups 
(push) and another container to "pull" these backups.


*WARNING AGAIN*: never, ever, store OVZDB backups in a container using 
Ploop layout: please, use bindfs to mount a directory from the host into 
the container


Have a good night!

Le 11/09/2020 à 16:05, tranxene50 a écrit :

Hello Steffan.

I am writing a "survival" guide in English: please let me some time to 
finish it. ;-)


Have a nice day!

Le 11/09/2020 à 15:53, mailingl...@tikklik.nl a écrit :
Thanx, im looking in to it, it looks very nice Im missing some 
documentation so i have some quastions...


1)
So if you take live backups
Then the seccond backup is incremental any you can in case of 
emergancy take the last incremental backup to restore the whole CT?


2) in your cron you use this, " -l 6 -q" can you explain what that does?

3)Push and pull
I miss documentation how to setup.
Have you any experiance in performance on push vs pull On my own 
nodes i can install the script on the live node But i also have 
clients with nodes i backup, but i dont want them to give access 
directly tot he backup server.


4) at night i want to backup, from tha main backup server to a remote 
sitelocation

 In case of a big desaster 😊
    what do i need tor sync?
    Everything with a date file/map name?
   and include the data dir?

Mayby for the future the option to pull the last update to a remote 
server 😊


Thanxs for the time.

Steffan

-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens 
tranxene50

Verzonden: woensdag 9 september 2020 01:02
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello!

Please forgive my bad English, I live in France.

A few years ago, as a hobby in the beginning, I created a file based 
"incremental" backup tool (that heavily relies on rsync) :

https://www.openvz-diff-backups.fr

It works flawlessly with OpenVZ 6 but only have been rapidly tested 
with OpenVZ 7.


The main difference between OpenVZ 6 and 7 is that memory dump
(checkpoint) is now done using CRIU instead of OpenVZ "Legacy" kernel.

But,  globally, the process is still the same: create a ploop 
snapshot, mount it, sync it (with rsync) and then create a "diff" 
backup (using rsync again with --link-dest).


As far as I know, this is one of the rarest GPL tools (any hint
appreciated!) able to backup/restore CT files and, most importantly, 
full memory state.


Restoring a "live" backup is like resuming an OS (Windows, Linux, MacOS,
etc) after it had been put to sleep: the container will resume and 
works again, just like nothing had happen.


So you can cheat and pretend 100% uptime even if a container was down 
most of the time... (evidently this a joke and, please, do not play 
at this game: /var/log/* will betray you)


Note: to migrate CT between OpenVZ 6 and 7, you must use "cold" 
backups because memory dumps are incompatible (OpenVZ Kernel vs CRIU).


To answer your questions:

1) you can restore any previous backup because each one is considered 
as a full backup (no diff/incremental computing: it is just 
files/directories/other - and hard links)


2) because backups are just a bunch of files (and mostly hard links), 
you can easily browse any backup of a CT and copy any 
files/directories needed


At the moment, development of openvz-diff-backups is on pause - 
because it fulfills all my needs with OpenVZ 6 - but I am in the 
process of moving to OpenVZ 7 in a few months.


So, if you encounter a bug or an issue, please leave me a message: 
the tool has a very conservative approach and is designed to cleanly 
stop if anything unexpected/unknown/abnormal happens.


Have a nice day!

Le 08/09/2020 à 14:24, mailingl...@tikklik.nl a écrit :

Hello,

Using openvz7
Im looking ad my backup strategy
I allways used rsync on openvz6
And looks lik

Re: [Users] Ploop Incremental backups strategy

2020-09-11 Thread tranxene50 

Hello Steffan.

I am writing a "survival" guide in English: please let me some time to 
finish it. ;-)


Have a nice day!

Le 11/09/2020 à 15:53, mailingl...@tikklik.nl a écrit :

Thanx, im looking in to it, it looks very nice Im missing some documentation so 
i have some quastions...

1)
So if you take live backups
Then the seccond backup is incremental any you can in case of emergancy take 
the last incremental backup to restore the whole CT?

2) in your cron you use this, " -l 6 -q" can you explain what that does?

3)Push and pull
I miss documentation how to setup.
Have you any experiance in performance on push vs pull On my own nodes i can 
install the script on the live node But i also have clients with nodes i 
backup, but i dont want them to give access directly tot he backup server.

4) at night i want to backup, from tha main backup server to a remote 
sitelocation
 In case of a big desaster 😊
what do i need tor sync?
Everything with a date file/map name?
   and include the data dir?

Mayby for the future the option to pull the last update to a remote server 😊

Thanxs for the time.

Steffan

-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens tranxene50
Verzonden: woensdag 9 september 2020 01:02
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello!

Please forgive my bad English, I live in France.

A few years ago, as a hobby in the beginning, I created a file based 
"incremental" backup tool (that heavily relies on rsync) :
https://www.openvz-diff-backups.fr

It works flawlessly with OpenVZ 6 but only have been rapidly tested with OpenVZ 
7.

The main difference between OpenVZ 6 and 7 is that memory dump
(checkpoint) is now done using CRIU instead of OpenVZ "Legacy" kernel.

But,  globally, the process is still the same: create a ploop snapshot, mount it, sync it 
(with rsync) and then create a "diff" backup (using rsync again with 
--link-dest).

As far as I know, this is one of the rarest GPL tools (any hint
appreciated!) able to backup/restore CT files and, most importantly, full 
memory state.

Restoring a "live" backup is like resuming an OS (Windows, Linux, MacOS,
etc) after it had been put to sleep: the container will resume and works again, 
just like nothing had happen.

So you can cheat and pretend 100% uptime even if a container was down most of 
the time... (evidently this a joke and, please, do not play at this game: 
/var/log/* will betray you)

Note: to migrate CT between OpenVZ 6 and 7, you must use "cold" backups because 
memory dumps are incompatible (OpenVZ Kernel vs CRIU).

To answer your questions:

1) you can restore any previous backup because each one is considered as a full 
backup (no diff/incremental computing: it is just files/directories/other - and 
hard links)

2) because backups are just a bunch of files (and mostly hard links), you can 
easily browse any backup of a CT and copy any files/directories needed

At the moment, development of openvz-diff-backups is on pause - because it 
fulfills all my needs with OpenVZ 6 - but I am in the process of moving to 
OpenVZ 7 in a few months.

So, if you encounter a bug or an issue, please leave me a message: the tool has 
a very conservative approach and is designed to cleanly stop if anything 
unexpected/unknown/abnormal happens.

Have a nice day!

Le 08/09/2020 à 14:24, mailingl...@tikklik.nl a écrit :

Hello,

Using openvz7
Im looking ad my backup strategy
I allways used rsync on openvz6
And looks like on openvz7 this can also be done on /vz/root/VEID But i
dont know if i can do a full restore from that...


Now im looking at snapshots
https://github.com/TamCore/vzpbackup
it can make full backups and incremental backups

Is someone using this script?
i have some question hope someone can help

the incremental backups are nice to save space and time on a remote
backupserver But how does a restore works.
For what i know you can only restore a full snapshot, the incremental
backups have only the changed files

Question 2.
Is it possible to extract a file from the backup for a single file restore?
And if so can someone tell me how?


Thanxs
Steffan









___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

--
tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users


___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users


--
tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2020-09-11 Thread mailinglist 
Thanx, im looking in to it, it looks very nice Im missing some documentation so 
i have some quastions...

1)
So if you take live backups
Then the seccond backup is incremental any you can in case of emergancy take 
the last incremental backup to restore the whole CT?

2) in your cron you use this, " -l 6 -q" can you explain what that does?

3)Push and pull
I miss documentation how to setup.
Have you any experiance in performance on push vs pull On my own nodes i can 
install the script on the live node But i also have clients with nodes i 
backup, but i dont want them to give access directly tot he backup server.

4) at night i want to backup, from tha main backup server to a remote 
sitelocation
In case of a big desaster 😊
   what do i need tor sync?
   Everything with a date file/map name?
  and include the data dir?

Mayby for the future the option to pull the last update to a remote server 😊

Thanxs for the time.

Steffan

-Oorspronkelijk bericht-
Van: users-boun...@openvz.org  Namens tranxene50
Verzonden: woensdag 9 september 2020 01:02
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello!

Please forgive my bad English, I live in France.

A few years ago, as a hobby in the beginning, I created a file based 
"incremental" backup tool (that heavily relies on rsync) : 
https://www.openvz-diff-backups.fr

It works flawlessly with OpenVZ 6 but only have been rapidly tested with OpenVZ 
7.

The main difference between OpenVZ 6 and 7 is that memory dump
(checkpoint) is now done using CRIU instead of OpenVZ "Legacy" kernel.

But,  globally, the process is still the same: create a ploop snapshot, mount 
it, sync it (with rsync) and then create a "diff" backup (using rsync again 
with --link-dest).

As far as I know, this is one of the rarest GPL tools (any hint
appreciated!) able to backup/restore CT files and, most importantly, full 
memory state.

Restoring a "live" backup is like resuming an OS (Windows, Linux, MacOS,
etc) after it had been put to sleep: the container will resume and works again, 
just like nothing had happen.

So you can cheat and pretend 100% uptime even if a container was down most of 
the time... (evidently this a joke and, please, do not play at this game: 
/var/log/* will betray you)

Note: to migrate CT between OpenVZ 6 and 7, you must use "cold" backups because 
memory dumps are incompatible (OpenVZ Kernel vs CRIU).

To answer your questions:

1) you can restore any previous backup because each one is considered as a full 
backup (no diff/incremental computing: it is just files/directories/other - and 
hard links)

2) because backups are just a bunch of files (and mostly hard links), you can 
easily browse any backup of a CT and copy any files/directories needed

At the moment, development of openvz-diff-backups is on pause - because it 
fulfills all my needs with OpenVZ 6 - but I am in the process of moving to 
OpenVZ 7 in a few months.

So, if you encounter a bug or an issue, please leave me a message: the tool has 
a very conservative approach and is designed to cleanly stop if anything 
unexpected/unknown/abnormal happens.

Have a nice day!

Le 08/09/2020 à 14:24, mailingl...@tikklik.nl a écrit :
> Hello,
>
> Using openvz7
> Im looking ad my backup strategy
> I allways used rsync on openvz6
> And looks like on openvz7 this can also be done on /vz/root/VEID But i 
> dont know if i can do a full restore from that...
>
>
> Now im looking at snapshots
> https://github.com/TamCore/vzpbackup
> it can make full backups and incremental backups
>
> Is someone using this script?
> i have some question hope someone can help
>
> the incremental backups are nice to save space and time on a remote 
> backupserver But how does a restore works.
> For what i know you can only restore a full snapshot, the incremental 
> backups have only the changed files
>
> Question 2.
> Is it possible to extract a file from the backup for a single file restore?
> And if so can someone tell me how?
>
>
> Thanxs
> Steffan
>
>
>
>
>
>
>
>
>
> ___
> Users mailing list
> Users@openvz.org
> https://lists.openvz.org/mailman/listinfo/users

--
tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users


___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2020-09-09 Thread jjs - mainphrame 
Thank you tranxene50, I've installed openvz-diff-backups on my ovz-7 hosts,
and so far it looks very promising.

Jake

On Tue, Sep 8, 2020 at 4:05 PM tranxene50 
wrote:

> Hello!
>
> Please forgive my bad English, I live in France.
>
> A few years ago, as a hobby in the beginning, I created a file based
> "incremental" backup tool (that heavily relies on rsync) :
> https://www.openvz-diff-backups.fr
>
> It works flawlessly with OpenVZ 6 but only have been rapidly tested with
> OpenVZ 7.
>
> The main difference between OpenVZ 6 and 7 is that memory dump
> (checkpoint) is now done using CRIU instead of OpenVZ "Legacy" kernel.
>
> But,  globally, the process is still the same: create a ploop snapshot,
> mount it, sync it (with rsync) and then create a "diff" backup (using
> rsync again with --link-dest).
>
> As far as I know, this is one of the rarest GPL tools (any hint
> appreciated!) able to backup/restore CT files and, most importantly,
> full memory state.
>
> Restoring a "live" backup is like resuming an OS (Windows, Linux, MacOS,
> etc) after it had been put to sleep: the container will resume and works
> again, just like nothing had happen.
>
> So you can cheat and pretend 100% uptime even if a container was down
> most of the time... (evidently this a joke and, please, do not play at
> this game: /var/log/* will betray you)
>
> Note: to migrate CT between OpenVZ 6 and 7, you must use "cold" backups
> because memory dumps are incompatible (OpenVZ Kernel vs CRIU).
>
> To answer your questions:
>
> 1) you can restore any previous backup because each one is considered as
> a full backup (no diff/incremental computing: it is just
> files/directories/other - and hard links)
>
> 2) because backups are just a bunch of files (and mostly hard links),
> you can easily browse any backup of a CT and copy any files/directories
> needed
>
> At the moment, development of openvz-diff-backups is on pause - because
> it fulfills all my needs with OpenVZ 6 - but I am in the process of
> moving to OpenVZ 7 in a few months.
>
> So, if you encounter a bug or an issue, please leave me a message: the
> tool has a very conservative approach and is designed to cleanly stop if
> anything unexpected/unknown/abnormal happens.
>
> Have a nice day!
>
> Le 08/09/2020 à 14:24, mailingl...@tikklik.nl a écrit :
> > Hello,
> >
> > Using openvz7
> > Im looking ad my backup strategy
> > I allways used rsync on openvz6
> > And looks like on openvz7 this can also be done on /vz/root/VEID
> > But i dont know if i can do a full restore from that...
> >
> >
> > Now im looking at snapshots
> > https://github.com/TamCore/vzpbackup
> > it can make full backups and incremental backups
> >
> > Is someone using this script?
> > i have some question hope someone can help
> >
> > the incremental backups are nice to save space and time on a remote
> > backupserver
> > But how does a restore works.
> > For what i know you can only restore a full snapshot, the incremental
> > backups have only the changed files
> >
> > Question 2.
> > Is it possible to extract a file from the backup for a single file
> restore?
> > And if so can someone tell me how?
> >
> >
> > Thanxs
> > Steffan
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@openvz.org
> > https://lists.openvz.org/mailman/listinfo/users
>
> --
> tranxene50
> tranxen...@openvz-diff-backups.fr
>
> ___
> Users mailing list
> Users@openvz.org
> https://lists.openvz.org/mailman/listinfo/users
>
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2020-09-08 Thread tranxene50 

Hello!

Please forgive my bad English, I live in France.

A few years ago, as a hobby in the beginning, I created a file based 
"incremental" backup tool (that heavily relies on rsync) : 
https://www.openvz-diff-backups.fr


It works flawlessly with OpenVZ 6 but only have been rapidly tested with 
OpenVZ 7.


The main difference between OpenVZ 6 and 7 is that memory dump 
(checkpoint) is now done using CRIU instead of OpenVZ "Legacy" kernel.


But,  globally, the process is still the same: create a ploop snapshot, 
mount it, sync it (with rsync) and then create a "diff" backup (using 
rsync again with --link-dest).


As far as I know, this is one of the rarest GPL tools (any hint 
appreciated!) able to backup/restore CT files and, most importantly, 
full memory state.


Restoring a "live" backup is like resuming an OS (Windows, Linux, MacOS, 
etc) after it had been put to sleep: the container will resume and works 
again, just like nothing had happen.


So you can cheat and pretend 100% uptime even if a container was down 
most of the time... (evidently this a joke and, please, do not play at 
this game: /var/log/* will betray you)


Note: to migrate CT between OpenVZ 6 and 7, you must use "cold" backups 
because memory dumps are incompatible (OpenVZ Kernel vs CRIU).


To answer your questions:

1) you can restore any previous backup because each one is considered as 
a full backup (no diff/incremental computing: it is just 
files/directories/other - and hard links)


2) because backups are just a bunch of files (and mostly hard links), 
you can easily browse any backup of a CT and copy any files/directories 
needed


At the moment, development of openvz-diff-backups is on pause - because 
it fulfills all my needs with OpenVZ 6 - but I am in the process of 
moving to OpenVZ 7 in a few months.


So, if you encounter a bug or an issue, please leave me a message: the 
tool has a very conservative approach and is designed to cleanly stop if 
anything unexpected/unknown/abnormal happens.


Have a nice day!

Le 08/09/2020 à 14:24, mailingl...@tikklik.nl a écrit :

Hello,

Using openvz7
Im looking ad my backup strategy
I allways used rsync on openvz6
And looks like on openvz7 this can also be done on /vz/root/VEID
But i dont know if i can do a full restore from that...


Now im looking at snapshots
https://github.com/TamCore/vzpbackup
it can make full backups and incremental backups

Is someone using this script?
i have some question hope someone can help

the incremental backups are nice to save space and time on a remote
backupserver
But how does a restore works.
For what i know you can only restore a full snapshot, the incremental
backups have only the changed files

Question 2.
Is it possible to extract a file from the backup for a single file restore?
And if so can someone tell me how?


Thanxs
Steffan









___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users


--
tranxene50
tranxen...@openvz-diff-backups.fr

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

[Users] Ploop Incremental backups strategy

2020-09-08 Thread mailinglist 
Hello,

Using openvz7
Im looking ad my backup strategy
I allways used rsync on openvz6
And looks like on openvz7 this can also be done on /vz/root/VEID
But i dont know if i can do a full restore from that...


Now im looking at snapshots
https://github.com/TamCore/vzpbackup
it can make full backups and incremental backups

Is someone using this script?
i have some question hope someone can help

the incremental backups are nice to save space and time on a remote
backupserver
But how does a restore works.
For what i know you can only restore a full snapshot, the incremental
backups have only the changed files

Question 2.
Is it possible to extract a file from the backup for a single file restore?
And if so can someone tell me how?


Thanxs 
Steffan









___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2015-05-01 Thread Steffan Noord 
Im using rsnapshot it creats incremental and full backups
So it does the same. I use it for years now.


-Oorspronkelijk bericht-
Van: users-boun...@openvz.org [mailto:users-boun...@openvz.org] Namens Pavel
Odintsov
Verzonden: donderdag 30 april 2015 22:11
Aan: OpenVZ users
Onderwerp: Re: [Users] Ploop Incremental backups strategy

Hello, folks!

I could recommend rdiff for incremental snapshots. It works fine for enough
small images but need patches in algorithm for huge snapshots.

On Thu, Apr 30, 2015 at 10:39 PM, Philipp Born  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I would say so. It gives you incremental and full backups. It misuses 
> snapshots for incremental backups, which has the downside of requiring 
> "a bit" more free diskspace on your node. But doing backups this way 
> is also faster than rsync'ing the whole container each time.
>
> I'm using my script now since seven months and so far I have no reason 
> to switch to something different. Before that I've tried pure 
> rsync'ing and stuff like rsnapshot, but I like it more this way.
>
> On 28.04.2015 11:12, Steffan Noord wrote:
>> Is this better then just rsync the container ?
>>
>>
>> -Oorspronkelijk bericht- Van: users-boun...@openvz.org 
>> [mailto:users-boun...@openvz.org] Namens Philipp Born Verzonden:
>> zaterdag 25 april 2015 14:23 Aan: users@openvz.org Onderwerp: Re:
>> [Users] Ploop Incremental backups strategy
>>
>> Hi,
>>
>> this is eactly what I'm doing. Have a look at 
>> https://github.com/TamCore/vzpbackup
>>
>> Regards Philipp
>>
>> On 01.04.2015 14:22, Simon Barrett wrote:
>>> Hi all,
>>
>>> Is there any reason why I should not create snapshot a ploop-backed 
>>> container each day (or hour, for that matter) then merge all 
>>> outstanding snapshots at the end of the week (vzctl
>>> snapshot-delete) and compact it?  This would allow me to do 
>>> efficient incremental backups to back up (using bacula, in this
>>> case) and I would imagine it's a core use case.
>>
>>> Are there any potential risks to be aware of (performance issues,  
>>> storage usage, corruption exposure)?
>>
>>> Regards,
>>
>>> Simon
>> ___ Users mailing list 
>> Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
>>
>> ___ Users mailing list 
>> Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
>>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJVQoTvAAoJEJrmlNhNgL+IsSAP+QHuflNO2aMWW8KM+K+kY1Rh
> 0ccz9dBFs6bBnCi7kAoVpXD9nvFRMctyPrU5heUmKIPFpDnmdJQIs+f7AIVoJ2vR
> A3ouO3wGyn4SPbUtNenxZxQfkhnTwJwaLsdVrnNb056lmLohG/tZCLvagG+iYfY3
> gypQFzcQlIiXPZJeFaFRDY+YWC4lLRiDBCdU4iKcAr5YxYjWxgZMtTbMw7f9FsbP
> faW3Uofnm+vGTkflUp3kvisGX3Y/EB7n9+FV37jbAyLnk8GhXcnZsECwmVFV5A53
> 6/fNhvh3ZuV2r4zqcRab8XgrAnmRMdQVFdTP21XdBpvlC5Je0opfWB+M4ATJOAUW
> 8HVi0KpIz8S35/qmfBSWo6cmwixhmkOI/IqBJ7rod5VzZFmQQoXJgSNdKOQ3aEK+
> fbxtSmXlLST/xcYiTkQPKYVflVpBzA6Lli0bVQAiYPxo1fqxx5iu9eUdqWk1nx3K
> VbS2AcJNb41OiSLenAn39ICPXIZD1QdFnTrh7X6oevVCpkOKUbbDO8eWBk46owu6
> uK659gVn3xxq+O2Tle31/119UD7fJ264MmZTykJqkidxr1oXcVoMyLgaoS4sbab+
> o/HSGt9iYtII3ANSgv0Tr5D9MscmfaykMHnAz9eWVu7aOIqO1ZFJAX+OBSV6iOwd
> hFBiNW9cYQ2nBJlAqmvi
> =/YzI
> -END PGP SIGNATURE-
> ___
> Users mailing list
> Users@openvz.org
> https://lists.openvz.org/mailman/listinfo/users



--
Sincerely yours, Pavel Odintsov
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2015-04-30 Thread Pavel Odintsov 
Hello, folks!

I could recommend rdiff for incremental snapshots. It works fine for
enough small images but need patches in algorithm for huge snapshots.

On Thu, Apr 30, 2015 at 10:39 PM, Philipp Born  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I would say so. It gives you incremental and full backups. It misuses
> snapshots for incremental backups, which has the downside of requiring
> "a bit" more free diskspace on your node. But doing backups this way
> is also faster than rsync'ing the whole container each time.
>
> I'm using my script now since seven months and so far I have no reason
> to switch to something different. Before that I've tried pure
> rsync'ing and stuff like rsnapshot, but I like it more this way.
>
> On 28.04.2015 11:12, Steffan Noord wrote:
>> Is this better then just rsync the container ?
>>
>>
>> -Oorspronkelijk bericht- Van: users-boun...@openvz.org
>> [mailto:users-boun...@openvz.org] Namens Philipp Born Verzonden:
>> zaterdag 25 april 2015 14:23 Aan: users@openvz.org Onderwerp: Re:
>> [Users] Ploop Incremental backups strategy
>>
>> Hi,
>>
>> this is eactly what I'm doing. Have a look at
>> https://github.com/TamCore/vzpbackup
>>
>> Regards Philipp
>>
>> On 01.04.2015 14:22, Simon Barrett wrote:
>>> Hi all,
>>
>>> Is there any reason why I should not create snapshot a
>>> ploop-backed container each day (or hour, for that matter) then
>>> merge all outstanding snapshots at the end of the week (vzctl
>>> snapshot-delete) and compact it?  This would allow me to do
>>> efficient incremental backups to back up (using bacula, in this
>>> case) and I would imagine it's a core use case.
>>
>>> Are there any potential risks to be aware of (performance issues,
>>>  storage usage, corruption exposure)?
>>
>>> Regards,
>>
>>> Simon
>> ___ Users mailing list
>> Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
>>
>> ___ Users mailing list
>> Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
>>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJVQoTvAAoJEJrmlNhNgL+IsSAP+QHuflNO2aMWW8KM+K+kY1Rh
> 0ccz9dBFs6bBnCi7kAoVpXD9nvFRMctyPrU5heUmKIPFpDnmdJQIs+f7AIVoJ2vR
> A3ouO3wGyn4SPbUtNenxZxQfkhnTwJwaLsdVrnNb056lmLohG/tZCLvagG+iYfY3
> gypQFzcQlIiXPZJeFaFRDY+YWC4lLRiDBCdU4iKcAr5YxYjWxgZMtTbMw7f9FsbP
> faW3Uofnm+vGTkflUp3kvisGX3Y/EB7n9+FV37jbAyLnk8GhXcnZsECwmVFV5A53
> 6/fNhvh3ZuV2r4zqcRab8XgrAnmRMdQVFdTP21XdBpvlC5Je0opfWB+M4ATJOAUW
> 8HVi0KpIz8S35/qmfBSWo6cmwixhmkOI/IqBJ7rod5VzZFmQQoXJgSNdKOQ3aEK+
> fbxtSmXlLST/xcYiTkQPKYVflVpBzA6Lli0bVQAiYPxo1fqxx5iu9eUdqWk1nx3K
> VbS2AcJNb41OiSLenAn39ICPXIZD1QdFnTrh7X6oevVCpkOKUbbDO8eWBk46owu6
> uK659gVn3xxq+O2Tle31/119UD7fJ264MmZTykJqkidxr1oXcVoMyLgaoS4sbab+
> o/HSGt9iYtII3ANSgv0Tr5D9MscmfaykMHnAz9eWVu7aOIqO1ZFJAX+OBSV6iOwd
> hFBiNW9cYQ2nBJlAqmvi
> =/YzI
> -END PGP SIGNATURE-
> ___
> Users mailing list
> Users@openvz.org
> https://lists.openvz.org/mailman/listinfo/users



-- 
Sincerely yours, Pavel Odintsov
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2015-04-30 Thread Philipp Born 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I would say so. It gives you incremental and full backups. It misuses
snapshots for incremental backups, which has the downside of requiring
"a bit" more free diskspace on your node. But doing backups this way
is also faster than rsync'ing the whole container each time.

I'm using my script now since seven months and so far I have no reason
to switch to something different. Before that I've tried pure
rsync'ing and stuff like rsnapshot, but I like it more this way.

On 28.04.2015 11:12, Steffan Noord wrote:
> Is this better then just rsync the container ?
> 
> 
> -Oorspronkelijk bericht- Van: users-boun...@openvz.org
> [mailto:users-boun...@openvz.org] Namens Philipp Born Verzonden:
> zaterdag 25 april 2015 14:23 Aan: users@openvz.org Onderwerp: Re:
> [Users] Ploop Incremental backups strategy
> 
> Hi,
> 
> this is eactly what I'm doing. Have a look at 
> https://github.com/TamCore/vzpbackup
> 
> Regards Philipp
> 
> On 01.04.2015 14:22, Simon Barrett wrote:
>> Hi all,
> 
>> Is there any reason why I should not create snapshot a
>> ploop-backed container each day (or hour, for that matter) then
>> merge all outstanding snapshots at the end of the week (vzctl 
>> snapshot-delete) and compact it?  This would allow me to do
>> efficient incremental backups to back up (using bacula, in this 
>> case) and I would imagine it's a core use case.
> 
>> Are there any potential risks to be aware of (performance issues,
>>  storage usage, corruption exposure)?
> 
>> Regards,
> 
>> Simon
> ___ Users mailing list 
> Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
> 
> ___ Users mailing list 
> Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJVQoTvAAoJEJrmlNhNgL+IsSAP+QHuflNO2aMWW8KM+K+kY1Rh
0ccz9dBFs6bBnCi7kAoVpXD9nvFRMctyPrU5heUmKIPFpDnmdJQIs+f7AIVoJ2vR
A3ouO3wGyn4SPbUtNenxZxQfkhnTwJwaLsdVrnNb056lmLohG/tZCLvagG+iYfY3
gypQFzcQlIiXPZJeFaFRDY+YWC4lLRiDBCdU4iKcAr5YxYjWxgZMtTbMw7f9FsbP
faW3Uofnm+vGTkflUp3kvisGX3Y/EB7n9+FV37jbAyLnk8GhXcnZsECwmVFV5A53
6/fNhvh3ZuV2r4zqcRab8XgrAnmRMdQVFdTP21XdBpvlC5Je0opfWB+M4ATJOAUW
8HVi0KpIz8S35/qmfBSWo6cmwixhmkOI/IqBJ7rod5VzZFmQQoXJgSNdKOQ3aEK+
fbxtSmXlLST/xcYiTkQPKYVflVpBzA6Lli0bVQAiYPxo1fqxx5iu9eUdqWk1nx3K
VbS2AcJNb41OiSLenAn39ICPXIZD1QdFnTrh7X6oevVCpkOKUbbDO8eWBk46owu6
uK659gVn3xxq+O2Tle31/119UD7fJ264MmZTykJqkidxr1oXcVoMyLgaoS4sbab+
o/HSGt9iYtII3ANSgv0Tr5D9MscmfaykMHnAz9eWVu7aOIqO1ZFJAX+OBSV6iOwd
hFBiNW9cYQ2nBJlAqmvi
=/YzI
-END PGP SIGNATURE-
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2015-04-28 Thread Steffan Noord 
Is this better then just rsync the container ?


-Oorspronkelijk bericht-
Van: users-boun...@openvz.org [mailto:users-boun...@openvz.org] Namens
Philipp Born
Verzonden: zaterdag 25 april 2015 14:23
Aan: users@openvz.org
Onderwerp: Re: [Users] Ploop Incremental backups strategy

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

this is eactly what I'm doing. Have a look at
https://github.com/TamCore/vzpbackup

Regards
Philipp

On 01.04.2015 14:22, Simon Barrett wrote:
> Hi all,
> 
> Is there any reason why I should not create snapshot a ploop-backed 
> container each day (or hour, for that matter) then merge all 
> outstanding snapshots at the end of the week (vzctl
> snapshot-delete) and compact it?  This would allow me to do efficient 
> incremental backups to back up (using bacula, in this
> case) and I would imagine it's a core use case.
> 
> Are there any potential risks to be aware of (performance issues, 
> storage usage, corruption exposure)?
> 
> Regards,
> 
> Simon
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJVO4cFAAoJEJrmlNhNgL+I5BoP/A4kWlmhOyxj/VoBTASmqlvR
DNpyiBm6pSRnRn7gK596gUEu22q0U8Ms3jLxc1TFZANEg7IHy//6bAiorQBgluUB
n6S7NDG+LYWMjxMmPVplV4co9NGoWgiaOAG1EQmOWGNmElgZ3U9txosdJNmx4XUE
mB6dVkMlZPz1TZzpm+Iyh/r2xoPuMUO4SeITXGZ58BfobP++uOILUuOwnWJ1nGK/
j9xRzarl9d90O+f5HwPDhvrYR8eQl1h3vFSqw7eYpUFSP2lzWruGgXEYS9oe8ht8
gAHyMgw84aBk3PPMZZugwASDQOhLGvMYZ0J6U4njc5r1NLwA8zfddrvaMCntJms7
dBnKced9dObgwgz3qb00asqtG5u5O/P+1XCxExDKGyLgO+uUkVpOObnx/DXD6YbM
kOTMvlvPD083dW4Kx5wqWxgxz8oNdVS7ro87QtyLZpqpHQE9ZgYzDPPi1qjDjZ/H
m9Zw9Yy7FyrNDz/TC+9HlnglmsanP31j0IpkKYkmNWYBsUqM5nhteBmc+Q/D2dpp
J3s9FL8srHorYNAvRmm9pejNXClNbENBw4O5NqMO3/UV2Y5o9Or7eMa1s7tZRZvK
JKZV1Vz1PkkiGgj8zngjKQPB6tmkrGUaW1feOfaVEnS0oGZE7xFVfm0Csy2PbXSO
160ejbYU7DQS+BVFyPcO
=zwFJ
-END PGP SIGNATURE-
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2015-04-25 Thread Philipp Born 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

this is eactly what I'm doing. Have a look at
https://github.com/TamCore/vzpbackup

Regards
Philipp

On 01.04.2015 14:22, Simon Barrett wrote:
> Hi all,
> 
> Is there any reason why I should not create snapshot a
> ploop-backed container each day (or hour, for that matter) then
> merge all outstanding snapshots at the end of the week (vzctl
> snapshot-delete) and compact it?  This would allow me to do
> efficient incremental backups to back up (using bacula, in this
> case) and I would imagine it's a core use case.
> 
> Are there any potential risks to be aware of (performance issues, 
> storage usage, corruption exposure)?
> 
> Regards,
> 
> Simon
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJVO4cFAAoJEJrmlNhNgL+I5BoP/A4kWlmhOyxj/VoBTASmqlvR
DNpyiBm6pSRnRn7gK596gUEu22q0U8Ms3jLxc1TFZANEg7IHy//6bAiorQBgluUB
n6S7NDG+LYWMjxMmPVplV4co9NGoWgiaOAG1EQmOWGNmElgZ3U9txosdJNmx4XUE
mB6dVkMlZPz1TZzpm+Iyh/r2xoPuMUO4SeITXGZ58BfobP++uOILUuOwnWJ1nGK/
j9xRzarl9d90O+f5HwPDhvrYR8eQl1h3vFSqw7eYpUFSP2lzWruGgXEYS9oe8ht8
gAHyMgw84aBk3PPMZZugwASDQOhLGvMYZ0J6U4njc5r1NLwA8zfddrvaMCntJms7
dBnKced9dObgwgz3qb00asqtG5u5O/P+1XCxExDKGyLgO+uUkVpOObnx/DXD6YbM
kOTMvlvPD083dW4Kx5wqWxgxz8oNdVS7ro87QtyLZpqpHQE9ZgYzDPPi1qjDjZ/H
m9Zw9Yy7FyrNDz/TC+9HlnglmsanP31j0IpkKYkmNWYBsUqM5nhteBmc+Q/D2dpp
J3s9FL8srHorYNAvRmm9pejNXClNbENBw4O5NqMO3/UV2Y5o9Or7eMa1s7tZRZvK
JKZV1Vz1PkkiGgj8zngjKQPB6tmkrGUaW1feOfaVEnS0oGZE7xFVfm0Csy2PbXSO
160ejbYU7DQS+BVFyPcO
=zwFJ
-END PGP SIGNATURE-
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2015-04-01 Thread Kir Kolyshkin 



On 04/01/2015 05:22 AM, Simon Barrett wrote:

Hi all,

Is there any reason why I should not create snapshot a ploop-backed 
container each day (or hour, for that matter) then merge all 
outstanding snapshots at the end of the week (vzctl snapshot-delete) 
and compact it?  This would allow me to do efficient incremental 
backups to back up (using bacula, in this case) and I would imagine 
it's a core use case.


Are there any potential risks to be aware of (performance issues, 
storage usage, corruption exposure)?


I am not aware of any, except a limitation of no more than 126 deltas 
mounted
(i.e. the distance from top to base delta should be < 127). If you try 
to hit the limit,
snapshot won't be created. So, hourly snapshots with weekly delete won't 
work, as

24*7 > 127.
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] Ploop Incremental backups strategy

2015-04-01 Thread Scott Dowdle 
Greetings,

- Original Message -
> Is there any reason why I should not create snapshot a ploop-backed
> container each day (or hour, for that matter) then merge all
> outstanding snapshots at the end of the week (vzctl snapshot-delete)
> and compact it? This would allow me to do efficient incremental
> backups to back up (using bacula, in this case) and I would imagine
> it's a core use case.
> 
> Are there any potential risks to be aware of (performance issues,
> storage usage, corruption exposure)?

People do backups differently.  If that's the strategy that works for you, go 
for it.  After doing it a while, feel free to update the ploop backup wiki 
page.  I haven't done it the way you propose and I don't use backula... so I 
can't answer you. I prefer to do file-based backups rather than copying image 
files... and just rsync.

I'm guessing you have already looked at it but here's the wiki page:

https://wiki.openvz.org/Ploop/Backup

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

[Users] Ploop Incremental backups strategy

2015-04-01 Thread Simon Barrett 
Hi all,

Is there any reason why I should not create snapshot a ploop-backed
container each day (or hour, for that matter) then merge all outstanding
snapshots at the end of the week (vzctl snapshot-delete) and compact it?
This would allow me to do efficient incremental backups to back up (using
bacula, in this case) and I would imagine it's a core use case.

Are there any potential risks to be aware of (performance issues, storage
usage, corruption exposure)?

Regards,

Simon
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users