SQL Server Backup Options

Restore your full backup, then run a few queries before you keep restoring transaction logs. Brent shows how to use the Standby option for restores.

In this five minute video, Brent demonstrates how to do it by creating a database, populating data, and then showing what disaster recovery is like by doing RESTORE WITH STANDBY.

Examine the powerful platform of SharePoint Server 2007 search for the end user and developer. Learn about the built-in Web Parts for search and writing search queries for your applications.

Win 2003, SQL 2005/SQL2008 64 bit enterprise failover cluster with 3 nodes and 6 instances. The mount points configured as cluster resources for the data/backup/logs. The entire cluster mount points are SAN replicated to a DR Site. But backup drives/LUNs are excluded from the replication. All the disk resources including backup LUNs are set to dependencies on the SQL Server server. The SQL Server is not coming on-line in the DR Site due to unavailability of the backup LUNs (failed resources). As per the documentation all the disk resources must be set to dependencies (http://support.microsoft.com/kb/835185). Thought it did not specifically mentions only Data/Log mount points and/or the backup LUNs as well. "The SQL Server 2005 resource depends on the SQL network name resource and the physical disk resources that hold its data. When mount points are being used together with the physical disks, each mount point must appear as a cluster resource. Additionally, each mount point must also be added as a SQL Server dependency. If only the root physical disks dependency is added and the mount points are not added, database corruption will occur on failover. Database corruption may also occur when SQL Server is restarted without failing over. "     What if I remove the backup LUNs from dependencies list. This will allow me to recover the SQL Server

Hi I have a server which is not backing up a db each day. When I look at the event log it displays the following...   SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\########\########_File_CS_DefaultData.ndf] in database [########] (5). The OS file handle is 0x000006A0. The offset of the latest long I/O is: 0x00000008e00000 2010-08-16 16:07:38.19 Backup Error: 3203, Severity: 16, State: 1. 2010-08-16 16:07:38.19 Backup Read on "D:\########\########_File_CS_DefaultData.ndf" failed: 1117(failed to retrieve text for this error. Reason: 15100) 2010-08-16 16:07:38.20 Backup Error: 3041, Severity: 16, State: 1. 2010-08-16 16:07:38.20 Backup BACKUP failed to complete the command BACKUP DATABASE ########. Check the backup application log for detailed messages. 2010-08-16 16:12:14.32 spid5s SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\########\########_File_CS_DefaultData.ndf] in database [########] (5). The OS file handle is 0x000006A0. The offset of the latest long I/O is: 0x00000009900000 2010-08-16 16:13:07.02 Backup Error: 3203, Severity: 16, State: 1. 2010-08-16 16:13:07.02 Backup Read on "D:\########\########_File_CS_DefaultData.ndf" failed: 1117(failed to retrieve text for this error. Reason: 15105) 2010-

I have a SQL Server 2005 database that contains 3 files.  Sometimes when I run rhe backup, it appears to only backup 2 of the three files.  The only way I can get it to return to a full backup is to restore the database from a backup tape.

To verify if the "2008 R2" version can be restored back to a "2008" dbserver I make an experiment:  construct a database on R2 version ( version : 10.50.xxx )  and backup it; then I try to restore the db backup to a "sql server 2008" db-server ( version : 10.0.xxx ) but get failed. Error message is as shown: The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.2531. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.   Originally I want to upgrade a "2008" server to "2008 r2" , but this problem withdraws me: if I do so , I am afraid all the existing clientuser's dbs cannot be backed up to themselves if they don't have "2008 r2" locally:   if a database is backed up under "2008 r2" environment whereas client user only has "2008" db server, does it mean he cannot restore it anymore?   So I wonder if there is an approach that helps me to create a "backward-compatible" database; when creating database on wizard there is an option to choose "compatibility level" but I don't think it meets my requirement..    Anyone can help me on this ??    

VERY IMPORTANT i am trying to restore database.bak in sql server 2005 (i know the database.bak was also generated in sql 2005 server) i am trying to restore back up database .bak into the new database i just created in sql server 2005 i have saved my database .bak into c drive and when i select database .bak "From Device", it doesn't get populated in the list below and i see nothing and it keeps on prompting a message "You must select a restore source" Here's the screen shot:   PLEASE HELP..it's really important (i tried restoring database in sql server 2008 and it was sucessful but i am facing this problem in sql server 2005 only)  

I have a SQL Server 2008 R2 instance that I need to backup and restore onto a SQL 2008 instance. When I attempt to restore the back up (.bak) database from the R2 SQL server onto the SQL 2008 server I get the following message: The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.2531. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.Smo) How can i backup the SQL 2008 R2 database to be compatible with SQL 2008?Ian Ceicys

I have a 2008R2 server that does AD, sharepoint and file shares.  What I need to have to is if the main server goes offline a second server pick up where it left off. What is the a good solution for me?   Thanks

