Best Practices for Integrating Neverfail Heartbeat V4.6 or Later with Backup Solutions.

Follow
Summary

This Knowledgebase article provides information about supported backup technologies and provides links to additional Knowledgebase articles, which describe how to best integrate them with Neverfail Heartbeat. This information should be read:

  • Prior to installing Neverfail Heartbeat on to a server where a backup solution is already deployed.
  • Prior to installing a backup solution on to a server pair where Neverfail Heartbeat is already deployed.


More information

If you are running an older version of Neverfail Heartbeat, please refer to Knowledgebase article #308 - 'Best Practices for Integrating Neverfail Heartbeat with Backup Solutions'.

There are several configurations in which backup tools may be deployed, depending on how the backup media is connected to the server(s), and how backups are performed (e.g. through the use of remote agents, etc.); Neverfail refers to these as topologies.

There are no Neverfail AMXs for any of these backup tools; therefore, some manual integration with Neverfail Heartbeat may be required. The amount of manual configuration and maintenance required depends on the combination of the backup solution and the topology.

Supported Technologies

The following list shows the products for which Neverfail has performed interoperability tests, and the topologies, which are supported for each tool. Please follow the corresponding links for specific details on how to deploy a particular tool in a specified topology, on a server pair running Neverfail Heartbeat.

Product Version Topology Knowledgebase articles.

Product Version Topology KB Article
Symantec NetBackup for Windows Servers (32 Bit) 6.5 #1 KB 1533
Symantec Backup Exec for Windows Servers 10d #1 KB 1175
Symantec Backup Exec for Windows Servers 10d #2 KB 1174
Symantec Backup Exec for Windows Servers 10d #4 KB 1173
Symantec Backup Exec for Windows Servers (32 Bit) 11d #1 KB 1224
Symantec Backup Exec for Windows Servers (32 Bit) 11d #2 KB 1223
Symantec Backup Exec for Windows Servers (32 Bit) 11d #4 KB 1222
Symantec Backup Exec for Windows Servers (64 Bit) 11d #1 KB 1301
Symantec Backup Exec for Windows Servers (64 Bit) 11d #2 KB 1302
Symantec Backup Exec for Windows Servers (64 Bit) 11d #4 KB 1303

Topologies

This section describes four possible topologies for a backup tool running on a Neverfail Heartbeat server pair.

Topology #1: Remote Backup Via Agents

If backups are to be performed on the active server regardless of identity, Primary or Secondary, then Neverfail recommends the use of remote backup agents. The backup jobs are managed by a remote server, which hosts the management software for the configuration of the backup jobs, and the backup hardware media.

This offers almost seamless integration because it alleviates the need to duplicate:

  • Backup software configuration changes between servers
  • Backup hardware (tape drives etc.)

If the remote agents do not depend on protected services, then no integration changes are required because backup agents can usually be left running on the server regardless of the role. However, if they depend on protected services, they will need to be added to at least one of the Neverfail Heartbeat application start scripts.

Topology #2: Local Backup on Active Server (LAN) with Shared Media

The backup and management software will be installed on both servers, and the backup media (e.g. tape device, external HDD, other machine) is accessible to both of them, either because it is attached to both servers (e.g. through a LAN) or because the hardware is duplicated. In the latter case, the two sets of backup hardware must be similar, in both geometry and configuration; and there should be no difference between the two servers, in terms of how the operating system sees the backup hardware. As an example, each server might have an external HDD attached: the HDDs must have the same size (at a minimum, they should have enough space to ensure backup jobs can run properly, irrespective of the server identity), and the same drive letter assigned to them.

Caution: While the current configuration of the backup tool will be replicated from the Primary server to the Secondary server during the installation of Neverfail Heartbeat, future changes to the configuration will usually not be replicated. It is therefore the Administrator's responsibility to maintain configuration changes between the two servers, so that the backup jobs will run successfully on the active server, be it Primary or Secondary. Documenting changes made to the configuration on the Primary server would be a useful way to maintain this information.

Topology #3: Local Backup on Active Server (LAN) with Unshared Media

The backup and management software will be installed on both servers, but the servers do not share the same backup media (e.g. tape device, external HDD) and will probably have different backup configurations.

Topology #4: Local Backup on Primary Server (when Active) only.

The backup and management software will be installed on the Primary server; the backup jobs will run only on this server, while active.

Caution: Because the configuration of the Primary server will be replicated to the Secondary server during the installation of Neverfail Heartbeat, once Neverfail Heartbeat installation is completed on the Secondary server, all services belonging to the backup software must be disabled. This will prevent them from being started inadvertently, either by Heartbeat, or if the server is rebooted for any reason.

Neverfail Heartbeat application start and stop scripts on the Secondary server may need to be edited. They should be checked carefully, and all references to backup software services must be removed.

Applies To

Neverfail Heartbeat V4.6 or Later


Related Information

None

KBID-1172

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.