Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hello and sorry for my english,
I have to create a new file server. I want to create server in windows server 2022 but for the share files i want to mount drive D to Netapp where will be the storage of files.
I want to do like this because i want to have functionnality i use on Netapp (snapshot, fabricPool, snapmirror...).
But i don't know what it the best to mount the volume. I don't want to mount with NFS because it native on windows now but not very good. I want to mount and manage file sharing with NTFS rights directly from windows.
So i have ISCSI or SMB (CIFS). What is the best for you for what i want to do ?
thanks a lot
Solved! See The Solution
1 ACCEPTED SOLUTION
prachana has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Snapmirror and Snapshots features are at volume level, regardless of what data protocols (iscsi or SMB). So whether you mount it iSCSI or CIFS, you will get those features.
If it's block storage then iSCSI is best the option (specially DB volumes) to present the volume. If flat files then CIFS would be good. If you create the volume with mixed filesystem type then you can share it as CIFS or NFS.
Hope that helps
2 REPLIES 2
prachana has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Snapmirror and Snapshots features are at volume level, regardless of what data protocols (iscsi or SMB). So whether you mount it iSCSI or CIFS, you will get those features.
If it's block storage then iSCSI is best the option (specially DB volumes) to present the volume. If flat files then CIFS would be good. If you create the volume with mixed filesystem type then you can share it as CIFS or NFS.
Hope that helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Guidelines for mapping LUNs to igroups
You can map a LUN only once to an igroup.
As a best practice, you should map a LUN to only one specific initiator through the igroup.
You can add a single initiator to multiple igroups, but the initiator can be mapped to only one LUN.
You cannot use the same LUN ID for two LUNs mapped to the same igroup.
You should use the same protocol type for igroups and port sets.
