cancel
Showing results for 
Search instead for 
Did you mean: 

SDR scratchspace

We have a number of SDR deployments out in the field and have successfully restored to disimilar hardware without issue, but, we have noticed that once we have a history of backups, the sdr file can grow to 50MB +. Once this happens, we are unable to load the.DR file as it is bigger than the space available on the RAM Disk which defaults to 32MB. We have used DISM to open the boot image, change the scratch space to 256MB and commited the changes. Now when we try to boot we get a 0xc0000225 "An error occured while attempting to read the boot configuration data" error. Does anyone know if it is possible to either create an image with larger scratch space that will boot, or, limit backup exec to only keep say the last 5 backup sets information in the .dr file in order to keep the file size down.

1 Solution

Accepted Solutions
Accepted Solution!

It's OK, I have solved it.

It's OK, I have solved it. For anyone else with the same issue, steps are below. You can substitute the 512 with 256 if you don't have much RAM in your server/PC.

 

1. Create your SDR iso in the usual way.

2. Open the iso image file and copy the contents to a folder on your hard drive such as C:\source

3. Create another folder such as C:\Mount

4. Open an administrator command prompt and type;

dism /mount-wim /wimfile:c:\source\sources\boot.wim /index:1 /mountdir:c:\mount

5. Once the image mounts type;

dism /image:c:\mount /set-scratchspace:512

6. Check that the scratchspace has taken successfully with;

dism /image:c:\mount /get-scratchspace

7. Un-mount the image and commit the new settings with;

dism /unmount-wim /mountdir:C:\mount /commit

8. Create an iso image of the new files that now exist in C:\source and make it bootable by importing the boot files from the original SDR iso you created in step 1. I used WinISO but any iso creation software should do the trick.

Hope this helps someone else.

 

 

View solution in original post

6 Replies

From BE 2012 onwards, if the

From BE 2012 onwards, if the media server still exists and you are performing remote SDR to restore a separate server, then the catalogs on the media server provide the SDR functionality, the .DR files are used when the media server is not availble and allow the direct mounting of storage device to restore from locally.

With regards space for the DR file you can put the DR files on a USB disk or even access them over a network (CIFS) share, they do not have to be copied into the RAM disk

Just tried with the .DR file

Just tried with the .DR file on a USB disk, error attached, it still tries to load the /DR file into the RAM disk. It's the same story from locally attached storage or a network drive.

Please see below a log file

Please see below a log file gathered from the same.

 

