IC63094: SYSTEM STATE BACKUP OPTIMIZATION ENHANCEMENT
This is a development APAR to improve the efficiency of the
method the TSM client uses to query the TSM server database for
information about system state files.
Additional Keywords: systemstate
Local fix
Problem summary***
DEFINE LIBRARY LIBNANE LIBTYPE=MANUAL
DEFINE DRIVE LIBNAME DRIVENAME
DEFINE PATH SERVERNAME DRIVENAME srctype=server desttype=drive
library=LIBENAME DEVICE=MT#.#.#.#
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Mehdi Salehi
Sent: Monday, Febru
This is mostly directed at Andy Raibeck
Just wondering when IBM is going to fix the problem with the Windows GUI
and connections being severed/ripped (vs properly closed) just for closing
the GUI session?
We discussed this many months ago. It started happening around the time
IBM converted the G
Hi,
I'm looking at virtualising our TSM server. The OS on the current server is
pretty messed up so I would prefer to start from scratch.
Can I install/configure a new server then transfer the database?
Version 5, Release 4, Level 4.0
Thanks,
Michael
+
Yes, you can restore a TSM data base to a new TSM server.
However, think twice before virtualizing - Tivoli doesn't support the TSM
server on a VM if you have tape drivers (i.e., physical tape or VTL). See
below.
http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=server+support+v
If you are interested in an upcoming release of the IBM Tivoli Storage
FlashCopy Manager, sign up to join the beta program! If interested,
please contact your IBM account representative to be nominated for this
beta program.
Quoted from the IBM link, the table refers to virtualisation where "the
resources are then purely virtual (not dedicated) and/or are not discrete". My
confusion, and I'd love someone to clear this up, is where we have RHEL running
KVM. Red Hat clearly stated in their customer seminar on RHEV-M
IBM responded to me with some good info after reading my post. Here is their
suggestion...
Johnny,
In general, when planning for Bare Machine Recovery for any server, there are
3 data types must be considered: The operating system, the application and the
data repositories. For Windows h
Remember, TSM (a.k.a. WDSF, ADSM) was originally _invented_ as a
virtualized application, under the system now known as z/VM, and was
supporetd there until V3.7. It should still have the fundamental design
to deal with running in a virtual machine. It does need resources such
as tapes to be dedicat
