I don’t know of any way to do what
you want to do with Netbackup, and you have more limitations in NBU3.4 compared
to the current version. Then again, you could do a search on Symantec’s
support site: http://www.symantec.com/business/support/index.jsp
I recommend creating a striped volume
using a volume management tool (Symantec Volume Manager or Solaris Disk Suite) to
group all your 34GB drives together into one large volume/storage unit. If
you want protection for this storage unit against a disk failure then go with
RAID1+0 or RAID5 (although RAID5 could slow down your backups due to parity
calculations). You could also create smaller stripe sets/storage units if
needed; it really depends upon your needs.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Andrey Halezov
Sent: Monday, March 24, 2008 16:43
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Disk and
Media Manager Storage Units and error 84(media write error) - beginners
question (NetBackup 3.4 onSolaris 8)
I have setup several 34G disks mounted as /backupdisk_1, /backupdisk_2, /backupdisk_3 and
etc... Each mount point becomes a separate Disk Storage Unit. I also have a
Media Manager Storage Unit - DLT tape library with 20 tapes.
All my backup classes are setup with property "Storage_Unit"
set to "any available".
To continue backup on the next Storage Unit (Disk or Media
Manager, whichever has space available) after one of the Storage
Units fills up.
The backup doesn't switch to the next Storage Unit.
I get error 84 (media write error) when the hard drive mounted under
/backupdisk_n fills up. The backup keeps trying to use the same Storage Unit
each time getting error 84 (while there is space available on the other Disk
Storage Units and Media Manager Storage Unit)
Looks like NetBackup chooses Storage Unit for the job and doesn't
change to different one after the chosen Storage Unit fills up.
Is there a way to fix my setup?
