Please consider moving this question to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and questions can go unanswered for a long time. You can do so by selecting "Move" under ACTIONS along the right. Then search for and select: "NetWorker Support Forum" which would be the most relevant for this question. There is also a recent post demonstrating the steps to do the same:
Seeing though that over a month has elapsed since you posted, maybe you have already found the answer? If so, consider sharing the resolution and also marking the question as "Answered" so that it can help others that have the same question. If not, once relocated, it will then have more visibility by the community of dedicated customers, partners, and EMC employees that are eager to assist.
This EldoS CallbackFS driver service error indicates Callback File System manufactured by EldoS is installed on your computer. Please verify whether any EldoS product is installed on your system. If so, please contact EldoS support to install the right driver. If you do not need EldoS products, you can delete them from your system.
Eldos driver is installed with NMM 2.4 and above. This is what facilitates the GLR (Granular Level Recovery).
The way it works is basically that once nsrmmd reads from the Data Domain device or AFTD, Eldos driver will mount a virtual file system (NWFS=NetWorker File System) so that actually there is no need to restore "physically" the data to disk from NW server to Exchange server, as you would do in a RDB restore but instead, the virtual file system will mount the DB you restored, and then you can read from within the "virtually mounted" DB to perform a granular restore.
Now, having this clear, this issue could be because of an actual failure in the installation of GLR feature (GLR installation requires a reboot of the host where NMM is being installed) or some additional issue.
What is the NW version and NMM version and build?
What about NMM Config Checker, did you run it? if so, what is the result? If not please run it and let us know the results.
christopher_ime
4 Operator
•
2K Posts
0
June 26th, 2013 01:00
mehdi-mkacher,
Please consider moving this question to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and questions can go unanswered for a long time. You can do so by selecting "Move" under ACTIONS along the right. Then search for and select: "NetWorker Support Forum" which would be the most relevant for this question. There is also a recent post demonstrating the steps to do the same:
EMC Community Network Frequently Asked Questions
Seeing though that over a month has elapsed since you posted, maybe you have already found the answer? If so, consider sharing the resolution and also marking the question as "Answered" so that it can help others that have the same question. If not, once relocated, it will then have more visibility by the community of dedicated customers, partners, and EMC employees that are eager to assist.
TimQuan
4 Operator
•
1.2K Posts
0
July 1st, 2013 19:00
This EldoS CallbackFS driver service error indicates Callback File System manufactured by EldoS is installed on your computer. Please verify whether any EldoS product is installed on your system. If so, please contact EldoS support to install the right driver. If you do not need EldoS products, you can delete them from your system.
EldoS corporation:
https://www.eldos.com/solutions/product-lines.php
CarlosRojas
1.7K Posts
0
July 3rd, 2013 13:00
Hi all,
Eldos driver is installed with NMM 2.4 and above. This is what facilitates the GLR (Granular Level Recovery).
The way it works is basically that once nsrmmd reads from the Data Domain device or AFTD, Eldos driver will mount a virtual file system (NWFS=NetWorker File System) so that actually there is no need to restore "physically" the data to disk from NW server to Exchange server, as you would do in a RDB restore but instead, the virtual file system will mount the DB you restored, and then you can read from within the "virtually mounted" DB to perform a granular restore.
Now, having this clear, this issue could be because of an actual failure in the installation of GLR feature (GLR installation requires a reboot of the host where NMM is being installed) or some additional issue.
What is the NW version and NMM version and build?
What about NMM Config Checker, did you run it? if so, what is the result? If not please run it and let us know the results.
Thank you,
Carlos