We had to set the virus scanner to ignore the ~snapshot directory to get rid of
the bulk of our access denied problems.
We still have an ongoing problem with wide UTF characters (tickets open with
IBM to resolve it), despite OnTap 7.3.4 and TSM 6.2.3.1. If I recall
correctly, we were seeing those invalid file handle messages related to this,
as well. We're also getting a fair number of "ANS1304W: An active backup
version could not be found", which I haven't been able to figure why.
To the original poster's question, we're running snapdiff from a 6.2 client to
a 5.4 server. IBM will tell you to piss off if you have any problems, though,
unless you can reproduce it against a 6.1 or 6.2 server.
-
Cameron Hanover
chanover AT umich DOT edu
Fill with mingled cream and amber,
I will drain that glass again.
Such hilarious visions clamber
Through the chamber of my brain —
Quaintest thoughts — queerest fancies
Come to life and fade away;
What care I how time advances?
I am drinking ale today.
—-Edgar Allan Poe
On Sep 22, 2011, at 3:44 PM, Huebschman, George J. wrote:
> I have the same issue...at least it sounds the same, with messages like
> this
> (Paraphrased)
> ANS4013E Invalid File Handle, and ANS4007E Access to the object denied
>
> I have been manually toggling virus scanning off and triggering manual
> backups of the errant files. That gets them backed up.
> Size of the file seems to be a factor...but not always.
>
> George Huebschman
> Storage Support Administrator
> Legg Mason, LMTS
>
> When you have a choice, spend your money where you would want to work if
> it was your only choice, because soon it might be.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Remco Post
> Sent: Thursday, September 22, 2011 3:30 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] snapdiff advice
>
> good to hear. We have major issues with a windows client for CIFS
> shares. The client keeps on complaining about the right to backup the
> file permissions without any clear indication of what is wrong. We even
> tried runninf the client as a domain admin with full access rights to
> everything and still no go....
>
> On 22 sep. 2011, at 20:57, Shawn Drew wrote:
>
>> I did have this working on TSM 5.5 with a TSM 6.2 AIX client (nfs
> shares).
>>
>>
>> We just have a subset of volumes that are on vfilers that is
> preventing
>> me from adopting this solution "whole-hog"
>>
>>
>> Regards,
>> Shawn
>> ________________________________________________
>> Shawn Drew
>>
>>
>>
>>
>>
>> Internet
>> r.post AT PLCS DOT NL
>>
>> Sent by: ADSM-L AT VM.MARIST DOT EDU
>> 09/22/2011 01:25 PM
>> Please respond to
>> ADSM-L AT VM.MARIST DOT EDU
>>
>>
>> To
>> ADSM-L
>> cc
>>
>> Subject
>> Re: [ADSM-L] snapdiff advice
>>
>>
>>
>>
>>
>>
>> Hi All,
>>
>> I've got another question, maybe not for the FAQ ;-)
>>
>> Has anybody got this working?
>>
>> And maybe for the FAQ:
>>
>> Are there TSM server requirements? Does SnapDiff require the TSM
> server to
>> be at version 6, or is a 5.5 server supported?
>>
>>
>> On 22 sep. 2011, at 17:31, Shawn Drew wrote:
>>
>>> I'd like to add a question to the FAQ if possible. I'll ask it
>> frequently
>>> if it helps getting it added!
>>>
>>> The documentation explicitly states that vfiler support (Multistore)
> is
>>> not supported. Is support for this somewhere on the roadmap? or is
>> there
>>> something on the Netapp side that prevents this?
>>>
>>> Regards,
>>> Shawn
>>> ________________________________________________
>>> Shawn Drew
>>>
>>>
>>>
>>>
>>>
>>> Internet
>>> ramke AT US.IBM DOT COM
>>>
>>> Sent by: ADSM-L AT VM.MARIST DOT EDU
>>> 09/22/2011 09:07 AM
>>> Please respond to
>>> ADSM-L AT VM.MARIST DOT EDU
>>>
>>>
>>> To
>>> ADSM-L
>>> cc
>>>
>>> Subject
>>> Re: [ADSM-L] snapdiff advice
>>>
>>>
>>>
>>>
>>>
>>>
>>> Hello Paul and David,
>>>
>>> A frequently asked questions website has been created for snapshot
>>> differencing.
>>> We have attempted to answer the questions you have recently raised.
>>>
>>>
>>
> https://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/Sn
> apshot
>>
>>>
>>> +Differencing+FAQ
>>>
>>>
>>>
>>> This message and any attachments (the "message") is intended solely
> for
>>> the addressees and is confidential. If you receive this message in
>> error,
>>> please delete it and immediately notify the sender. Any use not in
>> accord
>>> with its purpose, any dissemination or disclosure, either whole or
>> partial,
>>> is prohibited except formal approval. The internet can not guarantee
> the
>>> integrity of this message. BNP PARIBAS (and its subsidiaries) shall
>> (will)
>>> not therefore be liable for the message if modified. Please note that
>> certain
>>> functions and services for BNP Paribas may be performed by BNP
> Paribas
>> RCC, Inc.
>>
>> --
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post AT plcs DOT nl
>> +31 6 248 21 622
>>
>>
>>
>> This message and any attachments (the "message") is intended solely
> for
>> the addressees and is confidential. If you receive this message in
> error,
>> please delete it and immediately notify the sender. Any use not in
> accord
>> with its purpose, any dissemination or disclosure, either whole or
> partial,
>> is prohibited except formal approval. The internet can not guarantee
> the
>> integrity of this message. BNP PARIBAS (and its subsidiaries) shall
> (will)
>> not therefore be liable for the message if modified. Please note that
> certain
>> functions and services for BNP Paribas may be performed by BNP Paribas
> RCC, Inc.
>
> --
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post AT plcs DOT nl
> +31 6 248 21 622
>
> IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
> therefore recommends that you do not send any confidential or sensitive
> information to us via electronic mail, including social security numbers,
> account numbers, or personal identification numbers. Delivery, and or timely
> delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
> that you do not send time sensitive
> or action-oriented messages to us via electronic mail.
>
> This message is intended for the addressee only and may contain privileged or
> confidential information. Unless you are the intended recipient, you may not
> use, copy or disclose to anyone any information contained in this message. If
> you have received this message in error, please notify the author by replying
> to this message and then kindly delete the message. Thank you.
>
>
|
