Files with higher priority are preferred to remain in the cache. After discussing this with Martin I found out that the buffered copy moves the file into the cache at Priority2 while PVS vDisks use cache Priority5.

Originally I was going to use unbuffered IO so that the replication did not displace vDisks currently being used from the cache. There are two types of copying we could use for the replication buffered and unbuffered. So, we need to understand how the Windows Cache Manager works with different copying methods. What Martin taught me was that PVS uses the Windows Cache Manager as the mechanism to cache vDisks. PVS Internals #2 - How to properly Size Your Memory If you want to bone up on the subject you should read all his PVS blogs: Martin has written three of what I consider definitive Blogs on understanding PVS internals and he is incredible with PowerShell, to the point of making it art. When we decided to start the project, the first thing I did was take Martin out to dinner so I could pick his brain on the best way to approach the scripting technically. On this project, they all provided me with script examples and helped me work through the many possible ways to do this. You may have worked with them in the past, and you have probably read many blog posts from each of them over the years.

To that end, I met with several very smart and talented colleagues: Dan Morgan and Miguel Contreras, both from CCS, and Martin Zugec from Technical Marketing. Some colleagues and I thought it was time to develop a utility that would help customers simplify this process. One of the most common PVS questions Citrix Consulting Services (CCS) is asked about is what is the best way to replicate vDisks between PVS stores.

NetScaler Application Delivery Management.

NetScaler App Delivery and Security Service.

Download the new for windows REPLIKATOR