Here goes it(pdf file):

http://www.doxer.org/wp-content/uploads/2011/05/NetBackup_Commands.pdf

Firstly, please refer to http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Online_Storage_Reconfiguration_Guide/scanning-storage-interconnects.html for some pre-checking, like memory usage, sync etc.
Then, we should scan for new disk connected to hba one by one(issue_lip, Scenario:fabric on Linux with Emulex hbas), we should check dmpnodes are ALL in ENABLED state before moving on to another hba. This is because when scanning for new disks, we expect to result in disabling paths on that controller – and moving on only when the paths are confirmed enabled again. And during all procedures, tail -f /var/log/messages would help.

1) Checked the messages file for any existing issues. Identified and eliminated concerns of I/O error messages which have occured for some time:
May 29 04:11:05 testserver01 kernel: end_request: I/O error, dev sdft, sector 0^M
May 29 04:11:05 testserver01 kernel: Buffer I/O error on device sdft, logical block 0^M
May 29 04:11:05 testserver01 kernel: end_request: I/O error, dev sdft, sector 0^M
/var/log/messages.1:May 27 22:48:04 testserver01 kernel: end_request: I/O error, dev sdjt, sector 8
/var/log/messages.1:May 27 22:48:04 testserver01 kernel: Buffer I/O error on device sdjt3, logical block 1
2)Saved some output for comparison later:
syminq -pdevfile > /var/tmp/syminq-pdevfile-prior
We expected device as hyper 2C27 so I looked for this device in the output and, as expected, did not find it.
vxdisk -o  alldgs list > /var/tmp/vxdisk-oalldgs.list
3)Checked the current state of the vm devices dmp subpaths:
for disk in `vxdisk -q list | awk ‘{print $1}’`
do
echo $disk
vxdmpadm getsubpaths dmpnodename=${disk}
done | tee -a /var/tmp/getsubpaths.out  Read more…

Don’t panic.

You can allocate more memory to solaris virtual machine(like 1024Mb) and try again.

In the Sun Forums thread, they say that 609 MB is the lowest you can go. You can give it a little more memory size if allowed.

Firstly, download xming, install it on your windows pc system.

You can go to http://sourceforge.net/projects/xming/files/ to download.

Let’s assume that you want to run xclock on solaris/linux server 192.168.0.3, and want the gui display on your pc whose ip is 192.168.0.4.

After installation xming on your windows, log in linux/solaris server 192.168.0.3. Set environment variable DISPLAY to the ip address of your windows, and append a :0 to it:

#export DISPLAY=192.168.0.4:0

Then you must allow X11 forwarding in sshd configuration file. That is, set X11Forwarding to yes in /etc/ssh/sshd_config and restart your sshd daemon.

After this, you need set 192.168.0.3(linux/solaris) to the allowed server list on your windows. Edit X0.hosts which locates at the installation directory of xming(For example, C:\Program Files\Xming\X0.hosts), add a new entry in it:192.168.0.3, the ip address of linux/solaris that you want to run x11 utility from.

Note: Thanks to linuxdict.com :D

Then, restart xming on your windows. And on solaris/linux server(192.168.0.3), run a X11 programe, like

#/usr/openwin/bin/xclock &

You will then see a clock gui pop up in your windows pc. Read more…

Here’s the output of format -> verify command in my solaris10:

format> verify

Primary label contents:

Volume name = < >
ascii name =
pcyl = 2609
ncyl = 2607
acyl = 2
bcyl = 0
nhead = 255
nsect = 63
Part Tag Flag Cylinders Size Blocks
0 root wm 1 – 1306 10.00GB (1306/0/0) 20980890
1 var wm 1307 – 2351 8.01GB (1045/0/0) 16787925
2 backup wu 0 – 2606 19.97GB (2607/0/0) 41881455
3 stand wm 2352 – 2606 1.95GB (255/0/0) 4096575
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 – 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0

Now, let’s give it an analysis:

• Part

Solaris x86 has 9 slices for a disk, and for 8th and 9th, they’re preserved by solaris.

• Tag

This is used to indicate the purpose of the slice. Possible values are:

unassigned, boot, root, swap, usr, backup, stand, home, and public, private(The latter two are used by Sun StorEdge).

• Flag

wm – this slice is writable and mountable.

wu - this slice is writable and unmountable.

rm - this slice is readable and mountable.

ru – this slice is readable and unmountable.

• Cylinders

This part shows the start and end cylinder number of the slice.

• Size

The size of the slice.

• Blocks

This shows the number of cylinders and sectors of the slice.

Now, let’s create a slice and mount the filesystem: Read more…

Netbackup reported:

The following “sns*” files in /ftp/ftpst/datain/sns_a/success have been archived:/ftp/ftpst/datain/sns_a/success/sns_closed_09042011_180000_2.data/ftp/ftpst/datain/sns_a/success/sns_closed_09042011_180000_1.data

However, these files were still within the directories.

Here goes my comprehension:

We have had similar issues with other hosts which turns out to be more of an issue in the reporting of the script. It reports on the things it has selected for archiving rather than what has successfully been archived. Read more…