Hi
I have just test the new feature on TSM server 6.3 Tsm Replication on my test
environment , works fine very pleased …
A little question when trying to delete the nodename who was replicated on the
target server , I always get that ii can't be remove still in replicate status
I update the
you need to use remove replnode xxx on both servers.
Regards,
Alex Heindl
Von:Robert Ouzen rou...@univ.haifa.ac.il
An: ADSM-L@VM.MARIST.EDU
Datum: 16.04.2012 08:32
Betreff:[ADSM-L] Question about Tsm replication on V6.3
Gesendet von: ADSM: Dist Stor Manager
Cheers,
I've tried that already Rick. I saw the same, but to no avail.
John
Anybody else? :)
On 13/04/12 12:40, Rick Harderwijk wrote:
John,
The file is shown on my screen as having the # directly behind 1507 .
Should there be a space between these two?
Regards,
Rick
2012/4/13 John
Hi John,
Have you tried to specify the TCPPORT into the dsm.opt of baclient?
It works for me for the datamover node.
Thanks,
Hunter
I find my DB2 database in a deadlock condition. It's been deadlocked for about
40 hours.
It's run fine for many, many months until this weekend.
Running on Windows 2008 R2.
During node backup, migration kicked in (as it does frequently). But,
apparently, migration is trying to move a file
Are you also doing dedupe?
http://www-01.ibm.com/support/docview.wss?uid=swg1IC81115
___
John Monahan
Delivery Consultant
Logicalis, Inc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer,
We had this back in February, when a reorg deadlocked with a migration.
Get help right away, and while you're waiting, check APAR: IC81261
- Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [BS]
Sent: Monday, April
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
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 database and
log files to faster drives.
Historically, my TSM servers have not had sufficient local storage to
accommodate these volumes (as well as cached disk
Another bandaid:
For Win2K8 clients backing up to 5.5 servers, you can use the
SYSTEMSTATEBACKUPMETHOD parm described below in dsm.opt, to essentially force
the systemstate backup to work like it used to (all systemstate all of the
time), or opportunistic, (all systemstate if anything has
Thanks everyone...
IBM had me follow IC88605.
The issue was table/index reorg kicked in during the weekend when our schedules
are different.
I've been running this server for MONTHS without any problem.
I edited the serv.opt file, commented out the reorg parms and halted/started
TSM.
I'll
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
13 matches
Mail list logo
