I keep getting this error when trying to backup up the schema. We

[mikecaz33]

&nbsp;&nbsp;&nbsp;I keep getting this error when trying to backup up the schema.&nbsp;&nbsp;&nbsp;Went to veritas site and they said to run dsrepair 4.47 or higher with reapir laocal database.&nbsp;&nbsp;&nbsp;But that did not have any effect.&nbsp;&nbsp;&nbsp;Any help would be greatly appreciated.<br><br>4.11/5 mixed enviroment<br>backup exec 8<br><br>Mike Caswell<br>Network Administrator<br>CFC

 

[mikecaz33]

sorry that error is &quot;/ is a corrupt directory&quot;

 

[Zelandakh]

Have you got any Macs on your network?

 

[mikecaz33]

yeah we have some macs on our network, a seperate segment though

 

[Zelandakh]

The reason for asking is that if they put any data on the server, chances are that it is a Mac file that is causing the problem. If not, I'll scratch my head again.

 

[mikecaz33]

&nbsp;&nbsp;&nbsp;The macs do not write any data to the servers that are having the problem.&nbsp;&nbsp;&nbsp;They are isolated from novell.&nbsp;&nbsp;Run on an NT server.&nbsp;&nbsp;&nbsp;This has all of us here completely stumped..&nbsp;&nbsp;&nbsp;Thanks for any help

 

[Zelandakh]

This is backup exec for Novell or NT? I'm confused by your last reply.

 

[mikecaz33]

&nbsp;&nbsp;&nbsp;It is backup exec for netware v 8.0..&nbsp;&nbsp;the macs are running on an nt server.&nbsp;&nbsp;&nbsp;Was trying to say that they had nothing to do with the novell side of our network.&nbsp;&nbsp;&nbsp;sorry about the confusion.&nbsp;&nbsp;&nbsp;Thanks

 

[Zelandakh]

In that case, I'd go for the corrupted directory and/or pointer on the disk.<br><br>Do you have any idea where the directory is - does any of the log file get written before the problem arises so that you can narrow down where abouts the directory is located?<br><br>Once you can pare down that way, try excluding a parent directory from each backup until you find the back up works. Then add a child directory until it does not. Now you know fairly accurately where the troubled directory is you can take steps to re create it. Failing that, use something like Norton Utilities and get it to check b-tree leaves or their Novell equivalent.