Home » Penelusuran HowTo

How To Create Backup Policy Using Netbackup10.0.x For One month


This is only a sample on creating backup policy on  Netbackup during one month.

To create a backup policy for one month using Veritas NetBackup 10.1.x, you would follow these steps:

  1. Start the NetBackup Administration Console: Open the NetBackup Administration Console on your computer and log in using your administrator credentials.

  2. Define the Backup Policy: In the NetBackup Administration Console, navigate to the Policies section, right-click on the Policies folder and select New > Policy. Give the policy a name, such as "Monthly Backup Policy" and select a Backup Schedule that best fits your needs.

  3. Select the Clients: In the Clients section, select the clients you want to be included in the backup policy. You can select multiple clients by holding down the Control (Ctrl) key while clicking on the clients.

  4. Select the Backup Types: In the Backup Types section, select the types of backups you want to perform. For a monthly backup, a Full Backup is typically the most appropriate choice.

  5. Select the Backup Selections: In the Backup Selections section, select the files and folders you want to include in the backup. You can include specific files, folders, or entire file systems.

  6. Configure the Retention Settings: In the Retention section, configure the settings for how long you want the backup data to be stored. For a monthly backup, a retention of 30 days is typical.

  7. Save and Apply the Policy: Once you have completed the policy, click on the Save button to save the policy. Then, right-click on the policy and select Apply.

  8. Monitor the Backup Job: Monitor the backup job to ensure it runs successfully. You can view the status of the job in the Jobs section of the NetBackup Administration Console.

By following these steps, you can create a backup policy for one month using Veritas NetBackup 10.1.x. It is important to regularly test your backups and ensure that you can recover data in the event of a disaster.

How To Install UrBackup Server on Ubuntu 20.04 LTS

 In this article we will learn how to install UrBackup, an Open Source client/server backup system on Ubuntu 20.04 LTS operating system.

UrBackup is a free and oper source backup software which is widely used today. UrBackup is an easy to setup Open Source client/server backup system, that through a combination of image and file backups accomplishes both data safety and a fast restoration time. On this tutorial we will learn how to install UrBackup Server application on Ubuntu 20.04 LTS operating system.

Installing UrBackup On Ubuntu 20.04 LTS

UrBackup installation on Ubuntu Linux will be consist of several steps as mentioned below :

  • Adding UrBackup Repository
  • Updating System
  • Installing UrBackup Server Software
  • Accessing UrBackup Web

 1. Adding UrBackup Repository

In this step, we will add UrBackup repository to our Ubuntu packages system. The UrBackup will be using ppa:uroni/urbackup repository. Adding repository by using command line :

$ sudo add-apt-repository ppa:uroni/urbackup
 
Output : 
 
mpik@app01:~$ sudo add-apt-repository ppa:uroni/urbackup
[sudo] password for mpik:
 Efficient Client-Server Backup system for Linux and Windows. A client for Windows lets you backup open files and complete partition images. Backups are stored to disks in a efficient way (deduplication) on either Windows or Linux servers.
 More info: https://launchpad.net/~uroni/+archive/ubuntu/urbackup
Press [ENTER] to continue or Ctrl-c to cancel adding it.

Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]                                                
Hit:3 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease
. . .
Get:22 http://us.archive.ubuntu.com/ubuntu focal-backports/universe amd64 DEP-11 Metadata [10.4 kB]                       
Fetched 4,313 kB in 19s (227 kB/s)                                                                                        
Reading package lists... Done      
 

 2. Updating System

 By updating system repository, we will refresh our Ubuntu system to the latest package version, this task is performed by submitting command line :
 
$ sudo apt-get update
 
 Output :
 
mpik@app01:~$ sudo apt-get update
Hit:1 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease                                                         
Hit:2 http://us.archive.ubuntu.com/ubuntu focal InRelease                                                                
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease                                                         
Hit:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease                         
Hit:6 http://ppa.launchpad.net/uroni/urbackup/ubuntu focal InRelease                                
Get:7 https://dlm.mariadb.com/repo/mariadb-server/10.6/repo/ubuntu focal InRelease [6,264 B]        
Hit:8 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease                                            
Hit:3 https://downloads.mariadb.com/Tools/ubuntu focal InRelease                                               
Hit:9 https://downloads.mariadb.com/MaxScale/6.1.1/apt focal InRelease
Fetched 6,264 B in 4s (1,665 B/s)
Reading package lists... Done
 

 3. Installing UrBackup Server Software

After updating Ubuntu 20.04 system, now we will install the UrBackup server using its Official PPA repository by issuing the following commands in the terminal.
 
 $ sudo apt-get install urbackup-server
 
