ADSM-L

Re: [ADSM-L] Pointing FlashCopyManager.exe at a custom options file

2014-02-20 09:23:29
Subject: Re: [ADSM-L] Pointing FlashCopyManager.exe at a custom options file
From: "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 20 Feb 2014 09:07:25 -0500
Unless your DBA leaves the gui open and one of your scheduled backups kicks 
off, using the incorrect settings in the opt file.
Steve Schaub

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Remco Post
Sent: Wednesday, February 19, 2014 2:14 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Pointing FlashCopyManager.exe at a custom options file

Hi Neil,

we've opted to do the 'copy and overwrite' option files in a script that 
subsequently starts the GUI. The scripts are placed in the start menu and well, 
the exchange/sql admins see the difference, but the ease of use is such that 
there is very little to complain about.

Op 19 feb. 2014, om 16:58 heeft Neil Schofield <neil.schofield AT 
YORKSHIREWATER.CO DOT UK> het volgende geschreven:

> I've got something of a revolt on my hands from our SQL DBAs when it 
> comes to the new Flash Copy Manager interface for TDP for SQL. 
> Fundamentally, their objections arise from an inability to specify the 
> name of a custom options file when launching the console.
> 
> Previously, when managing multiple SQL Server instances in a Failover 
> Cluster the DBAs would have numerous shortcuts to TDPSQL.EXE with each 
> using the /TSMOPTFILE switch (along with /SQLSERVER ) to specify a 
> different options file on a shared disk. Unfortunately 
> FLASHCOPYMANAGER.EXE doesn't seem to allow the options file to be 
> specified in this way.
> 
> IBM offer some advice to work around this limitation but this seems to 
> boil down to reverting to using the now deprecated TDPSQL.EXE or a 
> rather kludgy series of scripts to overwrite the default copy of the 
> options file with a custom version prior to launching the console:
> http://www-01.ibm.com/support/docview.wss?uid=swg21597023
> 
> Neither of these is especially attractive and I wondered if anyone 
> else had a better way of coping with this scenario? The technote above 
> makes reference to reviewing this capability for future releases but 
> given this is now a year old and we've seen v7.1 arrive in the mean 
> time, I'm guessing they don't see it as a priority.
> 
> Regards
> Neil Schofield
> Infrastructure Architect, Hardware Engineering Yorkshire Water
> 
> 
> ----------------------------------------
> 
> Spotted a leak?
> If you spot a leak please report it immediately. Call us on 0800 57 
> 3553 or go to http://www.yorkshirewater.com/leaks
> 
> Get a free water saving pack
> Don't forget to request your free water and energy saving pack, it 
> could save you money on your utility bills and help you conserve 
> water. http://www.yorkshirewater.com/savewater
> 
> The information in this e-mail, and any files transmitted with it, is 
> confidential and may also be legally privileged. The contents are intended 
> solely for the addressee only and are subject to the legal notice available 
> at http://www.keldagroup.com/email.htm. This email does not constitute a 
> binding offer, acceptance, amendment, waiver or other agreement, or create 
> any obligation whatsoever, unless such intention is clearly stated in the 
> body of the email. If you are not the intended recipient, please return the 
> message by replying to it and then delete the message from your computer. Any 
> disclosure, copying, distribution or action taken in reliance on its contents 
> is prohibited and may be unlawful.
> 
> Yorkshire Water Services Limited
> Registered Office Western House, Halifax Road, Bradford, BD6 2SZ 
> Registered in England and Wales No 2366682

-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm