"RollbackSnapshotTempDB" in Single User Mode - can't delete
I have a "RollbackSnapshotTempDB" is single user mode on a system with SQL2012 and SSR2013.I havetried the following with no luck. Any help would be appreciated Step 1: USE master GO ALTER DATABASE "RollbackSnapshotTempDB{XXX}" SET OFFLINE WITH ROLLBACK IMMEDIATE GO Step 2: DROP DATABASE "RollbackSnapshotTempDB{XXX}" Step 3: ALTER DATABASE DISTRIBUTION SET MULTI_USER; GO
e000ff19 and e000ff16: communications failure SQL & VSS
Hi all. We have a problem with BESR 2010 on 2008 R2 64 bit and a MSSQL server 2008 enterprise on a 2008 R2 64 bit (SQL Agent). The full backupjob is always ok, but incremental fails always with VSS errors, and sometimes with SQL errors: e000ff16 - A communications failure has occurred with a Shadow Copy resource. e000ff19 - A communications failure has occurred with a SQL Server resource. I don't find any solution for this problem, I already searched 4 days long. Yesterday I tested an incr. backup and kept looking at the VSS service (on the client of course): when it shut down because it was idle, I startet it again manually and the backup was then OK. But when the backup runs alone without any intervention, it fails with the errors above and I think it's because of VSS that goes sleeping when it's idle. I already tried to change the backup sequence, doesn't change anything. If you need any other info feel free to ask ! I'm really desperate, and I'm also not a windows expert... Thanks !
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, Graham
BackupExec System Restore: SQL & SharePoint?
I've recently downloaded the trial of Backup Exec System Recovery 2010. We are currently using BE 11d and 12.5 for our existing physical servers, with SQL agents, and Sharepoint agents mixed in. The reason I'm trying BESR 2010 is because we just got involved in VMs, using Citrix XenServer. BE doesnt seem to restore to VMs very nicely from what we've seen or experienced, so I wanted to give BESR a try. I like that it is a more simple of an interface, resembling Ghost products. I've backuped and restored a test VM or two and it seems to work fine. I also like how the backup data that writes to disk can be compressed. Its a time saver for when I want to write backups to tape. Now that I've got VMs backing up using this, I want to explore how this handles backing up Sharepoint and SQL. In BE there are agents needed. Are there agents needed for BESR? I see blurbs that you can do granual backups of Exchange and Sharepoint, but I can't really seem to find detailed documentationon setting this up and/or doing restores (Sharepoint/SQL mainly) Should I shy away from this product for those purposes? Should someone be combining products, or can one do everything? ...p.s. One More quick question... I'm using my trial of BESR 2010 to backup our domain controllers which are VM's. I'm guessing if I needed to do a full restore of one of my 2 DC's, I would be fine... but if I wanted to restore individual AD items... I would not be able to, correct?BESR 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 !
Questions about BESR Virtual Edition
I have three ESXi4 hosts and 8 guests which include Exchange, Active Directory, SQL, etc. I'm contimplating getting BESR Virtual Edition but I have some questions before I pull the trigger. I know it can backup exchange servers and recover down to the message level but is it a real exchange aware software where backing up will get rid of the logs? Where is BESR VE installed? Can it be and should it be installed on a virtual server? Seems obvious but can it recover down to the file level? Just want to be sure. Would I need different agents for exchange, sql, etc.? Sorry again if these questions seem obvious but I was looking for an faq on this product and couldn't find one.