ADSM-L

Re: [ADSM-L] How to determine why a session is in IdleW

2017-03-30 07:25:57
Subject: Re: [ADSM-L] How to determine why a session is in IdleW
From: "Lee, Gary" <glee AT BSU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 30 Mar 2017 11:24:29 +0000
How many items are on the drive to be restored?
I have had some restores where the drive contains many items sit in idle state 
for a long time while database activity is happening.

I believe this was the rationale for the no query restore.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray
Sent: Wednesday, March 29, 2017 4:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] How to determine why a session is in IdleW

I have a user who has started a big restore (>31M objects and 8TB of data)
and all it keeps doing is sit in an IdleW state.

He has tried restarting it numerous times, including rebooting this newly
rebuilt Windows 2012R2 server.  He has the latest 8.1 client.  He is not
receiving any error messages on the client side and I don't see anything
from the server side.

It has now been waiting for >10,500 seconds (almost 3-hours).  I have
watched it from the server side and the Bytes Sent/Received have not
changed.  During one of his previous attempts, the server was running
replication but I killed it - did not make a difference.

It should be considered an NQR since all he did was select the "D:" drive
and told it to start the restore.

So how can I figure out what is going on?

--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
<Prev in Thread] Current Thread [Next in Thread>