We are trying out FreeNAS as a backup to disk device. Backing up to an HP Proliant running the release candidate 8.3.1, and trying to write to it from a Windows 2008 R2 server running Backup exec, backing up to disk.
I was trying to use NFS as from what I have read it should be faster (and does seem to be compare to earlier tests).
It is mostly working except one final hurdle is driving me nuts. The share can be accessed, backup image files are created, but they cannot be written to. When I check file permisssions on newly created files they are all '-rwxr-xr-x' User can write, but group and other cannot.
If I chmod 777 all the files, everything starts working until the backup process creates new images, which are created with the above permissions, and stay at 0 bytes in size till I chmod them all.
I have the ZFS volume with the below permissions. I have tried checking off the recursive option.
I created a dataset on the volume with the below permissions. I have tried checking off the recursive option.
The NFS share is configured as below. Was hoping that using mapall as root would avoid conflicting user name/permission problems. We'll come back to permissions once we proove the concept.
And I have the option for the NFS service checked to allow non root mount.
I've tried chown from the cli to assign root:wheel to the folders recursively, and chmod recursivley.
Just every time a new file is created in the share, it is not writeable in the 'group' or 'other' position, and our backups stop.
Not sure what I can do to correct that, or am I looking at this the wrong way? I'm just trying to set it up quick and wide open just to see if this will work for us on larger quantities of data.
Any suggestions would be greatly appreciated!
Thanks,
Glenn
I was trying to use NFS as from what I have read it should be faster (and does seem to be compare to earlier tests).
It is mostly working except one final hurdle is driving me nuts. The share can be accessed, backup image files are created, but they cannot be written to. When I check file permisssions on newly created files they are all '-rwxr-xr-x' User can write, but group and other cannot.
If I chmod 777 all the files, everything starts working until the backup process creates new images, which are created with the above permissions, and stay at 0 bytes in size till I chmod them all.
I have the ZFS volume with the below permissions. I have tried checking off the recursive option.

I created a dataset on the volume with the below permissions. I have tried checking off the recursive option.

The NFS share is configured as below. Was hoping that using mapall as root would avoid conflicting user name/permission problems. We'll come back to permissions once we proove the concept.

And I have the option for the NFS service checked to allow non root mount.
I've tried chown from the cli to assign root:wheel to the folders recursively, and chmod recursivley.
Just every time a new file is created in the share, it is not writeable in the 'group' or 'other' position, and our backups stop.
Not sure what I can do to correct that, or am I looking at this the wrong way? I'm just trying to set it up quick and wide open just to see if this will work for us on larger quantities of data.
Any suggestions would be greatly appreciated!
Thanks,
Glenn