On Monday 11 March 2013 14:08:10 Michael Leone wrote:
> > > CRASH. Everything came down hard.  Luckily (?)  the mains kicked in 
> right 
> > > around then. And it took so long for the main network switch to come 
> up, 
> > > that DNS resolution was failing (among other things). So NW assigned 
> new 
> > > client IDs to it's clients. And (apparently) purged a lot of histiory 
> > > while it was at it, since my log and index drive went from 8G free to 
> 85G 
> > > free ...
> > 
> > Think your analyzis of the failure is not quite right...
> > 
> > Why would Networker assign new Client ID:s because of a DNS failure?
> > He will in my opinion never really change those.
> 
> Extracts from the log:
> 
> nsrd SYSTEM warning: DNS lookup failed for pssql5: No such host is known. 
> 
> nsrmmdbd error, Unable to mount D:\Program Files\Legato\nsr\mm\mmvolume6: 
> database was not shutdown cleanly 
> 
> nsrmmdbd Creating new client id mapping for client:pssql5, client 
> id:24661238-00000004-487b744d-487baf31-00130000-0a400744 name:pssql5 
> 
> So it's possible it was the corruption of not shutting down the database.

Yes, That makes more sense. He couldn't find an old clientid (also stored in 
mm) and
decided that we need one.

> 
> > Could it be that you use NTP and the Networker time was something far
> > in the future instead?
> > That would for sure expire savesets.
> 
> I do not. And the log shows a proper timestamp.

Ok. Then just pure corruption.

Thanks!
Dag