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.
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.