- The mtree created for MFR on the secondary Data Domain was created with the name of the NetWorker server by a user other than the DDBoost user creating the device
- NetWorker needs to create an mtree with the name of the NetWorker server when writing to Data Domain. If done manually, there could be an issue. - The Data Domain will only allow the owner to write to the mtree.
- Rename the mtree --- The current owner of the mtree is not changed and can still access the existing data --- Simply changing the mtree owner to the DDBoost user will create issues with accessing the existing data
- Creation of the device in NetWorker will create the mtree on the Data Domain properly with the DDBoost user as the owner
Is was a mix of everything. The mtree of the NetWorker server was created due to the failure. But the permissions were wrong. So I corrected them. And also was the boost user locked.
bingo.1
1 Rookie
•
2430 Posts
5310
0
Posted February 20th, 2018 07:00
Verify that the user is listed for the m-tree with the commands found in the document.
Use ddboost storage show to do that.
Now, I do not know what will show up if there is no m-tree yet.
If this is true, install one via the DD admin GUI and assign the user here.
Then try to add the user to the mtree (with an 'admin' role).