Re: [Networker] legato + exchange module failing remotely

Bob, I find it INCONCEIVABLE that you could have an open ticket with EMC
for this problem for more than 30 days. What incident level did you
assign the ticket?

Production Exchange server that would have been a level 1 or 2 ticket
for me. Which means they would have called me back within 1 hour or 4
hours, but even my level 3 questions are answered within 24 hours
usually. If I were you, I would consider finding out who the tech
support team leader is for your region.

I didn't mention their supervisor BERNIE.. I have to admit he is the one
guy on the team I don't like so much so I thought his name should be
Richard and then abbreviated! But on the other team, my liking him is
not a requirement for him doing a good job. His team is awesome. Maybe
the Richard abbreviation thing is a requirement for the great team,
/shrug who knows. Good Job building the team Bernie!

I swear Bernie's team should shower me with gifts for speaking out for
them, but the fact is they truly are that good. On another point, they
call the USA a mixing pot... But dig the cool names from my "FORMER" EMC
tech support team in Canada, eh? Don't get confused by the SUE, she was
Filipina!

/Waving Hi Srood, Mohammed, Sue, Wail & Carlos - Not a bob, mark, dave
or Eddie among them. (what the heck no Dave?)

I love to joke about Canadians during football season, baseball season
well anything except Hockey Season (they take that stuff serious!) But
when it comes to tech support the Canadian team we had was top shelf.
They just went through a re-org so I don't know the new team... Yet!

Semper Fidelis et Paratus! /ALE

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of bob flynn
> Sent: Thursday, June 29, 2006 12:31 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] legato + exchange module failing remotely
> 
> Adding nsrxchsv to the backup command is the solution.
> 
> Many thanks for all the replies.
> 
> fyi,
> 
> I have had an outstanding ticket with Legato for the last 
> month to fix this. I have sent an email to this mailing list 
> and have the answer in 10 minutes.
> 
> -Bob
> 
> Browning, David wrote:
> 
> >Do you have the command nsrxchsv in the backup command field. 
> >
> >If you look at your configured client, you must have this command 
> >entered, and to get there, you go manage clients, and then 
> click on the
> >client, and look under the "remote" tab.   There is a field named
> >"backup command".   Make sure you have nsrxchsv in the field. 
> >
> >David M. Browning Jr.
> >LSUHSC Enterprise Network Operations/Help Desk
> >(504) 568-4364 (Direct)
> >(504) 654-7520 (BlackBerry number)
> >
> >
> >-----Original Message-----
> >From: Legato NetWorker discussion 
> >[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> >On Behalf Of bob flynn
> >Sent: Thursday, June 29, 2006 11:03 AM
> >To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> >Subject: [Networker] legato + exchange module failing remotely
> >
> >Hi,
> >
> >I have the following configuration
> >
> >    * Exchange 2003 server
> >    * Legato 7.2.1 Server
> >    * Current Legato client and Exchange module installed on exchange
> >      server.
> >
> >I can backup the exchange server manually from the command 
> line on the 
> >exchange server.
> >
> >When I attempt to run a scheduled backup, it fails.
> >
> >I have verified that the backup of non exchange components 
> works, so it 
> >seems to be either not parsing the exchange request correctly or its 
> >incorrectly formed on my side.
> >
> >An example output;
> >
> >NetWorker savegroup: (alert) Default completed, total 1 client(s), 0
> >Hostname(s) Unresolved, 1 Failed, 0 Succeeded. (exduba Failed) Start 
> >time: Wed May 31 15:28:34 2006 End time: Wed May 31 15:28:41 2006
> >
> >--- Unsuccessful Save Sets ---
> >
> >* exduba:MSEXCH:IS 1 retry attempted
> >* exduba:MSEXCH:IS save: Diagnostic: This client is not licensed for 
> >VSS.
> >* exduba:MSEXCH:IS save: MSEXCH:IS: No such file or directory
> >
> >--- Successful Save Sets ---
> >
> >* exduba:c:\dell save: Diagnostic: This client is not 
> licensed for VSS.
> >* exduba:c:\dell save: Diagnostic: c:\dell will be saved without a 
> >snapshot being taken.
> >exduba: c:\dell level=full, 9245 KB 00:00:01 15 files
> >mars: index:exduba level=full, 13 KB 00:00:00 7 files
> >
> >so the none exchange saveset runs ok, its the exchange saveset that 
> >seems not to trigger the exchange add on ?
> >
> >Any help appreciated.
> >
> >-Bob
> >
> >
> >
> >The information contained in this e-mail and in any attachments is 
> >confidential and is designated solely for the attention of 
> the intended 
> >recipient(s). If you are not an intended recipient, you must 
> not use, 
> >disclose, copy, distribute or retain this e-mail or any part 
> thereof. 
> >If you have received this e-mail in error, please notify the 
> sender by 
> >return e-mail and delete all copies of this e-mail from your 
> computer 
> >system(s).
> >Please direct any additional queries to: communications AT s3group DOT com.
> >Thank You.
> >
> >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
> >  
> >
> 
> 
> The information contained in this e-mail and in any 
> attachments is confidential and is designated solely for the 
> attention of the intended recipient(s). If you are not an 
> intended recipient, you must not use, disclose, copy, 
> distribute or retain this e-mail or any part thereof. If you 
> have received this e-mail in error, please notify the sender 
> by return e-mail and delete all copies of this e-mail from 
> your computer system(s).
> Please direct any additional queries to: communications AT s3group DOT com.
> Thank You.
> 
> 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