Re: Errors during MS-SQL backup using the TSM API

2005-05-27 Thread Lawrence Clark
Yes, I looked it up on the IBM site. For my reading, if full backups are done on each of the databses on each of the nodes, and the previous instances are deleted, it will accomplish the same result. >>> [EMAIL PROTECTED] 05/27/2005 11:53:49 AM >>> Richard is correct. These are documented in the

Re: Errors during MS-SQL backup using the TSM API

2005-05-27 Thread Del Hoobler
Richard is correct. These are documented in the IBM knowledge base. The best and easiest thing to do is to change the nodename of your Data Protection for SQL clients and start with new filespaces with no pre-existing objects. Make sure your management classes are set up correctly and the INCLUDE s

Re: Errors during MS-SQL backup using the TSM API

2005-05-27 Thread Richard Sims
Larry - Search on ANS0328E at the IBM site for APARs which describes the consistency problem which is occurring where management classes are changed. Richard Sims On May 27, 2005, at 10:45 AM, Lawrence Clark wrote: Last night we had an error on all our MS-SQL backups using the TSM API. The

Errors during MS-SQL backup using the TSM API

2005-05-27 Thread Lawrence Clark
Last night we had an error on all our MS-SQL backups using the TSM API. The only change to the configuration was that explicit mangement class assignments were added in the optioins file for the API. The management class for the databases backed up are assigned correctly and the backups appear to a