We have not found a way to get around the 84 errors caused by a dsu filling
up. NB isn't smart enough to try a different dsu. However, we have been
able to run parallel jobs to different dsu's. We have 3 media servers, each
with one dsu. We set job limits per dsu of 6. We then created 3 storage
unit groups. Each storage unit group has all 3 dsu's, however, each group
has a different priority for each dsu. Then each policy has a specific
storage unit group it uses. The policy A will always try to write to STU
group 1 first. Policy B will always try to write to STU group 2 first ,
etc. If one of those dsu's has the maximum number of jobs running, the job
runs on the next available dsu in the STU group. This ensures that the
maximum number of jobs run, but the load is spread out across dsu's. That
is provided you have balanced the policies so that roughly that each dest
STU is used equally.
Ebon Nash
Storage Administrator
Compuware Corporation
313-227-5109
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Weber,
Philip
Sent: Wednesday, January 19, 2005 10:16 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Disk Staging & Storage Unit Groups
NBU5.1
Master : Sun v880 Solaris 9.
3*Media : Sun v880 Solaris 9.
EMC Clariion Cx300.
Can disk storage units / disk staging storage units be configured to work
usefully in a storage unit group?
I have 3 media servers each with a disk staging area. I would like for
backups to go to one, then if full, go to a different one. The way things
stand at the moment, if the disk staging area fills up on the first server,
backups continue to go to it and all fail with 84. The equivalent would
work with tape drives.
Ideally, thinking about it, I'd like backups to go to all three staging
areas in parallel, but I can't think how to achieve this.
Disks / Staging areas / SSO is new ground for me so if the answer's "RTFM"
then I'll go and do so :-)
thanks, Phil
Phil Weber
Egg UNIX Technologist
Phone: 01384 26 4136
Mobile:
-----------------------------------------
Egg is a trading name of the Egg group of companies which includes: Egg plc
(reg no 2448340), Egg Financial Products ltd (reg no 3319027), Egg
International ltd (reg no 4059266), Egg Financial Intermediation ltd (reg
no 382828), Egg Investments ltd (reg no 3403963) and Egg Banking plc (reg
no 2999842. Egg Investments Ltd, Egg Banking plc and Egg Financial
Intermediation Ltd are authorised and regulated by the Financial Services
Authority (FSA) and are entered in the FSA register under numbers 190518,
205621 and 309551 respectively. These members of the Egg group are
registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA. This e-mail is confidential and for
use by the addressee only. If you are not the intended recipient of this
e-mail and have received it in error, please return the message to the
sender by replying to it and then delete it from your mailbox. Internet
e-mails are not necessarily secure. The Egg group of companies do not
accept responsibility for changes made to this message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by the Egg group of companies in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
This communication does not create or modify any contract.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
|
