This is just my own notes on Veritas Netbackup Command Line Guide, feel free to copy-paste;-):
————————————————————————————-
/usr/openv/netbackup/bin/jnbSA >>run NBU GUI
/usr/openv/netbackup/bin/bpadm >>NBU Menu Interface
/usr/openv/volmgr/bin/vmquery -deassignbyid QOSFEB 1 0 >>deassign media
/usr/openv/netbackup/bin/admincmd/bpexpdate -m QOSFEB -d 0 -force >>Expired
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -L >
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -add -max_jobs 99 >>set max jobs to 99
/usr/openv/netbackup/bin/bplist -C aziz -t 4 -R / >>chek list file that backed up already
/usr/openv/netbackup/bin/bpbackup -i -p test -s full -S sunserver1 >>Run jobs
/usr/openv/volmgr/bin/ltid -nsu >>robot will’t unload tape
/usr/openv/volmgr/bin/stopltid >>stop ltid
/usr/openv/netbackup/bin/admincmd/bperror -statuscode 96 >>explanation error
/usr/openv/netbackup/bin/admincmd/bpbackupdb >>backup catalog
/usr/openv/netbackup/bin/bpclntcmd -pn >>query master server communication
/usr/openv/netbackup/bin/bpclntcmd -sv >>query master server version
/usr/openv/netbackup/bin/admincmd/get_license_key >>add/remove license key
#/usr/openv/netbackup/bin/admincmd/:
bpmedia -movedb -ev -oldserver -newserver
bpmedia -movedb -ev PR0161 -oldserver drsskdb1 -newserver masterbackup >>move database to newserver
bpimage -newserver masterbackup -oldserver drsskdb1 -id BI0336 >>
/usr/openv/volmgr/bin/vmoprcmd -crawlreleasebyname
/usr/openv/netbackup/bin/bpdbm -consistency >>Catalog Backup Integrity check
Restore Catalog:
—————–
/usr/openv/netbackup/bin/admincmd/bprecover –help
/usr/openv/netbackup/bin/admincmd/bprecover -r all -dpath f: >>restore dari catalog di disk
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d dlt >>tape model dlt
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d 8mm >>tape model 8mm
/usr/openv/netbackup/bin/admincmd/bprecover -r all -tpath /dev/rmt/0cbn >>
bprecover -l -tpath /dev/rmt/hc2d4
————
{Verify the Netbackup communication daemons are listening for request:
netstat -a |grep bpcd
netstat -a |grep vnetd
{UNFREEZE TAPE MEDIA MARKED AS FROOZEN:
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT738L4
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT626L4
c:\Program Files\Veritas\Netbackup\bin> bpmedia -unfreeze -m -h
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -U -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -L -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bpmedialist -summary
c:\Program Files\Veritas\Netbackup\bin\goodies\available_media
{Remove information about existing media ID from NBU Catalog then delete the existing media ID:
/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -m
{initiate import media ID JKT152:
./bpimport -create_db_info -id JKT152
——————————————————————————————–
TUNING AND TWEAKING:
/usr/openv/netbackup
cat /usr/openv/netbackup/NET_BUFFER_SZ
65536
For example, a Network Buffer Size of 64KB could be configured and checked like this:
# echo “65536″ > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
65536
/usr/openv/netbackup/db/config:
NUMBER_DATA_BUFFERS
SIZE_DATA_BUFFERS
NUMBER_DATA_BUFFERS_RESTORE
NUMBER_DATA_BUFFERS:
8 for non-multiplexed backups
4 for multiplexed backups
8 for non-multiplexed restore, verify, import and duplicate
SIZE_DATA_BUFFERS:
32768 for non-multiplexed backups
65536 (64512 on Solaris) for multiplexed backups
NUMBER_DATA_BUFFERS_RESTORE:
12 (only effects restores of multiplexed backups)
—-
tpautoconf -report_disc , this command will list what device that had been missing or found.
tpautoconf -replace_drive drive_name –path drive_path, this command will update the existing device
{STOP NEXT SHCEDULE BACKUP REQUEST:
bprdreg -terminate >>WILL STOP BPRD services
{SHARED SYMANTEC PROCESS:
check with bpps -x command:
/opt/VRTSpbx/bin/vxpbx_exchange start
/opt/VRTSpbx/bin/vxpbx_exchange stop
Worm:W32/Downadup.gen, W32/Conficker.worm.gen, Mal/Conficker, Worm: Win32/Conficker
Conficker, also known as Downup, Downadup and Kido, is a computer worm targeting the Microsoft Windows operating system that was first detected in November 2008. The worm uses a combination of advanced malware techniques which has made it difficult to counter, and has since spread rapidly into what is now believed to be the largest computer worm infection since the 2003 SQL Slammer.
Sun StorageTek SL8500 is powerful tape library which enables 24×7 availability with fully redundant and replaceable robotics. StorageTek SL8500 modular library system is Sun extreme machine in storage. No matter how big you are or fast you grow, it totally accommodates your offline tape needs for data backup, archiving, and protection. It’s modular and can expand to 448 tape drives and 70,0001 tape slots–just under 200 feet long. just go to here for detail features and specifications.
Sun StorageTek SL8500 is an enterprise-class robotic tape library. One library stores a maximum of 6.5 petabytes of storage spread over 10000 cartridges. It supports a maximum of 64 tape drives. It uses up to 8 indepentent robots in each library. Up to seven such libraries can be connected side-by-side and automatically pass tapes between each other, forming a complex capable of storing over 70 PB of data and mounting 448 tape drives. Each tape drive installed in the sl8500 library has an independent data path. The aggregate data rate for all drives is 193.2 TB/hr. (Wikipedia).
Breaking Solaris SVM is easy, but sometimes if we type wrong command it will become a big trouble and wasting time to troubleshoot, like what I did yesterday, I’m stuck!;-). so, if you stuck with SVM, just remove or clear the whole SVM information on the disk (both mirror and submirror).
CLEAR / Remove Solaris Volume Manager Information:
———————————————————————-
1. All of the Solaris Volume Manager information is stored in three files:
/kernel/drv/md.conf
/etc/lvm/mddb.cf
/etc/lvm/md.cf
So to clear out Solaris Volume Manager, overwrite these files with the files from a system without Solaris Volume Manager or just remove the last entry configuration.
your three files configuration become like this:
bash-3.00# more /kernel/drv/md.conf
#
#pragma ident “@(#)md.conf 2.2 04/04/02 SMI”
#
# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
# The parameters nmd and md_nsets are obsolete. The values for these
# parameters no longer have any meaning.
name=”md” parent=”pseudo” nmd=128 md_nsets=4;
bash-3.00# more /etc/lvm/mddb.cf
#pragma ident “@(#)mddb.cf 2.1 00/07/07 SMI”
#
# Copyright (c) 2000 by Sun Microsystems, Inc.
# All rights reserved.
#metadevice database location file do not hand edit
#driver minor_t daddr_t checksum
bash-3.00# more /etc/lvm/md.cf
#pragma ident “@(#)md.cf 2.1 00/07/07 SMI”
#
# Copyright (c) 2000 by Sun Microsystems, Inc.
# All rights reserved.
#
# metadevice database configuration file
# do not hand edit
2. and also, there is an entry similar to “rootdev:/pseudo/md@0:0,0,blk” in the “/etc/system” file, dont forget to remove this entry. Do not just comment it out.
3. edit “/etc/vfstab” configuration, then reboot.
4. now, perform mirroring disk again;-)
From Wikipedia, Solaris Containers (including Solaris Zones) is an implementation of operating system-level virtualization technology first made available in 2005 as part of Solaris 10.
A Solaris Container is the combination of system resource controls and the boundary separation provided by zones. Zones act as completely isolated virtual servers within a single operating system instance. By consolidating multiple sets of application services onto one system and by placing each into isolated virtual server containers, system administrators can reduce cost and provide all the same protections of separate machines on a single machine.
Zones provide a new isolation primitive for the Solaris OS, which is secure, flexible, scalable and lightweight: virtualized OS services which look like different Solaris instances. Together with the existing Solaris Resource management framework, Solaris Zones forms the basis of Solaris Containers.
if you are fans of VirtualBox like me, the new version of VirtualBox; VirtualBox version 3.0.4 has been released per 4 August 2009. Lets download the VirtualBox binaries here:
http://www.virtualbox.org/wiki/Downloads
VirtualBox is an X86 virtualization software developen by Sun, distributed under two license, PUEL (Personal Use and Evaluation License) and GNU/GPL license.
Wikipedia said, VirtualBox is an x86 virtualization software package, originally created by German software company innotek, now developed by Sun Microsystems as part of its Sun xVM virtualization platform. It is installed on an existing host operating system; within this application, additional operating systems, each known as a Guest OS, can be loaded and run, each with its own virtual environment.
Supported host operating systems include Linux, Mac OS X, OS/2 Warp, Windows XP, Windows Vista, and Solaris; there is also experimental port to FreeBSD.[1] Supported guest operating systems include various versions of DragonFlyBSD, FreeBSD, Linux, OpenBSD, OS/2 Warp, Windows, Solaris, Haiku, Syllable, ReactOS and SkyOS.[2] The latest version also supports Windows 7 beta and release candidate 1.
Today, I got an error like this:
SUNW-MSG-ID: FMD-8000-2K, TYPE: Defect, VER: 1, SEVERITY: Minor EVENT-TIME: Tue Aug 4 14:52:43 WIT 2009 PLATFORM: SUNW,SPARC-Enterprise, CSN: BEF09142B8, HOSTNAME: server SOURCE: fmd-self-diagnosis, REV: 1.0 EVENT-ID: d232928b-dd11-e149-b515-82ff5df189f8 DESC: A Solaris Fault Manager component has experienced an error that required the module to be disabled. Refer to http://sun.com/msg/FMD-8000-2K for more information. AUTO-RESPONSE: The module has been disabled. Events destined for the module will be saved for manual diagnosis. IMPACT: Automated diagnosis and response for subsequent events associated with this module will not occur. REC-ACTION: Use fmdump -v -u <EVENT-ID> to locate the module. Use fmadm reset <module> to reset the module. root@server #
and this:
Aug 4 14:37:13 server ufs: NOTICE: alloc: /var: file system full
As we may know already that, tape device are in “/dev/rmt” directory. Actually tapes creates symbolic links in the “/dev/rmt” directory to the actual tape device special files under the “/devices” directory tree. tapes searches the kernel device tree to see what tape devices are attached to the system.
Each tape LUN seen by the system is represented by 24 minor nodes in the form of /dev/rmt/N, /dev/rmt/Nb, and /dev/rmt/Nbn, where N is an integer counter starting from 0. This number is picked by devfsadm during enumeration of new devices. Every new tape logical unit number (LUN) found by devfsadm gets the next available number in /dev/rmt.
Prepare the disk slice and partition for live upgrade:
disk 1 Partition:
c0d0s0 /
c0d0s1 swap
c0d0s2 backup
disk 2 partition:
c0d1s0 /copyroot
the partition on second disk (/copyroot) is same size as the root (/) partition and it must not appear in use in “/etc/vfstab”.
This example explains how to upgrade a Solaris 10 10/08 system to the Solaris 10 5/09 release. Solaris Live Upgrade has many capabilities but for a simple situation like upgrading a system to a new Solaris release, there are three commands:
• lucreate to create the copy
• luupgrade to upgrade the OS on the copy
• luactivate to choose the environment to boot
-
Recent Comments
Mohammed on Solaris 10 Remote X11,X-Server… Mitza on Download Cisco Unified Communi… Bruno on Symantec EndPoint Protection… Bruno on Symantec EndPoint Protection… mandar on How to Configure Drive on Sola… mandar on How to Configure Drive on Sola… Mal on CCNA Study Guide 640-802 Installation of Orac… on Step Install Oracle 10g R2 on … Sailaish on Symantec EndPoint Protection… Surick on “Cannot find VRTSperl to… -
My blog is worth $1,129.08.
How much is your blog worth?
Links
About Me
Just call me Aziz, An Ordinary human, live in Jakarta, work as an IT Engineer.
Contact:
saifulaziz@gmail.com
saifulaziz2004
-
Flickr Photos
More Photos Facebook Badge
SOCIAL NETWORKING
Visitors
DONATION
SEO STATS
