Troubleshooting NetBackup reports
Select the batch file you wish to change and click Open File.
Add the following line:
Save the file.
The administrator has access to operational progress reports through administrator interfaces. Reports may be generated for Backup Status, Client Backups, Problems, All Log Entries, Media Lists, Media Contents, Images on Media, Media Logs, Media Summary, and Media Written. These reports may be generated for a specific time frame, client, or master server. Refer to the NetBackup Administrator’s Guide, Volume I for details.
Minimizing timeout failures on large database restores
A large SQL Server restore may fail with a Client Read Timeout error before any data has been read from the NetBackup media. This occurs because the SQL Server may need to pre-write the database files before the restore operation begins. The time required for this process is a function of the size of the database files and the speed at which your host machine can write to disk. For example, if your system can perform disk writes at the rate of 60 megabytes per second and you have a 2.4 terabyte database, then it will take at least 12 hours for SQL Server to prep the disk before the actual restore can begin. In reality, the delay may be even longer than what you calculate by as much as 20% to 40%.
The timeout problem can be resolved by increasing the NetBackup Client Read Timeout setting. Use the NetBackup Administration Console on the server to change the properties of each client that contains a database you may need to restore. The default for the Client Read Timeout setting is 300 seconds (5 minutes). If you have clients which contain large SQL Server databases, you may need to set this value much higher.
If you are using SQL Server 2005, you can eliminate file initialization during SQL Server restores.
See “Instant data file initialization” on page 47.