Re: Remove onbar expired images

Hello theBP, Sure basically I ran all the onsmsync command possibilities i.e. onsmsync, onsymsync -g 1, onsmsync -i etc... 1. Version of Solaris - Solaris 10 2. Version of Netbackup - 6.5.2A 3. $INFORMIXDIR/etc/sm_versions - 1|1.1.0|VERITAS-NetBackup|1| 4. bar_act.log 2009-02-11 16:26:36 28617 2435 onsmsync -g 1 2009-02-11 16:26:38 28617 2435 Syncing sysutils and bootfile... 2009-02-11 16:26:39 28617 2435 Working with veritas-netbackup as generic storage manager. 2009-02-11 16:26:39 28617 2435 Successfully connected to Storage Manager. 2009-02-11 16:26:39 28617 2435 Querying for backups expired at Storage Manager... 2009-02-11 16:26:48 28617 2435 Building current timeline... 2009-02-11 16:26:48 28617 2435 onsmsync complete, returning 126 (0x7e) 6. Is the storage manager local or on another machine? - On another machine 7. If of another machine, does the local SM client report anything? - No, when I run onsmsync commands the SM doesn't report anything. 8. Do backups work? - Yes backups and restores work well. On Wed, Feb 11, 2009 at 4:20 AM, theBP <theBP@usenet-news.net> wrote: > Informix DBA wrote: > > Hello theBP, > > > > Yes I got your other email/post and I have read up on the > > documentation. However, none of those onsmsync commands work. Informix > > support is still looking into. > > > > Which Storage Manager have you seen the onsmsync work with? We are > > using Symantec's NetBackup as our storage manager. > > > > --David > > > Err, loads. (Mainly XBSA compliant ones ;) > > If you could expand a bit on "none of the onsmsync commands work" that may > help. > > Like : > > 1. Version of Solaris > 2. Version of Netbackup > 3. $INFORMIXDIR/etc/sm_versions > 4. bar_act.log > 6. Is the storage manager local or on another machine? > 7. If of another machine, does the local SM client report anything? > 8. Do backups work? > > etc. etc. etc. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >

Informix DBA wrote: > Hello theBP, > > Sure basically I ran all the onsmsync command possibilities i.e. > onsmsync, onsymsync -g 1, onsmsync -i etc... > > 1. Version of Solaris - Solaris 10 > 2. Version of Netbackup - 6.5.2A > 3. $INFORMIXDIR/etc/sm_versions - 1|1.1.0|VERITAS-NetBackup|1| > 4. bar_act.log > 2009-02-11 16:26:36 28617 2435 onsmsync -g 1 > 2009-02-11 16:26:38 28617 2435 Syncing sysutils and bootfile... > 2009-02-11 16:26:39 28617 2435 Working with veritas-netbackup as > generic storage manager. > 2009-02-11 16:26:39 28617 2435 Successfully connected to Storage Manager. > 2009-02-11 16:26:39 28617 2435 Querying for backups expired at Storage > Manager... > 2009-02-11 16:26:48 28617 2435 Building current timeline... > 2009-02-11 16:26:48 28617 2435 onsmsync complete, returning 126 (0x7e) > 6. Is the storage manager local or on another machine? - On another machine > 7. If of another machine, does the local SM client report anything? - > No, when I run onsmsync commands the SM doesn't report anything. > 8. Do backups work? - Yes backups and restores work well. > > > On Wed, Feb 11, 2009 at 4:20 AM, theBP <theBP@usenet-news.net > <mailto:theBP@usenet-news.net>> wrote: > > Informix DBA wrote: > > Hello theBP, > > > > Yes I got your other email/post and I have read up on the > > documentation. However, none of those onsmsync commands work. > Informix > > support is still looking into. > > > > Which Storage Manager have you seen the onsmsync work with? We are > > using Symantec's NetBackup as our storage manager. > > > > --David > > > Err, loads. (Mainly XBSA compliant ones ;) > > If you could expand a bit on "none of the onsmsync commands work" > that may help. > > Like : > > 1. Version of Solaris > 2. Version of Netbackup > 3. $INFORMIXDIR/etc/sm_versions > 4. bar_act.log > 6. Is the storage manager local or on another machine? > 7. If of another machine, does the local SM client report anything? > 8. Do backups work? > > etc. etc. etc. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org <mailto:Informix-list@iiug.org> > http://www.iiug.org/mailman/listinfo/informix-list > > Check your ixbar.<servernum> for anything wierd (i.e.is there any "corruption" like half a line, or basically something that could be mis-parsed, permissions?? If you only want 5 weeks worth, trim the ixbar file to hold just the 5 weeks worth (make sure you have the oldest Level 0 and the log which was active at the beginning of the level 0 in the ixbar file. Have you a test environment where you could just set up a dummy instance and do some backups from there? Always nice to test on ... test instances. Probably not a good idea to post the ixbar file here.

