05-10-2014
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
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
LEARN ABOUT DEBIAN
votequorum_leaving
VOTEQUORUM_LEAVING(3) Corosync Cluster Engine Programmer's Manual VOTEQUORUM_LEAVING(3)
NAME
votequorum_leaving - Tell other nodes that we are leaving the cluster
SYNOPSIS
#include <corosync/votequorum.h>
int votequorum_leaving(votequorum_handle_t handle);
DESCRIPTION
The votequorum_leaving function is used to tell the other nodes in the cluster that this node is leaving. They will (when the node actually
leaves) reduce quorum to keep the cluster running without this node.
This function should only be called if it is known that the node is being shut down for a known reason and could be out of the cluster for
an extended period of time.
Normal behaviour is for the cluster to reduce the total number of votes, but NOT expected_votes when a node leave the cluster, so the clus-
ter could become inquorate. This is correct behaviour and is ther eto prevent split-brain.
Do NOT call this function unless you know what you are doing.
RETURN VALUE
This call returns the CS_OK value if successful, otherwise an error is returned.
ERRORS
The errors are undocumented.
SEE ALSO
votequorum_overview(8), votequorum_initialize(3), votequorum_finalize(3), votequorum_dispatch(3), votequorum_fd_get(3),
corosync Man Page 2009-01-26 VOTEQUORUM_LEAVING(3)