Hi Othonas, I followed the discussion about TDP for Informix 4.1 and I have another question belonging to this one. Question: Is there a 64bit support within TDP for Informix 4.1? We are about upgrading our 6 SAP R/3 systems to 4.6C and Informix 7.31 UC7 under AIX 4.3.3. All software (AIX, SAP R/3 and Informix) supports 64bit, only TDP for Informix 3.7.0 doesn't. Is there a TDP for Informix supporting 64bit? Thanks a lot. Rainer Holzinger Haindl Papier GmbH Augsburg, Germany Othonas Xixis <[EMAIL PROTECTED]> am 14.02.2001 00:14:54 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] Kopie: (Blindkopie: Rainer Holzinger/HAINDL) Thema: Re: TDP for Informix 4.1 - Expiring Informix logs ...? George, here is the answers to yr questions: Question1: Can the TDP 4.1 restore from one machine to another??? Answer1: Yes, it can, we just refreshed a 380 GB Lawson DB from the production server to the QA server this past weekend, no problem at all. Question2: Also can the TDP 4.1 backup individual data bases or tables from an application server ??? Answer2: Yes, it can, via onbar. Not only backup them, but also restore them as well. Of-course, on both cases DBA expertise are needed, however TSM works as designed. Cheers. Othonas George Lesho <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/13/2001 05:38:57 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: expiring Informix logs ...? That's great info. Many thanks... will look into the TDP 4.1... didn't know it existed and SQL-BackTrack for Informix is quite an art to get it to actually work. Can the TDP 4.1 restore from one machine to another??? our developers are always wanting to put the production application server (either PeopleSoft, Lawson or DataMart) onto a test box to recreate things. Seems to me that this capability would not be affected by going to the TDP 4.1 as it is done via a virtual host entry in the dsm.opt file. Also can the TDP 4.1 backup individual data bases or tables from an application server? That is one advantage the new SQL-BackTrack has over the older version.... there the Informix server had to be DOWN to do this and that is seldom acceptable in a 24 hours production environment... Thanks for any info - George George Lesho Storage/System Admin AFC Enterprises Othonas Xixis <[EMAIL PROTECTED]> on 02/13/2001 04:27:48 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: expiring Informix logs ...? Hi George, I am fine, busy as always... thanks for asking, how is San Antonio ? On this Informix issue, I guess Arnaud did not mentioned, and I didn't realize at first that he was using SQL-BackTrack. Tivoli nowadays has a new TDP for Informix 4.1 and works fine. We had three Informix installations lately and we installed the TDP for Informix on all of them (onbar - online, full, L0, & L1 backups) and things are working great, without using SQL-BackTrack. Again, and even with the TDP, all the DB data and the log data is expired via TSM management and copygroup configuration because Informix can't control and pass the expiration information to the API. Informix, *SM API, and SQL BT versions is the main factor to tune and make all three products to work appropriately. Thanks. Othonas George Lesho <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/13/2001 03:21:12 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: expiring Informix logs ...? Howdy Othonas! Hope you are doing well... haven't heard from you in a while... I think the problem with doing expiration and reclamation of backups made with SQL-BackTrack for Informix lies in the fact that if you use an older version of the product, the agent places a long time stamp on the filespace name making each name UNIQUE. Thus, you are left with a zillion unique filespaces, each being an ONLY version of a db backup. This truly complicates expiration.... you basically must go in and erase filespaces manually. With the newer version of SQL-BackTrack for Informix, it has the ability to delete back generation of a database. The generations term is used by BMC to distinguish between versions as each Informix backup is actually unique. It appears you can only retain 9 unique generations at most; meaning if you backup up daily, the most you can retain, using the agent is 9 days worth. You can also expire using a date. These features only became available on V.3... we are testing it now and it is a pain to install... BMC's directions are not great ;-(. Anyway, I am far from an expert in these matters but I do have some experience with deleting filesets which is necessary, even if you put backups into their own management class/copy group. BTW: I have completed implimenting all the recommendations you made and just finished documenting the whole mess. During the course of the documentation, I redid all management classes, copy groups and schedules to make them work the way we wanted and have everything revolving around our logical business day as you suggested. The redbook has some good tips on scheduling stuff so that our admin processes are not overlapping with backups and such. Thanks- hope my rambling made some sense... George Lesho Storage / System Admin AFC Enterprises Othonas Xixis <[EMAIL PROTECTED]> on 02/13/2001 10:28:39 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: expiring Informix logs ...? Arnaud hi, I am a little troubled understanding why you say that "TSM is unable to expire those logs". If you use a separate mgmt class and copygroup for your logs, and your copygroup parameters are set properly, TSM will expire your logs. Maybe if you want to give us some more details of yr installation... Cheers. Othonas PS: I bet Basel is beautiful this time of the year... Arnaud Brion <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/13/2001 11:01:42 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: expiring Informix logs ...? Hi everybody ! I come back on something that seems to be an old subject for *SM'ers : we're using the Onbar API to ensure the backup of our informix logs, what works really nicely, except we're facing a huge increasing of the number of tapes used for this storagepool, due to the fact that TSM is unable to expire those logs. We tried to install the onsmsync utility a few month ago, which was supposed to give us a rid of this problem, but I just saw today that it isn't working at all ! Does anybody know if Informix or Tivoli found a solution to this problem (new version of onsmsync ?), or if there is any other way expiring those #@#@@... logs ? I saw there is a c programm existing but I have no idea of c language so if you know something easier, just let me know ! Thanks in advance ! ;-) Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
