probably too late to post, but...
cp kernel/drv/st.conf st.old
upgrade, then swap in st.old
SUN upgrades (and their cluster patches) have a nasty habit
of overwriting this file- causing a loss of drive definitions and sometime loss of robotic control as the sg passthrough driver gets blown...
You may have run out of disk at one point causing the image file to not be written
drill down into
/usr/openv/volmgr/database/images
find the client name
drill down further
backup-server10226611525_FULL
find the image file
10226611525
if it's zero byte size, delete it
also run...
Oddly, DLT drives write in variable length mode by default!
Although defining it does add scsi reserve/release for SSO environments and the biggie- hardware compression.
Check the messages file for hardware errors when you see a status 84 write error
There's usually another error leading up to...
the -p option adds it to the pool 'netbackup' where the default name is 'NetBackup'
else try
usr/openv/volmgr/bin/vmadd -help
for the options to add volumes or volume groups
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.