Data Protector: Object is a mounted filesystem => not restored.

Unexpected mounted filesystems detected when restoring a disk imageWhen restoring a disk image, you get a message that the disk image being restoredis a mounted filesystem and will not be restored:

Object is a mounted filesystem => not restored.

This happens when an application on the disk image leaves some patterns on thedisk image. The patterns confuse the system call that verifies whether the filesystemon the disk image is mounted or not, so the system call reports that there is a mountedfilesystem on the disk image.

Solution

1. Try zero out the device

dd if=/dev/zero of=/dev/r[logical volume] bs=8k

2. For AIX, lslv [logical volume] , verify it doesn’t contain DS_LVZ, otherwise, recreate it without -T O
3. For AIX with IBM SAN Volume Controller, run

lquerypr -ph  /dev/vpathX

4. For AIX, try not varyon the volume group in concurrent mode.

 

http://www.google.com/url?sa=t&source=web&cd=2&ved=0CBwQFjAB&url=http%3A%2F%2Fbizsupport.austin.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc01631245%2Fc01631245.pdf&rct=j&q=%22Object%20is%20a%20mounted%20filesystem%20%3D%3E%20not%20restored.%20%22&ei=ywWTTbuzJsaPcdWJpYkH&usg=AFQjCNGYnyf6RUAjGFa41m188gLmkq-Nqw&cad=rja

HPUX Managing CPU resource with PRM

Overview

Process Resource Manager (PRM) is a resource management tool used to control the amount of resources that processes use during peak system load (at 100% CPU resource or 100% memory resource). PRM can guarantee a minimum allocation of system resources available to a group of processes through the use of PRM groups.
A PRM group is a collection of users and applications that are joined together and assigned certain amounts of CPU and memory resource. The two types of PRM groups are FSS PRM groups and PSET PRM groups. An FSS PRM group is the traditional PRM group, whose CPU entitlement is specified in shares. This group uses the Fair Share Scheduler (FSS) in the HP-UX kernel within the system’s default processor set (PSET). A PSET PRM group is a PRM group whose CPU entitlement is specified by assigning it a subset of the system’s cores (PSET). (A core is the actual data-processing engine within a processor. A single processor might have multiple cores. A core might support multiple execution threads.) Processes in a PSET have equal access to CPU cycles on their assigned cores through the HP-UX standard scheduler.

Continue reading “HPUX Managing CPU resource with PRM”

Prepare user access right on Data Protector Cell Manager

Data Protector Server run on HP-UX, and managed by Windows Data Protector Cell Manager

You have to grant a suitable access right to your client workstation in order to manage with “Data Protector Manager”

Login as root

run

<pre lang=”bash”>/opt/omni/bin/omniusers  -add -type W -usergroup admin -name administrator -group \* -client \*</pre>

usergroup: admin Data Protector administrator privilege
name: administrator User login as administrator on Windows
group: \* The username belongs to any group
client: \* The client workstation can access Cell Manager from any Hostname

solaris patch installation for dummy

Important for solaris 10 user!

If your patch list included 141742-0?, make sure your /etc/ssh/sshd_config contain the following line for preferred encryption. Test it before start your patching.

Ciphers aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc

See the bug detail from here: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6850734

Here we go!
Continue reading “solaris patch installation for dummy”

matching cipher is not supported: aes256-cbc

ssh failed after 141742-01/02 patch on solaris 10 !

enabled aes192/aes256 support in ssh/sshd does not work on S10u3 or older released

A workaround is to disable the use of aes192/aes256 ciphers for ssh and sshd. Change the two config files /etc/ssh/ssh_config and /etc/ssh/sshd_config and add the following line:

Ciphers aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc

You’ll have to restart sshd to pickup the change (“svcadm restart ssh”).

hpux: How Do I configure routing or add route?

You can use route command to configure routing. Syntax is as follows:

route add net {network-address} netmask {subnet} {router-address}

Let us assume your router address is 192.168.1.254 and network ID is 192.168.1.0/24, then you can type route command as follows:

# route add net 192.168.1.0 netmask 255.255.255.0 192.168.1.254

OR

To add a default route:

# route add default 192.168.1.254

Verify that (display) routing table is updated (display routing table):

# netstat -nr

Test it i.e. try to ping or send nslookup request:

# ping mycorp.com

To flush all routing entries use command [quite handy to clean your gordian knot ;)] :

# route -f

However if I reboot HPUX box then above routing entries gets removed. To pick up your setting upon each reboot your need to configure Routes in HPUX networking configuration file – /etc/rc.config.d/netconf. To add default router/gateway 192.168.1.254:

# vi /etc/rc.config.d/netconf
Add or modify following entries

ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="192.168.1.254"
ROUTE_COUNT[0]="1"
ROUTE_ARGS[0]=""

managing hpvm

Start a VM

hpvmstart -P vmname

Stop a VM

hpvmstop -P vmname

List VM status

hpvmstatus

List individual VM status

hpvmstatus -P vmname

Assign a Host LV to a VM

hpvmmodify -P vmname -a disk:scsi:lv:/dev/vg_vm/rlv_vm01

Assign a Host scsi disk to a VM

hpvmmodify -P vmname -a disk:scsi:lv:/dev/rdsk/c0t0s0

Assign a Host tape drive to VM

hpvmmodiy -P vmname -a tape:scsi:attach:/dev/rscsi/c5t3d0

Remove allocated resource from VM

hpvmmodify -P vmname -d disk:scsi:lv:/dev/rdsk/c0t0s0