01-07-2002
I had trouble with this in the beginning also.
Volume Manager has to do with managing the disks, raid, striping, plexes, etc....
Veritas Filesystem is just that. Anything that you need to do to manage the data on the disks. Such as mkfs, mount, online resizing and defragmenting. It also gives you control over I/O, caching, and allocation.
Remember:
VM is managing the disks.
Veritas Filesystem is managing the data on the disks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
? (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. Solaris
Hi all,
I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume.
Please find a sutable solutions.
Thanks and Regards
B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies
3. UNIX for Advanced & Expert Users
hy guys
I am new at this thread , i have installed sf 5.0 and wanted to encapsulate root disk but when i get to optionn to enter private region i get this error:
Enter desired private region length
(default: 65536) 512
VxVM ERROR V-5-2-338
The encapsulation operation failed with the... (2 Replies)
Discussion started by: charneet
2 Replies
4. Solaris
Hi all,
Anybody know the URLs of veritas volume manager disk problems,volume problems,root disk problems ...etc.
Please share the URL's. i really appreciate for cooperation.
regards
krishna (4 Replies)
Discussion started by: murthy76
4 Replies
5. Solaris
Can somebody kindly help me to determine which one i should choose to better manipulate OS volume.
RAID manager or veritas volume manager?
Any critical differences between those two?
Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies
6. Solaris
Can you please let me know the certification code for veritas volume manager in solaris ? Thanks in advance. (2 Replies)
Discussion started by: gowthamakanthan
2 Replies
7. Solaris
Hi All,
recently i had the project.
Got 2 server, one is Mercury, and another is Procyon.
two server was attached to EMC Box and use the Veritas Filesystem.
My question is,
1. Is it possible first remove the filesystem(/u03,/u04) from Veritas in Procyon, no effect on the data? we still... (5 Replies)
Discussion started by: SmartAntz
5 Replies
8. Solaris
Hiii,
Can any one sugge me best practices for resizing a veritas voulume with vxfs file system?
I tried doing this
vxassist -g stg shrinkto stgvol 209715200
VxVM vxassist ERROR V-5-1-7236 Shrinking a FSGEN or RAID5 usage type volume can result in loss of data. It is recommended... (1 Reply)
Discussion started by: anwesh
1 Replies
9. UNIX for Dummies Questions & Answers
I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies
10. UNIX for Beginners Questions & Answers
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
vxsited(1M) vxsited(1M)
NAME
vxsited - site monitoring daemon
SYNOPSIS
/etc/vx/bin/vxsited [mail_address...]
DESCRIPTION
The vxsited daemon monitors Veritas Volume Manager (VxVM) for disks being attached, and reattaches a detached site if the disks that belong
to that site become accessible.
vxsited analyzes the output of the vxnotify command, and waits for a failed disk to attach. When a disk is attached, vxsited attempts to
online the disk, and tries to reattach the failed site. If a site is successfully reattached, vxsited starts recovery using vxrecover, and
sends mail to root (by default) or to other specified users.
Mail Notification
By default, vxsited sends mail to root with information about the disk status of any attempts to reattach the site. To send mail to other
users, add the user login name to the line that starts vxsited in the startup script, /etc/init.d/vxvm-recover, and reboot the system. For
example, if the line appears as:
nohup vxsited root &
and you want mail also to be sent to user1 and user2, change the line to read:
nohup vxsited root user1 user2 &
Alternatively, kill the vxsite process, and restart it from the command line with the required mail addresses as arguments.
The mail notification has a format that is similar to the following:
Subject : Volume Manager site reattach on host hostname
Reattached site sitename in disk-group diskgroup
Reattachment Procedure
If a disk from a detached site becomes accessible again, vxsited checks whether the relocation daemon, vxrelocd, is running. If vxrelocd
is running, vxsited attempts to reattach the site. The relocation daemon can then try to relocate the failed subdisks using space on the
available disks in the disk group. If the failed objects are successfully relocated, vxrelocd changes the state of the site to RECOVER,
and starts the recovery of volumes at the site. When all the plexes at a site have been recovered, the plexes are put into the ACTIVE
state, and the state of the site is set to ACTIVE.
If vxrelocd is not running, vxsited only reattaches a site when all the disks from that site become accessible. After successfully reat-
taching a site, vxsited changes the site state to ACTIVE, and initiates recovery using vxrecover. When all the plexes from a site have been
recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE.
vxsited does not attempt to reattach a site that has been explicitly detached by an administrator. The state OFFLINE is set for sites that
have been detached by using the following command:
vxdg -g dg_name detachsite sitename
Disabling vxsited
If you do not want a site to be recovered automatically, kill the vxsited daemon, and prevent it from restarting. To kill the daemon, run
the following command from the command line, and locate the process table entry for vxsited:
ps -ef
Execute the command:
kill -9 PID
Substitute the process ID of the vxsited process for PID. To prevent vxsited from being restarted, comment out the line that starts
vxsited in the startup script /sbin/init.d/vxvm-recover.
FILES
/sbin/init.d/vxvm-recover The startup file for vxsited.
SEE ALSO
kill(1), mailx(1), ps(1), vxdg(1M), vxrelocd(1M), vxintro(1M), vxnotify(1M), vxrecover(1M)
VxVM 5.0.31.1 24 Mar 2008 vxsited(1M)