BIOS is not ACPI compatible
Hello all, I've got a problem with the backup exec system recovery disc 2010. When I try to boot with the CD (on USB CD Drive) or USB Key, I have this message : Status: 0xc0000225 Info : Windows failed to load beacause the firmware (BIOS) is not ACPI compatible. A kb on symantec website tells to change the option in the BIOS but I don't have any option about ACPI. http://www.symantec.com/business/support/index?page=content&id=TECH57513 I found that the CD BESR is a Windows PE 2.5 (Vista). But the hardware which I try to restore isn't compatible with vista. Is there any solution for this problem like a Windows PE XP ? Thanks.How often do you create a new recovery point set (base)?
When defining a new backup job, the default is "Start a new recovery point set the first time the backup is run in a new month". On my servers (Exchange, files, Sharepoint, and 2 DCs) I have chagned this default to "Start a new recovery point set the first time the backup is run in a new week". Which is better in your opinion? What are the pros and cons of each configuration?
Mac Disk Recovery : Recover Deleted Boot Partition
Mac OS X hard drive is divided into various partitions, called volume, for effective management of your precious data stored on it. Every Mac computer has a boot volume, which contains critical system files that are required for your Mac OS X operating system-based computer to boot up. These files are pretty important for booting up your system. In case the boot partition gets damaged or deleted, your system become totally unbootable and unusable. It leads to severe data loss and require Mac drive recovery solutions to fix the problem, if there is no backup in place. The boot volume of your Mac OS X operating system contains the following files: Mac OS X operating system. MBR (Master Boot Record). BootX, Mac OS X boot loader. Operating system kernel. Binary files that are required for multiple kernel extensions. Mach/BSD data structures. Input/Output Kit. Init, Mach bootstrap (service naming) daemon. The boot volume of your Mac OS X hard drive must be a primary volume and set as active. This need can be completed on any hard drive on a computer that your system BIOS (Basic Input/Output System) searches when Mac OS X operating system starts. There are some situations where boot volume of your Mac computer may get damaged and your system can not boot up. This behavior cause critical data loss and put you in need of disk recovery Mac solutions. Boot volume may corrupt due to any of the following reasons: Improper system shutdown due to power outage, system crash, and user mistakes. Accidental deletion of some critical boot files by the user. Virus infection. Viruses are malicious programs that may enter your system through Internet, Email, or removable devices. Operating system malfunction. Missing or corrupt data structures, like file system, MBR, boot loader, and operating system kernel. If you come across any of the above mentioned situations, you need to format your hard drive, reinstall Mac OS X operating system, and then restore data from backup. But, you may face critical situations if backup is not available. In such situations, Mac disk recovery software come for your help to extract inaccessible data. The drive recovery Mac tools are particularly designed to scan entire drive and extract all inaccessible data from it.
Win32/Win64 API DeviceIoControl failed.
My school is using Backup Exec System Recovery 2010 at Windows Server 2008, it can't any backup from last week. I tried reboot the Windows Server, but it still doesn't work! This moring is show up an error message: Win32/Win64 API DeviceIoControl (IOCTL_VSNAP_MAKE_READONLY) failed. I don't know how to solve it, please anyone has any solution to solve it. Thanks, DanmakModule load completed but symbols could not be loaded for symsnap.sys
A server running Windows Server 2008 and BESR 2010 crashes. I am attempting to perform a crash dump analysis but I get an error saying that: "Module load completed but symbols could not be loaded for symsnap.sys". I am not sure that the BSOD is related to symsnap.sys, but I need the symbols for Windows dump analysis in order to complete the analysis. Where an I locate the requested symbols? Regards marius
windows failed to start
I used backup exec system recovery to convert virtual to physical , in the virtual server used BESR 2010 install agent and run backup all system and used SRD (symantec recovery disk) in the physical server and then after recovery the physical server is reboot after that the physical server cannot start up ,have the error "Windows failed to Start ......" Please help me !! damrongpol s.
