topic Re: ignite in Operating System - HP-UX

ignite

Waugh — Sat, 19 Jun 2010 19:14:15 GMT

Hi ,

We have archive.log ,flist under/var/opt/ignite/clients/devxen/recovery directoty
eg:
drwxr-xr-x 2 bin bin 1024 Feb 16 2008 2008-02-16,21:00
drwxr-xr-x 2 bin bin 1024 Sep 27 2008 2008-09-27,21:00
drwxr-xr-x 2 bin bin 1024 Apr 4 2009 2009-04-04,21:00
drwxr-xr-x 2 bin bin 1024 May 16 2009 2009-05-16,21:00
drwxr-xr-x 2 bin bin 1024 Jun 13 2009 2009-06-13,21:00
drwxr-xr-x 2 bin bin 1024 Jun 15 2009 2009-06-15,21:00
each directory contains the below files
total 27544
-rw-r--r-- 1 bin sys 33 Feb 16 2008 archive_content
-rw-r--r-- 1 bin sys 85690 Feb 16 2008 system_cfg
-rw-r--r-- 1 bin sys 29109 Feb 16 2008 control_cfg
-rw-r--r-- 1 bin sys 13822450 Feb 16 2008 flist
-rw-r--r-- 1 bin sys 117996 Feb 16 2008 recovery.log
-rw-r--r-- 1 bin sys 43795 Feb 16 2008 archive_cfg
so can we delete these directories which are very old. Is there any impact on ignite backup

Regards,
Rkumar

Re: ignite

Redhat — Sun, 20 Jun 2010 01:39:38 GMT

yes for a single client you can remove the old files if the recent ignite is successful

Re: ignite

madhuchakkaravarthy — Sun, 20 Jun 2010 03:22:43 GMT

hi

no problem u can go a head in deleting the old archives if recent ignite backup are up to date

regards

MC

Re: ignite

singh sanjeev — Sun, 20 Jun 2010 09:19:25 GMT

YEs you can delete the old ...archive..

Re: ignite

Bill Hassell — Sun, 20 Jun 2010 22:28:09 GMT

You can limit the number of backup directories by using -n with make_net_recovery. If you want to keep only the last 3, use -n 3 in your MNR command. You may need to trim all but the most recent 3 directories so MNR can manage the archive count.

Re: ignite

raghu_14 — Mon, 21 Jun 2010 03:42:28 GMT

Hi,

It all depends how many size you can accomodate for the archives in the /var. If you keep on saving the archive, then the new archive creation under /var may fail due to size issue.

The things you need to consider :
a. how many client's archive you need to save on this server
b. what is the max size limit to which /var can grow (check using bdf)
c. from (a) and (b) above, you can come to a conclusion as to how many number of archives you can save on /var per client on the system.
d. once you know that max number of archives/client, you can change your crontab entry or script which has make_net_recovery entry to use the -n option. make_net_recovery will take care of maintaining the latest n number archives. But just archiving things won't help. At times (you need to think about the frequency per your needs) to see that the archive you have created for each client can be restored successfully.

hope this helps,

Regards,
Raghu