Re: TDP for SQL 6.4.1 cross-server restore setup
Thanks, Del. As Steven H noted, someone really needs to impress on the developers that putting out a product that requires customers to made ad hoc changes to their production config files on the fly is really not enterprise quality engineering. -steve s -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Thursday, February 13, 2014 12:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for SQL 6.4.1 cross-server restore setup Hello, I am sorry for problems this has caused. A fix for this is targeted for the DP/SQL 7.1.0.1 iFix. Current estimate is April. Thank you. Del - ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/13/2014 11:53:25 AM: From: Hans Christian Riksheim bull...@gmail.com To: ADSM-L@vm.marist.edu, Date: 02/13/2014 11:54 AM Subject: Re: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu I agree. With the old GUI I put a link in the Public Desktop-folder for each MSSQL instance. Easy for the MSSQL-people just to double click on a named icon on their desktop which pointed to the correct configfile. Now they are copying cfg-files all around in the tdpsql directory. On one occation a configfile for an instance was emptied in this process. The backup schedule had no problem with that since it just backed up the default instance instead. So not only an inconvenience but also an added risk with the new GUI. I vote for a speedy resolve of this future improvement. Hans Chr. On Thu, Feb 13, 2014 at 12:11 PM, Steven Harris st...@stevenharris.infowrote: Thanks for the workaround Del, this is not directed at you. Surely this would have come up and been solved in any reasonable beta test program, well before being inflicted on long-suffering customers? Sometimes I wonder if any consideration is given to those who use the product day to day. The idiotic work arounds that we have to use, that have been in the TSM for years and continue to cause wasted time and effort by everyone flabbergast me. One of my accounts has just gone off to something that promises a brand new approach. Time will tell if the reality matches the glossies, but this is exactly the sort of reason why they leave. Spleen vented, submerging again, Steve Steven Harris TSM Admin Canberra Australia On 13/02/2014 5:04 AM, Del Hoobler wrote: Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=swg21597023 BTW... this is a known requirement. There are plans to add this function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file? - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: TDP for SQL 6.4.1 cross-server restore setup
Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: biloholdings.com X-Barracuda-Connect: mail-by2lp0239.outbound.protection.outlook.com[207.46.163.239] X-Barracuda-Start-Time: 1392383883 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: http://148.100.49.28:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at marist.edu X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests=INFO_TLD X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.145106 Rule breakdown below pts rule name description -- -- 0.00 INFO_TLD URI: Contains an URL in the INFO top-level domain Yup, this is one of my DBA team's biggest complaints regarding TSM. -Rick Adamson 904.783.5264 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sc= haub, Steve Sent: Friday, February 14, 2014 7:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for SQL 6.4.1 cross-server restore setup Thanks, Del. As Steven H noted, someone really needs to impress on the developers that p= utting out a product that requires customers to made ad hoc changes to thei= r production config files on the fly is really not enterprise quality engin= eering. -steve s -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of De= l Hoobler Sent: Thursday, February 13, 2014 12:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for SQL 6.4.1 cross-server restore setup Hello, I am sorry for problems this has caused. A fix for this is targeted for the DP/SQL 7.1.0.1 iFix. Current estimate is April. Thank you. Del - ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/13/2014 11:53:25 AM: From: Hans Christian Riksheim bull...@gmail.com To: ADSM-L@vm.marist.edu, Date: 02/13/2014 11:54 AM Subject: Re: TDP for SQL 6.4.1 cross-server restore setup Sent by:=20 ADSM: Dist Stor Manager ADSM-L@vm.marist.edu I agree. With the old GUI I put a link in the Public Desktop-folder for each MSSQL instance. Easy for the MSSQL-people just to double click on a named=20 icon on their desktop which pointed to the correct configfile. Now they are copying cfg-files all around in the tdpsql directory. On one occation a configfile for an instance was emptied in this process. The=20 backup schedule had no problem with that since it just backed up the=20 default instance instead. So not only an inconvenience but also an=20 added risk with the new GUI. I vote for a speedy resolve of this=20 future improvement. Hans Chr. On Thu, Feb 13, 2014 at 12:11 PM, Steven Harris st...@stevenharris.infowrote: Thanks for the workaround Del, this is not directed at you. Surely this would have come up and been solved in any reasonable=20 beta test program, well before being inflicted on long-suffering custom= ers? Sometimes I wonder if any consideration is given to those who use=20 the product day to day. The idiotic work arounds that we have to=20 use, that have been in the TSM for years and continue to cause wasted time and=20 effort by everyone flabbergast me. One of my accounts has just gone off to something that promises a brand new approach. Time will tell if the reality matches the glossies, but this is exactly the sort of reason why they leave. Spleen vented, submerging again, Steve Steven Harris TSM Admin Canberra Australia On 13/02/2014 5:04 AM, Del Hoobler wrote: Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=3Dswg21597023 BTW... this is a known requirement. There are plans to add this=20 function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by:=20 ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I=20 cant depend on them editing the dsm.opt file (tried that before,=20 ended up with a bunch of backups in the wrong place because they=20 forgot to change it back), I came up with a little pre-launch=20 script that allows them to pick a SQL node from our inventory to=20 restore from, then builds a temp opt file using that node name,=20 and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the=20 mmc, I haven't
Re: TDP for SQL 6.4.1 cross-server restore setup
Point well taken and thank you. As soon as I saw this on Wednesday, I shared it with the rest of the team. As I noted earlier, we will have a fix for this targeted for April in DP/SQL 7.1.0.1. I will take this opportunity to mention that we do have a TSM/FCM EAP/beta program running for the next release and would love to have anyone interested. If you are interested in enrolling, please submit a sign-up form here: https://www-304.ibm.com/software/support/trial/cst/forms/nomination.wss?id=5311 For any questions, please contact Mary Anne Filosa, mfil...@us.ibm.com Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/14/2014 07:06:29 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/14/2014 07:07 AM Subject: Re: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Thanks, Del. As Steven H noted, someone really needs to impress on the developers that putting out a product that requires customers to made ad hoc changes to their production config files on the fly is really not enterprise quality engineering. -steve s -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Thursday, February 13, 2014 12:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for SQL 6.4.1 cross-server restore setup Hello, I am sorry for problems this has caused. A fix for this is targeted for the DP/SQL 7.1.0.1 iFix. Current estimate is April. Thank you. Del - ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/13/2014 11:53:25 AM: From: Hans Christian Riksheim bull...@gmail.com To: ADSM-L@vm.marist.edu, Date: 02/13/2014 11:54 AM Subject: Re: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu I agree. With the old GUI I put a link in the Public Desktop-folder for each MSSQL instance. Easy for the MSSQL-people just to double click on a named icon on their desktop which pointed to the correct configfile. Now they are copying cfg-files all around in the tdpsql directory. On one occation a configfile for an instance was emptied in this process. The backup schedule had no problem with that since it just backed up the default instance instead. So not only an inconvenience but also an added risk with the new GUI. I vote for a speedy resolve of this future improvement. Hans Chr. On Thu, Feb 13, 2014 at 12:11 PM, Steven Harris st...@stevenharris.infowrote: Thanks for the workaround Del, this is not directed at you. Surely this would have come up and been solved in any reasonable beta test program, well before being inflicted on long-sufferingcustomers? Sometimes I wonder if any consideration is given to those who use the product day to day. The idiotic work arounds that we have to use, that have been in the TSM for years and continue to cause wasted time and effort by everyone flabbergast me. One of my accounts has just gone off to something that promises a brand new approach. Time will tell if the reality matches the glossies, but this is exactly the sort of reason why they leave. Spleen vented, submerging again, Steve Steven Harris TSM Admin Canberra Australia On 13/02/2014 5:04 AM, Del Hoobler wrote: Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=swg21597023 BTW... this is a known requirement. There are plans to add this function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file? - Please see the following link for the BlueCross BlueShield
Re: TDP for SQL 6.4.1 cross-server restore setup
Thanks for the workaround Del, this is not directed at you. Surely this would have come up and been solved in any reasonable beta test program, well before being inflicted on long-suffering customers? Sometimes I wonder if any consideration is given to those who use the product day to day. The idiotic work arounds that we have to use, that have been in the TSM for years and continue to cause wasted time and effort by everyone flabbergast me. One of my accounts has just gone off to something that promises a brand new approach. Time will tell if the reality matches the glossies, but this is exactly the sort of reason why they leave. Spleen vented, submerging again, Steve Steven Harris TSM Admin Canberra Australia On 13/02/2014 5:04 AM, Del Hoobler wrote: Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=swg21597023 BTW... this is a known requirement. There are plans to add this function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file?
Re: TDP for SQL 6.4.1 cross-server restore setup
Hello, I am sorry for problems this has caused. A fix for this is targeted for the DP/SQL 7.1.0.1 iFix. Current estimate is April. Thank you. Del - ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/13/2014 11:53:25 AM: From: Hans Christian Riksheim bull...@gmail.com To: ADSM-L@vm.marist.edu, Date: 02/13/2014 11:54 AM Subject: Re: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu I agree. With the old GUI I put a link in the Public Desktop-folder for each MSSQL instance. Easy for the MSSQL-people just to double click on a named icon on their desktop which pointed to the correct configfile. Now they are copying cfg-files all around in the tdpsql directory. On one occation a configfile for an instance was emptied in this process. The backup schedule had no problem with that since it just backed up the default instance instead. So not only an inconvenience but also an added risk with the new GUI. I vote for a speedy resolve of this future improvement. Hans Chr. On Thu, Feb 13, 2014 at 12:11 PM, Steven Harris st...@stevenharris.infowrote: Thanks for the workaround Del, this is not directed at you. Surely this would have come up and been solved in any reasonable beta test program, well before being inflicted on long-suffering customers? Sometimes I wonder if any consideration is given to those who use the product day to day. The idiotic work arounds that we have to use, that have been in the TSM for years and continue to cause wasted time and effort by everyone flabbergast me. One of my accounts has just gone off to something that promises a brand new approach. Time will tell if the reality matches the glossies, but this is exactly the sort of reason why they leave. Spleen vented, submerging again, Steve Steven Harris TSM Admin Canberra Australia On 13/02/2014 5:04 AM, Del Hoobler wrote: Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=swg21597023 BTW... this is a known requirement. There are plans to add this function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file?
TDP for SQL 6.4.1 cross-server restore setup
Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file? Thanks, Steve Schaub System Engineer II, Backup/Recovery Blue Cross Blue Shield of Tennessee - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: TDP for SQL 6.4.1 cross-server restore setup
Hi Steve, See if this helps: http://www-01.ibm.com/support/docview.wss?uid=swg21597023 BTW... this is a known requirement. There are plans to add this function directly to the launch of the MMC soon. Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 02/12/2014 11:46:58 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 02/12/2014 12:36 PM Subject: TDP for SQL 6.4.1 cross-server restore setup Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Windows 2012, TSM TDP 6.4.1 Our DBA's do a fair amount of cross-server restores here. Since I cant depend on them editing the dsm.opt file (tried that before, ended up with a bunch of backups in the wrong place because they forgot to change it back), I came up with a little pre-launch script that allows them to pick a SQL node from our inventory to restore from, then builds a temp opt file using that node name, and launches the tdp gui using that opt file. However, now that 6.4.1 has killed off the tdp gui in favor of the mmc, I haven't been able to figure out how to achieve the same results. Can someone tell me how to launch the mmc using an alternate opt file?
