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...
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.
Hello,
I need to backup the database to file and then copy it to Tape. Can anyone guide me how I should do it. I need to automate it.
Thanks.
Rea
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?
View 2 Replies View RelatedHi Folks,
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.
Thanks Folks
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
View 2 Replies View RelatedI'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
View 11 Replies View RelatedHello,
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.
Can you please give me some help on this one ?!
Thank you all.
Youss
Hello,
TSQL command works fine,
C:SQLCMD
1> BACKUP DATABASE TestDB TO TAPE = '\.Tape0'
2> GO
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.
Hello!
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 :-)
Hi,
How do we know that tape backups is working. And how do we know what is on them.
dindu
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
How much time does a 20 g tape backup take to recovery
I am on 6.5 sql and have compacq 15/30 gb DLT
How best to configure a standby sqk 2000 server
salim
__________________
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?
thx
Des
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
View 6 Replies View RelatedHi
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 ?!?
Regards
Jasper
Need help.
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 .
Please help
Thanks
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 **
View 1 Replies View RelatedI 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..
View 1 Replies View RelatedI 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.
Hello,
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: Error
Event Source: MSSQL$SQLEXPRESS
Event Category: (2)
Event ID: 3411
Date: 9/15/2006
Time: 8:16:36 AM
User: N/A
Computer: COPLEYNEWS
Description:
Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
Data:
0000: 53 0d 00 00 15 00 00 00 S.......
0008: 16 00 00 00 43 00 4f 00 ....C.O.
0010: 50 00 4c 00 45 00 59 00 P.L.E.Y.
0018: 4e 00 45 00 57 00 53 00 N.E.W.S.
0020: 5c 00 53 00 51 00 4c 00 .S.Q.L.
0028: 45 00 58 00 50 00 52 00 E.X.P.R.
0030: 45 00 53 00 53 00 00 00 E.S.S...
0038: 00 00 00 00 ....
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.
Any suggestions, thanks.
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???
Thanks for replys!!!
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.
View 7 Replies View RelatedCurrently we are running a full backup on Fridays and differentials monday through thursday. With the Logs being truncated. we are using Veritas 10d with a 5 tape auto loader.
As far as recovery goes will this be sufficient?
we have about 40 users doing normal work hours.
My main concern is the transaction logs and making sure that I will be able to recover my data.
also we do not have an open file option and cannot do backups during the day, only at night.
Thanks in advance :D
Backup Log ..... with no_truncate -- How to get it to work.
Applicable to SQL Server 7.0 Date 8/14/00 andrews_gary_w@solarturbines.com
Introduction to the "Backup Log
.with no_truncate" feature of SQL Server 7.0.
On occasion a database may become corrupt or a database file may be inaccessible. Ideally, in these cases you want to be able to restore and recover the data back to the current point in time.
This requires that the Transaction Log be backed up prior to the restore process beginning.
Microsoft has provided the "Backup Log
with no_truncate" feature for use in cases such as this. However, this feature works only under very specific conditions and thus is the topic of this document.
Background.
When a database is defined, it always has a primary file group. In some cases this may be the only file group defined for the database. The primary filegroup contains, at a minimum, the system tables for the database being defined. The systems tables hold metadata describing the database. Where no other filegroups have been defined, the primary file group will also contain the user defined tables/indexes.
Essential requirement
"Backup Log
with no_truncate" must be able to access the "metadata" located in the primary file group, or it will not work. This also means that this part of the database must not be corrupt or that the file containing this part of the database must not be inaccessible.
Specific conditions required for "Backup Log
.. with no_truncate" to work.
a. The database needs to be defined so that the user tables/indexes are contained in one or more file groups other than the primary filegroup.
b. Logging of changes to the database must be in effect.
c. A full backup must exist
d. Changes are made (logged) to the user database.
e. No non-logged operations must have been performed since the last full backup.
f. The primary filegroup file(s) must be available.
g. The primary filegroup data must not be corrupted. Or at least the portion needed by the backup operation must not be corrupted. I am not 100% sure about this issue.
h. The data in the filegroups other than primary may be corrupted or these files may be completely missing.
Process to restore/recover.
a. When problem detected (data file(s) inaccessible or database is corrupted), if primary filegroup is accessible, then perform the Backup Log
. with no_truncate.
b. Then perform the restore process using the "with replace" option for the database. This will get back any missing file(s) and recover you right up to when the last log backup was taken.
c.Post restore/recover process, your database will not be corrupt or missing any data file(s)
Bottom line
To achieve maximum recoverability, the following is recommended.
a. Define databases so that user data is not put in the primary file group.
i.e. Define not only a primary filegroup, but also one or more "other" filegroups.
b. Place user data in the "other" filegroup(s), NOT in the primary filegroup.
c. Place the primary filegroup on a disk drive separate from the "other" filegroup(s).
d. Place the log on a disk drive by itself.
Under the above scenario, at least three different disk drives would be needed to accommodate a single database.
Some sources recommend you put the primary file group and the transaction log on the same disk drive (mirrored). This would of course reduce the maximum number of disks needed to two. This topic, from my perspective, is another issue to be separately addressed and thus is not covered any further in this document.
Remember, even if the database files are isolated as recommended above:
a. Should the primary filegroup file(s) be inaccessible, then the Backup Log
. with no_truncate option will not work.
b. Should the primary filegroup file(s) be corrupt, then depending on where the corruption is determines whether or not the Backup Log
.. with no_truncate option will work.
I have been unsuccessful in getting the Backup Log with
No Truncate option to work.
Any tips, tricks, suggestions, etc., would be appreciated.
Thanks!!!
i know this topic has been covered and i've searched but i can't find the answer.
-SQL server is a diffrent server than my backup server
-i've installed the sql agent option on the backup exec server
-i've installed the client network utility on the remote server
the backup server doesn't see the SQL server databases. any thoughts
could it be a security issue?
thanks!
Hello everybody,
I have run into some problems with logfiles and backup logfiles (MS SQL server). I have read much about them but uptil now I dont seem to grasp how it works. Specially the part of working with backup log files.
Can someone please help me with this?
What I want todo is to create backup log files, so I can restore the database to any point in time before a failure occured. But using this method create's a problem with the backup log files. They get very big.
So how can I use backup log files without getting to large backup log files?
How can I shrink on a regular basis the backup log files and still be able to restore the database?
Please help.
Best regards,
Marc Janssen,
:)