Veritas-bu

[Veritas-bu] Aptare vs. NB 6.0 NOM reporting

2006-08-11 08:30:14
Subject: [Veritas-bu] Aptare vs. NB 6.0 NOM reporting
From: pkeating at bank-banque-canada.ca (Paul Keating)
Date: Fri, 11 Aug 2006 08:30:14 -0400

-- 


> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu 
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf 
> Of Greenberg, Katherine A
>  
> The thing I really like about Aptare is it's *real time* 
> capability. 

However, it does not give you *real time* data untill after the job has
completed.
In my opinion, that isn't exactly "real time".
;o)
No indicators are provided, as to the status of running jobs.
ie, jobs that have been running for 24 hours transferring 100KB/s,
because of a network issue, or Netbackup mistakenly mounted the tape in
a NDMP attached drive and is routing data all over kingdom come.

> I haven't played with NOM much. And I like it for what it is... an
> OPERATIONS tool.

Yes, if an operations tool is what you need, then Aptare is overpowered.
I've had Aptare Storage Console in production since the beginning of the
year, and to be honest, it just sits there and runs. We needed something
that would archive backup results for audit purposes....and in the case
we have to go back and provide that, it's there, but I haven't had the
time to look into whatever other "value add" it provides. Our ops folks
are still using Activity monitor, because they need to see *running*
jobs, and be able to run or re-run jobs.

> However, if you want to be able to do things like
> trending, etc. I would look at one of the reporting specific add-on
> tools not made by Veritas.

Yes, it seems Aptare does this well, from what I've been looking at.

One other issue we have is that we're using Inline Tape Copy. So each
job that runs has 3 jobids. A master, that holds no information (no tape
ID, no KB transferred, nothing) and then two more jobs....one job has
all the information for both compies, ie, both tape IDs, etc, then the
third job has the info for the "second copy" job
only......unfortunately, this is reported statistically in Aptare
Storage Console as 3 jobs....so there is some confusion.

Ie, when counting %-age successful, etc, we have to look at the fact
that NDMP jobs, and some hot database jobs are only one job, but most
network jobs are 2 jobs....and from what I've seen, not that I've dug
too deeply, it doesn't seem to report on the integrity of
duplications....

So for network jobs that write 2 copies with ITC, we get reporting on
the main site and DR site backup....but anything that's written to one
site then duplicated....the duplication is missed by Aptare.

Just a few little issues....A great product for what it does...possibly
overpowered in some areas, for our current requirements, yet missing a
few items we'd like to have.

We'll be looking at NOM with our 6.0 testing, to determine if the cost
of Aptare is justified for what we need.

Paul
-------------- next part --------------
====================================================================================

La version fran?aise suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le pr?sent courriel peut contenir de l'information privil?gi?e ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires d?sign?s est interdite Si vous 
recevez
ce courriel par erreur, veuillez le supprimer imm?diatement et envoyer sans 
d?lai ?
l'exp?diteur un message ?lectronique pour l'aviser que vous avez ?limin? de 
votre
ordinateur toute copie du courriel re?u.