Veritas Question 1

[cndcadams]

Confused on what is going on and why?

I have a Solaris test system which I have been playing around with Veritas 3.5 for upgrade knowledge. I am encapsulating the boot drive and mirroring it because some of the customers we support do this. I have been told many times by people not to encapulate boot drive but i can not control what our customers do. With that said this is my issue.

I load Solaris, then load veritas, then encapsulate the boot drive which goes fine, and my partitions I set up are maintained if I look at a prtvtoc output. The Issue I have is that when I mirror the boot drive the alternate boot drive actually ends up with the usr and var partitions on different slices then the main boot disk. I attached the format partition table so you guys can see what I am talking about. Also before I encapsulate the boot drive I have made the alternate boot drive partitions exactly the same as the main drive, so I know that Veritas is doing the change.

I have read through most of the Veritas documentation and can't seem to find anything that would explain why they do this?????

If anyone else has mirrored encapulated boot drive does yours also have different partitions?


Partition table for c0t0d0
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 1083 1.86GB (1084/0/0) 3892644
1 swap wu 1086 - 1668 1022.24MB (583/0/0) 2093553
2 backup wm 0 - 4923 8.43GB (4924/0/0) 17682084
3 var wm 1669 - 2524 1.47GB (856/0/0) 3073896
4 - wu 1085 - 1085 1.75MB (1/0/0) 3591
5 usr wm 2525 - 4235 2.93GB (1711/0/0) 6144201
6 unassigned wm 0 0 (0/0/0) 0
7 - wu 0 - 4923 8.43GB (4924/0/0) 17682084

Partition table for c0t1d0

Part Tag Flag Cylinders Size Blocks
0 root wm 689 - 1772 1.86GB (1084/0/0) 3892644
1 swap wu 1773 - 2355 1022.24MB (583/0/0) 2093553
2 backup wm 0 - 4923 8.43GB (4924/0/0) 17682084
3 - wu 0 - 0 1.75MB (1/0/0) 3591
4 - wu 1 - 4923 8.43GB (4923/0/0) 17678493
5 unassigned wm 0 0 (0/0/0) 0
6 usr wm 2356 - 4066 2.93GB (1711/0/0) 6144201
7 var wm 4067 - 4922 1.47GB (856/0/0) 3073896


Thanks

CA

 

[smishra]

Hi,
Veritas uses slice 3 and 4 to store private region and public region offset while creating a mirror disk i.e c0t1d0
.Initially when u have installed the Core OS in c0t0d0, u have already created var in slice number 3. So, when u did encaspulation, VM stored it's private region and public region offset in slice 4 and other available slice no. 7. So if you want to see VTOC of both mirror disks as same, then don't use slice 3 and 4 while installation of core OS ( Here I have assumed that u are being forced to use encaspulated root disk).

Thanks,
smishra

 

[cndcadams]

smishra;

Thank you very much for that info. I will have to go back over my veritas documents and specifically read up on that again.

CA