Hello,   Yes you can enable thin provisioning at any time w/o damage.  The host is not aware of the change.  Re: KB.  That article will help regardless of virus or malware scanner.  Since ANY read invokes a small write. DBs tend to do a lot of reads.  So the SQL engine is going to be doing those reads all the time.  Re: 64K NTFS cluster size.  That is a long standing recommendation that applies across storage vendors. The 64K stripe size of the EQL array means that if you send less than 64K the read or write will be misaligned from the RAID stripe.  On writes this means more steps to get the write done compared to one that aligns on the 64K boundary.  Other storage vendors may use a different size.   Unfortunately, you can only set that when you format the volume.  So you would have to create a new volume format it, then migrate your data.   However, if you are not expressing a large load on the array the difference won't be significant.  Regards,  Don     
  Hello, I want to enable the snapshot of a lun, but I have some doubts: Q1 - Where are shanpshot stored? In the same volume of the LUN? Or in another area? Q2 - The snapshot reserve (%) is the space provided for snapshot. Does this mean that if I want a 1TB LUN, do I need to create a larger LUN to accommodate this percentage? Does not this percentage interfere with the LUN's useful area space? Q3 - How do I estimate the space required to create a snapshot? If I select to keep two snapshots, do I have to double the amount of space consumed and so on? Q4 - What would these options be: - Make writable snapshots? - Set snapshot online? - Make snapshot read-write? Q5 - If I want to go back to snapshot, can I restore it to hot? Is there any procedure to run that I need to be aware of? Q6 - When I restore the LUN, but before setting it to offline, it appeared another snapshot in the list. Why did this happen?   Thank you.
Snapshot Doubts