This has happened to me in the past...server is UNIX...every time we
would have a power down when we would bring the server back up for some
reason it would switch back and forth between long name and short name.
In each of your subdirectories you have db6/*.* ?? Check your host
file too...
Have you had problems trying to put indexes back out there? I did and
still do. nsrck -L7 I still have problems trying to get some of my
indexes back...
Basically I had to copy all directories up...I got notes from Legato
support. Here is what I had to do:
ID: legato8379
Domain: primus_owner
Solution Class: solution
Fact
-------
NetWorker
Symptom
-------
Index is nested
Symptom
-------
Trying to recover but can't see the data that was backed up
Symptom
-------
Index directory is nested:
/nsr/index/FQDN/hostname/FQDN/hostname/FQDN/hostname
Symptom
-------
Volume is 'Unknown' when recovering
Symptom
-------
Error: 'No index is available'
Symptom
-------
Multiple index directories exist for this client
Cause
-------
There are several reasons why this might happen: the client_name was
changed from the shortname to the Fully Qualified Domain Name (also
called FQDN or long name) within the GUI, the hostname was changed,
Technical Bulletin #138 and/or #364 were not followed when renaming the
server/client
Fix
-------
Click Here To Go Back
1) Shutdown NetWorker
2) Move/Copy all files with an .k0, .k1 or .rec from the nested db6
folders into the first db6 folder of the client
/nsr/index/client_name/db6
3) Clean-up the directories so that it is back to /nsr/index/client_name
3) Restart NetWorker
4) Index path may be entered in the Client Resource, however, it should
not be necessary
Kathleen Scalise
Asst. Vice President
Network Services and Technology Support
Merrill Lynch - Jacksonville, Florida
Phone: 904.218.5139
Fax: 904.218.5445
kathleen_scalise AT ml DOT com
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Ultra Kiasu
Sent: Thursday, February 02, 2006 2:35 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Directory Depth for Index getting deeper for
certain clients?
Hi,
I don't really know how come my index for one client directory depth is
getting deeper?
I am using Legato NetWorker 7.1.2.Build.325 Business Edition/8
"raphael" is my backup server, it would mount network storage disk image
and perform local backup. full hostname with domain is
"raphael.mydomain.com"
/nsr/index/raphael/raphael.mydomain.com/raphael/raphael.raphael.mydomain
.com/raphael/db6/*.*
While other configured clients had shallow directory depth
/nsr/index/rx2600/db6/*.*
Anyone know what cause this erratic behaviour?
Thanks
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
--------------------------------------------------------
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
--------------------------------------------------------
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
|
