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.System Recovery 2011(Recovery Disk for 64bit system).
Hi, We are using the following:- 1. SRS 2011. 2. SRS Recovery Disk 2011. 3. Windows 2008 R2 (64bit). Now, We have successfully backed up the disk image to a disk. We were testing rge restore of the Os in to different System. The recovery disk was successfully booting but after completing the inatial screen windows gives an error : "can not find windows files" The files is not there or curropted. The error is some waht this. I have recovered the OS using SRS 2010 lots of time but thios is not working. I have found some KB articles below , where it mentioned that the Recovery Disk 2010 is developed PE 2.1 which does not support 64 bit system. http://www.symantec.com/business/support/index?page=content&id=TECH177792 Thanks.
Leveraging SSR to automate virtualization of a test environment?
We are running a mix of 400 physical & virutal servers in my production environment. SSR2011 Vmware4.1 A need has recently been identified to allow certain department to test production servers (physical OR virtual). my problem? Create a process that would automate the creation of production servers to a test environment. Can I leverage SSR to do this? My toughts: I stand up a VMware test enviroment, use existing jobs that backup production servers to v2i using SSR, create/automate a conversion job that converts SSR v2i backups to vmdk on the test enviroment EVA Attach vmdk to the vmware host, fire up the VM Test When test is over, Nuke the VM (not sure about this one) repeat every month as needed. (idealy, I only repeat turning on the VM as the jobs are set to run automatically) Will this work? Am I doing this the hard way? Can anyone recommend a simpler way to do this? Are there symantec products I can purchase that would help me accomplish this more efficiently? Or am I not using SSR for what it was intended to be used as? Other questions I have: Based on my understanding of SSR, I can't go directly to vmdk from the server agent (makes sense as SSR is a backup tool and not a conversion tool). I need to create the job that backs up to v2i, then run a job to convert to vmdk. Is this correct? Can the two jobs be automated so that the vmdk is always updated? If I take 1 full and 4 incremental jobs during the week, does the v2i to vmdk conversion update ONLY the changes since the last conversion? Or will it start a FULL conversion each day? I guess thats it for now, Let me know if you'd like me to clarify anything.
Symsnap.sys BSOD
Hi i have windows 2k8 R2 server this server was unexpectedley restarted. Below is the dump what could be the issue . Also now i am going to install Patch 9.0.4 BESR on the system. I think it could solve problem in future what u think? ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000168d4a7, address which referenced memory Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018c00e0 GetUlongFromAddress: unable to read from fffff800018c0198 0000000000000000 Nonpaged pool CURRENT_IRQL: 2 FAULTING_IP: nt!KeWaitForMultipleObjects+1cd fffff800`0168d4a7 f00fba2f07 lock bts dword ptr [rdi],7 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT_SERVER BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88005e4f260 -- (.trap 0xfffff88005e4f260) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000168d4a7 rsp=fffff88005e4f3f0 rbp=fffff88005e4f748 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KeWaitForMultipleObjects+0x1cd: fffff800`0168d4a7 f00fba2f07 lock bts dword ptr [rdi],7 ds:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001689469 to fffff80001689f00 STACK_TEXT: fffff880`05e4f118 fffff800`01689469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`05e4f120 fffff800`016880e0 : 00000000`00000000 fffff880`05e4f730 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`05e4f260 fffff800`0168d4a7 : fffffa80`00000000 fffffa80`03f127d0 00000000`03f09600 fffff880`0101bee1 : nt!KiPageFault+0x260 fffff880`05e4f3f0 fffff880`013817a9 : fffffa80`00000000 fffff880`05e4f6e0 00000000`00000001 00000000`00000000 : nt!KeWaitForMultipleObjects+0x1cd fffff880`05e4f6a0 fffffa80`00000000 : fffff880`05e4f6e0 00000000`00000001 00000000`00000000 00000000`00000000 : symsnap+0x1c7a9 fffff880`05e4f6a8 fffff880`05e4f6e0 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`05e4f700 : 0xfffffa80`00000000 fffff880`05e4f6b0 00000000`00000001 : 00000000`00000000 00000000`00000000 fffff880`05e4f700 00000000`00000000 : 0xfffff880`05e4f6e0 fffff880`05e4f6b8 00000000`00000000 : 00000000`00000000 fffff880`05e4f700 00000000`00000000 fffff880`05e4f730 : 0x1 STACK_COMMAND: kb FOLLOWUP_IP: symsnap+1c7a9 fffff880`013817a9 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: symsnap+1c7a9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: symsnap IMAGE_NAME: symsnap.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ab000d3 FAILURE_BUCKET_ID: X64_0xA_symsnap+1c7a9 BUCKET_ID: X64_0xA_symsnap+1c7a9 Followup: MachineOwner
backup destination unreachable after server reboot
I'm running in a recurrent problem with SSR2011 : We use to backup our server running under SBS2011 using SSR2011 onto a backup directory on a NAS. The backup directory is protected and access is granted to administrators (me, of course). Note that security on the NAS is managed by Active Directory. This uses to work perfectly except when server is rebooted (i.e. for updates) After server has been rebooted, the next backup fails because access to the backup destination is denied : Erreur EC8F17B7 : Impossible de créer des points de récupération pour l'opération : Sauvegarde du lecteur de Réservé au système (*:\), (C:\), DATA (E:\). Erreur EC8F03ED : Impossible de créer le point de récupération. Erreur E7D10041 : Impossible d'établir une connexion de réseau à \\nas1_cbl\svg_sbs. Erreur EBAB03F1 : Plusieurs connexions à un serveur ou à une ressource partagée par le même utilisateur, en utilisant plus d’un nom utilisateur, ne sont pas autorisées. Supprimez toutes les connexions précédentes au serveur ou à la ressource partagée et recommencez. (UMI:V-281-3215-6071) Détails : Source : Symantec System Recovery Sorry for the error message in French essentially, it says that SSR was unable to connect the NAS on the network because many connections to a single resource (the NAS) using more than one name are not allowed. However SSR knows only one name (mine) which worked fine before reboot of the server. I tried to remove any protection on NAS directory (access granted to all): same error. NAS can be accessed from the server using windows explorer. NAS can even be accessed from SSR using Recovery Point Browser. But no backup can be performed on the NAS and previous recovery points are declared unavailable !!! Up to now, the only solution I have found is to delete the current backup work, remove all protection on the NAS (not only for the Backup directory but fot the NAS as a whole), create a new backup work (which requires a name and password even if not needed - I use always the same - mine), have it run during a couple of backups and then reset the protection on the NAS. Any hint on why this happens? and how to cure it? BTW, I would like to know how to cancel all connecions to the NAS as suggested by the last sentence of the error message. I have already reset completely the NAS without any succes...
BESR USB 3TB Disk
I have BESR 8.5 working with 2TB USB drive for backup. I am trying to add a 3TB USB drive as a backup location and it will allow me to select it but will not continue through the backup job creation. It just stops and will not continue when I click next. I saw some discussion on 3TB USB 3.0 drives being supported as hot backup (windows needs to be running) locations. Should this work? Is there an issue with 8.5 that does not exist in the current version?