Disk-to-Disk preallocation

[Doug_Dockter]

It appears that the max size backup file that I can preallocate is 99GB. I'm getting the following error if I go over that: "An error occurred while processing a B2D command.
Drive: WriteMasterFMTable() WriteFile failed (G:\B2D000004.bkf). Error=1450".

My Full backup is about 340GB. Should I just preallocate around 50GB and then let BU Exec create additional D2D volumes as needed during the backup? What are others doing?

[Shilpa_pawar_2]

Hi,

Where does the backup to disk folder reside? Is it a local folder or a removable folder?

Are there any other errors in Application or system event logs?

For test purpose try creating a new B2D folder on a different volume.

What settings are defined under Backup to Disk Properties > Configuration tab?

Also refer:
http://support.veritas.com/docs/239539
http://support.veritas.com/docs/236295

Thanks!

[Doug_Dockter]

The B2D folder is on a SCSI disk storage unit attached to the BU Exec server. The event log error I am getting was included in my original message. My configuration settings for the B2D folder are as follows:

Maximum Size - 100GB
Maximum Number - 8192
Disk Space Reserve - 0
Device Settings = Auto Detect
Allow 1 concurrent operation

[Errol_Neal]

I have a bit over 5TB of storage. I actually ran some dummy jobs to fill that up. I do 200GB disk files. i've had that issue where preallocation would fail but, in my case, since I had so much space, it would mark that file as invalid and create another file I would then erase that file in the Device tab and it would recreate it properly then.

[shweta_rege]

Hello,


This has been observed mostly when Backup-to-Disk folder is pointing towards a drive connected remotely. Probably, due to network issues, the Backup Exec's device and media service is unable to detect the folder as soon as the network connection is regained.

Solution:
- To resolve the issue do the following:
a. Restart all the Backup Exec services.
b. Ensure that the B2D folder is configured as a mapped drive.
c. Ensure that there are no network connectivity issues.
d. Ensure that the hard disk is free of any errors perform scandisk or defragment it.




Thank You,

Shweta

[Doug_Dockter]

As I mentioned above, this drive is connected directly via SCSI to my BU Exec server.

[Doug_Dockter]

Errol, I'll have to give your dummy job suggestion a try. Thanks.

[Hywel_Mallett]

I'd do as you put in your first post - preallocate a smaller size and let it create B2D files as needed.

[Shilpa_pawar_2]

Hi,

Please update us on the issue!

Additionally refer:

http://support.veritas.com/docs/283264
http://seer.entsupport.symantec.com/docs/284014.htm

Thanks!