If I understand you correctly, you found that opening multiple streams
(jobs) to the filesystem was much faster than doing it as one stream.  You
want to make it simpler.  Here are some solutions:

- you can use the NEW_STREAM directive in the NetBackup policy to break
things up.  So you would put

        NEW_STREAM
        /Ora/db01
        NEW_STREAM
        /Ora/db02

        etc.  Make sure you have "allow multiple streams" turned on for that
policy

- you can also set ALL_LOCAL_DRIVES as the filelist.  This will open one
stream per filesystem.  If you want to break things up (e.g., one policy for
system files and root and one for Oracle), then you can create two policies,
both set to ALL_LOCAL_DRIVES, and create a separate exclude list for each
policy.

- You might also think about using user-directed backups.  On the client
side you would write a script to create the list of files to be backed up,
balance them by size, then put them in files as list of files and invoke
bpbackup on each list.

Good luck,

--
 Drew Fabbro [fabbro.andrew AT cnf DOT com]
 Unix Systems Group
 Desk: 503-450-3374
 Cell: 503-701-0369







-----Original Message-----
From: martin.d.roby AT verizon DOT com [mailto:martin.d.roby AT verizon DOT 
com] 
Sent: Tuesday, January 21, 2003 10:08 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Multiple Clients Per Directory



Hello Netbackup-er,

Lots of our file systems are 0+1 raids. We can handle multiple data streams
to the disks without thrashing (Especially if each job is taking the time to
compress the data).

To get multiple jobs to kick off I put ever  one of our dbf files into a
policy and it cut our backup time from 15+ hours to 5 hours. Can I get
NetBackup to do this on it's own?

martin



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu