IDS 9.4 and On-Bar

On my Production machines I am still running IDS9.21 and On-Archive with 4 weeks of tapes that we recycle - Mon1 to Fri1, Mon2 to Fri2, Mon3 to Fri3 and Mon4 to Fri4. We run 3 archives a day onto each daily tape. Each archive command contains what it is you want archived, level 0 all dbspaces, and an expiry date. If I use Mon1 tape on the 1st of Jan to do a backup by the time I come round to use Mon1 again on the 29th Jan the system knows this backup has expired and overwrites any data on the tape. I am trying to get the same backup strategy working on a Test machine with IDS 9.4 On-Bar & ISM. For testing purposes I only have 5 tapes Mon, Tue, Wed, Thu & Fri. I have set the retention policy to 7 days using ism_config –retention 7 I have labelled Thu tape using ism_op –label /dev/rmt/omnb –pool ISMData –volume thursday I have successfully run a backup using onbar –b –w but ism_show –volumes shows an expiry date of 01/10/09 which is obviously not the 7 days defined earlier. ism_show –volume thursday correctly shows 03/01/07 as the data of the backup Can I get the system to automatically reuse the tapes as I can with On-Archive? Is it something I have not configured correctly ? Sue

Hi, can you please use the interactive command "nsradmin -c" to check the retension settings for the devices, etc. I've described the use of this utility several times (maybe not for retension time, but other settings) in this forum. So you should be able to find the description in some archive ... Regards, Martin -- Sorry, but the following text is now required by German law: IBM Deutschland GmbH Vorsitzender des Aufsichtsrats: Hans Ulrich Maerki Geschäftsführung: Martin Jetter (Vorsitzender), Rudolf Bauer, Christian Diedrich, Christoph Grandpierre, Matthias Hartmann, Andreas Kerstan Sitz der Gesellschaft: Stuttgart Registergericht: Amtsgericht Stuttgart, HRB 14562 WEEE-Reg.-Nr. DE 99369940 ids-bounces@iiug.org wrote on 02.03.2007 15:22:55: > On my Production machines I am still running IDS9.21 and On-Archive with 4 > weeks of tapes that we recycle - Mon1 to Fri1, Mon2 to Fri2, Mon3 to Fri3 and > Mon4 to Fri4. We run 3 archives a day onto each daily tape. > > Each archive command contains what it is you want archived, level 0 all > dbspaces, and an expiry date. > > If I use Mon1 tape on the 1st of Jan to do a backup by the time I come round > to use Mon1 again on the 29th Jan the system knows this backup has expired and > overwrites any data on the tape. > > I am trying to get the same backup strategy working on a Test machine with IDS > 9.4 On-Bar & ISM. > > For testing purposes I only have 5 tapes Mon, Tue, Wed, Thu & Fri. > > I have set the retention policy to 7 days using ism_config ?retention 7 > > I have labelled Thu tape using ism_op ?label /dev/rmt/omnb ?pool ISMData > ?volume thursday > > I have successfully run a backup using onbar ?b ?w > but ism_show ?volumes shows an expiry date of 01/10/09 which is obviously not > the 7 days defined earlier. > ism_show ?volume thursday correctly shows 03/01/07 as the data of the backup > > Can I get the system to automatically reuse the tapes as I can with > On-Archive? > Is it something I have not configured correctly ? > > Sue > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

For testing purposes only I have 1. set the retention policy to 1 day ism_config -retention 1 and checked the settings using nsradmin -c 2. labeled my test tapes mon, tue, wed, thu, fri ism_op -label /dev/rmt/0mnb -pool ISMData -volume mon 3. on Friday I did a level 0 backup onto the fri tape successfully onbar -b 4. on Monday I did another level 0 backup onto the mon tape successfully onbar -b 5. on Tuesday I reloaded the fri tape which should now have expired and did another level 0 backup. It simply added another saveset to the volume rather than overwriting the saveset written on Friday I have been told there is an internal ISM task that runs when there is low activity on the ISM server to expire savesets and it will not reuse the tape until all savesets have expired. So in setting the retention period to 1 day and leaving it over the weekend I assumed that the single saveset from Friday would now have expired. Am I missing something ? Is there something else I need to do to get it to reuse the tapes ?

Hi, I have been experiencing this same problem. Also raised a message to OSS but also problem persisted. Hope someone can guide and advise how to make it work. Best Regards, Dominic Seah "SUE SIMMONDS" <sues@hmgcc.gsi.gov.uk> Sent by: ids-bounces@iiug.org 14-Mar-07 10:27 PM Please respond to ids@iiug.org To ids@iiug.org cc Subject Re: IDS 9.4 and On-Bar [8663] For testing purposes only I have 1. set the retention policy to 1 day ism_config -retention 1 and checked the settings using nsradmin -c 2. labeled my test tapes mon, tue, wed, thu, fri ism_op -label /dev/rmt/0mnb -pool ISMData -volume mon 3. on Friday I did a level 0 backup onto the fri tape successfully onbar -b 4. on Monday I did another level 0 backup onto the mon tape successfully onbar -b 5. on Tuesday I reloaded the fri tape which should now have expired and did another level 0 backup. It simply added another saveset to the volume rather than overwriting the saveset written on Friday I have been told there is an internal ISM task that runs when there is low activity on the ISM server to expire savesets and it will not reuse the tape until all savesets have expired. So in setting the retention period to 1 day and leaving it over the weekend I assumed that the single saveset from Friday would now have expired. Am I missing something ? Is there something else I need to do to get it to reuse the tapes ? ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.