Choose from the following topics:
Related Topics:
The use of QSnap or OFH ensures that file system metadata remain unchanged, and therefore consistent, during the backup operation. QSnap or OFH is fully integrated with Image Level ProxyHost, creating a software snapshot during the Scan phase of the backup. Thus, all of the components necessary for basic Image Level iDataAgent functionality are available without requiring specialized hardware. For improved performance and flexibility, and enhanced features, you can supplement the Image Level ProxyHost iDataAgent and QSnap or OFH with a hardware-based snapshot implementation.
The following must be done before using the Image Level ProxyHost iDataAgent with QSnap or OFH:
It is not necessary to quiesce the server for a file system backup with Image Level ProxyHost, and thus, no need of calling CVSnaptool from a pre-scan batch file.
We recommend that you test batch files before associating them with any subclients.
For specific information on the PreScan and PostBackup processes, see the Resource Pack for sample batch files.
The following must be installed on the production server:
The following must be installed on the backup host:
Note: OFH is installed automatically during installation of the Image Level iDataAgent.
For a clustered environment, first install the Windows File System iDataAgent and QSnap or OFH on the physical nodes, and then reboot the nodes. After rebooting the nodes, install the Image Level ProxyHost iDataAgent and the Image Level iDataAgent on the virtual node. (The Windows File System iDataAgent is automatically selected when you install the Image Level iDataAgent.)All configuration for Open File Handler (or QSnap) needs to be done only on the host machine’s Image Level iDataAgent.
The following software must be installed on the production server:
The following must be installed on the backup host:
For more information and procedures, see Deployment - Image Level ProxyHost iDataAgent.
Unlike a File System iDataAgent, the Image Level ProxyHost Agent backs up extents on the source drive. The extent size is initially set to 2 MB, effectively dividing the source volume. (On Unix, the GUI will display 4096.) In most cases, this 2MB default size is best for performance.
But there may be reasons for increasing or decreasing extent size to improve performance. Keep in mind that a 2MB extent with just 10KB of data is backed up entirely, including its empty blocks of data. Again, this will work fine in most cases, but factors such as the state of data fragmentation on the source, network bandwidth, and server speed should be considered. These factors, along with extent size, can impact both the speed and the size of backups.
If performance is inhibited because of extent size issues, contact your software provider for more information about tuning your software for maximum performance.
Also consider the following implications of changing extent sizes: