Run 'mminfo -m' to see what the media database says for these volumes. This will help you see if the problem is in the media database or if it's related to the NMC. Also, for one of the affected volumes, you can run
mminfo -q "volume=[name of volume here]" -r ssid,client,name,totalsize,ssflags,sumflags,volflags,volretent
This will confirm for you that there is data on the volume and give you more details on what data there is.
thanks for response; we are sure that data is and has been written to these volumes. So it does not look like a database issue, more like a NMC problem
May be the issue with the NMC or the Java if you checked that data is on the volume from the mminfo command mentioned by Bobby Cogan , So what is your Java version you are running for NMC ? Also try to clear the Java Cache from Control Panel > Java > Temporary Internet Files > Settings... > Delete Files.
If clearing the cache does not work and volumes are still being reported as 0% used this may be related to an issue we are investigating under Engineering reference NW135701. Please reference this Escalation when you raise the SR and ensure you quote the NetWorker version including the build number.
Please raise an SR with EMC Support and attach: -
Screenshot from GUI displaying some affected volumes.
mminfo command showing the MDB records different to GUI
If we require an export of the MDB we will supply instructions on how to do this.
yes it was fixed by changing the language locale LC_ALL in the end. EMC support suggested the following;-
======
try starting gstd in a shell where the locale has been set to English: "setenv LC_ALL C" (it may be sufficient to set "LC_NUMERIC", but first try setting "LC_ALL"). Only gstd need be started in that shell; all other Networker processes can be started in the default (French) locale. Setting the locale to English in a shell only affects the processes started in that shell.
coganb
736 Posts
1426
0
Posted February 29th, 2012 02:00
Hi,
Run 'mminfo -m' to see what the media database says for these volumes. This will help you see if the problem is in the media database or if it's related to the NMC. Also, for one of the affected volumes, you can run
mminfo -q "volume=[name of volume here]" -r ssid,client,name,totalsize,ssflags,sumflags,volflags,volretent
This will confirm for you that there is data on the volume and give you more details on what data there is.
-Bobby