purge issue on RME LMS 2.6

Answered Question
Jul 27th, 2008
User Badges:

I have config RME to keep only 2 version and purge everything else older than 3 month old.but when I go to dev file I found

some of the device have 30+ old archive. I did archive purge 3-4 times, plus I did force purge but those files(versions) some of them more than 2 years out there.

what other option I have to purge all those old version, it's consumed all my space.I did relocate my archive directory to new partition but all the garbage relocated together. any help!!! thanks in advance.

Correct Answer by Joe Clarke about 8 years 9 months ago

/opt/CSCOpx/bin/dbRestoreOrig.pl dsn=rmeng dmprefix=RME

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Mon, 07/28/2008 - 05:29
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

You'll need to enable ArchiveMgmt Service and ConfigJob debugging, run a purge job, then check the purge job log file for errors. There may be no errors, but the configs may still not purge if the RME database was ever reinitialized. There may be old configs on the file system that existed under the old RME database, that are no longer referenced. These could only be purged manually.


Another way to check this is to launch the Version Tree for a device which shows very old configs in the archive. If those old configs don't appear in the Version Tree, then those files are safe to delete.

eliaspaulos Mon, 07/28/2008 - 06:41
User Badges:

thanks J. looks like the RME initialize some time 04/2007. most of the file old back on 2006

not displayed on Version tree. literally more than 100000 files if I want to delete manually.my effort was when I relocate the archive path, I thought the RME start from scratch the config archive instead of backup the old one to new location.my question is can I start RME to archive from today. and save or Back up (or may be zipped on old location) to keep for rainy days? just to start from from today, we don't need the old version that much,even on future upgrade I don't want those config to migrate on the new CW. most of the config version don't have much difference, since we are using too many port open and close per day, that's the reason collected too many Versions. any suggestion??


Joe Clarke Mon, 07/28/2008 - 07:23
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

If you reinitialize the RME database, then clear out everything under your archive directory, then recreate the following directories in your archive directory:


baselinetemplates

configexport

devfiles

difffiles

newbaselinetemplates

shadow

temp


Then make sure casuser has access to them:


chown casuser:casusers

chmod 0750


You should be good to go. Of course, by doing this, you will lose all of your current RME data for all of your devices.


The important directories to backup are shadow and devfiles.

eliaspaulos Mon, 07/28/2008 - 08:32
User Badges:

great info thanks!!! how I can reinitialize the RME database.

Correct Answer
Joe Clarke Mon, 07/28/2008 - 08:35
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

/opt/CSCOpx/bin/dbRestoreOrig.pl dsn=rmeng dmprefix=RME

Actions

This Discussion