Output :
 
mpik@app01:~$ sudo apt-get install urbackup-server
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libevent-core-2.1-7 libevent-pthreads-2.1-7 libmecab2 libzip5 mecab-ipadic mecab-ipadic-utf8 mecab-utils
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  attr augeas-lenses btrfs-progs cpu-checker cryptsetup-bin db-util db5.3-util debootstrap dmeventd exfat-fuse
  exfat-utils extlinux f2fs-tools finalrd hfsplus ibverbs-providers icoutils ipxe-qemu ipxe-qemu-256k-compat-efi-roms
  kpartx ldmtool libafflib0v5 libaugeas0 libcacard0 libconfig9 libcrypto++6 libdate-manip-perl libdevmapper-event1.02.1
  libewf2 libf2fs-format4 libf2fs5 libfdt1 libguestfs-hfsplus libguestfs-perl libguestfs-reiserfs libguestfs-tools
  libguestfs-xfs libguestfs0 libhfsp0 libhivex0 libibverbs1 libintl-perl libintl-xs-perl libiscsi7 libldm-1.0-0
  liblvm2cmd2.03 libnetpbm10 librados2 librbd1 librdmacm1 libslirp0 libspice-server1 libstring-shellquote-perl
  libsys-virt-perl libtsk13 libusbredirparser1 libvirglrenderer1 libvirt0 libwin-hivex-perl libxml-xpath-perl libyara3
  lsscsi lvm2 lzop mdadm msr-tools netpbm osinfo-db ovmf qemu-block-extra qemu-system-common qemu-system-data
  qemu-system-gui qemu-system-x86 qemu-utils reiserfsprogs scrub seabios sharutils sleuthkit sqlite3 supermin
  thin-provisioning-tools xfsprogs zerofree
Suggested packages:
  augeas-doc duperemove arch-test squid-deb-proxy-client libterm-readline-gnu-perl | libterm-readline-perl-perl
  augeas-tools libguestfs-gfs2 libguestfs-jfs libguestfs-nilfs libguestfs-rescue libguestfs-rsync libguestfs-zfs
  gstreamer1.0-plugins-ugly default-mta | mail-transport-agent dracut-core samba vde2 sharutils-doc bsd-mailx | mailx
  autopsy mac-robber sqlite3-doc xfsdump quota
Recommended packages:
  linux-image-amd64
The following NEW packages will be installed:
  attr augeas-lenses btrfs-progs cpu-checker cryptsetup-bin db-util db5.3-util debootstrap dmeventd exfat-fuse
  exfat-utils extlinux f2fs-tools finalrd hfsplus ibverbs-providers icoutils ipxe-qemu ipxe-qemu-256k-compat-efi-roms
  kpartx ldmtool libafflib0v5 libaugeas0 libcacard0 libconfig9 libcrypto++6 libdate-manip-perl libdevmapper-event1.02.1
  libewf2 libf2fs-format4 libf2fs5 libfdt1 libguestfs-hfsplus libguestfs-perl libguestfs-reiserfs libguestfs-tools
  libguestfs-xfs libguestfs0 libhfsp0 libhivex0 libibverbs1 libintl-perl libintl-xs-perl libiscsi7 libldm-1.0-0
  liblvm2cmd2.03 libnetpbm10 librados2 librbd1 librdmacm1 libslirp0 libspice-server1 libstring-shellquote-perl
  libsys-virt-perl libtsk13 libusbredirparser1 libvirglrenderer1 libvirt0 libwin-hivex-perl libxml-xpath-perl libyara3
  lsscsi lvm2 lzop mdadm msr-tools netpbm osinfo-db ovmf qemu-block-extra qemu-system-common qemu-system-data
  qemu-system-gui qemu-system-x86 qemu-utils reiserfsprogs scrub seabios sharutils sleuthkit sqlite3 supermin
  thin-provisioning-tools urbackup-server xfsprogs zerofree
0 upgraded, 86 newly installed, 0 to remove and 406 not upgraded.
Need to get 46.5 MB of archives.
After this operation, 217 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://ppa.launchpad.net/uroni/urbackup/ubuntu focal/main amd64 urbackup-server amd64 2.4.13.0-1ubuntu1~focal [3,531 kB]
 
 During the installation, we will be asked to provide the backup location as shown below :
 
 
Setting backup location for UrBackup

 After all are set, then we will start UrBackup service to be running on the system, for this purpose we will do the following command lines.
 
$ sudo systemctl start urbackupsrv
$ sudo systemctl enable urbackupsrv
$ sudo systemctl status urbackupsrv
 
 Output :
 
