Thanks Margaret... you provided the crisp and shortened version. We fought the setup for several days, but those are the commands we would have used. I was answering "off the top of my head" yesterday.
------------------------------------------------ Harold Vandeventer Systems Programmer State of Kansas - Department of Administration - Office of Information Technology Services [email protected] (785) 296-0631 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Clark, Margaret Sent: Tuesday, March 13, 2012 12:45 PM To: [email protected] Subject: Re: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010? A few additional comments (things we found out the hard way): For Data Protection for Exchange to work, the TSM Client Agent must be installed. The *TDP clients need to be set up using USERID=NONE, after which we set the proxy access using server commands like this: register admin ExchangeServerTDP ExchangeServer1 passexp=0 register admin ExchangeServer1 ExchangeServer1 passexp=0 grant authority ExchangeServerTDP class=node authority=owner node=ExchangeServerTDP grant authority ExchangeServer1 class=node authority=owner node=ExchangeServer1 grant proxynode target=ExchangeServerTDP agent=ExchangeServer1 - Margaret Clark -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Vandeventer, Harold [BS] Sent: Monday, March 12, 2012 12:23 PM To: [email protected] Subject: Re: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010? I've not looked for a Redbook, we fought the initial setup for several days, using PMRs to get through several of the steps. The TSM server is 6.2.3.0, running on Windows 2008 R2. The major points that I recall: Created a new Domain, with only one Mgmt Class, thus the default. In that domain: Created a nodename that is used at the BA-Client. Let's call this "ExchangeServer1". Created a second nodename that is used at the TDP-Client. Let's call this "ExchangeServerTDP". ExchangeServerTDP displays ExchangeServer1 as a Proxy Authority: Via the AdminCenter GUI, open ExchangeServerTDP, click Proxy Authority, add ExchangeSever1. Both nodes (ExchangeServerTDP and ExchangeServer1) were given "client owner" authority level in the TSM server Administrators list. Created two schedules: one for C:\EXCFULL.CMD; one for C:\EXCINCR.CMD. Assigned the schedules to ExchangeServerTDP. I didn't do all the TDP install and VSS setup testing; that was done by the Exchange Server admin. I can only work with the TSM Server side details. The TDP install apparently created the excfull.cmd and excincr.cmd files as examples for customization. I recall the Exchange Admin was impressed by the 6.3 TDP GUI and how some initial testing for VSS setup was fairly easy. Our knees were very bloody getting through all of it; and at the moment scheduled backup appears to be successful only if the TDP Scheduler Service has "logon as" set to a domain account that has Exchange permissions. We've not seen that as a requirement in the setup guide. Recall the phrase: Your mileage may vary! Good luck with it. ------------------------------------------------ Harold Vandeventer Systems Programmer State of Kansas - Department of Administration - Office of Information Technology Services [email protected] (785) 296-0631 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Sheridan, Peter T. Sent: Monday, March 12, 2012 1:27 PM To: [email protected] Subject: Re: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010? Do any of you have a runbook or set of procedures to follow to get TSM setup to backup Exchange 2010 ? I have see the manual/power shell script, etc.. but am still struggling with the setup. Thanks in advance for any help, Pete. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Daniel Sparrman Sent: Monday, March 12, 2012 9:39 AM To: [email protected] Subject: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010? Hi That wont work since you will need domain-level administrator rights to backup Exchange 2010. Either create a new account with domain-level administrator rights and the role "Administrator" in Exchange, or use your existing Administrator account. Local System doesnt have domain-level administrator rights. Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 [email protected] http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -----"ADSM: Dist Stor Manager" <[email protected]> skrev: ----- Till: [email protected] Från: "Vandeventer, Harold [BS]" Sänt av: "ADSM: Dist Stor Manager" Datum: 03/12/2012 15:35 Ärende: [ADSM-L] TDP 6.3 and Exchange 2010? Is anyone using TDP 6.3 to run VSS backup against Exchange 2010 DAG? We're fighting a problem where a scheduled backup is reported as "successful" from the TSM server perspective, but according to the TDP/Exchange manager the backup never runs. He doesn't see any corresponding backup history in the TDP GUI. Setting the TDP Scheduler service to Log On As a domain account (not "Local System") seems to let scheduled backup work, but the TDP/Exchange manager wants to avoid password change polices by using Local System as he has for years with Exchange 2007. We've got a PMR open, with no progress other than "try a domain account". ------------------------------------------------ Harold Vandeventer
