We just got NW 7.3 and AS 3.1 running in our test environment on two separate
boxes and things are looking good so far (only been 4 days). We are now using
the DMI interface versus the CAPI interface, so we'll see how much 'better' the
'integration' is between the two products.
Cheers,
Jim
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Siobhan Ellis
Sent: January 5, 2006 12:55 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Networker 7.3 - Anyone look into using this with
AlphaStor yet?
NMC does not have to be on the NW server. Indeed, if you have multiple
NetWorker servers, it should be on a seperate machine.
Siobhán Ellis
Principal Technology Consultant
ENSTOR Pty Ltd
Level 10, 118 Alfred St
Milsons Point
NSW 2061
Australia
Mobile: +61 424 750 544
Phone: +61 2 9900 2100
Fax: +61 2 9900 2199
e-mail: siobhan.ellis AT enstor.com DOT au
web: http://www.enstor.com.au
>>> Tim.Kimball AT BRASS DOT COM 5/01/2006 4:49:26 pm >>>
Thanks for the heads up. I had the chance to grab copies of the release notes
for NW 7.1.3, 7.3, and AS 3.1 and go over the basics.
Mixing databases will not be an issue in our case, AS was installed on one of
our Storage Nodes and I'd put NMC on the Server. We also have hopes to remove
AS at the first opportunity, perhaps by spinning off any remaining active DLT
tapes post-migration onto a couple Autoloaders or something. An M1400 instead
of the L700 would be nice right about now... ;)
There is conflicting evidence regarding if AS and NMS can reside on the same
server. The AS release docs (Nov 2005) says no, due to a database port
conflict. The NW 7.3 docs (Dec 2005) actually says yes, as long as you follow
the included procedure to change the NMC database port. *shrug* Again,
probably best to leave AS on the Storage Node.
As for 'supporting later,' I can probably wait a little while. I'm actually
using the Sun EBS re-branded version, so I have to wait for Sun patches and/or
packages anyway; That's normally another 2-3 months unless it got fast-tracked
or done at the same time.
My main draw to 7.3 at the moment is the different retention times for clones
(which I can script around temporarily). The other big thing is to have a
stable AlphaStor in the interim, which apparently 3.1 is (even has FireFox
support, though it already does actually from my own testing - more stable than
IE too).
I'll be calling Legato and/or Sun probably on Friday to get details on this
(for planning), and will forward any clarifications I get.
--TSK
=====
Timothy S. Kimball
=====
-----Original Message-----
From: Wood, R A (Bob) [mailto:WoodR AT chevron DOT com]
Sent: Wednesday, January 04, 2006 5:00 AM
To: Legato NetWorker discussion; Kimball, Tim
Subject: RE: [Networker] Networker 7.3 - Anyone look into using this with
AlphaStor yet?
Tim,
FYI, AlphaStor documentation states that AlphaStor and NMC can't be
installed on same machine (both use host name as database engine
name)
I haven't heard of anyone testing 7.3 with AlphaStor (I get the feeling that
AlphaStor will not be supported until later, not sure where I get that feeling
from, probably something that was said during the initial beta selection).
Bob
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Tim.Kimball AT BRASS DOT COM
Sent: 03 January 2006 10:08
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Networker 7.3 - Anyone look into using this with AlphaStor
yet?
With the recent discussion over 7.3's caveats, I'm nervous now that the changes
will give me grief with our AlphaStor environment.
Since it is now 'released,' are any of the beta testers also AlphaStor users
who can comment on the upgrade? There are features to this Networker upgrade
that are very much needed to save us decent money on tapes, but if its going to
conflict on a Java front this is going to be a problem.
Also, I heard something about a new version of AlphaStor (3.1 I think)?
Thanks,
--TSK
=====
Timothy S. Kimball
=====
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 wit 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
wit 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
wit 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
wit 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
|