Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 05-08-2010, 07:04 AM
Active Member
 
Posts: 28
Default [SOLVED] Zimbra NE Backup Issue - session.xml.tmp was not renamed to session.xml

I've tried running a full backup and I am getting the following error. I applied 6.0.6.1 patch last night. Not sure if this has anything to do w/ it. I've tried running the back up again with the same error. Anyone have any clues or know what's going?


Label: * full-20100508.060003.411
Type: * *unknown
Status: *missing, incomplete, or invalid
Started: Sat, 2010/05/08 01:00:03.411 CDT
Number of accounts: 0 out of 0 completed
Number of errors: 1
Error: incomplete backup full-20100508.060003.411: /opt/zimbra/backup/sessions/full-20100508.060003.411/session.xml.tmp was not renamed to session.xml; backup did not complete successfully
com.zimbra.cs.backup.BackupServiceException: incomplete backup full-20100508.060003.411: /opt/zimbra/backup/sessions/full-20100508.060003.411/session.xml.tmp was not renamed to session.xml; backup did not complete successfully
ExceptionId:btpool0-648://localhost:7071/service/admin/soap/BackupQueryRequest:1273320795617:4d45080e7455f190
Code:backup.INCOMPLETE_BACKUP
at com.zimbra.cs.backup.BackupServiceException.INCOMP LETE_BACKUP(BackupServiceException.java:70)
at com.zimbra.cs.backup.FileBackupTarget$FileBackupSe t.<init>(FileBackupTarget.java:792)
at com.zimbra.cs.backup.FileBackupTarget.getBackupSet (FileBackupTarget.java:216)
at com.zimbra.cs.backup.FileBackupTarget.getBackupSet s(FileBackupTarget.java:236)
at com.zimbra.cs.service.backup.BackupQuery.handle(Ba ckupQuery.java:71)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:419)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:273)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:157)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:182)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:155)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:418)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Reply With Quote
  #2 (permalink)  
Old 05-08-2010, 07:16 AM
Moderator
 
Posts: 7,928
Default

Check /opt/zimbra/log/mailbox.log, around the time the backup kicked off, and see if any errors were reported.
__________________
Reply With Quote
  #3 (permalink)  
Old 05-08-2010, 05:12 PM
Active Member
 
Posts: 28
Default

The backup starts:

Code:
2010-05-08 19:03:39,144 INFO  [FullBackupThread] [] io - AsyncFileCopier is starting
2010-05-08 19:03:39,145 INFO  [FullBackupThread] [] backup - Full backup started for backup set; label: full-20100509.000338.757
2010-05-08 19:03:39,360 INFO  [FullBackupThread] [name=user@ourdomain.com;mid=560;] backup - redo log file sequence is 6559 at full backup for youngstown@southerncareinc.com
2010-05-08 19:03:39,417 INFO  [FullBackupThread] [name=user@ourdomain;mid=560;] backup - Full backup started for account user@ourdomain.com (3a373c26-4e8d-44d4-831d-6ca6e327c947) mailbox 560
2010-05-08 19:03:39,418 INFO  [FullBackupThread] [name=user@ourdomain.com;mid=560;] mailbox - Locking mailbox 560 for maintenance.
2010-05-08 19:03:39,431 INFO  [FullBackupThread] [name=user@ourdomain.com;mid=560;] backup - Number of blobs to backup for mailbox 560: 3364
2010-05-08 19:03:39,431 INFO  [FullBackupThread] [name=user@ourdomain.com;mid=560;] mailbox - Ending maintenance on mailbox 560.
2010-05-08 19:03:39,431 INFO  [FullBackupThread] [name=user@ourdomain.com;mid=560;] mbxmgr - Mailbox 560 account 3a373c26-4e8d-44d4-831d-6ca6e327c947 AVAILABLE
And then the following error:
Code:
2010-05-08 19:04:09,991 ERROR [ZipCopier-mbox560-2] [] backup - Unable to write to zip file
java.io.IOException: No space left on device
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at com.zimbra.common.util.zip.ZipOutputStream.writeOut(ZipOutputStream.java:903)
	at com.zimbra.common.util.zip.ZipOutputStream.write(ZipOutputStream.java:513)
	at com.zimbra.cs.backup.util.ParallelZipCopier$ZipCopierThread.run(ParallelZipCopier.java:213)
2010-05-08 19:04:09,991 ERROR [ZipCopier-mbox560-2] [] backup - Error reported by FileCopier: No space left on device
java.io.IOException: No space left on device
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at com.zimbra.common.util.zip.ZipOutputStream.writeOut(ZipOutputStream.java:903)
	at com.zimbra.common.util.zip.ZipOutputStream.write(ZipOutputStream.java:513)
	at com.zimbra.cs.backup.util.ParallelZipCopier$ZipCopierThread.run(ParallelZipCopier.java:213)
I'm out of disk space!

Last edited by Klug; 05-09-2010 at 08:09 AM..
Reply With Quote
  #4 (permalink)  
Old 05-09-2010, 08:10 AM
Moderator
 
Posts: 2,207
Default

I happened to me once.
As long as you don't remove the temporary file, you won't be able to do any more backups.

(I edited the previous post just to change the BBcode from "PHP" to "code")
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.