What I can tell you is that my testing was done with a 7.1.4 server, and I
reproduced the symptoms consistent with the old defect I mentioned in my
prior email. When I applied the workaround for that issue (QUIET option), I
could do the restore. The other ADSM-L poster, Michael Prix, verified that
QUIET solved it for him, too. So based on what I know, everything works as
I have described. At this time I have no reason to think that this is
attributable to a specific version of the server.
If you have a 184.108.40.206 client, try the same testing I described earlier:
back up a file to a 7.1.1 server, then try to restore it. Make sure you
explicitly specify the file for the restore file spec (not just the
dsmc restore /mydir/myfile.txt
and that VERBOSE logging is enabled. I would expect you to get the same
message, ANS4035W. Then try the restore again, with QUIET, and see if it
avoids the issue.
Assuming that this all works as I describe, then I would expect the same
behavior for 7.1.4 (or later) as I would for 7.1.1, or any prior server
If, in fact, the restore from tape from the 7.1.1 server is successful with
VERBOSE logging enabled, then repeat the restore like this:
dsmc restore /mydir/myfile.txt -traceflags=service,verbdetail
and send me the resulting trace file, and I will see what I can see...
Andrew Raibeck | IBM Spectrum Protect Level 3 | storman AT us.ibm DOT com
IBM Tivoli Storage Manager links:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2016-04-29
> From: "Schofield, Neil (Storage & Middleware, Backup & Restore)"
> <Neil.Schofield AT LLOYDSBANKING DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 2016-04-29 10:39
> Subject: Re: TSM Server 7.1.4 woes
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> Thanks for looking into this. We've got an upgrade from 7.1.1 to 7.
> 1.4 planned for next week so this thread got me a little worried as
> it does involve some legacy clients.
> Just so we're clear, can I reassure our users that with regards to
> this specific issue there will be no difference in the behaviour of
> the legacy clients between the two server versions? I know you
> managed to reproduce the issue that Mark described on a 7.1.4
> server, but I wondered whether you'd been able to prove it also
> existed with any server version prior to 7.1.4?
> Neil Schofield
> Tivoli Storage Manager SME
> Backup & Recovery | Storage & Middleware | Central Infrastructure
> Services | Infrastructure & Service Delivery | Group IT
> LLOYDS BANKING GROUP
> Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh
> EH1 1YZ. Registered in Scotland no. SC95000. Telephone: 0131 225
> 4555. Lloyds Bank plc. Registered Office: 25 Gresham Street, London
> EC2V 7HN. Registered in England and Wales no. 2065. Telephone
> 0207626 1500. Bank of Scotland plc. Registered Office: The Mound,
> Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. Telephone:
> 03457 801 801. Cheltenham & Gloucester plc. Registered Office:
> Barnett Way, Gloucester GL4 3RL. Registered in England and Wales
> 2299428. Telephone: 0345 603 1637
> Lloyds Bank plc, Bank of Scotland plc are authorised by the
> Prudential Regulation Authority and regulated by the Financial
> Conduct Authority and Prudential Regulation Authority.
> Cheltenham & Gloucester plc is authorised and regulated by the
> Financial Conduct Authority.
> Halifax is a division of Bank of Scotland plc. Cheltenham &
> Gloucester Savings is a division of Lloyds Bank plc.
> HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ.
> Registered in Scotland no. SC218813.
> This e-mail (including any attachments) is private and confidential
> and may contain privileged material. If you have received this e-
> mail in error, please notify the sender and delete it (including any
> attachments) immediately. You must not copy, distribute, disclose or
> use any of the information in it or any attachments. Telephone calls
> may be monitored or recorded.