Re: TSM BA installer rant
Hello, Thanks Del. Fortunately, the customer is using a DAG installation of Exchange... -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: Del Hoobler hoob...@us.ibm.com À: ADSM-L@VM.MARIST.EDU Envoyé: Mercredi 23 Juillet 2014 21:48:19 Objet: Re: [ADSM-L] TSM BA installer rant Hello, This falls into the same install code as the BA Client and APAR IC92587. http://www-01.ibm.com/support/docview.wss?uid=swg1IC92587 Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/22/2014 09:31:00 PM: From: Erwann SIMON erwann.si...@free.fr To: ADSM-L@vm.marist.edu Date: 07/22/2014 09:31 PM Subject: Re: TSM BA installer rant Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Hi all, I've just installed TSM for Mail (Exchange) 7.1 on two Exchange 2010 SP3 servers running on Windows 2008R2 SP1 and both servers rebooted twice during the installation of the prerequisites, without any warning... Same behavior with 7.1.0.0 and 7.1.0.2... It should not behave that way. -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: Bill Boyer bjdbo...@comcast.net À: ADSM-L@VM.MARIST.EDU Envoyé: Mardi 22 Juillet 2014 21:28:36 Objet: Re: [ADSM-L] TSM BA installer rant Double-click on the client installer .EXE and if the install says it needs to install the VC++ libraries or any other pre-req's, cancel out f the client install. Then go to the C:\tsm_images \TSM_BA_Client\ISSetupPrerequisites directory. There are directories for each of the pre-req's. Run them manually and if a reboot is required, you can say no and reboot at your leisure. Then come back and run the setup.exe and continue the TSM client install. As for client upgrades I've found that if you make sure to stop any of the TSM client services that running (JBB, CAD,Scheduler,...) before running the install I don't get asked for a reboot. Bill Boyer “If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all.” - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hans Christian Riksheim Sent: Friday, July 04, 2014 7:55 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM BA installer rant As many has experienced the 7.1 BA client for Windows not only requires a reboot, it will in the middle of the install reboot right into your face without any warning or prompt. On top of this it will do so despite you telling it not to. The same goes for the TDP SQL client btw. Cause is some C++ Windows things that must be installed for the GUI to work. For the BA client there is a warning in the Info Center on this. For the TDP it is not so clear, that crucial information is hidden in a technote. IBM therefore thinks they are not to blame but in practise a lot of users fall in that trap and breach their SLAs all over the place. With a GUI one has certain expectations on how it should behave and if no unprompted reboot happened in earlier versions why should it happen now? My opinion on this: 1. IBM should set as a design principle that no customer server should ever need a reboot when installing, upgrading or removing TSM software. 2. There should be no exceptions, but if there are at least make the installer prompt a warning so that the user can delay the reboot until service hours. 3. Software versions that will reboot a server without warning should be immediately removed from PA and other repositories until they are fixed. Regards, Hans Chr. Riksheim
IMPORT / EXPORT
Hi, I am currently export nodes to a new server which is working fine. Some of these exports are taking a very long time due to collocation not being switched on. I cannot stop the backups in the mean time. What I'm trying to find out is: Does the export just work with data retrieved at the start and therefore any new Active data is not included when the export finishes? Many Thanks, Jason Barkes Enterprise Support Group ** The information in this email is confidential and may be legally privileged. It may not represent the views of the SSE Group. It is intended solely for the addressees. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. SSE plc Registered Office: Inveralmond House 200 Dunkeld Road Perth PH1 3AQ Registered in Scotland No. SC117119 www.sse.com **
Re: TDP for MSSQL VSS and best practice
Hi Steve, You pretty much hit the nail on the head. For your use case, legacy backup still offers the simplest and most versatile solution. Since you don't have an immediate need for leveraging hardware snapshots or offloadeded backups, you don't need to use VSS. For SQL Server, legacy backups (VDI) still offer the widest backup and restore features and are the most efficient when it comes to data transferred and stored on the TSM Server. As for TSM for VE, if your SQL Servers are virtualized, and you begin to protect your VMs using TSM for VE, the good news is that you can back up your entire VM containing a running SQL Server, but still use Data Protection for SQL to restore a single SQL Server database from that TSM for VE backup. You can even combine it with Data Protection for SQL log backups if you want. We published a whitepaper titled IBM Tivoli Storage Manager Protecting Microsoft SQL Databases Hosted in VMware on how to do that: https://ibm.biz/BdRVbA This means you can use TSM for VE to back up your entire VM leveraging incremental forever, and still restore single a SQL Server database from those backups. Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/24/2014 11:55:45 PM: From: Steven Harris st...@stevenharris.info To: ADSM-L@vm.marist.edu Date: 07/24/2014 11:56 PM Subject: TDP for MSSQL VSS and best practice Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Having managed to finally get my customers to set up some new infrastructure with V6 TSM servers, I'm now going through the process of upgrading clients. The 5.5 TDP for SQL has long been in use, is well understood and is stable. The new TDP version 7.1 that we are moving to now has the option of VSS or legacy backups. I understand that VSS backups are essential if we need to offload backup processing or use hardware snapshots, or multiple local VSS restore points in the one day, but most of our SQL apps are small backup-in-full-once-a-day affairs. I feel inclined to continue to use legacy backup for these, mostly because of the set-up overhead and complexity for VSS. What is best practice? If you use both legacy and VSS, what criteria inform that choice? Does TSM for VE significantly affect the equation? (I don't have that yet, but the writing is on the wall) Regards Steve.
Re: IMPORT / EXPORT
It is my understanding the export only deals with data as it existed at the initial start of the EXPORT process. Newly arriving data from backup is not exported. The approach I used: Export the node, making note of the date the process started. Use SUSPEND EXPORT * in your daily maintenance scripts to temporarily pause the export before the next backup schedule. Then use RESTART EXPORT * in later scripting to pick up where that export left off. In time, perhaps a few days, the export will finish. When the initial export is done use the EXPORT node FROMDATE= parameter to collect the new backup activity. That let the node manager and I coordinate the cut of the node to the new TSM server on any date that was convenient without my manual oversight of repeated exports every day. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jason Barkes Sent: Friday, July 25, 2014 3:54 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] IMPORT / EXPORT Hi, I am currently export nodes to a new server which is working fine. Some of these exports are taking a very long time due to collocation not being switched on. I cannot stop the backups in the mean time. What I'm trying to find out is: Does the export just work with data retrieved at the start and therefore any new Active data is not included when the export finishes? Many Thanks, Jason Barkes Enterprise Support Group ** The information in this email is confidential and may be legally privileged. It may not represent the views of the SSE Group. It is intended solely for the addressees. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. SSE plc Registered Office: Inveralmond House 200 Dunkeld Road Perth PH1 3AQ Registered in Scotland No. SC117119 www.sse.com ** [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: IMPORT / EXPORT
Thanks Harold, Your approach is more or less what we are doing here, and you ratified what I believed to be the case. Many Thanks, Jason Barkes Enterprise Support Group From: Vandeventer, Harold [BS] harold.vandeven...@ks.gov To: ADSM-L@VM.MARIST.EDU Date: 25/07/2014 14:03 Subject:Re: [ADSM-L] IMPORT / EXPORT Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU It is my understanding the export only deals with data as it existed at the initial start of the EXPORT process. Newly arriving data from backup is not exported. The approach I used: Export the node, making note of the date the process started. Use SUSPEND EXPORT * in your daily maintenance scripts to temporarily pause the export before the next backup schedule. Then use RESTART EXPORT * in later scripting to pick up where that export left off. In time, perhaps a few days, the export will finish. When the initial export is done use the EXPORT node FROMDATE= parameter to collect the new backup activity. That let the node manager and I coordinate the cut of the node to the new TSM server on any date that was convenient without my manual oversight of repeated exports every day. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jason Barkes Sent: Friday, July 25, 2014 3:54 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] IMPORT / EXPORT Hi, I am currently export nodes to a new server which is working fine. Some of these exports are taking a very long time due to collocation not being switched on. I cannot stop the backups in the mean time. What I'm trying to find out is: Does the export just work with data retrieved at the start and therefore any new Active data is not included when the export finishes? Many Thanks, Jason Barkes Enterprise Support Group ** The information in this email is confidential and may be legally privileged. It may not represent the views of the SSE Group. It is intended solely for the addressees. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. SSE plc Registered Office: Inveralmond House 200 Dunkeld Road Perth PH1 3AQ Registered in Scotland No. SC117119 www.sse.com ** [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. ***
TSM/AC and CommandLine
TSM AC 6.3.4.300 IE 9 Seems to work fine, but when I try the command line I get the windows, type in a command and . nothing. Don't see the command being issues to the TSM server and it never comes back. You can't even click the Stop button. Any ideas?Bill Boyer DSS, Inc. (610) 927-4407 Enjoy life. It has an expiration date. - ??
Re: TSM/AC and CommandLine
Hello Bill, It can be a java problem, this is a java applet that is used for command. Try a different version of java (Java 6 seems to be workable). -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: Bill Boyer bjdbo...@comcast.net À: ADSM-L@VM.MARIST.EDU Envoyé: Vendredi 25 Juillet 2014 20:28:15 Objet: [ADSM-L] TSM/AC and CommandLine TSM AC 6.3.4.300 IE 9 Seems to work fine, but when I try the command line I get the windows, type in a command and . nothing. Don't see the command being issues to the TSM server and it never comes back. You can't even click the Stop button. Any ideas?Bill Boyer DSS, Inc. (610) 927-4407 Enjoy life. It has an expiration date. - ??
tsm for ve question
Is there or is there in planning, tsm for VE for hyper-v? We use both vmware and hyper-v and would like to standardize our backups.
Re: tsm for ve question
Hi Gary, We are very aware of this requirement. 1. What are your top use cases for this environment? 2. What % of VMware vs. Hyper-V do you have? 3. Are you migrating from one to the other? ... or do you foresee keeping both? Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/25/2014 03:29:39 PM: From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 07/25/2014 03:30 PM Subject: tsm for ve question Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Is there or is there in planning, tsm for VE for hyper-v? We use both vmware and hyper-v and would like to standardize our backups.
