SSR 2011 - can not restore running system
We have a Hyper-V server HOSTA (Windows Server 2008 Std SP2 x64) with 2 guests SBSA (Windows SBS 2008 SP2 x64) and APPSA (Windows Server 2008 Std SP2 x64). Both SBSA and APPSA have Symantec System Recovery 2011 (Build 10.0.0.39952) installed, and backup to share on HOSTA and Offsite to a FTP location. The Offsite location has HOSTB (Windows Server 2008 R2 Std SP1 x64) with Symantec System Recovery 2011 (Build 10.0.0.39952) installed. When the Restoring SBSA or APPSA it fails every time in all ways we have tried: Convert sv2i to Hyper-V VHD fail: Converts ok, then on start of VM guest runs the mini setup, then updates, then randomly reboots. after that we receive the stop 7b error, But the data on the .vhd can be mounted and accessed. Create Hyper-V guest and use System Recovery Disk fails: Towards the end of the restore a "Recover My Computer Wizard" box pops up with the message: Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Can::ReadFileFrameReal: .\Can.cpp(826): Read Failure. Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Can::ReadFileFrameReal: .\Can.cpp(826): Read Failure. with an Ok button that takes you to the menu screen. Convert to VMware Server Disk fails: The convert stops at 99% with 3 seconds to go (With or without "Run Windows Mini-Setup") Convert s2vi using VMware Player 3.1 fails: Very slow reading the s2vi file and then I enter the password and straight away I get the error from VMware Player: Failed to open virtual machine: Failed to query source for information. We have tried a One off recovery point on-site and taken it to the off-site location and receive the same issues. A convert to vhd of APPSA on APPSA: converts ok, moved to HOSTA. on boot of the restored guest APPSA we receive: Windows Boot Manager Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. choose your language settings, and then click “Next.” 3. click “Repair your computer.” If you do not have this disc, contact your system administrator or computer manufacturer for assistance. status: Oxc000000f Info: Windows failed to load because the NL5 data is missing, or corrupt. Please can someone suggest any ideas
PROBLEM to install altiris client with console management solution 2011 of backup exec
I'm trying to make the client installation from the Altiris management console exec backup solution for 2011 and send errors, try to install manually on a computer and a server and send the agent installation errors. Only able to install the console without problems, problems arise when trying to install as first point Altiris agent the new version. someone will have the same problem or help me with the correct way to configure these consoles. see file attachment. Greetings
ISCSI mapped drives to SAN
Hi all, I am new to BESR Server and have today downloaded the evaluation software. I have a basic question before I start backing up. We have two servers which have iscsi drive mappings to an HP SAN. So we have drives C, D, F (SAN) and G (SAN). The data on the SAN is SQL data. How to I approach this backup, as the F and G drives are too large to fit on the external drive I am using (although they would fit individually). The destination server is offsite, and has plenty disk space (albeit onboard as opposed to SAN). Any suggestions very welcome. Best regards, GrahamBackup exec 12.5 & system restore 8.5 to the same NAS NOT WORKING
Help!! I a having a problem with a server it is win server 03 running exchange sql and I am backing to a single nas drive. The data up with backup exec 12.5 with the sql add in and Exchange add in and also using system restore to allow for quick recovery to a virtual pc for disaster recovery. there is no overlap in the time window of the to jobs but every week or so system restore just fails to run with this message Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\), Data (E:\). Error EBAB0013: A test that safeguards the integrity of the program failed unexpectedly. CHECK failed, Can::GetSafeFrameFileOffset: .\Can.cpp(321): offset != INVALID_FRAME_INDEX. Details: 0xEBAB0013 Source: Backup Exec System Recovery adnd there is plenty of drive space????? GrahamBESR on windows 2008 R2 64 bit with MS-SQL Express: SQL Service doesn't run
Hi, We have tried a bare metal recovery with IDR on a server like following: 1- Full backup 2- creating the IDR-BootCD 3- (2 weeks later: the test -- backups are running every day: Sunday full, mon-sat incremental) 4- shutting down the server, taking the HDD's out and put some new HDD's in, for testing. 5- Disaster recovery is OK, has worked. 6- When booting the Server, it is impossible to restore the MS-SQL Express Databases, because it's not possible to bring the SQL services up. See Errorlog below. The system protocol says following about SQL: Der Dienst "SQL Server (SQLEXPRESS)" wurde mit folgendem dienstspezifischem Fehler beendet: Der angegebene Ressourcenname wurde nicht in der Image-Datei gefunden.. (Event ID 7024) Mindestens eine Datei stimmt nicht mit der primären Datei der Datenbank überein. Falls Sie eine Datenbank anzufügen versuchen, wiederholen Sie den Vorgang mit den richtigen Dateien. Falls es sich um eine vorhandene Datenbank handelt, ist die Datei möglicherweise beschädigt und sollte von einer Sicherung wiederhergestellt werden. (Event ID 5173) FileMgr::StartLogFiles: Betriebssystemfehler 2(Das System kann die angegebene Datei nicht finden.) beim Erstellen oder Öffnen der Datei 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBLog.ldf'. Diagnostizieren und korrigieren Sie den Betriebssystemfehler, und wiederholen Sie den Vorgang. (Event ID 17207) I already tried to repair/reinstall the sql server, but it doens't work either. Errorlog MSSQL Server: 2010-07-09 15:01:10.56 Server Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64) Jul 9 2008 14:17:44 Copyright (c) 1988-2008 Microsoft Corporation Express Edition with Advanced Services (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) 2010-07-09 15:01:10.56 Server (c) 2005 Microsoft Corporation. 2010-07-09 15:01:10.56 Server All rights reserved. 2010-07-09 15:01:10.56 Server Server process ID is 860. 2010-07-09 15:01:10.56 Server System Manufacturer: 'Supermicro', System Model: 'X7DBR-3'. 2010-07-09 15:01:10.56 Server Authentication mode is MIXED. 2010-07-09 15:01:10.56 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'. 2010-07-09 15:01:10.56 Server This instance of SQL Server last reported using a process ID of 4860 at 09.07.2010 14:52:49 (local) 09.07.2010 12:52:49 (UTC). This is an informational message only; no user action is required. 2010-07-09 15:01:10.56 Server Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf 2010-07-09 15:01:10.61 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2010-07-09 15:01:10.61 Server Detected 8 CPUs. This is an informational message; no user action is required. 2010-07-09 15:01:10.67 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2010-07-09 15:01:16.20 Server Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2010-07-09 15:01:16.25 spid7s Starting up database 'master'. 2010-07-09 15:01:16.45 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'. 2010-07-09 15:01:16.46 spid7s SQL Trace ID 1 was started by login "sa". 2010-07-09 15:01:16.48 spid7s Starting up database 'mssqlsystemresource'. 2010-07-09 15:01:16.54 spid7s The resource database build version is 10.00.1600. This is an informational message only. No user action is required. 2010-07-09 15:01:16.70 spid10s Starting up database 'model'. 2010-07-09 15:01:16.70 spid7s Server name is 'XXXXXXXX\SQLEXPRESS'. This is an informational message only. No user action is required. 2010-07-09 15:01:16.70 spid7s Information: Es wurden keine Sprachen mit Volltextunterstützung gefunden. 2010-07-09 15:01:16.70 spid7s Starting up database 'msdb'. 2010-07-09 15:01:16.75 spid7s Fehler: 17204, Schweregrad: 16, Status: 1. 2010-07-09 15:01:16.75 spid7s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 2(Das System kann die angegebene Datei nicht finden.). 2010-07-09 15:01:16.76 spid7s Fehler: 5120, Schweregrad: 16, Status: 101. 2010-07-09 15:01:16.76 spid7s Die physische Datei 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBData.mdf' kann nicht geöffnet werden. Betriebssystemfehler 2: '2(Das System kann die angegebene Datei nicht finden.)'. 2010-07-09 15:01:16.79 spid7s Fehler: 17207, Schweregrad: 16, Status: 1. 2010-07-09 15:01:16.79 spid7s FileMgr::StartLogFiles: Operating system error 2(Das System kann die angegebene Datei nicht finden.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation. 2010-07-09 15:01:16.79 spid7s Dateiaktivierungsfehler. Der physische Dateiname 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBLog.ldf' ist möglicherweise falsch. 2010-07-09 15:01:16.82 Server The certificate [Cert Hash(sha1) "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"] was successfully loaded for encryption. 2010-07-09 15:01:16.82 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ]. 2010-07-09 15:01:16.82 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ]. 2010-07-09 15:01:16.84 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required. 2010-07-09 15:01:16.84 spid10s Fehler: 5173, Schweregrad: 16, Status: 1. 2010-07-09 15:01:16.84 spid10s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. 2010-07-09 15:01:16.84 spid10s Fehler: 5173, Schweregrad: 16, Status: 1. 2010-07-09 15:01:16.84 spid10s One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. 2010-07-09 15:01:16.84 spid10s Die Protokolldatei 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\modellog.ldf' entspricht nicht der primären Datei. Sie stammt möglicherweise von einer anderen Datenbank, oder das Protokoll wurde zuvor neu erstellt. 2010-07-09 15:01:16.84 spid10s Fehler: 945, Schweregrad: 14, Status: 2. 2010-07-09 15:01:16.84 spid10s Die 'model'-Datenbank kann nicht geöffnet werden, da auf einige Dateien nicht zugegriffen werden kann oder nicht genügend Platz im Arbeitsspeicher oder auf dem Datenträger zur Verfügung steht. Detaillierte Informationen finden Sie im SQL Server-Fehlerprotokoll. 2010-07-09 15:01:16.84 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. 2010-07-09 15:01:16.84 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. 2010-07-09 15:01:16.85 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies. 2010-07-09 15:01:16.85 Server SQL Server is now ready for client connections. This is an informational message; no user action is required. Please help me, the testlicense is at about 40 days (max 60). Thanks !