To follow up with what has happened... This appears to be fallout from a raid
card issue we had
two weeks ago. Somehow, the index path on these two clients got reverted to
the value it had
10 months ago when the power had to be removed because the system was
completely unresponsive
(the root filesystem went read-only because the wrong disk in a raid-1 pair got
disabled by a
firmware bug).
EMC assisted me in recovering the two indexes and we've verified it is working
properly now.
Frank
On 3/29/10 10:40 AM, Francis Swasey wrote:
> Thank you... I have walked through the process of determining the full and
> 3's an 9's that were
> made and recovered the full, the last 3, and the last two 9's ... and found
> that it was just
> the last two 9's that had suddenly the idea of the "old" path for the indexes
> file.... so, I've
> opened up a sev 1 with EMC -- because nobody told NetWorker to go back to
> that path, it just
> decided it should all on its own.
>
> Frank
>
> On 3/29/10 10:36 AM, Venkat Tudi wrote:
>> find out when the last full of index is done. These indexes are saved
>> under the backup server indexes
>> index:servername
>>
>> do a NSRCK -L7 -t "Date and time" clientname
>>
>> Date and time has to be exact.
>>
>> This will bring back the indexes. Make sure the tapes are available.
>>
>> -Venkat
>>
>> On Mon, Mar 29, 2010 at 8:39 AM, Francis Swasey <Frank.Swasey AT uvm DOT edu
>> <mailto:Frank.Swasey AT uvm DOT edu>> wrote:
>>
>> Linux RHEL5 (64-bit), NetWorker 7.4sp5.2
>>
>> The root filesystem started alerting last night that it was getting
>> full and in researching
>> what was going on, I discovered a temporary directory that was only
>> used when we moved from
>> Solaris to Linux last May... It was used to hold the indexes for
>> our two largest systems
>> (because we ran out of space on the old Solaris system and split up
>> the indexes to get us
>> through until we replaced the server)...
>>
>> Anyway... as I *know* I updated networker to not use those paths
>> anymore back in May, I deleted
>> the data. This morning, I see emails from the NetWorker server
>> (starting AFTER I deleted the
>> directory tree) that state the filesystem holding the index for
>> these two systems is getting
>> full. Investigating, I find that sure enough, NetWorker has decided
>> that the indexes for these
>> two systems were in that directory tree.
>>
>> I've updated networker to to tell it that the indexes do NOT live in
>> that tree! Now, I'm
>> wondering what do I need to do to recover the data that I deleted?
>> I have not yet restarted
>> the server, so it may still have the data in memory (or still have
>> open file pointers to data
>> on disk).
>>
>> Thanks for any ideas.
>>
>> --
>> Frank Swasey | http://www.uvm.edu/~fcs
>> Sr Systems Administrator | Always remember: You are UNIQUE,
>> University of Vermont | just like everyone else.
>> "I am not young enough to know everything." - Oscar Wilde (1854-1900)
>>
>> To sign off this list, send email to listserv AT listserv.temple DOT edu
>> <mailto: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
>> <mailto: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
>> <http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER>
>>
>>
>>
>>
>> --
>> Venkat Tudi
>>
>
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
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
|
