Re: LTO5 Tuning
Hello Steve, what is the actual distance on the path to the tape drives? Can you ask your SAN team how many buffer credits are configured on the switch ports? It seems from your statement "76 km distance" that it might be a long distance connection. Make sure you have enought buffer credits on the long distance links to keep the whole length of the wire "populated". Also, if its a long distance connection, is this purely FC or is there some kind of FC-to-whatever equipment inbetween which might attribute to the high latency? On the fcs* devices what is your setting for the "max_xfer_size" attribute? Best regards, Frank Fegert On Fri, Oct 31, 2014 at 12:24:53PM +1100, Steven Harris wrote: > Thanks for your interest Mike. The san guy tells me it's 380 microseconds > which equates to 76 km distance. > > Regards > > Steve > On 30 Oct 2014 23:50, "Ryder, Michael S" wrote: > > > Steve: > > > > What is the latency on your intersite connection? > > > > Best regards, > > > > Mike, x7942 > > RMD IT Client Services > > > > On Thu, Oct 30, 2014 at 8:35 AM, Steven Harris > > wrote: > > > > > Hi All > > > > > > I have a TSM 6.3.4 server on newish P7 hardware and AIX V7.1. HBAs are > > > all 8Gb. The sans behind it are 8Gb or 4Gb depending which path they > > > take as we are in the middle of a SAN upgrade and there is still an old > > > switch in the mix. > > > > > > Disk is XIV behind SVC. Tape is TS3500 and LTO5. > > > > > > According to the LTO wikipedia entry I should be able to get 140MB/sec > > > raw out of the drive. I have an internal company document that suggests > > > sustained 210MB/sec (compressed) is attainable in the real world. > > > > > > So far my server backs up 500GB per night of DB2 and Oracle databases on > > > to file pools, without deduplication. Housekeeping then does a > > > single-streamed simultaneous migrate and copy to onsite and offsite > > > tapes. Inter site bandwidth is 4Gb and I have most of that to myself. > > > > > > That process takes over 5 hours so I'm seeing less than 100MB/sec. > > > > > > Accordingly I started a tuning exercise. I copied 50GB of my filepool > > > twice to give me a test dataset and started testing, of course when > > > there was no other activity on the TSM box. > > > > > > The data comes off disk at 500MB/sec to /dev/null, so that is not a > > > bottleneck. > > > > > > Copying using dd to tape runs at a peak of 120MB/sec with periods of > > > much lower than that, as measured using nmon's fc stats on the HBAs. I > > > presume some of that slowdown is where the tape reaches its end and has > > > to reverse direction. > > > > > > Elapsed time for 100GB is 18 min, with little variation so average speed > > > is 95MB/sec > > > > > > dd ibs and obs values were varied and ibs=256K obs=1024K seems to give > > > the best result. > > > > > > Elapsed time is very consistent. > > > > > > Copying to a local drive on the same switch blade as the tape HBA or > > > copying across blades made no difference. > > > > > > Copying to a drive at the remote site increased elapsed time by 2 > > > minutes, as one would expect with more switches in the path and a longer > > > turnaround time. > > > > > > Tape to tape copy was not noticeably different to disk to tape. > > > > > > Reading from tape to /dev/null was no different. > > > > > > In all cases CPU time was about half of the elapsed time. > > > > > > lsattr on the drives shows that compression is on (this is also the > > > default) > > > > > > The tape FC adapters are set to use the large transfer size. > > > > > > The test was also run using 64KB pages and svmon was used to verify the > > > setting was effective. Again no difference. > > > > > > I'm running out of ideas here. num_cmd_elements on the hbas is 500 (the > > > default) I'm thinking of increasing that to 2000, but it will require > > > an outage and hence change control. > > > > > > Does anyone have any ideas, references I could look at or practical > > > advice as to how to get this to perform? > > > > > > Thanks > > > > > > Steve > > > > > > Steven Harris > > > TSM Admin > > > Canberra Australia > > > > >
CFP for the 12th TSM Symposium 2015
Call for Papers We are seeking technical contributions in the form of papers and presentations from the TSM user community - the system managers and administrators who are arguably the real TSM experts - and this is an excellent chance to share your knowledge and wisdom. Possible topics / Ideas for a contribution Experiences / Usage Scenarios Protection of virtualized environments Data Protection products for applications (databases, mail, SAP) NDMP Backup and Restore Scenarios Dealing with Growth: HSM, Deduplication, ... DR Strategies in a world of limited backup/restore scenarios Changing Perspectives of Backup/Restore to Data Storage Concepts New Tape and Library Technologies Data Security - Data shredding / Encryption Dealing with the Cloud: CRUD devices and Big Data Backup to the Cloud Technical contributions from TSM solution architects and related storage vendors are also sought: this is an opportunity to demonstrate the flexibility and extensibility of TSM. The conference language will be English. All talks will have to be held in English language. Paper Submission To simplify submission of papers we have generated an appropiate form as PDF document. Please download the form using the link below, fill in all information you can give at this time and send the .pdf file as an Email-attachment to tsm2015 at uni-koeln.de. The overall layout of the symposium requires the length of your presentation to be about 25 or 40 minutes. 5 minutes for Q/A and/or discussion will follow your presentation. Justified exceptions from this schedule are feasible on demand. File Downloads http://tsm2015.uni-koeln.de/uploads/media/Paper_Submission_Form_03.pdf Please use this PDF-form to submit a paper to TSM2015. You may fill it in during multiple sessions with Acrobat-Reader, as you may store it on your local disk in the meantime before finally submitting it as an Email-Attachment. Go ahead and mark your calendar for 22nd to 25th Sep 15! If you still have budget available in 2014 for registering for the TSM Symposium 2015, be happy and keep it for registering. If everything works as planned, the registration will open Mid-November. Keep an eye on http://tsm2015.uni-koeln.de Thanks and best regards, Claus -- Claus Kalle, Universitaet zu Koeln, RRZK i i Leiter Abteilung Systeme I I E-Mail: ka...@uni-koeln.deM M Fon: 0221 470 89581 /I\ Fax: 0221 470 89625 MiMiMiM Snail-Mail: Weyertal 121, 50931 KoelnMIMiMiM
Re: LTO5 Tuning
Steve, is this a TCPIP or FC connection? Mike On Thursday, October 30, 2014, Steven Harris wrote: > Thanks for your interest Mike. The san guy tells me it's 380 microseconds > which equates to 76 km distance. > > Regards > > Steve > On 30 Oct 2014 23:50, "Ryder, Michael S" > wrote: > > > Steve: > > > > What is the latency on your intersite connection? > > > > Best regards, > > > > Mike, x7942 > > RMD IT Client Services > > > > On Thu, Oct 30, 2014 at 8:35 AM, Steven Harris > > > wrote: > > > > > Hi All > > > > > > I have a TSM 6.3.4 server on newish P7 hardware and AIX V7.1. HBAs are > > > all 8Gb. The sans behind it are 8Gb or 4Gb depending which path they > > > take as we are in the middle of a SAN upgrade and there is still an old > > > switch in the mix. > > > > > > Disk is XIV behind SVC. Tape is TS3500 and LTO5. > > > > > > According to the LTO wikipedia entry I should be able to get 140MB/sec > > > raw out of the drive. I have an internal company document that > suggests > > > sustained 210MB/sec (compressed) is attainable in the real world. > > > > > > So far my server backs up 500GB per night of DB2 and Oracle databases > on > > > to file pools, without deduplication. Housekeeping then does a > > > single-streamed simultaneous migrate and copy to onsite and offsite > > > tapes. Inter site bandwidth is 4Gb and I have most of that to myself. > > > > > > That process takes over 5 hours so I'm seeing less than 100MB/sec. > > > > > > Accordingly I started a tuning exercise. I copied 50GB of my filepool > > > twice to give me a test dataset and started testing, of course when > > > there was no other activity on the TSM box. > > > > > > The data comes off disk at 500MB/sec to /dev/null, so that is not a > > > bottleneck. > > > > > > Copying using dd to tape runs at a peak of 120MB/sec with periods of > > > much lower than that, as measured using nmon's fc stats on the HBAs. I > > > presume some of that slowdown is where the tape reaches its end and has > > > to reverse direction. > > > > > > Elapsed time for 100GB is 18 min, with little variation so average > speed > > > is 95MB/sec > > > > > > dd ibs and obs values were varied and ibs=256K obs=1024K seems to give > > > the best result. > > > > > > Elapsed time is very consistent. > > > > > > Copying to a local drive on the same switch blade as the tape HBA or > > > copying across blades made no difference. > > > > > > Copying to a drive at the remote site increased elapsed time by 2 > > > minutes, as one would expect with more switches in the path and a > longer > > > turnaround time. > > > > > > Tape to tape copy was not noticeably different to disk to tape. > > > > > > Reading from tape to /dev/null was no different. > > > > > > In all cases CPU time was about half of the elapsed time. > > > > > > lsattr on the drives shows that compression is on (this is also the > > > default) > > > > > > The tape FC adapters are set to use the large transfer size. > > > > > > The test was also run using 64KB pages and svmon was used to verify the > > > setting was effective. Again no difference. > > > > > > I'm running out of ideas here. num_cmd_elements on the hbas is 500 > (the > > > default) I'm thinking of increasing that to 2000, but it will require > > > an outage and hence change control. > > > > > > Does anyone have any ideas, references I could look at or practical > > > advice as to how to get this to perform? > > > > > > Thanks > > > > > > Steve > > > > > > Steven Harris > > > TSM Admin > > > Canberra Australia > > > > > > -- Best regards, Mike, x7942 RMD IT Client Services
Anyone else doing replica backups of exchange datastores? Need some help please.
I have been trying to get this to work for days now and I don't seem to be making any progress. I have tried all kinds of options in both the dsm.opt and tdpexc.cfg files and I get various messages. The documentation in the TDP for Exchange manual on doing replica backups is not very detailed at all. Our environment looks like this. We have two windows 2008 exchange 2007 servers setup for CCR replication to each other. I am trying to do replica backups on the offline cluster member so it doesn't affect performance on the live cluster member. The TSM server is 6.3.4.300 running on RHEL5 linux. I thought I had it working but nothing was actually backed up. The TSM session was established on the TSM server but no data was actually sent. The sessions appeared to be hung and seemed to eventually timeout. The other message I was receiving on the offline exchange cluster member was Updating mailbox history on TSM Server... Mailbox history has been updated successfully. Querying Exchange Server to gather component information, please wait... ACN5241E The Microsoft Exchange Information Store is currently not running. but from what I was told by our exchange experts is that that service only runs on the active cluster member and not on the offline member. Below are my sanitized dsm.opt and tdpexc.cfg dsm.opt NODename exchange deduplication no CLUSTERnode yes COMPRESSIon Off COMPRESSalwaysOn PASSWORDAccessGenerate resourceutilization 5 COMMMethodTCPip TCPPort 1500 TCPServeraddress tsmserver TCPWindowsize 128 TCPBuffSize 64 diskbuffsize 32 SCHEDMODE Prompted SCHEDLOGRetention 14,d HTTPport 1581 tdpexc.cfg BUFFers 4 BUFFERSIze 8192 clusternode yes compression off compressalways on LOGFile tdpexc.log LOGPrune 60 MOUNTWait Yes TEMPLOGRestorepath P:\TempRestoreLoc LASTPRUNEDate 10/31/2014 06:55:09 BACKUPMETHod LEGACY * BACKUPMETHod vss RETRies 0 LANGuage ENU BACKUPDESTination TSM LOCALDSMAgentnode exchangeofflineclustertsmnodename REMOTEDSMAgentnode exchange TEMPDBRestorepath P:\TempRestoreLoc CLIENTACcessserver Could someone who actually has this working send me their sanitized dsm.opt.tdpexc.cfg and the actual command used to do a replica backup from the offline cluster member?
Re: Monitoring Agent, 2 on a single TSM Server?
I'm building a new reporting server, and need to keep the current, older version, in production for a while. I also need to get data into the new monitoring server so I can test my custom reports and begin collecting historical data for future reporting. That lets me simply disable report delivery schedules on the old system and enable on the new, without a significant issue. I don't need the long term history from the old server, just several days that would be collected on the new system. Sounds like my only option is to put multiple local monitoring agents on the new system. Then, when ready to swing production to the new system, delete the local agents and upgrade the remote agents on the TSM servers. The only issue would be identical naming of the Agent I suppose. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee Miller Sent: Thursday, October 30, 2014 8:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Monitoring Agent, 2 on a single TSM Server? You can do that on AIX and Linux, by installing the code into different directories. You can't however do that on Windows. But what issue are you dealing with between the versions? Lee Miller Tivoli Storage Manager for System Backup and Recovery Development and IBM Tivoli Monitoring for Tivoli Storage Manager Phone: 817-874-7484 From: "Vandeventer, Harold [OITS]" To: ADSM-L@VM.MARIST.EDU Date: 10/30/2014 03:58 PM Subject:[ADSM-L] Monitoring Agent, 2 on a single TSM Server? Sent by:"ADSM: Dist Stor Manager" Is it possible to install two Monitoring Agents on a single TSM server? My hope: leave the current remote agent that pushes data from TSM 6.3.x to the production Monitoring/Reporting/Admin Center server where production reports are produced. But, also install a second Remote Monitoring Agent (related to TSM 7.1.1) on that same TSM 6.3 server and configure it to push data to a new Monitoring/Reporting server. This would let me workout the wrinkles in new reporting and continue to use Remote Agents, not several local agents. Alternative, I suppose: create a second local Agent on the new Monitoring server and in time delete it, when I upgrade the Remote Agent to the new release. Thanks. Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services STE 751-S 910 SW Jackson (785) 296-0631 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: TSM 7.1 usage of volumes for dedupe
I agree. As a wise man once said, "Stupid is as stupid does". In this case, the problem is really a lack of design. Running out of space on the LUN is inevitable, even a first year ComSci student could see that. So, the fact that TSM does not handle it properly is because they did not design a solution. The fact that the admin has to jump through hoops to clear it up once it does happen is a pretty good indication that something is broken. At least, I can remember a time when that is how it would have been viewed and IBM would have agreed. Perhaps I've just been around too long. I'm still willing to "tilt at windmills" once in awhile, so I'll give it a shot when I'm back from my trip and see what happens. Martha On 10/30/2014 5:25 PM, Remco Post wrote: Op 30 okt. 2014, om 22:04 heeft Colwell, William F. het volgende geschreven: Hi Martha, I am glad this was useful to you. I have not reported this as a bug; I expect they would say working-as-designed, try submitting an rfe. I never understood that working as designed is a reason to close a call. If the design is bodged, then it should be fixed. I’ve been told that even TSM is designed by people, and I’m sure sometimes those do make mistakes. - bill -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Martha M McConaghy Sent: Thursday, October 30, 2014 10:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 7.1 usage of volumes for dedupe Bill, I just wanted to let you know how much this information helped. I was able to clear out all the problem volumes and have removed the full LUNs from the devclass until there is enough space on them to be used again. This situation really seems strange to me. Why has TSM not been updated to handle the out of space condition better? If it has a command that shows how much space is left on the LUN, why can't TSM understand it is time to stop allocating volumes on it? Forcing admins to do manual clean up like this just to keep things healthy seems inconsistent with how the rest of TSM functions. Has anyone ever reported this as a bug? Martha On 10/22/2014 2:38 PM, Colwell, William F. wrote: Hi Martha, I see this situation occur when a filesystem gets almost completely full. Do 'q dirsp ' to check for nearly full filesystems. The server doesn't fence off a filesystem like this, instead it keeps hammering on it, allocating new volumes. When it tries to write to a volume and gets an immediate out-of-space error, it marks the volume full so it won't try to use it again. I run this sql to find such volumes and delete them - select 'del v '||cast(volume_name as char(40)), cast(stgpool_name as char(30)), last_write_date - from volumes where upper(status) = 'FULL' and pct_utilized = 0 and pct_reclaim = 0 order by 2, 3 You should remove such filesystems from the devclass directory list until reclaim has emptied them a little bit. Hope his helps, Bill Colwell Draper Lab -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Martha M McConaghy Sent: Wednesday, October 22, 2014 2:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 7.1 usage of volumes for dedupe Interesting. Seems very similar, except the status of these volumes is "FULL", not "EMPTY". However, the %reclaimable space is 0.0. I think this is a bug. I would expect the volume to leave the pool once it is "reclaimed". It would be OK with me if it did not. However, since the status is "FULL", it will never be reused. That seems wrong. If it is going to remain attached to the dedupepool, the status should convert to EMPTY so the file can be reused. Or, go away altogether so the space can be reclaimed and reused. In looking at the filesystem on the Linux side (sorry I didn't mention this is running on RHEL), the file exists on /data0, but with no size: [urmm@tsmserver data0]$ ls -l *d57* -rw--- 1 tsminst1 tsmsrvrs 0 Oct 10 20:22 0d57.bfs /data0 is 100% utilized, so this file can never grow. Seems like it should get cleaned up rather than continue to exist. Martha On 10/22/2014 1:58 PM, Erwann SIMON wrote: hi Martha, See if this can apply : www-01.ibm.com/support/docview.wss?uid=swg21685554 Note that I had a situation where Q CONT returned that the volume was empty but it wasn't in reality since it was impossible to delete it (without discrading data). A select statement against the contents showed some files. Unforunately, I don't know how this story finished... -- Martha McConaghy Marist: System Architect/Technical Lead SHARE: Director of Operations Marist College IT Poughkeepsie, NY 12601 Notice: This email and any attachments may contain proprietary (Draper non-public) and/or export-controlled information of Draper Laboratory. If you are not the intended recipient of this email, please immediately notify the sender by replying to this email and immediately d
Re: Anyone else doing replica backups of exchange datastores? Need some help please.
Hi John, This looks like a configuration issue to me. Exchange Server 2007 CCR and LCR replica copies can be backed up and restored by using the VSS method only. Microsoft does not allow Legacy backups of Exchange Server 2007 CCR and LCR replica copies. Also keep in mind, all VSS Restores of a CCR or LCR replica can be restored only into the running instance of a storage group (primary, recovery, or alternate). Microsoft does not support VSS Restores into a replica instance. If you want to back up from the replica copy when running in a CCR or LCR environment, specify the "FromReplica True" backup option in the Protect tab of the MMC GUI. You can also specify the /fromreplica parameter with the tdpexcc backup command on the command-line interface. Here is the important one... For CCR copies, you must run the backup while logged on to the secondary node of the cluster that currently contains the replica copy and you must use the "FROMREPLICA" option. Here are a few more things: http://www-01.ibm.com/support/knowledgecenter/SSTG2D_6.4.0/com.ibm.itsm.mail.exc.doc/c_dpfcm_bup_replica_exc.html?cp=SSTG2D_6.4.0&lang=en If you are not able to get this working, you should open a PMR so that the service team can help you get the configuration working. Del "ADSM: Dist Stor Manager" wrote on 10/31/2014 08:40:00 AM: > From: "Dury, John C." > To: ADSM-L@VM.MARIST.EDU > Date: 10/31/2014 08:42 AM > Subject: Anyone else doing replica backups of exchange datastores? > Need some help please. > Sent by: "ADSM: Dist Stor Manager" > > I have been trying to get this to work for days now and I don't seem > to be making any progress. I have tried all kinds of options in both > the dsm.opt and tdpexc.cfg files and I get various messages. The > documentation in the TDP for Exchange manual on doing replica > backups is not very detailed at all. > Our environment looks like this. > We have two windows 2008 exchange 2007 servers setup for CCR > replication to each other. I am trying to do replica backups on the > offline cluster member so it doesn't affect performance on the live > cluster member. > The TSM server is 6.3.4.300 running on RHEL5 linux. > I thought I had it working but nothing was actually backed up. The > TSM session was established on the TSM server but no data was > actually sent. The sessions appeared to be hung and seemed to > eventually timeout. > The other message I was receiving on the offline exchange cluster member was > Updating mailbox history on TSM Server... > Mailbox history has been updated successfully. > > Querying Exchange Server to gather component information, please wait... > > ACN5241E The Microsoft Exchange Information Store is currently not running. > but from what I was told by our exchange experts is that that > service only runs on the active cluster member and not on the offline member. > Below are my sanitized dsm.opt and tdpexc.cfg > dsm.opt > NODename exchange > deduplication no > CLUSTERnode yes > COMPRESSIon Off > COMPRESSalwaysOn > PASSWORDAccessGenerate > resourceutilization 5 > COMMMethodTCPip > TCPPort 1500 > TCPServeraddress tsmserver > TCPWindowsize 128 > TCPBuffSize 64 > diskbuffsize 32 > SCHEDMODE Prompted > SCHEDLOGRetention 14,d > HTTPport 1581 > tdpexc.cfg > BUFFers 4 > BUFFERSIze 8192 > clusternode yes > compression off > compressalways on > LOGFile tdpexc.log > LOGPrune 60 > MOUNTWait Yes > TEMPLOGRestorepath P:\TempRestoreLoc > LASTPRUNEDate 10/31/2014 06:55:09 > BACKUPMETHod LEGACY > * BACKUPMETHod vss > RETRies 0 > LANGuage ENU > BACKUPDESTination TSM > LOCALDSMAgentnode exchangeofflineclustertsmnodename > REMOTEDSMAgentnode exchange > TEMPDBRestorepath P:\TempRestoreLoc > CLIENTACcessserver > > Could someone who actually has this working send me their sanitized > dsm.opt.tdpexc.cfg and the actual command used to do a replica backup from the > offline cluster member? >
Re: Anyone else doing replica backups of exchange datastores? Need some help please.
Thanks for the reply. I agree that it sounds like a configuration issue. We are trying to do this via command line so it can be scripted and therefore automated. I do have a problem open with IBM and sent them some logs and lots of information but their first was response was to tell me that it wasn't configured correctly as they were looking at early entries in the logs I sent them instead of further down. Lesson learned, delete all of your logs before recreating problem as support won't look at timestamps and first error they see must be the problem. The command line I am using looks like this: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup incr /fromreplica /backupmethod=vss /backupdestination=tsm /tsmoptfile="c:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt" I was getting it to create a TSM session but the session would just be WAITING on the server for hours and never actually did anything. FWIW, the datastore I am testing with is tiny. Now when I try running the backup on the inactive CCR replica I get: Updating mailbox history on TSM Server... Mailbox history has been updated successfully. Querying Exchange Server to gather component information, please wait... ACN5241E The Microsoft Exchange Information Store is currently not running. but as I mentioned before, according to my exchange admins, that service should never be running on both sides of the CCR cluster. I have changed the dsm.opt and tdpexc.cfg options so many times with every option can think of which is why I was hoping someone had a sanitized version of their dsm.opt and tdpexc.cfg that are working in their environment I could look at. Hi John, This looks like a configuration issue to me. Exchange Server 2007 CCR and LCR replica copies can be backed up and restored by using the VSS method only. Microsoft does not allow Legacy backups of Exchange Server 2007 CCR and LCR replica copies. Also keep in mind, all VSS Restores of a CCR or LCR replica can be restored only into the running instance of a storage group (primary, recovery, or alternate). Microsoft does not support VSS Restores into a replica instance. If you want to back up from the replica copy when running in a CCR or LCR environment, specify the "FromReplica True" backup option in the Protect tab of the MMC GUI. You can also specify the /fromreplica parameter with the tdpexcc backup command on the command-line interface. Here is the important one... For CCR copies, you must run the backup while logged on to the secondary node of the cluster that currently contains the replica copy and you must use the "FROMREPLICA" option. Here are a few more things: http://www-01.ibm.com/support/knowledgecenter/SSTG2D_6.4.0/com.ibm.itsm.mail.exc.doc/c_dpfcm_bup_replica_exc.html?cp=SSTG2D_6.4.0&lang=en If you are not able to get this working, you should open a PMR so that the service team can help you get the configuration working. Del "ADSM: Dist Stor Manager" wrote on 10/31/2014 08:40:00 AM: > From: "Dury, John C." > To: ADSM-L AT VM.MARIST DOT EDU > Date: 10/31/2014 08:42 AM > Subject: Anyone else doing replica backups of exchange datastores? > Need some help please. > Sent by: "ADSM: Dist Stor Manager" > > I have been trying to get this to work for days now and I don't seem > to be making any progress. I have tried all kinds of options in both > the dsm.opt and tdpexc.cfg files and I get various messages. The > documentation in the TDP for Exchange manual on doing replica > backups is not very detailed at all. > Our environment looks like this. > We have two windows 2008 exchange 2007 servers setup for CCR > replication to each other. I am trying to do replica backups on the > offline cluster member so it doesn't affect performance on the live > cluster member. > The TSM server is 6.3.4.300 running on RHEL5 linux. > I thought I had it working but nothing was actually backed up. The > TSM session was established on the TSM server but no data was > actually sent. The sessions appeared to be hung and seemed to > eventually timeout. > The other message I was receiving on the offline exchange cluster member was > Updating mailbox history on TSM Server... > Mailbox history has been updated successfully. > > Querying Exchange Server to gather component information, please wait... > > ACN5241E The Microsoft Exchange Information Store is currently not running. > but from what I was told by our exchange experts is that that > service only runs on the active cluster member and not on the offline member. > Below are my sanitized dsm.opt and tdpexc.cfg > dsm.opt > NODename exchange > deduplication no > CLUSTERnode yes > COMPRESSIon Off > COMPRESSalways On > PASSWORDAccess Generate > resourceutilization 5 > COMMMethod TCPip > TCPPort 1500 > TCPServeraddress tsmserver > TCPWindowsize 128 > TCPBuffSize 64 > diskbuffsize 32 > SCHEDMODE Prompted > SCHEDLOGRetention 14,d > HTTPport 1
Re: Anyone else doing replica backups of exchange datastores? Need some help please.
Hi John, You can't run a backup of a replica from the primary server. You must be running that command on the passive server. The Microsoft Exchange Replica Writer will be running on the passive server. That is the machine you need to have DP/Exchange and the Windows BA Client installed and configured on. Also keep in mind that it's the DSMAGENT (Windows BA Client) is the node that actually sends the data to the TSM Server. It uses the proxy capability to store the data on behalf of the DP/Exchange node. The service team can assist you through this. Thank you, Del "ADSM: Dist Stor Manager" wrote on 10/31/2014 02:47:25 PM: > From: "Dury, John C." > To: ADSM-L@VM.MARIST.EDU > Date: 10/31/2014 02:49 PM > Subject: Re: Anyone else doing replica backups of exchange > datastores? Need some help please. > Sent by: "ADSM: Dist Stor Manager" > > Thanks for the reply. I agree that it sounds like a configuration > issue. We are trying to do this via command line so it can be > scripted and therefore automated. I do have a problem open with IBM > and sent them some logs and lots of information but their first was > response was to tell me that it wasn't configured correctly as they > were looking at early entries in the logs I sent them instead of > further down. Lesson learned, delete all of your logs before > recreating problem as support won't look at timestamps and first > error they see must be the problem. The command line I am > using looks like this: > C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup > incr /fromreplica /backupmethod=vss /backupdestination=tsm / > tsmoptfile="c:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt" > I was getting it to create a TSM session but the session would just > be WAITING on the server for hours and never actually did anything. > FWIW, the datastore I am testing with is tiny. > Now when I try running the backup on the inactive CCR replica I get: > Updating mailbox history on TSM Server... > Mailbox history has been updated successfully. > Querying Exchange Server to gather component information, please wait... > ACN5241E The Microsoft Exchange Information Store is currently not running. > but as I mentioned before, according to my exchange admins, that > service should never be running on both sides of the CCR cluster. > I have changed the dsm.opt and tdpexc.cfg options so many times with > every option can think of which is why I was hoping someone had a > sanitized version of their dsm.opt and tdpexc.cfg that are working > in their environment I could look at. >
