The recovery disks are for repairing a broken boot (stage 2 in the following scenario)
1.After pressing the power button, the PC’s firmware initiates a Power-On Self Test (POST) and loads firmware settings. This pre-boot process ends when a valid system disk is detected.
2.Firmware reads the master boot record (MBR), and then starts Bootmgr.exe. Bootmgr.exe finds and starts the Windows loader (Winload.exe) on the Windows boot partition.
3.Essential drivers required to start the Windows kernel are loaded and the kernel starts to run, loading into memory the system registry hive and additional drivers that are marked as BOOT_START.
4.The kernel passes control to the session manager process (Smss.exe) which initializes the system session, and loads and starts the devices and drivers that are not marked BOOT_START.
5.Winlogon.exe starts, the user logon screen appears, the service control manager starts services, and any Group Policy scripts are run. When the user logs in, Windows creates a session for that user.
6.Explorer.exe starts, the system creates the desktop window manager (DWM) process, which initializes the desktop and displays it.
.sys files are OS drivers which you'll see are located and loaded in steps 3 and 4.
This indicates that your problem is deeper in the OS than just getting the boot manager to work, and means that the OS has become corrupted, either by the restore process, or by whatever problem prompted you to restore in the first place. That would suggest that the backup image you are using is not a good one, or that the restore point you chose does not go back far enough to precede the cause of the problem.
What was your initial problem, and what have you tried to fix it ?