What is Intelligent caching?
Intelligent caching enabled login will ensure that you have the latest version of the file data and the folder contents in your IBackup account at any given point of time. This option is useful when multiple users access the same account from more than one location. With intelligent caching, there will be local caching for faster access of files. If users modify the contents of the file from different locations, then IDrive will pull the latest version of the file from the IBackup server to the local cache during any operations like opening and copying of files or folders. Intelligent caching is enabled by default.
Intelligent caching enabled login ensures that you have the latest version of the file data and folder contents in your account, at any given point of time. This option is useful when multiple users are accessing the same account from more than one location. With the intelligent caching feature, a local cache is created for faster access to the files. If the users modify the contents of the file from different locations, then IBackup Drive pulls the latest version of the file from the IBackup server to the local cache, during operations like opening and copying of files/folders. Intelligent caching is enabled by default.
Intelligent Caching is a technology that allows customers to make read cache more efficient as compared to caching in traditional storage arrays. NetApp does this by caching only a single copy of blocks that are deduplicated or non-deduplicated (FlexClone). Cache efficiencies can be as great as 255:1 within a single NetApp volume. Using Deduplication with File and Volume FlexClone decreases the amount of data on disk and also reduces the amount of Cache required as well. An Example of Disk and Cache Efficiency So what does that mean? For example, a company wanted to role out 1000 Virtual Desktops and their OS disk was 20GB in size and had 250 VMs in a 4 NFS datastores or 10 VMs on 100 LUNS. Calculating pure capacity on a traditional storage array they would need at least 20TB of storage just for the OS disk. This calculation is excluding all user data, transient data (for example vswap & pagefiles). The same is true for cache. If the working set is 200MB per VM, the amount of cache req
