Hi all , I have two questions would really appreciate your helpful and kind replies.

1. Is there any limit on the size of sem5 database ( embedded database ) that we can backup or not . for example if sem5 exceeds 15 GB we cannot backup it up via the SEPM Backup utility
   
    
2. Is there any limitation on the size of DB that we can restore via SEPM restore utility . for example if the size of DB exceeds 20 GB we cannot restore it via the Restore utlity of SEPM

I remember I read somehwere that there is a limit on size of DB if it exceeds then we cannot restore it . Please correct me if I am wrong . Thanks

Any 1 ?

There is no limit on size only amount of clients (5000 clients is the max).

There is a tool to shrink it that was created by Symantec:

http://www.symantec.com/connect/downloads/shrink-symantec-endpoint-protection-manager-121-embedded-database

there is no such limitation that I am aware of. and logically speaking for a ideal environment which uses embedded db to grow that big is simply out of cards. 

the only limitation of embedded db is that i can support only upto 5000 users nothing else that I am aware of.

Thanks for your reply guys , but what if at the version of SEPM is 12.1.5 with content revision set to 180 . I belive it shouldn't be any issue while doing the restore.

Again, size should not be an issue regardless of content. It's only limitation is amount of clients.

There is size limits for database backup in SEPM.

I have seen scenarios where restoration of a huge backup files failed due to restriction of the database size on the SQL database of the new SEPM (on which you are restoring the backup). In such cases, just setting the size limitation for the database (in SQL management studio) to "unrestricted growth" and then restoring the database again has always worked.

http://www.symantec.com/docs/TECH184770

Syed your reply is so logical . I am very impressed . Keep rocking :)

Thank you Brian for your reply as well . I appreciate your time for replying to my posts :)

Thank you Praveen for your reply as well . You guys have always been helpful . Much appreciated

Sorry but the answer you marked is not what your question was about.

I guess I don't understand.

are you looking for SQL or embedded DB ?  and as you know with SEPM version 12.1.5 SEPM will retain only one full.zip and the rest will be delta packages. so the entire definition sets should not exceed more than 3 to 4 GB even if you are retaining 180 sets of them. 

by the way are you sure you want to retain such high sets of defs for a small time org (going by embedded DB limitation of 5000 clients)

Yeah actually there was a buisness requirement to retian such much content defs as mostly the machines are ATM with slow WAN links which rarely come online to grab defs from SEPM.

We intend to take backup from SEPM running with embdedded DB and restore on a SEPM with a SQL instance.

then it makes sense, but then the database size DB shoudn't exceed 3 to 5 GB. Moreover I have once once seen a SBE customer with 15+ GB of sem5.db file a couple of years ago with SEPM version of 12.1.1 I believe. so you wouldn't run into any problems by my guess.  on the other hand SQL does offer a lot of added features.

if you are planning to move your embedded db to SQL please refer to below article.

Symantec Endpoint Protection Manager: Moving from the embedded database to Microsoft SQL Server

I just checked the content size in DB and it is reflecting only 1 GB we have 90 content revision. so as I said earlier the content size in DB wouldn't exceed 2 to 3 GB.

Thanka a lot for your reply praveen.You have been so helpful . Regards

you are most welcome. I am happy that I am able to help others.