Bug 81 - Full backup too long
Summary: Full backup too long
Status: CONFIRMED
Alias: None
Product: ZeXtras
Classification: Unclassified
Component: ZxBackup (show other bugs)
Version: 1.8.9
Hardware: -- CentOS 6 - 64bit
: Normal enhancement
Assignee: ZeXtras Bugzilla Admin
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2013-06-22 19:23 CEST by prod-info
Modified: 2013-08-18 14:31 CEST (History)
2 users (show)

See Also:
Browser: ---
Zimlet Chat version: ---
Zimbra Version: 7.2.3


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description prod-info 2013-06-22 19:23:15 CEST
Hello,
I have installed Zextra backup to add hot-backup of 400Gb of data
(3 000 000 files):
The full backup is very very long:
When I check the data, it seems they are compressed using gzip.
Maybe in future version, an option like "compress using lzo" or "no compression" could be a good way to speed up the first full backup?
If this is not possible, an option like "rebuild full backup using smartbackup" could be a good way to speed up the process :-)

Best Regards,

js.
Comment 1 Cine 2013-06-25 15:14:19 CEST
Thank you for your time, the R&D and Dev team have been notified of your suggestion.

Regards,
the ZeXtras Team
Comment 2 prod-info 2013-08-18 14:30:57 CEST
Actuel situation:

460 Go of Data, 3,5 billion of files
external storage: smb share on a 1Gb connexion.
Time to do a full backup: 11 hours:
- stats -
                   new accounts: 0
               accounts updated: 2
       skipped accounts(by COS): 0
                   item updated: 6117
                   new metadata: 3237
                      new files: 2171
                  checked items: 3417836
                    backup path: /mnt/backup/zimbra/backup
                  skipped items: 0
              num skipped files: 0
             I/O read exception: 0
                      items/sec: 86.68538

Problems:
1/To slow
2/In case of complete restore, we don't know
how much time it will take to complete

Solutions:
1/Change compression for LZO or "no compression"
2/Change the backup mechanism: avoid transfer of small files
(less than 20Mb): maybe a "database like" store could be
a good solution? It's far better when we upload files to a
network share.

Thank you for your help :)
Regards,

js.