Hi Aleksandr,
Your confusion is not unfounded.
SFCFS and SFCFS are separately licensed features. SFCFS with VCS is good
for configuration of a clustered environment but it lacks some failover
capabilities which are only available with SFCFS HA which additionally
includes some HA agents which
Is it occuring after you reinstalled your VM from 4.1 to 5.0 ?
Ravi kumar wrote:
Hi All,
Has anyone seen this error? If so how is it repaired?
-bash-3.00# vxdisk list
VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not
accessible
-bash-3.00# vxconfigd
VxVM
Hi Folks,
I am a bit confused over Storage Checkpoint and Snapshot. Which one
should one use over other ? In what scenarios are does checkpoint scores
over snapshot and vice versa. Any leads to any document or reference is
appreciated.
Regards,
Amit
I guess VxFS allows compression with the help of fsadm command. more
specifically, fsadm -d is the option to compress the directories.
You can refer to following URL :
http://docs.hp.com/en/B2355-90691/fsadm_vxfs.1M.html.
Please let me know if this helps..
Esson, Paul wrote:
Folks,
yes, As Sharninder pointed out, there is no compression facility
available in VxFS. fsadm -d option reorganizes the directory on the
basis of of their access time. While doing this reorganization, it also
frees up some space if possible.
Sharninder wrote:
Apologies if this list is VxVM
The node that is master or slave can be found out by the command vxdctl
-c mode. To find the primary node after the a volume is mounted the
command is fsclustadm.
For Eg: I have node1,node2 and node3 and a vol1 is mounted across all
the nodes. There will be 1 node which will be primary. To find
)
Please note that this will set node1 as primary for only vol1. For
different volumes you can set different nodes as primary.
Hope this helps even better.
-Amit
Amit Chaurasia wrote:
The node that is master or slave can be found out by the command vxdctl
-c mode. To find the primary node after
