Unidentified Backup from NethServer


(Hitesh Dubey) #1

I have some misunderstand related to Backup Module in NS. I have set NFS server on NS and shared 1 directory Eg. - ( /backup ) and i have set Incremental Backup + Full Backup on Sunday.
but when i see in /backup everyday its creating a lot of backup files so we are not able to understand
which is our authentic backup.
SO please Help us to understand, How it takes Backup which backup is authentic and why it is creating everytime new backup files.

root@mc # ll /backup
-rw- nfsnobody nfsnobody 262090662 Nov 29 23:39 duplicity-full.20151129T170114Z.vol985.difftar.gz
-rw-1 nfsnobody nfsnobody 262122544 Nov 29 23:40 duplicity-full.20151129T170114Z.vol986.difftar.gz
-rw-1 nfsnobody nfsnobody 262103378 Nov 29 23:40 duplicity-full.20151129T170114Z.vol987.difftar.gz
-rw- 1 nfsnobody nfsnobody 262101379 Nov 29 23:40 duplicity-full.20151129T170114Z.vol988.difftar.gz
-rw- 1 nfsnobody nfsnobody 262119630 Nov 29 23:41 duplicity-full.20151129T170114Z.vol989.difftar.gz
-rw- 1 nfsnobody nfsnobody 262119660 Nov 29 18:39 duplicity-full.20151129T170114Z.vol98.difftar.gz
-rw- 1 nfsnobody nfsnobody 262090348 Nov 29 23:41 duplicity-full.20151129T170114Z.vol990.difftar.gz
-rw–1 nfsnobody nfsnobody 262105403 Nov 29 23:42 duplicity-full.20151129T170114Z.vol991.difftar.gz
-rw–1 nfsnobody nfsnobody 262091883 Nov 29 23:42 duplicity-full.20151129T170114Z.vol992.difftar.gz
-rw–1 nfsnobody nfsnobody 262101944 Nov 29 23:42 duplicity-full.20151129T170114Z.vol993.difftar.gz
-rw- 1 nfsnobody nfsnobody 262132530 Nov 29 23:43 duplicity-full.20151129T170114Z.vol994.difftar.gz
-rw- 1 nfsnobody nfsnobody 262092980 Nov 29 23:43 duplicity-full.20151129T170114Z.vol995.difftar.gz
-rw-1 nfsnobody nfsnobody 262100488 Nov 29 23:43 duplicity-full.20151129T170114Z.vol996.difftar.gz
-rw-1 nfsnobody nfsnobody 262093581 Nov 29 23:44 duplicity-full.20151129T170114Z.vol997.difftar.gz
-rw-1 nfsnobody nfsnobody 262103048 Nov 29 23:44 duplicity-full.20151129T170114Z.vol998.difftar.gz
-rw-1 nfsnobody nfsnobody 262109360 Nov 29 23:45 duplicity-full.20151129T170114Z.vol999.difftar.gz
-rw-1 nfsnobody nfsnobody 262113039 Nov 29 18:39 duplicity-full.20151129T170114Z.vol99.difftar.gz
-rw-1 nfsnobody nfsnobody 262122595 Nov 29 18:04 duplicity-full.20151129T170114Z.vol9.difftar.gz
rw–1 nfsnobody nfsnobody 4251918427 Nov 30 01:50 duplicity-full-signatures.20151129T170114Z.sigtar.gz

and also tell us what it means of duplicity -full and dfftar, and sigtar ?


(Alessio Fattorini) #2

It’s the same backup but it’s split into different files, in your example your backup is duplicity-full.20151129T170114Z full backup executed on 29 Nov

(Hitesh Dubey) #3

Dear alefattorini,

Thanks for your valuable reply.

but i don’t understand, if i create 1 full backup and it creates 200 Files for backup. So at the time of restoration we have to select 200 files for restore.
what kind of backup philosophy is this ?
i have done full backup then it created 200 tar backup files, then i set incremental backup and set sunday for full backup with 1 week retention policy but we are not able to identify which backup is Full or which backup is incremented.

So please give us an idea about this in brief and tell whether we can restore this backup ?


(Alessio Fattorini) #4

Why select? Check this

restore a file

restore-file / /var/lib/nethserver/vmail/test

Restore the system


Very simple :smile: and you can use web interface too

(Hitesh Dubey) #5

Dear Alefattorini,

200 Tar files backup is like this "duplicity-full.20151129T170114Z.vol998.difftar.gz"
so now how i ll restore this, and also not identified which one is incremental backup.

Is there any other way to take backup like Eg. - Rsync

and also tell us how to take backup of owncloud ?


(Giacomo Sanchietti) #6

The backup is split in chunks of fixed size; this is how duplicity works: http://duplicity.nongnu.org/features.html

How to Restore Tar Backup in NethServer
(Stefano) #7

I guess/hope you meant:


or do you expect Hitesh to read the italian page? :smiley:

(Alessio Fattorini) #8

Yep that’s the proper link!