SearchFAQMemberlist Log in
Reply to topic Page 2 of 2
Goto page Previous  1, 2
7241:savegrp: nsrim run recently, skipping
Author Message
Post 7241:savegrp: nsrim run recently, skipping 
You can also run the following command to check what files are in the
online index of the client.

nsrinfo client_name > index.txt

Once you open the file, check the dates against the files as to when it was
backedup.

Thanks & Regards

Akshay Bhumkar
+91-9342420444
* < at > k$h < at > y*



On Fri, Nov 18, 2011 at 1:47 AM, Tim Mooney <Tim.Mooney < at > ndsu.edu> wrote:

In regard to: [Networker] 7241:savegrp: nsrim run recently, skipping,...:


I was able to backup one of the savesets

F40115L4 ****** 11/17/11 6 KB full /factiva

So i think if we put the directories in Saveset box we can have backup,
but question remains same: Why it failed with Saveset: All?


In one of your earlier posts, you mentioned that the client was running
the networker 7.4.1 client.

I don't think 7.4.x is still supported, but even if it is, the early
releases in 7.4.x had a number of problems. If you're going to use
the 7.4.x series, I highly recommend you upgrade to the last point
release, probably 7.4.5.something.

Beyond that, there are several things that can cause "nothing to save"
messages. I've seen it in several different instances over the years,
sometimes because the version of the client software didn't correctly
support the OS & version of the client, and other times because of client
index corruption or because the client index data was being saved to
the wrong index. You may wish to try a

nsrck -L6 clientname

on your networker server, to do all available index checks for that client
index.

There was an earlier suggestion, I believe from Chester, to use
(on the networker server)

savegrp -pvvvv -c your_client_name_here your_client_group_here

and I also recommend you try that. Once that completes, whether it works
or not, have the admin on the client run

nsr_render_logs /nsr/logs/daemon.raw

and send you the output. That might also contain a clue as to what the
problem is.

Tim
--
Tim Mooney Tim.Mooney < at > ndsu.edu
Enterprise Computing & Infrastructure 701-231-1076(Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164



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



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Display posts from previous:
Reply to topic Page 2 of 2
Goto page Previous  1, 2
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB