The guy responsible for maintaining the SVN server was not having knowledge about the SVN server. Whenever he was told to take the backup of repository, He was just copying the folder of the repository from the server. He never took the backup using backup option in TortoiseSvn. Now the server is crashed. Is it possible to restore the repository from the copy of repository folder. This copy have the .svn folder as well. Please help.
I have scheduled backup and every day copies of:
- bare metal recovery
- system state
- system reserved
- local disk C:\
Backup is stored on iscsi disk. On local disk C are databases mdf with logs. In theory can I restore databases from full windows server backup if there is something wrong with SQL server generated backup of databases like mydatabase.bak ?
Thanks
I've got a backup of my SQL Server 2005 database that I want to put on my dev machine (much quicker to develop against than via writing queries through remote desktop.)
I was able to restore this on one machine at work, so I know that the backup is good (well, I assume it is -- I did have to copy it to an external harddrive and then copy it off again onto my current machine).
The error I'm getting is this:
TITLE: Microsoft SQL Server Management Studio
Restore failed for Server 'XPS17200911\SQL2005'. (Microsoft.SqlServer.SmoExtended)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: File 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\TDC.ndf' is claimed by 'BankA_Tables02'(4) and 'BankA_Tables01'(3). The WITH MOVE clause can be used to relocate one or more files. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1447.4+((KJ_RTM).100213-0103+)&LinkId=20476
And the SQL Script that is generated (you know what I mean) is this:
RESTORE DATABASE [TDC] FROM DISK = N'C:\Users\Matt\Desktop\banka.bak' WITH FILE = 1,
MOVE N'BankA' TO N'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\TDC.mdf',
MOVE N'BankA_Tables01' TO N'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\TDC.ndf',
MOVE N'BankA_Tables02' TO N'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\TDC.ndf',
MOVE N'BankA_Tables03' TO N'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\TDC.ndf',
MOVE N'BankA_Log' TO N'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\TDC.ldf',
NOUNLOAD, REPLACE, STATS = 10
GO
I formatted it a little bit, but only with carriage returns.
I tried to Google this sucker, but the specific file names might be fouling it up. Plus all of the results seemed to assume a simple database format (this one has 5 files, not just 2 like "normal" SQL Server databases) and all dealt with changing filenames, and I don't think that's my problem here.
Any help would be greatly appreciated.
We just got a major disaster: somebody made an uncontrolled update on the production database, and obviously, the backup process is not working since a long time, so we got a major data loss. A 40 millions rows table is now full of garbage.
Does anybody has an idea to restore the data? For example, a tool using filesystem recovery?
Facts:
- ext3 fs (on Debian)
- InnoDB engine (on Mysql 5.0)
Honestly, it's not the first major disaster in our company, but this one could easily be the last one. We usually come up with some idea to save the day, but this time, I'm really out of ideas. Clusterf*ck...
Edit: the problem occurred after an update statement without where. Problem is, th problem happened between monday afternoon and tuersday morning (France time), and was only discovered today, for various reasons (the application offers a synchronization tool, so new data is inserted with the now missing data, but a foreign key in another table is now completly broken). So actually, almost all rows in the table (except the newly inserted) contains the same data (except the id column).
About ibdata* and ib_logfile*, I stopped the replicated server, so they stay as they are now. I can't stop the database on the main server to copy the files.
I have been advise by Commvault partner support to turn off the backup of the master database as the backup failed due to the log file being lock.
The following is the advise given:
"The message is caused by Commvault’s inability to backup the master database’s transaction log. If this is happening intermittently its possible that something is locking the transaction log, preventing SQL iData agent from accessing the log. Typically the master database is just a template and is not used by any applications (applications that do require the use of an SQL database create their own) so there should be no harm in preventing it from being backed up You can do this by nominating NOT to back it up in the primary copy for the SQL data agent"
The following is the error that I get.
sqlxx SQL Server/
SQLxx N/A/
System DBs 19856*
(CWE) Transaction Log N/A 01/08/2010 19:00:16
(01/08/2010 19:00:18 ) 01/08/2010 19:03:15
(01/08/2010 19:03:14 ) 1.44 MB 0:01:11 0.071 2 0 1
ITD014L2
Failure Reason:
• ERROR CODE [30:325]: Error encountered during backup. Error: [ERROR: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot back up the log of the master database. Use BACKUP DATABASE instead. [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.]
Job Options:Create new index, Start new media, Backup all subclients, Truncation Log, Follow mount points , Backup files protected by system file protection , Stop DHCP service when backing up system state data, Stop WINS service when backing up system state data Associated Events:
• 79714 [backupxx/JobManager] [01/08/2010 19:03:15 ]: Backup job [19856] completed. Client [sqlxx], Agent Type [SQL Server], Subclient [System DBs], Backup Level [Transaction Log], Objects [2], Failed [1], Duration [00:02:59], Total Size [1.44 MB], Media or Mount Path Used [ITD014L2].
• 79712 [sqlxx/SQLiDA] [01/08/2010 19:01:53 ]: Error encountered during backup. Error: [ERROR: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot back up the log of the master database. Use BACKUP DATABASE instead. [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.]
• 79711 [sqlxx/SQLiDA] [01/08/2010 19:01:51 ]: Query Result [[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot back up the log of the master database. Use BACKUP DATABASE instead. [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.].
• 79707 [backupxx/JobManager] [01/08/2010 19:00:15 ]: New backup request received for Client [sqlxx], iDataAgent [SQL Server], Instance [SQLxx], Subclient [System DBs], Backup Level [Transaction Log].
Files failed to back up:
• Backup Database[master] Failed
Please advise, thank you.