Unsolved
This post is more than 5 years old
76 Posts
0
3938
Networker server has no index
I somehow whacked some scripts on my only NW server. So I thougt I'd just restore them. Recover command returns this: No files have been backed up for this client. No index was found on the server for the path
However the server has been getting backed up and there are indexes listed also. What is going on here?
Here is a sampling
000132 | LTO Ultrium-4 server.domain.com 02/10/12 21:20:25 66 MB 2251677305 cr full index:server.domain.com |
000285 | LTO Ultrium-4 server.domain.com 02/10/12 21:20:25 66 MB 2251677305 cr full index:server.domain.com |
OnsiteFull.0005 adv_file server.domain.com 02/10/12 21:20:25 66 MB 2251677305 cr full index:server.domain.com
OnsiteFull.0005.RO adv_file server.domain.com 02/10/12 21:20:25 66 MB 2251677305 cr full index:server.domain.com
000133 | LTO Ultrium-4 server.domain.com 02/11/12 21:04:19 273 KB 926362675 cr 9 index:server.domain.com |
OnsiteIncremental.0001 adv_file server.domain.com 02/11/12 21:04:19 273 KB 926362675 cr 9 index:server.domain.com
OnsiteIncremental.0001.RO adv_file server.domain.com 02/11/12 21:04:19 273 KB 926362675 cr 9 index:server.domain.com
000133 | LTO Ultrium-4 server.domain.com 02/12/12 21:30:35 2 KB 4047012827 cr 9 index:server.domain.com |
OnsiteIncremental.0002 adv_file server.domain.com 02/12/12 21:30:35 2 KB 4047012827 cr 9 index:server.domain.com
OnsiteIncremental.0002.RO adv_file server.domain.com 02/12/12 21:30:35 2 KB 4047012827 cr 9 index:server.domain.com
000133 | LTO Ultrium-4 server.domain.com 02/13/12 21:31:32 80 KB 2755253652 cr 9 index:server.domain.com |
OnsiteIncremental.0001 adv_file server.domain.com 02/13/12 21:31:32 80 KB 2755253652 cr 9 index:server.domain.com
OnsiteIncremental.0001.RO adv_file server.domain.com 02/13/12 21:31:32 80 KB 2755253652 cr 9 index:server.domain.com
OnsiteIncremental.0001 adv_file server.domain.com 02/14/12 21:30:38 2 KB 1648043742 cr 9 index:server.domain.com
OnsiteIncremental.0001.RO adv_file server.domain.com 02/14/12 21:30:38 2 KB 1648043742 cr 9 index:server.domain.com
UU1607 | LTO Ultrium-4 server.domain.com 02/14/12 21:30:38 2 KB 1648043742 cr 9 index:server.domain.com |
Thierry101
2 Intern
2 Intern
•
326 Posts
0
February 15th, 2012 17:00
what is the output from mminfo?
>mminfo -q client= -r sscreate,volume,ssbrowse,ssretent,clretent,pool,sumsize,ssflags,name
kmkramer25
76 Posts
0
February 16th, 2012 06:00
the list is long, what specifically are you looking for? Here is what I've tried last night
I scanned in the last full of the index
scanner -i -S XXXX -c server.domain.com
nsrck -L6 server.domain.com
nsrck: /dbvol/nsr/index/server.domain.com contains 0 records occupying 0 KB
coganb
736 Posts
0
February 16th, 2012 07:00
Hi,
You might have the wrong date in your nsrck command which would cause this to fail. What you can do is:
mminfo -avot -N index:[client name here]
Get the exact output of this command as the date for your nsrck command:
for example:
nsrck -t "2/2/2011 9:27:59 PM" -L7 [client name]
If you are still having trouble with the indexes, then you might want to bypass them for now and concentrate on just getting your data back first. You can use saveset recover for this:
To recover the saveset without using the client indexes, run the following command:
1) On the server, run:
mminfo -q client=[client_name_here] -r ssid,name,level,savetime,ssbrowse,clretent,ssretent,sumflags,totalsize,clflags -ot > mminfo_output 2>&1
Replace only the client name in this command - everything else stays as it is. Check the resultant file mminfo_output and identify the saveset id (first column) for the saveset that you wish to restore - the savetime in the third column will give you the dates of the backup and the latest backups will be at the bottom of the results.
2) On the client, run (if you don't know the path to the file, you can leave that out, but be sure to have enough space in your destination for the entire saveset (totalsize column from mminfo output)
recover -vvvvv -s [nw_server_name_here] -d [destination_to_recover_to] -S [ssid] [/complete/path/to/file]
for example:
Saveset Recover Unix Example
mkdir /recov
recover -vvvvv -s vm-lego-230 -d "/recov" -S 1725715655 /etc/krb5.conf
-Bobby
kmkramer25
76 Posts
0
February 16th, 2012 07:00
I can't even do this
nsrck -L7 -t 02/01/12 server.domain.com
nsrck: checking index for 'server.domain.com'
9343:nsrck: The file index for client 'server.domain.com' will be recovered.9348:nsrck: The index recovery for 'server.domain.com' failed.39078:nsrck: File index error: can't find index backups for 'server.domain.com' on server 'server'
server.domain.com and server are the same NW server, my only NW server.
kmkramer25
76 Posts
0
February 16th, 2012 08:00
"...
mminfo -avot -N index:[client name here]
Get the exact output of this command as the date for your nsrck command:
for example:
nsrck -t "2/2/2011 9:27:59 PM" -L7 [client name] ..."
This gave the same error.
I am able to recover the data so that is good. I manually ran a backup of the server this morning also and it appears that my NMCASA directive is failing which may be causing my index issue. I removed that directive and the index was updated with the backup for the manual run. I still need to get my old index merged in somehow.