Greg,
What you described below is in line with what I see. My linux client's don't
show the error about writing to the temp file, but my windows clients do. I
imagine that if our Networker server was running on linux, I wouldn't see the
errors on the server side either.
Also, to add to this, I'm now having problems with savepnc. I've been
babysitting our backups all night (it's now 4:50 AM), and I've noticed that on
our main linux Oracle DB servers that savepnpc is not working reliably.
What happens is that the nsrpre command get's run successfully, then after a
couple of minutes, the nsrpst script runs, but the backups haven't even
started, let alone finished yet. Here's what's in the savepnpc.log file on out
client:
09/05/2009 04:25:43 AM preclntsave: Starting up the precmds.
09/05/2009 04:32:08 AM preclntsave: All command(s) ran successfully.
09/05/2009 04:33:08 AM pstclntsave: Client is not active in the worklist.
09/05/2009 04:33:08 AM pstclntsave: All savesets on the worklist are done.
09/05/2009 04:33:08 AM pstclntsave: Starting up the pstcmds.
09/05/2009 04:34:27 AM pstclntsave: Client's backup did not start.
09/05/2009 04:34:27 AM pstclntsave: Savegroup may have aborted.
09/05/2009 04:34:27 AM pstclntsave: Please check if some saves were aborted.
09/05/2009 04:34:27 AM pstclntsave: Starting up the pstcmds.
09/05/2009 04:36:13 AM pstclntsave: All command(s) ran successfully.
09/05/2009 04:36:13 AM pstclntsave: Exited.
The abort is from where I manually aborted the group. So far, I'm seeing this
on all my linux clients. I haven't had time to check our Windows servers
(mostly because it's almost 5:00am)
I'm really starting to get disappointed in Networker since EMC bought them.
The whole 7.x series has just been riddled with bugs and I regret upgrading
from the 6.x series even though it's no longer support. But it just worked.
I think I'm going to have to ditch Networker here soon because of these issues.
getling wrote:
> Dave,
>
> My networker server, storage node and this one client are the only ones on
> 7.4.5 - everything else is still on 7.4.4 (I had JUST upgraded the
> environment when 7.4.5 was released). The server and storage node are RHEL4
> and are not exhibiting the error, while the client is w2k3 SE R2. To clear
> the error, we shut down the client process, moved the tmp folder, removed the
> global directive from the client definition, then restarted the client
> service. We also noticed that even if the directive was applied, it would
> succeed without errors for the first backup after this process (moving tmp
> and restarting the service).
>
> So to me, it clearly looks related directly to 7.4.5, and at least for me
> only on the Windows side.
>
> Sorry I don't have more info at this second - the students return on Tuesday
> and we are also finally making the Novell->AD transition so we are a bit busy
> around here!
>
> Regards,
> Greg
>
> ------------------------------
>
> Date: Thu, 3 Sep 2009 15:31:52 -0400
> From: dfields <networker-forum < at > BACKUPCENTRAL.COM>
> Subject: Errors after upgrading to 7.4SP5
>
> Greg,
>
> Thanks for the reply. I've got a bit more information on this today. I've
> noticed that I'm getting these errors on both our Windows clients and our
> Network server now. On the clients, the errors are in opening the tmp file
> wherever the client is installed "c:\program files\legato\nsr\tmp". The
> server side errors are being generated because it can't create tmp files
> where the server software is installed, in my case d:\nsr\tmp.
>
> I tried turning off directives for one of my clients and ran a test backup,
> but that didn't seem to completely solve the issue. I didn't get error
> messages from the client about not being able to make the tmp files, but I
> still got them on the backup server.
>
> I've also noticed that older clients (7.4.sp1) don't produce the client side
> error messages. But even with an older client, I'm still getting the error
> on the server side.
>
> In your case, are your errors on the client (and if so, what client version
> are you using?). If you've only got on client that has the 7.4sp5 client
> software installed, that would explain why you only have problems with one
> client. And are you seeing errors about creating the tmp files on the
> Networker server itself?
>
> Thanks,
>
> Dave
>
>
>
> getling wrote:
>
>
> >
> > > David,
> > >
> > > I have seen the same behaviour, but it is limited to one single windows
> > > client (actually a new client). I have a case open with EMC that I need
> > > to keep working on, but we have narrowed it down to the fact that the
> > > local machine is having issues related to writing the global directives
> > > to disk (which is what you will likely see if you open those files on the
> > > client - they DO exist). You can test it by disabling the directive for
> > > the client and running a backup. The next steps they are walking me
> > > through though reek of workaround rather than fix: last one (which I
> > > refused) was to give the client administrator rights in my server user
> > > group (um, no), current one is to create local directives (which i will
> > > do for testing purposes). If you contact EMC, reference my service
> > > request SR: 31088598.
> > >
> > > Greg
> > > ------------------------------
> > >
> > >
> > > Greg Etling <getling < at > stern.nyu.edu <mailto:getling < at >
> > > stern.nyu.edu>>
> > > Systems Administrator
> > > Stern IT Enterprise Operations
> > > NYU Stern School of Business
> > >
> > >
> > > ------------------------------
> > >
> > > Date: Wed, 2 Sep 2009 16:02:37 -0400
> > > From: dfields <networker-forum < at > BACKUPCENTRAL.COM>
> > > Subject: Errors after upgrading to 7.4SP5
> > >
> > > We just upgraded our Networker server and most of our clients to 7.4SP5.
> > > So far everything seems to be OK, except that now I'm getting the
> > > following error in my Windows and even my Linux/Unix clients:
> > >
> > > * xxx.xxxx.com:C:\ save: There was an error creating the file:
> > > "D:\nsr\tmp\sd000001" errno: 17.
> > >
> > >
> > > The Networker software is stored on the D: drive of a Windows 2003
> > > server, which is where it looks like it's having trouble writing these
> > > files.
> > >
> > > I've tried cleaning up d:\nsr\tmp on the Networker server, but that
> > > doesn't seem to fix the problem.
> > >
> > > Anyone else seen this?
> > >
> > > +----------------------------------------------------------------------
> > > |This was sent by david.fields < at > acs-inc.com via Backup Central.
> > > |Forward SPAM to abuse < at > backupcentral.com.
> > > +----------------------------------------------------------------------
> > >
> > >
> > > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >
> > >
> > > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >
> >
> >
>
>
> +----------------------------------------------------------------------
> |This was sent by david.fields < at > acs-inc.com via Backup Central.
> |Forward SPAM to abuse < at > backupcentral.com.
> +----------------------------------------------------------------------
>
>
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
>
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
+----------------------------------------------------------------------
|This was sent by david.fields AT acs-inc 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
|