I check the ixbar file and there is no corruption. I even deleted it and ran onsmsync -b which does work as it only syncs the ixbar and sysutils tables. So it generated a nice new clean file. Yes I have been testing on a small test instance in a test environment. Yes I guess I will have to trim the ixbar file manually (automated) and delete records from the sysutils onbar tables. As far as I know now there is the ixbar file and the 4 onbar tables in sysutils. Is there anything else that I need to be aware of or any "gotchas" when trimming the file or deleting records from those 4 tables? --Dave On Wed, Feb 11, 2009 at 5:43 PM, theBP <theBP@usenet-news.net> wrote: > Informix DBA wrote: > > Hello theBP, > > > > Sure basically I ran all the onsmsync command possibilities i.e. > > onsmsync, onsymsync -g 1, onsmsync -i etc... > > > > 1. Version of Solaris - Solaris 10 > > 2. Version of Netbackup - 6.5.2A > > 3. $INFORMIXDIR/etc/sm_versions - 1|1.1.0|VERITAS-NetBackup|1| > > 4. bar_act.log > > 2009-02-11 16:26:36 28617 2435 onsmsync -g 1 > > 2009-02-11 16:26:38 28617 2435 Syncing sysutils and bootfile... > > 2009-02-11 16:26:39 28617 2435 Working with veritas-netbackup as > > generic storage manager. > > 2009-02-11 16:26:39 28617 2435 Successfully connected to Storage > Manager. > > 2009-02-11 16:26:39 28617 2435 Querying for backups expired at Storage > > Manager... > > 2009-02-11 16:26:48 28617 2435 Building current timeline... > > 2009-02-11 16:26:48 28617 2435 onsmsync complete, returning 126 (0x7e) > > 6. Is the storage manager local or on another machine? - On another > machine > > 7. If of another machine, does the local SM client report anything? - > > No, when I run onsmsync commands the SM doesn't report anything. > > 8. Do backups work? - Yes backups and restores work well. > > > > > > On Wed, Feb 11, 2009 at 4:20 AM, theBP <theBP@usenet-news.net > > <mailto:theBP@usenet-news.net>> wrote: > > > > Informix DBA wrote: > > > Hello theBP, > > > > > > Yes I got your other email/post and I have read up on the > > > documentation. However, none of those onsmsync commands work. > > Informix > > > support is still looking into. > > > > > > Which Storage Manager have you seen the onsmsync work with? We > are > > > using Symantec's NetBackup as our storage manager. > > > > > > --David > > > > > Err, loads. (Mainly XBSA compliant ones ;) > > > > If you could expand a bit on "none of the onsmsync commands work" > > that may help. > > > > Like : > > > > 1. Version of Solaris > > 2. Version of Netbackup > > 3. $INFORMIXDIR/etc/sm_versions > > 4. bar_act.log > > 6. Is the storage manager local or on another machine? > > 7. If of another machine, does the local SM client report anything? > > 8. Do backups work? > > > > etc. etc. etc. > > _______________________________________________ > > Informix-list mailing list > > Informix-list@iiug.org <mailto:Informix-list@iiug.org> > > http://www.iiug.org/mailman/listinfo/informix-list > > > > > > Check your ixbar.<servernum> for anything wierd (i.e.is there any > "corruption" like half a line, or basically something that could > be mis-parsed, permissions?? > > If you only want 5 weeks worth, trim the ixbar file to hold just the 5 > weeks worth (make sure you have the oldest Level 0 and the > log which was active at the beginning of the level 0 in the ixbar file. > > Have you a test environment where you could just set up a dummy instance > and do some backups from there? Always nice to test on ... > test instances. > > Probably not a good idea to post the ixbar file here. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >

Informix DBA wrote: > I check the ixbar file and there is no corruption. I even deleted it > and ran onsmsync -b which does work as it only syncs the ixbar and > sysutils tables. So it generated a nice new clean file. > > Yes I have been testing on a small test instance in a test environment. > > Yes I guess I will have to trim the ixbar file manually (automated) and > delete records from the sysutils onbar tables. As far as I know now > there is the ixbar file and the 4 onbar tables in sysutils. Is there > anything else that I need to be aware of or any "gotchas" when trimming > the file or deleting records from those 4 tables? > > --Dave > :-/ I would not really recommend that :-/ Work out the issue is probably the best way :)

theBP wrote: > Informix DBA wrote: >> I check the ixbar file and there is no corruption. I even deleted it >> and ran onsmsync -b which does work as it only syncs the ixbar and >> sysutils tables. So it generated a nice new clean file. >> >> Yes I have been testing on a small test instance in a test environment. >> >> Yes I guess I will have to trim the ixbar file manually (automated) >> and delete records from the sysutils onbar tables. As far as I know >> now there is the ixbar file and the 4 onbar tables in sysutils. Is >> there anything else that I need to be aware of or any "gotchas" when >> trimming the file or deleting records from those 4 tables? >> >> --Dave >> > > :-/ > > I would not really recommend that :-/ > > Work out the issue is probably the best way :) Hmmm ... Provide an ls -l of : - the ixbar.* files and df -k of the filesystem. - onsmsync Issue would seem to be related to writing the new ixbar file or moving the existing one to an old name