============================
Starting New Logging Session
============================
[1432] [01/12/2015 13:57:10]: Info: Disaster Recovery Wizard's Build Number: 14.0.1798.1364
[1432] [01/12/2015 13:57:10]: Info: A 64-bit SDR Disk (AMD64) is used to boot this SDR session.
[1432] [01/12/2015 13:57:10]: Info: Resource dll used: X:\windows\System32\Bkupexec\bedrwiz_EN.dll
[1432] [01/12/2015 13:57:10]: IsIDRInProgressPriv: 0x1
[1432] [01/12/2015 13:57:10]: CBedrwizPropSheets::DoPreProcessing() - Info:  SCSI Controller(s) are present
[1432] [01/12/2015 13:57:10]: CBedrwizPropSheets::ProcessKnownNetBusEnumList() - Cannot open file <X:\windows\TEMP\\BEDRWIZ.INI>
[1432] [01/12/2015 13:57:10]: SetSSLCertificatesPath() - Info: Successfully set the registry key 'Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Misc\Data Path' to: X:\windows\system32\BkupExec\Raws\Data. Used to store SSL Certificates
[1432] [01/12/2015 13:57:10]: SetSSLCertificatesPath() - Info: Successfully set the registry key 'Software\Symantec\Backup Exec For Windows\Remote Agent for Windows Servers\Install\Path' to: X:\windows\system32\BkupExec\Raws. Used to store SSL Certificates
[1432] [01/12/2015 13:57:14]: Recovery Method = Local Recovery (1)
[1432] [01/12/2015 13:57:14]: GetLocalDiskStorageDevices() - Enter
[1432] [01/12/2015 13:57:14]:  Info: Found the Storage control XML file: D:\BEControl\BESCF.XML
[1432] [01/12/2015 13:57:14]:  Info: version of the D:\BEControl\BESCF.XML file: 1.02
[1432] [01/12/2015 13:57:14]: GetLocalDiskStorageDevices() - Exit
[1432] [01/12/2015 13:57:31]: CDRFile::RemoveDriverStreamAndSaveTo() - Cannot write to the output file: X:\windows\TEMP\SBS.domain.CO.UK.DR. Error code: 112
[1432] [01/12/2015 13:57:31]: Failed to copy file <G:\SBS.domain.co.uk.DR> to <X:\windows\TEMP\SBS.domain.CO.UK.DR>. Error Code [112]
[1432] [01/12/2015 14:12:31]: CDRFile::RemoveDriverStreamAndSaveTo() - Cannot write to the output file: X:\windows\TEMP\SBS.domain.CO.UK.DR. Error code: 112
[1432] [01/12/2015 14:12:31]: Failed to copy file <G:\SBS.domain.co.uk.DR> to <X:\windows\TEMP\SBS.domain.CO.UK.DR>. Error Code [112]
[1432] [01/12/2015 14:12:37]: CDRFile::RemoveDriverStreamAndSaveTo() - Cannot write to the output file: X:\windows\TEMP\RDS.domain.CO.UK.DR. Error code: 112
[1432] [01/12/2015 14:12:37]: CDRFile::RemoveDriverStreamAndSaveTo() - Cannot seek to the position before the DRIVERS stream in the input file.: D:\RDS.domain.co.uk.DR. Error code: 112
[1432] [01/12/2015 14:12:37]: Failed to copy file <D:\RDS.domain.co.uk.DR> to <X:\windows\TEMP\RDS.domain.CO.UK.DR>. Error Code [112]
[1432] [01/12/2015 14:12:59]: Recovery Method = Local Recovery (1)
[1432] [01/12/2015 14:12:59]: GetLocalDiskStorageDevices() - Enter
[1432] [01/12/2015 14:12:59]:  Info: Found the Storage control XML file: D:\BEControl\BESCF.XML
[1432] [01/12/2015 14:12:59]:  Info: version of the D:\BEControl\BESCF.XML file: 1.02
[1432] [01/12/2015 14:12:59]: GetLocalDiskStorageDevices() - Exit

============================
Starting New Logging Session
============================
[0940] [01/12/2015 14:13:03]: Info: Disaster Recovery Wizard's Build Number: 14.0.1798.1364
[0940] [01/12/2015 14:13:03]: Info: A 64-bit SDR Disk (AMD64) is used to boot this SDR session.

As the issue occurs even if

 

 

As the issue occurs even if you try to load the DR files from USB I would suggest you log a formal support case for us to look into this further.

I have seen this occuring on

I have seen this occuring on a case. Approx 32MB is the size allocated (and afaik, this cannot be changed) and this is usually sufficient to load the .DR file

Which .DR file is bigger ? Is it the one on the BE media server or the one which exists on the Disk Storage ?

If the one on the media server is bigger, rename the existing .DR file and paste over the smaller size .DR file from the Disk Storage and retry the SDR.

Accepted Solution!

It's OK, I have solved it.

It's OK, I have solved it. For anyone else with the same issue, steps are below. You can substitute the 512 with 256 if you don't have much RAM in your server/PC.

 

1. Create your SDR iso in the usual way.

2. Open the iso image file and copy the contents to a folder on your hard drive such as C:\source

3. Create another folder such as C:\Mount

4. Open an administrator command prompt and type;

dism /mount-wim /wimfile:c:\source\sources\boot.wim /index:1 /mountdir:c:\mount

5. Once the image mounts type;

dism /image:c:\mount /set-scratchspace:512

6. Check that the scratchspace has taken successfully with;

dism /image:c:\mount /get-scratchspace

7. Un-mount the image and commit the new settings with;

dism /unmount-wim /mountdir:C:\mount /commit

8. Create an iso image of the new files that now exist in C:\source and make it bootable by importing the boot files from the original SDR iso you created in step 1. I used WinISO but any iso creation software should do the trick.

Hope this helps someone else.

 

 

View solution in original post