Can I Restore Sql 2000 From Veritas Under Sql 2005?
Nov 14, 2006
While ago my SBS 2003 which had SQL 2000 crashed so I had to rebuild everything and this time I used SBS 2003 R2. My SQL 2000 databases were backed up under Veritas 10 and now I'm trying to restore them under SQL 2005. Is this possible?
While ago my SBS 2003 which had SQL 2000 crashed so I had to rebuild everything and this time I used SBS 2003 R2. My SQL 2000 databases were backed up under Veritas 10 and now I'm trying to restore them under SQL 2005. Is this possible?
We are running SQL 2000 sp4, only one user database (SAP) the database is 63 GB. The ldf files were trashed so I went to tape to restore. We are using veritas backup exec 9.1 sp4. Veritas is on the same server. I can restore the master db and the msdb fine. However when we attempt to restore the DEV db it runs for 2 hours and then fails with a communication error from veritas. When we restore the master the DEV db comes up suspect as there are no files for it to attach to) so we cannot attach to it to restore, so I have deleted it and attempted to restore - same communication error. I have recreated a db named DEV with the mdf etc created to the size needed plus some to be sure, no good same behavior (behavior described below). The job starts and it creates all the folders for the database (there are 1 MDF, 5 NDF, and 4 LDF files each in its own folder). Then it begins to create teh individual files it gets ~half way through at about an hour-hour and fifteen. During this time there are a large number of writes being performed by SQL (I assume it is creating the structures). Then it switches over to reading from tape a large number of read by beengine for another 45-1.5 hours then the job fails with the error unable to communicate with the device. I ahve noticed that once it starts reading from tape the db is gone from enterprise manager, and the mdf etc. files that were being created are now gone.
Hi,I have an old 2000 bak file for a db that I would now like restoredonto sql server 2005. I keep erroring out though, this is what I'mdoing:Went to Restore Database in sql 2005, selected the db I want itrestored to, and File (say c: empxyz.bak)Checked the restore checkbox, went to options checked Overwrite theexisting database.Do I need to do anything else, maybe in the Restore the database filesas section? As those path are listed as:C:Program FilesMicrosoft SQL ServerMSSQLdataxyz.mdfC:Program FilesMicrosoft SQL ServerMSSQLdataxyz_log.ldfIf I just run it without updating those mdf and ldf paths, I keepgetting an error:Exclusive Access could not be obtained because the database is in use.Thanks.
I'm tring to restor a DB from sql 2005 (which is located on my local computer) into sql 2000 (which is located on the server) and I am getting this type of message:
TITLE: Microsoft SQL Server Management Studio ------------------------------
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Too many backup devices specified for backup or restore; only 64 are allowed. RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3205)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0818&EvtSrc=MSSQLServer&EvtID=3205&LinkId=20476
My customer has SQL Server 2005. I have SQL Server 2000 on my laptop (on XP Pro). I believe I have an empty database the same as theirs, but I need to restore their data. They sent me a normal SQL Backup, but my laptop threw a fit and cannot work with it.
They are now trying to export the database to Microsoft Access and send me that, but I won't get that until next week now. However is there a better and easier solution for those of us with insufficient experience of this, please?
Hi All I have a problem in transferring a 2005 backed up database to SQL Server 2000 SP3. i got an error message, crux of it is "too many backup devices specified only 64 allowed"
the i browsed MICROSOFT help, downloaded SQL 2000 SP4 - mentioned as a fix for the above error.
Now get a message,crux of it is "current version of Database in 611 and destination version is 536"
Is there a solution???? should i download any other patches or Should i tweak the SQL 2005 backup process??? ASAP Plz
Does anyone know if this works to where the data is viewable/usable?
I have an application that takes datasets out of the SQL database. We decommisioned our old SQL 2000 SP4 machine and brought in a SQL 2005 Server. What we did was backed up the old database and then restored it on the new Server.
Now the application does not see the old datasets but will collect new ones that are viewable. We can import older datasets but we have nearly 27 GB of data, which our DBA can see the old tables in Enterprise Manager but our applciation can't see it.
I'm thinking it might be a schema issue or the way that 2005 translate the odler 2000 SP4 database. Does anyone know, or have they run a back up on a older 2000 Server and then restored it to a 2005?
i've made a backup from a MS SQL Server 2005 database and i tried to restore this database to a MS SQL Server 2000. Unfortunately, I got following error
The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrad this database.
what can i do ? is it possible to restore the MS SQL Server 2005 DB on a MS SQL Server 2000 ?
I have a database backup from Server Express 2005 that I want to restore to SQL Server 2000. I keep getting an error message saying it was created a newer version and wont work. Is there a workaround to this.
I am maintaining a .net 1.0 asp.net web application that accesses a SQL server 2000 database. I need to backup the database and then restore it on a laptop. Currently it resides on a server. The problem is that on the server they are using sql server 2005. If I backup using 2005 and then try and restore this database using SQL server 2000 or 2005 on the laptop, I get an error message. "Too many backup devices specified for backup or restore; only 64 are allowed. RESTORE DATABASE is terminating abnormally. What can I do to restore the database? Must it be backed up with SQL server 2000 and then restored with SQL Server 2005? Please help!
I'm trying to see the differences between Backup/Restore and Attach/Detach. I backup and detach a database from SQL Server 2000 SP3 and then attach and restore it to SQL Server 2005 SP1.
The differences I noticed are:
1. The restored database has a much larger initial size (database size is same) for data and log. 2. The attached database has a last backup date 3. If the backup is restored over a database, the restored database is showing owned by the database owner of the database restored over but syslogins and sysusers do not match.
I don't understand why #1 happens.
Are there any other differences between Backup/Restore and Attach/Detach?
Hi All I have Computer is setuped SQL Server 2000 and SQL server 2005 when I restore SQL Server 2005 it's OK but when it's not OK when I restore in SQL Server 2000. The Error as follows:
Hi Friends,I have installed SQL server 2005 Express Edition and SQL Server managementI have a SQL server 2000 db backup file. I try create a new database in my SQL server 2005 express Edition and try restore that backup file from device, it only searching for file with *.bak and *.tm extension! I tried generate backup file with .bak extension and tried restore into SQl server 2005 express edition but still it is not allowing to do so! I also tried copy my database's data file and log file and paste it under SQL server 2005 express edition Data folder and still not able to read the tables.Is that any ways to do restoring for this SQL server 2000 backup file into SQL server 2005 express edition! Anybody can help me on this please...:eek:
May Any one guide me? I have a backup file of database which is in SQL Server 2000. it has no Extension.I want to restore this backupfile or this database in my SQL Server 2005. I have tried to Attach Database or attach this backup file in Sql Server2005 but it also fails . First I have created New database name as is on the backupfile and then I have also tried to rename this file with .bak extension and then try to restore again it fails. Plese Guide me urgently........ :eek: :eek: :eek: :eek: :eek:
This is a very urgent requirement of my client having 200 stores and one Head office. the HO has just installed SQL-Server 2005, The HO sends small backups of the data related to stock transfer which needs to be restored at stores. It was working find when both the HO and stores were SQL-Server 2000. but the process has come to a dead halt as the HO has SQL-Server 2005. It is not possible to convert the stores immediately. please help me out.
I was running Small Business Server 2003 with MS SQL Server 2000. I put backups of all my SQL Server 2000 databases on hard disk d: and the operating system and applications on c:/. I then reformatted c:/ (but left d:/ intact) and installed Windows XP Home. Then I installed MS SQL Server 2005 Developer's Edition.
I would like to now restore the backups of the SQL Server 2000 databases (still intact on drive d:/) to SQL Server 2005, but I get a variety of error messages.
I suspect that I am going about this the wrong way. I have done several hours of research in the documentation without success. I cannot attach the SQL Server 2000 database to SQL Server 2005 because it is a backup, not a database. I cannot migrate the databases as part of the installation of SQL Server 2005 because (a) they are back-ups, and (b) I don't have SQL Server 2000 installed when I install SQL Server 2005.
I have a file backup database SQL Server 2000 I want to restore it to SQL Server 2005. But it failed. I try : Database ( right-click) - Restore Database - From Device - Specify Backup Add Locate Backup File. I must choose File of Type is All File so that i can find file backup from SQL 2000, if i choose File of Type is *.bak,*.trn so i cannot find that file. And then i choose OK all. But it failed. The error is below :
Restore failed for Server 'DHBK-734D0C3663'. (Microsoft.SqlServer.Smo) ------------------------------ ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: Directory lookup for the file "C:Program FilesMicrosoft SQL ServerMSSQLdataqlsach_Data.MDF" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv) at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()
===================================
System.Data.SqlClient.SqlError: Directory lookup for the file "C:Program FilesMicrosoft SQL ServerMSSQLdataqlsach_Data.MDF" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Smo)
Program Location:
at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection queries, ServerMessageEventHandler dbccMessageHandler, Boolean errorsAsMessages) at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server server, StringCollection queries) at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
Hello, We use Veritas BE with SQL agent to backup all the company's databases. Has anyone used Veritas for SQL backups and restores, adn what are the pros/cons verses some scripting. I've been in a few recovery situations with veritas although limited it's easy for a network analyst to restore, but I prefer scripts to restore. Our SQL shop is young and still in alot of it's development phase. I'd like to break the trend we have now and write some decent batch/sql scipts for backups?
Right now veritas backs up all our NT boxes, hence why we use it for SQL. I have scripts, but haven't implimented. Should we switch to scripts or stay with Veritas?
Hi , I greatly appreciate if anybody can tell me where can i get information regarding SQL Server 7.0 using Veritas media management tool for backup and restore. thanks in advance Mohan
I have Veritas Backup Exec. The software does a good job with the backup. However a few of my SQL 7 Databases the files are skipped even though I have told the software to lock the file. Specificaly this happens on my EPICOR Accounting Databases. Is there a command I can issue to stop the SQL server from running prior to the backup and then re-start after the backup has completed. Any help would be appreciated. Thanks
Could someone please explain the pros/cons of installing the VeritasSQL agent versus backing up the .bak file generated by SQL Server? Ihave worked with both setups in the past, but never really understoodwhat made one better than another.TIA,Brad