Restore of database too large for the volume

Silent compression for faster, smaller SQL Server backups

Moderators: eddie davis, Colin Millerchip, fionag

Restore of database too large for the volume

Postby cschwinge » Wed Jun 22, 2011 3:17 pm

Hello,

I'm trying to restore a database that is too large for the volume, and am getting an error:

Msg 3257, Level 16, State 0, Line 1
There is insufficient free space on disk volume 'I:\\' to create the database. The database requires 225443840000 additional free bytes, while only 161451290624 bytes are available.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

After reasing the forums, I tried using the following line to the hyperbac.conf file and restarting the Hyperbac control service, but I get the same error.

VirtualDiskSize=325

Using windows 2000, sql server 2000 (8.00.2039). I even upgraded Hyperbac to the latest available version, so I've had this problem in 5.0.22 and in 5.2.9

When this compressed database was created, it was not too large for the volume, so I don't know if this has ever worked.

Any ideas?

Thanks in advance
-Claus
cschwinge
 
Posts: 2
Joined: Tue Jan 26, 2010 8:05 pm

Postby eddie davis » Thu Jun 23, 2011 8:30 pm

Thank you for your post into the forum.

Are you restoring this backup file to overwrite an existing database? Or creating a new database?

The fact that you are restoring from a compressed backup file, the data held in the backup file is uncompressed as it is written to the disk to restore the database.

Basically you do not have sufficient free disk space to complete the restore process.

The VirtualDiskSize parameter which can be added to the config file will only help if you are restoring the backup file to create a virtual database using SQL Virtual Restore or compressed database using SQL Storage Compress. As the parameter is used to fool SQL Server into believing there is sufficient disk to complete the restore.

Many Thanks
Eddie
Eddie Davis
Technical Support Engineer
Red Gate Software Ltd
E-mail: support@red-gate.com
eddie davis
 
Posts: 942
Joined: Wed Jun 14, 2006 3:47 pm
Location: Red Gate Software

Postby cschwinge » Fri Jun 24, 2011 2:37 pm

I am using Storage Compress, and restoring to a new database using the command:

restore database TST_FA_H3
from disk = 'X:\\MSSQL\\SQL2KDEV1\\SQL_BAK_FILES\\TST_FA_H3_BAK.hbc'
WITH MOVE 'TST_FA_H3_Data' TO 'I:\\MSSQL\\SQL2KDEV1\\SQL_DAT_FILES\\TST_FA_H3_data.mdfx',
MOVE 'TST_FA_H3_Log' TO 'X:\\MSSQL\\SQL2KDEV1\\SQL_LOG_FILES\\TST_FA_H3_Log.ldfx'

In the Hyperbac Configuration Manager - Extensions tab I can see the the mdfx and ldfx extensions are enabled and online. Also in the Status tab I can see the VirtualDiskSize=325 change
cschwinge
 
Posts: 2
Joined: Tue Jan 26, 2010 8:05 pm


Return to SQL HyperBac 5

Who is online

Users browsing this forum: No registered users and 0 guests