Backup - ProxyHost

Topics | How To | Use Cases | Related Topics

Overview

Supported Backup Types

Backup Considerations

Advanced Backup Options

Overview

Plan your backup jobs for this agent by reviewing the following information:

• For an overview of backup jobs, see Backup Data.
• For a list of supported data types for this agent, see Supported Data Types.
• For information on subclients, see Subclients
  • For information on configuring subclients for this agent, see Subclients - SAN iDataAgents.
  • Excluding Data from Data Protection Operations for information on excluding data via subclients.

Supported Backup Types

This agent supports the following backup types:

• Full Backups
• Differential Backups
• Incremental Backups
• Synthetic Full Backups

Backup Considerations

Before performing any backup procedures for this agent, review the following information:

• Synthetic Full backups are not supported for TimeFinder Exchange Database or SQL Database data.
• For file system data you can initiate an immediate full, incremental, or differential backup for the selected subclient. An incremental backup backs up all data that is new or has changed since the last backup of any type, whereas a differential backup backs up all data that is new or has changed since the last full backup.

  For Exchange data you can only initiate full backups for the selected subclient. Because ProxyHost iDataAgent software does not use API to backup Exchange Database data, incremental or differential backups can possibly miss the partially filled transaction log, which was backed up by the previous full backup.

• When backing up Exchange Databases, circular logging must be manually disabled for Exchange 2000 and Exchange 2003.
• When using the ProxyHost iDataAgent to backup databases, a backup might not be considered successful unless every single file is backed up successfully. To cause such a backup job to be reported as "Failed", create the nFAILFORPROXY registry key, and set its value greater than or equal to "1".

• Filters can be used in conjunction with the "Items That Failed" list on the data protection Job History Report to eliminate backup or archive failures by excluding items which consistently fail that are not integral to the operation of the system or applications. Some items fail because they are locked by the operating system or application and cannot be opened at the time of the data protection operation. This often occurs with certain system-related files and database application files.

  Also, keep in mind that you will need to run a full backup after adding failed files to the filter in order to remove them.

Back to Top