Video Screencast Help

BE2012 B2D

Created: 15 May 2013 • Updated: 20 May 2013 | 1 comment
This issue has been solved. See solution.

Hello, I had questions regarding B2D.

I have a CAS and 2 MMS servers.  I have a small B2D folder on each MMS' (1.63TB) that I was using for temp Restore and one large storage Array (32TB)  that I have been using for my larger B2D jobs?  I was thinking about using one of the smaller B2D for smaller jobs that I have been spinning to tape.  If I do this, I would like to increase the concurrent write sessions.  One of the MMS would have a small B2D and the Large Array connected so I'm thinking increasing write sessions would impact performance and throughput.

Is there is recommendation on how many concurrent B2D write sessions can run at one time?  I currently have this configured to 3 for my largest B2D device.  What do I need to consider for adding more B2D write sessions before performance is diminished.   Are there any suggestions for balancing the backup jobs across more than one B2D?  I've also read some information on large files vs small files and did not know if this would impact B2D.  I have 2 jobs that run 14+ hours and push a large amount of data.  I'm trying to find ways to fine tune the backups and reduce the back up window and still meet my SOP's.

Thank you in advance for your time.

Operating Systems:

Comments 1 CommentJump to latest comment

teiva-boy's picture

Rule of thumb, 1 concurrent stream per spindle of disk in your array.  Up to a maximum of 16 streams.

Keep going higher until you see throughput or disk queue go up in to unacceptable territory...  Then back down 1-2 streams, to allow for headroom

There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) "We backup data to restore, we don't backup data just to back it up."