04-21-2014 02:17 PM
I had restore of sql db worth 1.5TB.
I am restoring it to other drive (than original location). I started restore.
Checked destination folder..it alredy occupied that space (around 1.5TB)...what is this called ?..something indexing..can u pls explain...
Restore goes to "begin reading" and its still there without showing any kilobytes.
Solved! Go to Solution.
04-21-2014 04:26 PM
NetBackup just works as VDI provider, and does not handle db files directly. This is matter of SQL Server. I think SQL Server first acquires space for DB then fills logical data in it.
04-21-2014 04:26 PM
NetBackup just works as VDI provider, and does not handle db files directly. This is matter of SQL Server. I think SQL Server first acquires space for DB then fills logical data in it.
04-21-2014 11:50 PM
Totally agree with Yasuhisa.
SQL pre-allocatates space, then 'initialize' the database before any data is actually read from NBU.
This is the reason why long-long-long Client Read timeout may be needed.
Please read up in NetBackup for Microsoft SQL Server Administrator's Guide :
About minimizing timeout failures on large SQL Server database restores
04-24-2014 05:11 PM
trying now...
04-25-2014 02:20 AM
Hopefully you have also seen this section in NBU for SQL guide?
About instant data file initialization
When you restore a database, filegroup, or database file, SQL Server zeroes the
file space before it begins the restore operation. This action can slow the total
recovery time by as much as a factor of 2. To eliminate file initialization, run the
MSSQLSERVER service under a Windows account that has been assigned the
SE_MANAGE_VOLUME_NAME. For more information about eliminating the file
initialization, see the SQL Server and the Windows documentation.