I am trying to backup a database to a tape. It works when it wants to. I get a 3013 error. The drive is fully functional. Seagate backup works fine. SQL Backup does not. I think it might be that the tape needs retensioning sometimes. Here is the sql statement: BACKUP DATABASE pubs TO TAPE='.ape0' WITH FORMAT. Is there a retension parameter I am failing to see?
Hi, Does Any one know How to find out How much space left in a Tape Drive? Is it possible with Win nt OR Win 2000? or It required some special utility. Any one know please suggest, Thanks Nil.
Hi I Have 8 small databases around 10 to 30 MB each. I am taking tape backup. Full database backup Daily. Now problem i am facing that i am not able to schedule this process because when it complete one database backup, tape automatically come out. So due to this reason i am not able to schdule this job. If any one has solution for this please suggest. Thanks. Nil.
We have Dell Optiplex GX1 PCs with Seagate ST22000 IDE tape backup devices, running NT Workstation or NT Server and SQL 7.0 with SP1, NTSP5. SQL 6.5 will backup successfully to these devices, but SQL 7.0 will not. The most common error message is 18257, Device or media does not support ... 42000 Syntax error, permission violation, or other nonspecific error...
I have a SQL Server 7.0 with and exteranl SCSI tape device. When I attempt to backup a database in EM the tape device is being greyed out.
I have add the backup device using sp_dumpdevice and made sure that it is in sysdevices table. It will not allow me to add this backup device from the drop down.
1. Why does EM not see this device ? 2. If I try to back this up using T-SQL will I be able to use the registared tape device.
I want to create a backup device for the tape drive. So I go in "Server Objects"=>"Backup Devices" and create a new device. Problem is: In "Destination" I can't select "Tape:".
The ntbackup.exe program recognizes the tape drive, but SQL2005 not.
I have this: -SQL2005 Enterprise edition 64bit. -Tape drive HP StorageWorks Ultrium 960.
Someone knows how I can create a backupdevice for the tape?
Thanks
IF Debugging = removing bugs from program THEN programming := putting bugs in program;
HiWe are running SQL 2000 Enterprice version with SP3a on a DellPoweedge 5600 server running Advance Server. It has Tape drivePowerVault 110T (DLT VS80 Tape Drive) & uses DLT tapeIV tapes. A DBmaintenance job had been specified to backup on to tape daily. I havefollowing issues;1.The backup job sometimes fails with the following error in Eventlog(Event ID:17055)3041: Backup failed to complete the command BACKUP DATABASE [UNIQRS]TO TAPE = N"\.Tape0 WITH NOINIT, NOUNLOAD, NOSKIP, STATS = 10,NOFORMAT. The job is specified with the Verification option.2. If I try to restore a succeeded backup it asks for a initial tapewith a past date which does not exists3. Is there a way to view the content of the tape & free space etc.4. It is recommended to put a disk backup & transfer it to tape usingWindows backup utility. Is there a way to automate this by initiatingthe Backup utility when the SQL finishes the disk backup.ThanksChirath
I've got a new HP ML370 G4 Server 2003 SP1 with a fresh install of SQL 2005 SP1. I'm trying to create a backup device for the internal HP DAT 40 and tape is greyed out as an option. I have the newest HP software drivers and firmware. The tape drive is seen by Server 2003 device manager and by NTBACKUP. I can backup using that program. Why doesn't SQL 2005 see it? I tried a new HP Ultrium tape drive with the same results. Anyone else see this and can recommend a fix? TIA
I am trying to configure the backup device on SQL Server 2005. I cannot get the Tape device list. The Tape Device is attached physicaly to the server ! (IBM Ultrium-TD3 scsi). I can 'see' the device using Windows Backup; but I cannot even get the list of tapes on SQL Server.
but how to append more than one databases( SQL 2005) to the same tape.
Having said this, what is the solution for " I've got a new HP ML370 G4 Server 2003 SP1 with a fresh install of SQL 2005 SP1. I'm trying to create a backup device for the internal HP DAT 40 and tape is greyed out as an option .........." Pls advice me.
Me and my collegues was recently assigned to maintain a SQL Server 2000 instance, which pretty much only holds one database. From what we can tell, a backup of this database has never been created, atleast not through SQL Server. When asking the previous owner, the answer was "We have been taking 'Legato backups' every day!"
We now intend to schedule a SQL Server backup job, but out of curiosity... In case of a disaster, would these "Legato backups" have been any use at all? Please elaborate :-)
My company is using backup exec to bacup all servers and when it came to this particular server these backups were skipped. I checked the log files and backups that are ran within SQL. Can someone explain to me what may have caused this. My guess is that there was something with the media that was trying to backup this server. Thanks for all of you help.
Below is the error message that was recieved after backup exec attempted to backup up this server.
Media Name: "DIFF" Backup of "SQLserver1E$ " Backup set #49 on storage media #1 Backup set description: "Daily 5" Backup Type: DIFFERENTIAL - Changed Files Backup started on 11/05/2001 at 11:46:00 PM. The item MSSQL7Datadatabase1_Data.MDF in use - skipped. The item MSSQL7Datadatabase1_Log.LDF in use - skipped. The item MSSQL7Datadatabase2_Data.MDF in use - skipped. The item MSSQL7Datadatabase2_Log.LDF in use - skipped. The item MSSQL7Datamaster.mdf in use - skipped. The item MSSQL7Datamastlog.ldf in use - skipped. The item MSSQL7Datamodel.mdf in use - skipped. The item MSSQL7Datamodellog.ldf in use - skipped. The item MSSQL7Datamsdbdata.mdf in use - skipped. The item MSSQL7Datamsdblog.ldf in use - skipped. The item MSSQL7Dataorthwnd.ldf in use - skipped. The item MSSQL7Dataorthwnd.mdf in use - skipped. The item MSSQL7Datapubs.mdf in use - skipped. The item MSSQL7Datapubs_log.ldf in use - skipped. The item MSSQL7Datasysdev_Data.MDF in use - skipped. The item MSSQL7Datasysdev_Log.LDF in use - skipped. The item MSSQL7DataTEMPDB.MDF in use - skipped. The item MSSQL7DataTEMPLOG.LDF in use - skipped. Access denied to directory emp. ^ ^ ^ ^ ^
Backup completed on 11/05/2001 at 11:47:02 PM. Backed up 55 files in 48 directories. 19 items were skipped. Processed 84,537,951 bytes in 1 minute and 2 seconds.
Hi, we have backups taken regularly on tape device. When I restore the back up on the same server,it is working. But if I try to resotre the same backup on a new server it is giving problems I have the same configuration of the new and old server. It is giving error 10005 DB process dead and after that the database is marked grey and in bracket (loading) and a lot of other errors like Begin Stack Trace, sympton dump created,end stack trace ,etc( A very Long List of errors) and a new dump is created in log directory It is also telling "EXCEPTION_ACCESS_VIOLATION" i am having the same problem on all the servers we have. Help me regarding this. DP
Hi I am having some trouble with our Veritas Backup Exec not properly releasing db backup files, & thus interfering with the deleting of old backups. We have other servers still needing tape backups implemented and I wonder if anyone has a good backup software/hardware system to recommend, that is ideal for database backups, & on the hardware side is reliable? Anyone have any to recommend?
i have taken full database backup on tape drive one week ago,by automated scripts ,now when i check the maintenance plan history , it says the task failed and gives a message that unable to open the \. ape0 ,with error
([Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device '\. ape0'. Device error or device off-line. See the SQL Server error log for more details. [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally. )
Environment: Win Server 2003 Standard Version, SQL Server 2000, HPDDS3 Tape(local).Backup procedure:1. open SQL Server Enterprise Manager2. find the database i want to backup3. right click and select "All Tasks"-"Backup Databse..."4. Select "destination"-"backup to"-->>"Tape"5. Click "Add", Select "Tape" device name(or may address)"\.Tape0"6. Click "OK" begin to backupError:system prompt:The file on device '\.Tape0' is not a valid Microsoft Tape Formatbackup set. BACKUP DATABSE is terminating abormally.On this SAME server, using the same TAPE, but USE Tapeware(a HP backupsoftware come with HP tape machine) to back file, everything is OK.I don't have any clue about this. am new to Windwos, new to SQLserver. Any body could show me light? Thanks in advance.A.Y. From shanghai/China
Hi I have two database called test1 and test2 both are of same size(both device and log). I run the following statements to take the backup of both the databases using the tape device 'tapedevice1'. dump database test1 to 'tapedevice1' dump database test2 to 'tapedevice1' After this I run the load statement load database test2 from 'tapedevice1'. It just restore the database test2 with test1 data which is added first to the tape with a warning. Is there any restriction that in a single tape backup of more than one database is not possible. Your valuable suggestion appreciated Jiji
Does anyone know if it is possible to have a tape device another server as a tape dump device on SQL. Instead on removing the tape drive and installing it locally ?!?
We lost (Couldn't find ) the full backup on a Tape we were supposed to use for restore, but seems like they lost it. All we have is a Diff backup. Wondering if that is any good at all .
First posting to the group. I have received a lot of valuable info from youguys. Now, an OT question:What's a good tape drive to perform unmanned weekly backups for a WindowsXP Pro box running SQL server 2000?--Joel Farris | AIM: FarrisJoel** Their Web. Your Way. http://getfirefox.com **
I have inherited a SQLS erver 2000 instance where the client neverimplemented a backup startegy for the "master" and "msdb" databases.MSDB is now showing errors and my only option for a restore is from atape backup of the server.Any thoughts..
I have schedule backup job from SQL Server 2000 to Tape. Each Jobs consist of 4 steps which backup different database.
Sometimes I encounter problem. The Message is
Executed as user:dbo. The file on device '\.Tape0' is not a valid Microsoft Tape Format backup set. [SQLSTATE 42000] (Error 3242) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
There is no problem at the command, as it will run normally when i manually trigger the schedule job. Sometimes the error occur only after few days the job run.
I would like to restore SQL Server Express and its databases from a tape backup to the same server. This is a disaster recovery senario.
I backed up the Master, Model, MSDB and my own test database using SQLCMD scripts. I have no problem restoring these using task scheduler on the server before the disaster recovery.
However, in my real disaster recovery testing, When the server is restored by tape drive (HP one button disaster recovery), I try to run my SQLCMD restore scripts in task scheduler and I cannot connect to the sql server. Also I cannot connect with Management studio. I have recieved the following error in event viewer.
Event Type: Warning Event Source: SQLBrowser Event Category: None Event ID: 3 Date: 9/15/2006 Time: 8:16:36 AM User: N/A Computer: COPLEYNEWS Description: The configuration of the AdminConnectionTCP protocol in the SQL instance SQLEXPRESS is not valid.
Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7024 Date: 9/15/2006 Time: 8:16:36 AM User: N/A Computer: COPLEYNEWS Description: The SQL Server (SQLEXPRESS) service terminated with service-specific error 3411. C:Program FilesMicrosoft SQL Server90ToolsBinn>sqlcmd -S.SQLExpr COPLEYNEWSDATABASEscriptsMASTERFULLRESTORE.sql" HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred whi shing a connection to the server. When connecting to SQL Server 2005, re may be caused by the fact that under the default settings SQL Serve allow remote connections.. Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
My question is, what is the correct procedure to follow when I want to do a disaster recovery and restore SQL Server Express from tape backup using the Simple Backup method and scripts.
Is it always required to reinstall sql server express from the original program file or is it possible to reinstall from back up tape.
I know my backup and restore scripts work because I tested them on the server before I do the disaster recovery and rebuild that server from tape.
This is some kind of issue with SQL Server Express being restored by tape backup.
I have used google and searched these forums but haven't found an answer.
Here is my problem:
I have MS SQL 2005 DB I need to backup to tape daily. I want the tape to eject (or unload) when it is complete. I know how to do it with a manual backup (simply check off the option), but there aren't any options I can see with a Maintenance Plan backup. I would rather not do a manual backup EVERY DAY.
I really don't understand why MS makes this so complicated...why would the option be in another area when you use a maintenance plan???
Can we backup our cluster databases directly to tape using native backups (without using any third party tool) ? It's SQL Server 2012 two node Active/Passive cluster. One of the DB will be huge in size, hence checking if we can directly backup from the cluster instance to a tape.
I am using the Simple recovery model and I'm taking a weekly full backup each Monday morning with differentials taken every 4 hours during the day.
On Wednesday afternoon, a programmer ran a process that corrupted the db and I had to restore to the most recent differential. It was 5pm in the afternoon and a differential backup had just occured at 4pm. No problem, I figured.
I restored the full backup from Monday morning and tried to restore the most recent differential backup. The differential restore failed. Since I had used T-SQL for the initial attempt, I tried using Enterprise Manager to try again.
When viewing the backup history, I see my initial full backup taken on Monday plus all the differentials. BUT, on closer inspection, I noticed another full backup in the backup history that was taken early Tuesday morning. I can't figure out where this Tuesday morning full backup came from. It wasn't taken by me (or scheduled by me) and I'm the only one with access to the server. My full backups are usually named something like HCMPRP_20070718_FULL.bak. This erroneous full backup was named something like HCMPRP_03a_361adk2k_dd53.bak. It seemed like it was a system generated name. Not something I would choose. To top it off, I could not find this backup file anywhere on the server and when I tried to restore using this full backup, it failed.
Does anyone have any clues as to where this full backup might come from? Does SQL Server trigger a full backup on its own if some threshold is reached?
I ended up having to restore using the differential taken just before this erroneous full backup and lost a day of transactions.
Guys I was wondering if you can help me figure out the problem with the script.
1) I am getting the following error message on one of the job which is backing up all the databases on the server.
...ges for database 'AdminWorkFlow_Reports', file 'AdminWorkFlow_Reports_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1 pages for database 'AdminWorkFlow_Reports', file 'AdminWorkFlow_Reports_Log' on file 1. [SQLSTATE 01000] (Message 4035) Backup or restore operation successfully processed 433177 pages in 64.328 seconds (55.163 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 113720 pages for database 'BMSRep', file 'BMS_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1 pages for database 'BMSRep', file ' BMS_Log' on file 1. [SQLSTATE 01000] (Message 4035) Backup or restore operation successfully processed 113721 pages in 17.200 seconds (54.162 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 208 pages for database 'EmailAddress', file 'EMailAddress_STGE_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1 pages for database 'EmailAddress', file 'EMailAddress_STGE_Log' on file 1. [SQLSTATE 01000] (Message 4035) Backup or restore operation succe... The step failed.
Not sure where to start. I looked up the backup script it looks fine.
BackUp Database AdminWorkFlow_Reports to Disk = 'q:\AdminWorkFlow_Reports12-17-2007.bak'
-- -- -- --
BackUp Database EmailAddress to Disk = 'q:\EmailAddress12-17-2007.bak'
2)Also I have another script which for some reason doesn't run on some nights. Its enabled and the job is scheduled daily but its not running for about a week.
DECLARE DB_Cursor CURSOR FOR SELECT NAME FROM sysdatabases
OPEN DB_Cursor
FETCH NEXT FROM DB_Cursor INTO @DB_Name
WHILE @@FETCH_STATUS = 0 BEGIN IF @DB_Name <> 'tempdb' AND @DB_Name <> 'model' BEGIN print '--------------------------------<< ' + @db_name + ' >>--------------------------------' SET @Backup_Path = N'd:sql2005backupsightly' + @DB_Name + 'Daily' + '.bak' SET @Backup_Name = @DB_Name + N' backup' BACKUP DATABASE @DB_Name TO DISK = @Backup_Path WITH INIT print '' END FETCH NEXT FROM DB_Cursor INTO @DB_Name END
I have a trans log backup that runs every 15 minutes on san, works fine until I do a backup after a large load. I get the below error message. Anyone had this before?
Executed as user: DPSCSDOMsqlexec. The file on device 'n:sqllogsmdentallgdmp' is not a valid Microsoft Tape Format backup set. [SQLSTATE 42000] (Error 3242) BACKUP LOG is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step fail
My transaction log backup is failing with the following error: Does anyone know how I can fix it? (null) Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.194 Copyright (C) Microsoft Corporation (null) Logged on to SQL Server as 'NT AUTHORITYSYSTEM' (trusted) Starting maintenance plan 'Maint Plan - TLogs' on 5/7/2001 8:18:11 AM Backup can not be performed on database. This sub task is ignored. (null) Thanks