- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: High Availability Basics
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО03-09-2010 07:15 AM
тАО03-09-2010 07:15 AM
High Availability Basics
Here's a brief description of my situation, I have a front end that serves up ssh connections to customers, I'd like to make it redundant in that I'd like to have a 'failover' server that would take over if that front end failed.
Here's my problem:
There are several cron jobs that run at specific times on this front end, if I were to setup a 'failover' server as part of a High Availability cluster where could I move those jobs too, as it wouldn't be good if they ran on both nodes of the cluster. However if I set them up on just one node, then I have a single point of failure, if that node goes down, those cron jobs will never run.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2010 07:29 AM
тАО03-09-2010 07:29 AM
Re: High Availability Basics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2010 07:59 AM
тАО03-09-2010 07:59 AM
Re: High Availability Basics
Start script should look like:
/usr/bin/crontab CRON
The file CRON should reside on a file system configured in the package, or you manually replicate it on all nodes. You shouldn't populate your crons with "crontab -e", you should first edit CRON file then use "/usr/bin/crontab CRON" to update crons.
stop script should look like:
/usr/bin/crontab -r
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2010 08:36 AM
тАО03-09-2010 08:36 AM
Re: High Availability Basics
place all your several cron job under "Cluster pkg" mount points and your place crontab under "pkg.cntl.file" as shown below
function customer_defined_run_cmds
{
# ADD customer defined run commands.
: # do nothing instruction, because a function must contain some command.
/opt/smx/bin/rc/rchDB.pd1 s nv
/usr/sbin/inetd -c
/usr/bin/crontab /opt/smx/bin/cron/abc.cron
test_return 51
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2010 10:19 AM
тАО03-09-2010 10:19 AM
Re: High Availability Basics
Put all your cronjobs where you do, in cron.
Now put all those same cronjobs on the other servers cron. Now you are going to set them up with one little 'difference'.
A good while back I came across a truly sleek script that Simon Hargrave wrote. What this does is goes out to see if the package is running on "this" node and runs the cron job. If the package isn't running then it does not run the job. Stephen Doud called the script elegant - and it is.
Take a look at this thread.....
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=886789&admit=109447626+1268158640672+28353475
We use it here on our cluster...
Kindest regards,
Rita