• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1396
  • Last Modified:

Symantec Backup Exec and HP D2D Storageworks 2504

Hi all,
I am about ready to pull my hair out.  We are using Backup Exec 2010 and we have 2 HP Storageworks D2D2504i devices.  One is G01 the other is G02.

We were using a virtual tape library and decided to switch to NAS.  We moved all backups to write to a temporary server.  I have clean up/deleted all the tapes and data on the HP D2D devices.  I created a Share on each of the devices.  

When we run the backups from backup exec to the NAS on the HP D2D devices, the backup stops when it writes about 7 or 8 files to each share.  It will sit there loading media/ pause/load media/pause but it never continues.  

The HP devices each have a 3 TB capacity, but less that 35 gb is used on each device.  Anybody have any idea why the backups stop after writing a certain number of files, even though there is sufficient disk space on the D2D device?

I hope this makes sense.  Any help is greatly appreciated
0
connieskala
Asked:
connieskala
  • 3
1 Solution
 
andyalderSaggar makers bottom knockerCommented:
Is the OST plug-in installed on the media server and is BE configured to use that rather than trying to use the D2D as a generic NAS?
0
 
connieskalaAuthor Commented:
Thanks for the reply.  How can i tell if the OST is installed? Recently had this passed on to me, and haven't worked with it much at all.  I'm still learning.
0
 
andyalderSaggar makers bottom knockerCommented:
Hmm, looking again it seems OST is for NetBackup only, not BE. Without using OST plug-in I think you're generic file-share situation if you're not using (an can't use) the plugin.

"The StoreOnce Backup system should not be used as a generic file-share device and will not perform optimally if used as such as it has been designed and optimized for performing backup and hence includes data deduplication and support for low-bandwidth replication."

http://h18000.www1.hp.com/products/quickspecs/13218_div/13218_div.html suggests to me that it should only be used as a NAS backup target if the plugin is used, but I'm not an expert on that side either, just use them as VTLs as they were initially designed for.
0
 
andyalderSaggar makers bottom knockerCommented:
Think I've got it. http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02747486/c02747486.pdf?jumpid=reg_R1002_USEN says the following:

6. Configure the maximum size that each Backup-To-Disk file may reach before spanning to a new file.
The default size is 4GB; however this should be set to a larger size in order to improve
performance. It is suggested that this maximum file size is set to at least the size of the full backup with enough headroom for future data growth. (If in doubt about the amount of growth expected, setting this to the maximum value of 4TB (4096GB) will have no detrimental effect.) This means a single file can hold the entire backup and prevents the houskeeping process, which starts whenever a file is closed, from interfering with the remainder of the backup job.

So if you leave BE with its default B2D file size as soon as a second B2D file is created the de-dupe process kicks in on the first and kills performance. Settings are completely different than when used with a normal NAS edvice.
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now