Hi Steven!
If you are going to use the legacy backup method be sure to upgrade to 7.1.0.1
first because otherwise the legacy parameter in your tdpsql.cfg file is not
processed properly. The client works but issues an error that the software is
not properly configured.
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Harris
Sent: vrijdag 25 juli 2014 5:56
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TDP for MSSQL VSS and best practice
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All
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.
Steven Harris
TSM Admin,
Canberra Australia.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJT0dU5AAoJENyzJ5R4j0ydwIIIAKUo6HIXeG76Q5yveRi19UnZ
JNGZQTdJaUK7K915GCxTA7NlC0HL5H8E9vs889kWR1oERWDQ3C/bd7+jZQ/cPBIG
rWZK4vq8hsyQPKiV0Bn4V8C/o/kiOIRc8pg5V/lqvP14bbYKC29zMbwQysT+gXkZ
gOICtZommjeNphA0xeve1x0abdhorqATk97xmsbdPI59JGIcG1fU4aUhsCABSY/P
T0soM6XsBqZGw43Pzht2R6Ky5S7OSUhiYQgMWLCzbHCBAVgWxO+slOK/8jciZr9L
C85KGMIcO+k+HBAPZIPZ8hLmM+l7K7biUhbPCgF33WryXeTbLZH94mg/ymH2rmE=
=gl+l
-----END PGP SIGNATURE-----
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
|
