Re: Rebinding Exchange Backups
Hi Steve, Yes, the older backups matching the specification should get rebound. Del "ADSM: Dist Stor Manager" wrote on 11/11/2016 12:26:28 AM: > From: Steven Harris > To: ADSM-L@VM.MARIST.EDU > Date: 11/11/2016 12:27 AM > Subject: Rebinding Exchange Backups > Sent by: "ADSM: Dist Stor Manager" > > Hi guys > > I have some exchange backups that were bound to the wrong management class > because of incorrect VSSPOLICY statements. > > Will correcting the VSSPOLICY statements cause the old backups to be > rebound? > > Thanks > > Steve > > Steven Harr > TSM Admin,Canberra Australia > > Hit me up with any consulting queries you may have,,, I cant charge you for > them while I'm pn my current contract, but can look at them for free, >
Rebinding Exchange Backups
Hi guys I have some exchange backups that were bound to the wrong management class because of incorrect VSSPOLICY statements. Will correcting the VSSPOLICY statements cause the old backups to be rebound? Thanks Steve Steven Harr TSM Admin,Canberra Australia Hit me up with any consulting queries you may have,,, I cant charge you for them while I'm pn my current contract, but can look at them for free,
Re: Exchange backups
Hi Geoff, Ray and Wanda are correct. (See their answers.) As for the "Platform" changing... it has to do with the fact the scheduler connects as the "TDP" node and changes it to "WinNT" and then DP/Exchange connects and changes it to "TDP MSExchg". This is a known issue which is on the list to resolve. Thank you, Del "ADSM: Dist Stor Manager" wrote on 05/14/2014 10:53:58 AM: > From: Geoff Gill > To: ADSM-L@vm.marist.edu, > Date: 05/14/2014 10:56 AM > Subject: Exchange backups > Sent by: "ADSM: Dist Stor Manager" > > > > Looking for some Exchange knowledge. Last week admin ID's for nodes > were being removed and it was discovered 2 days later that this > broke the Exchange backups. Once they were put back backups started > working again but what confuses me is when comparing 2 different > sites things seems to work differently as it relates to Exchange. > > I have no access to the client side, only the TSM server, so I can't > relay anything except what I see here. At one site the nodes are set > up just like any other node it looks like. Licensing shows 2 > Exchange TDP in use but when looking at q no the platform shows > WinNt. These nodes do NOT have an associated admin ID that I can > find and backups work just fine. Why things report the way they do I > don't understand. > > The second site licensing shows 6 Exchange TDP in use and q no on > these show the Platform as TDP MSExchg. These nodes are also > configured with Proxynode Agents too whereas the first site is not. > Why this I don't understand either. Since I don't know much about > Exchange backups in general I would have assumed based on the first > site this would be the normal way they would be set up. > > This second site is the one that Exchange backups stopped working > when the Admin ID's were deleted. I put everything back and backups > work now but when looking at the admin ID's it seems as though only > one of them shows Days Since Last Access 1 so I don't know if > removing the others would break this again or not. Support told me > these Admin ID's need to be there for Exchange to work but this > doesn't seem to be the case at the site that works where are no > admin ID's there are not associated with an Exchange node. > > Hopefully someone has some explanation for this. > > Thank You > Geoff Gill > >
Re: Exchange backups
Short answer: Yes it's different depending on the version of Exchange and the version of the TDP. Longer answer: With old versions of Exchange and TDP, doing only legacy backups, you only had the TDP client and a TDP scheduler service. Starting with Exchange 2010, you can no longer do Legacy backups, you are *required* to do VSS backups. If you do VSS backups, you have the admin account and dsmcad involved, and dsmcad takes on the function of being the VSS requestor (in addition to its roles as webclient-server-upper and managed-services-scheduler-manager). (It's not going to make sense from the server side, you would have to see how it is installed on the client side to know.) And starting with Exchange 2010, most sites us DAG databases, which is different than storage groups in Exchange 2007. When you do DAG DB's, it is to your advantage to use proxy nodes so that all the filespaces are lodged under one TSM nodename. That prevents you from getting multiple copies of backups when DB's fail back and forth between Exchange servers, which is what 2010-2013 DAGs are designed to do. Also lets you restore any DB to any Exchange server. So stuff changes depending on whether you are using a V5 TDP with Ex 2007 Legacy, V5 TDP with Ex 2007 VSS, V6 TDP with Ex2007 legacy, V6 TDP with EX2007 VSS, EX2010 with VSS ,EX2010 with VSS and DAGs and Proxies Oh My. Some of it is change in the TDP structure, some of it due to change in Exchange structure, some of it due to TDP changes made to handle the new Exchange features. (And I also don't know why sometimes the Exchange TDP reports as MSExchange and sometimes as WinNT. It's annoying and not consistent, and doesn't seem to have a Why). W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Geoff Gill Sent: Wednesday, May 14, 2014 10:54 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Exchange backups Looking for some Exchange knowledge. Last week admin ID's for nodes were being removed and it was discovered 2 days later that this broke the Exchange backups. Once they were put back backups started working again but what confuses me is when comparing 2 different sites things seems to work differently as it relates to Exchange. I have no access to the client side, only the TSM server, so I can't relay anything except what I see here. At one site the nodes are set up just like any other node it looks like. Licensing shows 2 Exchange TDP in use but when looking at q no the platform shows WinNt. These nodes do NOT have an associated admin ID that I can find and backups work just fine. Why things report the way they do I don't understand. The second site licensing shows 6 Exchange TDP in use and q no on these show the Platform as TDP MSExchg. These nodes are also configured with Proxynode Agents too whereas the first site is not. Why this I don't understand either. Since I don't know much about Exchange backups in general I would have assumed based on the first site this would be the normal way they would be set up. This second site is the one that Exchange backups stopped working when the Admin ID's were deleted. I put everything back and backups work now but when looking at the admin ID's it seems as though only one of them shows Days Since Last Access 1 so I don't know if removing the others would break this again or not. Support told me these Admin ID's need to be there for Exchange to work but this doesn't seem to be the case at the site that works where are no admin ID's there are not associated with an Exchange node. Hopefully someone has some explanation for this. Thank You Geoff Gill
Re: Exchange backups
Geoff, I'm not completely clear what is going on with your Exchange backup. However, I would strongly recommend you work with your Exchange admins and the TDP for Exchange client install and configuration document to confirm your backup nodes are configured correctly. You must use a proxy node configuration for Exchange 2010 and Exchange 2013 backups. The TDP for Exchange has minimum version requirements depending on Exchange version and service pack release--I do not recall the specifics. Ray Storer NIBCO INC. 574.295.3457 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Geoff Gill Sent: Wednesday, May 14, 2014 10:54 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Exchange backups Looking for some Exchange knowledge. Last week admin ID's for nodes were being removed and it was discovered 2 days later that this broke the Exchange backups. Once they were put back backups started working again but what confuses me is when comparing 2 different sites things seems to work differently as it relates to Exchange. I have no access to the client side, only the TSM server, so I can't relay anything except what I see here. At one site the nodes are set up just like any other node it looks like. Licensing shows 2 Exchange TDP in use but when looking at q no the platform shows WinNt. These nodes do NOT have an associated admin ID that I can find and backups work just fine. Why things report the way they do I don't understand. The second site licensing shows 6 Exchange TDP in use and q no on these show the Platform as TDP MSExchg. These nodes are also configured with Proxynode Agents too whereas the first site is not. Why this I don't understand either. Since I don't know much about Exchange backups in general I would have assumed based on the first site this would be the normal way they would be set up. This second site is the one that Exchange backups stopped working when the Admin ID's were deleted. I put everything back and backups work now but when looking at the admin ID's it seems as though only one of them shows Days Since Last Access 1 so I don't know if removing the others would break this again or not. Support told me these Admin ID's need to be there for Exchange to work but this doesn't seem to be the case at the site that works where are no admin ID's there are not associated with an Exchange node. Hopefully someone has some explanation for this. Thank You Geoff Gill CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Exchange backups
Looking for some Exchange knowledge. Last week admin ID's for nodes were being removed and it was discovered 2 days later that this broke the Exchange backups. Once they were put back backups started working again but what confuses me is when comparing 2 different sites things seems to work differently as it relates to Exchange. I have no access to the client side, only the TSM server, so I can't relay anything except what I see here. At one site the nodes are set up just like any other node it looks like. Licensing shows 2 Exchange TDP in use but when looking at q no the platform shows WinNt. These nodes do NOT have an associated admin ID that I can find and backups work just fine. Why things report the way they do I don't understand. The second site licensing shows 6 Exchange TDP in use and q no on these show the Platform as TDP MSExchg. These nodes are also configured with Proxynode Agents too whereas the first site is not. Why this I don't understand either. Since I don't know much about Exchange backups in general I would have assumed based on the first site this would be the normal way they would be set up. This second site is the one that Exchange backups stopped working when the Admin ID's were deleted. I put everything back and backups work now but when looking at the admin ID's it seems as though only one of them shows Days Since Last Access 1 so I don't know if removing the others would break this again or not. Support told me these Admin ID's need to be there for Exchange to work but this doesn't seem to be the case at the site that works where are no admin ID's there are not associated with an Exchange node. Hopefully someone has some explanation for this. Thank You Geoff Gill
Re: Exchange backups slow to start sending data
Hi Bill Take a look at this: http://www-01.ibm.com/support/docview.wss?uid=swg21422363 Thanks, Del "ADSM: Dist Stor Manager" wrote on 03/21/2012 12:03:08 PM: > From: Bill Boyer > To: ADSM-L@vm.marist.edu > Date: 03/21/2012 12:06 PM > Subject: Exchange backups slow to start sending data > Sent by: "ADSM: Dist Stor Manager" > > Exchange 2007. The server crashed a couple weeks ago and is now rebuilt and > restored. But since then when the full backups of the databases runs, we see > the ACN3500 full backup is starting, but then it's a long wait before you > see any data. The session on the TSm server show IdleWait. For example just > this morning a full backup of a 33GB database took almost 2-hours. And it > isn't the actual data transmission. Backup of the next database is now in > IdleWait for 51-minutes with no data transferred > > > TSM server is 5.5 on Linux. > > > > Can anybody give us an idea of where/what is causing this excessive wait > time? >
Exchange backups slow to start sending data
Exchange 2007. The server crashed a couple weeks ago and is now rebuilt and restored. But since then when the full backups of the databases runs, we see the ACN3500 full backup is starting, but then it's a long wait before you see any data. The session on the TSm server show IdleWait. For example just this morning a full backup of a 33GB database took almost 2-hours. And it isn't the actual data transmission. Backup of the next database is now in IdleWait for 51-minutes with no data transferred TSM server is 5.5 on Linux. Can anybody give us an idea of where/what is causing this excessive wait time? Bill Boyer DSS, Inc. (610) 927-4407 "Enjoy life. It has an expiration date." - ??
Re: Problem with Exchange backups and logs not being deleted
Many thanks Del, I'll pass this on to our Exchange admin and get them to have a look at their end first ( rather than point the finger at TSM right away! ). Regards Farren -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Del Hoobler Sent: 20 March 2012 10:52 To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Problem with Exchange backups and logs not being deleted Hi Farren DP/Exchange does not actually truncate the logs, the Exchange Server does the actual truncation. When a DP/Exchange backup completes successfully, it will tell the Exchange Server that it has stored the backup and that it can truncate the logs. At that point, the Exchange Server decides on the appropriate time to truncate the logs. I have seen this before. If a reboot does not solve it, you should get Microsoft involved. You are always welcome to open a PMR with IBM too. From my experience, if log truncation has been working, and then stops working, it usually is something in the Exchange Server that is "stuck" and needs attention from Microsoft support. Thanks, Del "ADSM: Dist Stor Manager" wrote on 03/20/2012 04:14:27 AM: > From: "Minns, Farren - Chichester" > To: ADSM-L@vm.marist.edu > Date: 03/20/2012 04:18 AM > Subject: Problem with Exchange backups and logs not being deleted > Sent by: "ADSM: Dist Stor Manager" > > Morning all, > > I'm not that clued up on Exchange so I'm not sure if this is a TSM > or Exchange issue. > > Basically, we have 20 Storage Groups and up until recently backups > have been running fine (have been for years). But just recently I > was alerted to the fact that four of the storage groups > (coincidental all on the same drive), were not having old log files > removed after the backups. So eventually the disk just fills up and > the files have to be manually deleted. > > I can see that weekly full backups and daily incremental are still > running fine. > > Before I get bogged down in trying to figure out exactly what's > wrong, can someone tell me if this is something that the TSM TDP for > exchange should be taking care of? > > Farren John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ.
Re: Problem with Exchange backups and logs not being deleted
Hi Farren DP/Exchange does not actually truncate the logs, the Exchange Server does the actual truncation. When a DP/Exchange backup completes successfully, it will tell the Exchange Server that it has stored the backup and that it can truncate the logs. At that point, the Exchange Server decides on the appropriate time to truncate the logs. I have seen this before. If a reboot does not solve it, you should get Microsoft involved. You are always welcome to open a PMR with IBM too. From my experience, if log truncation has been working, and then stops working, it usually is something in the Exchange Server that is "stuck" and needs attention from Microsoft support. Thanks, Del "ADSM: Dist Stor Manager" wrote on 03/20/2012 04:14:27 AM: > From: "Minns, Farren - Chichester" > To: ADSM-L@vm.marist.edu > Date: 03/20/2012 04:18 AM > Subject: Problem with Exchange backups and logs not being deleted > Sent by: "ADSM: Dist Stor Manager" > > Morning all, > > I'm not that clued up on Exchange so I'm not sure if this is a TSM > or Exchange issue. > > Basically, we have 20 Storage Groups and up until recently backups > have been running fine (have been for years). But just recently I > was alerted to the fact that four of the storage groups > (coincidental all on the same drive), were not having old log files > removed after the backups. So eventually the disk just fills up and > the files have to be manually deleted. > > I can see that weekly full backups and daily incremental are still > running fine. > > Before I get bogged down in trying to figure out exactly what's > wrong, can someone tell me if this is something that the TSM TDP for > exchange should be taking care of? > > Farren
Re: Problem with Exchange backups and logs not being deleted
Hi, This is the copyg related to the Exchange TSM Client. PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data Data ExtraOnly NameName NameExists Deleted Versions Version - - - - --- EXCHANGE ACTIVEDEFMC STANDARD317 30 60 EXCHANGE LIVE DEFMC STANDARD317 30 60 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns, Farren - Chichester Sent: 20 March 2012 08:14 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Problem with Exchange backups and logs not being deleted Morning all, I'm not that clued up on Exchange so I'm not sure if this is a TSM or Exchange issue. Basically, we have 20 Storage Groups and up until recently backups have been running fine (have been for years). But just recently I was alerted to the fact that four of the storage groups (coincidental all on the same drive), were not having old log files removed after the backups. So eventually the disk just fills up and the files have to be manually deleted. I can see that weekly full backups and daily incremental are still running fine. Before I get bogged down in trying to figure out exactly what's wrong, can someone tell me if this is something that the TSM TDP for exchange should be taking care of? Farren John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ. John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ.
Problem with Exchange backups and logs not being deleted
Morning all, I'm not that clued up on Exchange so I'm not sure if this is a TSM or Exchange issue. Basically, we have 20 Storage Groups and up until recently backups have been running fine (have been for years). But just recently I was alerted to the fact that four of the storage groups (coincidental all on the same drive), were not having old log files removed after the backups. So eventually the disk just fills up and the files have to be manually deleted. I can see that weekly full backups and daily incremental are still running fine. Before I get bogged down in trying to figure out exactly what's wrong, can someone tell me if this is something that the TSM TDP for exchange should be taking care of? Farren John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, United Kingdom. PO19 8SQ.
Re: multi-threaded Exchange backups
Steve, Me too -- Dmitry Dukhov Siberia Software SL (Tivoli Storage Manager Software) http://www.s-iberia.com On 28.11.2011 18:00, Schaub, Steve wrote: In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: multi-threaded Exchange backups
Hi Steve, If I'm correct there is a "download" section in ADSM.ORG forum, that could be used for such purposes ... http://adsm.org/forum/downloads.php Cheers. Arnaud ** Corporate IT Systems & Datacenter Responsible Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com ** -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Tuesday, 29 November, 2011 13:23 To: ADSM-L@VM.MARIST.EDU Subject: Re: multi-threaded Exchange backups On that subject, is there a central repository somewhere on this site or elsewhere that we could use to share scripts? I don't mind email, but it doesn't help the person who comes looking for an answer a month from now. -steve schaub -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Tuesday, November 29, 2011 6:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] multi-threaded Exchange backups When a list participant offers a script or other aid, and instructs those interested to contact him or her to obtain a copy, the thing to do is directly email that person at the address they provided for this purpose. This will prevent all the annoying "me too" mails which clutter the inboxes of the 1500 participants of the list, who can do nothing to provide the aid, and save space on the List Server which Marist graciously hosts. Richard Sims - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: multi-threaded Exchange backups
On that subject, is there a central repository somewhere on this site or elsewhere that we could use to share scripts? I don't mind email, but it doesn't help the person who comes looking for an answer a month from now. -steve schaub -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Tuesday, November 29, 2011 6:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] multi-threaded Exchange backups When a list participant offers a script or other aid, and instructs those interested to contact him or her to obtain a copy, the thing to do is directly email that person at the address they provided for this purpose. This will prevent all the annoying "me too" mails which clutter the inboxes of the 1500 participants of the list, who can do nothing to provide the aid, and save space on the List Server which Marist graciously hosts. Richard Sims - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: multi-threaded Exchange backups
When a list participant offers a script or other aid, and instructs those interested to contact him or her to obtain a copy, the thing to do is directly email that person at the address they provided for this purpose. This will prevent all the annoying "me too" mails which clutter the inboxes of the 1500 participants of the list, who can do nothing to provide the aid, and save space on the List Server which Marist graciously hosts. Richard Sims
Re: multi-threaded Exchange backups
Me too pls This E-Mail is sent from My BlackBerry® Handheld Device - Original Message - From: ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU Sent: Tue Nov 29 11:55:51 2011 Subject: Re: [ADSM-L] multi-threaded Exchange backups Me too ! :) Thanks ! -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Howard Coles Envoyé : lundi 28 novembre 2011 21:49 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] multi-threaded Exchange backups I would also be interested. See Ya' Howard Coles Jr. John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Monday, November 28, 2011 8:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. Please consider the environment before printing this e-mail. Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à l’intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et d’en avertir immédiatement l’expéditeur. Internet ne permettant pas de garantir l’intégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message s’il a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (“the email”) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whatsoever is prohibited without Caisse des Depots et Consignations's prior written consent. If you have received this email in error, please delete it without saving a copy and notify the sender immediately. Internet emails are not necessarily secured, and declines responsibility for any changes that may have been made to this email after it was sent. While we take all reasonable precautions to ensure that viruses are not transmitted via emails, we recommend that you take your own measures to prevent viruses from entering your computer system. Disclaimer: The content of this email and any attachments (the “email”) is confidential, may be privileged or propriety, is subject to copyright and is the property of Global Investment House (“Global”). No person, other than the recipient may use or disclose the contents of this email, links or attachments hereto, to any person whatsoever. The information in this email, links or attachments thereto is intended for the attention and use of the addressee only. If you are not the intended addressee/recipient, you are hereby notified that any disclosure, copying or distribution of the contents of this email or the taking of any action in reliance thereon or pursuant thereto, is strictly prohibited. Should you have received this email in error, please delete and destroy it immediately and notify the sender. Unless specifically indicated, this email is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Global. Glob
Re: multi-threaded Exchange backups
Me too ! :) Thanks ! -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Howard Coles Envoyé : lundi 28 novembre 2011 21:49 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] multi-threaded Exchange backups I would also be interested. See Ya' Howard Coles Jr. John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Monday, November 28, 2011 8:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. Please consider the environment before printing this e-mail. Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à l’intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et d’en avertir immédiatement l’expéditeur. Internet ne permettant pas de garantir l’intégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message s’il a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (“the email”) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whatsoever is prohibited without Caisse des Depots et Consignations's prior written consent. If you have received this email in error, please delete it without saving a copy and notify the sender immediately. Internet emails are not necessarily secured, and declines responsibility for any changes that may have been made to this email after it was sent. While we take all reasonable precautions to ensure that viruses are not transmitted via emails, we recommend that you take your own measures to prevent viruses from entering your computer system.
AW: multi-threaded Exchange backups
Hello Steve, we would also appreciate to have a look on that scripts. Thanks in advance Marcus marcus.koeh...@rossmann.de -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Schaub, Steve" Sänt av: "ADSM: Dist Stor Manager" Datum: 11/28/2011 15:07 Ärende: multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: multi-threaded Exchange backups
Would love to see your script Steve. Regards, Stefan On Mon, Nov 28, 2011 at 3:00 PM, Schaub, Steve wrote: > In case anyone is interested, I modified our Powershell script for full > backup of our Exchange databases so that it now backs up multiple > concurrent Storage Groups in a single script (because I'm too darn lazy to > deal with multiple node names, schedules, etc). > > In our case, it dropped elapsed times from 36hr to 11hr, running 4 > concurrent threads. > > If anyone would like a copy, just contact me. > > Steve Schaub > Systems Engineer II, Windows Backup/Recovery > BlueCross BlueShield of Tennessee > steve_schaub "at" bcbst.com > > - > Please see the following link for the BlueCross BlueShield of Tennessee > E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm >
Antwort: [ADSM-L] multi-threaded Exchange backups
Hi, I am interested, too. Mit freundlichen Grüßen / Kind regards Thorsten Burghardt mailto: thorsten.burgha...@bechtle.com Von:"Schaub, Steve" An: ADSM-L@VM.MARIST.EDU Datum: 28.11.11 15:11 Betreff:[ADSM-L] multi-threaded Exchange backups Gesendet von: "ADSM: Dist Stor Manager" In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm + 750 Jahre Knappschaft. Soziale Verantwortung zu jeder Zeit. www.750jahre.info +
Re: multi-threaded Exchange backups
I would also be interested. See Ya' Howard Coles Jr. John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Monday, November 28, 2011 8:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. Please consider the environment before printing this e-mail.
Re: multi-threaded Exchange backups
Me too. Thanks Matthew J. Leonard Network Administrator AtlasAir Worldwide Holdings Network Operations Department matthew.leon...@atlasair.com Office: 914.701.8715 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Monday, November 28, 2011 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: Ang: multi-threaded Exchange backups
me too. I would be interest -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Ouzen Sent: Monday, November 28, 2011 9:49 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Ang: multi-threaded Exchange backups Hi Steve I will be too interested about this script if you pleased Regards Robert rou...@univ.haifa.ac.il -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Monday, November 28, 2011 4:17 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: multi-threaded Exchange backups Hi I wouldnt mind getting a copy of that script, I'm not much of a fan of multiple nodes / schedules either. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Schaub, Steve" Sänt av: "ADSM: Dist Stor Manager" Datum: 11/28/2011 15:07 Ärende: multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: multi-threaded Exchange backups
Yes, Please send me a copy. The original was definitely not working in our environment. This would be great. Thanks. Matthew J. Leonard Network Administrator AtlasAir Worldwide Holdings Network Operations Department matthew.leon...@atlasair.com Office: 914.701.8715 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Monday, November 28, 2011 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: multi-threaded Exchange backups
Having the same issue. Would be great to get a look at your script. JoeA Joseph A Abbott MCSE/MCTS 2003/2008R2, MCSA/MCTS 2003/2008R2 Tivoli Storage Manager Architect CDP jabb...@partners.org Cell-617-633-8471 Desk-617-724-4929 Page-# (617) 362-6341 - 36364 6173391...@usamobility.net "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Monday, November 28, 2011 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
multi-threaded Exchange backups
Steve, would love to get a copy of this. Question. Does it clear the logs after each DB backup or after the entire job finishes? Regards, Matthew J. Leonard On Nov 28, 2011, at 9:08 AM, "Schaub, Steve" wrote: > In case anyone is interested, I modified our Powershell script for full > backup of our Exchange databases so that it now backs up multiple concurrent > Storage Groups in a single script (because I'm too darn lazy to deal with > multiple node names, schedules, etc). > > In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent > threads. > > If anyone would like a copy, just contact me. > > Steve Schaub > Systems Engineer II, Windows Backup/Recovery > BlueCross BlueShield of Tennessee > steve_schaub "at" bcbst.com > > - > Please see the following link for the BlueCross BlueShield of Tennessee > E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm >
Re: multi-threaded Exchange backups
A copy of the script would be appreciated here also. Thanks. Harold Vandeventer Systems Programmer State of Kansas - Department of Administration/COMPACT harold.vandeven...@da.ks.gov (785) 296-0631 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Abbott, Joseph Sent: Monday, November 28, 2011 8:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] multi-threaded Exchange backups Having the same issue. Would be great to get a look at your script. JoeA Joseph A Abbott MCSE/MCTS 2003/2008R2, MCSA/MCTS 2003/2008R2 Tivoli Storage Manager Architect CDP jabb...@partners.org Cell-617-633-8471 Desk-617-724-4929 Page-# (617) 362-6341 - 36364 6173391...@usamobility.net "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schaub, Steve Sent: Monday, November 28, 2011 9:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.
Re: Ang: multi-threaded Exchange backups
Hi Steve I will be too interested about this script if you pleased Regards Robert rou...@univ.haifa.ac.il -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Monday, November 28, 2011 4:17 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: multi-threaded Exchange backups Hi I wouldnt mind getting a copy of that script, I'm not much of a fan of multiple nodes / schedules either. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Schaub, Steve" Sänt av: "ADSM: Dist Stor Manager" Datum: 11/28/2011 15:07 Ärende: multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: Ang: multi-threaded Exchange backups
Hello, same here. The script would be much appreciated. Thanks Lisa Seay 850-487- Ext 2059 PLEASE NOTE: Florida has a very broad public records law. Most written communications to or from state officials regarding state business are considered to be public records and will be made available to the public and the media upon request. Your e-mail messages may, therefore, be subject to public disclosure. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel Sparrman Sent: Monday, November 28, 2011 9:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Ang: multi-threaded Exchange backups Hi I wouldnt mind getting a copy of that script, I'm not much of a fan of multiple nodes / schedules either. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Schaub, Steve" Sänt av: "ADSM: Dist Stor Manager" Datum: 11/28/2011 15:07 Ärende: multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Ang: multi-threaded Exchange backups
Hi I wouldnt mind getting a copy of that script, I'm not much of a fan of multiple nodes / schedules either. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: "Schaub, Steve" Sänt av: "ADSM: Dist Stor Manager" Datum: 11/28/2011 15:07 Ärende: multi-threaded Exchange backups In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
multi-threaded Exchange backups
In case anyone is interested, I modified our Powershell script for full backup of our Exchange databases so that it now backs up multiple concurrent Storage Groups in a single script (because I'm too darn lazy to deal with multiple node names, schedules, etc). In our case, it dropped elapsed times from 36hr to 11hr, running 4 concurrent threads. If anyone would like a copy, just contact me. Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee steve_schaub "at" bcbst.com - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: [adsm] Increase speed of TDP Exchange Backups
That looks to be somewhere in the area of 290MB/sec. I'd suspect that the client host (Exchange server) isn't capable of sending it any faster. Have you looked at the client end? -Lloyd On 06/12/2011 09:49 PM, Leonard, Matthew wrote: Our exchange backups (Doing Full) are a little under 4.0 TB and they are taking 14 hours. We are using a Virtual Tape library and the bandwidth is great, however they are just taking way to long. I also increased the Amount to 5 for each exchange node as we have 120 drives. Does anyone have any ideas of how I can increase the duration of these exchange backups? Any help would be much appreciated. Thanks in advance Matthew J. Leonard Network Administrator AtlasAir Worldwide Holdings Network Operations Department matthew.leon...@atlasair.com Office: 914.701.8715 Mobile: 914.262.3974
Re: Increase speed of TDP Exchange Backups
The speed has somewhat been the same and nothing has changed. We are using Falconstor Virtual Tape Library w/ Deduplication occurring on the appliance. No Dedupe within Tivoli. Exchange data ENTITY MEGABYTES START_TIMEEND_TIME SUCCESSFULL --- EXVS02 1496263.00 2011-06-11-19.002011-06-12-09.39YES EXVS03 844071.00 2011-06-11-19.002011-06-12-06.28YES EXVS01 359404.00 2011-06-11-19.00 2011-06-12-00.55 YES EXVS04 42404.002011-06-11-19.162011-06-11-19.47YES EXVS04 3758.00 2011-06-11-19.132011-06-11-19.16YES EXVS04 16443.00 2011-06-11-19.002011-06-11-19.12 YES Matthew J. Leonard Network Administrator AtlasAir Worldwide Holdings Network Operations Department matthew.leon...@atlasair.com Office: 914.701.8715 Mobile: 914.262.3974 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Langdale Sent: Monday, June 13, 2011 3:56 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Increase speed of TDP Exchange Backups On 13 June 2011 02:49, Leonard, Matthew wrote: > Our exchange backups (Doing Full) are a little under 4.0 TB and they > are taking 14 hours. We are using a Virtual Tape library and the > bandwidth is great, however they are just taking way to long. I also > increased the Amount to 5 for each exchange node as we have 120 > drives. Does anyone have any ideas of how I can increase the duration > of these exchange backups? Any help would be much appreciated. > Thanks in advance > > OK a few questions: Has it always been slower than you want? If not, what has changed? What VTL do you have? I asusme LAN Free? Steven
Re: Increase speed of TDP Exchange Backups
On 13 June 2011 02:49, Leonard, Matthew wrote: > Our exchange backups (Doing Full) are a little under 4.0 TB and they are > taking 14 hours. We are using a Virtual Tape library and the bandwidth is > great, however they are just taking way to long. I also increased the > Amount to 5 for each exchange node as we have 120 drives. Does anyone have > any ideas of how I can increase the duration of these exchange backups? Any > help would be much appreciated. Thanks in advance > > OK a few questions: Has it always been slower than you want? If not, what has changed? What VTL do you have? I asusme LAN Free? Steven
Re: Increase speed of TDP Exchange Backups
are you using any deduplication feature on your vtl? On Sun, Jun 12, 2011 at 9:49 PM, Leonard, Matthew < matthew.leon...@atlasair.com> wrote: > Our exchange backups (Doing Full) are a little under 4.0 TB and they are > taking 14 hours. We are using a Virtual Tape library and the bandwidth is > great, however they are just taking way to long. I also increased the > Amount to 5 for each exchange node as we have 120 drives. Does anyone have > any ideas of how I can increase the duration of these exchange backups? Any > help would be much appreciated. Thanks in advance > > Matthew J. Leonard > Network Administrator > AtlasAir Worldwide Holdings > Network Operations Department > matthew.leon...@atlasair.com > Office: 914.701.8715 > Mobile: 914.262.3974 >
Increase speed of TDP Exchange Backups
Our exchange backups (Doing Full) are a little under 4.0 TB and they are taking 14 hours. We are using a Virtual Tape library and the bandwidth is great, however they are just taking way to long. I also increased the Amount to 5 for each exchange node as we have 120 drives. Does anyone have any ideas of how I can increase the duration of these exchange backups? Any help would be much appreciated. Thanks in advance Matthew J. Leonard Network Administrator AtlasAir Worldwide Holdings Network Operations Department matthew.leon...@atlasair.com Office: 914.701.8715 Mobile: 914.262.3974
My Scheduled Exchange backups fail on Windows Server 2008
I changed the location of the .cmd archives to another route and the backups started to work. Thanks a lot! +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: My Scheduled Exchange backups fail on Windows Server 2008
Also, you might try redirecting your stdout and stderr to a log file. This is a good troubleshooting practice. ... object=' "c:\path with spaces\file.bat" >c:\temp\file.out 2>&1 ' As Bill mentions, note the use of the single quotes and the double quotes. Alex Paschal Storage Solutions Engineer MSI Systems Integrators Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bill Boyer Sent: Sunday, February 15, 2009 9:00 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] My Scheduled Exchange backups fail on Windows Server 2008 No. In your schedule the OBJ= needs to be either the 8.3 name of the c:\Program files directory or you need to put quotes around it. Like OBJ='" C:\Program Files\Tivoli\TSM\TDPExchange\excfull.cmd"'. You need those quotes around the filename since there's a blank in there. That's why you're getting the RC=1, file not found. Bill Boyer "There are 10 types of people in the world. Those that instand binary and those that don't" - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of admbackup Sent: Sunday, February 15, 2009 8:16 PM To: ADSM-L@VM.MARIST.EDU Subject: My Scheduled Exchange backups fail on Windows Server 2008 Hi I have installed the TDP v5.5for Exchange on a Windows Server 2008. I have done a full backup with the TDP Application without probems. My problem is when I try to configure scheduled backups. They always fail with code 1. This is what I have in my dsmsched log: Executing scheduled command now. 02/15/2009 19:55:34 Executing Operating System command or script: C:\Program Files\Tivoli\TSM\TDPExchange\excfull.cmd 02/15/2009 19:55:34 Finished command. Return code is: 1 02/15/2009 19:55:34 ANS1909E The scheduled command failed. 02/15/2009 19:55:34 ANS1512E Scheduled event '@325' failed. Return code = 1. 02/15/2009 19:55:34 Sending results for scheduled event '@325'. 02/15/2009 19:55:34 Results sent to server for scheduled event '@325'. I think that it is a TCP/IP port problem. In my dsm.opt I have: TCPCLIENTPORT 1500 TCPPORT1500 Do I have to change them? Sorry for my grammar. My native language is not english. +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Re: My Scheduled Exchange backups fail on Windows Server 2008
No. In your schedule the OBJ= needs to be either the 8.3 name of the c:\Program files directory or you need to put quotes around it. Like OBJ='" C:\Program Files\Tivoli\TSM\TDPExchange\excfull.cmd"'. You need those quotes around the filename since there's a blank in there. That's why you're getting the RC=1, file not found. Bill Boyer "There are 10 types of people in the world. Those that instand binary and those that don't" - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of admbackup Sent: Sunday, February 15, 2009 8:16 PM To: ADSM-L@VM.MARIST.EDU Subject: My Scheduled Exchange backups fail on Windows Server 2008 Hi I have installed the TDP v5.5for Exchange on a Windows Server 2008. I have done a full backup with the TDP Application without probems. My problem is when I try to configure scheduled backups. They always fail with code 1. This is what I have in my dsmsched log: Executing scheduled command now. 02/15/2009 19:55:34 Executing Operating System command or script: C:\Program Files\Tivoli\TSM\TDPExchange\excfull.cmd 02/15/2009 19:55:34 Finished command. Return code is: 1 02/15/2009 19:55:34 ANS1909E The scheduled command failed. 02/15/2009 19:55:34 ANS1512E Scheduled event '@325' failed. Return code = 1. 02/15/2009 19:55:34 Sending results for scheduled event '@325'. 02/15/2009 19:55:34 Results sent to server for scheduled event '@325'. I think that it is a TCP/IP port problem. In my dsm.opt I have: TCPCLIENTPORT 1500 TCPPORT1500 Do I have to change them? Sorry for my grammar. My native language is not english. +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
My Scheduled Exchange backups fail on Windows Server 2008
I think that is a problem with the rights. The user that I was provided by the client is not administrator. It has only some rights. If the client provides me with an administrator user I have to reinstall the TDP or just create again the cmds ? +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: My Scheduled Exchange backups fail on Windows Server 2008
A return code of 1 usually means that the client schedule cannot find the batch file that it is pointed at. Check to make sure that excfull.cmd actually exists where you say it does, and that you have execution rights on the file. -- Mark Stapleton System engineer, CDW -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of admbackup Sent: Sunday, February 15, 2009 7:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] My Scheduled Exchange backups fail on Windows Server 2008 Hi I have installed the TDP v5.5for Exchange on a Windows Server 2008. I have done a full backup with the TDP Application without probems. My problem is when I try to configure scheduled backups. They always fail with code 1. This is what I have in my dsmsched log: Executing scheduled command now. 02/15/2009 19:55:34 Executing Operating System command or script: C:\Program Files\Tivoli\TSM\TDPExchange\excfull.cmd 02/15/2009 19:55:34 Finished command. Return code is: 1 02/15/2009 19:55:34 ANS1909E The scheduled command failed. 02/15/2009 19:55:34 ANS1512E Scheduled event '@325' failed. Return code = 1. 02/15/2009 19:55:34 Sending results for scheduled event '@325'. 02/15/2009 19:55:34 Results sent to server for scheduled event '@325'. I think that it is a TCP/IP port problem. In my dsm.opt I have: TCPCLIENTPORT 1500 TCPPORT1500 Do I have to change them? Sorry for my grammar. My native language is not english. +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.10.23/1953 - Release Date: 14-Feb-09 6:01 PM No virus found in this outgoing message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.10.23/1953 - Release Date: 14-Feb-09 6:01 PM
My Scheduled Exchange backups fail on Windows Server 2008
Hi I have installed the TDP v5.5for Exchange on a Windows Server 2008. I have done a full backup with the TDP Application without probems. My problem is when I try to configure scheduled backups. They always fail with code 1. This is what I have in my dsmsched log: Executing scheduled command now. 02/15/2009 19:55:34 Executing Operating System command or script: C:\Program Files\Tivoli\TSM\TDPExchange\excfull.cmd 02/15/2009 19:55:34 Finished command. Return code is: 1 02/15/2009 19:55:34 ANS1909E The scheduled command failed. 02/15/2009 19:55:34 ANS1512E Scheduled event '@325' failed. Return code = 1. 02/15/2009 19:55:34 Sending results for scheduled event '@325'. 02/15/2009 19:55:34 Results sent to server for scheduled event '@325'. I think that it is a TCP/IP port problem. In my dsm.opt I have: TCPCLIENTPORT 1500 TCPPORT1500 Do I have to change them? Sorry for my grammar. My native language is not english. +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Exchange backups
is there any power diffrence between the clinets, compression takes cpu time from the client, and if you had fairly powerful cpu machines with slow network, then ofcouse youre backuptime would be reduced, but if on the other hand if you had a old cpu´s and a network that where flying, comression on the client would slow the backup process. "It´s better to aim at perfection and miss than it is to aim at imperfection and hit it" Founder Thomas J. Watson Kær kveðja / Best regards, Pétur Eyþórsson · Tæknilegur ráðgjafi eServer & Storage · Tivoli Advanced Storage Solutons Techical Expert · MCSE · SNIA Professional · SNIA FC-SAN Practitioner · IBM C AIX S · TSM CP · TSRM CP · TASS DP · IBM SAN P Sími/tel: +354 569-7700 · GSM: +354 863-0560 www.nyherji.is "LeBlanc, Patricia" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 22.09.2005 11:57 Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Exchange backups I recently turned on compression for my exchange backups. All backup times improved, with the exception of two servers who are now taking 2 hours longer to backup. Clients are w2k3. TSM Server is AIX. Anyone using compression on exchange?
Exchange backups
I recently turned on compression for my exchange backups. All backup times improved, with the exception of two servers who are now taking 2 hours longer to backup. Clients are w2k3. TSM Server is AIX. Anyone using compression on exchange?
Re: TDP Exchange Backups
Pattie, RC=419 is an "internal error". If the DP for Exchange log does not provide any further information, try this: 1. Retry the operation that failed. 2. If the problem occurred during an incremental, differential, or database copy backup, run a full backup. If the full backup completes successfully, retry the operation that failed. 3. If the problem still exists, close other applications, especially those applications that interact with Exchange (anti-virus applications, for example). Retry the operation that failed. 4. If the problem still exists: a. Shut down the Exchange server. b. Start the Exchange server again. c. Retry the operation that failed. 5. If the problem still exists: a. Shut down the entire machine. b. Start the machine again. c. Retry the operation that failed. 6. If the problem still exists, determine if it is occurring on other Exchange servers, and then call IBM support. Thanks, Del > I'm seeing my TDP Exchange backups failing with rc = 419. The backup > will stop and restart itself. I can't find anything on the knowledge > base about this error code. We used to see rc = 418 which I believe is > network related. > > Running tsm server on aix 5.1.1.6 > Running tsm client on w2k b/a client 5.1.6 > Running tdp exchange client 5.1.5
TDP Exchange Backups
I'm seeing my TDP Exchange backups failing with rc = 419. The backup will stop and restart itself. I can't find anything on the knowledge base about this error code. We used to see rc = 418 which I believe is network related. Running tsm server on aix 5.1.1.6 Running tsm client on w2k b/a client 5.1.6 Running tdp exchange client 5.1.5 Any help is appreciated! Pattie
