SEO

Hi

I have recently mirrored the boot disks on my machine using Veritas
Volume Manager VxVM 4.1 and Solaris 9. Ater mirroring the disks when i
look at the partition table, following questions come in my mind


1. Is this a problem, if root slice does not start from cylinder 0 i.e.

it starts from cylinder 2 or any other.?
2. should the partition table of both disks look same ?


I am pasting the partition tables of both disks below


Disk 1
Part Tag Flag Cylinders Size Blocks
0 root wm 6595 - 9686 15.00GB (3092/0/0)
31464192
1 swap wu 0 - 6594 32.00GB (6595/0/0)
67110720
2 backup wm 0 - 14086 68.35GB (14087/0/0)
143349312
3 - wu 0 - 14086 68.35GB (14087/0/0)
143349312
4 - wu 14085 - 14086 9.94MB (2/0/0)
20352
5 unassigned wm 0 0 (0/0/0)
0
6 unassigned wm 0 0 (0/0/0)
0
7 unassigned wm 9687 - 9790 516.75MB (104/0/0)
1058304


Disk 2


Part Tag Flag Cylinders Size Blocks
0 root wm 2 - 3093 15.00GB (3092/0/0)
31464192
1 swap wu 3198 - 9792 32.00GB (6595/0/0)
67110720
2 backup wu 0 - 14086 68.35GB (14087/0/0)
143349312
3 - wu 1 - 1 4.97MB (1/0/0)
10176
4 - wu 2 - 14086 68.34GB (14085/0/0)
143328960
5 unassigned wm 0 0 (0/0/0)
0
6 unassigned wm 0 0 (0/0/0)
0
7 unassigned wm 3094 - 3197 516.75MB (104/0/0)
1058304


Also, tell me if there are any good practices for mirroring boot disks
as i have to mirror boot devices of other systems using veritas volume
manager.


Regards
Arif Iqbal

itsmearif@gmail.com wrote:


> 1. Is this a problem, if root slice does not start from cylinder 0 i.e.

Hi man, no isn't a problem if FOR NOW the root slice don't start from
cylinder 0

> it starts from cylinder 2 or any other.?

The best way for start point of root slice in a encaspulated volume like
a rootvol, is start from cylinder 2 because with cyl 0 and 1 VxVM can
protect the block zero (the VTOC). Private region must to be start at
start of the disk, vxvm when have a root slice that don't start from cyl
2, create a little volume called rootdiskPriv and a subdisk called
"rootdisk-B0".

I see that the disk 2 is a mirror disk because after encapsulation
veritas can't modify the partition table, but can when you mirror a disk
with vxdiskadm command.


> Disk 2
>
>
> Part Tag Flag Cylinders Size Blocks
> 0 root wm 2 - 3093 15.00GB (3092/0/0)
> 31464192
> 1 swap wu 3198 - 9792 32.00GB (6595/0/0)
> 67110720
> 2 backup wu 0 - 14086 68.35GB (14087/0/0)
> 143349312
> 3 - wu 1 - 1 4.97MB (1/0/0)
> 10176
> 4 - wu 2 - 14086 68.34GB (14085/0/0)
> 143328960
> 5 unassigned wm 0 0 (0/0/0)
> 0
> 6 unassigned wm 0 0 (0/0/0)
> 0
> 7 unassigned wm 3094 - 3197 516.75MB (104/0/0)
> 1058304
>

The best way for mirror disk is encapsulate the root disk, mirror disk
with vxdiskadm (like now) and after resync, remove plex, remove primary
disk and vxdiskunsetp of the disk, after reinizialized primary disk,
readd in rootdg and re mirror with vxdiskadm command.
After this you can see the slice of primary and mirror disk the same.

>
> Also, tell me if there are any good practices for mirroring boot disks
> as i have to mirror boot devices of other systems using veritas volume
> manager.

If you don't see for some reasons the slice 5,6 or 7, you can write it
with vxmksdpart command.

Bye