It is basic, but after you commented out the include.image statement,
did you restart the scheduler?
Is the Client still associated to an image backup schedule?
To answer whether the tapeonly management class is still being used, you
can look up what management class your data is using either at the
client or the server.
        Query backup at the client
        Or, at the server run a select against the backups table...that
is a heavy query to run though.  If you have a large db it can take a
long time to run.  Limiting the query by object type and filespace_id
will make it more efficient.  That will also show you if it is still
trying to do image backups.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jeff White
Sent: Monday, April 14, 2008 7:36 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Image Backup/Incr Backup Problem

Hi



TSM SERVER v5.4.0 running on Windows 2003

TSM Client v5.4.0.2



I run a daily incremental backup of a filesystem and writes to a 1tb
disk pool.



The Filesystem is 2tb, the occupied space is 1..45tb. The Incremental BU
inspects c9m files and backs up approc 7gb.



This has ran successfully for some time now, but takes a long time to
run (the delay is at the inspection side).



So, i tried LVSA Snapshot Image backup as a test.

I created and activated a new management class called TAPEONLY. I then
updated the DSM.OPT file to say 'include.image e:\ tapeonly' to write
directly to tape (LTO3). Runs fine. I can see the tape mounts etc and
took 7 hrs to backup.



Now, having completed my test, when i have gone back to my normal incr
backups, i get message 'ANS1114I waiting for mount of offline media' - a
'query session' shows a tape mount. But i am not using the include/image
statement any longer (it is commented out of the DSM.OPT file) and it
should be going to disk pool, as it always has done.



I have read that if the server thinks the image to be backed up is
larger than the target storage pool, it will go to that storage pools'
next stgpool. In this case, i am wondering if the TSM server now expects
1.45tb (the LVSA Image size) but the disk_pool is only 1tb. Next stgpool
is the tape_pool, hence the ANS1114I message.



Any thoughts?



Jeff



************************************************************************
****
Woolworths plc
Registered Office: 242 Marylebone Road, London NW1 6JL Registered in
England, Number 104206

This e-mail is only intended for the person(s) to whom it is addressed
and may contain confidential information.  Unless stated to the
contrary, any opinions or comments are personal to the writer and do not
represent the official view of the company.  If you have received this
e-mail in error, please notify us immediately by reply e-mail and then
delete this message from your system Please do not copy it or use it for
any purposes,  or disclose its contents to any other person.  Thank you
for your co-operation.
************************************************************************
****
------------------------------------------------------------------------
------------
Email scanned for viruses and unwanted content by emailsystems

Information regarding this service can be found at www.emailsystems.com

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.