Veritas CloudPoint Release Notes
- Getting help
- Known issues
- Fixed issues
Disk-level snapshot restore fails if MongoDB configuration file is at a non-default location (13130)
If you configure a MongoDB instance from a configuration file that is located at a non-default location, then a restore operation for the MongoDB disk-level snapshot fails with the following error:
Failed to unmount /mongodata (umount: /mongodata: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) )
There is no known workaround for this issue. As an alternative, you can launch MongoDB instances using a configuration file from the default location; snapshot restore does not fail for such instances.