Symantec Endpoint Protection Manager database backups using the built-in backup utility appear corrupt or invalid by other zip utilities

Article:TECH123357  |  Created: 2010-01-19  |  Updated: 2011-02-10  |  Article URL http://www.symantec.com/docs/TECH123357
Article Type
Technical Solution

Product(s)

Environment

Issue



When using the built-in Symantec Endpoint Protection Manager (SEPM) utility "Database Back Up and Restore" with a large database size that results in a zip file greater than 4 GBs, the resulting zip file will appear to be corrupt by any other zip utility.


Cause



The SEPM's Backup Utility uses custom technologies to create a backup file that is not able to be viewed or opened by third party compression utilities. The zip files we create are invalid from any other tool's perspective. The resulting zip is no longer using the standard zip format and cannot be fully used by these tools.


Solution



This is currently working as designed. Though these .zip files cannot be opened by common third-party tools, the files are not necessarily damaged or corrupt.  Backups created using the SEPM's built-in backup utility that are larger than (or that result in a zip file that is) 4 GBs will appear corrupt or invalid to third party zip utilities. The SEPM's built-in restore utility is able to read and restore its own backups successfully and does not have a size limitation.

If you are using Microsoft SQL to host the database you can also create a full backup by using the Microsoft SQL Backup Utility to create your backups. For information about how to backup the database using Microsoft SQL 2005, read the following document: Backing up a Microsoft SQL 2005 database with the Database Maintenance Plan wizard.


Supplemental Materials

SourceETrack
Value1979760


Legacy ID



2010021910351848


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


Terms of use for this information are found in Legal Notices