HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Serviceguard and Ignite-UX
Operating System - HP-UX
1833387
Members
2935
Online
110052
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
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
06-16-2011 06:19 AM
06-16-2011 06:19 AM
Serviceguard and Ignite-UX
Is there a best practices for Ignite-UX with Serviceguard available?
We need to be able to in a disaster, rebuild one node of a cluster and have all services up and running. This means, the locvg and the LVM vgs that are used in the packages. I suppose it means it will run as a one-node cluster.
Are there considerations to be taken into account during the make_tape_recovery phase?
Are there considerations in the ignite phase?
How do things like the cdfs get set properly, and the lockvg, etc.?
Since the file systems are defined in the cluster config, not /etc/fstab, how does one ensure that a) the vgs and file systems are set up properly, etc.
I.e., I think there would be a different set of informaiton gathering for an SG environment than for a normal environment, and the build in a disaster would look somewhat different.
We need to be able to in a disaster, rebuild one node of a cluster and have all services up and running. This means, the locvg and the LVM vgs that are used in the packages. I suppose it means it will run as a one-node cluster.
Are there considerations to be taken into account during the make_tape_recovery phase?
Are there considerations in the ignite phase?
How do things like the cdfs get set properly, and the lockvg, etc.?
Since the file systems are defined in the cluster config, not /etc/fstab, how does one ensure that a) the vgs and file systems are set up properly, etc.
I.e., I think there would be a different set of informaiton gathering for an SG environment than for a normal environment, and the build in a disaster would look somewhat different.
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