I've just started building VHD files (Hyper-V) but instead of using the Hyper-V GUI each time i've created a 40GB fixed and i'm just copying/pasting to make duplicates. During this process the CPU is sitting at above 90% causing other access to the filer to grind to a hault.
Is this normal for the FAS2020? I have enabled flow control and jumbo frames end-to-end. The host NICs and switch ports have been set to 1000Mbps FD but I understand the FAS2020 cannot be specifically set to 1000Mbps FD so it's auto neg.
Using Microsoft iSCSI Initiator on 2008 R2 with 2 dedicated NICs and switches to the FAS2020. TOE etc on the host NICs are set to TX/RX.
Haven't check At-a-Glance yet but System Manager the I/O (bytes/sec) is peaking at about 0.4M, the Operations (ops/sec) is peaking at about 1K and the Read Latency (msec) is peaking at 8.0. If that helps.
1st point the sysstat -m shows the right utilization of the CPUs and when you do the sysstat it show CPU utilization more when more than 1 CPU is being used at good rate , it does not mean that your CPU is highly utilized. Checked it out by sysstat -m
2nd word what you want to do, do you want to make the clone of files , ok if this is your query than please you can have the vol clone command clone the volume and then you can target that cloned volume where you want. But take care that cloned volume is created using the snapshot so if the snapshot is being carried out via script then script will fail at that time if that snap used for creating the LUN is still in use and that leads to the replication failure if that happen. you can split the clone volume do remember you should have space in the aggregate to guarantee the space to new volume being split.