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
mount(8) System Manager's Manual mount(8)
Name
mount, umount - mount or unmount file systems
Syntax
/etc/mount [ options ] [ device ] [ directory ]
/etc/umount [ options ] [ device ] [ directory ]
Description
This is a general description of the command. Additional descriptions are provided to define the syntax and options for the NFS and UFS
file systems.
Each invocation of the command announces to the system that a file system is present on the device device. The file system may be local or
remote. File directory must exist as a directory file. It becomes the name of the newly mounted file system root.
If invoked without arguments, prints the list of mounted file systems.
Physically write-protected disks and magnetic tape file systems must be mounted read-only or an error will occur at mount time.
General users can only mount file systems with certain restrictions. For example, the user, other than the superuser, performing the mount
must own the directory directory. Furthermore, no users other than the superuser can execute or programs on the mounted file systems. In
addition, users other than the superuser cannot access block or special character devices such as on the mounted file systems.
The command announces to the system that the removable file system previously mounted on the specified directory is to be removed. Only
the person who mounted a particular file system or the superuser can unmount the file system again.
Options
-a Reads the file and mounts, or unmounts, all file systems listed there.
-f Fast unmount. The option has no meaning for local file systems and directories. However, for remote file system types (such
as NFS), the option causes the client to unmount the remotely mounted file systems and directories without notifying the
server. This can avoid the delay of waiting for acknowledgment from a server that is down.
-o options Specifies a string that is passed to the kernel and used by the specific file system's mount routine in the kernel. For spe-
cific options, refer to the file system-specific description, such as
-r Indicates that the file system is to be mounted read only. To share a disk, each host must mount the file system with the -r
option.
-t type Specifies the type of file system is being mounted. When used with the option, the option mounts all file systems of the given
type found in the file. For specific file system types, refer to the file system-specific description, such as
-v Tells what did or did not happen. (Verbose flag)
The options for are:
-a Unmounts all mounted file systems. It may be necessary to execute twice to accomplish unmounting of all mounted file systems.
-v Tells what did or did not happen. (Verbose flag)
Restrictions
Mounting corrupted file systems will crash the system.
Files
File systems information table
See Also
getmnt(2), mount(2), fstab(5), fsck(8), mount(8nfs), mount(8ufs)
mount(8)