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 <steve AT stevenharris DOT
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 AT vm.marist DOT edu> wrote on 02/12/2014
>> 11:46:58 AM:
>>
>> From: "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>
>>> To: ADSM-L AT vm.marist DOT 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 AT vm.marist DOT 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?
>>>
>>>
|
