Local Storage Cache Overview
Creation Date: March 06, 2009
Revision Date: December 15, 2010
Product: DS‑Client
Summary
The Local Storage Cache feature enables DS-Clients to perform backup on a local attached disk or UNC path accessible by the DS-Client software and send the data to DS-System later when DS-System service becomes available. Backup sets must be configured to use this option. The Local Storage Cache option is available for backup sets if DS-Client has the Local Storage tool enabled (from DS-System).
See Also
Saving Data to Local Storage Cache
If backup sets are configured with the Local Storage Cache option, DS-Client will send data to the Local Storage Cache when the following occurs:
• The connection between DS-Client and DS-System is lost during a backup activity and the connection cannot be re-established after the configured number of retries. (To configure the number of retries, click DS-User > Setup > Configuration > Parameters and see options in the Backup Options section.)
• DS-Client cannot establish a connection with DS-System for a scheduled or on-demand backup activity.
• The backup activity is stopped from the DS-System-side and DS-Client fails to reconnect to DS-System based on the configured number of retries for backup activities.
• [Windows DS-Client only]: backup activity starts and data still exists in the Local Storage Cache buffer for this backup set.
If a DS-Client tries to connect to a DS-System and cannot establish the connection, DS-Client will process the data and save it in the Local Storage Cache buffer. Once DS-Client is able to connect to DS-System, a Local Cache Copy process will be triggered which will send to DS-System each generation of the required files in the required format: i.e. master/delta/regular.
If DS-Client established a connection with DS-System for this backup set and the backup activity was interrupted, DS-Client will run a synchronization activity and then proceed with the Local Cache Copy process when connection to the DS-System is re-established.
The Local Cache Copy process is considered as a backup activity (by DS-System) with the same priority and the same backup set locking rules.
Data in Local Storage Buffer vs. Data in Local Storage Cache Buffer
Feature | Local Storage Buffer | Local Storage Cache Buffer |
Data is stored in "Buffer" when: | Connection to DS-System is available | Connection to DS-System is NOT available |
Types of Generations: | Full File Content ("Regular" generation format) | Full File Content ("Master" generation format) + Meta Data ("Delta" generation pointers) |
Compression: | Yes | Yes |
Encryption: | No (by default) Can be configured using the “EncryptedLocalData” Parameter. | Yes |
Data "Buffered" during Initial Backup: | No | No |
Data is sent to the Local Storage Buffer at the same time when data is being processed to be sent to DS-System (there is an established connection between DS-Client and DS-System). Data is sent to the Local Storage Cache Buffer, ONLY when connection to the DS-System is NOT available.
By default, data is saved in the Local Storage Buffer compressed, but not encrypted (configurable), and as "regular" generations of the files. Data is saved in the Local Storage Buffer buffer is compressed and encrypted as "master" generations of the files.
Data is saved in the Local Storage Cache buffer as a master generation that includes additional information that determines which blocks of data from within that file are required for delta generations.
When connection between DS-Client and DS-System is established, DS-Client will move the required files to the Local Storage Buffer (based on backup set configuration) in the format they were stored in the Local Storage Cache Buffer (encrypted and compressed) and will send only "delta" generations to DS-System (when applicable).
As a result, DS-Client can still process Master/Delta (Incremental forever) when performing backup using the Local Storage Cache Option. Similarly, the Local Storage Buffer may include encrypted as well as unencrypted data, depending on when the files were processed during a particular backup activity.
Files are removed from the Local Storage Cache Buffer or moved to the Local Storage Buffer when they have been successfully transferred to DS-System. File are released from Local Storage Cache Buffer one-by-one as their successful transmission to the DS-System is confirmed between DS-System and DS-Client.
An initial backup session does not process data for Local Storage Buffer or Local Storage Cache Buffer.
Local Storage Number of Generations vs. Local Storage Cache Number of Generations
The configured number of generations for the items of a backup set does not take effect when data is sent to the Local Storage Cache Buffer. For example: A backup set is configured to store a maximum of three generations of data on the DS-System Online Storage. It can store more than three generations of data in the Local Storage Cache Buffer if DS-System is unavailable and/or DS-Client did not finish moving the data from the Local Storage Cache Buffer to the DS-System. All generations will be sent to DS-System whenever possible as regular generations or Master/Delta generations and DS-System will process them as it would process any generations sent directly to it (e.g. it will mark generations as recycled when required, it will trigger reconstruction when required, etc.).
By default, the Local Storage Buffer will store the latest generation of all the files processed for a backup set. However, if Local Storage Retention is enabled and assigned to a backup set with Local Storage Options enabled, DS-Client will store all generations that meet the criteria specified in the Local Storage Retention rules in the Local Storage Buffer.
Restoring data from Local Storage Buffer vs. Local Storage Cache Buffer
DS-Client can restore data directly from the Local Storage Buffer and can connect to DS-System to retrieve only data that does not exist in the Local Storage Buffer (configure this behavior from the Restore Wizard, before triggering the restore activity). Data from the Local Storage Cache Buffer cannot be restored until it has been transferred to DS-System.
Detecting File Corruptions in the Local Storage Cache Buffer
DS-Client can perform basic checks to ensure the validity of the files from the Local Storage Cache Buffer when the files are transferred to DS-System. As a result of these checks, if DS-Client determines that the files are corrupted, it will remove the file information from the DS-Client database and will try to determine if the files need to be backed up again during the subsequent backup session.
IMPORTANT NOTES
• If a backup set is marked as out-of-sync and DS-Client cannot connect to DS-System to perform synchronization, then DS-Client cannot run backup to the Local Storage Cache Buffer.
• DS-Client Administrators must ensure that sufficient Local Storage disk space is available to accommodate all data in the Local Storage Buffer or Local Storage Cache Buffer for all the configured backup sets.
• If data exists in the Local Storage Cache Buffer for a selected backup set, that data must first be transferred to DS-System, and only afterwards can DS-Client perform subsequent backups for that backup set directly to DS-System.
• Suspending a backup set configured with the Local Storage Cache Buffer will not allow the Local Storage Cache Copy process to be triggered and to connect to DS-System to move the data.