05-11-2014
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 12:46 PM..
4 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
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 (1 Reply)
Discussion started by: aravind_mg
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
which software is recommended for backup of UNIX systems ( e.g. SUN, Solaris ). Backup software and database e.g. Oracle.
One possibility is Networker, but license is expensive and also service contract.
Best regards
Dieter (2 Replies)
Discussion started by: rhacodactylus
2 Replies
3. UNIX for Dummies Questions & Answers
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... (19 Replies)
Discussion started by: gen4ik
19 Replies
4. AIX
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,... (2 Replies)
Discussion started by: Mohannad
2 Replies
FSTAB(5) File Formats Manual FSTAB(5)
NAME
fstab, mtab - list of file systems to mount, mounted file system table.
SYNOPSIS
/etc/fstab
/etc/mtab
DESCRIPTION
/etc/fstab is a table of file system to mount at boot time, /etc/mtab is a table of currently mounted file systems as maintained by mount
and umount.
/etc/fstab is not read by mount as it should be. It is instead a simple shell script listing the three devices that Minix needs to oper-
ate: The device names of the root file system, the temporary (scratch) file system, and the file system for /usr. Of these only the /usr
file system is mounted in /etc/rc, the scratch file system is there for the system administrator to test new kernels, or as a temporary
file system.
/etc/mtab contains lines of four fields. The layout is:
device directory type options
These fields may be explained as follows:
device
A block special device.
directory
Mount point.
type
Either 1, or 2, indicating a V1 or V2 file system.
options
Either ro, or rw, indicating a read-only or read-write mounted file system.
FILES
/etc/fstab Shell script naming three important file systems.
/etc/mtab List of mounted file systems.
SEE ALSO
printroot(8), mount(1), fsck(1), mkfs(1).
BUGS
/etc/fstab is a joke.
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
FSTAB(5)