2009-07-03 03:14 AM
Is this a new device you are trying to get to work or a working system with an error message in PM you are not sure about?
Is the library online?
Also on the filer try
Also I have an issue with NDMP traffic routing via e0M and the main VIF. This killed NDMP but it looked like it was running slow. Fixed with
options ndmpd.preferred_interface vif1
Hope it helps
2009-08-05 05:32 AM
we are experinceing some issues with restore done with DFM(OM).
We want to restore from a standard Snapvault and receive "NDMP communication error: NDMP_DATA_GET_STATE: 0x2 (The device is in use)".
Sorry for the 'blackouts' but our customer is picky on information sharing...
Any kind of info welcome.
Thanks and have a nice day
2010-01-05 05:53 AM
We also have this problem sometimes. In all cases the data seemes to be restored correctly.
I would also like to know why "device is busy" is reported and if this has any consequences.
2011-08-12 02:06 AM
I've run into the same problem... but in our case for this directory, no data is restored!
Getting the warning for the last 67 minutes, while nothing else is using the filesystem on both the snapvault filer's volume and the destination volume (was NFS mounted, but I unmounted it with no visible effect on the restore).
DFM version is 4.0.2.
2011-08-17 02:11 AM
Hi Berks, Elmar,
During restore operations from SnapVault, Qtree SnapMirror, or Volume Snapmirror secondaries will throw a benign warning message saying "NDMP_DATA_GET_STATE: 0x2 (The device is in use)." This warning by itself will not cause the restore operation for fail.
This warning message is not critical and can be ignored or you can upgrade to Oncommand 5.0 where the fix for Burt 377559 is available.