ADSM-L

Re: [ADSM-L] Is memoryefficientbackup incompatible with VM

2010-09-10 02:52:26
Subject: Re: [ADSM-L] Is memoryefficientbackup incompatible with VM
From: Grigori Solonovitch <Grigori.Solonovitch AT AHLIUNITED DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 10 Sep 2010 09:48:08 +0300
Try to upgrade TSM Client to the latest version (there is APAR from IBM). I 
have fixed similar problem by upgrading to 6.2.1.1 (6.2.1.2 now). I think 
latest 6.1.3 has the same fix as well.

________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Huebschman, George J. [gjhuebschman AT LEGGMASON DOT COM]
Sent: Friday, September 10, 2010 12:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Is memoryefficientbackup incompatible with VM

Or, should I just exclude the Y$?
=======================
Client - 6.1.3.0
Host - Win2K3 R2 SP2
TSM Server - 5.5.1.0
TSM Server OS - AIX 5.3.0.0
=======================

 - Backing up Windows VMs with standard BAclient
*** Backups have begun failing with ANS1030E messages, "The operating
system refused a TSM request for memory allocation."
I tried adding "memoryefficientbackup yes" to the dsm.opt file, then ran
an incremental manually.

Things looked better at first, CPU usage stayed low and the paging file
stayed below 2.7G.  But the client began throwing out thousands of
messages nearly identical to the following:

09/09/2010 15:35:29 ANS1228E Sending of object
'\\<server_name>\y$\default\main\Some_subFolder\SomePig\Wilbur\Charlotte
s\Ping.aspx' failed
09/09/2010 15:35:29 calloc() failed: Size 51706 File cuopt.cpp Line 444
09/09/2010 15:35:29 calloc() failed: Size 51706 File cuopt.cpp Line 445

 - The Y$ drive on this server is an IWFS (Intl. Wine & Food Soc.?)
filesystem.  (Possibly something related to the Interwoven application,
which runs on this server.)
 -  It is exactly the same size and utilization, to the byte, of the D:
drive but the objects backed up are not the same.
 -  The D: drive presents as a local drive.  In Device Manager, two
devices are shown under Disk drives as VMware Virtual disk SCSI Disk
Devices.  They are unnamed.  I tentatively assume they are C: and D:.
Drilling into properties shows one with "Bus Number 0, Target ID 1, LUN
0", and the other with Bus Number 0, Target ID 0, LUN 0.

I found an old apar IC48767: AE IC46065  related to the TSM 5.3.2 client
and specifically related to the Microsoft API call GetFileSecurity.  It
has superficially similar error messages, but it appears to be something
different.

? How do I get successful backups and avoid either clobbering this
server, or getting errors for an entire drive?



George Huebschman
Storage Support Team, Media Librarian
Legg Mason, LMTS
410 580-7911 (office)
410 522-8581 (mobile)

Please consider the environment before printing this e-mail



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.

Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
message and any attachments hereto may be legally privileged and confidential. 
The information is intended only for the recipient(s) named in this message. If 
you are not the intended recipient you are notified that any use, disclosure, 
copying or distribution is prohibited. If you have received this in error 
please contact the sender and delete this message and any attachments from your 
computer system. We do not guarantee that this message or any attachment to it 
is secure or free from errors, computer viruses or other conditions that may 
damage or interfere with data, hardware or software.

<Prev in Thread] Current Thread [Next in Thread>