mpik@app01:~$ sudo systemctl start urbackupsrv
[sudo] password for mpik:
mpik@app01:~$ sudo systemctl enable urbackupsrv
urbackupsrv.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable urbackupsrv

mpik@app01:~$ sudo systemctl status urbackupsrv
● urbackupsrv.service - LSB: Server for doing backups
     Loaded: loaded (/etc/init.d/urbackupsrv; generated)
     Active: active (running) since Mon 2021-09-13 17:58:11 PDT; 1min 25s ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 17 (limit: 9436)
     Memory: 19.6M
     CGroup: /system.slice/urbackupsrv.service
             └─1196 /usr/bin/urbackupsrv run --config /etc/default/urbackupsrv --daemon --pidfile /var/run/>

Sep 13 17:58:11 app01.otodiginet.com systemd[1]: Starting LSB: Server for doing backups...
Sep 13 17:58:11 app01.otodiginet.com systemd[1]: Started LSB: Server for doing backups.
 
 Until this step, UrBackup installation process has just done. Next step, we will configure UrBackup to make it run properly.   

4. Accessing UrBackup Web Interface

 By default UrBackup will use port 55414 for web interface. We will use web browser to access UrBackup web interface by typing url http://<ipaddress_server_or_server_hostname>:55414.
 
 

 



Conclusion

 The UrBackup installation on Ubuntu 20.04 LTS operating system has been done properly. I hope this article will be helpful.
How Do I Take Thread Dumps on Solaris 10 ?

How Do I Take Thread Dumps on Solaris 10 ?

Currently, many applications are using JVM for processing, the active process are divided into various java threads. The list of java threads that are currently active in the JVM is called as thread dump. Sometimes we are faced with a condition where the java thread is running not as it should be, then checks are needed for investigation. To check for java threads needed tools. There are several ways to take thread dumps from a JVM.

 For our case, we will use jstack with Solaris 10 environment as our case test. Here's how to take thread dump with jstack in a Solaris 10 environment.

1. List the PID of all active java processes
[joe01@testbed01]$ uname -a
SunOS utest01 5.10 Generic_150400-30 sun4v sparc SUNW,SPARC-Enterprise-T5220
[joe01@testbed01 ]$ ps -ef| grep java
stystem  3498  3469   0   Sep 26 ?         550:55 /usr/jre1.6.0_07/bin/java -Dprogram.name=run.sh -server -Xms256m -Xmx3072m -XX:
stystem  26440     1   0   Oct 05 ?          98:35 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem 24938 24919   0 20:56:18 pts/5       0:00 grep java
stystem  7233     1   0   Oct 05 ?         100:47 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem  2073     1   0   Oct 05 ?          26:10 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem  2842     1   0   Oct 05 ?          75:55 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem  1284     1   0   Oct 05 ?          85:36 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem 28953     1   0   Oct 05 ?         179:41 /app/st/jdk1.6.0_12/bin/java -Djava.security.properties=/app/st/jre1.7.0_

 2. Run the jstack to request thread dump from the JVM. The command line will be jstack -l
[joe01@testbed01]pwd
/app/rapcorp/jdk1.6.0_12/bin
[joe01@testbed01]$ ls -ltr jstack
-rwxr-xr-x   1 rapcorpadm rapcorp      47788 Apr 28  2016 jstack
[joe01@testbed01]$ ./jstack -h
Usage:
    jstack [-l]
        (to connect to running process)
    jstack -F [-m] [-l]
        (to connect to a hung process)
    jstack [-m] [-l]
        (to connect to a core file)
    jstack [-m] [-l] [server_id@]
        (to connect to a remote debug server)

Options:
    -F  to force a thread dump. Use when jstack does not respond (process is hung)
    -m  to print both java and native frames (mixed mode)
    -l  long listing. Prints additional information about locks
    -h or -help to print this help message


[joe01@testbed01]$ ./jstack -l 26440| more
2017-10-25 15:50:37
Full thread dump Java HotSpot(TM) Server VM (11.2-b01 mixed mode):

"Attach Listener" daemon prio=3 tid=0x00afb400 nid=0x718d waiting on condition [0x00000000..0x00000000]
   java.lang.Thread.State: RUNNABLE
[joe01@testbed01]$ ./jstack -F 25468
ttaching to process ID 25468, please wait...
Exception in thread "main" java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at sun.tools.jstack.JStack.runJStackTool(JStack.java:118)
        at sun.tools.jstack.JStack.main(JStack.java:84)
