Showing results for 
Search instead for 
Did you mean: 

Backup Exec 2014 not creating DR file on some servers

Level 3

I have installed Backup Exec 2014 on a new server. On some servers when a full backup is succesful completed there is not any .dr file created. The green dot for SDR is lit and there is no fault in any log files. 

This is happening on random servers with different server OS. The only thing is that, remote agent for BE 2012 have been installed in must of the servers once before and have been updated to the new version

I have tried to uninstall the agent and the agent with no change to the problem.

I have re-created the backup jobs.

I have installed BACK EXEC 2014 on a different server.

Hope that the community can help


Level 5

Hello, I have not seen this. If the green dot is there and the backup is successful, a DR file is created. So let's take a look. Under Configurations and setting - > Backup Exec Settings -> Simplified Disaster Recovery verify your paths. Put in an Alternate path if one's not there.

Check the job log for .dr file creation. It should tell you that a dr file was created in the job log. Check the Windows\system32 directory. If something happened to the dr path, then it might put them there. Make sure Backup Exec has rights to the folders you want the dr file in.

If you have both a successful backup with a dr file creation and another successful backup without the dr file for the same resource, please attach it.


Hello again

The path is the right one and BE has the rights to it and the alternate path.

In the job log there is no indication of creation of any DR file or update of one. There is no file in System32 or anywhere else.

This "error" happens to 50 % of our servers. But with no indications off any fault in the backup job

Level 4

Is  there any common thread between the servers where the DR file does not get created? For instance are those servers running the same Operating System / SP ? Or same version of the Backup Exec Remote Agent?

If a specific server does get a DR file created, does it always get one created ? Or does the issue move around ?

A screen shot of your selection screen might also be helpful.

Level 5

Hello again. I did a test of my system and in the job log it states that the .dr file was updated. Can you attach a job log of a successful backup without the .dr file creation and a screen shot of the selection from that job.

The only common thread is that it is the same servers and it does not move around. After the re-installation of the of 2014 on another server it was still the same servers that have this problem. 

When I load up the SDR media I can select the server to restore, but there is no point in time or backup sets hence the missing DR files.

I have attached the logs for a succesful server and an unsuccesful server and a screenshot of selection screen of the unsuccesful server.

Level 5

Ok, I have review the files. There's good new and bad. The bad news is we are going to need some debug logs. The good news is dr has a lot of logging in the debug log.

I will need debugs for the media server and the two remote servers, FPS01B and FPS01A.

To enabled debugging

On both the Backup Exec Server & Remote agent systems:

1. Stop all Backup Exec for Windows Servers services


3. Browse to HKey_Local_Machine\Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\Logging

4. Change the value of CreateDebugLog to 1 to enable debug logging

5. Quit the registry editor

6. Start the Backup Exec for Windows Servers services

This will create the following files:

Backup Exec media server:
   Directory =  \Program Files\Symantec\Backup Exec\Logs 
   Filenames = <ServerName>-BENGINExx.Log

Backup Exec remote servers:
   Directory =  \Program Files\Symantec\Backup Exec\RAWS\Logs by default.
   Filename =  <ServerName>-BEREMOTExx.LOG

Here are the debug logs

2 Files 

Level 5

Ok, I see a problem. I'm sending this to the DR guy.


[5788] 2016-11-03T09:33:13.286 | *************************************************
[5788] 2016-11-03T09:33:13.286 | * Load DR File - C:\backup exec\Data\FPS01B.DR.TMP (1)
[5788] 2016-11-03T09:33:13.286 | *
[5788] 2016-11-03T09:33:13.286 | *
[5788] 2016-11-03T09:33:13.286 | * Load DR File - Complete (C:\backup exec\Data\FPS01B.DR.TMP)
[5788] 2016-11-03T09:33:13.286 | *************************************************


[7624] 2016-11-03T09:01:01.518 | *************************************************
[7624] 2016-11-03T09:01:01.518 | * Load DR File - C:\Program Files\Symantec\Backup Exec\RAWS\Data\FPS01A.DR.TMP (1)
[7624] 2016-11-03T09:01:01.518 | *
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x56465244, size - 4 (0x4)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x47464353, size - 532 (0x214)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x54445252, size - 342 (0x156)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x464e4953, size - 4928 (0x1340)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x4c415645, size - 18 (0x12)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x44525341, size - 37794 (0x93a2)
[7624] 2016-11-03T09:01:01.518 | CDRFile::ExtractASRStreamAtLoad()
[7624] 2016-11-03T09:01:01.518 | CDRFile::ExtractASRStreamAtLoad() - Complete
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x32565049, size - 2072 (0x818)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x5450544d, size - 8942 (0x22ee)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x5442564e, size - 320 (0x140)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x4d544441, size - 16 (0x10)
[7624] 2016-11-03T09:01:01.518 | CDRFile::Load() - type - 0x53565244, size - 13656 (0x3558)
[7624] 2016-11-03T09:01:01.580 | *
[7624] 2016-11-03T09:01:01.580 | * Load DR File - Complete (C:\Program Files\Symantec\Backup Exec\RAWS\Data\FPS01A.DR.TMP)

Level 5

Sorry for the long delay, but you are going to have to open a support case. There's too much needed to resolve over the forums. I'm sorry about that.