Re: TDP mail upgrd from 6.4 to 7.1 - Windows Powershell 3.0 requirement?

Wanda, Powershell 3.0 is mentioned under the "additional Microsoft prerequisites" part. Op 21 mei 2014 05:08 schreef "Prather, Wanda" : > TDP for mail is at 6.4, Exchange 2010. > > Ran install of 7.1 on top, then ran setupfcm.exe. > Started DP for Exchange, it immediately fails with FMM50009E, sa

Re: TSM 7.1 upgrade

Lol, nt 4 and base lvl 5.1? Might want to look into some upgrading as both are out of support. Btw, apart from not running base level stuff, 7.1 doesn't support 5.1 clients. Op 16 mei 2014 21:28 schreef "Huebner, Andy" : > We are testing the upgrade from 6.2 to 7.1 and we get this error when > st

TDP mail upgrd from 6.4 to 7.1 - Windows Powershell 3.0 requirement?

TDP for mail is at 6.4, Exchange 2010. Ran install of 7.1 on top, then ran setupfcm.exe. Started DP for Exchange, it immediately fails with FMM50009E, says Windows Powershell 3.0 is a pre-req. Nothing about this in the planning & prereqs section of the TDP 7.1 install guide. Is there any impact

Re: EMC NDMP folder exclusion

Nope. TSM is just driving the NDMP support built into the NAS device. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Gee, Norman Sent: Tuesday, May 20, 2014 10:32 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] EMC NDMP folder exclusion Is they

Re: compressed file is corrupted and cannot be expanded (repost)

Kinda what I thought. I couldn't find anything via Googling. Thanks Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never

Re: SQL Query for "replstate"

Hi Harold, It may be diffrent with another version of TSM, but this is from a 6.3.4 : TSM> select distinct repl_state from nodes REPL_STATE --- ENABLED NONE -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: "Harold Vandeventer [BS]" À:

Re: compressed file is corrupted and cannot be expanded (repost)

Hi Zoltan, I recommend opening a PMR if you haven't already done so. Thank you, Del "ADSM: Dist Stor Manager" wrote on 05/20/2014 12:55:44 PM: > From: Zoltan Forray > To: ADSM-L@vm.marist.edu > Date: 05/20/2014 12:56 PM > Subject: compre

EMC NDMP folder exclusion

Is they a way to exclude certain sub-folders on an EMC NDMP backup using TSM? Within the EMC configuration there is a way to set environment variables to exclude directories, but TSM is ignoring the environment variables.

SQL Query for "replstate"

I need to run a query (such as SELECT * FROM WHERE = 'ENABLED') to list nodes and their "replstate" status But I don't find "REPLSTATE" as a column in the NODES table. And I don't see a column name that seems related. Q REPLNODE * returns multiple rows for each node; but REPLNODE is not a

compressed file is corrupted and cannot be expanded (repost)

I am reposting this since I didn't get any feedback whatsoever and am concerned I have a ticking time-bomb on my hand. I was hoping for IBM to chime-in. - Server: Linux 6.3.4.300Client 7.1.0.2 Doing a large restore and getting hundreds of these messages: 5/9/2014 10:05:47 AM ANE403

Exchange TDP upgrade

Hi folks, We are currently running TSM server 5.5 We are looking at upgrading our DP for Exchange. What is the latest supported level? I am reading here that 6.4 is not supported on server 5.5. The reason we are doing this is that we want to test single mailbox recovery and the last time I ra

Re: TSM client scheduler issue

It may mean the TSM Scheduler is already running when the Acceptor or dsmcad tries to start it. That can happen when a backup session crashes and an orphan Scheduler process is left dangling. And, I may be confusing two recent weird problems we had. One of them was a RC -53. K. On May 20, 2014

Re: TSM client scheduler issue

Thanks, It was a DNS issue. Resolved now :) -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco Post Sent: 20 May 2014 03:42 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM client scheduler issue tsm rc -53 means auth failure iirc, ch

Re: TSM client scheduler issue

tsm rc -53 means auth failure iirc, check your password settings. Op 20 mei 2014, om 15:03 heeft Swartz, Jerome het volgende geschreven: > Hi Fellow TSM'ers > > TSM server 5.5 > Client 5.4 > > It seems my client has lost connection to the backup server. > > Errorlog: > 5/20/2014 14:48:14 ANS

Re: TSM client scheduler issue

Can you PING the IP of the TSM Server? Or TELNET 1500? Those tests check for network connectivity and open firewalls. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Swartz, Jerome Sent: Tuesday, May 20, 2014 8:03 AM To: ADSM-L@VM.MARIST.EDU S

TSM client scheduler issue

Hi Fellow TSM'ers TSM server 5.5 Client 5.4 It seems my client has lost connection to the backup server. Errorlog: 5/20/2014 14:48:14 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 05/20/2014 14:48:14 ANS1029E Communication with the TSM s