Not recommend as it uses different versions of the same components (baclient,
etc.), and updating TSMVE may break the TSM server itself. In my case, DBBackup
were broken after VE update due version mismatch.
It is much safer to run VE in a separate virtual machine. Or physical, because
you
Looks like there is some nasty bug with BAC 8.1.4.1 itself: DB backup doesn't
work on a clean installation of TSM server V8.1.4.0 with BAC 8.1.4.1 and
rollback to BAC 8.1.4.0 didn't help.
-Original Message-
From: ADSM: Dist Stor Manager On Behalf Of Anders Rantila
We finally installed (upgraded) the
8.1.2 client on a Windows test machine and it connected and backed-up without
any issues. We haven't tried scheduling since it is a test machine.
On Tue, Aug 29, 2017 at 9:24 AM, Mikhail Tolkonyuk <mtolkon...@cinimex.ru>
wrote:
> You must update server
You must update server certificate to SHA-256 before upgrading clients or
disable SSL in dsm.opt on all of them.
BAC 8.1.2 remembers server certificate and uses TLS by default, it will work
with old 7.1.x SHA-1 (or MD5) certificate until you upgrade server and OC to
8.1.2. During upgrade
The issue with FTP downloads still exists, I tried to download TSM 8.1.1 with
different settings using Download Master:
1. Multi-stream download: BROKEN
2. Single-stream with pause and resume: BROKEN
3. Single-stream in single attempt (like browsers do): OK
-Original Message-
From: