Backing up user profiles/data before deploying image
- 
 @RobertD Oh that’s a easy one. That is because /images is read-only at the share level. That is why fog uploads to /images/dev which is read-write at the share level. showmount -e 127.0.0.1might show this or/etc/exportswill.
- 
 So we should be mounting to a sub directory in images/dev… Export list for 172.31.16.155: /images/dev * /images *
- 
 add it to /etc/exports as an rw share 
 then execute as rootecho "/images/userbackup *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=2)" >> /etc/exports exportfs -a systemctl restart rpcbind # or something like i dont remember de name exactly systemctl restart ntfs-serverTry it if you can. 
- 
 @EduardoTSeoane said in Backing up user profiles/data before deploying image: add it to /etc/exports as an rw share You can do that just watch your IDs and pick the next integer. something like /images/userbackup *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=2)Then an exportfs -a showmount -e 127.0.0.1should show the new share. 
- 
 @EduardoTSeoane said in Backing up user profiles/data before deploying image: echo “/images/userbackup *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=2)” Guess you meant: echo "/images/userbackup *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=2)" >> /etc/exports ...
- 
 Wow you guys are a great help. We were looking at folder permissions that whole time when it was the share permissions. 
- 
 @Sebastian-Roth 
 yes, i want to say that i correct it in the post