I have several databases that, despite being backed up regularly, do not release space to the operating system.  In one extreme case, I have a log file that is less than 1% utilized (and has been for months.) I know how to manually force a shrink, but I should not need to do that on any sort of regular basis.  In fact, it is against best practices to manually shrink a log file (or any database file for that matter) because of the very high risk of an unrecoverable error. It is my understanding that SQL Server will eventually handle these things on its own.  However, it does not appear to be doing so.  Any thoughts as to why? Thanks, Dave

our application uses the SQL server 2008 compact edition and entity framework. The application will control the instrument. It may run for several days before it stops. In order to protect the database crash (database failure), we plan to backup SQL compact database during running. Can we backup or duplicate the ~.sdf when application is running? Is there any SQL server command we can call inside the application to achive the backup? Or we only can backup the database when application is not running. thx!  

After installing the trial version of Sharepointn 2010 I wanted to restore my Sharepoint 2007 sites to it but received the following error:  "The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space." I went on to create a new content database in sharepoint 2010 but it still did not work. The old database i.e the one used by the sharepoint 2007 server is SQL 2005. During the installation of the sharepoint 2010 version I selected SQl Server Express for the database. Is there any specifics for migrating from MOSS 2007 to sharepoint 2010? Thanks for helping

I want to retire a Windows 2003 Standard server (named Meton) running Sharepoint 3.0 and transfer its entire database in a transparent manner (I want it to be exactly like it is on the old server) to a 2008 R2 standard guest partitian. I have sucessfully backup up the old server using both the operations tab of the web GUI and this bat file: cd\ cd Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN stsadm -o backup -url http://meton.pond_rd.wtpsmercer.k12.nj.us -directory D:\Wholesite -backupmethod full -percentage 10 -backupthreads 3 pause Both worked. Giving credit where due both this and the import bat were derived from information on http://www.epnetworking.com/blog/?p=179. Attempting to import with the GUI produced nothing. Then I ran this bat: c: cd\ cd Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN stsadm -o restore -hostheaderwebapplicationurl http://sharepoint.pond_rd.wtpsmercer.k12.nj.us -directory C:\ -restoremethod new -username xxxxxx -password xxxxxx -newdatabaseserver sql2008 pause   Despite the information on technet that stsadm is not interactive there are a series of questions and it would not let me choice the default database name, see below. Verbose: Adding WSS_Administration to Restore list. Verbose: Adding Web Application to Restore list. Verbose: Adding SharePoint_AdminContent_c829909f-fe1e-48d8-8649

I get the following error when this perl script tries to backup the database using ASCMD.exe 2008 command line tool

<return xmlns="urn:schemas-microsoft-com:xml-analysis"><root xmlns="urn:schemas-
microsoft-com:xml-analysis:empty"><Exception xmlns="urn:schemas-microsoft-com:xm
l-analysis:exception" /><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:
exception"><Error ErrorCode="3239313412" Description="Errors in the metadata man
ager. Either the database with the ID of &#39;xyz_old&#39; does not exi
st in the server with the ID of &#39;ABCD\Sql_AS&#39;, or the user doe
s not have permissions to access the object." Source="Microsoft SQL Server 2008
Analysis Services" HelpFile="" /></Messages></root></return>

I have tried using different account for impersonation but everything fails.

Any help would be really appreciated.

Thanks.

all I have a beefy server that currenty runs my SQL server, however i would like to backup this server and restore it to a different server then use SQL replication in a DR solution.

Details:

I have W3K R2 SP1 with SQL 2005 (version 9.00.3042.00)
The phycial server has:
DISK 0 - C: (conatins OS and system files 12GB)
and E: (conatins SQL logs 124GB)

DISK 1 - D: (some program files, and the SQL DB 408GB) - Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

all DISK's are NTFS formatted

How can I best accomplish my goal?

Should I use NTBACKUP and then do a restore onto a new server?
Should I build a new sever with W3KR2 with the same partitions and then backup the sql db via sql and do a restore onto the new server?
could I utilise hyper-v?

I do not have much experience with MS SQL server.

MCSE, MCTS 

I have a Sharepoint 2010 server running SQL Express. (SERVER A)     I have an identically configured Sharepoint 2010 server running SQL Express (SERVER B).   I want to migrate the data from SERVER A to SERVER B.   Does anyone out there have a step by step guide for this?

During logshipping, job on secondary server is ran successfully BUT give this information

"Skipping log backup file since load delay period has not expired ...."

What is this "Load delay period" ? Can we configure this somehow, somewhere ?

NOTE : The value on "Restore Transasction Log tab", Delay Restoring backups at least = Default (zero minutes)

Thanks

---

Think BIG but Positive, may be GLOBAL better UNIVERSAL.