10-07-2002
Our company has created a procedure for creating a backup root disk called BROOT. All new boxes are put into production with this functionality.
It was meant for an add'l recovery disk for VG00, but it can be used to copy from one disk to another, when you might ever upgrade a Disk to a larger one.
Here is the script. We have a script that creates this script, but this can be edited and reused. This should give you something to work with.
I didn't write this, but it is very good for this type of work
root:/usr/localcw/opt/broot
# cat vgbroot.script
#!/usr/bin/ksh
exec >/usr/localcw/opt/broot/vgbroot.output 2>&1
mkdir /broot
mkdir /dev/vgbroot
mknod /dev/vgbroot/group c 64 0x030000
pvcreate -fB /dev/rdsk/c0t2d0
mkboot /dev/rdsk/c0t2d0
mkboot -a "hpux -lq" /dev/rdsk/c0t2d0
lifcp /dev/dsk/c0t2d0:AUTO -
vgcreate /dev/vgbroot /dev/dsk/c0t2d0
lvcreate -s y -C y -r n -n bstand vgbroot
lvextend -L 1 /dev/vgbroot/bstand /dev/dsk/c0t2d0
lvextend -L 300 /dev/vgbroot/bstand
lvlnboot -r /dev/vgbroot/bstand /dev/vgbroot
lvlnboot -v
umount /broot/bstand
lvcreate -s y -C y -r n -n bswap vgbroot
lvextend -L 1 /dev/vgbroot/bswap /dev/dsk/c0t2d0
lvextend -L 1000 /dev/vgbroot/bswap
lvlnboot -s /dev/vgbroot/bswap /dev/vgbroot
lvlnboot -v
grep -q "/dev/vgbroot/bswap swap swap pri=0 0 0 0" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bswap swap swap pri=0 0 0 0" >> /etc/fstab
fi
umount /broot/bswap
lvcreate -s y -C y -r n -n broot vgbroot
lvextend -L 1 /dev/vgbroot/broot /dev/dsk/c0t2d0
lvextend -L 252 /dev/vgbroot/broot
lvlnboot -r /dev/vgbroot/broot /dev/vgbroot
lvlnboot -v
umount /broot/broot
lvcreate -s y -C y -n bopt vgbroot
lvextend -L 1 /dev/vgbroot/bopt /dev/dsk/c0t2d0
lvextend -L 1200 /dev/vgbroot/bopt
mkdir /broot/bopt
newfs /dev/vgbroot/rbopt
mount /dev/vgbroot/bopt /broot/bopt
grep -q "/dev/vgbroot/bopt /broot/bopt vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bopt /broot/bopt vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/bopt
lvcreate -s y -C y -n busr vgbroot
lvextend -L 1 /dev/vgbroot/busr /dev/dsk/c0t2d0
lvextend -L 1200 /dev/vgbroot/busr
mkdir /broot/busr
newfs /dev/vgbroot/rbusr
mount /dev/vgbroot/busr /broot/busr
grep -q "/dev/vgbroot/busr /broot/busr vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/busr /broot/busr vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/busr
lvcreate -s y -C y -n bvar vgbroot
lvextend -L 1 /dev/vgbroot/bvar /dev/dsk/c0t2d0
lvextend -L 1600 /dev/vgbroot/bvar
mkdir /broot/bvar
newfs /dev/vgbroot/rbvar
mount /dev/vgbroot/bvar /broot/bvar
grep -q "/dev/vgbroot/bvar /broot/bvar vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bvar /broot/bvar vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/bvar
lvcreate -s y -C y -n bopenv vgbroot
lvextend -L 1 /dev/vgbroot/bopenv /dev/dsk/c0t2d0
lvextend -L 2000 /dev/vgbroot/bopenv
mkdir /broot/bopenv
newfs /dev/vgbroot/rbopenv
mount /dev/vgbroot/bopenv /broot/bopenv
grep -q "/dev/vgbroot/bopenv /broot/bopenv vxfs delaylog 0 2" /etc/fstab
if (( $? != 0 ))
then
print "/dev/vgbroot/bopenv /broot/bopenv vxfs delaylog 0 2" >> /etc/fstab
fi
umount /broot/bopenv
# The following sequence of coding was modified by Peter Gunawan
# on 5/19/2001
lvlnboot -b /dev/vgbroot/bstand
lvlnboot -r /dev/vgbroot/broot
lvlnboot -s /dev/vgbroot/bswap
lvlnboot -v /dev/vgbroot
vgcfgbackup vgbroot
cp /etc/fstab /etc/fstab.19042002
grep -v ^/dev/vgbroot /etc/fstab >/tmp/fstab
cp /tmp/fstab /etc/fstab
echo "-------- dd copy completed - psg"
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies
2. UNIX for Dummies Questions & Answers
I have a SunOS 5.8 server. I suspect there may be errors with one of the physical disks (based on someone reporting hearing a "clicking sound" during the night shift, however I do not hear anything this morning).
Which log would show this?
Thank you. (2 Replies)
Discussion started by: FredSmith
2 Replies
3. AIX
Hi,
I'm getting the errors below in the errpt report for a IBM Blade server. I'm guessing there's a problem with one of the disks but don't know how I can confirm this. Can anyone offer any suggestions?
Regards
Gareth (4 Replies)
Discussion started by: m223464
4 Replies
4. UNIX for Dummies Questions & Answers
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies
5. Filesystems, Disks and Memory
so we have a solrais 9 system attached to an HP SAN.
we are using sssu to do snap clones every hour.
the only problem is the we get write errors on the solrais system every time we do a snap.
from /var/adm/messages
Apr 21 14:37:48 svr001 scsi: WARNING:... (0 Replies)
Discussion started by: robsonde
0 Replies
6. Shell Programming and Scripting
I am looking for some tips or suggestions in how to do the following.
1) From a Solaris server, I run the command iostat -En and receive output that is similiar to the following which shows your disks along with the cdrom/dvdrom:
c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport... (1 Reply)
Discussion started by: sunsysadm2003
1 Replies
7. Solaris
Hi all.
I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'.
I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies
8. AIX
Hi,
The system is a Power6 8204 with an external storage 7031. OS is AIX 5.3. I replaced a failed disk hdisk28 and put it back to the volume group. Everything looks just fine. After the replacement, errpt has kept sending "Perm DISK OPERATION ERROR".
Other than the error, everything still... (1 Reply)
Discussion started by: aixlover
1 Replies
9. Ubuntu
Hi,
During start up I got the message "Your disk drives are being checked for errors". But it went so fast that I could read following messages.
Once logged I though I could find it in "dmesg" but nothing...
May someone know where I can find plese ? :) (3 Replies)
Discussion started by: xib.be
3 Replies
10. Solaris
Hi,
What are the initial checks needs to be done while observing hard errors on one of the hard disk drive.
Thanks,
Babu. (1 Reply)
Discussion started by: lbreddy
1 Replies
fd(4) Kernel Interfaces Manual fd(4)
NAME
fd - file descriptor files
DESCRIPTION
The /dev/fd file system is a pseudo-file system layered beneath the Virtual File System (VFS). The file descriptor files (fd*) are those
files that are accessible through file descriptors. The file descriptors use the naming convention /dev/fd/0, /dev/fd/1, /dev/fd/2 and so
on up to any number.
To make the /dev/fd file system known to the operating system, you must create the directory with the correct privileges, then you must
mount the file system. The following steps describe how to create the directory, mount the file system both manually and automatically,
and how to dismount the file system: Create the directory using the mkdir and chmod commands: mkdir /dev/fd; chmod 777 /dev/fd Mount the
file system manually using the mount command: mount -t fdfs /dev/fd /dev/fd Mount the file system automatically by editing either the
/etc/fstab file or the /sbin/bcheckrc file.
Add the following entry to the /etc/fstab file: /dev/fd /dev/fd fdfs rw 0 0 This entry mounts the pseudodevice /dev/fd on the
/dev/fd directory with read/write privileges. The file system type is fdfs and the zeros (0) in the remaining fields specify that
the file system is not to be backed up nor can file system checks be performed by the fsck command as this is a virtual file system.
Add the following entry to the /sbin/bcheckrc file: # # mount fdfs # echo 'Mounting /dev/fd filesystem' /sbin/mount -a -v -t fdfs
Again, the /dev/fd file system should not be mounted in this manner if an entire system is to be backed up starting from the root
directory. Dismount the file system using the umount command: umount /dev/fd For correct truncate() behavior on fd files, you must
load your program using the -lsys5 flag.
RESTRICTIONS
The /dev/fd file descriptors should not be exported.
EXAMPLES
The following example show how the open and dup functions have the same effect if file descriptor n is opened:
fd = open("/dev/fd/n", mode);
fd = dup(n);
In the above example, the open function is equal to the creat function and mode is ignored. Using the dup function, subsequent reads or
writes on the fd file descriptor files fail unless the original file descriptor enables the operation.
ERRORS
The following error condition exists: The file descriptor is not valid.
RELATED INFORMATION
Commands: chmod(1), mkdir(1), mount(8).
Functions: creat(2), dup(2), open(2). delim off
fd(4)