Monitoring file systems backup

Login or Register to Reply

 
Thread Tools Search this Thread
# 1  
Monitoring file systems backup

Hello,
I have some questions.
There are some File systems which are located on a SAN. There are two scenarios:
1) Some file systems are permanently mounted on certain servers
2) Others are part of a high availability cluster

In case of a cluster the needed file systems for a certain application are all visible to all cluster nodes (cluster servers) at the same time. A certain node is assigned to primarily run a certain service. Therefore it mounts the file system and provides the service as a new, virtual IP. The trick is now, that the virtual IP and virtual name can also be brought up by another cluster node in case the first one fails. This by itself is not a problem but it has turned out that this provides a problem for the backup because the backup is naturally file system oriented. From a user (or calling services) perspective the user only talks to the virtual IP and name, which never changes. He has no idea that this IP is in reality running on a physical cluster node with its own IP and name and on top of that the cluster nodes can even change.

by the default log file, I just get the machine names, mount points, full backup and incremental backups.

Now the question is how to be sure if file systems are correctly backed up?


I can think of some aproached:
1- check the list of file system and check the list of backed up files and compare to see if those FS are in back up. we pay attention to timestamp
2- the same as above but this time comparing also the size
3- check if machines in general are backed up
4- MD5 checksum

can someone give me any other idea and in general some suggestion?

Thanks
# 2  
You don't state what hardware platform you have, what the cluster software suite is, or what the backup software is.

Your post indicates that you have a good understanding of how a (generically speaking) cluster works and that any one filesystem can only be under the control of one node at a time. Having multiple nodes thinking they could write to the volume would be anarchy and a clear recipe for data corruption. It is definitely the job of the cluster software suite to ensure that that never happens. Having said that, different cluster suites can have starkly different functionality.

Similarly, backup software suites also vary in the manner of operation.

So discussing cluster backup in generic terms I would say that there are two options for implementing backups. Firstly, when node-A fails and node-B takes over (by checking orphaned filesystems and then mounting them, taking over and broadcasting the cluster name and ip address (node-C and ipaddr-C) some cluster software will also failover scheduled jobs (eg, backup). Of course, the backup device(s) need to be still available (or node-B needs to have its own tape drive, for example) for this to work. Alternatively, like all the user community who only know about node-C and ipaddr-C, the backup is run from a machine outside the cluster which "calls in" on node-C, accesses or NFS mounts the filesystem, and backs it up. Usually, this is the preferred method.

Now in this scenario the backup software has no knowledge that it is backing up a cluster volume and it should work exactly the same way as it would with a local volume, ie, if it loses communication with the volume, it will report a backup failure. Some backup software suites (eg, NetBackup) are of client/server architecture which are very intelligent and will report failures in exactly the same way they usually do.

So in summary, the fact that it is a cluster should be largely irrelevant to reporting errors in backup schedules. How the success of a backup is verified is the same as the non-cluster scenario.

Hope that helps. Feel free to continue your questions but please give us all a clue of the platform and software(s) involved.

Last edited by hicksd8; 05-11-2014 at 11:46 AM..
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
How to exclude directory from (File Systems) backup?
Mohannad
Hello AIX experts, I have a file system called /bossapp Its size = 77.5 GB I want to take a File Systems backup for this one using smitty, it is very easy, but the problem is I want to exclude one directory called (ORIGIN). How? The steps are very easy to take a File Systems backup,...... AIX
2
AIX
Monitoring Unix systems
gen4ik
I am looking for a commercial tool that will give me -UNIX Monitoring performance solution+ reports on CCV format. (as perfmon on windows machines). The tool must have following counters per PROCESS: Page Faults/sec Virtual Bytes % Processor Time Handles count Threads count...... UNIX for Dummies Questions & Answers
19
UNIX for Dummies Questions & Answers
Backup Linux file systems
aravind_mg
Hi, I need to backup files on our Solaris machines onto a windows machine. I have Samba installed. Is it possible to backup these files on Solaris/Linux machines onto a Windows machine. Thanks Aravind... Filesystems, Disks and Memory
1
Filesystems, Disks and Memory
UNIX and Linux

Unix (trademarked as the UNIX certification mark) is a very mature family of multitasking, multiuser computer operating systems that evolved from the original AT&T Unix. Unix development starting in the 1970s by legendary Bell Labs programmers Ken Thompson, Dennis Ritchie, and others. Unix was first targeted for the Bell System and AT&T licensed Unix to outside parties. In the 1970s time period, this lead to a variety of for-profit as well as not-for-profit Unix variants.
In the early days, this included the University of California, Berkeley (BSD), Microsoft (Xenix), IBM (AIX), and Sun Microsystems (Solaris). In the early 1990s, AT&T sold their Unix rights to Novell. In 1995 Novell sold their Unix business to the Santa Cruz Operation (SCO). The UNIX trademark was passed to The Open Group, a "neutral" industry consortium. The Open Group promoted the use of the UNIX trademark for certified operating systems that comply with the Single UNIX Specification (SUS). In 2014 Apple's macOS became the Unix version with the largest global install base and macOS remains the largest Unix-user base today.
Linux is a family of open source Unix-like operating systems based on the Linux kernel. The Linux kernel is an operating system kernel first released by Linus Torvalds on 17 September 1991. Linux distributions include the Linux kernel, system software and libraries. Popular free open source Linux distributions include Debian, Fedora, and Ubuntu. Commercial Linux distributions include Red Hat Enterprise Linux and SUSE Linux Enterprise Server. Linux may be freely modified and redistributed. Anyone on the planet may create a Linux distribution for any purpose.
Please enjoy and help our forum community by "showing your work" and posting your code, even when your code is not working as expected. To help others help you, please wrap your code blocks, sample input, sample output, error messages, and other data in CODE tags and wrap your short commands and short data objects in ICODE tags. We were all beginners in the beginning. If you have any questions about how to register or how to post, please contact us in Live Chat. Thank you and enjoy this "forever free" technical support community for UNIX, Linux and computer information technology in general.