I must say I'd be amazed if that was the case, it's not just a few files
it's skipping it's thousands. I've included a snippet from the server error
log.
>From what I understand, TSM is attempting to restore a file to a directory
that dosn't yet exist. We have not as yet rstored a complete server to see
what happens at the end but I've been told by IBM that TSM will not retry
the files at the end of the restore so cannot see how they wuold be
restored.

Ignore the dates, just noticed we hadn't set the date right on the server we
were playing with.

Thanks in advance.

        .........Rikk

19-08-2001 23:51:57 ANS1905E NetWare SMS error processing
'VOL1:/USERS/EverettV/WORK BITS/HSE Details/HS
10/form_hs10_-_annual_health_&_safety_training_and_competency_review
(EQUINET) 20-02-2002.doc':
(TSA500.NLM 5.5 315) The program's attempt to scan failed, probably because
an invalid path was specified.
19-08-2001 23:51:57 ANS1905E NetWare SMS error processing
'VOL1:/USERS/EverettV/WORK BITS/HSE Details/HS 10/RMS HS10 Manager Annual
Review 2001.doc':
(TSA500.NLM 5.5 315) The program's attempt to scan failed, probably because
an invalid path was specified.
19-08-2001 23:51:57 ANS1905E NetWare SMS error processing
'VOL1:/USERS/EverettV/WORK BITS/HSE Details/HS 10/RMS HS10B Manager Annual
Review 2001.doc':
(TSA500.NLM 5.5 315) The program's attempt to scan failed, probably because
an invalid path was specified.
------------------------------------------------------------------

Rikk,

Are you observing this behavior?  When NetWare is restoring files which do
not have a supporting directory structure, a temporary directory entry
(i.e., no trustee information) is created by Novell's backup API; when the
directory entries do come from the server at a later time they are
restored over the  temporary directory entry; the end result is that the
files and directories are restored fully and correctly regardless of their
ordering from the server.  If you are not seeing this behavior, I would
suggest talking to the service organization.

Thanks,
Jim

J.P. (Jim) Smith
TSM Client Development

>>>

-----Original Message-----
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: 31 July 2002 13:51
To: [EMAIL PROTECTED]
Subject: Re: Backing Up Dir's


Along this thread...  Are there any guidelines for retention and number of
copies in the DIRMC management class? I've looked and looked and it seems
the best scenario is to clone your management class with the longest
retention. But, is this correct?

John G. Talafous              IS Technical Principal
The Timken Company            Global Software Support
P.O. Box 6927                 Data Management
1835 Dueber Ave. S.W.         Phone: (330)-471-3390
Canton, Ohio USA  44706-0927  Fax  : (330)-471-4034
[EMAIL PROTECTED]           http://www.timken.com


**********************************************************************
This message and any attachments are intended for the
individual or entity named above. If you are not the intended
recipient, please do not forward, copy, print, use or disclose this
communication to others; also please notify the sender by
replying to this message, and then delete it from your system.

The Timken Company
**********************************************************************


****************************************************************************************************
Equitas Limited, 33 St Mary Axe, London EC3A 8LL, UK
NOTICE: This message is intended only for use by the named addressee
and may contain privileged and/or confidential information.  If you are
not the named addressee you should not disseminate, copy or take any
action in reliance on it.  If you have received this message in error
please notify [EMAIL PROTECTED] and delete the message and any
attachments accompanying it immediately.

Equitas reserve the right to monitor and/or record emails, (including the
contents thereof) sent and received via its network for any lawful business
purpose to the extent permitted by applicable law

Registered in England: Registered no. 3173352 Registered address above
****************************************************************************************************

Reply via email to