InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 12:52:55 GMT20http://www.sqlservercentral.com/Forums/Topic1380263-384-1.aspxHiIf speed is the issue, then use the right tools, right? Research VDI. In my experience writing from VDI device connected to a seperate server hosting the backup file was 80% faster than not using VDI.Keep an eye on the log files. When the db is restored, and it's created as the default size, when the restore happens and you have a 100GB log file the OS will create a file sized 100GB and format it to be available for the database.Better ways?Fri, 16 Nov 2012 04:45:39 GMTAlocytehttp://www.sqlservercentral.com/Forums/Topic1380263-384-1.aspxThe advice above on differentials is correct. One other note, please keep all log backups for all full backups. There is always a possibility that your latest full backup does not work and you go back two days to 8pm. Then you would restore all log backups since then.I can only speak for Red Gate tools, but our SQL Backup supports object recovery and we have an Object Level Recovery tool. ([url]http://www.red-gate.com/products/dba/sql-backup/[/url]). Disclosure, I work for Red Gate.Fri, 02 Nov 2012 09:56:01 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic1380263-384-1.aspxyou can schedule Differential backup according to your environment ,it can reduces your restore steps.2. No ,you can not ..not sure if any third party tool available for it. for table backup you can useselect * into backup_table from original_tableFri, 02 Nov 2012 05:34:20 GMTsanket kokanehttp://www.sqlservercentral.com/Forums/Topic1380263-384-1.aspxScenario:I have Databases which are backed up every night (Full Backup); the Backups are saved on a Tape then deleted from the Sever after three days. 1.The Backups are taken at 8pm the previous day and if something goes wrong, for example at 4ppm the next day I would have to Restore the last Backup then rerestorell the Log files since the last Backup (The Log Backups are done every 15 minutes), imagining the Database will need to be Back online as soon as possible; the procedure will take a very long time.I wanted to know if there is a better way of performing a Disaster Recovery other than the following Procedure: RESTORE DATABASE DB_TestLSN_RestoreFROM DISK = 'c:\Backup\DB_TestLSN.bak'WITH MOVE 'DB_TestLSN' TO 'E:\MSSQL\DATADB_TestLSN_Restore.mdf',MOVE 'DB_TestLSN_log' TO 'F:\MSSQL\LOG\DB_TestLSN_log_Restore.ldf',NORECOVERY, NOUNLOAD, STATS = 10GORESTORE LOG DB_TestLSN_RestoreFROM DISK = N'C:\Backup\DB_TestLSN_LOG1'WITH NORECOVERY, NOUNLOAD, STATS = 10GORESTORE LOG DB_TestLSN_RestoreFROM DISK = N'C:\Backup\DB_TestLSN_LOG2'WITH RECOVERY, NOUNLOAD, STATS = 10GOAnd so on until the last log is Restored.2. Is there a way, if possible just to restore a single table if for example something gets deleted or if the table becomes corrupted?Thank you in advance!Fri, 02 Nov 2012 04:37:17 GMTtt-615680