hello and sorry for my english,   I have Vmware hypervisor connect to my cluster in ISCSI. So, VM disks are store on Netapp cluster. On my files volumes, Antiransomware is activate but not on Vmware volumes. Do you think it is a bad or good idea to activate antiransomware on volumes where Vwmare disks are store ?   thanks a lot ... View more

hello： I would like to ask if there are detailed steps to upload the stored configuration information to the FTP server.    thank you ... View more

Hello. Currently, I am doing a periodic snapshot with a Powershell script using the following command: >New-NcSnapshot $netapp_volume_name $netapp_newsnap_name   In the settings of each volume, I think that snaplock will be enabled from the next snapshot acquisition by setting snapshot-locking-enabled to TRUE, but the command "New-NcSnapshot" in the Powershell toolkit does not have the option to specify the retention period. In other words, we believe that the only way to execute a snapshot is to execute it without specifying the retention period. In this case, is it correct to assume that the retention period of the SnapLock Retention Period set for the volume will be adopted? Is there a difference in behavior when taking snapshots with the Powershell Toolkit?   * This question uses Google Translate, so there is a possibility that the sentence is wrong. ... View more

Have a couple of questions about vol moves.  Customer has roughly 34 volumes to move from an A200 to an new A250 in the cluster.   They would like to start baselining all of the volume moves with deferred cutovers.  The cutovers will be manually triggered during their maintenance window in a couple of weeks.   1) Does the vol move start with the "cutover-action wait" parameter just do a one time baseline of the data and then when you manually trigger the cutover it does an incremental copy of all changes since the baseline or does the job do some sort of incremental changes periodically between the baseline and the manual cutover?   2) It looks like there is a parameter on vol moves which restricts you to 8 concurrent vol moves.   It looks like we can increase that option.   Is it ok to bump it up for this customer to allow more than 8 vol moves to be sitting in a cutover deferred state? We would still not have more than 4-8 concurrent baselines going at one time but we would want to be able to have all 34 volumes in a cutover deferred state at the end of the process to prep for cutting them all over during the maintenance window and avoid having to baseline the larger volumes during that window.   Thanks... Dean ... View more