I have a Solaris 10 system configured with Veritas File Systems. The goal is to clone the diskgroup structure onto another systems so as to save time building the structure manually. I want all the volumes the same size and the same names as my source.
Below is a script used to perform this task. The script must be run from the source server. It then gets all of the diskgroup structure information then outputs into a file the commands needed to recreate.
At some point you may have a solaris non-global zone up and running but are not able to take it down to add a network interface. For the longest time I thought in order to make any config change to a local zone would require the zone to be halted. Not the case any more with Solaris 10.
If you are wanting to add a permanent network interface to the zone, you still must use zonecfg to configure the zone so that once it does reboot the interface will be there. From the global zone do:
Running EMC NetWorker server on a Server 2009 R2 w/ sp1 VM running on ESXi host. The VMDK is stored on a VNXe machine along with the VMDKs for all the other VM servers our organization runs. None of the other VMs have this issue:
Each night for the latter half of this week, sometime after 9pm, this server loses its hard drive. Checking the systems in the morning I find this machine sitting at the boot prompt after it has tried PXE and it reports it cannot find a bootable device. Checking the VM settings I find there is no hard drive attached to the machine.
You can easily add more swap to your system if swap is a part of rpool providing there is space available. If you do not have enough space in rpool to increase swap then you are SOL. The only option you have is to create another zfs pool with more luns (disks).
After carving up a Clariion lun to one of my sun servers. I tried to add it to Veritas but it kept failing with an error similar to
root:dwhdev2 :[/root] vxdisk -f init c#t#d3
VxVM vxdisk ERROR V-5-1-5433 Device c#t#d3: init failed:
Disk VTOC does not list private partition