ion is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" wrote on 2010-09-09
18:57:16:
> From: "Prather, Wanda"
> To: ADSM-L@vm.marist.edu
> Date: 2010-09-09 19:04
> Subject: Re
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Tim
Brown
Sent: Thursday, September 09, 2010 5:26 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] long time for client backup
Would the journal service help
Tim
-Original Message-
From: ADSM: Dist Stor Ma
On Sep 9, 2010, at 2:41 PM, Tim Brown wrote:
> Client backup starts 8:30PM, It takes 3 hours to get to first processed
> message
> ANS1898I * Processed 500 files *
> ...
That's the time it takes to query the TSM server for the inventory of Active
files for the file system: the mor
Would the journal service help
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Clark,
Margaret
Sent: Thursday, September 09, 2010 4:48 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: long time for client backup
I bet you've got a lot of l
mailto:ads...@vm.marist.edu] On Behalf Of Tim
Brown
Sent: Thursday, September 09, 2010 11:41 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] long time for client backup
Client backup starts 8:30PM, It takes 3 hours to get to first processed message
ANS1898I * Processed 500 files *
I
Client backup starts 8:30PM, It takes 3 hours to get to first processed message
ANS1898I * Processed 500 files *
I restarted the server, no difference, It happens to be a Windows 2003 cluster.
Any idea why it takes so long.
09/08/2010 20:33:09 --- SCHEDULEREC OBJECT BEGIN NT_WKD_OF
