Networker

Re: [Networker] EDL with Embedded Networker Storage Node

2008-09-09 11:30:37
Subject: Re: [Networker] EDL with Embedded Networker Storage Node
From: Bruce Breidall <Bruce.Breidall AT CONCUR DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 9 Sep 2008 08:17:21 -0700
Thanks for the valuable input. Too bad there is always something that is
not covered in the sales pitch. Hopefully the pros have outweighed the
cons for your implementation.


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of brerrabbit
Sent: Monday, September 08, 2008 10:06 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] EDL with Embedded Networker Storage Node

Bruce Breidall wrote:
> There is a web based java gui to manage the CDL/EDL. Should have been
> installed with the units. Very good application.
> 


I agree, there is a very good GUI application to manage the EDL, but
what's missing is a good way to manage the embedded storage node.  For
example, if I want to run an inquire command to get a listing of the
scsi devices, serial numbers, etc visible to the storage node, or if I'm
troubleshooting drive behavior with mt, I have to have EMC support open
an ssh session and have *them* login as root, as they will not hand out
that password.  I've heard, and we are trying to get this set up at our
site, that if you ask your TC nicely, he/she can have someone from EMC
set up a non-root linux user that has permission to run some of the
commands like inquire from the linux environment/embedded storage node.

This is one of the few medium grade annoyances I have with the EDL.
Another one is that, while there is a command-line interface to generate
reports about the EDL utilization, you have to log in to the GUI to get
them.  In a large environment I want to script and schedule that and
can't because of a design oversite.

One other comment about using the embedded storage node and cloning.
Assuming that a) your environment uses a shared-storage node to backup
up to the VTL and b) your budget allows for the licenses, I strongly
recommend that you zone the shared storage node to also see the physical
tape library, i.e. the embedded storage can see the VTL and the physical
library and so can the shared storage node.  The reason for this is
that, in the event that you have a connectivity problem between the ESN
and the PTL, you can clone from the shared storage node.  Clones from
the shared storage node may not happen as quickly, but the added
flexibility is well worth the minor cost. (Yes, we learned this the hard
way!)......

HTH 
-brerrabbit

+----------------------------------------------------------------------
|This was sent by drhulme AT tarrantcounty DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER