It is strange you see it... dpt is directory prefix table. Try to do nsrck -L6 for that client and see if that makes any difference (if file is gone). I assume when you saw dpt file no backup was active for that index space?
does that file exist after backup completion ? or only while the backup is running ?
- this file should not exist while the backup is running , I think it is one of the index conversation temp files
it should not also grow to that size , it should normally be big , but not that big ! how many directories do you have on the File system that is being backed up ?
Does that file system host any Automatic Build application like Jenkins
I must say that I did see such problem happening , but only when the FS was used by a software automation build/test tools , where the created directory structure is very complex and sometimes "circular"
- if this File size is blocking the operation of the NW server host by filling up the NW server FS , then you must stop the backup or abort the NDMP backup process (nsrndmp_save)
- is this problem consistent ? or only intermittent
The client is a NDMP client.
Yes, we know that from the title of this thread My question was something else.