You always have to use /ifs as root directory to store data otherwise at least data protection will not work. As best practice you might add another level of directory like /ifs/userdata to exclude some “system files/folders in the /ifs” from Snapshot or other jobs/functions. (e.g. /ifs/.ifsvar)
In that case NFS exports will reflect your directory structure as /ifs/userdata and with SMB shares you can always use as \\FQDN\userdata without reflecting underlying directory structure.
For similar functionality to SMB share names you can also use NFS Aliases. Old but useful articles about it:
The thing is the connection here is through ndmp, then in TSM(backup tool) they register the mount point. So they need the same structure -> /ABC_RECOVER1/Restore. If the structure is different it would not work as it doesn't like /ifs//ABC_RECOVER1/Restore. Will the aliasing you mentioned will work in this case.
Ozen Zorba
1 Rookie
•
28 Posts
644
1
Posted July 8th, 2022 07:00
You always have to use /ifs as root directory to store data otherwise at least data protection will not work. As best practice you might add another level of directory like /ifs/userdata to exclude some “system files/folders in the /ifs” from Snapshot or other jobs/functions. (e.g. /ifs/.ifsvar)
In that case NFS exports will reflect your directory structure as /ifs/userdata and with SMB shares you can always use as \\FQDN\userdata without reflecting underlying directory structure.
For similar functionality to SMB share names you can also use NFS Aliases. Old but useful articles about it:
http://doc.isilon.com/onefs/7.2.0/help/en-us/GUID-4132E1C7-2463-4488-AFF6-74C545CB1C3C.html
http://doc.isilon.com/onefs/zzz_archive/cloudpools_staging/ifs_c_nfs_aliases.html