Talk with other users about your NetApp data storage solutions and VMware server and desktop virtualization solutions, as well as NetApp Virtual Storage Console (VSC) for VMware’s vSphere cloud computing foundation.
Talk with other users about your NetApp data storage solutions and VMware server and desktop virtualization solutions, as well as NetApp Virtual Storage Console (VSC) for VMware’s vSphere cloud computing foundation.
We are on SnapCenter 4.6 currently setting up VMware snapshot protection. I got a few questions wish someone can share your experience. 1. if we take snapshots on datastores, will IOs be hold during snapshot? is there any snapshot technology involved? 2. we have many datastores (around hundred for one folder on same VCenter), should we create single resource group or split to multiple resource groups? We have a resource group with 30 datastores, it took around 15 minutes to complete the snapshot, just wonder if any Array resource (CPU, memory, cache) will be consumed to impact the array performance? 3. is there any easier way to run a VM on demand snapshot instead of create resource group? 4. is there time and space usage difference for an on demand snapshot between a single VM and its datastore? 5. we plan to keep one week datastore snapshots, is that a good approach?
... View more
Is there a way to get a list of the array's available spare discs using the Rest API when ADP root-data partitioning is configured? I'm trying to locate any spare discs that will be in the shared container.
... View more
Our environment includes solidfire H410S and H700E nodes. We're upgrading to ESXi 7.0 U3 (from 6.7 U3). I wanted to know about HCI and VMware compatibility to run the latest version of the 7.0 U3 hypervisor and the minimal HCI software and firmware versions. What NDE, Element Software, and computing (BMC, BIOS, NIC) firmware is needed for ESXi7.0 U3?
... View more
Hello, Today's logic with iGroup is way too strict and creates an unwanted situation. As documented in the following KB: VSC and VASA_Provider/Why does Virtual Storage Console (VSC) create "rcu_generated_alua" iGroup and Storage Replication Adapter: What determines if a new initiator group or export policy is created during a failover operation? , we learn a new iGroup gets created if the system doesn't find an equivalent iGroup with all initiators. So far, nothing's wrong but the problem appears when you have an iGroup with all detected initiators but with extra initiators used by your backup system whose requirement is to connect on a LUN to backup or restore. Your only way to back to your original IGroup is to "force" unmap, map the LUN again and rediscover your system storage. It creates a system service disturbance which is a situation no one wants. Now, you add your extra initiators to an automatically created iGroup by either VSC or SRM well next time you do a similar operation like creating a LUN/NFS or failOver, it will try to create a new iGroup or choose an iGroup with exact same list of initiators/export. Would it be possible to switch or leave the operator to decide to use minimal requirements (detected initiators) instead of strict requirements? Regards, Oli
... View more
Hello, I know this is probably something recurring, but I searched for a way to troubleshoot it and can't really find something like my case. I have a thick provisioned volume of 25TB, containing some thick provisioned LUNs, no dedup nor snapshots (neither at LUN nor volume level). The sum of the space covered by LUNs is about 12TB, but the volume shows less than 600GB available. I tried some commands and it seems that the remaining space is "reserved" but not available...and I can't understand why. Can you please help me troubleshooting this situation? How can I recover the missing 12TB? Thank you in advance! Little prologue: on the same aggregate there was a volume where dedup was ON and its temporary files probably grew over the total amount of space of the aggregate. This locked two thin provisioned LUNs within the 25TB volume. So I resized these LUNs, and made them thick. Some command outputs: ::> volume show-space -volume vol_recorders_win_08 Vserver : svm_win Volume : vol_recorders_win_08 Feature Used Used% -------------------------------- ---------- ------ User Data 24.34TB 97% Filesystem Metadata 4.88GB 0% Inodes 52KB 0% Performance Metadata 28.21GB 0% Total Used 24.37TB 97% Total Physical Used 12.09TB 48% ::> volume show-footprint -volume vol_recorders_win_08 Vserver : svm_win Volume : vol_recorders_win_08 Feature Used Used% -------------------------------- ---------- ----- Volume Data Footprint 12.09TB 40% Volume Guarantee 12.65TB 41% Flexible Volume Metadata 142.2GB 0% Delayed Frees 267.2GB 1% File Operation Metadata 4KB 0% Total Footprint 25.14TB 82% ::> df -r -g -aggregate aggr_data_08 Filesystem total used avail reserved Mounted on Vserver /vol/vol_backup_vms_08/ 1288GB 0GB 1288GB 0GB /vol_backup_vms_08 backup_vms /vol/vol_backup_vms_08/.snapshot 227GB 0GB 227GB 0GB /vol_backup_vms_08/.snapshot backup_vms /vol/vol_recorders_win_08/ 25600GB 25037GB 562GB 12350GB --- svm_win /vol/vol_recorders_win_08/.snapshot 0GB 0GB 0GB 0GB --- svm_win /vol/vmcluster_ctn_nfs_data_08/ 3793GB 1574GB 2219GB 0GB /vmcluster_ctn_nfs_data_08 vmcluster-ctn_vms /vol/vmcluster_ctn_nfs_data_08/.snapshot 199GB 411GB 0GB 0GB /vmcluster_ctn_nfs_data_08/.snapshot vmcluster-ctn_vms
... View more
