Abstract

Losing an entire member boot disk—which only affects a single member—or cluster_root, cluster_usr, and cluster_var or problems to your data file system(s) are extremely rare situations if guidance provided in the TruCluster Server documentation is properly followed. This chapter highlights on solutions to some of these types of problems and show the way to work out ways of a few tight situations. Moreover, the chapter shows how to change some of the characteristics of cluster such as the IP address and the cluster interconnect. Backing up cluster includes saving each member's boot disk, cluster_root, cluster_usr, and cluster_var. The least complicated scenario for restoring the cluster_root file system is to restore it to a disk that is already known to the cluster. Once booted from the ER disk it is possible to have a different view of the storage, namely the device special file names. Restoring cluster root to a new disk has to be done if there is no option already available on a shared bus. It's the disk that was originally used to build the operating system and from which ran clu_create (8) was run. It is recommended to keep this disk and the operating system file systems intact after installation. I/O Barriers are used in TruCluster Server version 5 to ensure data integrity in the cluster. For systems to be allowed to access storage, the member must be a part of the cluster and the cluster must have quorum.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.