Caused by: java.lang.RuntimeException: Type "nmethodBucket*", referenced in VMStructs::localHotSpotVMStructs in the remote VM, was not present in the remote VMStructs::localHotSpotVMTypes table (should have been caught in the debug build of that VM). Can not continue.
        at sun.jvm.hotspot.HotSpotTypeDataBase.lookupOrFail(HotSpotTypeDataBase.java:361)
        at sun.jvm.hotspot.HotSpotTypeDataBase.readVMStructs(HotSpotTypeDataBase.java:252)
        at sun.jvm.hotspot.HotSpotTypeDataBase.(HotSpotTypeDataBase.java:87)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.setupVM(BugSpotAgent.java:562)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.go(BugSpotAgent.java:494)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.attach(BugSpotAgent.java:332)


For convenion way, we throw the result to a file.

Changing Media Density

Sometimes, for special purpose we need to change the media density. Maybe our customer request restore for data that have been backed up, unfortunately our tape drive has upgrade to higher density. Maybe here is one of the way for changing media density to higher one. Here is the case where tape is written by LTO1 tape drive on L700 and will be restored to LTO3 on ACS-SL8500 tape library :
1. Identify the tape that is required for the restoration. This can be obtained from the catalog. To ensure this can be done with bpmedialist command :
2. Eject the tapes from the TLD library (L700).
3. Perform an inventory of the TLD library to change the RobotType to "standalone".
4. Inject the tape into the ACS library.
Note: Some procedure is necessary to inject the tapes into the correct pool and setting the appropriate ownership.
5. After the tapes are injected into the ACS library, perform a robot inventory of the ACS library.
6. After the volume database is updated, the RobotType of the media will change to "ACS" and the tapes should be recognized as "hcart".
7. Run "vmchange -new_mt -m " to change the density. It should be "hcart3" for the LTO Gen-3 drive and refers to the media barcode. An eg would be "vmchange -new_mt hcart3 -m TD2222".
8. Run "vmquery -m " to check that the density have been updated to "hcart3" from "hcart".
9. One media server that holds this tape run "bpmedia -changeden -new -ev "
Note: This command will take some time to complete. Please be patient and let it complete on it's own. If terminated halfway, strange things may occur later.
10. Run "bpmedialist -m " to check that the density have been updated.
11. Run the normal restoration procedure to restore the data from the LTO Gen1 tapes using the ACS library.
12. Once, we have completed the restoration, the tape should be ejected from the ACS library to prevent it from being used for future backups. If necessary, will need to execute the commands in Step 7 and 9 to change the density back to "hcart".




How to Mount disk in HP-UX using Native Command

How to Mount disk in HP-UX using Native Command

Sometimes our users need some space for storing their new data to our HP-Ux servers. There are several way for doing this, especially if our servers is using storage controller software, such as : powerpath from EMC or HDLM from HDS.

Here, I will try to share the native HP-UX command for mounting new disk to the system. Here are the steps :

1. run ioscan command
serverdb1:/# ioscan -fnC disk
disk 175 0/0/12/1/0.10.194.0.0.3.0 sdisk CLAIMED DEVICE HITACHI OPEN-V
disk 176 1/0/14/1/0.10.16.0.0.3.0 sdisk CLAIMED DEVICE HITACHI OPEN-V
we have two link for our new disk

2. run insf -e command
disk 176 1/0/14/1/0.10.16.0.0.3.0 sdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/dsk/c20t3d0 /dev/rdsk/c20t3d0
disk 175 0/0/12/1/0.10.194.0.0.3.0 sdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/dsk/c22t3d0 /dev/rdsk/c22t3d0

3. Check the disk for ensuring it is the right new disk for preventing from wrong disks
serverdb1:/# diskinfo /dev/rdsk/c22t3d0
SCSI describe of /dev/rdsk/c22t3d0:
vendor: HITACHI
product id: OPEN-V
type: direct access
size: 167772480 Kbytes
bytes per sector: 512

serverdb1:/# pvdisplay /dev/dsk/c22t3d0
pvdisplay: Couldn't find the volume group to which
physical volume "/dev/dsk/c22t3d0" belongs.

4. create new physical
serverdb1:/# pvcreate /dev/rdsk/c22t3d0
serverdb1:/# cd /dev
serverdb1:/# mkdir vgnew
serverdb1:/dev/vgtrtda# pwd
/dev/vgnew

5. create new volume group
serverdb1:/dev/vgtrtda# mknod group c 64 0x050000
serverdb1:/dev/vgtrtda# vgcreate /dev/vgnew /dev/dsk/c22t3d0
Increased the number of physical extents per physical volume to 40960.
vgcreate: Volume group "/dev/vgnew" could not be created:
VGRA for the disk is too big for the specified parameters. Increase the
extent size or decrease max_PVs/max_LVs and try again.

