cancel
Showing results for 
Search instead for 
Did you mean: 

Best practices for using Backup-to-Folders (BE 10.1)?

Wesley_Marlor
Level 2
I've found several scattered notes about performance when using backup-to-folders but is there a 'best practices' guideline published somewhere?
5 REPLIES 5

priya_khire
Level 6
Hello,

There are no such known issues when using backup to disk folders.You can check the following technote about an issue with backup to disk folders.

http://support.veritas.com/docs/236295

The backups on b2d's are in fact faster. You can find additional information in the backup exec admin guide at the following link. Check the section on backup to disk folders:

http://support.veritas.com/docs/279401

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Regards.

Wesley_Marlor
Level 2
Not quite sure what the reply was about. I've read the admin guide and I'm already using B2D successfully. I'm wanting to tune performance for B2D. Perhaps some specifics would help:

Running BE 10.1 on SAN attached DL360 G4. Backing up 20+ servers (SQL, Exchange, UNIX, Windows file servers). Network is gigabit over copper.

Current config:

(4) Backup to Folder selections/folders:

Active Directory and Exchange Group
SQL Server Group
Standard Group (file servers)
UNIX Group

Running full backup on weekends and incrementals during the week

What performance gotchas should I look for? Better performance if I increase the number of jobs (1 per server?) and use concurrent connections? Increase/decrease number of folders? Defrag SAN and targets?

Shilpa_pawar_2
Level 6
Hi,

There are no specific best practices/advantages for backing up to disk it is the same as backing up to a tape.

The advantages of backing up to disk are:-

Backups and restores are faster than from a tape.

No specific hardware changes are required for backup and restores.

Additionally refer this:
- Defrag the Server Partitions
- Monitor the network for physical problems (Use management utilities for
managed network equipment, Network monitor, Protocol analyzer, Event
Viewer, etc.)
- Do not use AOFO for database backups like Exchange and SQL.

Additionally refer these technotes:
http://support.veritas.com/docs/237444
http://support.veritas.com/docs/268141


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

Wesley_Marlor
Level 2
I have to disagree here a little bit. B2D is not the same as tape. Backup to tape runs sequentially and I/O is bottlenecked at the tape drive. B2D allows concurrent connections to each device/folder (16 max) and I/O is presumably bottlenecked by the network.

I want my Full backup jobs to overwrite media and my incrementals to append to that same media so currently I'm running (4) jobs against (4) folders.

Is it reasonable to allow (15) servers (ea running its own job) to backup at the same time to one folder? How about (15) servers backing up to (15) different folders? Should I run a post-command to defrag each drive after backup? Any additional suggestions are greatly appreciated.

Deepali_Badave
Level 6
Hello,

In this case an issue may occur if the Opp and Ap are not set properly and if you are using one b2d folder.

You can also refer the following technote:

http://support.veritas.com/docs/248751

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.