Difference between revisions of "VALT Warm Standby"
IVSWikiBlue (talk | contribs) |
IVSWikiBlue (talk | contribs) |
||
Line 39: | Line 39: | ||
#Run {{Code Block - Mini | text = <span class="code_file">VALTStandbyServerConfig.sh</span>}} on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server. | #Run {{Code Block - Mini | text = <span class="code_file">VALTStandbyServerConfig.sh</span>}} on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server. | ||
− | If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the {{Code Block - Mini | text = <span class="code_filepath">/usr/local/valt/bin/</span>}} directory and set to executable. These scripts are provided below if the {{Code Block - Mini | text = <span class="code_2">VALTRedundancy.tar.gz</span> | + | If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the {{Code Block - Mini | text = <span class="code_filepath">/usr/local/valt/bin/</span>}} directory and set to executable. These scripts are provided below if the {{Code Block - Mini | text = <span class="code_2">VALTRedundancy.tar.gz</span>}} package was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover. |
<hr> | <hr> |
Revision as of 16:39, 27 July 2023
⚠DISCLAIMER: This is not a step by step instruction. This article assumes the reader has a working understanding of the VALT application and how to modify the configuration files. This procedure should only be completed by an IVS support engineer. This may be incorporated into the command line menu in the future.