Howdy, TSM folks.
So I think I've gotten to the bottom of a performance issue I've been
seeing recently (and a crash!) and I wanted to compare notes.
Cutting to the chase, I've been seeing obnoxious log consumption on one
of my TSM servers every night recently, and once a few months ago it got
Sent: Monday, April 16, 2012 2:22 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Objects Assigned vs. Your Database.
Howdy, TSM folks.
So I think I've gotten to the bottom of a performance issue I've been
seeing recently (and a crash!) and I wanted to compare notes.
Cutting to the chase, I've been
@VM.MARIST.EDU] On Behalf Of Rick
Adamson
Sent: Monday, April 16, 2012 3:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Objects Assigned vs. Your Database.
Allen,
I had the same issue on my 5.5. servers backing up 6.2.x.x client system states
and was able to remedy the situation by moving my
At 05:08 PM 4/16/2012, Prather, Wanda wrote:
But from experience at a customer where we had similar problems (Win2K8
clients were taking 8 hours for the incremental systemstate backup), the
long-term solution is to get your clients to a V6.2+ TSM server.
I'll echo Wanda's observations. We've
We do not allow Windows Vista/2008/7 System State backups to our
remaining V5.5 servers, and are reluctant to allow them on our new
V6.2.3 server. We enforce this with client option sets. Ever since Vista
landed, we have had extreme problems with the System State, and we
decided to simply prohibit
