SixtyFive
16 years agoLevel 2
$4idr files not being created
I am using Backup Exec version 10d with Service Pack 4.
I am encountering a problem when I try to backup my SQL Server Standard 2005 64 bit installation, in that it does not create the 4 $4idr files that are needed to recover the Master and Model database. Backup Exec and SQL Server are installed on separate servers, so the Windows Remote agent is being used. The Backup Exec Server is installed with Windows Server Standard 2003 with SP2 and the SQL Server is using Windows Server Enterprise 2003 x64 with SP2.
As the SQL Server is 64bit, I have installed the Windows agent via mapping a drive to the Program Files\VERITAS\Backup Exec\NT\Agents\RANT64EX folder and running the setup.exe
After investigation, I have tried the following:
1. Checked the Data folder on mssql is selected to be backed up
2. Backup Exec was previously on SP3, so I upgraded to SP4 and then re-installed the 64 bit windows agent on the SQL Server
3. Given the Backup Exec logon account full access to the following registry keys on the SQL Server
hkey_local_machine\software\microsoft\microsoft sql server
hkey_local_machine\software\microsoft\mssqlserver
4. Given the Backup Exec logon account full control to the folder c:\program files\microsoft sql server\mssql.1\mssql\data on the SQL Server
5. Made the Backup Exec logon account a System Admin in SQL on the SQL Server
6. Changed the logon service of SQLAgent$bkupexec from Local Service to the Backup Exec logon account on the Backup server
After all this, I have manually ran a backup of the master, model and msdb databases and the c:\program files\microsoft sql server\mssql.1\mssql\data on the SQL Server This still did not produce the required $4idr files
Could someone help me with this issue?
As a side note the Backup Server already backups a SQL Server and produces the $4idr files, but this is 32 bit
I am encountering a problem when I try to backup my SQL Server Standard 2005 64 bit installation, in that it does not create the 4 $4idr files that are needed to recover the Master and Model database. Backup Exec and SQL Server are installed on separate servers, so the Windows Remote agent is being used. The Backup Exec Server is installed with Windows Server Standard 2003 with SP2 and the SQL Server is using Windows Server Enterprise 2003 x64 with SP2.
As the SQL Server is 64bit, I have installed the Windows agent via mapping a drive to the Program Files\VERITAS\Backup Exec\NT\Agents\RANT64EX folder and running the setup.exe
After investigation, I have tried the following:
1. Checked the Data folder on mssql is selected to be backed up
2. Backup Exec was previously on SP3, so I upgraded to SP4 and then re-installed the 64 bit windows agent on the SQL Server
3. Given the Backup Exec logon account full access to the following registry keys on the SQL Server
hkey_local_machine\software\microsoft\microsoft sql server
hkey_local_machine\software\microsoft\mssqlserver
4. Given the Backup Exec logon account full control to the folder c:\program files\microsoft sql server\mssql.1\mssql\data on the SQL Server
5. Made the Backup Exec logon account a System Admin in SQL on the SQL Server
6. Changed the logon service of SQLAgent$bkupexec from Local Service to the Backup Exec logon account on the Backup server
After all this, I have manually ran a backup of the master, model and msdb databases and the c:\program files\microsoft sql server\mssql.1\mssql\data on the SQL Server This still did not produce the required $4idr files
Could someone help me with this issue?
As a side note the Backup Server already backups a SQL Server and produces the $4idr files, but this is 32 bit