I'm currently using the archiving process to take advantage of the 'configure replace timer' command, but it seems as if the counter that it uses to determine how many archives there are is reset upon reload. Some of our devices with spotty power never make it to our maximum, and therefore never delete their older archives, and the flash just fills up with random config files. I'm also using the "most recent" archive to determine which file is the startup config to do a 'configure compare running startup' to determine if the configuration is saved or not programmatically. Since this list is emptied upon reboot there is no most recent archive. My workaround so far has been to do a 'configure archive' on boot, but that still doesn't help the fact I essentially have a memory leak on all my devices now. Is there a way to either automatically delete the older archives or have the archive counter remain consistent between reloads?