(for disk above 100GB ussualy more than '4' value for -s)
serverdb1:/dev/vgtrtda# vgcreate -s 16 /dev/vgnew /dev/dsk/c22t3d0
Increased the number of physical extents per physical volume to 10240.
Volume group "/dev/vgnew" has been successfully created.
Volume Group configuration for /dev/vgnew has been saved in /etc/lvmconf/vgnew.conf

serverdb1:/dev/vgnew# vgdisplay vgnew
--- Volume groups ---
VG Name /dev/vgnew
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 10240
VGDA 2
PE Size (Mbytes) 16
Total PE 10238
Alloc PE 0
Free PE 10238
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

6. Create Logical Volume
serverdb1:/dev/vgnew# lvcreate -l 10238 /dev/vgnew
Logical volume "/dev/vgnew/lvol1" has been successfully created with
character device "/dev/vgnew/rlvol1".
Logical volume "/dev/vgnew/lvol1" has been successfully extended.
Volume Group configuration for /dev/vgnew has been saved in /etc/lvmconf/vgnew.conf
serverdb1:/dev/vgnew# newfs -F vxfs /dev/vgnew/rlvol1
version 5 layout
167739392 sectors, 167739392 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles not supported
167739392 data blocks, 167680712 free data blocks
5119 allocation units of 32768 blocks, 32768 data blocks
serverdb1:/dev/vgtrtda# cd /

7. Mount new directory
serverdb1:/# mkdir newdirforu

serverdb1:/dev/vgtrtda# lvcreate -l 10238 /dev/vgnew
Logical volume "/dev/vgnew/lvol1" has been successfully created with
Volume Group configuration for /dev/vgnew has been saved in /etc/lvmconf/vgtrtda.conf

7.1. Filesystem formating
serverdb1:/dev/vgnew# newfs -F vxfs /dev/vgnew/rlvol1
version 5 layout
167739392 sectors, 167739392 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles not supported
167739392 data blocks, 167680712 free data blocks
5119 allocation units of 32768 blocks, 32768 data blocks
serverdb1:/dev/vgnew# cd /
serverdb1:/# mkdir trtdadebug
serverdb1:/# mount /dev/vgnew/lvol1 /newdirforu
serverdb1:/# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 5242880 690736 4516584 13% /
/dev/vg00/lvol1 10485760 220432 10185224 2% /stand
/dev/vg00/lvol8 10485760 7879504 2586224 75% /var
/dev/vg00/lvol7 6291456 2714464 3549096 43% /usr
/dev/vg00/lvol6 5242880 3066944 2162112 59% /tmp
/dev/vg00/lvol5 10485760 5874848 4574904 56% /opt
/dev/vg00/lvol4 1048576 18792 1021800 2% /home
/dev/vg00/lvol9 17203200 11853334 5018074 70% /app
/dev/vgtrtda/lvol1 167739392 57581 157201705 0% /newdirforu


8. Add on /etc/fstab files
serverdb1:/# more /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand vxfs tranflush 0 1
/dev/vg00/lvol4 /home vxfs delaylog 0 2
/dev/vg00/lvol5 /opt vxfs delaylog 0 2
/dev/vg00/lvol6 /tmp vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg00/lvol9 /app vxfs delaylog 0 2
/dev/vgnew/lvol1 /newdirforu vxfs delaylog 0 2

9. Add alternate link :
serverdb1:/# vgextend vgnew /dev/dsk/c20t3d0
Volume group "vgnew" has been successfully extended.
Volume Group configuration for /dev/vgnew has been saved in /etc/lvmconf/vgnew.conf
serverdb1:/# strings /etc/lvmconf/vgnew.conf
CONFIG01
/dev/vgnew
/dev/rdsk/c22t3d0
/dev/rdsk/c20t3d0
LVMREC01
4aMQ
4aMQ
LVMREC01
4aMQ
4aMQ
4aMQ
4aMQ
VGDA0001
VGSA0001MQ

serverdb1:/# vgdisplay -v vgnew
--- Volume groups ---
VG Name /dev/vgnew
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 10240
VGDA 2
PE Size (Mbytes) 16
Total PE 10238
Alloc PE 10238
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vgnew/lvol1
LV Status available/syncd
LV Size (Mbytes) 163808
Current LE 10238
Allocated PE 10238
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c22t3d0
PV Name /dev/dsk/c20t3d0 Alternate Link
PV Status available
Total PE 10238
Free PE 0
Autoswitch On
Proactive Polling On

These steps only for remembering if sometimes i'm forget.
Back To Top