Re: Q about TSM 6.1 DB and hardware replication
Hi Wanda, On 15 dec 2009, at 18:40, Wanda Prather wrote: > In prior TSM server versions, replicating the TSM DB and log using hardware > replication works fine as long as the DB and log are in a consistency group. > > Any issues with hardware replication of the TSM 6.1 DB and log? With > appropriate changes to dsmserv.opt, will a DR TSM server be able to open the > replicated DB and use it? (Just a little nervous about what all those DB2 > services will think..) > There are some tricks involved in getting db2 to start the database on a server with a different hostname, but in essence this should not be a problem. DB2 is supported on HACMP. I've developed (but not tested yet) a setup for a manual fail-over of TSM 6.1 using LVM mirroring of the database and logs across two sites. A hint is to look at commands like 'db2 catalog' and look into files as 'db2nodes.cfg'. I think that the db2 database is more robust, and less likely to be corrupted after a crash than the old tsm 5 database. > Any insight appreciated! > > W -- Met vriendelijke groeten/Kind regards, Remco Post
Re: Q about TSM 6.1 DB and hardware replication
Grigori, It should not be necessary to stop your TSM database. DB2 can suspend IO with the command set write suspend for db you can then sync your mirrors and issue set write resume for db This will need a DB2 connection rather than a TSM command line, and the suspend and resume should be issued from the same connection. How easy is it to access the DB2 instance directly under 6.1? Regards Steve Steven Harris TSM Admin Finally prospectively employed again after six months! Sydney Australia Grigori Solonovitch wrote: Hello Wanda, We have TSM Server 5.5.4.0 under AIX 5.3. We are mirroring TSM database to disaster site by IBM Metro Mirror (PPRC) for DS8100. I have experienced some problems with online mirroring. It means we faced problems with disaster site activation in case of sending any changes at Head Office (DB, logs and configuration files) to Disaster Site online (nature of PPRC). Finally I came to next procedure: 1) complete all backups for current day; 2) complete all copies for current day; 3) run TSM database backup to tape volume; 4) run backups for volume history and device configuration; 5) stop TSM Server; 6) enable mirroring to Disaster Site; 7) wait till both sites are in sync (usually only a few minutes, because we have two 1Gb/s fiber optics links for mirroring); 8) suspend mirroring; 9) start TSM Server at Head Office and send disaster copy volumes to disaster site. In this case, TSM database, logs and configuration files are in sync and they are in sync with disaster copy of data. I think, for TSM 6.1 you need to use the same procedure or something similar, because DB2 will definitely escalate all problems with online mirroring. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Tuesday, December 15, 2009 8:40 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Q about TSM 6.1 DB and hardware replication In prior TSM server versions, replicating the TSM DB and log using hardware replication works fine as long as the DB and log are in a consistency group. Any issues with hardware replication of the TSM 6.1 DB and log? With appropriate changes to dsmserv.opt, will a DR TSM server be able to open the replicated DB and use it? (Just a little nervous about what all those DB2 services will think..) Any insight appreciated! W Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME." No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.716 / Virus Database: 270.14.109/2567 - Release Date: 12/16/09 06:58:00
Re: Q about TSM 6.1 DB and hardware replication
Hello Steve, I have mentioned in my message my TSM Server Version is 5.5.4.0. So I do not have DB2 at all now in production. I am testing TSM 6.1.2.1 now, but I have not reached disaster recovery testing yet. I hate DB2 administration after managing application called MERVA (similar to SWIFT) in the past. I only hope we will not need to administrate DB2 straight way in TSM 6.1. At least I am running TSM 6.1 in test mode for quite long time (6.1.0 --> 6.1.1 --> 6.1.2.0 -->6.1.2.1) and I never use direct DB2 administration, but I saw some advices in documentation like "Connect to DB2 and do next". Any way, I prefer to shutdown TSM Server before making replication copy. Of course, it is possible in my environment, but it can be impossible in other cases. You advice is useful for non-stop environment. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Steven Harris Sent: Wednesday, December 16, 2009 11:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Q about TSM 6.1 DB and hardware replication Grigori, It should not be necessary to stop your TSM database. DB2 can suspend IO with the command set write suspend for db you can then sync your mirrors and issue set write resume for db This will need a DB2 connection rather than a TSM command line, and the suspend and resume should be issued from the same connection. How easy is it to access the DB2 instance directly under 6.1? Regards Steve Steven Harris TSM Admin Finally prospectively employed again after six months! Sydney Australia Grigori Solonovitch wrote: > Hello Wanda, > > We have TSM Server 5.5.4.0 under AIX 5.3. > > We are mirroring TSM database to disaster site by IBM Metro Mirror (PPRC) for > DS8100. > > I have experienced some problems with online mirroring. It means we faced > problems with disaster site activation in case of sending any changes at Head > Office (DB, logs and configuration files) to Disaster Site online (nature of > PPRC). Finally I came to next procedure: > > 1) complete all backups for current day; > > 2) complete all copies for current day; > > 3) run TSM database backup to tape volume; > > 4) run backups for volume history and device configuration; > > 5) stop TSM Server; > > 6) enable mirroring to Disaster Site; > > 7) wait till both sites are in sync (usually only a few minutes, because we > have two 1Gb/s fiber optics links for mirroring); > > 8) suspend mirroring; > > 9) start TSM Server at Head Office and send disaster copy volumes to disaster > site. > > In this case, TSM database, logs and configuration files are in sync and they > are in sync with disaster copy of data. > > I think, for TSM 6.1 you need to use the same procedure or something similar, > because DB2 will definitely escalate all problems with online mirroring. > > Kindest regards, > > > > Grigori G. Solonovitch > > > > Senior Technical Architect > > > > Information Technology Bank of Kuwait and Middle East http://www.bkme.com > > > > Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: > g.solonovi...@bkme.com > > > > Please consider the environment before printing this Email > > > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Wanda Prather > Sent: Tuesday, December 15, 2009 8:40 PM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Q about TSM 6.1 DB and hardware replication > > > > In prior TSM server versions, replicating the TSM DB and log using hardware > > replication works fine as long as the DB and log are in a consistency group. > > > > Any issues with hardware replication of the TSM 6.1 DB and log? With > > appropriate changes to dsmserv.opt, will a DR TSM server be able to open the > > replicated DB and use it? (Just a little nervous about what all those DB2 > > services will think..) > > > > Any insight appreciated! > > > > W > > > > Please consider the environment before printing this Email. > > > "This email message and any attachments transmitted with it may contain > confidential and proprietary information, intended only for the named > recipient(s). If you have received this message in error, or if you are not > the named recipient(s), please delete this email after notifying the sender > immediately. BKME cannot guarantee the integrity of this communication and > accepts no liability for any damage caused by this email or its attachments > due to viruses, any other defects, interception or unauthorized modification. > The informatio
TSM 5.3.4 Policy problem
Hello All, I meet a problem, If I want to retain deleted data 60days in TSM, what commands should I input to modified policy in TSM? should the "versions data exists" and "versions data deleted" be modified from 2 to 59 , right? These are my configuration: --- tsm: SHITSM01>q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 --- tsm: SHITSM01>q domain f=d Policy Domain Name: DOM_SRV Activated Policy Set: SET_SRV Activation Date/Time: 05/10/2007 11:09:44 Days Since Activation: 951 Activated Default Mgmt Class: MC_90DAYS Number of Registered Nodes: 3 Description: Backup Retention (Grace Period): 60 Archive Retention (Grace Period): 1,095 Last Update by (administrator): ADMIN Last Update Date/Time: 07/30/2009 11:30:05 Managing profile: Changes Pending: Yes Policy Domain Name: STANDARD Activated Policy Set: STANDARD Activation Date/Time: 05/09/2007 12:41:05 Days Since Activation: 952 Activated Default Mgmt Class: STANDARD Number of Registered Nodes: 1 Description: Installed default policy domain. Backup Retention (Grace Period): 30 Archive Retention (Grace Period): 365 Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No --- tsm: SHITSM01>q mgmtclass PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD Yes Installed default management class. STANDARD STANDARD STANDARD Yes Installed default management class. --
Re: TSM 5.3.4 Policy problem
Yes, but it is better to use 60 instead of 59. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3.4 Policy problem Hello All, I meet a problem, If I want to retain deleted data 60days in TSM, what commands should I input to modified policy in TSM? should the "versions data exists" and "versions data deleted" be modified from 2 to 59 , right? These are my configuration: --- tsm: SHITSM01>q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 --- tsm: SHITSM01>q domain f=d Policy Domain Name: DOM_SRV Activated Policy Set: SET_SRV Activation Date/Time: 05/10/2007 11:09:44 Days Since Activation: 951 Activated Default Mgmt Class: MC_90DAYS Number of Registered Nodes: 3 Description: Backup Retention (Grace Period): 60 Archive Retention (Grace Period): 1,095 Last Update by (administrator): ADMIN Last Update Date/Time: 07/30/2009 11:30:05 Managing profile: Changes Pending: Yes Policy Domain Name: STANDARD Activated Policy Set: STANDARD Activation Date/Time: 05/09/2007 12:41:05 Days Since Activation: 952 Activated Default Mgmt Class: STANDARD Number of Registered Nodes: 1 Description: Installed default policy domain. Backup Retention (Grace Period): 30 Archive Retention (Grace Period): 365 Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No --- tsm: SHITSM01>q mgmtclass PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD Yes Installed default management class. STANDARD STANDARD STANDARD Yes Installed default management class. -- Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
Re: TSM 5.3.4 Policy problem
I would take a look at the RETExtra/Only parm of the copy group, they manage the data by date instead of versions. Managing retention time using the versions parameters can give some unintended results (an extra backup of a changed file will reduce the period you can restore from for instance). Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3.4 Policy problem Yes, but it is better to use 60 instead of 59. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3.4 Policy problem Hello All, I meet a problem, If I want to retain deleted data 60days in TSM, what commands should I input to modified policy in TSM? should the "versions data exists" and "versions data deleted" be modified from 2 to 59 , right? These are my configuration: --- tsm: SHITSM01>q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 --- tsm: SHITSM01>q domain f=d Policy Domain Name: DOM_SRV Activated Policy Set: SET_SRV Activation Date/Time: 05/10/2007 11:09:44 Days Since Activation: 951 Activated Default Mgmt Class: MC_90DAYS Number of Registered Nodes: 3 Description: Backup Retention (Grace Period): 60 Archive Retention (Grace Period): 1,095 Last Update by (administrator): ADMIN Last Update Date/Time: 07/30/2009 11:30:05 Managing profile: Changes Pending: Yes Policy Domain Name: STANDARD Activated Policy Set: STANDARD Activation Date/Time: 05/09/2007 12:41:05 Days Since Activation: 952 Activated Default Mgmt Class: STANDARD Number of Registered Nodes: 1 Description: Installed default policy domain. Backup Retention (Grace Period): 30 Archive Retention (Grace Period): 365 Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No --- tsm: SHITSM01>q mgmtclass PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD Yes Installed default management class. STANDARD STANDARD STANDARD Yes Installed default management class. -- Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME." ÿþD i t b e r i c h t i s v e r
TDP for Exchange 2007 scenario
Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. = Unable to obtain the Microsoft Exchange version running on your system. Microsoft Exchange 2003 is being assumed. Unexpected results may occur. = Querying Exchange Server to gather storage group information, please wait... ACN5241E The Microsoft Exchange Information Store is currently not running. C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc /excserv=exfront1 query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN0102E Invalid command: /excserv=exfront1 Is there any methodology to install TDP on this scenario? Any help is appreciated. Mario
Re: TDP for Exchange 2007 scenario
Mario, >>>ACN5241E The Microsoft Exchange Information Store is currently not >>>running.<<< Ensure that the Information Store service is up and running then execute the tdpexcc query exchange and tdpexcc query tsm to check your configuration. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. = Unable to obtain the Microsoft Exchange version running on your system. Microsoft Exchange 2003 is being assumed. Unexpected results may occur. = Querying Exchange Server to gather storage group information, please wait... ACN5241E The Microsoft Exchange Information Store is currently not running. C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc /excserv=exfront1 query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN0102E Invalid command: /excserv=exfront1 Is there any methodology to install TDP on this scenario? Any help is appreciated. Mario IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: TDP for Exchange 2007 scenario
I think you should lok for file tdpexc.cfg or make it from appropriate smp file. From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Mario Behring [mariobehr...@yahoo.com] Sent: Wednesday, December 16, 2009 4:21 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. = Unable to obtain the Microsoft Exchange version running on your system. Microsoft Exchange 2003 is being assumed. Unexpected results may occur. = Querying Exchange Server to gather storage group information, please wait... ACN5241E The Microsoft Exchange Information Store is currently not running. C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc /excserv=exfront1 query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN0102E Invalid command: /excserv=exfront1 Is there any methodology to install TDP on this scenario? Any help is appreciated. Mario Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
Re: TDP for Exchange 2007 scenario
Bertaut, There is no service with this name on Exchange 2007..not that I can find on services.msc anyway. Alsothis error happened when I tried the TDP on the so called FRONTEND machine..and I am not sure where should I install the TDP on this scenario. 1 frontend machine running Windows 2003 Server and Exchange 2007 Server binaries.these are the Exchange services running: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Anti-spam Update Microsoft Exchange EdgeSync Microsoft Exchange File Distribution Microsoft Exchange POP3 Microsoft Exchange Service Host Microsoft Exchange Transport Microsoft Exchange Transport Log Search 2 MSCS nodes running Windows 2003 x64 Server and the following exchange services: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Information Store Microsoft Exchange Mail Submission Microsoft Exchange Mailbox Assistants Microsoft Exchange Replication Service Microsoft Exchange Search Indexer Microsoft Exchange Service Host Microsoft Exchange System Attendant Microsoft Exchange Transport Log Search Microsoft Search (Exchange) Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 11:33:36 AM Subject: Re: TDP for Exchange 2007 scenario Mario, >>>ACN5241E The Microsoft Exchange Information Store is currently not >>>running.<<< Ensure that the Information Store service is up and running then execute the tdpexcc query exchange and tdpexcc query tsm to check your configuration. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. = Unable to obtain the Microsoft Exchange version running on your system. Microsoft Exchange 2003 is being assumed. Unexpected results may occur. = Querying Exchange Server to gather storage group information, please wait... ACN5241E The Microsoft Exchange Information Store is currently not running. C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc /excserv=exfront1 query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN0102E Invalid command: /excserv=exfront1 Is there any methodology to install TDP on this scenario? Any help is appreciated. Mario IMPORTANT: E-mail sent through the Internet is not secure. Legg Mas
Re: TDP for Exchange 2007 scenario
Mario, The specific service pertaining to the ACN5237E TDP error I was referring to is the "Microsoft Exchange Information Store" service. Please ensure that service is up and running then executed the tdpexcc query exchange and tsm commands. I also found this previous ADSM post somewhat related to your issue: http://www.adsm.org/forum/showthread.php?t=10546 I hope it helps. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:59 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2007 scenario Bertaut, There is no service with this name on Exchange 2007..not that I can find on services.msc anyway. Alsothis error happened when I tried the TDP on the so called FRONTEND machine..and I am not sure where should I install the TDP on this scenario. 1 frontend machine running Windows 2003 Server and Exchange 2007 Server binaries.these are the Exchange services running: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Anti-spam Update Microsoft Exchange EdgeSync Microsoft Exchange File Distribution Microsoft Exchange POP3 Microsoft Exchange Service Host Microsoft Exchange Transport Microsoft Exchange Transport Log Search 2 MSCS nodes running Windows 2003 x64 Server and the following exchange services: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Information Store Microsoft Exchange Mail Submission Microsoft Exchange Mailbox Assistants Microsoft Exchange Replication Service Microsoft Exchange Search Indexer Microsoft Exchange Service Host Microsoft Exchange System Attendant Microsoft Exchange Transport Log Search Microsoft Search (Exchange) Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 11:33:36 AM Subject: Re: TDP for Exchange 2007 scenario Mario, >>>ACN5241E The Microsoft Exchange Information Store is currently not >>>running.<<< Ensure that the Information Store service is up and running then execute the tdpexcc query exchange and tdpexcc query tsm to check your configuration. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. = Unable to obtain the Microsoft Exchange version running on your system. Microsoft Exchange 2003 is being assumed. Unexpected results
Re: TDP for Exchange 2007 scenario
Hi Grigori, The tdpexc.cfg file exists and is configured.I don´t think the problem lies in it..this is more like an architectural issue I believe..it´s not clear to me where I should install the TDP agent..considering the 3 machines scenario: 1 front end with the Exchange 2007 Server and 2 cluster nodes where the Exchange DBs reside. Mario From: Grigori Solonovitch To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 11:54:49 AM Subject: Re: TDP for Exchange 2007 scenario I think you should lok for file tdpexc.cfg or make it from appropriate smp file. From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Mario Behring [mariobehr...@yahoo.com] Sent: Wednesday, December 16, 2009 4:21 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. = Unable to obtain the Microsoft Exchange version running on your system. Microsoft Exchange 2003 is being assumed. Unexpected results may occur. = Querying Exchange Server to gather storage group information, please wait... ACN5241E The Microsoft Exchange Information Store is currently not running. C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc /excserv=exfront1 query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN0102E Invalid command: /excserv=exfront1 Is there any methodology to install TDP on this scenario? Any help is appreciated. Mario Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
Re: TDP for Exchange 2007 scenario
Bertaut, I knowthe service exists and is running on both cluster nodes, where the Exchange DBs are..but the service is not even installed on the frontend machine, the one where the actual Exchange Server binaries are... I´ll try to install this service on the frontend machine and see what happens then. Thanks Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 12:14:26 PM Subject: Re: TDP for Exchange 2007 scenario Mario, The specific service pertaining to the ACN5237E TDP error I was referring to is the "Microsoft Exchange Information Store" service. Please ensure that service is up and running then executed the tdpexcc query exchange and tsm commands. I also found this previous ADSM post somewhat related to your issue: http://www.adsm.org/forum/showthread.php?t=10546 I hope it helps. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:59 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2007 scenario Bertaut, There is no service with this name on Exchange 2007..not that I can find on services.msc anyway. Alsothis error happened when I tried the TDP on the so called FRONTEND machine..and I am not sure where should I install the TDP on this scenario. 1 frontend machine running Windows 2003 Server and Exchange 2007 Server binaries.these are the Exchange services running: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Anti-spam Update Microsoft Exchange EdgeSync Microsoft Exchange File Distribution Microsoft Exchange POP3 Microsoft Exchange Service Host Microsoft Exchange Transport Microsoft Exchange Transport Log Search 2 MSCS nodes running Windows 2003 x64 Server and the following exchange services: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Information Store Microsoft Exchange Mail Submission Microsoft Exchange Mailbox Assistants Microsoft Exchange Replication Service Microsoft Exchange Search Indexer Microsoft Exchange Service Host Microsoft Exchange System Attendant Microsoft Exchange Transport Log Search Microsoft Search (Exchange) Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 11:33:36 AM Subject: Re: TDP for Exchange 2007 scenario Mario, >>>ACN5241E The Microsoft Exchange Information Store is currently not >>>running.<<< Ensure that the Information Store service is up and running then execute the tdpexcc query exchange and tdpexcc query tsm to check your configuration. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protectio
Data Protection for Domino
Dear All, could one of you send me a link from where I can download Data Protection for Domino 5.5.2 (for Windows)? Currently I have 5.5.1 installed, but after the Domino server upgrade TSM started filling the log with "domdsmc.exe has terminated abnormally" messages. Perhaps reinstalling 5.5.1 might solve the problem, but 5.5.2 surely supports Domino 8.5.1. Your help would be highly appreciated. With kind regards, Elek Kurucsó
Has anyone done a silent install/configuration of TSM's LVSA?
Folks: We are rolling out an Exchange-based mail system here at Cornell, and in response, a number of units are switching to the Outlook email client - and discovering that they need to implement TSM's Open File Support to backup the local .pst files. As most of the systems on campus are Windows XP systems, enabling Open File Support means installing and configuring the LVSA. We are aware of two means of doing so, using the Setup Wizard or the Edit->Preferences menu item, both of which require human interaction with the system. Given the number of systems involved (>1000) and the fact that a considerable number of these systems are scattered around the country (and world), the tech support folks in these units are desperately seeking a silent install process they could push to all these systems. Thanks in advance for any help! -- Robert (Bob) Talda EZ-Backup Team Cornell University 714 Rhodes Hall Ithaca, NY 14853 (607) 255-8280 ezbac...@cornell.edu
Lib Manager question
I have a library manager that is sharing a 8 drives in a 3584 library to two tsm instances. All are TSM 5.5.3.0. If I update the path between a drive and one of the instances offline, will the lib manager then not use that drive when allocating drives to that instance? Or will it allocate the drive and then generate a failure because the instance can't access it? What I am trying to do, for troubleshooting purposes, is to make a drive available to one of the instances but not the other. David
Re: TSM 5.x DB and hardware replication
Wanda, In TSM v5, do you find hardware replication to work better than TSM mirroring for replicating the TSM DB and log to a DR site? David >>> Wanda Prather 12/15/2009 12:40 PM >>> In prior TSM server versions, replicating the TSM DB and log using hardware replication works fine as long as the DB and log are in a consistency group. Any issues with hardware replication of the TSM 6.1 DB and log? With appropriate changes to dsmserv.opt, will a DR TSM server be able to open the replicated DB and use it? (Just a little nervous about what all those DB2 services will think..) Any insight appreciated! W
Re: TSM 5.x DB and hardware replication
In cases where I had local fibre, I'd certainly be happy to set up TSM mirroring. But: AFAIK you can't do that with TSM 6.1. It will mirror logs, but not the DB. And this customer is doing very long distance (hundreds of miles) mirroring over PPRC (or the EMC equivalent), which has to be asynchronous. In order for TSM to do the mirroring, you need the drive/filesystem to appear to be a local device to the TSM server. I don't have that option right now, all I've got to play with is the hardware function. W On Wed, Dec 16, 2009 at 11:11 AM, David E Ehresman wrote: > Wanda, > > In TSM v5, do you find hardware replication to work better than TSM > mirroring for replicating the TSM DB and log to a DR site? > > David > > >>> Wanda Prather 12/15/2009 12:40 PM >>> > In prior TSM server versions, replicating the TSM DB and log using hardware > replication works fine as long as the DB and log are in a consistency > group. > > Any issues with hardware replication of the TSM 6.1 DB and log? With > appropriate changes to dsmserv.opt, will a DR TSM server be able to open > the > replicated DB and use it? (Just a little nervous about what all those DB2 > services will think..) > > Any insight appreciated! > > W >
Re: TDP for Exchange 2007 scenario
Bertaut, Consider the TDP Exch installed on the MSCS nodes tdpexcc query tsm is working fine..it connects to the TSM Server. .tdpexcc query exchange keeps showing me the error message below: ACN5237E Unable to communicate with the Microsoft Exchange Server Any ideas? Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 12:14:26 PM Subject: Re: TDP for Exchange 2007 scenario Mario, The specific service pertaining to the ACN5237E TDP error I was referring to is the "Microsoft Exchange Information Store" service. Please ensure that service is up and running then executed the tdpexcc query exchange and tsm commands. I also found this previous ADSM post somewhat related to your issue: http://www.adsm.org/forum/showthread.php?t=10546 I hope it helps. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:59 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2007 scenario Bertaut, There is no service with this name on Exchange 2007..not that I can find on services.msc anyway. Alsothis error happened when I tried the TDP on the so called FRONTEND machine..and I am not sure where should I install the TDP on this scenario. 1 frontend machine running Windows 2003 Server and Exchange 2007 Server binaries.these are the Exchange services running: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Anti-spam Update Microsoft Exchange EdgeSync Microsoft Exchange File Distribution Microsoft Exchange POP3 Microsoft Exchange Service Host Microsoft Exchange Transport Microsoft Exchange Transport Log Search 2 MSCS nodes running Windows 2003 x64 Server and the following exchange services: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Information Store Microsoft Exchange Mail Submission Microsoft Exchange Mailbox Assistants Microsoft Exchange Replication Service Microsoft Exchange Search Indexer Microsoft Exchange Service Host Microsoft Exchange System Attendant Microsoft Exchange Transport Log Search Microsoft Search (Exchange) Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 11:33:36 AM Subject: Re: TDP for Exchange 2007 scenario Mario, >>>ACN5241E The Microsoft Exchange Information Store is currently not >>>running.<<< Ensure that the Information Store service is up and running then execute the tdpexcc query exchange and tdpexcc query tsm to check your configuration. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS environments before, with Exchange 2003and everything was fine. This 2007 scenario is different thoughit uses a 3rd machine, like a frontend.only the Exchange Databases are on the cluster nodes I´ve tried installing the TDP on the frontend machine also, which is a standalone machine and it is where the Exchange Server binaries are installedand I got the following error: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Versi
Re: Lib Manager question
>> On Wed, 16 Dec 2009 10:51:53 -0500, David E Ehresman >> said: > I have a library manager that is sharing a 8 drives in a 3584 > library to two tsm instances. All are TSM 5.5.3.0. > If I update the path between a drive and one of the instances > offline, will the lib manager then not use that drive when > allocating drives to that instance? Exactly. > What I am trying to do, for troubleshooting purposes, is to make a > drive available to one of the instances but not the other. yep. - Allen S. Rout
Re: TDP for Exchange 2007 scenario
Sorry to hear that Mario; I provided the link below in my previous post as it was related to your issue (http://www.adsm.org/forum/showthread.php?t=10546); placing the clustername in the excserv switch took care of that particular problem in the posting. The ACN5237E error code is pretty straightforward, verifying that the Microsoft Exchange Information Store service and exchange server run and that the appropriate name is being used in the excserv switch should be enough. Besides those steps, there is nothing else I can think of at the moment. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 12:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2007 scenario Bertaut, Consider the TDP Exch installed on the MSCS nodes tdpexcc query tsm is working fine..it connects to the TSM Server. .tdpexcc query exchange keeps showing me the error message below: ACN5237E Unable to communicate with the Microsoft Exchange Server Any ideas? Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 12:14:26 PM Subject: Re: TDP for Exchange 2007 scenario Mario, The specific service pertaining to the ACN5237E TDP error I was referring to is the "Microsoft Exchange Information Store" service. Please ensure that service is up and running then executed the tdpexcc query exchange and tsm commands. I also found this previous ADSM post somewhat related to your issue: http://www.adsm.org/forum/showthread.php?t=10546 I hope it helps. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:59 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2007 scenario Bertaut, There is no service with this name on Exchange 2007..not that I can find on services.msc anyway. Alsothis error happened when I tried the TDP on the so called FRONTEND machine..and I am not sure where should I install the TDP on this scenario. 1 frontend machine running Windows 2003 Server and Exchange 2007 Server binaries.these are the Exchange services running: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Anti-spam Update Microsoft Exchange EdgeSync Microsoft Exchange File Distribution Microsoft Exchange POP3 Microsoft Exchange Service Host Microsoft Exchange Transport Microsoft Exchange Transport Log Search 2 MSCS nodes running Windows 2003 x64 Server and the following exchange services: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Information Store Microsoft Exchange Mail Submission Microsoft Exchange Mailbox Assistants Microsoft Exchange Replication Service Microsoft Exchange Search Indexer Microsoft Exchange Service Host Microsoft Exchange System Attendant Microsoft Exchange Transport Log Search Microsoft Search (Exchange) Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 11:33:36 AM Subject: Re: TDP for Exchange 2007 scenario Mario, >>>ACN5241E The Microsoft Exchange Information Store is currently not >>>running.<<< Ensure that the Information Store service is up and running then execute the tdpexcc query exchange and tdpexcc query tsm to check your configuration. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Serve
Netware restore problem/question
Netware 6.0 server running TSM client 5.2.5. The user is using the web client to restore some files in a directory. That directory is not shown/listed. Even using the show active/inactive option. Looking in the dsmsched.log file, I can see that files are actively being backed up from that directory as current as of last night. I think my question is.will the TSM web client only display directories/files that the current user can restore based on permission? And is the web client using the saved (NWPFILE) information? TIA, Bill Boyer
TDP SQL connection error
Hi list, I´ve installed TDP for SQL 5.5.1 on a Windows 2008 Server with Microsoft SQL Server 2008. I am getting the error below when trying to connect the TDP for SQL agent using thetdpsqlc query SQL command: C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query SQL IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server Version 5, Release 5, Level 0.0 (C) Copyright IBM Corporation 1997, 2007. All rights reserved. Connecting to SQL Server, please wait... ACO5422E Received the following from the MS SQL server: Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, Public KeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. The tdpsqlc query tsm command connnects to the TSM Server without errors. I´ve already searched the Microsoft website and instaleld the Microsoft SQL Server 2008 Management Objects package.but the error remains. Mario
Re: TDP SQL connection error
Hi Mario, It looks like you are running DP for SQL 5.5.0 MS SQL server 2008 is supported in DP for SQL 5.5.2 - http://www-01.ibm.com/support/docview.wss?rs=667&uid=swg21321370 Regards, Mark From: Mario Behring To: ADSM-L@VM.MARIST.EDU Date: 12/16/2009 11:24 AM Subject:[ADSM-L] TDP SQL connection error Hi list, I´ve installed TDP for SQL 5.5.1 on a Windows 2008 Server with Microsoft SQL Server 2008. I am getting the error below when trying to connect the TDP for SQL agent using thetdpsqlc query SQL command: C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query SQL IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server: Version 5, Release 5, Level 0.0 (C) Copyright IBM Corporation 1997, 2007. All rights reserved. Connecting to SQL Server, please wait ACO5422E Received the following from the MS SQL server: Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, Public KeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. The tdpsqlc query tsm command connnects to the TSM Server without errors. I´ve already searched the Microsoft website and instaleld the Microsoft SQL Server 2008 Management Objects package.but the error remains. Mario
collocation increases tape mounts while backup
Depending on how you set up your collocation (File Systems, Server or Server Group). If you chose collocation by file system then you would mount a tape for each file sys, if you set by server then a mount per server etc ... Hope that helps. +-- |This was sent by charles_h...@uhc.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TDP for Exchange 2007 scenario
Mario, Did you happen to look at the section in the book where it discusses running in an MSCS cluster setup? Whenever you are communicating with a clustered (SCC) Exchange server, you must use the "/EXCSERVER=virtual-server-name" option on the TDPEXC and TDPEXCC commands. I assume from your description that you are running Exchange SCC clustering and not CCR clustering? Exchange CCR clustering is a bit different because there is no shared storage. There are two copies of the Exchange database, one is an active one and the other one is a passive (replica). It does use Microsoft clustering underneath, but not the traditional MSCS-SCC clustering. Either way... You only need to install and run Data Protection for Exchange on the machines that contain your mailbox databases and your public folder databases. Once it is installed using the installation program and configured (you cannot simply copy the binaries to the machine because the installation program makes required registry updates necessary for runtime operations) you then would launch a CLI command as follows: TDPEXCC QUERY EXCHANGE /EXCSERVER=virtual-server-name or via the GUI TDPEXC /EXCSERVER=virtual-server-name where "virtual-server-name" is the name of the Exchange virtual server. If you cannot get things to work, please call IBM support. Thanks, Del "ADSM: Dist Stor Manager" wrote on 12/16/2009 08:21:59 AM: > [image removed] > > TDP for Exchange 2007 scenario > > Mario Behring > > to: > > ADSM-L > > 12/16/2009 08:23 AM > > Sent by: > > "ADSM: Dist Stor Manager" > > Please respond to "ADSM: Dist Stor Manager" > > Hi list, > > I have the following scenario and I am having a hard time making TDP > for Exchange work > > > 1- Microsoft Exchange 2007 binaries installed in one machine, as > afront end machine. > 2- Microsoft Exchange 2007 Database Agents installed on 2 other > machines running MCSC (Microsoft Cluster Server). > 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. > > > I´ve installed TDP for Exch on both nodes and I am getting the error > below when verifying my installation: > > > C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange > > IBM Tivoli Storage Manager for Mail: > Data Protection for Microsoft Exchange Server > Version 5, Release 5, Level 1.0 > (C) Copyright IBM Corporation 1998, 2008. All rights reserved. > > ACN5051I The configuration file cannot be found, using default settings. > > ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log > file has been pruned successfully. > > Querying Exchange Server to gather storage group information, please wait... > > ACN5237E Unable to communicate with the Microsoft Exchange Server. > > > > On the dsm.opt file, the NODENAME parameter is pointing to the > virtual server name on the MSCS, as recommended by the TDP for > Exchange Installation Guide... > > I did TDP for Exchange installations in MSCS environments before, > with Exchange 2003and everything was fine. This 2007 scenario is > different thoughit uses a 3rd machine, like a frontend.only > the Exchange Databases are on the cluster nodes > > > > > I´ve tried installing the TDP on the frontend machine also, which is > a standalone machine and it is where the Exchange Server binaries > are installedand I got the following error: > > > C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange > > IBM Tivoli Storage Manager for Mail: > Data Protection for Microsoft Exchange Server > Version 5, Release 5, Level 1.0 > (C) Copyright IBM Corporation 1998, 2008. All rights reserved. > > ACN5051I The configuration file cannot be found, using default settings. > > ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log > file has been pruned successfully. > > = > Unable to obtain the Microsoft Exchange version running on your system. > Microsoft Exchange 2003 is being assumed. Unexpected results may occur. > = > > Querying Exchange Server to gather storage group information, please wait... > > ACN5241E The Microsoft Exchange Information Store is currently not running. > > > C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc /excserv=exfront1 > query exchange > > IBM Tivoli Storage Manager for Mail: > Data Protection for Microsoft Exchange Server > Version 5, Release 5, Level 1.0 > (C) Copyright IBM Corporation 1998, 2008. All rights reserved. > > ACN0102E Invalid command: /excserv=exfront1 > > > > > Is there any methodology to install TDP on this scenario? > > Any help is appreciated. > > Mario > > > >
Re: Data Protection for Domino
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/tivoli-data-protection/domino/Windows/x32/v552/ ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/tivoli-data-protection/domino/Windows/x64/v552/ "ADSM: Dist Stor Manager" wrote on 12/16/2009 09:25:00 AM: > [image removed] > > Data Protection for Domino > > Elek Kurucsó > > to: > > ADSM-L > > 12/16/2009 09:26 AM > > Sent by: > > "ADSM: Dist Stor Manager" > > Please respond to "ADSM: Dist Stor Manager" > > Dear All, > > could one of you send me a link from where I can download Data Protection > for Domino 5.5.2 (for Windows)? > > Currently I have 5.5.1 installed, but after the Domino server upgrade TSM > started filling the log with "domdsmc.exe has terminated abnormally" > messages. > > Perhaps reinstalling 5.5.1 might solve the problem, but 5.5.2 surely > supports Domino 8.5.1. > > > Your help would be highly appreciated. > > > With kind regards, > Elek Kurucsó
Re: TDP SQL connection error
Mario, I would recommend getting the latest version which is Data Protection for SQL 5.5.3. You can find it here: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntsql/v553/ This web page: http://www-01.ibm.com/support/docview.wss?&uid=swg21403340 shows these prereqs: * Microsoft .NET Framework version 2.0 (or later) * Microsoft Core XML Services (MSXML) 6.0 (or later) * Microsoft SQL Server 2008 Native Client * Microsoft SQL Server 2008 Management Objects * Microsoft SQL Server System CLR Types Thanks, Del "ADSM: Dist Stor Manager" wrote on 12/16/2009 02:22:29 PM: > [image removed] > > TDP SQL connection error > > Mario Behring > > to: > > ADSM-L > > 12/16/2009 02:23 PM > > Sent by: > > "ADSM: Dist Stor Manager" > > Please respond to "ADSM: Dist Stor Manager" > > Hi list, > > I´ve installed TDP for SQL 5.5.1 on a Windows 2008 Server with > Microsoft SQL Server 2008. I am getting the error below when trying > to connect the TDP for SQL agent using thetdpsqlc query SQL command: > > > C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query SQL > > IBM Tivoli Storage Manager for Databases: > Data Protection for Microsoft SQL Server > Version 5, Release 5, Level 0.0 > (C) Copyright IBM Corporation 1997, 2007. All rights reserved. > > Connecting to SQL Server, please wait... > > ACO5422E Received the following from the MS SQL server: > Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9. > 0.242.0, Culture=neutral, Public > KeyToken=89845dcd8080cc91' or one of its dependencies. The system > cannot find the file specified. > > > The tdpsqlc query tsm command connnects to the TSM Server without errors. > > I´ve already searched the Microsoft website and instaleld the > Microsoft SQL Server 2008 Management Objects package.but the > error remains. > > Mario > > > >
Re: TDP SQL connection error
This error usually comes when there is an issue with pre-reqs install. Did you try repair on TDP? Thanks, Sanju -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Thursday, December 17, 2009 12:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP SQL connection error Hi list, I´ve installed TDP for SQL 5.5.1 on a Windows 2008 Server with Microsoft SQL Server 2008. I am getting the error below when trying to connect the TDP for SQL agent using thetdpsqlc query SQL command: C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc query SQL IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server Version 5, Release 5, Level 0.0 (C) Copyright IBM Corporation 1997, 2007. All rights reserved. Connecting to SQL Server, please wait... ACO5422E Received the following from the MS SQL server: Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, Public KeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. The tdpsqlc query tsm command connnects to the TSM Server without errors. I´ve already searched the Microsoft website and instaleld the Microsoft SQL Server 2008 Management Objects package.but the error remains. Mario
Re: TSM 5.3.4 Policy problem
Hello, Thanks Grigori,Karel, I want to retain deleted data 60days in TSM. So should I input: Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 verdeleted=60 retextra=60 retonly=60 But got error, said, active policy cannot be modified, So could anyone can tell me how can I modified my policy set and copygroup so that I can get what I want? Many thanks! William -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bos, Karel Sent: Wednesday, December 16, 2009 6:27 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem I would take a look at the RETExtra/Only parm of the copy group, they manage the data by date instead of versions. Managing retention time using the versions parameters can give some unintended results (an extra backup of a changed file will reduce the period you can restore from for instance). Kind regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: woensdag 16 december 2009 10:31 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3.4 Policy problem Yes, but it is better to use 60 instead of 59. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Wednesday, December 16, 2009 12:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.3.4 Policy problem Hello All, I meet a problem, If I want to retain deleted data 60days in TSM, what commands should I input to modified policy in TSM? should the "versions data exists" and "versions data deleted" be modified from 2 to 59 , right? These are my configuration: --- tsm: SHITSM01>q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD90 90 90 90 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 --- tsm: SHITSM01>q domain f=d Policy Domain Name: DOM_SRV Activated Policy Set: SET_SRV Activation Date/Time: 05/10/2007 11:09:44 Days Since Activation: 951 Activated Default Mgmt Class: MC_90DAYS Number of Registered Nodes: 3 Description: Backup Retention (Grace Period): 60 Archive Retention (Grace Period): 1,095 Last Update by (administrator): ADMIN Last Update Date/Time: 07/30/2009 11:30:05 Managing profile: Changes Pending: Yes Policy Domain Name: STANDARD Activated Policy Set: STANDARD Activation Date/Time: 05/09/2007 12:41:05 Days Since Activation: 952 Activated Default Mgmt Class: STANDARD Number of Registered Nodes: 1 Description: Installed default policy domain. Backup Retention (Grace Period): 30 Archive Retention (Grace Period): 365 Last Update by (administrator): SERVER_CONSOLE Last Update Date/Time: 05/09/2007 12:41:05 Managing profile: Changes Pending: No --- tsm: SHITSM01>q mgmtclass PolicyPolicyMgmt Default Description DomainSet Name Class Mgmt NameName Class ? - - - - DOM_SRV ACTIVEMC_90DAYS Yes DOM_SRV SET_SRV MC_90DAYS Yes STANDARD ACTIVESTANDARD Yes Installed default management class. STANDARD STANDARD STANDARD Yes Installed default management class. -- Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confid
Re: TSM 5.3.4 Policy problem
You actually want to modify the copy group from your inactive policy set. In most cases this should be STANDARD rather than ACTIVE. You then swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. William ZHANG wrote: > Hello, > > Thanks Grigori,Karel, > I want to retain deleted data 60days in TSM. > So should I input: > > Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 > verdeleted=60 retextra=60 retonly=60 > > But got error, said, active policy cannot be modified, > So could anyone can tell me how can I modified my policy set and copygroup > so that I can get what I want? > > > Many thanks! > > William > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Bos, Karel > Sent: Wednesday, December 16, 2009 6:27 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem > > I would take a look at the RETExtra/Only parm of the copy group, they manage > the data by date instead of versions. Managing retention time using the > versions parameters can give some unintended results (an extra backup of a > changed file will reduce the period you can restore from for instance). > > Kind regards, > > Karel > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Grigori Solonovitch > Sent: woensdag 16 december 2009 10:31 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM 5.3.4 Policy problem > > Yes, but it is better to use 60 instead of 59. > > Grigori G. Solonovitch > > Senior Technical Architect > > Information Technology Bank of Kuwait and Middle East http://www.bkme.com > > Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: > g.solonovi...@bkme.com > > Please consider the environment before printing this Email > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > William ZHANG > Sent: Wednesday, December 16, 2009 12:28 PM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] TSM 5.3.4 Policy problem > > Hello All, > > > > I meet a problem, > > If I want to retain deleted data 60days in TSM, what commands should I input > to modified policy in TSM? > > > > should the "versions data exists" and "versions data deleted" be modified > from 2 to 59 , right? > > > > These are my configuration: > > --- > > tsm: SHITSM01>q copygroup > > > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > > DomainSet Name Class Group Data > DataExtraOnly > > NameName NameExists > Deleted Versions Version > > - - - - > --- > > DOM_SRV ACTIVEMC_90DAYS STANDARD 2 > 1 90 90 > > DOM_SRV SET_SRV MC_90DAYS STANDARD90 > 90 90 90 > > STANDARD ACTIVESTANDARD STANDARD 2 > 1 30 60 > > STANDARD STANDARD STANDARD STANDARD 2 > 1 30 60 > > --- > > tsm: SHITSM01>q domain f=d > > > > Policy Domain Name: DOM_SRV > > Activated Policy Set: SET_SRV > > Activation Date/Time: 05/10/2007 11:09:44 > >Days Since Activation: 951 > > Activated Default Mgmt Class: MC_90DAYS > > Number of Registered Nodes: 3 > > Description: > > Backup Retention (Grace Period): 60 > > Archive Retention (Grace Period): 1,095 > > Last Update by (administrator): ADMIN > >Last Update Date/Time: 07/30/2009 11:30:05 > > Managing profile: > > Changes Pending: Yes > > > > Policy Domain Name: STANDARD > > Activated Policy Set: STANDARD > > Activation Date/Time: 05/09/2007 12:41:05 > >Days Since Activation: 952 > > Activated Default Mgmt Class: STANDARD > > Number of Registered Nodes: 1 > > Description: Installed default policy domain. > > Backup Retention (Grace Period): 30 > > Archive Retention (Grace Period): 365 > > Last Update by (administrator): SERVER_CONSOLE > >Last Update Date/Time: 05/09/2007 12:41:05 > > Managing profile: > > Changes Pending: No > > > > --- > > tsm: SHITSM01>q mgmtclass > > > > PolicyPolicyMgmt Default Description > > DomainSet Name Class Mgmt > > NameName Class ? > > - - - - > > > DOM_SRV ACTIVEMC_90DAYS Yes > > DOM_SRV SET_SRV
TSM Client Schedules failing...
Hi, I am using TSM Server and client V5.5.0.0. My schedules are getting failed with the following error. ANS4008E Error processing '/vol01': file is temporarily unavailable I am backing up file server with GPFS file system on RHEL. I checked the error code and made changes as suggested. But did not worked .Please suggest. Regards, Kiran. Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address
Re: TSM 5.3.4 Policy problem
Hello Skylar, Do you mean, > update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 > active policyset DOM_SRV SET_SRV Then, > update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 verdeleted=60 retextra=60 retonly=60 > active policyset DOM_SRV ACTIVE Right? tsm: SHITSM01>q copygroup PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DOM_SRV ACTIVEMC_90DAYS STANDARD 2 1 90 90 DOM_SRV SET_SRV MC_90DAYS STANDARD 2 1 60 60 STANDARD ACTIVESTANDARD STANDARD 2 1 30 60 STANDARD STANDARD STANDARD STANDARD 2 1 30 60 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Skylar Thompson Sent: Thursday, December 17, 2009 12:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem You actually want to modify the copy group from your inactive policy set. In most cases this should be STANDARD rather than ACTIVE. You then swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. William ZHANG wrote: > Hello, > > Thanks Grigori,Karel, > I want to retain deleted data 60days in TSM. > So should I input: > > Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 > verdeleted=60 retextra=60 retonly=60 > > But got error, said, active policy cannot be modified, > So could anyone can tell me how can I modified my policy set and copygroup > so that I can get what I want? > > > Many thanks! > > William > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Bos, Karel > Sent: Wednesday, December 16, 2009 6:27 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem > > I would take a look at the RETExtra/Only parm of the copy group, they manage > the data by date instead of versions. Managing retention time using the > versions parameters can give some unintended results (an extra backup of a > changed file will reduce the period you can restore from for instance). > > Kind regards, > > Karel > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Grigori Solonovitch > Sent: woensdag 16 december 2009 10:31 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: TSM 5.3.4 Policy problem > > Yes, but it is better to use 60 instead of 59. > > Grigori G. Solonovitch > > Senior Technical Architect > > Information Technology Bank of Kuwait and Middle East http://www.bkme.com > > Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: > g.solonovi...@bkme.com > > Please consider the environment before printing this Email > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > William ZHANG > Sent: Wednesday, December 16, 2009 12:28 PM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] TSM 5.3.4 Policy problem > > Hello All, > > > > I meet a problem, > > If I want to retain deleted data 60days in TSM, what commands should I input > to modified policy in TSM? > > > > should the "versions data exists" and "versions data deleted" be modified > from 2 to 59 , right? > > > > These are my configuration: > > --- > > tsm: SHITSM01>q copygroup > > > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > > DomainSet Name Class Group Data > DataExtraOnly > > NameName NameExists > Deleted Versions Version > > - - - - > --- > > DOM_SRV ACTIVEMC_90DAYS STANDARD 2 > 1 90 90 > > DOM_SRV SET_SRV MC_90DAYS STANDARD90 > 90 90 90 > > STANDARD ACTIVESTANDARD STANDARD 2 > 1 30 60 > > STANDARD STANDARD STANDARD STANDARD 2 > 1 30 60 > > --- > > tsm: SHITSM01>q domain f=d > > > > Policy Domain Name: DOM_SRV > > Activated Policy Set: SET_SRV > > Activation Date/Time: 05/10/2007 11:09:44 > >Days Since Activation: 951 > > Activated Default Mgmt Class: MC_90DAYS > > Number of Registered Nodes: 3 > > Description:
Re: TSM 5.3.4 Policy problem
Yeah, I typo'd the activate statement. It should be: ACTIVATE POLICYSET DOM_SRC STANDARD This will actually rename STANDARD to ACTIVE, and ACTIVE to STANDARD. William ZHANG wrote: > Hello Skylar, > > Do you mean, > >> update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists=60 >> > verdeleted=60 retextra=60 retonly=60 > >> active policyset DOM_SRV SET_SRV >> > Then, > >> update copygroup DOM_SRV ACTIVE MC_90DAYS STANDARD verexists=60 >> > verdeleted=60 retextra=60 retonly=60 > >> active policyset DOM_SRV ACTIVE >> > > Right? > > tsm: SHITSM01>q copygroup > > PolicyPolicyMgmt Copy Versions > Versions Retain Retain > DomainSet Name Class Group Data > DataExtraOnly > NameName NameExists > Deleted Versions Version > - - - - > --- > DOM_SRV ACTIVEMC_90DAYS STANDARD 2 > 1 90 90 > DOM_SRV SET_SRV MC_90DAYS STANDARD 2 > 1 60 60 > STANDARD ACTIVESTANDARD STANDARD 2 > 1 30 60 > STANDARD STANDARD STANDARD STANDARD 2 > 1 30 60 > > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of > Skylar Thompson > Sent: Thursday, December 17, 2009 12:44 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem > > You actually want to modify the copy group from your inactive policy > set. In most cases this should be STANDARD rather than ACTIVE. You then > swap STANDARD and ACTIVE with ACTIVATE POLICYSET DOM_SRV ACTIVE. > > William ZHANG wrote: > >> Hello, >> >> Thanks Grigori,Karel, >> I want to retain deleted data 60days in TSM. >> So should I input: >> >> Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60 >> verdeleted=60 retextra=60 retonly=60 >> >> But got error, said, active policy cannot be modified, >> So could anyone can tell me how can I modified my policy set and copygroup >> so that I can get what I want? >> >> >> Many thanks! >> >> William >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> Bos, Karel >> Sent: Wednesday, December 16, 2009 6:27 PM >> To: ADSM-L@VM.MARIST.EDU >> Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem >> >> I would take a look at the RETExtra/Only parm of the copy group, they >> > manage > >> the data by date instead of versions. Managing retention time using the >> versions parameters can give some unintended results (an extra backup of a >> changed file will reduce the period you can restore from for instance). >> >> Kind regards, >> >> Karel >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> Grigori Solonovitch >> Sent: woensdag 16 december 2009 10:31 >> To: ADSM-L@VM.MARIST.EDU >> Subject: Re: TSM 5.3.4 Policy problem >> >> Yes, but it is better to use 60 instead of 59. >> >> Grigori G. Solonovitch >> >> Senior Technical Architect >> >> Information Technology Bank of Kuwait and Middle East http://www.bkme.com >> >> Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: >> g.solonovi...@bkme.com >> >> Please consider the environment before printing this Email >> >> >> -Original Message- >> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of >> William ZHANG >> Sent: Wednesday, December 16, 2009 12:28 PM >> To: ADSM-L@VM.MARIST.EDU >> Subject: [ADSM-L] TSM 5.3.4 Policy problem >> >> Hello All, >> >> >> >> I meet a problem, >> >> If I want to retain deleted data 60days in TSM, what commands should I >> > input > >> to modified policy in TSM? >> >> >> >> should the "versions data exists" and "versions data deleted" be modified >> from 2 to 59 , right? >> >> >> >> These are my configuration: >> >> --- >> >> tsm: SHITSM01>q copygroup >> >> >> >> PolicyPolicyMgmt Copy Versions >> Versions Retain Retain >> >> DomainSet Name Class Group Data >> DataExtraOnly >> >> NameName NameExists >> Deleted Versions Version >> >> - - - - >> --- >> >> DOM_SRV ACTIVEMC_90DAYS STANDARD 2 >> 1 90 90 >> >> DOM_SRV SET_SRV MC_90DAYS STANDARD90 >> 90 90 90 >> >> STANDARD ACTIVESTANDARD STANDARD 2 >> 1 30 60 >> >> STANDARD STANDARD STANDARD STANDARD 2 >> 1 30 60 >> >>
Re: Data Protection for Domino
Try: http://ftp.software.ibm.com/storage/tivoli-storage-management/ Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Elek Kurucso Sent: Wednesday, December 16, 2009 5:25 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Data Protection for Domino Dear All, could one of you send me a link from where I can download Data Protection for Domino 5.5.2 (for Windows)? Currently I have 5.5.1 installed, but after the Domino server upgrade TSM started filling the log with "domdsmc.exe has terminated abnormally" messages. Perhaps reinstalling 5.5.1 might solve the problem, but 5.5.2 surely supports Domino 8.5.1. Your help would be highly appreciated. With kind regards, Elek Kurucsó Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
Re: TSM 5.x DB and hardware replication
I think a combination of Metro Mirror and Remote Copy can do the work. It means, you can mirror TSM database to the shorter distance by Metro Mirror and use long distance Remote Copy at appropriate time. It is a little bit complicated, but it should work properly. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Wednesday, December 16, 2009 7:34 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.x DB and hardware replication In cases where I had local fibre, I'd certainly be happy to set up TSM mirroring. But: AFAIK you can't do that with TSM 6.1. It will mirror logs, but not the DB. And this customer is doing very long distance (hundreds of miles) mirroring over PPRC (or the EMC equivalent), which has to be asynchronous. In order for TSM to do the mirroring, you need the drive/filesystem to appear to be a local device to the TSM server. I don't have that option right now, all I've got to play with is the hardware function. W On Wed, Dec 16, 2009 at 11:11 AM, David E Ehresman wrote: > Wanda, > > In TSM v5, do you find hardware replication to work better than TSM > mirroring for replicating the TSM DB and log to a DR site? > > David > > >>> Wanda Prather 12/15/2009 12:40 PM >>> > In prior TSM server versions, replicating the TSM DB and log using hardware > replication works fine as long as the DB and log are in a consistency > group. > > Any issues with hardware replication of the TSM 6.1 DB and log? With > appropriate changes to dsmserv.opt, will a DR TSM server be able to open > the > replicated DB and use it? (Just a little nervous about what all those DB2 > services will think..) > > Any insight appreciated! > > W > Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME."
Re: TDP for Exchange 2007 scenario
Could you check next link? http://www.adsm.org/forum/showthread.php?p=70917 Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2007 scenario Bertaut, Consider the TDP Exch installed on the MSCS nodes tdpexcc query tsm is working fine..it connects to the TSM Server. .tdpexcc query exchange keeps showing me the error message below: ACN5237E Unable to communicate with the Microsoft Exchange Server Any ideas? Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 12:14:26 PM Subject: Re: TDP for Exchange 2007 scenario Mario, The specific service pertaining to the ACN5237E TDP error I was referring to is the "Microsoft Exchange Information Store" service. Please ensure that service is up and running then executed the tdpexcc query exchange and tsm commands. I also found this previous ADSM post somewhat related to your issue: http://www.adsm.org/forum/showthread.php?t=10546 I hope it helps. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:59 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2007 scenario Bertaut, There is no service with this name on Exchange 2007..not that I can find on services.msc anyway. Alsothis error happened when I tried the TDP on the so called FRONTEND machine..and I am not sure where should I install the TDP on this scenario. 1 frontend machine running Windows 2003 Server and Exchange 2007 Server binaries.these are the Exchange services running: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Anti-spam Update Microsoft Exchange EdgeSync Microsoft Exchange File Distribution Microsoft Exchange POP3 Microsoft Exchange Service Host Microsoft Exchange Transport Microsoft Exchange Transport Log Search 2 MSCS nodes running Windows 2003 x64 Server and the following exchange services: Microsoft Exchange Active Directory Topology Service Microsoft Exchange Information Store Microsoft Exchange Mail Submission Microsoft Exchange Mailbox Assistants Microsoft Exchange Replication Service Microsoft Exchange Search Indexer Microsoft Exchange Service Host Microsoft Exchange System Attendant Microsoft Exchange Transport Log Search Microsoft Search (Exchange) Mario From: "Tchuise, Bertaut" To: ADSM-L@VM.MARIST.EDU Sent: Wed, December 16, 2009 11:33:36 AM Subject: Re: TDP for Exchange 2007 scenario Mario, >>>ACN5241E The Microsoft Exchange Information Store is currently not >>>running.<<< Ensure that the Information Store service is up and running then execute the tdpexcc query exchange and tdpexcc query tsm to check your configuration. BERTAUT TCHUISE TSM/NetApp Storage Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Wednesday, December 16, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP for Exchange 2007 scenario Hi list, I have the following scenario and I am having a hard time making TDP for Exchange work 1- Microsoft Exchange 2007 binaries installed in one machine, as afront end machine. 2- Microsoft Exchange 2007 Database Agents installed on 2 other machines running MCSC (Microsoft Cluster Server). 3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes. I´ve installed TDP for Exch on both nodes and I am getting the error below when verifying my installation: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Version 5, Release 5, Level 1.0 (C) Copyright IBM Corporation 1998, 2008. All rights reserved. ACN5051I The configuration file cannot be found, using default settings. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Querying Exchange Server to gather storage group information, please wait... ACN5237E Unable to communicate with the Microsoft Exchange Server. On the dsm.opt file, the NODENAME parameter is pointing to the virtual server name on the MSCS, as recommended by the TDP for Exchange Installation Guide... I did TDP for Exchange installations in MSCS en
