Comments
4 comments
-
Hi,
Have you installed SQL Backup on both nodes? -
It's installed on 1 of the 3 instances on Node-B. Here's our setup:
Node-A - Inst1
Node-B - Inst2; Inst3; Inst4
SQL Backup is installed, and runs nightly, on Inst1, and Inst2. Inst1 failed-over to Node-B, and SQL Backup failed because it couldn't find the xp_sqlbackup.dll. -
In your situation, you would have needed to install SQL Backup eight times, 4 times on each server for each of the instances. This would have placed xp_sqlbackup on each instance's Binn folder, and also installed the service on each active and passive node (if not configured as a cluster resource). See http://www.red-gate.com/messageboard/viewtopic.php?t=1880.
Currently, the installation isn't 'cluster aware', but will be so in the next version. -
Thanks, Peter, I'll give that a try.
Add comment
Please sign in to leave a comment.
Error reads: Cannot load the DLL xp_sqlbackup.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.). [SQLSTATE 42000] (Error 0). The step failed.
SQL Backup is installed and is used on both sides of the cluster. 1 named instance runs on Node-A and 3 different named instances run on Node-B. The named instance on Node-A failed over to Node-B. That is the instance that failed to backup.
What do I need to do to prevent this error? I want the backups to still run if a fail-over occurs.
Thanks,
Mike