Re: TDP Exchange 2003 Legacy Restore With Differential Backups
Robin, You can do this. The auto-select is selecting all databases by default. After everything is selected,, you can then de-select the databases you do not want to restore. This works just fine. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/28/2008 06:32:16 PM: [image removed] TDP Exchange 2003 Legacy Restore With Differential Backups Robin Lowe to: ADSM-L 10/28/2008 06:33 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager I have a query on the process to use when executing Legacy TDP Exchange 2003 Restores when using Differential Backups. My client's environment is MSCS Exchange 2003 Virtual Servers. TSM Server is AIX 5.4.3.2 Windows TSM client is 5.3.4.3 and 5.4.1.2 TDP 5.3.3 TDP GUI is used for all restores. Currently all daily backups using TDP are FULL backups, but as the volume of data grows I am looking at implementing differential backups to reduce the amount of data transferred in the backup window. The restore process, is to always use the Recovery Storage Group. So, a restore of a single Mailstore Database can be safely executed without compromising the live data. In order to do this, the Exchange administrator first defines the database to be restored in the RSG, then we run the restore from the Full backup. When we introduce the Differential backup, does the restore process have to be altered from Mailstore Database granularity to Storage Group by any chance? It appears that when you select the Differential Backup in the GUI during Restore processing, the previous FULL backup appears to select all mailstore DBs in the SG, is this correct? The worry is that in order to use RSG and Differential restores, the Exchange administrator would have to define to the RSG all the mailstore DBs in a Storage Group in order to restore a single mailstore DB. Surely this cannot be correct; have I missed something in the process? Thanks Robin Lowe Storage Consultant
TDP Exchange 2003 Legacy Restore With Differential Backups
I have a query on the process to use when executing Legacy TDP Exchange 2003 Restores when using Differential Backups. My client's environment is MSCS Exchange 2003 Virtual Servers. TSM Server is AIX 5.4.3.2 Windows TSM client is 5.3.4.3 and 5.4.1.2 TDP 5.3.3 TDP GUI is used for all restores. Currently all daily backups using TDP are FULL backups, but as the volume of data grows I am looking at implementing differential backups to reduce the amount of data transferred in the backup window. The restore process, is to always use the Recovery Storage Group. So, a restore of a single Mailstore Database can be safely executed without compromising the live data. In order to do this, the Exchange administrator first defines the database to be restored in the RSG, then we run the restore from the Full backup. When we introduce the Differential backup, does the restore process have to be altered from Mailstore Database granularity to Storage Group by any chance? It appears that when you select the Differential Backup in the GUI during Restore processing, the previous FULL backup appears to select all mailstore DBs in the SG, is this correct? The worry is that in order to use RSG and Differential restores, the Exchange administrator would have to define to the RSG all the mailstore DBs in a Storage Group in order to restore a single mailstore DB. Surely this cannot be correct; have I missed something in the process? Thanks Robin Lowe Storage Consultant
standard backup/archive exclusions for Exchange 2003 folders/files
I can't seem to find a list anywhere of items I should exclude from the regular OS backup on an exchange 2003 server. Anyone? Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097
Re: standard backup/archive exclusions for Exchange 2003 folders/files
Hi, The CommVault Galaxy admin books have a good list of per (type of) server exclude's. In any other case, just run a back-up and filter the errors into a default in/exclude list. In any case, if you are using the TDP for Exchange, the database files of exchange can be excluded. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of T. Lists Sent: dinsdag 23 januari 2007 19:07 To: ADSM-L@VM.MARIST.EDU Subject: standard backup/archive exclusions for Exchange 2003 folders/files I can't seem to find a list anywhere of items I should exclude from the regular OS backup on an exchange 2003 server. Anyone? Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t
Re: standard backup/archive exclusions for Exchange 2003 folders/files
The Exchange Server 2003 database files have a .EDB and .STM extension. For example: MBDB1.EDB, MBDB1.STM, MBDB2.EDB, MBDB2.STM The Exchange Server 2003 log files look like this: Exxx.log For example: E00.log, E001.log, E002.log, E00tmp.log There are also 2 reserve logs called res1.log and res2.log. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/23/2007 01:07:17 PM: I can't seem to find a list anywhere of items I should exclude from the regular OS backup on an exchange 2003 server. Anyone? Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097
Re: standard backup/archive exclusions for Exchange 2003 folders/files
Thanks a bunch. Is this documented anywhere? I looked, but couldn't find anything. --- Del Hoobler [EMAIL PROTECTED] wrote: The Exchange Server 2003 database files have a .EDB and .STM extension. For example: MBDB1.EDB, MBDB1.STM, MBDB2.EDB, MBDB2.STM The Exchange Server 2003 log files look like this: Exxx.log For example: E00.log, E001.log, E002.log, E00tmp.log There are also 2 reserve logs called res1.log and res2.log. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/23/2007 01:07:17 PM: I can't seem to find a list anywhere of items I should exclude from the regular OS backup on an exchange 2003 server. Anyone? Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com
Re: standard backup/archive exclusions for Exchange 2003 folders/files
I am sure the filenames are documented in the Microsoft publications. It is not currently documented in the DP/Exchange book. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/23/2007 03:42:12 PM: Thanks a bunch. Is this documented anywhere? I looked, but couldn't find anything. --- Del Hoobler [EMAIL PROTECTED] wrote: The Exchange Server 2003 database files have a .EDB and .STM extension. For example: MBDB1.EDB, MBDB1.STM, MBDB2.EDB, MBDB2.STM The Exchange Server 2003 log files look like this: Exxx.log For example: E00.log, E001.log, E002.log, E00tmp.log There are also 2 reserve logs called res1.log and res2.log. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/23/2007 01:07:17 PM: I can't seem to find a list anywhere of items I should exclude from the regular OS backup on an exchange 2003 server. Anyone? Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com
Re: Exchange 2003 on MSCS with TDP
Was wondering if you can help with TDP configuration on our Exchange cluster: We have 4 xchange machines clustered in an active/active/active/passive config. Three clusters: Cluster1 = exch1, exch4, exch3, exch2(failover) Cluster2 = exch2, exch4, exch3, exch1(failover) Cluster3 = exch3, exch2, exch1, exch4(failover) I understand that I only have to 1. install TDP for Exch on all nodes 2. install baclient on all nodes (to use scheduler) 3. registered all nodes, exch1, exch2...etc to TSM 4. registered all tdpnodes, exch1_tdp, exch2_tdp...etc to TSM Here is a copy of my opt files for baclient and tdp: TDP: NODename exch4_tdp CLUSTERnode yes COMPRESSIon Off PASSWORDAccessGenerate COMMMethodTCPip TCPPort 1500 TCPServeraddress 99tivolisrv1 *TCPServeraddress xx.xx.xx.xx TCPWindowsize 63 TCPBuffSize 32 *SCHEDMODE Polling *SCHEDLOGRetention 14 SCHEDMODE Prompted TCPCLIENTADDRESS 10.200.6.193 TCPCLIENTPORT 1502 Baclient: nodename exch1 commmethod tcpip tcpport 1500 TCPServeraddress 99tivolisrv1 TXNBYTElimit 25600 TCPWindowsize 63 TCPBuffsize 31 passwordaccess generate Domain c: schedlogretention 10 errorlogretention 10 dirmc directory Am I on the right track? After I have all nodes and all tdp nodes configured this way should it work? Thanks (new to the list) Tony Cuellar International Bank of Commerce San Antonio, TX Forum: ADSM.ORG - ADSM / TSM Mailing List Archive Date: 2004, Sep 16 From: Daniel Sparrman nobody at nowhere.com mailto:nobody%20at%20nowhere.com We have a customer backing up 4 clusters, with 8 nodes total. Each=20 Exchange Virtual server has approx. 4.000 users. Each server is running MS = Exch 2003 in a active/passive cluster configuration. Have been running for = a while now. No problems this far. We have conducted test-restores without = any problems. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellerv=E4gen 6B 183 62 T=C4BY V=E4xel: 08 - 754 98 00 Mobil: 070 - 399 27 51 TSM=5FUser tsm=5Fuser AT YAHOO DOT COM mailto:tsm=5Fuser%20AT%20YAHOO%20DOT%20COM =20 Sent by: ADSM: Dist Stor Manager ADSM-L AT VM.MARIST DOT EDU mailto:ADSM-L%20AT%20VM.MARIST%20DOT%20EDU 2004-09-16 15:18 Please respond to ADSM: Dist Stor Manager ADSM-L AT VM.MARIST DOT EDU mailto:ADSM-L%20AT%20VM.MARIST%20DOT%20EDU To ADSM-L AT VM.MARIST DOT EDU mailto:ADSM-L%20AT%20VM.MARIST%20DOT%20EDU cc Subject Exchange 2003 on MSCS with TDP I have run the Exchange TDP on a Microsoft Cluster with Exchange 2000. I=20 have also run the TDP on Exchange 2003. In both cases I haven't had any=20 problems. We have a few customers that are going to be moving to Exchange = 2003 on Cluster Servers. I was wondering how many people have already started backing up Exchange=20 2003 on cluster server with the latest TDP for Exchange? I have no reason = to beleive there will be any questions my customers are just asking how=20 many others are doing it so far.
Re: Exchange 2003 on MSCS with TDP
Antonio, You are on the right track. You may want set up a separate scheduler instance for each virtual exchange server on each of the machines that could run that particular virtual exchange server. This scheduler should be dependant on the virtual exchange server, so that it follows the virtual exchange server, wherever it goes. (similar to the other dependant exchange services.) Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/06/2006 12:19:29 PM: Was wondering if you can help with TDP configuration on our Exchange cluster: We have 4 xchange machines clustered in an active/active/active/passive config. Three clusters: Cluster1 = exch1, exch4, exch3, exch2(failover) Cluster2 = exch2, exch4, exch3, exch1(failover) Cluster3 = exch3, exch2, exch1, exch4(failover) I understand that I only have to 1. install TDP for Exch on all nodes 2. install baclient on all nodes (to use scheduler) 3. registered all nodes, exch1, exch2...etc to TSM 4. registered all tdpnodes, exch1_tdp, exch2_tdp...etc to TSM Here is a copy of my opt files for baclient and tdp: TDP: NODename exch4_tdp CLUSTERnode yes COMPRESSIon Off PASSWORDAccessGenerate COMMMethodTCPip TCPPort 1500 TCPServeraddress 99tivolisrv1 *TCPServeraddress xx.xx.xx.xx TCPWindowsize 63 TCPBuffSize 32 *SCHEDMODE Polling *SCHEDLOGRetention 14 SCHEDMODE Prompted TCPCLIENTADDRESS 10.200.6.193 TCPCLIENTPORT 1502 Baclient: nodename exch1 commmethod tcpip tcpport 1500 TCPServeraddress 99tivolisrv1 TXNBYTElimit 25600 TCPWindowsize 63 TCPBuffsize 31 passwordaccess generate Domain c: schedlogretention 10 errorlogretention 10 dirmc directory Am I on the right track? After I have all nodes and all tdp nodes configured this way should it work?
tdp version for exchange 2003
I don't know why, but I always have the hardest time finding the simplest information on IBM's web site. What TDP for Exchange supports Exchange 2003? Any besides 5.3? Is there a simple (ha!) spreadsheet somewhere that lays out requirements, prereqs, etc for this kind of thing? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: tdp version for exchange 2003
Exchange 2003 support was added in Data Protection for Microsoft Exchange version 5.2.1. Here is a web page that shows the Hardware and software requirements for IBM Tivoli Storage Manager for Mail version 5.3.3: http://www-1.ibm.com/support/docview.wss?rs=669context=SSTG2Duid=swg21233936loc=en_UScs=utf-8lang=en Also.. from the READMEs... = Data Protection for Microsoft Exchange version 5.3.3 requires the following MINIMUM software levels: - Microsoft Windows 2000 Server SP4 Microsoft Windows Server 2003 SP1 - Microsoft Exchange 2000 Server SP3 Microsoft Exchange 2003 Server SP1 = = Data Protection for Microsoft Exchange version 5.2.1 requires the following MINIMUM software levels: - Microsoft Windows NT Server SP5 Microsoft Windows 2000 Server SP3 Microsoft Windows Server 2003 - Microsoft Exchange Server 5.5 SP3 Microsoft Exchange 2000 Server SP2 Microsoft Exchange 2003 Server = Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/18/2006 04:19:33 PM: I don't know why, but I always have the hardest time finding the simplest information on IBM's web site. What TDP for Exchange supports Exchange 2003? Any besides 5.3? Is there a simple (ha!) spreadsheet somewhere that lays out requirements, prereqs, etc for this kind of thing?
Exchange 2003 Mailbox store backup
I would like to exclude the Public Folder database within a certain Storage Group (SG) in Exchange 2003 from FULL backup, but it seems that I can only specify SG for backup and not any specific Mailbox Store (database) within an SG. The TDPEXEC (GUI) even the TDPEXCC (CLI) backup all the databases within an SG. The only exception is the Database Copy backup type, but the downside is that this type of backup does not prune the transaction logs after successful backup. Am I missing anything? Can someone help me confirm that this is true or is there another method of achieving what I want to accomplish here. Thank you very much for any help and feedback. Khalid Khan Systems Engineer American Transmission Co. [EMAIL PROTECTED]
Re: Exchange 2003 Mailbox store backup
Khalid, This is not allowed because the transacation logs for an Exchange Storage Group are at the Storage Group level, not at the database level. If a backup product allowed you to do this, it would be letting you create backup that may not be recoverable in the event that you lost the disk that contained your public folder database. Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/30/2006 02:33:15 PM: I would like to exclude the Public Folder database within a certain Storage Group (SG) in Exchange 2003 from FULL backup, but it seems that I can only specify SG for backup and not any specific Mailbox Store (database) within an SG. The TDPEXEC (GUI) even the TDPEXCC (CLI) backup all the databases within an SG. The only exception is the Database Copy backup type, but the downside is that this type of backup does not prune the transaction logs after successful backup. Am I missing anything? Can someone help me confirm that this is true or is there another method of achieving what I want to accomplish here. Thank you very much for any help and feedback. Khalid Khan Systems Engineer American Transmission Co. [EMAIL PROTECTED]
Re: Exchange 2003 Mailbox store backup
Thank you very much Del. I knew about the logs being associated per SG, but did not put the two facts together. I guess my only other option is to create another SG and move the Public Folder db to it and exclude it. Thanks again for your feedback, much appreciated. Khalid -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, January 30, 2006 1:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Exchange 2003 Mailbox store backup Khalid, This is not allowed because the transacation logs for an Exchange Storage Group are at the Storage Group level, not at the database level. If a backup product allowed you to do this, it would be letting you create backup that may not be recoverable in the event that you lost the disk that contained your public folder database. Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/30/2006 02:33:15 PM: I would like to exclude the Public Folder database within a certain Storage Group (SG) in Exchange 2003 from FULL backup, but it seems that I can only specify SG for backup and not any specific Mailbox Store (database) within an SG. The TDPEXEC (GUI) even the TDPEXCC (CLI) backup all the databases within an SG. The only exception is the Database Copy backup type, but the downside is that this type of backup does not prune the transaction logs after successful backup. Am I missing anything? Can someone help me confirm that this is true or is there another method of achieving what I want to accomplish here. Thank you very much for any help and feedback. Khalid Khan Systems Engineer American Transmission Co. [EMAIL PROTECTED]
Re: Exchange 2003 restore to another server. HELP!
While Del is on vacation, we'll depend upon his previous postings... See http://www.mail-archive.com/adsm-l@vm.marist.edu/msg49740.html for starters on approaching this error condition. Another hit is http://www.mail-archive.com/adsm-l@vm.marist.edu/msg46912.html . Richard Sims TDP amateur On Apr 25, 2005, at 7:26 PM, Coats, Jack wrote: I am using the TDP for Exchange GUI, and restoring to a similar leveled version of Exchange on the same base OS. I get the following manual from the client: 04/25/2005 17:57:03 ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. 04/25/2005 17:57:03 Total backups inspected: 1 From the error logs on the Exchange server, I get the impression that I am not restoring to the correct Exchange database. How can I restore one exchange server (or portions) to another server? If my answer is RTFM, that is OK, please let me know which Fine Manual to read and where! ... TIA Jack
Exchange 2003
Does anybody know what version of TDP for mail is needed to backup Exchange 2003? Thanks Jim Murray Senior Systems Engineer Liberty Bank 860.638.2919 [EMAIL PROTECTED] There are only 10 kinds of people in this world - those that know binary and those that do not. Unless you have received this email through the Liberty bank secure email system, before you respond, please consider that any unencrypted e-mail that is sent to us is not secure. If you send regular e-mail to Liberty Bank, please do not include any private or confidential information such as social security numbers, unlisted telephone numbers, bank account numbers, personal income information, user names, passwords, etc. If you need to provide us with such information, please telephone us at (888)570-0773 during business hours or write to us at 315 Main St. Middletown, CT 06457. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer without disclosing it. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Bank. Thank you.
Re: Exchange 2003
Jim, We're using 5.21 on a number of Exchange Exchange cluster boxes with no problems. Regards, Iain Barnetson IT Systems Administrator UKN Infrastructure Operations -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Murray, Jim Sent: 26 April 2005 14:20 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Exchange 2003 Does anybody know what version of TDP for mail is needed to backup Exchange 2003? Thanks Jim Murray Senior Systems Engineer Liberty Bank 860.638.2919 [EMAIL PROTECTED] There are only 10 kinds of people in this world - those that know binary and those that do not. Unless you have received this email through the Liberty bank secure email system, before you respond, please consider that any unencrypted e-mail that is sent to us is not secure. If you send regular e-mail to Liberty Bank, please do not include any private or confidential information such as social security numbers, unlisted telephone numbers, bank account numbers, personal income information, user names, passwords, etc. If you need to provide us with such information, please telephone us at (888)570-0773 during business hours or write to us at 315 Main St. Middletown, CT 06457. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer without disclosing it. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Bank. Thank you.
Re: Exchange 2003 restore to another server. HELP!
Jack, As Richard suggested... Before doing the restore, on the Exchange server to which you will perform the restore to, you need to create the Storage Groups and databases exactly as they appeared on the original server (the upper/lower casing of the names also needs to exactly match). You may also need to mark the databases as: This database can be overwritten by a restore. Then you should be able to perform the restore. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 04/25/2005 07:26:52 PM: I am using the TDP for Exchange GUI, and restoring to a similar leveled version of Exchange on the same base OS. I get the following manual from the client: 04/25/2005 17:57:03 ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. 04/25/2005 17:57:03 Total backups inspected: 1 From the error logs on the Exchange server, I get the impression that I am not restoring to the correct Exchange database. How can I restore one exchange server (or portions) to another server? If my answer is RTFM, that is OK, please let me know which Fine Manual to read and where! ... TIA Jack
Exchange 2003 restore to another server. HELP!
I am using the TDP for Exchange GUI, and restoring to a similar leveled version of Exchange on the same base OS. I get the following manual from the client: 04/25/2005 17:57:03 ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. 04/25/2005 17:57:03 Total backups inspected: 1 From the error logs on the Exchange server, I get the impression that I am not restoring to the correct Exchange database. How can I restore one exchange server (or portions) to another server? If my answer is RTFM, that is OK, please let me know which Fine Manual to read and where! ... TIA Jack
[Question Answered]:Exchange 2003 on MSCS Windows 2003 with TDP 5.2.1
Hello All, Just wanted to follow up on the answer I got from Tivoli Level II support and others regarding my post. Yes, Tivoli does support TDP 5.2.1 w/Win 2k3 and Exchange 2k3 in Active/Passive mode. The documentation appears to be misleading. I have posted the response from Level II tech support also. Thanks to Del Hoobler for affirming this also. (I think someone else replied in the affirmative, but I can't seem to find it as I write this post.) Marc -- Response from Stephen Hull, IBM: Hi Marc, The documentation is a bit misleading, but DP for Exchange does support Exchange 2003 in an Active/Passive cluster. I'll try to get this updated for the next manual release. Per your voicemail, I'll go ahead and close the PMR. Regards, Stephen Stephen Hull IBM Tivoli Storage Manager, Level II Support - Excerpts from Original Post: We are installing Exchange 2003 on a 2 node Windows 2003 cluster. We are planning to run the Exchange server in Active/passive mode. According to the notes found on page 10 of the Installation and User's Guide (SC32-9058-01): 4. MSCS Active/Passive Configuration (Exchange Server 5.5, Exchange 2000 Server) 5. MSCS Active/Active Configuration (Exchange 2000 Server, Exchange Server 2003) I just got off the phone with IBM Tivoli support and they tell me that point 5 does hold. I have asked it to be escalated so that I can get a technical reason for this limitation. In my mind this puts the cart before the horse for the backup client to force me to configure Exchange in this way.
Re: TDP for exchange 2003
Exchange 2003 is supported at TDP for Exchange V5.2.1. Also, Windows 2003 is supported with V5.2 client and server. We've done a lot of testing with V5.2.3.2 and so far all is well. Ugie, Brian [EMAIL PROTECTED] wrote:Hi all, I have TDP for exchange version 2.2.0.0. Can this be used to backup exchange 2003? Our TSM server is version 4.1.3 If not, what is the min required? I have version 2.2.0.0 installed but I can not browse the info store when using the gui. Thanks Brian - Do you Yahoo!? vote.yahoo.com - Register online to vote today!
Re: TDP for exchange 2003
I have been told that TSM server must be at version 5.1.6.x or above in order to backup Exchange 2003 (with 5.2.1TDP)... is this correct or do I need to be running 5.2 server? Could someone please straighten this out? Thanks in advance Jon -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of TSM_User Sent: 08 October 2004 15:27 To: [EMAIL PROTECTED] Subject: Re: TDP for exchange 2003 Exchange 2003 is supported at TDP for Exchange V5.2.1. Also, Windows 2003 is supported with V5.2 client and server. We've done a lot of testing with V5.2.3.2 and so far all is well. Ugie, Brian [EMAIL PROTECTED] wrote:Hi all, I have TDP for exchange version 2.2.0.0. Can this be used to backup exchange 2003? Our TSM server is version 4.1.3 If not, what is the min required? I have version 2.2.0.0 installed but I can not browse the info store when using the gui. Thanks Brian - Do you Yahoo!? vote.yahoo.com - Register online to vote today!
Re: TDP for exchange 2003
Jon, The requirements as noted in the README file for Data Protection for Exchange 5.2.1 are: - IBM Tivoli Storage Manager Server 5.1 You do not need to be running a 5.2 TSM Server. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/08/2004 11:48:02 AM: I have been told that TSM server must be at version 5.1.6.x or above in order to backup Exchange 2003 (with 5.2.1TDP)... is this correct or do I need to be running 5.2 server? Could someone please straighten this out? Thanks in advance Jon -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of TSM_User Sent: 08 October 2004 15:27 To: [EMAIL PROTECTED] Subject: Re: TDP for exchange 2003 Exchange 2003 is supported at TDP for Exchange V5.2.1. Also, Windows 2003 is supported with V5.2 client and server. We've done a lot of testing with V5.2.3.2 and so far all is well. Ugie, Brian [EMAIL PROTECTED] wrote:Hi all, I have TDP for exchange version 2.2.0.0. Can this be used to backup exchange 2003? Our TSM server is version 4.1.3 If not, what is the min required? I have version 2.2.0.0 installed but I can not browse the info store when using the gui. Thanks Brian - Do you Yahoo!? vote.yahoo.com - Register online to vote today!
TDP for exchange 2003
Hi all, I have TDP for exchange version 2.2.0.0. Can this be used to backup exchange 2003? Our TSM server is version 4.1.3 If not, what is the min required? I have version 2.2.0.0 installed but I can not browse the info store when using the gui. Thanks Brian
Re: TDP for exchange 2003
You will have to run TDP for Exchange v5.2. We just brought up our first 2003 server. Not sure about server code. We are running 5.1.8.1. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ugie, Brian Sent: Thursday, October 07, 2004 3:38 PM To: [EMAIL PROTECTED] Subject: TDP for exchange 2003 Hi all, I have TDP for exchange version 2.2.0.0. Can this be used to backup exchange 2003? Our TSM server is version 4.1.3 If not, what is the min required? I have version 2.2.0.0 installed but I can not browse the info store when using the gui. Thanks Brian -- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. --
Exchange 2003 on MSCS Windows 2003 with TDP 5.2.1
Hello Fellow TSM'ers! We are installing Exchange 2003 on a 2 node Windows 2003 cluster. We are planning to run the Exchange server in Active/passive mode. According to the notes found on page 10 of the Installation and User's Guide (SC32-9058-01): 4. MSCS Active/Passive Configuration (Exchange Server 5.5, Exchange 2000 Server) 5. MSCS Active/Active Configuration (Exchange 2000 Server, Exchange Server 2003) I just got off the phone with IBM Tivoli support and they tell me that point 5 does hold. I have asked it to be escalated so that I can get a technical reason for this limitation. In my mind this puts the cart before the horse for the backup client to force me to configure Exchange in this way. If there are any of you out there who are running Exch 2003 on a Win 2003 cluster in Active/Passive support, I would love to hear from you. Thanks. Marc -- Marc D. Taylor Research Programmer Beckman Institute at the University of Illinois, Urbana-Champaign Phone: 217-244-7373, Fax: 217-333-8206 http:\\biss.beckman.uiuc.edu
Re: Exchange 2003 on MSCS Windows 2003 with TDP 5.2.1
Marc, Sorry, the book is misleading. Data Protection for Exchange works in both Active/Passive and Active/Active! As a rule of thumb, if something supports Active/Active, it also supports Active/Passive since Active/Passive is a simplified case of Active/Active. It works just fine. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 10/05/2004 01:26:55 PM: Hello Fellow TSM'ers! We are installing Exchange 2003 on a 2 node Windows 2003 cluster. We are planning to run the Exchange server in Active/passive mode. According to the notes found on page 10 of the Installation and User's Guide (SC32-9058-01): 4. MSCS Active/Passive Configuration (Exchange Server 5.5, Exchange 2000 Server) 5. MSCS Active/Active Configuration (Exchange 2000 Server, Exchange Server 2003) I just got off the phone with IBM Tivoli support and they tell me that point 5 does hold. I have asked it to be escalated so that I can get a technical reason for this limitation. In my mind this puts the cart before the horse for the backup client to force me to configure Exchange in this way. If there are any of you out there who are running Exch 2003 on a Win 2003 cluster in Active/Passive support, I would love to hear from you. Thanks. Marc -- Marc D. Taylor Research Programmer Beckman Institute at the University of Illinois, Urbana-Champaign Phone: 217-244-7373, Fax: 217-333-8206 http:\\biss.beckman.uiuc.edu
Re: Exchange 2003 on MSCS with TDP
Yes, We are using TDP on Exchange 2003 to back up Exchange 2003 on cluster server. We also do daily restores at disaster site and so far its going smooth. Regards Yashwant Rane On Thu, 16 Sep 2004 TSM_User wrote : I have run the Exchange TDP on a Microsoft Cluster with Exchange 2000. I have also run the TDP on Exchange 2003. In both cases I haven't had any problems. We have a few customers that are going to be moving to Exchange 2003 on Cluster Servers. I was wondering how many people have already started backing up Exchange 2003 on cluster server with the latest TDP for Exchange? I have no reason to beleive there will be any questions my customers are just asking how many others are doing it so far. - Do you Yahoo!? vote.yahoo.com - Register online to vote today! With Best Regards Yashwant Rane
Exchange 2003 on MSCS with TDP
I have run the Exchange TDP on a Microsoft Cluster with Exchange 2000. I have also run the TDP on Exchange 2003. In both cases I haven't had any problems. We have a few customers that are going to be moving to Exchange 2003 on Cluster Servers. I was wondering how many people have already started backing up Exchange 2003 on cluster server with the latest TDP for Exchange? I have no reason to beleive there will be any questions my customers are just asking how many others are doing it so far. - Do you Yahoo!? Yahoo! Mail is new and improved - Check it out!
Re: Exchange 2003 on MSCS with TDP
We have a customer backing up 4 clusters, with 8 nodes total. Each Exchange Virtual server has approx. 4.000 users. Each server is running MS Exch 2003 in a active/passive cluster configuration. Have been running for a while now. No problems this far. We have conducted test-restores without any problems. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 TÄBY Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 TSM_User [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 2004-09-16 15:18 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Exchange 2003 on MSCS with TDP I have run the Exchange TDP on a Microsoft Cluster with Exchange 2000. I have also run the TDP on Exchange 2003. In both cases I haven't had any problems. We have a few customers that are going to be moving to Exchange 2003 on Cluster Servers. I was wondering how many people have already started backing up Exchange 2003 on cluster server with the latest TDP for Exchange? I have no reason to beleive there will be any questions my customers are just asking how many others are doing it so far. - Do you Yahoo!? Yahoo! Mail is new and improved - Check it out!
Exchange 2003 on MSCS with TDP
I have run the Exchange TDP on a Microsoft Cluster with Exchange 2000. I have also run the TDP on Exchange 2003. In both cases I haven't had any problems. We have a few customers that are going to be moving to Exchange 2003 on Cluster Servers. I was wondering how many people have already started backing up Exchange 2003 on cluster server with the latest TDP for Exchange? I have no reason to beleive there will be any questions my customers are just asking how many others are doing it so far. - Do you Yahoo!? vote.yahoo.com - Register online to vote today!
Re: Exchange 2003 on MSCS with TDP
Hi, We were early adopters of exchange 2003 (we went live the week it came out, we skipped from 5.5 to 2003). We beta tested the TDP version that supports 2003 with no problems. We have done restores with the production client several times (doing one right now). Both the test bed and the production servers were/are clustered. We just made a separate scheduler for the exchange product per the manual and made that a cluster resource (generic service). Michael Wheelock Integris Health -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of TSM_User Sent: Thursday, September 16, 2004 8:47 AM To: [EMAIL PROTECTED] Subject: Exchange 2003 on MSCS with TDP I have run the Exchange TDP on a Microsoft Cluster with Exchange 2000. I have also run the TDP on Exchange 2003. In both cases I haven't had any problems. We have a few customers that are going to be moving to Exchange 2003 on Cluster Servers. I was wondering how many people have already started backing up Exchange 2003 on cluster server with the latest TDP for Exchange? I have no reason to beleive there will be any questions my customers are just asking how many others are doing it so far. - Do you Yahoo!? vote.yahoo.com - Register online to vote today! ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). **
TDP, Exchange 2003, and SANs
I am working up my plan to backup our new Exchange 2003 storage groups. Our environment includes: Exchange 2003 running on Windows 2003 TSM 5.2.2.5 running on AIX 5.2 Shark storage for the AIX server's disk based storage EVA (I think) storage for the Exchange server data LTO1 in a 3584 accessed across a McData 4500 SAN switch I read through the TDP for Exchange v5.2 documentation. It appears that I cannot split up the different data types (meta, data, logs) into different management classes, but I can put the different backup types (full, copy, incr, diff, dbcopy) into different management classes. My questions are... When doing an incr, or diff backup via TDP, how does TDP do that? I intend to backup the storage groups full across the SAN. The storage groups will be 20GB in size. From what the Exchange admins are telling me, Exchange creates log files with a max size of 5MB. During an incr or diff backup, does TDP backup all the log file transaction information as one filename to TSM, allowing for less overhead when using a SAN, or does TDP keep individual log file names intact, backing up each one serially (which would lead me to believe that using the SAN would actually slow things down)? All my experience with TDP is in SQL (and a bit in Domino). Does TDP for Exchange get out of sync as easily as TDP for SQL when dealing with management class name changes? With TDP for SQL, I have to rename the existing filespaces and start with new filespaces whenever I change management class names to ensure the meta stays in sync with the data. Are there any quirks like this in TDP for Exchange? Are there any other things I should be considering? Thanks in advance, Todd
Re: TDP, Exchange 2003, and SANs
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Todd Lundstedt I read through the TDP for Exchange v5.2 documentation. It appears that I cannot split up the different data types (meta, data, logs) into different management classes, but I can put the different backup types (full, copy, incr, diff, dbcopy) into different management classes. When doing an incr, or diff backup via TDP, how does TDP do that? An incremental backup with TDP for Mail (Exchange) is actually a backup of all log files since the last incremental backup. A differential backup is, IIRC, a backup of the all the log files since the last full backup. -- Mark Stapleton
Re: TDP, Exchange 2003, and SANs
Todd, I have embedded some answers below. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/24/2004 10:39:59 AM: I am working up my plan to backup our new Exchange 2003 storage groups. Our environment includes: Exchange 2003 running on Windows 2003 TSM 5.2.2.5 running on AIX 5.2 Shark storage for the AIX server's disk based storage EVA (I think) storage for the Exchange server data LTO1 in a 3584 accessed across a McData 4500 SAN switch I read through the TDP for Exchange v5.2 documentation. It appears that I cannot split up the different data types (meta, data, logs) into different management classes, but I can put the different backup types (full, copy, incr, diff, dbcopy) into different management classes. This is intentional because you want all TSM objects that represent a single, logical backup to be managed under the same policy but you may also want to be able to manage the different backup types with different policy. My questions are... When doing an incr, or diff backup via TDP, how does TDP do that? I intend to backup the storage groups full across the SAN. The storage groups will be 20GB in size. From what the Exchange admins are telling me, Exchange creates log files with a max size of 5MB. During an incr or diff backup, does TDP backup all the log file transaction information as one filename to TSM, allowing for less overhead when using a SAN, or does TDP keep individual log file names intact, backing up each one serially (which would lead me to believe that using the SAN would actually slow things down)? Data Protection for Exchange performs incremental and differential backups by backing up the full transaction log files to TSM. They are all placed into a single TSM backup object. During restore, Data Protection for Exchange will pull the individual log files out of the single TSM object and write them to disk. All my experience with TDP is in SQL (and a bit in Domino). Does TDP for Exchange get out of sync as easily as TDP for SQL when dealing with management class name changes? With TDP for SQL, I have to rename the existing filespaces and start with new filespaces whenever I change management class names to ensure the meta stays in sync with the data. Are there any quirks like this in TDP for Exchange? SQL has some unique issues that cause the anomaly that you are referring to. The root cause of it on SQL is the multiple-striping that is allowed and the temporary objects that are used to hold pre-transaction-commit striped data. Even if you didn't use multiple-striping, it can occur. Data Protection for Exchange does NOT have this issue. Are there any other things I should be considering? Thanks in advance, Todd
Re: TDP, Exchange 2003, and SANs
Yeah.. I read that in the documentation, and understand that log files are deleted after a successful incremental, and not deleted after a successful diff... But, I am looking for more detail in the actual transfer and storage, as the rest of my email indicated. Thx though Stapleton, Mark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/24/2004 09:45 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Fax to: Subject:Re: TDP, Exchange 2003, and SANs From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Todd Lundstedt I read through the TDP for Exchange v5.2 documentation. It appears that I cannot split up the different data types (meta, data, logs) into different management classes, but I can put the different backup types (full, copy, incr, diff, dbcopy) into different management classes. When doing an incr, or diff backup via TDP, how does TDP do that? An incremental backup with TDP for Mail (Exchange) is actually a backup of all log files since the last incremental backup. A differential backup is, IIRC, a backup of the all the log files since the last full backup. -- Mark Stapleton
Re: TDP, Exchange 2003, and SANs
Del, Thanks.. follow up question... You said... Data Protection for Exchange performs incremental and differential backups by backing up the full transaction log files to TSM. They are all placed into a single TSM backup object. From this, would it be safe to assume that the data from hundreds of 5MB log files would stream well across the SAN, since your description infers that the incr would be handled with a single TSM database transaction? Does the txngroupmax value have any bearing on this? You said the incr/diff backup only backs up the full transaction log files. That concerns me a bit. The Exchange admin indicated that Exchange has four log files open at all times. This means that up to 20 MB of transactions would not get backed up during a backup (full included). We are new to Exchange, migrating from Domino (plea$e, plea$e, don't a$k me why we would even what to do that... it'$ a long $tory). I guess we will have to just live with the incomplete/incorrect point of recovery. Thanks again for the quick and informative reply, Todd Del Hoobler [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/24/2004 10:02 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Fax to: Subject:Re: TDP, Exchange 2003, and SANs Todd, I have embedded some answers below. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/24/2004 10:39:59 AM: I am working up my plan to backup our new Exchange 2003 storage groups. Our environment includes: Exchange 2003 running on Windows 2003 TSM 5.2.2.5 running on AIX 5.2 Shark storage for the AIX server's disk based storage EVA (I think) storage for the Exchange server data LTO1 in a 3584 accessed across a McData 4500 SAN switch I read through the TDP for Exchange v5.2 documentation. It appears that I cannot split up the different data types (meta, data, logs) into different management classes, but I can put the different backup types (full, copy, incr, diff, dbcopy) into different management classes. This is intentional because you want all TSM objects that represent a single, logical backup to be managed under the same policy but you may also want to be able to manage the different backup types with different policy. My questions are... When doing an incr, or diff backup via TDP, how does TDP do that? I intend to backup the storage groups full across the SAN. The storage groups will be 20GB in size. From what the Exchange admins are telling me, Exchange creates log files with a max size of 5MB. During an incr or diff backup, does TDP backup all the log file transaction information as one filename to TSM, allowing for less overhead when using a SAN, or does TDP keep individual log file names intact, backing up each one serially (which would lead me to believe that using the SAN would actually slow things down)? Data Protection for Exchange performs incremental and differential backups by backing up the full transaction log files to TSM. They are all placed into a single TSM backup object. During restore, Data Protection for Exchange will pull the individual log files out of the single TSM object and write them to disk. All my experience with TDP is in SQL (and a bit in Domino). Does TDP for Exchange get out of sync as easily as TDP for SQL when dealing with management class name changes? With TDP for SQL, I have to rename the existing filespaces and start with new filespaces whenever I change management class names to ensure the meta stays in sync with the data. Are there any quirks like this in TDP for Exchange? SQL has some unique issues that cause the anomaly that you are referring to. The root cause of it on SQL is the multiple-striping that is allowed and the temporary objects that are used to hold pre-transaction-commit striped data. Even if you didn't use multiple-striping, it can occur. Data Protection for Exchange does NOT have this issue. Are there any other things I should be considering? Thanks in advance, Todd
Re: TDP, Exchange 2003, and SANs
Todd, Answers embedded. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/24/2004 11:17:55 AM: Del, Thanks.. follow up question... You said... Data Protection for Exchange performs incremental and differential backups by backing up the full transaction log files to TSM. They are all placed into a single TSM backup object. From this, would it be safe to assume that the data from hundreds of 5MB log files would stream well across the SAN, since your description infers that the incr would be handled with a single TSM database transaction? Does the txngroupmax value have any bearing on this? There are always various factors that can influence this, however, in theory, you are correct. These will be represented by a single stream of data being backing up to a single TSM object. txngroupmax will not affect this since it is a single TSM object. My best suggestion is to try it to see how it performs for you. You said the incr/diff backup only backs up the full transaction log files. That concerns me a bit. The Exchange admin indicated that Exchange has four log files open at all times. This means that up to 20 MB of transactions would not get backed up during a backup (full included). We are new to Exchange, migrating from Domino (plea$e, plea$e, don't a$k me why we would even what to do that... it'$ a long $tory). I guess we will have to just live with the incomplete/incorrect point of recovery. You don't need to live with anything. You don't need to be concerned, either. Data Protection for Exchange works directly in conjunction with the Exchange server through the Exchange backup API. The Exchange Server tells Data Protection for Exchange which logs files need to be backed up. Data Protection for Exchange takes that list and backs them up. You don't need to worry about an incomplete backup, either. Since Data Protection for Exchange uses the Exchange backup API, all of your backups will be completely consistent. Thanks again for the quick and informative reply, Todd
Re: TDP, Exchange 2003, and SANs
Thanks, Del. My comment regarding living with an incomplete/incorrect point of recovery was solely meant to represent that in a complete data center wipe-out, the existing full and incrementals that we have offsite would not accurately represent what was in a particular mailbox at the time of the backup. Since TDP doesn't backup a log file unless it is filled (and I assume that means if a log file is open, the TDP doesn't backup that information in those logs). If somehow, TDP is able to get this information from the currently open log files (four per storage group, or is it four per mail store), then we will be OK. Thanks again.. I will be testing how all this works as soon as we can. Todd Del Hoobler [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/24/2004 10:39 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Fax to: Subject:Re: TDP, Exchange 2003, and SANs Todd, Answers embedded. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/24/2004 11:17:55 AM: Del, Thanks.. follow up question... You said... Data Protection for Exchange performs incremental and differential backups by backing up the full transaction log files to TSM. They are all placed into a single TSM backup object. From this, would it be safe to assume that the data from hundreds of 5MB log files would stream well across the SAN, since your description infers that the incr would be handled with a single TSM database transaction? Does the txngroupmax value have any bearing on this? There are always various factors that can influence this, however, in theory, you are correct. These will be represented by a single stream of data being backing up to a single TSM object. txngroupmax will not affect this since it is a single TSM object. My best suggestion is to try it to see how it performs for you. You said the incr/diff backup only backs up the full transaction log files. That concerns me a bit. The Exchange admin indicated that Exchange has four log files open at all times. This means that up to 20 MB of transactions would not get backed up during a backup (full included). We are new to Exchange, migrating from Domino (plea$e, plea$e, don't a$k me why we would even what to do that... it'$ a long $tory). I guess we will have to just live with the incomplete/incorrect point of recovery. You don't need to live with anything. You don't need to be concerned, either. Data Protection for Exchange works directly in conjunction with the Exchange server through the Exchange backup API. The Exchange Server tells Data Protection for Exchange which logs files need to be backed up. Data Protection for Exchange takes that list and backs them up. You don't need to worry about an incomplete backup, either. Since Data Protection for Exchange uses the Exchange backup API, all of your backups will be completely consistent. Thanks again for the quick and informative reply, Todd
Re: TDP, Exchange 2003, and SANs
Todd, Again, you don't need to worry about it. When Data Protection for Exchange signals that it will start a backup, the Exchange Server starts a new set of logs. That is, the current transaction logs are no longer written to and are marked full and backed up (even though there may be some unused portions of the file.) Exchange handles all of this for you. Obviously, in the case of a complete disaster, you can only restore what has been backed up. If you aren't doing a constant incremental backup, you will also be missing the the full logs that have been generated since the last incremental. You will want to base the frequency of your incremental backups on how much data you are willing to lose in case of a complete disaster... in most cases a rare occurance. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/24/2004 11:59:45 AM: Thanks, Del. My comment regarding living with an incomplete/incorrect point of recovery was solely meant to represent that in a complete data center wipe-out, the existing full and incrementals that we have offsite would not accurately represent what was in a particular mailbox at the time of the backup. Since TDP doesn't backup a log file unless it is filled (and I assume that means if a log file is open, the TDP doesn't backup that information in those logs). If somehow, TDP is able to get this information from the currently open log files (four per storage group, or is it four per mail store), then we will be OK. Thanks again.. I will be testing how all this works as soon as we can. Todd
Re: need help with ms-exchange 2003 cluster backups
Thanks to all for the pointers -- Del, the magic was your note about /EXCSERVER (along with getting the resources for server one back on server one -- sigh). Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, June 14, 2004 11:34 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, Can you please get the answers to these questions from your people? 1. What do you see in the TDPEXC.LOG file? 2. What errors messages are you getting? Check the output the TDPEXC.LOG file and the output of the TDPEXCC command? 3. Does the userid that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? One thing to keep in mind for a cluster setup is that you should only be running the scheduled backup on the machine that currently has the running instance of the Exchange virtual server. When running with the TSM BA client scheduler this is accomplished by creating a cluster resource for the TSM BA scheduler that is dependant on the Exchange virtual server cluster resource. Also, when running in a cluster, you need to run specify the /EXCSERVER=virt-exch-server-name option, where virt-exch-server-name is the name of your Exchange virtual server. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 11:15:17 AM: I know it's not much to go on -- that's what I'm getting from MY people :-( At the server side, I see no connect from the cluster, so I'm making the assumption that the Windows 2003 scheduling process (whatever it is) isn't actually working (Is there anything besides the 'at' command? I haven't looked at this aspect of Windows since NT 3.51 . . .) Tom Kauffman NIBCO, Inc
need help with ms-exchange 2003 cluster backups
I don't do windows and my windows support people have hit a blank wall. We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is) and went to a clustered environment - two nodes in active/active mode, with the userbase and info-store split between them. And, of course, went to the current TDP Exchange client that claims to know both Exchange 2003 and clustering. We're using the Windows scheduling process to kick off the backups - and it's not happening. I don't have the regular TSM client on these two systems, as our 'bare metal restore' concept is rebuild/relaod from CD and then restore the info-store. I'm looking for suggestions on what to tell the guys to look for, and where to look. Any help would be appreciated! Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
Tom, it's not happening is not much to go on. :-) Can you get more details on what is not working? What do you see in the TDPEXC.LOG file? What errors are you getting? Does the user-id that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? Data Protection for Exchange 5.2.1 has been tested in an Exchange 2003 Active/Active Cluster environment. All scheduler testing was done using the TSM backup/archive client scheduler. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 09:37:24 AM: I don't do windows and my windows support people have hit a blank wall. We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is) and went to a clustered environment - two nodes in active/active mode, with the userbase and info-store split between them. And, of course, went to the current TDP Exchange client that claims to know both Exchange 2003 and clustering. We're using the Windows scheduling process to kick off the backups - and it's not happening. I don't have the regular TSM client on these two systems, as our 'bare metal restore' concept is rebuild/relaod from CD and then restore the info-store. I'm looking for suggestions on what to tell the guys to look for, and where to look. Any help would be appreciated! Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
I know it's not much to go on -- that's what I'm getting from MY people :-( At the server side, I see no connect from the cluster, so I'm making the assumption that the Windows 2003 scheduling process (whatever it is) isn't actually working (Is there anything besides the 'at' command? I haven't looked at this aspect of Windows since NT 3.51 . . .) Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, June 14, 2004 9:12 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, it's not happening is not much to go on. :-) Can you get more details on what is not working? What do you see in the TDPEXC.LOG file? What errors are you getting? Does the user-id that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? Data Protection for Exchange 5.2.1 has been tested in an Exchange 2003 Active/Active Cluster environment. All scheduler testing was done using the TSM backup/archive client scheduler. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 09:37:24 AM: I don't do windows and my windows support people have hit a blank wall. We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is) and went to a clustered environment - two nodes in active/active mode, with the userbase and info-store split between them. And, of course, went to the current TDP Exchange client that claims to know both Exchange 2003 and clustering. We're using the Windows scheduling process to kick off the backups - and it's not happening. I don't have the regular TSM client on these two systems, as our 'bare metal restore' concept is rebuild/relaod from CD and then restore the info-store. I'm looking for suggestions on what to tell the guys to look for, and where to look. Any help would be appreciated! Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
Tom, From the looks of it, only the TDP is installed. In the readme it is stated that: Software Requirements - Data Protection for Microsoft Exchange version 5.2.1 requires the following MINIMUM software levels: - IBM Tivoli Storage Manager API 5.1.5 The API is deliverd in the BA client package. Before scheduling the back-ups, I would recommend making one session from the GUI, to see if the communication between the TDP is working. Regards, Karel Bos Customer Unit Nuon Atos Origin Naritaweg 50-52 1043 BZ Amsterdam Office: +31 (0)20 4841132 Fax:+31 (0)20 Mobile: +31 (0)6 51 29 88 01 [EMAIL PROTECTED] www.atosorigin.com This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Kauffman, Tom Sent: maandag 14 juni 2004 17:15 To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups I know it's not much to go on -- that's what I'm getting from MY people :-( At the server side, I see no connect from the cluster, so I'm making the assumption that the Windows 2003 scheduling process (whatever it is) isn't actually working (Is there anything besides the 'at' command? I haven't looked at this aspect of Windows since NT 3.51 . . .) Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, June 14, 2004 9:12 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, it's not happening is not much to go on. :-) Can you get more details on what is not working? What do you see in the TDPEXC.LOG file? What errors are you getting? Does the user-id that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? Data Protection for Exchange 5.2.1 has been tested in an Exchange 2003 Active/Active Cluster environment. All scheduler testing was done using the TSM backup/archive client scheduler. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 09:37:24 AM: I don't do windows and my windows support people have hit a blank wall. We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is) and went to a clustered environment - two nodes in active/active mode, with the userbase and info-store split between them. And, of course, went to the current TDP Exchange client that claims to know both Exchange 2003 and clustering. We're using the Windows scheduling process to kick off the backups - and it's not happening. I don't have the regular TSM client on these two systems, as our 'bare metal restore' concept is rebuild/relaod from CD and then restore the info-store. I'm looking for suggestions on what to tell the guys to look for, and where to look. Any help would be appreciated! Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
1) Can they connect from the TDP gui and/or command line ? 2) If so, can they backup the Exchange server ? 3) If not, what are the errors they are receiving ? Check the tsm\tdpexc\dsierror.log and dsmerror.log, also, check the event viewer for this system and see if any additional errors are logged. You do not need the BA client software to use the TDP client. Duane Ochs Enterprise Computing Quad/Graphics Sussex, Wisconsin 414-566-2375 phone 414-917-0736 beeper [EMAIL PROTECTED] www.QG.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Sent: Monday, June 14, 2004 10:15 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups I know it's not much to go on -- that's what I'm getting from MY people :-( At the server side, I see no connect from the cluster, so I'm making the assumption that the Windows 2003 scheduling process (whatever it is) isn't actually working (Is there anything besides the 'at' command? I haven't looked at this aspect of Windows since NT 3.51 . . .) Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, June 14, 2004 9:12 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, it's not happening is not much to go on. :-) Can you get more details on what is not working? What do you see in the TDPEXC.LOG file? What errors are you getting? Does the user-id that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? Data Protection for Exchange 5.2.1 has been tested in an Exchange 2003 Active/Active Cluster environment. All scheduler testing was done using the TSM backup/archive client scheduler. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 09:37:24 AM: I don't do windows and my windows support people have hit a blank wall. We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is) and went to a clustered environment - two nodes in active/active mode, with the userbase and info-store split between them. And, of course, went to the current TDP Exchange client that claims to know both Exchange 2003 and clustering. We're using the Windows scheduling process to kick off the backups - and it's not happening. I don't have the regular TSM client on these two systems, as our 'bare metal restore' concept is rebuild/relaod from CD and then restore the info-store. I'm looking for suggestions on what to tell the guys to look for, and where to look. Any help would be appreciated! Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
Tom, Can you please get the answers to these questions from your people? 1. What do you see in the TDPEXC.LOG file? 2. What errors messages are you getting? Check the output the TDPEXC.LOG file and the output of the TDPEXCC command? 3. Does the userid that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? One thing to keep in mind for a cluster setup is that you should only be running the scheduled backup on the machine that currently has the running instance of the Exchange virtual server. When running with the TSM BA client scheduler this is accomplished by creating a cluster resource for the TSM BA scheduler that is dependant on the Exchange virtual server cluster resource. Also, when running in a cluster, you need to run specify the /EXCSERVER=virt-exch-server-name option, where virt-exch-server-name is the name of your Exchange virtual server. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 11:15:17 AM: I know it's not much to go on -- that's what I'm getting from MY people :-( At the server side, I see no connect from the cluster, so I'm making the assumption that the Windows 2003 scheduling process (whatever it is) isn't actually working (Is there anything besides the 'at' command? I haven't looked at this aspect of Windows since NT 3.51 . . .) Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
1) Yes 2) Yes And this is why I'm thinking it's actually a scheduling issue. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Monday, June 14, 2004 11:30 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups 1) Can they connect from the TDP gui and/or command line ? 2) If so, can they backup the Exchange server ? 3) If not, what are the errors they are receiving ? Check the tsm\tdpexc\dsierror.log and dsmerror.log, also, check the event viewer for this system and see if any additional errors are logged. You do not need the BA client software to use the TDP client. Duane Ochs Enterprise Computing Quad/Graphics Sussex, Wisconsin 414-566-2375 phone 414-917-0736 beeper [EMAIL PROTECTED] www.QG.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Sent: Monday, June 14, 2004 10:15 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups I know it's not much to go on -- that's what I'm getting from MY people :-( At the server side, I see no connect from the cluster, so I'm making the assumption that the Windows 2003 scheduling process (whatever it is) isn't actually working (Is there anything besides the 'at' command? I haven't looked at this aspect of Windows since NT 3.51 . . .) Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, June 14, 2004 9:12 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, it's not happening is not much to go on. :-) Can you get more details on what is not working? What do you see in the TDPEXC.LOG file? What errors are you getting? Does the user-id that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? Data Protection for Exchange 5.2.1 has been tested in an Exchange 2003 Active/Active Cluster environment. All scheduler testing was done using the TSM backup/archive client scheduler. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 09:37:24 AM: I don't do windows and my windows support people have hit a blank wall. We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is) and went to a clustered environment - two nodes in active/active mode, with the userbase and info-store split between them. And, of course, went to the current TDP Exchange client that claims to know both Exchange 2003 and clustering. We're using the Windows scheduling process to kick off the backups - and it's not happening. I don't have the regular TSM client on these two systems, as our 'bare metal restore' concept is rebuild/relaod from CD and then restore the info-store. I'm looking for suggestions on what to tell the guys to look for, and where to look. Any help would be appreciated! Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
Drat! I missed that! . . . What is fascinating is that the backups can be run by hand and look like they're working correctly . . . We'll drop the API on and see if anything changes. Thanks. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, June 14, 2004 10:42 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, From the looks of it, only the TDP is installed. In the readme it is stated that: Software Requirements - Data Protection for Microsoft Exchange version 5.2.1 requires the following MINIMUM software levels: - IBM Tivoli Storage Manager API 5.1.5 The API is deliverd in the BA client package. Before scheduling the back-ups, I would recommend making one session from the GUI, to see if the communication between the TDP is working. Regards, Karel Bos Customer Unit Nuon Atos Origin Naritaweg 50-52 1043 BZ Amsterdam Office: +31 (0)20 4841132 Fax:+31 (0)20 Mobile: +31 (0)6 51 29 88 01 [EMAIL PROTECTED] www.atosorigin.com This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Kauffman, Tom Sent: maandag 14 juni 2004 17:15 To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups I know it's not much to go on -- that's what I'm getting from MY people :-( At the server side, I see no connect from the cluster, so I'm making the assumption that the Windows 2003 scheduling process (whatever it is) isn't actually working (Is there anything besides the 'at' command? I haven't looked at this aspect of Windows since NT 3.51 . . .) Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, June 14, 2004 9:12 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, it's not happening is not much to go on. :-) Can you get more details on what is not working? What do you see in the TDPEXC.LOG file? What errors are you getting? Does the user-id that owns the Windows Scheduler Service have enough authority to back up the Exchange server and access the Windows registry? Data Protection for Exchange 5.2.1 has been tested in an Exchange 2003 Active/Active Cluster environment. All scheduler testing was done using the TSM backup/archive client scheduler. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 09:37:24 AM: I don't do windows and my windows support people have hit a blank wall. We just migrated from MS-Exchange 5.5 to Exchange 2003 (I think it is) and went to a clustered environment - two nodes in active/active mode, with the userbase and info-store split between them. And, of course, went to the current TDP Exchange client that claims to know both Exchange 2003 and clustering. We're using the Windows scheduling process to kick off the backups - and it's not happening. I don't have the regular TSM client on these two systems, as our 'bare metal restore' concept is rebuild/relaod from CD and then restore the info-store. I'm looking for suggestions on what to tell the guys to look for, and where to look. Any help would be appreciated! Tom Kauffman NIBCO, Inc
Re: need help with ms-exchange 2003 cluster backups
Tom, This isn't the problem. Data Protection for Exchange automatically ships and installs the TSM API. You do not need to install the TSM BA client unless you decide to the use the TSM BA client scheduler. Please refer to my previous append to get more details about the problem. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 01:17:51 PM: Drat! I missed that! . . . What is fascinating is that the backups can be run by hand and look like they're working correctly . . . We'll drop the API on and see if anything changes. Thanks. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, June 14, 2004 10:42 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, From the looks of it, only the TDP is installed. In the readme it is stated that: Software Requirements - Data Protection for Microsoft Exchange version 5.2.1 requires the following MINIMUM software levels: - IBM Tivoli Storage Manager API 5.1.5 The API is deliverd in the BA client package. Before scheduling the back-ups, I would recommend making one session from the GUI, to see if the communication between the TDP is working. Regards, Karel Bos Customer Unit Nuon
Re: need help with ms-exchange 2003 cluster backups
Thanks, Del -- I feel a bit better now. I'll have the guys look at the tdpexch.log and see if there's any indication of the process trying to start and then quitting without attempting to contact the tsm server (or reporting it can't FIND the tsm server). One note, which I think I mentioned up front -- this is an active/active cluster, with both sides running at all times with half the workload each. In the event of a failure, either side will fail over to the other which will run both info-stores. All set up by a pair of Dell consultants with a fair bit of experience under their belts. Now they're off to the next project and our people are trying to remember what they were told and figure out what the forgot to ask about (there are other alligators in this swamp they're working with). And, in all fairness, I've had the same results with AIX consultants and my memory. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Monday, June 14, 2004 12:27 PM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, This isn't the problem. Data Protection for Exchange automatically ships and installs the TSM API. You do not need to install the TSM BA client unless you decide to the use the TSM BA client scheduler. Please refer to my previous append to get more details about the problem. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/14/2004 01:17:51 PM: Drat! I missed that! . . . What is fascinating is that the backups can be run by hand and look like they're working correctly . . . We'll drop the API on and see if anything changes. Thanks. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, June 14, 2004 10:42 AM To: [EMAIL PROTECTED] Subject: Re: need help with ms-exchange 2003 cluster backups Tom, From the looks of it, only the TDP is installed. In the readme it is stated that: Software Requirements - Data Protection for Microsoft Exchange version 5.2.1 requires the following MINIMUM software levels: - IBM Tivoli Storage Manager API 5.1.5 The API is deliverd in the BA client package. Before scheduling the back-ups, I would recommend making one session from the GUI, to see if the communication between the TDP is working. Regards, Karel Bos Customer Unit Nuon
Exchange 2003 Public Folders
Is there a way to restore public folders on exchange 2003 using TDP 5.1.x Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. **
Re: Exchange 2003 Public Folders
Mehdi, You need to have Data Protection for Exchange version 5.2.1 in order to back up and restore Exchange 2003. With Data Protection for Exchange version 5.2.1 you can back up and restore at the database level. And so, you would restore the Public Folder Store database in order to restore the public folders appearing within that database. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/27/2004 10:28:07 AM: Is there a way to restore public folders on exchange 2003 using TDP 5.1.x
Re: Exchange 2003 Public Folders
Thanks Del, But we are getting this error when restoring the public folder ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. Background. We are trying to restore from EX04 onto EX03 by changing the DSM.OPT file on EX04\TDP to point to EX03 -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 10:54 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Public Folders Mehdi, You need to have Data Protection for Exchange version 5.2.1 in order to back up and restore Exchange 2003. With Data Protection for Exchange version 5.2.1 you can back up and restore at the database level. And so, you would restore the Public Folder Store database in order to restore the public folders appearing within that database. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/27/2004 10:28:07 AM: Is there a way to restore public folders on exchange 2003 using TDP 5.1.x ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. **
Re: Exchange 2003 Public Folders
Mehdi, You need to create the storage group and database with the exact same names on the target Exchange server first. After you create the storage group and database on the target server, you need to set the following option on the new database on the target machine using the database: Properties -- Database Tab: This database can be overwritten by a restore This is done via Exchange System Manager. Then, perform your restore. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/27/2004 11:03:51 AM: Thanks Del, But we are getting this error when restoring the public folder ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. Background. We are trying to restore from EX04 onto EX03 by changing the DSM.OPT file on EX04\TDP to point to EX03
Re: Exchange 2003 Public Folders
I believe that due to the intrigration of Exchange with AD you can no longer (starting at Exchange 2000) recovery information from one Exchange server to another by changing the dsm.opt file. With Exchange 2000 you had to bring up the server on an isolated netowrk. With Exchange 2003 you have the abililty to use a restore storage group. There is a section called Exchange 2003 Recovery Storage Group in the Data Protection for Microsoft Exchange Server Installation and User's Guide. It can be found at: http://publib.boulder.ibm.com/tividd/td/StorageManagerforMail5.2.1.html. Also the Microsoft KB has a lot of information on this topic as well. Amini, Mehdi [EMAIL PROTECTED] wrote: Thanks Del, But we are getting this error when restoring the public folder ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. Background. We are trying to restore from EX04 onto EX03 by changing the DSM.OPT file on EX04\TDP to point to EX03 -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 10:54 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Public Folders Mehdi, You need to have Data Protection for Exchange version 5.2.1 in order to back up and restore Exchange 2003. With Data Protection for Exchange version 5.2.1 you can back up and restore at the database level. And so, you would restore the Public Folder Store database in order to restore the public folders appearing within that database. Thanks, Del ADSM: Dist Stor Manager wrote on 02/27/2004 10:28:07 AM: Is there a way to restore public folders on exchange 2003 using TDP 5.1.x ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** - Do you Yahoo!? Get better spam protection with Yahoo! Mail
Re: Exchange 2003 Public Folders
In regards to this response... Mehdi was asking about Public Folders. You mentioned the Recovery Storage Group as a solution. The Recovery Storage Group only works with Mailbox databases. It does not work with Public Folder databases. Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/27/2004 12:56:34 PM: I believe that due to the intrigration of Exchange with AD you can no longer (starting at Exchange 2000) recovery information from one Exchange server to another by changing the dsm.opt file. With Exchange 2000 you had to bring up the server on an isolated netowrk. With Exchange 2003 you have the abililty to use a restore storage group. There is a section called Exchange 2003 Recovery Storage Group in the Data Protection for Microsoft Exchange Server Installation and User's Guide. It can be found at: http://publib.boulder.ibm. com/tividd/td/StorageManagerforMail5.2.1.html. Also the Microsoft KB has a lot of information on this topic as well.
Exchange 2003
Has anyone restored Exchange 2003...Is there any documentations? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. **
Re: Exchange 2003
Mehdi, Data Protection for Exchange version 5.2.1 will back up and restore Exchange 2003 databases. Exchange 2003 backup and restore is very similar to Exchange 2000 backup and restore. The only difference is when you have an Exchange 2003 Recovery Storage Group. Here is the Data Protection for Exchange User's Guide for version 5.2.1. It will explain how to use Data Protection for Exchange with the Exchange 2003 Recovery Storage Group: http://publib.boulder.ibm.com/tividd/td/StorageManagerforMail5.2.1.html Here is the a Microsoft document that explains this from the Microsoft Exchange Server angle. This document provides information on how to determine if a recovery storage group is useful in your deployment, how to set up a recovery storage group, and how to troubleshoot common problems. http://www.microsoft.com/downloads/details.aspx?FamilyID=df144af6-bee5-4b35-866a-557e25fe2ba1displaylang=en Thanks, Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 02/20/2004 09:43:15 AM: Has anyone restored Exchange 2003...Is there any documentations? Thanks Mehdi Amini
Exchange 2003 backup fails - ANR4993 RC=418
Hi All, Anybody has solution to following error :- TSMSERVER - 5.1.6.5 on AIX 5.1 ML4 TDP for Exchange - 5.2.1 Exchange 2003 on Windows 2003 TSM BA Client and API - 5.1.6 BUFFers 3 BUFFERSIze 1024 Store size 13GB When Exchange backup is started it work till about 1.5 GB data is transferred and then on client it says waiting for TSM server and on server q sess state shows RecvW and wait time keep on increasing. (This backup was working fine earlier) After some time gets following errors in activity log ANR4993 RC=418 In tdpexec.log ANS1017E (RC-50) Session rejected: TCP/IP connection failure In dsierror.log 10/18/2003 02:18:43 sessSendVerb: Error sending Verb, rc: -50 Regards Rane
Exchange 2003 and TDP 5.2.1 issue
Hi, I have an exchange 2003 cluster. We have had (for two or three weeks) no backup issues (or restore for that matter) with this system. As far as I can tell, the only change that happened between the last successful backup and today is the cluster was failed to the other node. I can do a tdpexcc query exchange with no problems. I cannot do a tdpexcc query tsm ... . I get the happy answer ACN0004E Unknown error. The good node is still good (ie. it will do the query tsm process just fine, so there is nothing wrong with the node definition). The files are exactly the same on both nodes (I copied them this morning just in case). Any ideas? Additionally, the rest of the backups (ie. file level backups of the nodes and cluster disks) work fine. Michael Wheelock Integris Healh This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Exchange 2003 and TDP 5.2.1 issue
Michael, There is not much to go on here... but since the TDPEXCC QUERY TSM command uses the TSM API, it appears as if there may be a possible problem with the TSM API installation or pathing. Take a look at the DSIERROR.LOG file. If it does not give you any ideas on what is wrong, your best bet is to call IBM Support so some traces can be looked at to find out exactly where the problem is occuring. Thanks, Del I have an exchange 2003 cluster. We have had (for two or three weeks) no backup issues (or restore for that matter) with this system. As far as I can tell, the only change that happened between the last successful backup and today is the cluster was failed to the other node. I can do a tdpexcc query exchange with no problems. I cannot do a tdpexcc query tsm ... . I get the happy answer ACN0004E Unknown error. The good node is still good (ie. it will do the query tsm process just fine, so there is nothing wrong with the node definition). The files are exactly the same on both nodes (I copied them this morning just in case). Any ideas? Additionally, the rest of the backups (ie. file level backups of the nodes and cluster disks) work fine.
Re: Exchange 2003 and TDP 5.2.1 issue
Hi, On a whim (and figuring hey, its windows) I ran setup again for the TDP for Exchange. I selected the repair option and whammo...it works again. Wowweird. Michael -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2003 10:06 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 and TDP 5.2.1 issue Michael, There is not much to go on here... but since the TDPEXCC QUERY TSM command uses the TSM API, it appears as if there may be a possible problem with the TSM API installation or pathing. Take a look at the DSIERROR.LOG file. If it does not give you any ideas on what is wrong, your best bet is to call IBM Support so some traces can be looked at to find out exactly where the problem is occuring. Thanks, Del I have an exchange 2003 cluster. We have had (for two or three weeks) no backup issues (or restore for that matter) with this system. As far as I can tell, the only change that happened between the last successful backup and today is the cluster was failed to the other node. I can do a tdpexcc query exchange with no problems. I cannot do a tdpexcc query tsm ... . I get the happy answer ACN0004E Unknown error. The good node is still good (ie. it will do the query tsm process just fine, so there is nothing wrong with the node definition). The files are exactly the same on both nodes (I copied them this morning just in case). Any ideas? Additionally, the rest of the backups (ie. file level backups of the nodes and cluster disks) work fine. This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Exchange 2003
Can you send me the link to download this. Thanks -Original Message- From: Wheelock, Michael D [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Hi, TSM supports Exchange 2003 as of TDP Mail for Exchange 5.2.1 which is avaiable electronically (I haven't gotten my cd yet). We have it installed, and have tested everything short of a complete disaster recovery. Michael Wheelock Integris Health of Oklahoma -Original Message- From: Mark Mooney [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Exchange 2003
Hi, I downloaded it via passport advantage over a month ago, but I bet it is on ftp.boulder.ibm.com under /storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntexch /v521/nt the english version is IP22698.exe. Michael -Original Message- From: Amini, Mehdi [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 8:59 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Can you send me the link to download this. Thanks -Original Message- From: Wheelock, Michael D [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Hi, TSM supports Exchange 2003 as of TDP Mail for Exchange 5.2.1 which is avaiable electronically (I haven't gotten my cd yet). We have it installed, and have tested everything short of a complete disaster recovery. Michael Wheelock Integris Health of Oklahoma -Original Message- From: Mark Mooney [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Exchange 2003
Hi Mehdi! You can download Dp for Exchange 5.2.1 at ftp://ftp.storsys.ibm.com/tivoli-storage-management/maintenance/tivoli-data- protection/ntexch/v521/nt/ but I doubt you will not be able to use it. The last time I tried it wasn't working because you need the license file (I believe it's called exchange.lic) and it wasn't installed. When I installed the software from CD it was, so it's probably not included in the download version... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Amini, Mehdi [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 15:59 To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Can you send me the link to download this. Thanks -Original Message- From: Wheelock, Michael D [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Hi, TSM supports Exchange 2003 as of TDP Mail for Exchange 5.2.1 which is avaiable electronically (I haven't gotten my cd yet). We have it installed, and have tested everything short of a complete disaster recovery. Michael Wheelock Integris Health of Oklahoma -Original Message- From: Mark Mooney [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Exchange 2003
Thanks -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 10:17 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Hi Mehdi! You can download Dp for Exchange 5.2.1 at ftp://ftp.storsys.ibm.com/tivoli-storage-management/maintenance/tivoli-data- protection/ntexch/v521/nt/ but I doubt you will not be able to use it. The last time I tried it wasn't working because you need the license file (I believe it's called exchange.lic) and it wasn't installed. When I installed the software from CD it was, so it's probably not included in the download version... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Amini, Mehdi [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 15:59 To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Can you send me the link to download this. Thanks -Original Message- From: Wheelock, Michael D [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Hi, TSM supports Exchange 2003 as of TDP Mail for Exchange 5.2.1 which is avaiable electronically (I haven't gotten my cd yet). We have it installed, and have tested everything short of a complete disaster recovery. Michael Wheelock Integris Health of Oklahoma -Original Message- From: Mark Mooney [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Exchange 2003
Mehdi, If you have a paid PD of a previous version 2.2 or 5.1.5, you can install it first... so that you get the paid license on your machine.. then install the 5.2.1 PTF package over the top of it. That will work. You will then be able to back up your Exchange 2003 server. Thanks, Del You can download Dp for Exchange 5.2.1 at ftp://ftp.storsys.ibm.com/tivoli-storage-management/maintenance/tivoli-data- protection/ntexch/v521/nt/ but I doubt you will not be able to use it. The last time I tried it wasn't working because you need the license file (I believe it's called exchange.lic) and it wasn't installed. When I installed the software from CD it was, so it's probably not included in the download version...
Re: Exchange 2003
Michael, Thanks for that, I installed it on out exchange 2003/server 2003 box and it worked great. Mooney -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Thursday, November 06, 2003 08:59 To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Can you send me the link to download this. Thanks -Original Message- From: Wheelock, Michael D [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 11:04 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Hi, TSM supports Exchange 2003 as of TDP Mail for Exchange 5.2.1 which is avaiable electronically (I haven't gotten my cd yet). We have it installed, and have tested everything short of a complete disaster recovery. Michael Wheelock Integris Health of Oklahoma -Original Message- From: Mark Mooney [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Exchange 2003
Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. **
Re: Exchange 2003
Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. **
Re: Exchange 2003
It will, if you use the correct TDP version: Software Requirements - Data Protection for Microsoft Exchange version 5.2.1 requires the following MINIMUM software levels: - Microsoft Windows NT Server SP5 Microsoft Windows 2000 Server SP3 Microsoft Windows Server 2003 - Microsoft Exchange Server 5.5 SP3 Microsoft Exchange 2000 Server SP2 Microsoft Exchange 2003 Server - IBM Tivoli Storage Manager API 5.1.5 - IBM Tivoli Storage Manager Server 5.1 IBM Tivoli Storage Manager Server does not have to be on the same machine as Data Protection for Exchange and may be on any platform supported by IBM Tivoli Storage Manager Server. - IBM Tivoli Storage Manager Backup-Archive Client 5.1 Required only if the central scheduler service of the IBM Tivoli Storage Manager Backup-Archive Client will be used. If so, the Backup-Archive Client must reside on the same machine as Data Protection for Exchange. - Microsoft Internet Explorer V4.01 The Online Information (User's Guide, and links to Web sites) requires this support. For the web links to work in Online Information, Internet Explorer needs to be configured to access the Internet. -Oorspronkelijk bericht- Van: Amini, Mehdi [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 16:33 Aan: [EMAIL PROTECTED] Onderwerp: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. **
Re: Exchange 2003
Hi, TSM supports Exchange 2003 as of TDP Mail for Exchange 5.2.1 which is avaiable electronically (I haven't gotten my cd yet). We have it installed, and have tested everything short of a complete disaster recovery. Michael Wheelock Integris Health of Oklahoma -Original Message- From: Mark Mooney [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 Does TSM support Exchange 2003 yet? Thanks Mehdi Amini LAN/WAN Engineer ValueOptions 12369 Sunrise Valley Drive Suite C Reston, VA 20191 Phone: 703-390-6855 Fax: 703-390-2581 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
TSM TDP for Exchange 2003
Hi, I realize that exchange 2003 isn't released yet, but my manager has been asking when TSM TDP for Mail will support 2003. Anyone seen a roadmap lately that has this on it? Thanks in advance. Michael Wheelock Integris Health of Oklahoma This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: TSM TDP for Exchange 2003
I realize that exchange 2003 isn't released yet, but my manager has been asking when TSM TDP for Mail will support 2003. Anyone seen a roadmap lately that has this on it? Thanks in advance. See Del Hoobler's 5/28 08:27 posting on that question.
Exchange 2003 + TSM for Exchange 5.1.5
Hello Has anyone tried TSM for Exchange together with Exchange 2003? Does it work? Mvh Niklas Lundström Swedbank
Re: Exchange 2003 + TSM for Exchange 5.1.5
From: Niklas Lundstrom Has anyone tried TSM for Exchange together with Exchange 2003? Does it work? Well, seeing that Exchange 2003's gold code isn't scheduled for release until 4Q2003, I'd have to venture that no has. (Beta code doesn't count, since it is subject to change.) -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Exchange 2003 + TSM for Exchange 5.1.5
Has anyone tried TSM for Exchange together with Exchange 2003? Does it work? Niklas, We are working on Exchange 2003 support right now. Look for Data Protection for Exchange to support Exchange 2003 somewhere in the timeframe when it is officially released from Microsoft or soon after. As far as DP for Exchange 5.1.5 working with Exchange 2003... Microsoft changed a registry entry that causes 5.1.5 to fail. If you manage to modify the registry to fix that, there will be problem if you have a Recovery Storage Group enabled. The best thing will be to wait for the official support. Thanks, Del
