ZxBackup Operation Purge failed on some mailbox servers
Page 1 of 2 12 LastLast
Results 1 to 10 of 18
Like Tree2Likes

Thread: ZxBackup Operation Purge failed on some mailbox servers

  1. #1
    Senior Member
    Join Date
    Oct 2013
    Posts
    70

    ZxBackup Operation Purge failed on some mailbox servers

    We have a multi-server installation running CentOS 6 x86_64 on 17 Zimbra servers of which 9 are mailbox servers.
    We run Zimbra 8.0.4 OSE and ZeXtras 1.8.17.

    I got the following notification errors from the Purge operation on two of our mailbox servers (on other servers it completed successfully)...
    Code:
    This is an automated notification from ZxBackup about Purge.
    
    Operation Purge Failed.
    
    Operation Id: cc186f64-3619-4c7c-9f3a-48300d91f97d
    Operation Host: zm-mbox-01.cloud
    Scheduled operation
    
    ZeXtras Version: 1.8.17
    ZeXtras commit: 3b7a8649b068d66a838dccbab045261aa8f9c19c
    Zimbra version: 8.0.4_GA_5737 20130524120036 20130524-1204 FOSS
    
    
    -- exceptions --
    - Blocking operation error: For input string: "149040~0"
    Last progress info:
    
    
    
    This is an automated notification from ZxBackup about Purge.
    
    Operation Purge Failed.
    
    Operation Id: c34bcf88-a622-46be-a4b5-65943936c2e1
    Operation Host: zm-mbox-02.cloud
    Scheduled operation
    
    ZeXtras Version: 1.8.17
    ZeXtras commit: 3b7a8649b068d66a838dccbab045261aa8f9c19c
    Zimbra version: 8.0.4_GA_5737 20130524120036 20130524-1204 FOSS
    
    
    -- exceptions --
    - Blocking operation error: For input string: "6547.d~0"
    Last progress info:
    Any hints?

  2. #2
    Jay
    Jay is offline
    Code Master ZeXtras Employee
    Join Date
    May 2011
    Posts
    26
    Which file system are you using?
    ZeXtras doesn't write files with "~0", my guess is that the path was cut by the file system because it was too long.

    Regards,
    Jay
    ZeXtras Website # ZeXtras Wiki # ZeXtras Store

    Head of ZeXtras Suite Developers

  3. #3
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Quote Originally Posted by Jay View Post
    Which file system are you using?
    ZeXtras doesn't write files with "~0", my guess is that the path was cut by the file system because it was too long.
    ext4 mounted over NFS.

    About 290 files with ~ in the filename exist in this backuppath ...
    Code:
    [root@klnbmed02 zm-MBCP]# find zm-mbox-02.cloud/ -name '*~*'
    zm-mbox-02.cloud/accounts/ee7fcec3-987a-4deb-b722-0d7b0d28ff0f/items/47/6547.d~0
    zm-mbox-02.cloud/accounts/ee7fcec3-987a-4deb-b722-0d7b0d28ff0f/items/47/42147~0
    ...
    zm-mbox-02.cloud/accounts/ee7fcec3-987a-4deb-b722-0d7b0d28ff0f/items/88/6988.d~0
    zm-mbox-02.cloud/accounts/ee7fcec3-987a-4deb-b722-0d7b0d28ff0f/items/88/8588.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/68/6868.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/68/22~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/68/5168.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/5463.d~0
    ...
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/1763.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/9363.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/4163.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/2663.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/3863.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/5263.d~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/17963.del~0
    zm-mbox-02.cloud/accounts/da7a86f4-8a29-4771-bbe1-2ddd06f0d64b/items/63/2563.d~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/71/74~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/71/71~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/69/30769~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/77/36~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/77/92~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/77/30777~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/77/1377.d~0
    zm-mbox-02.cloud/accounts/222ebf1a-05e2-422c-9c0d-f6ecf0fd7fa3/items/77/1277.d~0
    
    [root@klnbmed02 zm-MBCP]# ls -l zm-mbox-02.cloud/accounts/ee7fcec3-987a-4deb-b722-0d7b0d28ff0f/items/47/6547.d~0
    -rw-r-----. 1 zimbra zimbra 2937 Oct 29  2013 zm-mbox-02.cloud/accounts/ee7fcec3-987a-4deb-b722-0d7b0d28ff0f/items/47/6547.d~0
    
    [root@klnbmed02 zm-MBCP]# cat zm-mbox-02.cloud/accounts/ee7fcec3-987a-4deb-b722-0d7b0d28ff0f/items/47/6547.d~0 
    [{"start_date":1382102831272,"type":"message","metadata":"d2:dci1382102829e4:dgst44:d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=2:dti1379418516e2:fgi0e3:fidi6084e2:idi6547e3:idxi6547e4:imapi6547e3:loc1:14:meta260:d1:f153:Issue ( View Online ) Key: IPENGRPM-835 Issue Type: [IPENG RPM New Issue] IPENG RPM New Issue Status: [Open] Open Priority: [Normal] Normal Assignee: ...1:p7:[JIRA] 1:s50:\"(JIRA) ggia@xx.gr\" <jira-reply@xx.gr>1:t17:pparb@xx.gr1:vi10ee4:modci11340e4:modmi11340e3:pidi6235e3:sbj77:(IPENGRPM-835) Commented: Ενεργοποίηση νέων ASA firewalls στο DCN του pop KLN2:szi15303e2:tpi5e2:uci0e1:vi10ee","digest":"d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=","end_date":1382137289980},{"start_date":1382137289980,"type":"message","metadata":"d2:dci1382102829e4:dgst44:d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=2:dti1379418516e2:fgi0e3:fidi6084e2:idi6547e3:idxi6547e4:imapi6547e3:loc1:34:meta260:d1:f153:Issue ( View Online ) Key: IPENGRPM-835 Issue Type: [IPENG RPM New Issue] IPENG RPM New Issue Status: [Open] Open Priority: [Normal] Normal Assignee: ...1:p7:[JIRA] 1:s50:\"(JIRA) ggia@xx.gr\" <jira-reply@xx.gr>1:t17:pparb@xx.gr1:vi10ee4:modci11340e4:modmi11340e3:pidi6235e3:sbj77:(IPENGRPM-835) Commented: Ενεργοποίηση νέων ASA firewalls στο DCN του pop KLN2:szi15303e2:tpi5e2:uci0e1:vi10ee","digest":"d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=","end_date":1383080774805},{"start_date":1383080774805,"type":"message","metadata":"d2:dci1383080772e4:dgst44:d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=2:dti1379418516e2:fgi144e3:fidi6084e2:idi6547e3:idxi6547e4:imapi6547e3:loc1:34:meta260:d1:f153:Issue ( View Online ) Key: IPENGRPM-835 Issue Type: [IPENG RPM New Issue] IPENG RPM New Issue Status: [Open] Open Priority: [Normal] Normal Assignee: ...1:p7:[JIRA] 1:s50:\"(JIRA) ggia@xx.gr\" <jira-reply@xx.gr>1:t17:pparb@xx.gr1:vi10ee4:modci11340e4:modmi81071e3:pidi-6547e3:sbj77:(IPENGRPM-835) Commented: Ενεργοποίηση νέων ASA firewalls στο DCN του pop KLN2:szi15303e2:tpi5e2:uci0e1:vi10ee","digest":"d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=","end_date":1383081773134},{"start_date":1383081773134,"type":"message","metadata":"d2:dci1383080772e4:dgst44:d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=2:dti1379418516e2:fgi144e3:fidi6084e2:idi6547e3:idxi6547e4:imapi6547e3:loc1:34:meta260:d1:f153:Issue ( View Online ) Key: IPENGRPM-835 Issue Type: [IPENG RPM New Issue] IPENG RPM New Issue Status: [Open] Open Priority: [Normal] Normal Assignee: ...1:p7:[JIRA] 1:s50:\"(JIRA) ggia@xx.gr\" <jira-reply@xx.gr>1:t17:pparb@xx.gr1:vi10ee4:modci11340e4:modmi81071e3:pidi-6547e3:sbj77:(IPENGRPM-835) Commented: Ενεργοποίηση νέων ASA firewalls στο DCN του pop KLN2:szi15303e2:tpi5e2:uci0e1:vi10ee","digest":"d6Hq1l6CrrjjX3RrLeisnSD,08iHQv63duQ7t6EwZaE=","deleted":true}][root@klnbmed02 zm-MBCP]# 
    [root@klnbmed02 zm-MBCP]#
    Further looking at these files, their timestamp is oct/nov 2013..
    So maybe a previous version of ZeXtras wrote them..
    Anyway, they are far older than 30 days that is our current retention, so I suppose that purge would delete them (if it didn't exit with fatal error).
    Is it safe to delete them from the filesystem now?
    Can we also make ZeXtras not exit with a fatal error if they exist in backuppath?
    Last edited by stsimb; 08-25-2014 at 06:39 PM.

  4. #4
    Jay
    Jay is offline
    Code Master ZeXtras Employee
    Join Date
    May 2011
    Posts
    26
    Quote Originally Posted by stsimb View Post
    Further looking at these files, their timestamp is oct/nov 2013..
    So maybe a previous version of ZeXtras wrote them..
    I'm sure ZeXtras doesn't use this "~0", maybe NFS driver under some circumstances.

    Quote Originally Posted by stsimb View Post
    Anyway, they are far older than 30 days that is our current retention, so I suppose that purge would delete them (if it didn't exit with fatal error).
    Is it safe to delete them from the filesystem now?
    Yes it is safe, but purge won't be able to delete related emails, they will be there for the time being.

    If you are ok with losing ~290 * ~0.3MB per email = ~87MB and it's not worth your time you could just remove "~0" files, otherwise you can check which and how many emails are in this state by running

    Code:
    zxsuite backup doCoherencyCheck /my/backup/path
    This command must be ran with real time scanner disabled and smart scan disabled, it read backup several times and it takes a long time.

    Quote Originally Posted by stsimb View Post
    Can we also make ZeXtras not exit with a fatal error if they exist in backuppath?
    We could, we are considering it, but by doing so we may hide problems.

    Regards,
    Jay
    ZeXtras Website # ZeXtras Wiki # ZeXtras Store

    Head of ZeXtras Suite Developers

  5. #5
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Quote Originally Posted by Jay View Post
    Code:
    zxsuite backup doCoherencyCheck /my/backup/path
    This command must be ran with real time scanner disabled and smart scan disabled, it read backup several times and it takes a long time.
    I stopped smartScan and RealTime Scanner.
    The filenames with "~" character were in directories with zimbra Ids.
    I mapped zimbra IDs to usernames, and I started a coherencyCheck only for the 3 accounts in which I found filenames with "~" character (to save a lot of time).
    Just a minute later, it failed..
    Code:
    date: Tue Aug 26 21:34:08 EEST 2014
    This is an automated notification from ZxBackup about Coherency Check.
    
    Operation Coherency Check Started.
    
    Operation Id: 7d345c0f-1013-47b1-bfa3-e6639a105042
    Operation Host: zm-mbox-02.cloud
    Monitor Command: zxsuite backup monitor 7d345c0f-1013-47b1-bfa3-e6639a105042
    
    Operation requested by: zimbra
    
    ZeXtras Version: 1.8.17
    ZeXtras commit: 3b7a8649b068d66a838dccbab045261aa8f9c19c
    Zimbra version: 8.0.4_GA_5737 20130524120036 20130524-1204 FOSS
    
    
    
    date: Tue Aug 26 21:34:43 EEST 2014
    This is an automated notification from ZxBackup about Coherency Check.
    
    Operation Coherency Check Completed.
    
    Operation Id: 7d345c0f-1013-47b1-bfa3-e6639a105042
    Operation Host: zm-mbox-02.cloud
    Operation Start Time: 26/08/2014 21:34:08
    Operation Duration: 34 seconds
    Operation requested by: zimbra
    
    ZeXtras Version: 1.8.17
    ZeXtras commit: 3b7a8649b068d66a838dccbab045261aa8f9c19c
    Zimbra version: 8.0.4_GA_5737 20130524120036 20130524-1204 FOSS
    
    Following problems were found (/mail-backup/zm-mbox-02.cloud):
    
    -- exceptions --
    - java.util.concurrent.ExecutionException: com.zextras.lib.json.JSONException: Error reading JSON file
            at io.netty.util.concurrent.AbstractFuture.get ( AbstractFuture.java:37 )
            at com.zextras.backup.v2.BackupStoreReadOnlyAccessorImpl.readAllServerConfigurations ( BackupStoreReadOnlyAccessorImpl.java:225 )
            at com.zextras.op.backup.coherency.CoherencyCheckServerConfigurations.check ( CoherencyCheckServerConfigurations.java:46 )
            at com.zextras.op.backup.coherency.CoherencyCheck.exec ( CoherencyCheck.java:204 )
            at com.zextras.op.StatefulOperationImpl.exec ( StatefulOperationImpl.java:69 )
            at com.zextras.op.OperationStarterActivity.doActivity ( OperationStarterActivity.java:46 )
            at com.zextras.lib.activities.ActivityThread.run ( ActivityThread.java:118 )
    Caused by: com.zextras.lib.json.JSONException: Error reading JSON file
            at com.zextras.lib.ZEUtils.readJSONObject ( ZEUtils.java:482 )
            at com.zextras.backup.v2.legacybackupstore.LegacyBackupStoreServerConfiguration.read ( LegacyBackupStoreServerConfiguration.java:119 )
            at com.zextras.backup.v2.legacybackupstore.LegacyBackupStoreServerConfiguration.readAllServerConfigurationFiles ( LegacyBackupStoreServerConfiguration.java:53 )
            at com.zextras.backup.v2.legacybackupstore.LegacyBackupStoreReadOnly.readAllServerConfigurations ( LegacyBackupStoreReadOnly.java:588 )
            at com.zextras.backup.v2.BackupStoreReadOnlyAccessorImpl.readAllServerConfigurations ( BackupStoreReadOnlyAccessorImpl.java:222 )
            at com.zextras.op.backup.coherency.CoherencyCheckServerConfigurations.check ( CoherencyCheckServerConfigurations.java:46 )
            at com.zextras.op.backup.coherency.CoherencyCheck.exec ( CoherencyCheck.java:204 )
            at com.zextras.op.StatefulOperationImpl.exec ( StatefulOperationImpl.java:69 )
            at com.zextras.op.OperationStarterActivity.doActivity ( OperationStarterActivity.java:46 )
            at com.zextras.lib.activities.ActivityThread.run ( ActivityThread.java:118 )
    Caused by: com.fasterxml.jackson.core.JsonParseException: Illegal character ((CTRL-CHAR, code 31)): only regular white space (\r, \n, \t) is allowed between tokens
     at [Source: [B@5c3e7263; line: 1, column: 2]
            at com.fasterxml.jackson.core.JsonParser._constructError ( null:-1 )
            at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError ( null:-1 )
            at com.fasterxml.jackson.core.base.ParserMinimalBase._throwInvalidSpace ( null:-1 )
            at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._skipWSOrEnd ( null:-1 )
            at com.fasterxml.jackson.core.json.UTF8StreamJsonParser.nextToken ( null:-1 )
            at com.fasterxml.jackson.databind.ObjectMapper._initForReading ( null:-1 )
            at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose ( null:-1 )
            at com.fasterxml.jackson.databind.ObjectMapper.readValue ( null:-1 )
            at com.zextras.lib.ZEUtils.readJSONObject ( ZEUtils.java:478 )
            at com.zextras.backup.v2.legacybackupstore.LegacyBackupStoreServerConfiguration.read ( LegacyBackupStoreServerConfiguration.java:119 )
            at com.zextras.backup.v2.legacybackupstore.LegacyBackupStoreServerConfiguration.readAllServerConfigurationFiles ( LegacyBackupStoreServerConfiguration.java:53 )
            at com.zextras.backup.v2.legacybackupstore.LegacyBackupStoreReadOnly.readAllServerConfigurations ( LegacyBackupStoreReadOnly.java:588 )
            at com.zextras.backup.v2.BackupStoreReadOnlyAccessorImpl.readAllServerConfigurations ( BackupStoreReadOnlyAccessorImpl.java:222 )
            at com.zextras.op.backup.coherency.CoherencyCheckServerConfigurations.check ( CoherencyCheckServerConfigurations.java:46 )
            at com.zextras.op.backup.coherency.CoherencyCheck.exec ( CoherencyCheck.java:204 )
            at com.zextras.op.StatefulOperationImpl.exec ( StatefulOperationImpl.java:69 )
            at com.zextras.op.OperationStarterActivity.doActivity ( OperationStarterActivity.java:46 )
            at com.zextras.lib.activities.ActivityThread.run ( ActivityThread.java:118 )

  6. #6
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello stsimb!

    The command didn't actually fail - the "Operation Completed" notification was correctly displayed - but actually encountered an error probably because of a corrupted file...

    I'd suggest to:

    - Delete the badly named files.
    - Run a "deep" SmartScan from the command line
    Code:
    zxsuite backup doSmartScan deep true
    - Stop the RealTime Scanner and all Backup Operations
    - Run the coherency check (please run it on all accounts, otherwise it won't be useful for your case)
    Code:
    zxsuite backup doCoherencyCheck /my/backup/path
    Have a nice day,
    Cine
    the ZeXtras Team

  7. #7
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Hello Cine, welcome back and thanks for the reply.

    I will try your suggestions and report back when I have some results (it will probably take very long)..

  8. #8
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Hello Cine,

    After 6 days, deep SmartScan ended successfully on one backend (still going in the other).
    I stopped RealTime Scanner and backups, then started the Coherency Check.
    After a few hours it failed with this error message
    Code:
    This is an automated notification from ZxBackup about Coherency Check.
    
    Operation Coherency Check Failed.
    
    Operation Id: 2ba144dd-381e-405a-962f-69d0bbfc9e25
    Operation Host: zm-mbox-01.cloud
    Operation requested by: zimbra
    
    ZeXtras Version: 1.8.17
    ZeXtras commit: 3b7a8649b068d66a838dccbab045261aa8f9c19c
    Zimbra version: 8.0.4_GA_5737 20130524120036 20130524-1204 FOSS
    
    
    -- exceptions --
    - This operation has been stopped due to a high number of errors (> 10056).
    Last progress info:
     -- 
     Scanning account: 32/122
     Scanning item:    706500
     Last account:     d88c204d-145c-4925-91dc-23494bd41357
     Checked digest:   0
    Please advice,
    Thanks!

  9. #9
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    Unfortunately, after 10 days of deep SmartScan in zm-mbox-02, it reported no progress in the last 24hrs (same number of items scanned etc).
    People started complaining about very slow zimbra access or no access at all, so we had to restart mailboxd.
    I've sent a copy of zmdiaglog output via email at community@zextras.com.

    Please advice on how we can have a reliable backup again on the two backends.
    Thanks!

  10. #10
    Senior Member
    Join Date
    Oct 2013
    Posts
    70
    More backup problems..

    1. Backup jobs take too long to start, e.g. zm-mbox-02.
    Job submitted at 23/09/2014 00:11:09 and it's still queued, not started.
    Code:
    Tue Sep 23 15:46:37 EEST 2014
    
            operationList                           
    
                    module                                                      ZxBackup
                    name                                                        SmartScan
                    descName                                                    Smart Scan
                    id                                                          50e61a1f-e312-481b-bbb1-22261376d9b5
                    state                                                       Queued
                    host                                                        zm-mbox-02.cloud.forthnet.prv
                    parameters                              
                        origin                                                          ZxLink
                        isDeep                                                          false
                        additionalNotificationAddresses         
                        requesterAddress                                                zimbra
                    monitorCommand                                              zxsuite backup monitor 50e61a1f-e312-481b-bbb1-22261376d9b5
                    queuedTime                                                  23/09/2014 00:11:09
            realTimeScanOperations                              76493
    2. Overlapping Purge & SmartScan jobs
    Running simultaneously on another backend (zm-mbox-03)..
    Code:
    [zimbra@zm-mbox-03 ~]$ zxsuite core getAllOperations
    
            operationList                           
    
                    startTime                                                   21/09/2014 01:01:11
                    module                                                      ZxBackup
                    name                                                        DoPurge
                    descName                                                    Purge
                    id                                                          c7e1e666-758a-4c4a-83b4-3853ae2b0b95
                    state                                                       Started
                    host                                                        zm-mbox-03.cloud.forthnet.prv
                    parameters                              
                        backupDirectory                                                 /mail-backup/zm-mbox-03.cloud.forthnet.prv/
                    monitorCommand                                              zxsuite backup monitor c7e1e666-758a-4c4a-83b4-3853ae2b0b95
                    queuedTime                                                  21/09/2014 01:01:11
    
                    startTime                                                   22/09/2014 01:01:00
                    module                                                      ZxBackup
                    name                                                        SmartScan
                    descName                                                    Smart Scan
                    id                                                          e16fed14-a110-44b3-b651-73830c621ff7
                    state                                                       Started
                    host                                                        zm-mbox-03.cloud.forthnet.prv
                    parameters                              
                        origin                                                          Cron
                        isDeep                                                          false
                        additionalNotificationAddresses         
                    monitorCommand                                              zxsuite backup monitor e16fed14-a110-44b3-b651-73830c621ff7
                    queuedTime                                                  22/09/2014 01:01:00
    
                    startTime                                                   23/09/2014 01:01:17
                    module                                                      ZxBackup
                    name                                                        SmartScan
                    descName                                                    Smart Scan
                    id                                                          84dbf08d-5c9f-44c1-ad34-47a55aa87927
                    state                                                       Started
                    host                                                        zm-mbox-03.cloud.forthnet.prv
                    parameters                              
                        origin                                                          Cron
                        isDeep                                                          false
                        additionalNotificationAddresses         
                    monitorCommand                                              zxsuite backup monitor 84dbf08d-5c9f-44c1-ad34-47a55aa87927
                    queuedTime                                                  23/09/2014 01:01:01
            realTimeScanOperations                              128444
    I will use the script from http://forums.zextras.com/zxbackup/9...frequency.html as a workaround to avoid this schedule overlap..

    I have saved the output of zmthrdump on both servers if you want to see it.
    zmthrdump.zip

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

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