On Jun 16, 2009, at 11:43 PM, Steven Harris wrote:
One possibility would be to install TSM for SAN on the partitions
that need
it, but there is some administrative overhead with doing this, and
we are
finding that drive sharing is not as error free as we would like
with only
a 5 way split. We
Hi TSM-ers!
Our windows department is looking at different backup products for
backing up their server.
They have two major problems with TSM. One I cannot solve: the TSM
client license is processor based, so quite expensive for the majority
of small servers. I think we all agree that the TSM
Hi Eric
IBM do have a Sub Capacity Licencing model where you Licence only what
portion of ESX the Server is running on.
Have a look at their site, it might be of assistance.
Must admit, they are annoying me no end with their model.
Regards
Adrian Compton
-Original Message-
From:
EJ,
Have you reviewed TSM V6.1 Windows BA documentation? It looks like
it coordinates backups through VMware Consolidated Backup (VCB). And
allws for both image and file level backups. We will be investigating
this feature within the next few weeks as our virtual environment is
rapidly
Eric,
TSM does backup running VMs; for TSM versions prior to 5.5, you had to
backup each individual VM just like you would backup physical servers
(this meant getting a TSM license for each and every VM instance). TSM
V5.5 goes a step further and makes use of the VM Consolidated backup
(VCB) to
Hi Eric,
Look at the redbook: TSM 5.4-5.5 Technical Guide SG24-7447
Read the chapter on TSM 5.5. support for VMWare VCB backups.
The TSM 5.5 client integrates nicely with VMWare VCB to do the snapshots and
take file-level backups.
The TSM 6.1 client (which you can use with a 5.4/5.5 server)
TSM license is for the hardware platform. So, if you have 5 VMware
servers, you need 5 TSM licenses, no matter how many virtual servers you
have running. A 4 processor, quad core license is more expensive than a
2 processor, single core license, but, TSM/IBM does not care how many
servers are
Hello Eric,
If the windows folks are using DPM I suspect that they are using the Microsoft
Hyper-V support and not vmware. I have not heard that TSM support Hyper-V
client per say.
When DPM first came out they only supported backing up to disk. To move the
disk backups to tape required
Eric,
1. cant help with licensing, IBM is horrible in this area
2. ask your windows guys who implemented Microsoft's DPM what their
strategy is for DR - chances are you'll get a blank look since they
haven't thought about how to make offsite copies.
3. check out Storserver Agent for VCB, we use
Hum..
DPM supports site replication so offsite copies should not be a problem. I
think even Windows guys can read a manual.
We are using TSM and VCB to backup ~800 WM´s. I don't really see why I should
need Storserver Agent for VCB?
//Henrik
-Original Message-
From: ADSM: Dist Stor
TSM license is for the hardware platform. So, if you have 5 VMware
servers, you need 5 TSM licenses, no matter how many
virtual servers you have running. A 4 processor, quad core license is
more expensive than a
2 processor, single core license, but, TSM/IBM does not care how many
servers are
Hi Len!
I don't know anything about Windows virtualization, but I heard him talk
about Hyper-V, whatever it may be, so I guess you are right.
Thank you all for responding!!! I will send him the Technical Guide and
let him read what is and what isn't possible with TSM.
Kind regards,
Eric van Loon
Evans,
I agree with your statement below as long as you install the
Backup/Archive client on each and every VM server. However, with the use
of VCB on V5.5 and above, you will not have to purchase 5 TSM licenses;
for the small number of VMs in your example, you will only need one TSM
license on
You don't need a license for each VM if you use a proxy.
Buddy Howeth
Computer Operations Specialist
Information Systems
Pacific Coast Producers
Corporate Offices
631 N. Cluff Ave
Lodi, CA 95240-0756
(209) 367-8800 - Main#
(209) 367-6288 - Computer Room
(209) 366-6240 - Alpha Pager
We do it all the time. We have 3 servers running linux redhat with about
20 vm hosted on those machines.. We use a machine as a proxy. Virtual
Consolidated Backup. Each VM drops it's snapshot on the D drive on this
machine and they are saved with the proxy. We control which machines will
Currently our VM windows guy wants to use the VM VCB function and TSM.
He's not sure, how he should sent of the user accounts and where they go.
Has anyone or is anyone using VM's VCB TSM with success and would like
to shed some light on how we can get this up and running. I can put you
in
We are on TSM 5.4 and have 3 VM servers running redhat. we use a Virtual
Consolidated Backup (windows machine ) as a proxy to backup the VMs
(snapshots). They are created when the client runs because of the
schedule pre/post tasks defined in the TSM client and dumped to the D
drive on the VCB.
Buddy,
Could you please elaborate, or provide some form of reference/proof for your
assertion ?
This would be absolutely great news, but as far as I know, IBM is not a
non-profit organization ;-)
Cheers.
Arnaud
**
I've just run into a roadblock with the TSM gui on
the Macintosh - both v5 and v6 clients. There apparently
was a Java software update (1.5.0_19) that was just
released and I believe it to be causing the problem
with the TSM client.
If you start the GUI, you get an ANS1971E (v6) or
ANS5179E (v5)
We had IBM come to our company to help with the setup.
We have 3 ESX 3.5 servers running linux that are our hosts for the VMs. We
have one physical windows box which is the VCB (Virtual Consolidate
Backup). This machine has a TSM Windows client installed. In the
pre/post schedule section of the
Hi,
We had a user with this today on TSM 5.5, and I've recreated the error
on a second machine by upgrading to that version of Java. So it seems
likely that you're right that it's the Java update.
We're now wondering whether this will affect all Mac clients that have
upgraded to Java
The notice in the software update states for Mac OS X
10.5.7 and later. Formally, it's this update:
Java for Mac OS X 10.5 Update 4 Version 1.0
IBM/Tivoli has several PMRs open on this one (I've
added our incident to the list), and it's in the
hands of the developers.
-Original
On 17 jun 2009, at 19:24, Gretchen L. Thiele wrote:
The notice in the software update states for Mac OS X
10.5.7 and later. Formally, it's this update:
Java for Mac OS X 10.5 Update 4 Version 1.0
IBM/Tivoli has several PMRs open on this one (I've
added our incident to the list), and it's in
You need to separate the non-qtree data first before TSM looks at it.
We use snapvault for our short-term backups and TSM NDMP for the long term
stuff.
So we created one snapvault destination to grab all of the non-qtree stuff
using the /vol/xyz/- as the source.
Then you can backup that with TSM
Add my thanks, Gretchen. We have a lot of Macs here. I've opened another
PMR with IBM and added our names to the list of interested parties. ..Paul
At 11:29 AM 6/17/2009, Gretchen L. Thiele wrote:
I've just run into a roadblock with the TSM gui on the Macintosh - both v5
and v6 clients.
The existence of docs that describe the process of Complete Restores of
Windows Systems with the TSM Client implies that such is possible and
probable with W2K8 nodes. One of the Windows admins here has quite a bit
of effort into documenting the specifics required for this process to
work.
So far
We confirm that the Macintosh Java update 4 for OS X 10.5.7 from June 15 seems
to cause the Tivoli Storage Manager application versions 5.5.1.6, 5.5.2.0, and
6.1.0.0 to give an error of ANS1971E The remote client agent (dsmagent) could
not be started.
There is a June 15th Java update 9 for
I have a number of LTO3 tape volumes as follows:
812 BKPLTO3POOL LTO3CLASS1,180,167 0.0
Full
823 BKPLTO3POOL LTO3CLASS1,433,743 0.2
Full
801 BKPLTO3POOL LTO3CLASS1,134,86837.3
Full
827
Get in the habit of adding Format=Detailed to query commands when
pursuing issues, to see the status of the resources involved an full
information about them. Here, query your volumes and storage pool to
check their status, and inspect the Activity Log for error condition
messages.
Richard
Is the install path c:\program files\IBM\ISC601, or c:\program
files\IBM\ISC6011?
If you're sure it's correct, and it still won't install, I'd suggest a manual
de-install of the ISC, followed by a reboot and reinstall of the ISC AC.
-Lloyd
On Tue, 16 Jun 2009 16:33:43 -0700
Mario Behring
30 matches
Mail list logo
