FMC backup

[anazarenko]

Dear All,

I tried to create a config backup on FMC, but it consumes around 160MB.

How do people rancid and manage configuration versions on FMC with such monstrous files?

I didn't find a way how to backup FTD config. 

[Keith Miller]

You can also configure the backups to be copied to another location using SCP:

HTH,

Keith

[anazarenko]

I saw it, but we need to manage each config change. I can't imagine copying 160MB config files each time I do some rule change.

[itsupport]

It is 2017. $10USD buys a 16Gb USB key, which could hold 100 backups that size.

I just copied one of those backup files from my crappy old desktop PC to our 5 year old server, took 12 seconds.

Not really seeing a problem.

[anazarenko]

The matter is to see which changes were made by colleages. Looking into 160MB backup files doesn't seem to be a right way to do it.

[Oliver Kaiser]

No offense but that logic is kinda flawed. I am not a big fan of the backup concept either. Its basically a database dump with some configuration files attached. I have some larger installations which already produce backup files that are > 2GB of size.

@anazarenko - unfortunately you will need to live with the backup size. as of now there is no flat file configuration backup like what you are used to. 6.2.2.1 should include a better audit trail which might help you with compliance requirements.