License Error When PXE Booting to B&R 11
I am using B&R Advanced Workstation 11 (11.0.17437) and attempted to boot to it via a Fedora Linux PXE server. I have successfully got it to boot by extracting the needed files from the Rescue Media CD I created from a licensed machine. I get a "There are no Licenses for backing up some of the selected data types..." error. I recall a similar issue with B&R 10 that someone from the support staff helped me with by sending me a custom ramdisk file. Is there a similar fix for version 11? I have 24 licenses on file.
A screen shot of the error is attached.
There is only a description for Acronis Snap Deploy in http://kb.acronis.com/content/2215
But i think it should work, if you temporarily enable the Acronis PXE server, upload the bootable components to it for including the license and then take the files from:
Windows 2000/2003, Windows XP: \Documents and Settings\All Users\Application Data\Acronis\PXEServer\Bootmenu
Windows Vista, Windows 7, Windows Server 2008: \ProgramData\Acronis\PXEServer\Bootmenu
Basically, Acronis Linux-Rescue looks like three things:
The Bootloader (that reminds me of grub4dos)
Linux Kernel
Acronis Initrd (the .dat file).
Unfortunately the licensing is buried somewhere and gets lost when you leave the bootloader (which happens if you copy off the kernel and initrd and try to use it with pxelinux for example).
The solution is buried somewhere in the forum, but it's easy: Just use the complete ISO and boot it via memdisk. Put the ISO on your TFTP (or WEB if you use gpxe) and try these lines:
MENU BEGIN ^Acronis
label acronisbr11
MENU LABEL Acronis Backup & Recovery 11
kernel memdisk
append initrd=http://boot.xxx.xx/acronis/br11_17318.iso iso raw
Basically, Acronis Linux-Rescue looks like three things:
The Bootloader (that reminds me of grub4dos)
Linux Kernel
Acronis Initrd (the .dat file).Unfortunately the licensing is buried somewhere and gets lost when you leave the bootloader (which happens if you copy off the kernel and initrd and try to use it with pxelinux for example).
The solution is buried somewhere in the forum, but it's easy: Just use the complete ISO and boot it via memdisk. Put the ISO on your TFTP (or WEB if you use gpxe) and try these lines:
MENU BEGIN ^Acronis
label acronisbr11
MENU LABEL Acronis Backup & Recovery 11
kernel memdisk
append initrd=http://boot.xxx.xx/acronis/br11_17318.iso iso raw
Thank you! I will give this a shot!
I think I got this fixed so far with the help of the suggested feed back. Thanks for the help. I wanted to expand on my solution for others that may have the same issue.
Basically, Acronis Linux-Rescue looks like three things:
The Bootloader (that reminds me of grub4dos)
Linux Kernel
Acronis Initrd (the .dat file).Unfortunately the licensing is buried somewhere and gets lost when you leave the bootloader (which happens if you copy off the kernel and initrd and try to use it with pxelinux for example).
The solution is buried somewhere in the forum, but it's easy: Just use the complete ISO and boot it via memdisk. Put the ISO on your TFTP (or WEB if you use gpxe) and try these lines:
MENU BEGIN ^Acronis
label acronisbr11
MENU LABEL Acronis Backup & Recovery 11
kernel memdisk
append initrd=http://boot.xxx.xx/acronis/br11_17318.iso iso raw
This solution did indeed work, but was rather slow since the 300+ MB ISO file had to load over tftp.
There is only a description for Acronis Snap Deploy in http://kb.acronis.com/content/2215
But i think it should work, if you temporarily enable the Acronis PXE server, upload the bootable components to it for including the license and then take the files from:
Windows 2000/2003, Windows XP: \Documents and Settings\All Users\Application Data\Acronis\PXEServer\Bootmenu
Windows Vista, Windows 7, Windows Server 2008: \ProgramData\Acronis\PXEServer\Bootmenu
This solution worked, but there is one item of note: The kernel and ramdisk files will exist in the location as stated, but are renamed to what appears to be random character filenames (eg: F05650FA2, F399E0CCA, etc). The trick is finding the file that is about 1.5 MB for the kernel file and the file that is about 104 MB for the ramdisk file. The same boot parameters can be used as in B&R 10, for example:
append initrd=ramdisk.dat /s mbrcrcs=on vga=791 load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=40000 quiet
So far so good with this solution. I will post any further feedback as I play with it more. Thanks Stefan and Heiko!