VVR error while configure
Updated: 21 May 2010 | 7 comments
Dear All,
We have installed SF 5.0 MP1 (vxvm, vxfs, vvr) in two server which have solaris 8 os. We are trying to configure vvr, it gives following error.
bash-2.03# vradmin -g rootdg createpri pr_rds data rep_log
Message from Primary:
VxVM vxassist ERROR V-5-1-434 Cannot allocate space for 512 block log
bash-2.03#
Please reply if anybody knows.
Regards,
Dharmesh
discussion Filed Under:
Comments
Operation failed due to insufficient space
Hi Dharmesh,
It looks like your data volume does not have sufficient space to add DCM logging for VVR configuration.
Kapalin
Hi Kapalin, Thanks for
Hi Kapalin,
Thanks for reponse.
the "data" volume is 20 GB and currently it is empty.
Regards,
Dharmesh
Dharmesh, The log is not
Dharmesh,
The log is not allocated from the space on volume; it's a separate object that's being allocated from space in the disk group.
Thus, from the error, it appears the disk group does not have sufficient space to add the log (see "Associating a Data Change Map to a data volume" for guide of what log size should be here: http://sfdoccentral.symantec.com/sf/5.0/solaris/ht... )
Check the disk group has sufficient space (vxdg -g <dg> free) to add the DCM; if it doesn't then either add space to the dg or shrink the volume so the createpri has space to allocate the DCM.
If this post has helped you, please vote or mark as solution
Thanks for reply, We are
Thanks for reply,
We are trying following command but the result are same.
bash-2.03# vradmin -g rootdg createpri pr_rds data rep_log
Message from Primary:
VxVM vxassist ERROR V-5-1-434 Cannot allocate space for 512 block log
bash-2.03# vxassist -g rootdg addlog data logtype=dcm
VxVM vxassist ERROR V-5-1-434 Cannot allocate space for 512 block log
Also check the following command
vxdg -g rootdg free
bash-2.03# vxdg -g rootdg free
DISK DEVICE TAG OFFSET LENGTH FLAGS
rootdg01 c1t0d0s2 c1t0d0 69644543 40968576 -
rootdg01 c1t0d0s2 c1t0d0 167252735 119344128 -
please reply.
VVR mirrors the DCM by default
"VVR mirrors the DCM by default" (from link provided above, above the Note section)
The vxdg free output shows only one disk (rootdg01) has free space - therefore vradmin & vxassist cannot create a mirrored DCM, so this is why your command(s) are failing.
Therefore, you need to free up space on another disk / add another disk to the diskgroup to be able to create a mirrored DCM.
Hope that helps
Edit: although it's preferred/strongly recommended to mirror the DCM, if still wish to proceed with unmirrored DCM the following technote may be useful: http://seer.entsupport.symantec.com/docs/239712.htm
If this post has helped you, please vote or mark as solution
Dear, Thanks, Can you reply
Dear,
Thanks,
Can you reply with the all steps for normal configuring VVR between two solaris 8 sparc server with requirement lik vxvm etc.
Regards,
Dharmesh, As the exact
Dharmesh,
As the exact configuration is dependent on your particular requirements/environment, would suggest looking at the VVR Administrator's Guide and VVR Planning and Tuning Guide to determine what is best for your current setup.
Link below is for Solaris 5.0MP3, the VVR documents are at the bottom:
http://sfdoccentral.symantec.com/Storage_Foundatio...
The following sections in particular may be helpful as starting points (from Administrator's Guide)
Chapter 1 - Introducing Veritas Volume Replicator
Components of VVR
http://sfdoccentral.symantec.com/sf/5.0MP3/solaris...
Chapter 4 - Setting up replication:
Best practices for setting up replication
http://sfdoccentral.symantec.com/sf/5.0MP3/solaris...
Creating a Replicated Data Set
http://sfdoccentral.symantec.com/sf/5.0MP3/solaris...
Examples for setting up a simple Volume Replicator configuration
http://sfdoccentral.symantec.com/sf/5.0MP3/solaris...
If this post has helped you, please vote or mark as solution
Would you like to reply?
Login or Register to post your comment.