Re: Still huge problems with Mac OSX client 5.2.3.12
Morning all Can someone tell me where I can get a complete list of the trace flags available to the Mac client? Many thanks Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Still huge problems with Mac OSX client 5.2.3.12
Farren, Is there some reason that you can't upgrade to the latest Mac TSM client: 5.3.2.? All/most of our OSX backup complaints were fixed with Mac TSM client 5.3.2.0. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Still huge problems with Mac OSX client 5.2.3.12
Hi Well sadly we are still running TSM Server 5.1.6.2 as I'm still waiting for new server hardware to arrive to do the upgrade. It's been a struggle to get the money for the new kit hence I'm a little behind the times. I don't think a 5.3 client would work on a 5.1 server (though I could be wrong). Farren |-+---| | James R Owen | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 02/12/2005 09:22 |Subject| | | Re: [ADSM-L] Still huge | | Please respond to | problems with Mac OSX | | ADSM: Dist Stor| client 5.2.3.12 | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Farren, Is there some reason that you can't upgrade to the latest Mac TSM client: 5.3.2.? All/most of our OSX backup complaints were fixed with Mac TSM client 5.3.2.0. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU | ADSM-L@VM.MARIST.EDU | | | cc| | 01/12/2005 16:45 | | | | Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor | problems with Mac OSX | | Manager | client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained in
Re: Still huge problems with Mac OSX client 5.2.3.12
Farren, I don't have time now to look at the IBM/Tivoli web site for you, but we are using TSM clients 5.3.2.x with TSM servers 5.2.3.x here. I would expect any TSM client 5... to work with any TSM server 5... Unless you know/find otherwise on their website, I would download and try it. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Hi Well sadly we are still running TSM Server 5.1.6.2 as I'm still waiting for new server hardware to arrive to do the upgrade. It's been a struggle to get the money for the new kit hence I'm a little behind the times. I don't think a 5.3 client would work on a 5.1 server (though I could be wrong). Farren |-+---| | James R Owen | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 02/12/2005 09:22 |Subject| | | Re: [ADSM-L] Still huge | | Please respond to | problems with Mac OSX | | ADSM: Dist Stor| client 5.2.3.12 | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Farren, Is there some reason that you can't upgrade to the latest Mac TSM client: 5.3.2.? All/most of our OSX backup complaints were fixed with Mac TSM client 5.3.2.0. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or
Re: Still huge problems with Mac OSX client 5.2.3.12
A more recent client, v5.3.2.1, is now available. I haven't seen any major problems yet. On Dec 2, 2005, at 4:22 AM, James R Owen wrote: Farren, Is there some reason that you can't upgrade to the latest Mac TSM client: 5.3.2.? All/most of our OSX backup complaints were fixed with Mac TSM client 5.3.2.0.
Re: Still huge problems with Mac OSX client 5.2.3.12
Hi all Many thanks for all the help with this, but it looks like converting the file systems to Unicode is the only way forward. So now I have a 500Gb backup to do, oh dear :-( All the best to everyone Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons Ltd |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Still huge problems with Mac OSX client 5.2.3.12
Hi all Right, I know I have been here before but we are still having some baaad problems with our Mac OSX 5.2.3.12 clients. I'm currently still only running TSM Server 5.1.6.2 on Solaris until the hardware arrives for the upgrade (v soon), but as far as I am concerned, there should be no problem running 5.2 clients on a 5.1 server. In fact, as far as I know the TSM structure is designed to accommodate this. Now, at the moment, the file systems on the two Mac servers are NOT unicode enabled as this will mean full backups for both servers (which will take some time). I would rather get the server upgrade out of the way before doing this if it's even necessary. So, the problems I am seeing are whole groups of directories not being backed up! Since the upgrade to 5.2.3.12 I have been allowing the client to backup via the scheduler demon (which I could never get to work properly before). But I can see that where the client used to check some 300,000 files, it now only check 70,000 approx! I have never seen such problems with any other clients flavours and I really don't know where to start looking. Are there other people out there running Mac clients that are getting complete successful backups and if so is there something I'm doing wrong. Sadly I'm not a Mac admin so there may be something OS based that is wrong. Any help would be much appreciated as people are not very happy (and who can blame them). All the best Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Still huge problems with Mac OSX client 5.2.3.12
Hi all Well, it looks like we were having quite a few problems with version 5.1.5.16 of the Mac OSX client, but since going to 5.2.3.12 we have had even more. So, while I'm waiting to see if IBM can help me, I will probably have to end up going back to the previous version of the client. Now, I know that the older version of the client will be unable to restore data backed up by the later version, but is there anything else I need to be aware of when trying to downgrade. I assume that there will be data left lying around in the database with no-where to go? What happens to this, if anything? Thanks in advance Farren Minns Hi all Right, I know I have been here before but we are still having some baaad problems with our Mac OSX 5.2.3.12 clients. I'm currently still only running TSM Server 5.1.6.2 on Solaris until the hardware arrives for the upgrade (v soon), but as far as I am concerned, there should be no problem running 5.2 clients on a 5.1 server. In fact, as far as I know the TSM structure is designed to accommodate this. Now, at the moment, the file systems on the two Mac servers are NOT unicode enabled as this will mean full backups for both servers (which will take some time). I would rather get the server upgrade out of the way before doing this if it's even necessary. So, the problems I am seeing are whole groups of directories not being backed up! Since the upgrade to 5.2.3.12 I have been allowing the client to backup via the scheduler demon (which I could never get to work properly before). But I can see that where the client used to check some 300,000 files, it now only check 70,000 approx! I have never seen such problems with any other clients flavours and I really don't know where to start looking. Are there other people out there running Mac clients that are getting complete successful backups and if so is there something I'm doing wrong. Sadly I'm not a Mac admin so there may be something OS based that is wrong. Any help would be much appreciated as people are not very happy (and who can blame them). All the best Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Still huge problems with Mac OSX client 5.2.3.12
On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims
Re: Still huge problems with Mac OSX client 5.2.3.12
Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
