ADSM-L

[ADSM-L] TDP for MSSQL VSS and best practice

2014-07-24 23:58:00
Subject: [ADSM-L] TDP for MSSQL VSS and best practice
From: Steven Harris <steve AT STEVENHARRIS DOT INFO>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 25 Jul 2014 13:55:45 +1000
-----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-----

<Prev in Thread] Current Thread [Next in Thread>