CSM v3.3.1 backup file size incredible 3GB

Unanswered Question
Jun 30th, 2010


Does anybody else have backup files with the size of 3GB and more with a CSM v3.3.1 SP1? The interessting thing is that this CSM manages about 30 network devices. Looking into the backup files it's just the "vms.db" file which consumes the most (2.9 GB) of the data.

Is this normal behaviour for a CSM?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Panos Kampanakis Wed, 07/07/2010 - 10:46

The backup size of CSM has indeed increased.

I would suggest you to go under Administration and Config Archive and clear some archived files (leave last 5-10 per device for example). That should decrease the backup size.

I hope it helps.


ROBERTO GIANA Fri, 07/09/2010 - 07:46

I tried it and got the following message:

"At present configuration purge is not required because no devices in csm now or none of the devices exceed max configuration versions defined in CSM (10)."

What happens to the vms.db if the devices are deleted? Are the configuration versions of them also deleted?

Kind regards


Stefano De Crescenzo Wed, 11/10/2010 - 16:13

Yes, all the information linked to the that device will be deleted by the database.

Regarding vms.db it is not a file that is present in your system but it is created everytime you trigger a backup. Honestly 3GB is not really big itself so I would not worry too much


ROBERTO GIANA Mon, 11/15/2010 - 00:15

Hi Stefano

I'm not worried about the size itself. I'm worried, that by just installing a minor software update the backup size increases by the factor of 10. That's ridiculous. TAC wasn't able to provide me a reason. Basicly the answer was something like "it's the way it is".

By the way: Do you want to have something to laugh about? Just try to find out if 64 bit Windows is supported by the CSM. Just little hint: Go through the release numbers.

You will find: Releases pre v3.2 don't support 64 bit, v3.2 does, v3.3 doesn't and for release v4 it's recommended.

ROBERTO GIANA Mon, 11/15/2010 - 08:09

Well. It seems to have been adopted on the web and on newer versions of the doc. I'm refering to the v2 of the v3.2.2 installation guide, as I have used it to install, update and migrate several customer installations.

I think mistakes can hapen. But such mistakes should be at least worth a field notice to inform customers and partners that something has to be corrected. It's not really fun to look like a complete idiot to the customer, one who can not even read install guides.

Stefano De Crescenzo Mon, 11/15/2010 - 23:48

Hi Roberto,

I understand your point, I will try to bring this back internally .

Regarding the specific issue, indeed that installation guide was wrong and got fixed after we flagged this issue on: CSCsz22077


Sorry for all the confusion it led . Let me know if there is anything else we can do, appreciate your suggestion



This Discussion

Related Content