The configuration archive Shadow directory is an image of the most recent configurations gathered by the configuration archive.
The Shadow directory contains subdirectories that represent each device class and the latest configurations supported by the configuration archive.
Each file name is DisplayName.cfg, where DisplayName is the device's Display Name as defined in the Device and Credential Repository. Each time the archive is updated, the Shadow directory is updated with the corresponding information.
The Shadow directory can be used as an alternative method to derive the latest configuration information programmatically by using scripts or other means.
The shadow dir is updated and managed only when it is enabled. You can enable/disable shadow dir from:
*(This needs to stop/start the ConfigMgmtServer, which can be done from : Admin > System > Server Monitoring > Processes)
Apart from this, ciscoworks saves all the configuration archive in NMSROOT\files\rme\dcma\devfiles, which is not in a format to be interpreted easily. That is solely for ciscoworks to create its own pointer in DB for archive-device-version match up.
On your quetions :
1) How to take daily backup from LMS and where it is stored?
>There are two ways :
a. You can create a scheduled job run daily to archive device configs.
b. There is default system job, which needs to be enabled to archive configs. For more details on this check :
2) Is there any way to read the config files in VLAN folder?
> As stated, you may not be able to corelate the devices with config and hence it is nearly impossible to do so. For this 'shadow' directory is there.
3) What we need to do for not loosing the old config files?
> Ciscoworks does not deletes/removes anything unless configured for. You can configure LMS for Config Archive Purge Settings to enable/disable archive purge setup. You can purge configurations based on two criteria:
•Number of versions to retain. Maximum number of versions of each configuration to be retained.
•Age. Configurations older than the number of days that you specify are purged.
Archive Management will not purge the configuration files, if there are only two versions of these files in the archive.
Archived configurations that match the purge criteria that you set are purged from the system. This purge policy applies to Running configuration only.
Unless this is enable, ciscoworks will keep all the configuration archives. You can specify when to purge archived configurations. Purging archives frees disk space and keeps your archive at a manageable size. By default, the purging jobs are disabled.
**Rating Encourages contributors, and its really free. **
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...