ADSM-L

Re: [ADSM-L] TSM for Virtual Environments - Reporting

2012-10-05 19:48:08
Subject: Re: [ADSM-L] TSM for Virtual Environments - Reporting
From: Gergana V Markova <gmarkova AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 5 Oct 2012 16:41:54 -0700
 Some information on how to infer that information is available in the
TSM-VE Deployment Guide:

https://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/Tivoli+Storage+Manager+for+Virtual+Environments+Deployment+Guide

Thanks.

Regards/Pozdravi, Gergana

| |      ~\\  !  //~
| |   ( ( 'o . o' ) )    Imagination can change the equation . .
| |        (  w  )
| |  Gergana V Markova       gmarkova AT us.ibm DOT com
| | (+1 US) 520 799 5716    T/L 321-5716
| |  IBM Tivoli Storage Manager(TSM) - Server Development



From:
"Prather, Wanda" <Wanda.Prather AT ICFI DOT COM>
To:
ADSM-L AT vm.marist DOT edu
Date:
10/05/2012 09:37 AM
Subject:
Re: [ADSM-L] TSM for Virtual Environments - Reporting



Trying to grep that stuff out of the logs is a nightmare.
And it doesn't' cover the case where a VM gets vmotioned to a different
ESX host, and for some reason that host wasn't set up to find and backup
all VM's on it.

So I"ve been tackling it from the opposite direction:
   select filespace_name, date(backup_end) from filespaces where
node_name='VEDATACENTERNODE' order by 2

The good thing about VE, is that all the filespaces are stored under the
one nodename.
So I figure any VM that doesn't have a backup date of yesterday had a
backup failure, and those are the only ones I need to go looking for.

Better yet, VE 6.4 is announced and will be available 11/16.
It's supposed to have better reporting built into it, but I haven't seen
it for myself yet.

W



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Friday, September 28, 2012 6:32 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM for Virtual Environments - Reporting

Understood.  I'm looking for more of a "q event" type output.  Maybe from
a third party reporting system.  Maybe even the IBM reporting and
monitoring if anyone can suggest something.   Just a one-liner, vm name,
success, fail, date, etc.

Regards,
Shawn
________________________________________________
Shawn Drew





Internet
rcowen AT CPPASSOCIATES DOT COM

Sent by: ADSM-L AT VM.MARIST DOT EDU
09/28/2012 05:16 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
Re: [ADSM-L] TSM for Virtual Environments - Reporting






Shawn,

Are you seeing these messages?

ANE4146I Starting Full VM backup of Virtual Machine 'vmname'
ANE4147I Successful Full VM backup of Virtual Machine 'vmname'
ANE4148E Full VM backup of Virtual Machine 'vmname' failed with RC rc

Do they have session/process numbers?

There are a host of other VM related messages that should help describe
the status...

Richard

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Friday, September 28, 2012 4:15 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM for Virtual Environments - Reporting

Quick question, may be a long answer.
How is everyone reporting on success/failures for Full VM backups using
TSM for VE.  My reports are grabbing lines from the actlog and it is
uugly.

2012-09-25      11:40:27        ANE4142I   virtual machine NODE1 backed up
to nodename DATAMOVER1
2012-09-25      11:40:27        ANE4142I   virtual machine NODE2 backed up
to nodename DATAMOVER1
2012-09-25      11:40:27        ANE4143I Total number of virtual machines
failed: 0



Regards,
Shawn
________________________________________________
Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or
partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. BNP PARIBAS (and its
subsidiaries) shall (will) not therefore be liable for the message if
modified. Please note that certain functions and services for BNP Paribas
may be performed by BNP Paribas RCC, Inc.



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or
partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. BNP PARIBAS (and its
subsidiaries) shall (will) not therefore be liable for the message if
modified. Please note that certain functions and services for BNP Paribas
may be performed by BNP Paribas RCC, Inc.

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