Difference between revisions of "Not able to take complete backup"

("Unable to parse XML file" error when taking using legacy backup)
 
Line 2: Line 2:
 
__FORCETOC__
 
__FORCETOC__
 
<div class="col-md-12 ibox-content">
 
<div class="col-md-12 ibox-content">
="Unable to parse XML file" error when taking using legacy backup=
+
="Unable to parse XML file" error when using legacy backup=
 
<hr>
 
<hr>
 
{{KB|{{ZC}}|{{ZCS 8.7}}||||}}  
 
{{KB|{{ZC}}|{{ZCS 8.7}}||||}}  

Latest revision as of 13:12, 17 April 2020

"Unable to parse XML file" error when using legacy backup


   KB 23346        Last updated on 2020-04-17  




0.00
(0 votes)




Problem

Not able to take complete backup and getting following exception in mailbox.log file.

com.zimbra.common.service.ServiceException: system failure: unable to read metadata for account ff0cf615-6749-4e94-aa53-548cd8dba365 backup full-20161005.025406.465
ExceptionId:qtp509886383-791257:https://127.0.0.1:7071/service/admin/soap/BackupRequest:1475690422338:c777d25a962adbb8
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:260)
at com.zimbra.cs.service.backup.Backup.handleNetworkRequest(Backup.java:160)
at com.zimbra.cs.service.NetworkDocumentHandler.handle(NetworkDocumentHandler.java:23)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:581)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:435)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:266) 
        ... 52 more
Caused by: com.zimbra.common.service.ServiceException: system failure: Unable to parse XML file /backup/sessions/full-20161005.025406.465/accounts/ff0/cf6/ff0cf615-6749-4e94-aa53-548cd8dba365/meta.xml
ExceptionId:qtp509886383-791257:https://127.0.0.1:7071/service/admin/soap/BackupRequest:1475690422338:c777d25a962adbb8
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:260)
        at com.zimbra.cs.backup.XmlMeta.readAccountBackup(XmlMeta.java:409)
        at com.zimbra.cs.backup.FileBackupTarget$RestoreAcctSession.<init>(FileBackupTarget.java:2020)
        ... 56 more

Solution

  • Go to configured backup path (default is - /opt/zimbra/backup)
  • Open accounts.xml in your text editor, and remember the two lines related to that account.

For example, if the original entry is like so :

<account zimbraId="0e98d0df-0c92-48d2-bd01-a01027504d8a" email="user@example.com" latestFullBackupLabel="full-20130919.102126.721"> 
</account> 
<account zimbraId="ff0cf615-6749-4e94-aa53-548cd8dba365" email="issue@example.com" latestFullBackupLabel="full-20130919.102126.721">
</account>
<account zimbraId="c0263897-e300-4836-9da3-4356dbe2498e" email="user2@example.com latestFullBackupLabel="full-20130919.102126.721"> 
</account>


Remove the lines pertaining to that account. In our example, it'll be 'issue@example.com'. So we remove both, the <account -info- > and </account> lines and remaining entries will looks like following:

<account zimbraId="0e98d0df-0c92-48d2-bd01-a01027504d8a" email="user@example.com" latestFullBackupLabel="full-20130919.102126.721"> 
</account> 
<account zimbraId="c0263897-e300-4836-9da3-4356dbe2498e" email="user2@example.com latestFullBackupLabel="full-20130919.102126.721"> 
</account>


  • Then re-run backup
zmbackup -f -a -all



Submitted by: Sourabh Bhushan
Verified Against: ZCS 8.7.11 Date Created: 2020-04-13
Article ID: https://wiki.zimbra.com/index.php?title=Not_able_to_take_complete_backup Date Modified: 2020-04-17



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »


Jump to: navigation, search