* Fixed a bug in anvil-manage-dr where protect jobs with multiple potential targets wouldn't know which to use during job runs.

Signed-off-by: digimer <mkelly@alteeve.ca>
main
digimer 2 years ago
parent e9f390b65b
commit 053e5312e1
  1. 1
      tools/anvil-manage-dr

@ -2587,6 +2587,7 @@ sub process_protect
{ {
my $job_data = "server=".$anvil->data->{switches}{server}."\n"; my $job_data = "server=".$anvil->data->{switches}{server}."\n";
$job_data .= "protect=1\n"; $job_data .= "protect=1\n";
$job_data .= "dr-host=".$anvil->data->{sys}{dr_host_name}."\n";
$job_data .= "protocol=".$anvil->data->{switches}{protocol}."\n"; $job_data .= "protocol=".$anvil->data->{switches}{protocol}."\n";
# We always record the job against node 1, as it has to use cluster info to run this, so we # We always record the job against node 1, as it has to use cluster info to run this, so we

Loading…
Cancel
Save