Running 4.01. I have Cirrus saving a copy of the configs to the config-archive directory via the Cirrus Configuration Manager Settings. Yes the box to "save copy of configs" is checked. But Cirrus is not "always" saving a copy. I have my schedule set to download my configs at 1am every night if they have changed. Yep, it is doing that. I can see all the configs and dates in the GUI. But the damn product isn't saving them out to the config-archive directory.
Ok, so let me do a manual export... what a cluster! 1 hour later and still waiting, just a couple of configs have been exported. Moving status bar would be great here to know the progam hasn't frozen up. Have no idea what is going on. I do know that the GUI is frozen processing the request. So I guess I just leave my RDP session up and going so it can continue its config export?
I have a dualcore 3gig Xeon with 4gigs ram in it, so we are not talking about a desktop system here. My db server is similar with 4gigs ram running SQL enterprise edition.
Anyone notice this? I suggest you go check. It will be in the database but not exported out as a text file in your config-archive directory