Hi,
how to cancel a session with media wait in a manual library? can sess does
not work. TSM keeps the waiting session even if you restart the client node.
(TSM server 5.3 in AIX 5.3) The session will die after the 60 minutes of
timeout.
Thanks
: Wednesday, August 18, 2010 5:55 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] cancel a session with MediaW
Hi,
how to cancel a session with media wait in a manual library? can sess
does
not work. TSM keeps the waiting session even if you restart the client
node.
(TSM server 5.3 in AIX 5.3
the process. I would have to wait until it finished that file
before. That doesn't happen anymore and the process cancels immediately
now.
I'm not sure if that directly correlates with this issue as I haven't
canceled a mediaW session in a while.
Regards,
Shawn
Agreed, I noticed this also Shawn
~Rick
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Shawn Drew
Sent: Wednesday, August 18, 2010 10:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] cancel a session with MediaW
They did change the way
Hi,
I'm on TSM server v.5.2 Win2000, TSM TDP for SQL client v.5.2 Win2000
I've done TDPSQL restores in the past successfully, but now I've got a
strange problem.
There are two sessions between server and client. One is on SendW, the other
on MediaW. There is only one mount and I've got three empty
On Feb 2, 2005, at 5:09 AM, Yiannakis Vakis wrote:
I'm on TSM server v.5.2 Win2000, TSM TDP for SQL client v.5.2 Win2000
I've done TDPSQL restores in the past successfully, but now I've got a
strange problem.
There are two sessions between server and client. One is on SendW, the
other
on MediaW
02, 2005 5:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: TDPSQL restore - MediaW
Hi,
I'm on TSM server v.5.2 Win2000, TSM TDP for SQL client v.5.2 Win2000
I've done TDPSQL restores in the past successfully, but now I've got a
strange problem. There are two sessions between server and client. One
streams.
-Original Message-
From: Yiannakis Vakis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 5:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: TDPSQL restore - MediaW
Hi,
I'm on TSM server v.5.2 Win2000, TSM TDP for SQL client v.5.2 Win2000
I've done TDPSQL restores
: Dist Stor Manager [EMAIL PROTECTED]
19.06.2003 17:50
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Client backups in MediaW state
We often run into this situation: Client backups normally go to the disk
storage pool, but if it fills
We often run into this situation: Client backups normally go to the disk
storage pool, but if it fills up, they start going directly to tape. We
have many more clients than tape drives, so we eventually have a number of
clients in MediaW state. Eventually, migration frees up a good portion
increase your disk pool, thats the best solution
-Original Message-
From: Brazner, Bob [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 19, 2003 9:50 AM
To: [EMAIL PROTECTED]
Subject: Client backups in MediaW state
We often run into this situation: Client backups normally go to the disk
Richard,
I'm glad you mentioned VirtualMountPoint. Is there ANY way to simulate
that in Windows?
Gosh, Tab, are you still using the world's last wholly proprietary
operating system and enduring all the pain of System Objects?? ;-)
I'm not aware of any way in Windows to achieve the same
To: [EMAIL PROTECTED]
cc:
Subject:Re: AW: MediaW
Richard,
I'm glad you mentioned VirtualMountPoint. Is there ANY way to simulate
that in Windows?
Gosh, Tab, are you still using the world's last wholly proprietary
operating system and enduring all the pain
Tab,
I'm thinking you could have a script/cmd file that shares out the
directories on the drive, then assigns drive letters to the shares, and
another script that undoes this, and have them as your pre and post-sched
commands. Or even a script that would share a directory, attach to it,
back it
not)
Zlatko Krastev
IT Consultant
David E Ehresman [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
12.06.2003 15:29
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: MediaW
IBM/TSM reps spent a lot of capital
PROTECTED]
Betreff: Re: MediaW
Our target is satisfactory restore time. It has been our experience
that if one has adequate set up for restore the backups run just fine.
In our shop, adequate restore time requires collocation. That said, in
my shop one must also take into account workplace
That begs the question of why a collocated session can not have
multiple backup threads.
Collocation is often diminished in List discussions for lack of
qualification. That is, there are two types of Collocation:
by node, and by filespace. Therein lies additional opportunity,
further enhanced
Administrator
Laitram LLC
Richard Sims [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
06/13/2003 08:08 AM
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: AW: MediaW
That begs the question of why a collocated
.
Zlatko Krastev
IT Consultant
David E Ehresman [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
11.06.2003 17:56
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: MediaW
Thanks Geoff. We'd much rather have
[EMAIL PROTECTED]
11.06.2003 17:56
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: MediaW
Thanks Geoff. We'd much rather have the session wait during backups
than during restore so we'll leave collocation on and ignore
]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
12.06.2003 15:29
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: MediaW
IBM/TSM reps spent a lot of capital and management spent a lot of money
to get us to an environment
Tulsa, OK 74116-5020
* phone: +01-918-292-4364
* cell: +01-918-629-1819
* mailto:[EMAIL PROTECTED]
www.eds.com
-Original Message-
From: David E Ehresman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2003 2:27 PM
To: [EMAIL PROTECTED]
Subject: MediaW
I have a client node
Yes, there are adequate scratch volumes and drives and paths are
online.
Thanks,
David
[EMAIL PROTECTED] 06/10/03 03:48PM
Any ideas why a tape is not being mounted?
This may not be the issue, but is the destination stgpool configured
with
an adequate number of scratch volumes allowed
To: [EMAIL PROTECTED]
Subject: Re: MediaW
Collocation is set YES. Can collocation not go to multiple tapes?
[EMAIL PROTECTED] 06/10/03 03:44PM
David,
Have you verified that collocation is set to NO on the tape storage
pool
that this client is backing up to.
Geoff Raymer
EDS - Tulsa BUR
]
LLE.EDU cc:
Sent by: ADSM: Fax to:
Dist StorSubject: Re: MediaW
Manager
[EMAIL PROTECTED]
.EDU
06/11/2003 09
Thanks Geoff. We'd much rather have the session wait during backups
than during restore so we'll leave collocation on and ignore the
MediaW.
David
[EMAIL PROTECTED] 06/11/03 10:32AM
David,
We have had these same types of problems when collocation is set to
yes.
Try turning it off and running
If warranted, you can momentarily toggle the active tape volume status
from READWrite to READOnly, then back, to cause the multiple sessions
to each get their own output volumes.
Richard Sims, BU
I have a client node that backs up over the lan to tape. When I do a Q
SESS during a backup, there are 3-4 sessions running. One session has a
tape mounted but one of the others remains in MediaW. The node has
Maximum Mount Points Allowed: 2 defined. The device class has Mount
Limit: DRIVES
]
www.eds.com
-Original Message-
From: David E Ehresman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2003 2:27 PM
To: [EMAIL PROTECTED]
Subject: MediaW
I have a client node that backs up over the lan to tape. When I do a Q
SESS during a backup, there are 3-4 sessions running. One
Any ideas why a tape is not being mounted?
This may not be the issue, but is the destination stgpool configured with
an adequate number of scratch volumes allowed (MAXSCRATCH)?
One other thing to look at - are all drives and paths online?
Ted
PROTECTED]
Subject: MediaW
I have a client node that backs up over the lan to tape. When I do a Q
SESS during a backup, there are 3-4 sessions running. One session has a
tape mounted but one of the others remains in MediaW. The node has
Maximum Mount Points Allowed: 2 defined. The device class has
From: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED]
We are on TSM server version 5.1.6.0 and I have noticed that
the stats for MediaW in the Summary table is incorrect some
of the time, but not all of the time. In doing a LAN-free
backup, the total time for the backup was 43
Hi all,
We are on TSM server version 5.1.6.0 and I have noticed that the stats for
MediaW in the Summary table is incorrect some of the time, but not all of
the time. In doing a LAN-free backup, the total time for the backup was 43
minutes. The summary table showed 2143 secs of mediaw time
My storage pools filled up causing by backups to go into a mediaw state
waiting for a tape drive to free up. My tape drives were busy migrating
data to free space in my storage pools. Is there anyway to force the
client sessions out of the mediaw and to start sending data to my disk
storage
My storage pools filled up causing by backups to go into a mediaw state
waiting for a tape drive to free up. My tape drives were busy migrating
data to free space in my storage pools. Is there anyway to force the
client sessions out of the mediaw and to start sending data to my disk
storage
Has anyone noticed when doing a restore from tape it almost grinds down
to a halt when another process/session requests the same tape?
We had this happen when an impatient client decided to run 2 restores, where
the data on the 2nd restore was on the same tape. The restore slowed from
5MB/s to
I run my backups at night around 10:30pm. I have around 50 servers doing
incrementals concurrently at this time. I noticed that about half are
experiencing MEDIAW when I do a "q session". They seem to be waitng to for
a tape to load in my library for them to write to but the st
My question is, if they are suppose to be going to
disk storage pool first and it isn't full then why are they waiting for
tape.
Richard - This is probably due to a large file which will not fit into
the space remaining in the disk storage pool such that it
must go into the next
PROTECTED]
Subject: MediaW problem
I run my backups at night around 10:30pm. I have around 50 servers doing
incrementals concurrently at this time. I noticed that about half are
experiencing MEDIAW when I do a "q session". They seem to be waitng to for
a tape to load in my librar
I noticed that about half are
experiencing MEDIAW when I do a "q session". They seem to be waitng to for
a tape to load in my library for them to write to but the storage pool that
these clients write to first is disk based then when it fills to 90% it
should migrate to tape. My question is, if t
To confirm that they are waiting on tape do a "q ses f=d"
Regards
Alex.
-Original Message-
From: Dearman, Richard [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 04, 2001 8:01 PM
To: [EMAIL PROTECTED]
Subject: MediaW problem
I run my backups at night around 10:30pm. I h
twice as fast.
Those are just some of the things you can do. But again, you don't have to,
your backups are getting done as is!
-Original Message-
From: Talafous, John G.
To: [EMAIL PROTECTED]
Sent: 3/4/01 2:56 PM
Subject: MediaW, Tape drive availability, Disk STGpool space
are, in fact, utilizing physical
tape drives. Notice also that there are twenty-three (23) client tasks with
MediaW as the session state. We have not begun sending client data direct to
tape because of the limited number of tape drives available. To date, this
performance enhancement has not been an issue
there are twenty-three (23) client tasks with
MediaW as the session state. We have not begun sending client data direct to
tape because of the limited number of tape drives available. To date, this
performance enhancement has not been an issue.
What is TSM doing? How can I better understand and provide
44 matches
Mail list logo
