Re: remove archive (187 Views)
Reply
Occasional Contributor
eslamk
Posts: 3
Registered: ‎06-27-2011
Message 1 of 3 (218 Views)
Accepted Solution

remove archive

Dear Admins,

 

how to safely remove old archives from ignite-ux server.

 

 

Thanks,

Eslam

Honored Contributor
Bill Hassell
Posts: 14,218
Registered: ‎05-29-2000
Message 2 of 3 (198 Views)

Re: remove archive

[ Edited ]

Ignite archives are normally cleaned up after every backup. However, changing the number of archives can sometimes get the cleanup process confused and older archives are no longer removed.

 

There are two directories that store the backup files and a control file called CINDEX that holds the current list. Start by cd'ing to /var/opt/ignite/clients directory. There you will normally find a set of MAC addresses (0x...) and symlinks pointing from hostnames to the appropriate MAC address. In a poorly maintained server, there may be one or more MAC addresses that are no longer valid (sever retired, LAN card replaced, etc). There may also be hostname symlinks pointing non-existent MAC addresses. There may even be MAC-to-MAC symlinks typically used when deploying multiple servers.

 

To safely cleanup this directory, you need an accurate list of the active servers and the MAC address of the LAN card used for the Ignite backup. Then make sure there is just one hostname symlink pointing to the correct MAC address. Once that is complete, you can remove extraneous symlinks and remove MAC address directories for non-existent LAN cards.

 

Then look at each hostname's CINDEX file. It will look something like this:

 

# cat /var/opt/ignite/clients/<hostname>/CINDEX
cfg "2013-11-09,09:14 Recovery Archive" { description "11.11 atl3 Recovery Archive" "recovery/2013-11-09,09:14/system_cfg" "recovery/2013-11-09,09:14/control_cfg" "recovery/2013-11-09,09:14/archive_cfg" } cfg "2013-11-16,09:14 Recovery Archive" { description "11.11 atl3 Recovery Archive" "recovery/2013-11-16,09:14/system_cfg" "recovery/2013-11-16,09:14/control_cfg" "recovery/2013-11-16,09:14/archive_cfg" } cfg "2013-11-23,09:14 Recovery Archive" { description "11.11 atl3 Recovery Archive" "recovery/2013-11-23,09:14/system_cfg" "recovery/2013-11-23,09:14/control_cfg" "recovery/2013-11-23,09:14/archive_cfg" }=TRUE

 

 This is the list that Ignite will use in recovery menus. In each hostname directory, there will be a recovery directory with several directories that are dates, like this:

 

# ll /var/opt/ignite/clients/<hostname>/recovery
drwxr-xr-x 2 bin bin 1024 Nov 9 10:00 2013-11-09,09:14 drwxr-xr-x 2 bin bin 1024 Nov 16 10:00 2013-11-16,09:14 drwxr-xr-x 2 bin bin 1024 Nov 23 10:01 2013-11-23,09:14 -rw-r--r-- 1 bin sys 273 Nov 10 2010 archive_content -rw------- 1 bin bin 290 Nov 23 10:01 client_status -rw-r--r-- 1 bin sys 462 Nov 10 2010 defaults lrwxr-xr-x 1 root root 16 Nov 23 09:14 latest -> 2013-11-23,09:14

 

There must be a match between each CINDEX cfg stanza and the directories in recovery. It is possible that there are more (which can be removed) or there are missing recovery directories. The goal for cleanup is a match between CINDEX and the recovery directory. Removing a stanza, that is, the cfg "..title.." {...info...} lines will remove this item from the Ignite menu.

 

Now you can remove the extra date directories that do not have matching entry in CINDEX.

 

The second step is to remove the same date files that don't match CINDEX. These are the actual tar archives and are simple files, but in a parallel directory like this:

 

ll /var/opt/ignite/recovery/archives/<hostname>/
-rw------- 1 bin sys 3118651320 Nov 9 10:00 2013-11-09,09:14
-rw------- 1 bin sys 3118712432 Nov 16 10:00 2013-11-16,09:14
-rw------- 1 bin sys 3091637080 Nov 23 10:01 2013-11-23,09:14

Remove any file (looks like a date) that does not appear in the CINDEX file.

 

 

 

 

 

 

 

 

 

Occasional Contributor
eslamk
Posts: 3
Registered: ‎06-27-2011
Message 3 of 3 (187 Views)

Re: remove archive

Thank you Bill for detailed clarification
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.