ZxBackup import problem
Results 1 to 4 of 4

Thread: ZxBackup import problem

  1. #1
    Junior Member
    Join Date
    Jan 2014

    ZxBackup import problem

    Hello guys.

    First of all thanks for this amazing tool called ZxMig

    Well I have a problem using ZxMig to export the data and using ZxBackup to import the backup, it's taking too long check the following data:

    zimbra@celebrimor3:/root$ zxsuite backup getAllOperations

    name ExternalRestore
    descName External Restore
    id c9d8dab9-d3a0-49a7-afa2-1c718631834e
    state started
    host celebrimor3.adsender.spc
    startTime 17/01/2014 18:09:04 CET

    And when I try to monitor the progress it seems to be a loop:

    zimbra@celebrimor3:/root$ zxsuite backup monitor c9d8dab9-d3a0-49a7-afa2-1c718631834e

    Operation log path: /opt/zimbra/log/zextras_ZxBackup_ExternalRestore_c9d8dab9-d3a0-49a7-afa2-1c718631834e.log
    Warnings/Errors: 76/0
    Restored Accounts(only attributes): 148/148
    Restored Accounts(common items): 69/148
    Restored Accounts(only shared & datasources): 0/148
    Current Account: username@mydomain.com
    Restored/Skipped Items: 662000/386
    Unrestored Items: 40

    It started on 17/01/2014 and it still running. The size of the data is not so big.

    thank you.

  2. #2
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Hello damasceno,
    welcome to the forums and thank you for your kind words!

    Import performances are greatly affected by your server's resources, and especially by I/O throughput. I suggest to keep an eye on your server's load and ram/swap usage, and to check your I/O status using iostat to verify if there's any bottleneck slowing the operation.
    If your server runs on a virtual environment, also make sure that there are no resource limitations for the Zimbra VM.

    Out of curiosity (since it's not possible to give an estimate), may I ask what's the size of the exported data and what are your server's specs? CPUs, RAM, storage system...

    Have a nice day,
    the ZeXtras Team

  3. #3
    Junior Member
    Join Date
    Jan 2014
    Hello Cine! Thank you

    yes I'm running Zimbra on Xen.

    I'm migrating from Zimbra 8.0.6 (Ubuntu 10.04) to Zimbra 8.0.6 (Ubuntu 12.04), these are the configuration of the VM:

    - Memory: 8 GB
    - Processor: 12
    - Hard Disk: 600 GB

    I checked if there was I/O errors using htop but there isn't. I'm trying to understand why it's taking so long... Now I checked and it's importing another account but still it's very slow, check the current status of the server:

    zimbra@celebrimor3:~/backup$ free -m
    total used free shared buffers cached
    Mem: 7951 7823 128 0 393 4095
    -/+ buffers/cache: 3334 4616
    Swap: 127 127 0

    CPU Percentage: 12%

    zimbra@celebrimor3:~/backup$ df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/xvda2 709G 177G 497G 27% /
    udev 3.9G 4.0K 3.9G 1% /dev
    tmpfs 1.6G 144K 1.6G 1% /run
    none 5.0M 0 5.0M 0% /run/lock
    none 3.9G 0 3.9G 0% /run/shm

    And the server is not slow I can access with no problem. :/

    Thanks for your help.

  4. #4
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Hello damasceno!

    Some suggestion to improve your import speed:

    - Make sure that zimbra's Heap Size is set to at least 20% the size of the total ram on the system (you should have received a ZeXtras Suite Notification if the value was lower than this thereshold).
    - I'm not aware of any htop option thar can be of use to monitor your storage in a case like this... Use `dmesg` to check for disk errors and `iostat -xm 1` to monitor the I/O load (let it run for 20-30 seconds).
    - Add some swap and set the swappiness to "0" (as root: `sysctl vm.swappiness=0`).
    - If you can, always store the data you are going to import on a different physical disk than the one containing your Zimbra volume(s).

    You didn't specify the type of storage you are using, the eventual raid configuration and how it's connected to the hypervisor, but if you are using a nework storage make sure there are no bottleneks there too.

    Have a nice day,


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts