An interesting read Rejean. Do you know of many people using this
facility yet?
I can't say I've played about with 6.X too much yet, so don't know a
typical DB restore time using a normal TSM DB backup. Is it much longer
than 5.5? The last 5.5 one I did for a 120GB DB took 40 mins (DB backups
Have you found the problem?
What kind of drives?
What speed FC?
How many drives zoned to each FC port?
Type of switch?
Host or drive compression?
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of peppix
Sent: Wednesday, November 24,
I am out of the office until 12/30/2010.
Team,
I will be out of the office on Thursday, 23-Dec-10, but will return on
Thursday 29-Dec-10. Kun yao Cheng, Zigang Zhang (strong) and Steve Dawe
will be on deck.
Happy Holidays
Thanks
Keith
Note: This is an automated response to your message Re:
Bob,
We've installed the TSM 6.2.2 client on a virtual machine that we designated as
a backup proxy within vSphere 4.1. We can confirm that 6.2.2 does use the TSM
API's directly for full image backups (new to 6.2.2) as well as support for
agentless file-level backups (which shipped in 6.2).
We're delighted to see that IBM has expanded vmWare support significantly with
the 6.2.2 release by redesigning the TSM client to use the vmWare vStorage API
for full image backups directly to TSM (without using legacy VCB support). We
have installed the TSM 6.2.2 release for Windows (and
Issues with TSM 6.2.2 Client and vmWare vStorage API Backups
We're delighted to see that IBM has expanded vmWare support significantly with
the 6.2.2 release by redesigning the TSM client to use the vmWare vStorage API
for full image backups directly to TSM (without using legacy VCB support).
