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

cmrunnode

cmrunnode(1m)															     cmrunnode(1m)

NAME

       cmrunnode - run a node in a high availability cluster

SYNOPSIS

       cmrunnode [-v] [node_name...]  [-t | -w none]

DESCRIPTION

       cmrunnode  causes  a node to start its cluster daemon to join the existing cluster.  This command verifies the network configuration before
       causing the node to start its cluster daemon.

       To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus-
       ter configuration file. See access policy in cmquerycl(1m).

       Starting  a node will not cause any active packages to be moved to the new node.  However, if a package is DOWN, has its switching enabled,
       and is able to run on the new node, that package will automatically run there.

       If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster.

   Options
       cmrunnode supports the following options:

	      -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. The	-w
		   option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet
		   any external dependencies such as EMS resources, package subnets, and storage.

	      node_name...
		   Start the cluster daemon on the specified node(s).

	      -w none
		   By default network probing is performed to check that the network connectivity is the same as when the cluster was  configured.
		   Any	anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should
		   only be used if this network configuration is known to be correct from a recent check.

RETURN VALUE

       cmrunnode returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Run the cluster daemon on the current node:

	      cmrunnode

       Run the cluster daemons on node1 and node2:

	      cmrunnode node1 node2

AUTHOR

       cmrunnode was developed by HP.

SEE ALSO

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

						      Requires Optional Serviceguard Software					     cmrunnode(1m)