# Created a new directory in all Managed Nodes, where permission is 777. But yet can't be used as storage path for backup.

**URL:** <https://community.dynatrace.com/t/created-a-new-directory-in-all-managed-nodes-where-permission-is-777-but-yet-cant-be-used-as-storage-path-for-backup/19535>\
**Category:** Dynatrace Managed\
**Tags:** dynatrace-managed, account-management, cluster-management-console\
**Created:** [June 11, 2020, 7:20am UTC](https://community.dynatrace.com/t/created-a-new-directory-in-all-managed-nodes-where-permission-is-777-but-yet-cant-be-used-as-storage-path-for-backup/19535 "2020-06-11T07:20:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [June 11, 2020, 1:22pm UTC](https://community.dynatrace.com/t/created-a-new-directory-in-all-managed-nodes-where-permission-is-777-but-yet-cant-be-used-as-storage-path-for-backup/19535/3 "2020-06-11T13:22:32Z")

</div>

So it dosent have to be local or NAS. Ours was a mounted drive, that was on a SAN, so it in essence was NAS but it was also local. We always had a yellow warning in the CMC for the back up, but the backup worked without an issue. We had issues with updating where a host was changing permission levels. I had concluded that it was a security application that was reverting the permissions because I could manually change them, update the cluster and it would work. But weeks later when the auto update would kick off, it would fail due to permissions and I would have to change the permissions again on that one failed node. it was odd.

I feel that you issue is very similar if not the same, just at a backup permission level.

---

_[View the full topic](https://community.dynatrace.com/t/created-a-new-directory-in-all-managed-nodes-where-permission-is-777-but-yet-cant-be-used-as-storage-path-for-backup/19535)._
