Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Product Support and Discussion

older | 1 | .... | 4 | 5 | (Page 6) | 7 | 8 | .... | 36 | newer

    0 0

    Can you post the restore script?

    0 0

    Used GUI - but, this is in the Activity Log - db name changed for forum posts.


    SQL Backup log file 7.0.5.1

    -SQL "RESTORE DATABASE [ABC_ARCHIVE]
    FROM DISK = '\\servername\foldername\foldername\ABCPROD_FULL_20130109.bak'
    WITH NORECOVERY, DISCONNECT_EXISTING,
    MOVE 'ABCPROD_Data.MDF' TO 'F:\Datafiles\ABC_ARCHIVE_Data.MDF',
    MOVE 'ABCPROD_Log.LDF' TO 'F:\Logfiles\ABC_ARCHIVE_Log.LDF',
    REPLACE "

    0 0

    Did you check this message out? Look for Error trying to Restore DB & Move files with NORECOVERY in this forum. It looks pretty similar.

    HTH

    Chris

    0 0

    If you meant this thread
    http://www.red-gate.com/messageboard/viewtopic.php?t=16340&highlight=restore++move+files+norecovery

    the thread OP got an error. I do not have an error. In fact, the Activity Log reports restore process completed successfully. However, on both SQL Backup and SSMS, that particular database has the status "restoring ...". And it has been there for 2 days; but the SQL Backup suggests the restore completed successfully in about 1 hour and 27 mins.

    0 0

    Have you looked at the actual size of the files after the 'successfull' restore? In this case the files will be allocated and then filled by the backed up data.

    I am sure something will be in the logs that show what has happened.

    Chris

    0 0

    NORECOVERY means it is not available for use. You need to use RECOVERY.

    Chris

    0 0

    Yes I did. The ABC_ARCHIVE database data file is 771GB and log file is 18 GB - which is the same size as the ABCPROD database on the day the backup was taken.

    To rule out the hard disk space (at first I thought it was the hard disk space issue failure); I still have 2.8 Terabytes on that drive where the data & log files are located.

    0 0

    ChrisAVWood wrote:
    NORECOVERY means it is not available for use. You need to use RECOVERY.

    Chris


    I'm going to try restore with recovery.

    0 0

    In the backup wizard, step 3 of 6 under the Backup location section:

    If this is my Folder specification: C:\000\<DATETIME yyyy_mm_dd>\ AND I turn on the "Delete existing backup filies in this folder for the selected databases" will this housekeeping actually work?

    I wonder because the folder name would change everyday... is the program smart enough to search these folders and delete databases that full under its criteria?

    Thanks!
    Mike Murphy

    0 0

    No, SQL Backup won't be able to delete the old files. It only looks in the folder(s) where the current backup file(s) are stored.

    0 0

    Did the RECOVERY option work?
    I am curious.

    Chris

    0 0

    hi. i like it thanks for sharing this site.this is very informative post .

    0 0

    I have SQL Backup with Virtual Restore licensed. I would like to use the SQL Backup extended stored proc to perform a virtual restore but the script shown below always does a full restore.
    Is this possible and if so, can you point-out why the script is bad? It is my impression that .vmdf and .vldf extensions signal a virtual restore.

    DECLARE @ec int
    DECLARE @sec int

    EXECUTE master..sqlbackup '-SQL "RESTORE DATABASE [MyDB_Restored] FROM DISK = ''D:\SQLBackup\MyDB\*.sqb'' SOURCE = ''MyDB''
    LATEST_ALL WITH RECOVERY, DISCONNECT_EXISTING, MOVE ''MyDB_Data'' TO ''F:\SQLDataVirtual\MyDB.vmdf'',
    MOVE ''MyDB_Log'' TO ''F:\SQLDataVirtual\MyDB_Log.vldf'', REPLACE, CHECKDB = ''NO_INFOMSGS, ALL_ERRORMSGS'', DROPDB"', @ec OUT, @sec OUT

    0 0

    I am occasionally getting the error "Warning 130: MOVETO error: Failed to move file....(The file exists.)"

    The log file of the previous log restore reports that the moveto completed successfully.

    Successful restore log file extract:

    06/02/2013 06:54:45: Moved LOG_GAII_Build_20130206064000.sqb to \\ggnas1\SQLBackup\LogShipping\GI\.
    06/02/2013 06:54:45: Restoring GAII_Build_GI (transaction logs) from:
    06/02/2013 06:54:45: E:\Logship\FromGib\LOG_GAII_Build_20130206065000.sqb

    06/02/2013 06:54:45: RESTORE LOG [GAII_Build_GI] FROM VIRTUAL_DEVICE = 'SQLBACKUP_BA3265BC-89A4-47BC-97A4-245F3EE3D10D', VIRTUAL_DEVICE = 'SQLBACKUP_BA3265BC-89A4-47BC-97A4-245F3EE3D10D01', VIRTUAL_DEVICE = 'SQLBACKUP_BA3265BC-89A4-47BC-97A4-245F3EE3D10D02', VIRTUAL_DEVICE = 'SQLBACKUP_BA3265BC-89A4-47BC-97A4-245F3EE3D10D03' WITH BUFFERCOUNT = 24, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , STANDBY = N'E:\SQLBackup\Undo_GAII_Build_GI.dat'

    06/02/2013 06:54:48: Processed 0 pages for database 'GAII_Build_GI', file 'GAII_Primary' on file 1.
    06/02/2013 06:54:48: Processed 0 pages for database 'GAII_Build_GI', file 'Session' on file 1.
    06/02/2013 06:54:48: Processed 0 pages for database 'GAII_Build_GI', file 'AccountJournal' on file 1.
    06/02/2013 06:54:48: Processed 0 pages for database 'GAII_Build_GI', file 'Indexes' on file 1.
    06/02/2013 06:54:48: Processed 0 pages for database 'GAII_Build_GI', file 'CLUSINDEXES' on file 1.
    06/02/2013 06:54:48: Processed 0 pages for database 'GAII_Build_GI', file 'TextAndBlob' on file 1.
    06/02/2013 06:54:48: Processed 0 pages for database 'GAII_Build_GI', file 'HEAP' on file 1.
    06/02/2013 06:54:48: Processed 305 pages for database 'GAII_Build_GI', file 'GAII_build_log' on file 1.
    06/02/2013 06:54:48: RESTORE LOG successfully processed 305 pages in 0.093 seconds (25.584 MB/sec).

    [b]06/02/2013 06:54:48: Moved LOG_GAII_Build_20130206065000.sqb to \\ggnas1\SQLBackup\LogShipping\GI\.[/b]


    Subsequent log file extract:
    06/02/2013 07:04:01: Restoring GAII_Build_GI (transaction logs) from:
    06/02/2013 07:04:01: E:\Logship\FromGib\LOG_GAII_Build_20130206065000.sqb

    06/02/2013 07:04:01: ALTER DATABASE [GAII_Build_GI] SET ONLINE RESTORE LOG [GAII_Build_GI] FROM VIRTUAL_DEVICE = 'SQLBACKUP_8912C898-F5B2-4A1E-BB96-7700CA896065', VIRTUAL_DEVICE = 'SQLBACKUP_8912C898-F5B2-4A1E-BB96-7700CA89606501', VIRTUAL_DEVICE = 'SQLBACKUP_8912C898-F5B2-4A1E-BB96-7700CA89606502', VIRTUAL_DEVICE = 'SQLBACKUP_8912C898-F5B2-4A1E-BB96-7700CA89606503' WITH BUFFERCOUNT = 24, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , STANDBY = N'E:\SQLBackup\Undo_GAII_Build_GI.dat'

    06/02/2013 07:04:45: Processed 0 pages for database 'GAII_Build_GI', file 'GAII_Primary' on file 1.
    06/02/2013 07:04:45: Processed 0 pages for database 'GAII_Build_GI', file 'Session' on file 1.
    06/02/2013 07:04:45: Processed 0 pages for database 'GAII_Build_GI', file 'AccountJournal' on file 1.
    06/02/2013 07:04:45: Processed 0 pages for database 'GAII_Build_GI', file 'Indexes' on file 1.
    06/02/2013 07:04:45: Processed 0 pages for database 'GAII_Build_GI', file 'CLUSINDEXES' on file 1.
    06/02/2013 07:04:45: Processed 0 pages for database 'GAII_Build_GI', file 'TextAndBlob' on file 1.
    06/02/2013 07:04:45: Processed 0 pages for database 'GAII_Build_GI', file 'HEAP' on file 1.
    06/02/2013 07:04:45: Processed 305 pages for database 'GAII_Build_GI', file 'GAII_build_log' on file 1.
    06/02/2013 07:04:45: RESTORE LOG successfully processed 305 pages in 0.123 seconds (19.344 MB/sec).

    [b]06/02/2013 07:04:46: Warning 130: MOVETO error: Failed to move file: E:\Logship\FromGib\LOG_GAII_Build_20130206065000.sqb (The file exists.)
    [/b]

    Is there anyway to make the MOVETO overwrite an existing file, or having an error reported if the delete part of the move does not complete successfully?

    0 0

    Quote:
    Is there anyway to make the MOVETO overwrite an existing file

    Use FILEOPTIONS = 4, e.g.

    Code:
    EXEC master..sqlbackup '-sql "RESTORE ... WITH MOVETO = ..., FILEOPTIONS = 4"'


    Quote:
    having an error reported if the delete part of the move does not complete successfully?

    It isn't possible currently. Windows reports that the move succeeded, but SQL Backup does not actually check if the source file still exists.

    0 0

    Thank you for this information Petey.

    It's worth noting that this information is not included in the documentation for the RESTORE command, this states the for FILEOPTIONS: Valid values are 1, 2, and 3.

    0 0

    Hi,

    We have a daily log restore to a secondary database. For one reason or another, we have problems getting all the user connections to be automatically disconnected before the restore starts and so sometimes we get the restore failing with the error 1010 "could not get exclusive access to the database".

    The weird thing is, the restore log attempts to start at 9.30pm, but it takes all the way until 4.15am before the job actually fails. It seems that redgate doesn't realize for 7 hours that it can't start the restore.

    Why does it take so long for it to report a failure?

    It's kind of a bummer because if it failed within 20mins of starting, I would still be awake to manually restart it!

    Any thoughts? I'm actually using SQL Backup 6.5 (sorry i know this is the SQL 7 forum - couldn't see one for 6.5).

    Thanks,

    Reinis

    0 0

    There should be no need to call the SQL Backup extended stored procedure because the Hyperbac service should be able to handle .sqb extension of SQL Backup.

    The only difference would be that multi-threaded SQL Backup backups are handled by repeating the DISK parameter in the RESTORE command, once for each thread used during the backup process.

    Here is an example for a .sqb file with a thread count of 3

    RESTORE DATABASE [WidgetProduction_Virtual] FROM
    DISK=N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Backup\FULL_SQL2008R2_WidgetProduction_20120430_133003.sqb',
    DISK=N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Backup\FULL_SQL2008R2_WidgetProduction_20120430_133003.sqb',
    DISK=N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Backup\FULL_SQL2008R2_WidgetProduction_20120430_133003.sqb'
    WITH MOVE N'WidgetProduction' TO N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Data\WidgetProduction_WidgetProduction_Virtual.vmdf',
    MOVE N'WidgetProduction_log' TO N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Data\WidgetProduction_log_WidgetProduction_Virtual.vldf',
    NORECOVERY, STATS=1
    GO
    RESTORE DATABASE [WidgetProduction_Virtual] WITH RECOVERY
    GO

    0 0

    Thanks for the response.

    I reason I opted for the extended sp is because it accepts "...\*.sqb" and then figures out which files (full or full+diff) and the number of threads used, which is not a simple thing!

    So are you saying that there is no way to do a virtual restore via the extended sp?

    0 0

    Thanks for the forum post.

    The virtual restore extensions can only be used with a native TSQL Restore syntax. You are currently using the SQL Backup restore syntax. That's why the script is not work for SVR. The extensions are being ignored by hyperbac when you try any other syntax. Within current syntax SQL Backup is just doing a normal restore.

older | 1 | .... | 4 | 5 | (Page 6) | 7 | 8 | .... | 36 | newer