"Restore Failed" error during restore operation of Symantec Endpoint Protection Manager (SEPM) database backup

Article:TECH134017  |  Created: 2010-01-18  |  Updated: 2012-05-18  |  Article URL http://www.symantec.com/docs/TECH134017
Article Type
Technical Solution


Issue




While restoring a SEPM database backup, and error about the Site USN is displayed.    


Error




Restore Failed - Could not read local Site Update Sequence Number information from the restored database. - The restore might have failed.




Looking in ..\Symantec Endpoint Protection Manager\tomcat\logs\ backup.log and backup.err files you might find similar entries:


---backup.log-----------------------------------------------------------------------------------
SELECT CONTENT FROM SYSTEM_STATE WHERE OWNER = 'BE3C60D00AA012F30153853B83EF2BC4'
Has valid SAV license
Info>> No SNAC license file in D:\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
2010 Jun 11 12:11:23 PM CEST
------------------------------------------------------------------------------------------------

---backup.err-----------------------------------------------------------------------------------
java.util.zip.ZipException: invalid entry CRC (expected 0xd61b0493 but got 0x921b4363)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:171)
at com.sygate.scm.util.ZipUtil.unzipFromInputStream(ZipUtil.java:246)
at com.sygate.scm.util.ZipUtil.unzipFile(ZipUtil.java:159)
at com.sygate.scm.server.metadata.BackupManager.restore(BackupManager.java:290)
at com.sygate.scm.tools.DatabaseFrame.doRestore(DatabaseFrame.java:864)
at com.sygate.scm.tools.DatabaseFrame.restore(DatabaseFrame.java:696)
at com.sygate.scm.tools.DatabaseFrame.access$800(DatabaseFrame.java:100)
at com.sygate.scm.tools.DatabaseFrame$3$1.construct(DatabaseFrame.java:296)
at com.sygate.scm.tools.SwingWorker$2.run(SwingWorker.java:122)
at java.lang.Thread.run(Thread.java:619)
java.sql.SQLException: No current row in the ResultSet.
at net.sourceforge.jtds.jdbc.JtdsResultSet.getColumn(JtdsResultSet.java:278)
at net.sourceforge.jtds.jdbc.JtdsResultSet.getLong(JtdsResultSet.java:647)
at com.sygate.scm.tools.DatabaseFrame.getLatestUSN(DatabaseFrame.java:1036)
at com.sygate.scm.tools.DatabaseFrame.doRestore(DatabaseFrame.java:982)
at com.sygate.scm.tools.DatabaseFrame.restore(DatabaseFrame.java:696)
at com.sygate.scm.tools.DatabaseFrame.access$800(DatabaseFrame.java:100)
at com.sygate.scm.tools.DatabaseFrame$3$1.construct(DatabaseFrame.java:296)
at com.sygate.scm.tools.SwingWorker$2.run(SwingWorker.java:122)
at java.lang.Thread.run(Thread.java:619)
------------------------------------------------------------------------------------------------


Cause



Corruption of the database backup file seems to be the main cause of this error message.

The most common cause of file corruption is FTP transfer using resume of file upload/download due to disconnections with the FTP server.

Please note that even if the database is saved with a .zip extension, it is not possible to do a CRC check or test the .zip file with utilities like WinRAR, WinZIP, 7z, etc. due to non-standard features of the backup files created by the SEPM backup process.  These features enable SEPM to correctly handle files bigger than 4 Gb, but will prevent common tools from accurately processing the files.


Solution



  • Use a different database backup file.
  • Compare the unique MD5 or SHA-1 hash values of the transferred files against the original values to ensure that no corruption has occurred in case of transferred files.



References
Availability and description of the File Checksum Integrity Verifier utility

http://support.microsoft.com/kb/841290




Legacy ID



2010061812052248


Article URL http://www.symantec.com/docs/TECH134017


Terms of use for this information are found in Legal Notices