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.info>wrote: > > > 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
