Monitoring file systems backup Post: 302901023

Sponsored Content

Special Forums UNIX and Linux Applications Infrastructure Monitoring Monitoring file systems backup Post 302901023 by frhling on Saturday 10th of May 2014 04:34:12 PM

05-10-2014

Registered User

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

frhling

View Public Profile for frhling

Find all posts by frhling

4 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Backup Linux file systems

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

2. UNIX for Dummies Questions & Answers

Backup Software for UNIX systems

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

3. UNIX for Dummies Questions & Answers

Monitoring Unix systems

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...

4. AIX

How to exclude directory from (File Systems) backup?

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,...

LEARN ABOUT HPUX

cmhaltnode

cmhaltnode(1m)															    cmhaltnode(1m)

NAME

       cmhaltnode - halt a node in a high availability cluster

SYNOPSIS

       cmhaltnode [-f] [-v] [-t] [node_name...]

DESCRIPTION

       cmhaltnode causes a node to halt its cluster daemon and remove itself from the existing cluster.

       To halt cluster on the node, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configu-
       ration file. See access policy in cmquerycl.

       When cmhaltnode is run on a node, the cluster daemon is halted and, optionally, all packages that were running on that node  are  moved	to
       other nodes if possible.

       If node_name is not specified, the cluster daemon running on the local node will be halted and removed from the existing cluster.

       If  you issue this command while a cluster is still in the process of forming, the command will fail with the message "Unable to connect to
       daemon."  If this happens, wait for the cluster to form successfully, then issue the command again.

   Options
       cmhaltnode supports the following options:

	      -f	Force the node to halt even if there are packages or group members running on it.  The group members on the node  will	be
			terminated.   The halt scripts for all packages running on the node will be run; based on priority or dependency relation-
			ships, this may affect packages on other nodes. In other words, packages on other nodes may either start or halt based	on
			this  package halting.	If the package configuration and current cluster membership permit, and if the package halt script
			succeeds, the packages will be started on other nodes.	Without this option, if packages are running on  the  given  node,
			the command will fail.	If a package fails to halt, the node halt will also fail.

	      -v	Verbose output will be displayed.

	      -t	Test  only.  Provide  an assessment of the package placement without affecting the current state of the nodes or packages.
			This option validates the node's eligibility with respect to the package dependencies as well as the external dependencies
			such as EMS resources, package subnets, and storage before predicting any package placement decisions. If there is a pack-
			age in maintenance mode running on the nodes being halted, the package will always be halted and not failover  to  another
			node; the report will not display an assessment for that package.

	      node_name...
			The name of the node(s) to halt.

RETURN VALUE

       cmhaltnode returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Halt the cluster daemon on two other nodes:

	      cmhaltnode node2 node3

AUTHOR

       cmhaltnode was developed by HP.

SEE ALSO

       cmquerycl(1m), cmhaltcl(1m), cmruncl(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).

						      Requires Optional Serviceguard Software					    cmhaltnode(1m)