Restore Of Database Via Veritas 9.1 Fails With Communication Error
May 24, 2006
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.
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?
I'm trying to use ADO to restore a SQL 7 database using a backup file. Thedatabase already exists on the target computer, and is named the same as onthe source computer, and the MDF and LDF files are named the same as well.I am running the below in a stored procedure:RESTORE DATABASE DB1FROM DISK = 'c:mssql7ackupDB1.bak'WITH MOVE 'DB1' TO 'c:mssql7dataDB1.mdf',MOVE 'DB1_log' TO 'c:mssql7dataDB1_log.ldf'And I get an error message "File 'DB1' is not a database file for database'DB1' ".I also tried it without the LDF file in the expression. Same results.Thanks.
I am trying to restore a production database backup to a new location on a development workstation, and it fails with "An internal consistency error occurred, Contact Support". When I tried this on a more powerful workstation it ran without a hitch. The db is about 1.5GB, and I think the dev workstation may be running out of resources during the restore. I stopped non-essential services and ran from TSQL, and it still fails. Any suggestions other than getting a better workstation?
Trying to keep out sysadmins & sa during/between database RESTORE
Configuration: WINNT Server Enterprise 4.0 w/SP5 SQL Server 7 Enterprise & SP1
2 SQL Servers: Production Server Standby server
I Backup (full backup) databases to disk on primary server (logical backup devices are physicaly located on a Standby server (dedicated gigabit NIC in each server for this process). Transaction logs are applied to the Standby server throughout the day.
Problem: How to keep out "sa" and sysadmins from a database while I'm restoring (or between restores) to a standby server? The database being restored cannot be in use during a restore. If a DBA forgets that this process is happening, the statement fails (RESTORE)for the database they happen to be in at the time of the restore.
Example restore statement: Standby Server - RESTORE DATABASE databasename FROM database_dd WITH DBO_ONLY, REPLACE, STANDBY = 'g:Mssql7FromPrimaryDatabaseName_undo.ldf'
I could restrict Domain sysadmin access and change sa password. I could also put the database in "Single user" mode, however this could become problem if my process disconnects and then someone else connects - then my process is locked out. What I'm really looking for is to lock out all activity for a database that is in "standby mode" except for RESTORE processes.
Hi, I run 2 steps viz with NORECOVERY and with RECOVERY in sequence as SQP jobs. The 2nd step fails some times. When it starts failing, I run full backup of the production server again and the 2nd step starts succeding. Unless I run the full backup the 2nd step keeps on failing.
What are the conditions which generate for [SQLSTATE 42000] (Error 3013) and how to tackle this problem.?
The 2 steps are :- 1.RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionsql_full_backup' WITH Replace , MOVE 'arsystem' TO 'd:ardataarsystem.mdf' , MOVE 'arsystem_log' TO 'D:ARLOGARsystem' , NORECOVERY GO
2.RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionSQL daily diff back up' WITH Recovery
The status of the 2 steps is : 1 Executed as user: BPOTESTREMEDY emedybackup. Processed 104480 pages for database 'ARSYSTEM', file 'ARSystem' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1 pages for database 'ARSYSTEM', file 'ARSystem_log' on file 1. [SQLSTATE 01000] (Message 4035) RESTORE DATABASE successfully processed 104481 pages in 49.452 seconds (17.307 MB/sec). [SQLSTATE 01000] (Message 3014)
2. Cannot apply the backup on device 'E:SQL backup from productionSQL daily diff back up' to database 'ARSYSTEM'. [SQLSTATE 42000] (Error 3136) RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
I have a fresh install of sqlExpress and Management Studio Express on my test server. I want to restore my master database from backup.
From the command prompt I set the Sqlservr -s SQLEXPRESS -m
Then I opened another comand prompt and ran my SQLCMD script to restore the Master Database.
here is the sql script: RESTORE DATABASE [Master] FROM DISK = N'E:COPLEYNEWSDATABASEBACKUPMaster.bak' WITH FILE = 1, MOVE N'mastlog' TO N'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAMaster_1.ldf', NOUNLOAD, STATS = 10 GO
I recieve the following error.
Msg 3154, Level 16, State 4, Server COPLEYNEWSSQLEXPRESS, Line 1 The backup set holds a backup of a database other than the existing 'Master' dat abase. Msg 3013, Level 16, State 1, Server COPLEYNEWSSQLEXPRESS, Line 1
How do I restore a Master Database on SQL Express?
I'm a newbie so please be gentle.In attempting to run a restore I get the following error message:"Exclusive access could not be obtained because the database is inuse." However, it doesn't appear that there are any connections to thedatabase. At the suggestion of another thread, I ran sp_who2 and thereare no connections to the database in question. I've been running thesame restore for months and all has been well, until yesterday....I wrote an .asp page (below) to test connectivity to this database.The vb code ran successfully and soon thereafter, my nightly restorefailed. Task manager does no show that the asp page is active.Lastly, I did add a user ("jbtest") as well as change the option to useeither Windows authentication or SQL Server authentication inEnterprise Manager.Any ideas would be greatly appreciated.Thanks.<%@ Language=VBScript %><%companyName = "agemni"Set cnn = Server.CreateObject("ADODB.Connection")cnn.ConnectionString = "DRIVER=SQLServer;SERVER=SHEELA-NA-GIG;UID=jbtest;PWD=test1;APP=MicrosoftDevelopment Environment;WSID=SHEELA-NA-GIG;DATABASE=" & companyName &";Trusted_Connection=No"cnn.ConnectionTimeout = 300cnn.CommandTimeout = 300cnn.OpenSet RS = Server.CreateObject("ADODB.Recordset")strSQL = "SELECT * FROM Preferences"RS.Open strSQL, cnnResponse.Write "connection established with the <b>" & RS("CompanyName") & "</b> database. They are a <b>" & RS("street") & "</b>customer. "RS.CloseSet RS = Nothing%>
Anyone have experience using Veritas to backup SQL Server databases?
I just started with a client who's SQL Server froze with the CPU pegged at 99% on my first day. I think it might be related to using Veritas SQL Server component to run hot backups of the database, while the SQL Server Agent was running simultaneous independent backups. All this on a live database of course, while a user was completing a large transaction.
I advised them to disable the Veritas SQL Server backup component and let SQL Server back up its own databases. Then use Veritas just to archive SQL Server's backup files.
I think I saw a similiar issue at a previous client site that was using Veritas. Please let me know if you have prior experience in this area, and your evaluation of the quality of Veritas database backup component.
Michael writes "We are running SQL and Veritas to backup the databases. Supposedly the SQL agent in Veritas, after a full backup, truncates the log files but for some reason this isn't happening... any ideas?"
I am applying hourly differential backup to the backup server from production with the following command. This command makes the database on standby server into read only mode.
RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionsql_full_backup' WITH MOVE 'arsystem' TO 'd:ardataarsystem.mdf' , MOVE 'arsystem_log' TO 'D:ARLOGARsystem' , STANDBY = 'E:SQL backup from productionSQL daily diff back up'
Now I want to run a command which will put the database in write mode. I have created a job which would make the datbase Write mode. This job runs successfully sometimes and fails sometimes. I need to ensure that the job always succeeds. When it fails, how do I troubleshoot and what is the possible fix?
Thanks in advance.
The error message is
Cannot apply the backup on device 'E:SQL backup from productionSQL daily diff back up' to database 'ARSYSTEM'. [SQLSTATE 42000] (Error 3136) RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
The steps for the job are as follows with the failing step highlighted in bold.
copy /y "\172.31.9.12Remedy BackupackupSQL backupsql_full_backup" "E:SQL backup from productionsql_full_backup"
copy /y "\172.31.9.12Remedy BackupackupSQL backupSQL daily diff back up" "E:SQL backup from productionSQL daily diff back up"
xp_cmdshell 'net stop "bmc remedy action request system server"'
exec rp_kill_db_processes 'ARSYSTEM'
RESTORE DATABASE ARSYSTEM
FROM DISK = 'E:SQL backup from productionsql_full_backup'
WITH
MOVE 'arsystem' TO 'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
NORECOVERY
Failing step
RESTORE DATABASE ARSYSTEM
FROM DISK = 'E:SQL backup from productionSQL daily diff back up'
WITH
MOVE 'arsystem' TO 'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
RECOVERY
xp_cmdshell 'del /f "E:SQL backup from productionsql_full_backup"'
xp_cmdshell 'del /f "E:SQL backup from productionsql daily diff back up"'
xp_cmdshell 'net start "bmc remedy action request system server"'
I have scheduled the following hourly diffential restore job too which never fails.
RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionsql_full_backup' WITH MOVE 'arsystem' TO 'd:ardataarsystem.mdf' , MOVE 'arsystem_log' TO 'D:ARLOGARsystem' , STANDBY = 'E:SQL backup from productionSQL daily diff back up' EXEC MASTER..XP_CMDSHELL 'del /f "E:SQL backup from productionSQL daily diff back up"'
Is it safe to backup while the database is running 1000 transaction/sec.? If yes - why should I buy Veritas Backup Exec Server Edition and Veritas Backup Exec Online Backup Pack ?
Hi Y'all, When i alter 1 single value in my sql server 2000 sometimes i get following error: 1) [MICROSOFT][ODBC SQL SERVER DRIVER] Communication link failure After clicking away: 2)CANNOT START MORE TRANSACTION ON THIS SESSION Maybe someone can help me out on this? Thanks!
I am using ADO in my application to connect and retrieve data from Microsoft SQL Server 2000 SP4. When I start my application, it establishes connection to the server successfully and I am able to retrieve data from the server. here is my test scenario:
1. unplug the network cable from the client machine and put the cable back in after some time. I disconnect from the database in my code when the client machine disconnects from the network
2. Once the client machine comes back on the network, I try to reconnect and retrieve data from the sql server but I get the following error message when I try to execute a sql command:
[Microsoft][ODBC SQL Server Driver]Communication Link failure
This problem occurs only with Window XP SP2. With XP SP1 it works fine. It seems to be problem on the client side as with Windows XP SP1 I do not get this error message at all.
Hello. I have my database and client application. I want my application to know (and to do certain things) when something has happened to a database (for example a row has been inserted). By means of what can it be done??I hope this forum is right place to ask such questions. Thanks for replies!
This is regarding the intermittent failure of communication between the application server and database server in one of our customer environment. Application error as well as SQL error log shows "General Network Error","Communication Link Failure". Please find below the server configuration
Application Server OS: Win 2003 server + Service Pack1, Standard Edition Database Server OS: Win 2003 server + Service Pack1, MS SQL Server 2000 + SP4
We have checked the Client/Server Network utility associated with SQL Server and found TCP/IP protocol is used in communication neither than Named Pipes. DSN is used. We have also followed and implemented as per one KB article which mentioned Win 2003 server's feature of preventing Denial of Service attacks (Chance may be there to prevent the valid login packets).We made the registry changes and disabled this feature. A scheduled job which updates the database happens every morning. Also backup was done using a backup utility which needs the exclusive access to DB. So we have asked the customer to use enterprise manager for back up the DB instead of using the other utility to backup. If any one have experienced the same issue, please let me know.
TestMachine1 runs SQL2005 SP2 and has as linked server myRemoteServer (SQL2000) server. I run an stored procedure in TestMachine1 which inserts about 20,000 rows to a table in myRemoteServer and brings back a similar quantity of rows. This stored procedures take about 1.5min to complete, but no error appears.
When running the same stored procedure in TestMachine2 (also SQL2005SP2), the following error appears after about 1 minute of execution (not the exact text):
SQLNCli. TCP Provider: network name is no longer available - communication link failure.
Please note that this stored procedure worked before on TestMachine2 (but with less than 10,000 rows) and that connectivity is proven among TestMachine1 and myRemoteServer, since I can execute "select * from synonym_MyRemoteTable" with no problems at all in the TestMachine2's Management Studio.
TestMachine1 and TestMachine2 have Windows XP Professional SP2; myRemoteServer has Windows 2003 and SQL Server 2000 SP4.
I have an SSIS package which runs subsequent packages in a batch. When I run the main package through command line or a SQL job and connect to a data warehouse that is on the same machine, it runs without a problem. When I try and connect to a warehouse on a remote machine (ideal configuration), it fails with this error:
Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ".
This seems to happen on random subpackages and isn't always consistent.
My Master.dts.Config file has this connection info:
We are taking database backup using SQL backup option and trying to restore the database on another server giving the following error
Microsoft SQL-DMO (ODBC SQL state 42000) The header for file d:power.mdf is not a valid database file header.The page audit property is incorrect.Restore could not start database "power".Backup or restore operation terminated obnormally The partition on both servers are same and directory structure also same Please help
Hi, When I restore my database on other sqlserver,the system prompted "The database you are attempting to load was dumped under a different sort order ID(42) than the one current running on this server(52),and at least one of them is a non-binary sort order". How can I do? Any help will be appreciated!
I' have several database to restore. I created scripts. Here is an example:
RESTORE DATABASE DatabaseName FROM DISK = 'C:DatabaseName.bak'
This is the error message: Server: Msg 3154, Level 16, State 2, Line 2 The backup set holds a backup of a database other than the existing 'CAMS' database.
While restoring a database from a backup file having extension .back we are getting the following error "back is not part of the multiple family media set backup with format can be used to form a new media set"
I am just few months started to learn SQL server. I just attempt to restore a database which I have backuped last week. The following error appears each time when I was trying Restore it from Hard Disk.
Error :
RESTORE DATABASE must be used in single user mode. when trying restore the master database. RESTORE DATABASE is terminating abnormally.
I am wondering if you guys have any experience with failing Stored Procedures running inside a SSIS package with the following error:
===================================================== Message Executed as user: GAALPSVR034FSYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:51:22 AM Error: 2008-05-19 09:06:55.15 Code: 0x00000000 Source: usp_SLIM_Site_PreProcess Description: TCP Provider: The specified network name is no longer available. End Error Error: 2008-05-19 09:06:55.18 Code: 0xC002F210 Source: usp_SLIM_Site_PreProcess Execute SQL Task Description: Executing the query "Exec usp_SLIM_Site_PreProcess" failed with the following error: "Communication link failure". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:51:22 AM Finished: 9:06:55 AM Elapsed: 932.203 seconds. The package execution failed. The step failed. ======================================================
Sometime it fails when gets called through a job and sometimes even when a package is open in a design mode. The actual Stored Procedure NEVER fails if called in SQL Server Management Studio.
Any ideas or suggestions will be very helpful and appreciated Thanks for your help!
I'm trying to use schedulled task to automate restore and i keep getting the error database in use, it is set to dbo only and single user, and it has me as the user that has the lock, i have tried to kill it but it won't go, i have even started and stopped the server. any ideas?
Database Restore & Attach Error I have a problem with restoring or attaching DB files from different version of the engine. I Have a existing SQL server 7.x and another one is SQL 2000 but I try to backup my database and restore it into the 2000 engine This is the following Problem which occurs :-
1st Problem : During Restoration, The restoration process was runing fine until it reach the last inficatior tab and it fail and say Database terminated abnormal. I been try to restore into other machine also but it give me the same problem.
2nd Problem : Say I can't restore but I stop the engine and manual copy the *.mdf and *.ldf to another machine. I try to restore it but it "is on a network device not supported for database files." So what shall I Do with it.
Pls Advise If anything need to be done before I do the restoring and anything need to be done in both 7.x and 2000 Engine.
hi.. im having a hard time restoring my .bak file.... i have a stored procedure like this.. and every time i call this in my program an error displays... (database in use. the system administrator must have exclusive use ot the database to run the restore procedure)
CREATE PROCEDURE sp_db_restore AS RESTORE DATABASE Inventory FROM DISK = 'C:MSSQL7BACKUPInventory.bak' WITH MOVE 'Inventory_data' TO 'C:Inventory_data.mdf', MOVE 'Inventory_log' TO 'C:Inventory_log.ldf', REPLACE
I am trying to restore and SQL 2000 database into a new SQL 2005 database. I performed by SQL 2000 backup and created a blank database FERS_Production in SQL 2005. FERS_Production was the original name of the database in the SQL 2000 instance.
I have tried giving the new database the same name as the original and a different name to the original database
(Below is the scripted T-SQL that I get from the DB Admin tool
RESTORE DATABASE [Fers_Production] FILE = N'FERS_Production_dat', FILE = N'FERS_Production_log' FROM DISK = N'D:Microsoft SQL Server (2000)MSSQLBackupFers_ProductionFers_Production_db_200607270206.BAK' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 10 GO
When I run this I get the following error.
Msg 3154, Level 16, State 4, Line 1 The backup set holds a backup of a database other than the existing 'Fers_Production' database. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally.
Other searches I have performed trying to fix this problem have said to use the REPLACE clause with the RESTORE DATABASE command, but as you can see I am doing that.
Also I no longer have SQL 2000 installed so I cannot try to do a DTS copy which was another suggestion I came across.
In my string below, my forum setup up file, setup.asp , when run delivers an error that it is unable to connect to the database. Error: 800004005
I am running this from within IIS 5.0 aon a Windows 2000 Server, by right clicking the file in IIS and choosing "browse" I am trying to set this up so user IUSR_SERVER_NAME can "read and Write" to the database or instance I have created called rpggamerpro. The authentication in the SSSAC is set to use both Windows and SQL Authentication for the "master". I have set permissions on the folder which contains the SQL 2005 Express installation and database for IUSR_SERVER_NAME to read/write. I have created a IUSR_SERVER_NAME user in the Security/User directory for the database or instance "rpggamerpro" and gave the user read/write permissions there. So I am still at a loss as to what permissions, strings, settings, configuration or whatever the heck else needs to be done in order to get this thing to work. Please anyone willing to help a realative new commer to the SQL and DB world would be greatly appreciated.
trConnString = "Provider=SQLOLEDB;Data Source=nssqlexpress;database=rpggamerpro;uid=IUSR_NS;pwd=;" '## MS SQL Server 6.x/7.x/2000 (OLEDB connection)
