What are the challenges you face when working across database platforms? Take the survey
Options

SQL Backup and HyperBac Config

lhallacylhallacy Posts: 7
edited May 6, 2011 1:39AM in SQL Backup Previous Versions
I recently ran into an issue where a restore presented the following message:

5/5/2011 8:41:02 AM: SQL error 3257: SQL error 3257: There is insufficient free space on disk volume 'F:\' to create the database. The database requires 160429965312 additional free bytes, while only 100931731456 bytes are available.

the F: drive had 230GB free and it puzzled me for a few hours. We also have Virtual Restore installed on the server and the Hyperbac Config file had a VirtualDisk=94 entry which corresponds exactly to the 100931732456. I changed it to 200 and all works well. Is SQLBackup supposed to use this Config file for simple (non-virtual) restores?

Comments

  • Options
    peteypetey Posts: 2,358 New member
    SQL Backup doesn't use any of Hyperbac product settings. Since SQL Server is really the application that's restoring the database, and SQL Backup only provides it the backup data, it's more likely that SQL Virtual Restore is responding to SQL Server's queries re. space availability.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.