HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Failover scripts
Operating System - HP-UX
1835242
Members
1970
Online
110078
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2002 11:28 AM
07-19-2002 11:28 AM
Heres the situation:
I have a 2 node cluster
Prod node: I have 2 db instances on individual packages, snfuprd and snfcprd.
Each of these packages have a dbstart script in the "customer run defined commands"
Test Node: I have 4 db instances set up the same way.
What I want to:
When one of my prod packages fails over to the test server I want to shut down one of the test packages on the test server....
Any one have any examples of scripts that do this? Any help would be appreciated...
I hope this makes sense.
I have a 2 node cluster
Prod node: I have 2 db instances on individual packages, snfuprd and snfcprd.
Each of these packages have a dbstart script in the "customer run defined commands"
Test Node: I have 4 db instances set up the same way.
What I want to:
When one of my prod packages fails over to the test server I want to shut down one of the test packages on the test server....
Any one have any examples of scripts that do this? Any help would be appreciated...
I hope this makes sense.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2002 11:59 AM
07-19-2002 11:59 AM
Solution
If test and production are both different packages then you can use RESOURCE Dependencies within service guard to accomplish this.
I think you could use these to create a dependency that says only run if the prod package != test server.
I don't have an exact example of this, but have used resource dependencies in the package ascii file to tie packages together (i.e. application package starts after database packages, etc.)
Hope that helps.
I think you could use these to create a dependency that says only run if the prod package != test server.
I don't have an exact example of this, but have used resource dependencies in the package ascii file to tie packages together (i.e. application package starts after database packages, etc.)
Hope that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2002 12:55 PM
07-19-2002 12:55 PM
Re: Failover scripts
Herer is an example from .cntl file.
-------------------
function customer_defined_run_cmds
{
# ADD customer defined run commands.
# This will execute any PRE_STARTUP commands that need to execute before
# bringing up this package. The most likely contents of this script
# will be to execute a series of shutdown commands for the databases
# on the failover node.
if [ -x $PRE_STARTUP ];then
$PRE_STARTUP
fi
----------------------
The script defined as $PRE_STARTUP is different on each node depending on what needs to be shut down prior to starting the package.
-------------------
function customer_defined_run_cmds
{
# ADD customer defined run commands.
# This will execute any PRE_STARTUP commands that need to execute before
# bringing up this package. The most likely contents of this script
# will be to execute a series of shutdown commands for the databases
# on the failover node.
if [ -x $PRE_STARTUP ];then
$PRE_STARTUP
fi
----------------------
The script defined as $PRE_STARTUP is different on each node depending on what needs to be shut down prior to starting the package.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2002 02:42 PM
07-19-2002 02:42 PM
Re: Failover scripts
Hi Mike,
George & Rich have pretty much set you on the correct track.
What I want to point out is that in your scenario you'll have to wait until the pre-startup scripts complete successfully before the adopted pkg will start.
So bear in mind that you'll have to calculate the DB shutdown & startup time as well as detection in the failover times as a whole.
And note the deliberate use of the word successfully in that statement, if pkg_to_stop doesn't, then pkg_to_start won't as well. Your monitor scripts are just as critical. If you don't failover a DB that doesn't respond to normal client traffic but does respond to simple monitors, than you have no failover.
My $0.02
Jeff
George & Rich have pretty much set you on the correct track.
What I want to point out is that in your scenario you'll have to wait until the pre-startup scripts complete successfully before the adopted pkg will start.
So bear in mind that you'll have to calculate the DB shutdown & startup time as well as detection in the failover times as a whole.
And note the deliberate use of the word successfully in that statement, if pkg_to_stop doesn't, then pkg_to_start won't as well. Your monitor scripts are just as critical. If you don't failover a DB that doesn't respond to normal client traffic but does respond to simple monitors, than you have no failover.
My $0.02
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP