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

(Page 1) | 2 | 3 | .... | 36 | newer

    0 0

    Could you please run the following on the SQL Server instance that you are taking the backups on

    Code:
    SELECT * FROM msdb..backupset WHERE database_name = 'model'
      AND backup_start_date >= '2012-12-03 03:00' AND backup_finish_date <= '2012-12-03 03:05'

    and post the results. Thanks.

    0 0

    Hi petey,

    Here is the results (hope it helps, but it shows nothing):

    backup_set_id backup_set_uuid media_set_id first_family_number first_media_number last_family_number last_media_number catalog_family_number catalog_media_number position expiration_date software_vendor_id name description user_name software_major_version software_minor_version software_build_version time_zone mtf_minor_version first_lsn last_lsn checkpoint_lsn database_backup_lsn database_creation_date backup_start_date backup_finish_date type sort_order code_page compatibility_level database_version backup_size database_name server_name machine_name flags unicode_locale unicode_compare_style collation_name is_password_protected recovery_model has_bulk_logged_data is_snapshot is_readonly is_single_user has_backup_checksums is_damaged begins_log_chain has_incomplete_metadata is_force_offline is_copy_only first_recovery_fork_guid last_recovery_fork_guid fork_point_lsn database_guid family_guid differential_base_lsn differential_base_guid compressed_backup_size
    ------------- ------------------------------------ ------------ ------------------- ------------------ ------------------ ----------------- --------------------- -------------------- ----------- ----------------------- ------------------ -------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ---------------------- ---------------------- ---------------------- --------- ----------------- --------------------------------------- --------------------------------------- --------------------------------------- --------------------------------------- ----------------------- ----------------------- ----------------------- ---- ---------- --------- ------------------- ---------------- --------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ----------- -------------- --------------------- -------------------------------------------------------------------------------------------------------------------------------- --------------------- ------------------------------------------------------------ -------------------- ----------- ----------- -------------- -------------------- ---------- ---------------- ----------------------- ---------------- ------------ ------------------------------------ ------------------------------------ --------------------------------------- ------------------------------------ ------------------------------------ --------------------------------------- ------------------------------------ ---------------------------------------

    (0 row(s) affected)

    0 0

    Strange, it should at least have a record of the backup made of the 'model' database made on that date. Is your instance set up to delete backup history details older than 2 days?

    0 0

    Pete,

    Your note had said 'It then waits 30 seconds for SQL Server to respond' when it could wait for up to a maximum of 30 seconds as this is the default for DISKRETRYINTERVAL. I am not trying to be pickey.

    Chris

    0 0

    Hi Peter,

    My mistake. here's the info:
    ------------------------------

    backup_set_id backup_set_uuid media_set_id first_family_number first_media_number last_family_number last_media_number catalog_family_number catalog_media_number position expiration_date software_vendor_id name description user_name software_major_version software_minor_version software_build_version time_zone mtf_minor_version first_lsn last_lsn checkpoint_lsn database_backup_lsn database_creation_date backup_start_date backup_finish_date type sort_order code_page compatibility_level database_version backup_size database_name server_name machine_name flags unicode_locale unicode_compare_style collation_name is_password_protected recovery_model has_bulk_logged_data is_snapshot is_readonly is_single_user has_backup_checksums is_damaged begins_log_chain has_incomplete_metadata is_force_offline is_copy_only first_recovery_fork_guid last_recovery_fork_guid fork_point_lsn database_guid family_guid differential_base_lsn differential_base_guid compressed_backup_size
    ------------- ------------------------------------ ------------ ------------------- ------------------ ------------------ ----------------- --------------------- -------------------- ----------- ----------------------- ------------------ -------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ---------------------- ---------------------- ---------------------- --------- ----------------- --------------------------------------- --------------------------------------- --------------------------------------- --------------------------------------- ----------------------- ----------------------- ----------------------- ---- ---------- --------- ------------------- ---------------- --------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ----------- -------------- --------------------- -------------------------------------------------------------------------------------------------------------------------------- --------------------- ------------------------------------------------------------ -------------------- ----------- ----------- -------------- -------------------- ---------- ---------------- ----------------------- ---------------- ------------ ------------------------------------ ------------------------------------ --------------------------------------- ------------------------------------ ------------------------------------ --------------------------------------- ------------------------------------ ---------------------------------------
    1899 4C38B831-DBF6-45C7-BD01-540D813D6F88 1899 1 1 3 1 1 1 1 NULL 4608 Database (model), 12/1/2012 3:00:01 AM Backup on 12/1/2012 3:00:01 AM Server: VM-HDCSQLPROD06 Database: model ATG\sqlagent 10 50 2500 -20 0 27000000043100037 27000000044700001 27000000043100037 27000000040900037 2003-04-08 09:13:36.000 2012-12-01 03:00:01.000 2012-12-01 03:00:01.000 D 52 0 100 661 3705856 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 3705856
    1902 D7AE1DAB-AD8C-4380-B21F-BAD70DE45477 1902 1 1 1 1 1 1 1 NULL 4608 model_backup_2012_12_01_030002_0986891 NULL ATG\sqlagent 10 50 2500 -20 0 27000000045300037 27000000046900001 27000000045300037 27000000043100037 2003-04-08 09:13:36.000 2012-12-01 03:00:26.000 2012-12-01 03:00:35.000 D 52 0 100 661 1396736 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 1396736
    1942 D2C70A39-1DCA-4BB6-BA0B-D3FD7891C7AD 1942 1 1 3 1 1 1 1 NULL 4608 Database (model), 12/2/2012 3:00:00 AM Backup on 12/2/2012 3:00:00 AM Server: VM-HDCSQLPROD06 Database: model ATG\sqlagent 10 50 2500 -20 0 27000000047500037 27000000049100001 27000000047500037 27000000045300037 2003-04-08 09:13:36.000 2012-12-02 03:00:01.000 2012-12-02 03:00:01.000 D 52 0 100 661 3705856 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 3705856
    1945 1846DC42-3741-4CFC-9B41-F5B923F1F148 1945 1 1 1 1 1 1 1 NULL 4608 model_backup_2012_12_02_030002_0026109 NULL ATG\sqlagent 10 50 2500 -20 0 27000000049700037 28000000001700001 27000000049700037 27000000047500037 2003-04-08 09:13:36.000 2012-12-02 03:00:06.000 2012-12-02 03:00:06.000 D 52 0 100 661 1463296 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 1463296
    1985 CC7315AC-1EE3-4928-A6DE-2C1356550026 1985 1 1 3 1 2 1 1 NULL 4608 Database (model), 12/3/2012 3:00:00 AM Backup on 12/3/2012 3:00:00 AM Server: VM-HDCSQLPROD06 Database: model ATG\sqlagent 10 50 2500 -20 0 28000000002300037 28000000003900001 28000000002300037 27000000049700037 2003-04-08 09:13:36.000 2012-12-03 03:00:00.000 2012-12-03 03:00:01.000 D 52 0 100 661 3705856 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 3705856
    1988 D930D6C2-EF1A-47F5-8611-0820F679DDE8 1988 1 1 1 1 1 1 1 NULL 4608 model_backup_2012_12_03_030002_2245378 NULL ATG\sqlagent 10 50 2500 -20 0 28000000004500037 28000000006100001 28000000004500037 28000000002300037 2003-04-08 09:13:36.000 2012-12-03 03:00:19.000 2012-12-03 03:00:24.000 D 52 0 100 661 1396736 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 1396736
    2028 EFEC36FB-E122-48F9-B055-A480A9B314F6 2028 1 1 3 1 1 1 1 NULL 4608 Database (model), 12/4/2012 3:00:01 AM Backup on 12/4/2012 3:00:01 AM Server: VM-HDCSQLPROD06 Database: model ATG\sqlagent 10 50 2500 -20 0 28000000006700037 28000000008300001 28000000006700037 28000000004500037 2003-04-08 09:13:36.000 2012-12-04 03:00:01.000 2012-12-04 03:00:01.000 D 52 0 100 661 3705856 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 3705856
    2031 6F180032-98EC-4858-B554-D501C718B83C 2031 1 1 1 1 1 1 1 NULL 4608 model_backup_2012_12_04_030002_7434868 NULL ATG\sqlagent 10 50 2500 -20 0 28000000008900037 28000000010500001 28000000008900037 28000000006700037 2003-04-08 09:13:36.000 2012-12-04 03:00:13.000 2012-12-04 03:00:17.000 D 52 0 100 661 1396736 model VM-HDCSQLPROD06 VM-HDCSQLPROD06 512 1033 196609 SQL_Latin1_General_CP1_CI_AS 0 FULL 0 0 0 0 0 0 0 0 0 0 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 90D16058-F1D1-4E96-8EC6-8D7BFDA42F15 NULL EBD0FE66-F91F-43F1-99C3-B52D803BB136 EBD0FE66-F91F-43F1-99C3-B52D803BB136 NULL NULL 1396736

    (8 row(s) affected)

    0 0

    The results show that only one backup was performed by SQL Backup each day, though there seemed to be another native backup performed by SQL Server after each SQL Backup backup.

    At this point, I don't know how the backup file got copied to the network share, before SQL Backup attempted to copy it over. We used to have a tool named CopyTool, that was a standalone application to copy backup files outside of SQL Backup. Do you happen to be using this tool, or another third-party app (Robocopy, Syncback etc), to copy the backup files?

    0 0

    My apologies for the confusion. Yes, that sentence should have been 'waits up to 30 seconds for SQL Server to respond'. Thanks for pointing that out.

    0 0

    It looks like this is a known problem with SQL 2012:

    http://connect.microsoft.com/SQLServer/feedback/details/737341/sql-server-2012-openrowset-on-msdb-dbo-sp-help-job-throws-error

    There's a few workarounds listed there - does anything there help?

    0 0

    petey wrote:
    You will need to use SQL Backup if you want to restore directly from those files.

    The alternative is to first convert those files to native SQL Server backup files using the SQBConverterGUI or SQBConverter applications (found in the SQL Backup installation folder), then use SQL Server to restore using those converted files.



    Thanks Petey. BTW - I did try and find this info first but could not. Is this restriction mentioned naywhere in the SQL Back documentation? What about any mention of the 2 applications you mentioned, SQBConverterGUI & SQBConverter ?

    0 0
  • 12/07/12--11:53: Exclude Databases option
  • Hi
    I scheduled a backup job using the EXCLUDE OPTION to set aside thos databases i don't need to regularly backup.... Job is running well without any problems

    Our SQL Server manages hundreds of databases some of which don't need to be backed up (demo databases) and therefore are excluded. If a DB is no longer required it is manually excluded from the respective backup jobs.

    Question: How does SQL Backup keep track of the Databases that are backed up?. Is this list stored at some location?
    I'm looking for a way to automatically exclude a database when it's no longer required to be backed up and update the job accordingly. Deleting the datase obviously would solve it but not a good alternative

    Thanks in advanced

    0 0
  • 12/07/12--17:30: RE: Exclude Databases option
  • Each time a backup is ran with the EXCLUDE option, SQL Backup retrieves a list of active databases from SQL Server. It then removes the excluded databases from that list, then proceeds to back up the remaining databases.

    You would need to maintain the exclusion list yourself, and add modify the SQL Backup command accordingly. Perhaps the following code snippet might provide some hints on how to do this:

    Code:
    CREATE TABLE SQBTEST_DBsToExclude (db nvarchar(128))
    GO
    INSERT INTO SQBTEST_DBsToExclude VALUES ('db1')
    INSERT INTO SQBTEST_DBsToExclude VALUES ('db2')
    INSERT INTO SQBTEST_DBsToExclude VALUES ('db3')
    INSERT INTO SQBTEST_DBsToExclude VALUES ('db4')
    INSERT INTO SQBTEST_DBsToExclude VALUES ('db5')
    GO

    DECLARE @cmd NVARCHAR(MAX)
    DECLARE @dblist NVARCHAR(MAX)

    SET @dblist =
    (SELECT TOP 1
     SUBSTRING(
     (
      SELECT ( ', ' + db)
      FROM SQBTEST_DBsToExclude t1
      FOR XML PATH('')
     ), 3, 2048)
    FROM SQBTEST_DBsToExclude)

    SET @cmd = '-sql "BACKUP DATABASES EXCLUDE [' + @dblist + '] TO DISK = [<AUTO>]"'
    SELECT @cmd
    -- EXEC master..sqlbackup @cmd

    0 0

    I don't know if this 'restriction' is mentioned anywhere in the documentation. If you need a version of SQL Backup to only restore databases, you could contact the Red Gate sales department for options.

    With regards to the conversion applications, it's under 'Tools & Utilities > SQL Backup File Converter'.

    0 0

    I am trying to script this and it is not working, keeps saying I have an extra '

    SET @SQL = ' EXECUTE master..sqlbackup ''-SQL "RESTORE DATABASE ' + @sitename +
    ' FROM DISK = ''''D:\SQLVMDEV10\' + @sitename + '\FULL\*.sqb'''' WITH MOVE DATAFILES TO ''''G:\VirtualRestore'''' , SOURCE = ''''' + @sitename + ''''' LATEST_FULL WITH MAILTO = ''ed.watson@swfwmd.state.fl.us',
    RECOVERY, DISCONNECT_EXISTING,
    MOVE LOGFILES TO ''''G:\VirtualRestore'''' , REPLACE , CHECKDB = ''ALL_ERRORMSGS, DATA_PURITY, EXTENDED_LOGICAL_CHECKS'', DROPDB''', @exitcode OUT, @sqlerrorcode OUT" '' '

    Any ideas?

    0 0

    Or actually it says

    [SQLSTATE 42000] (Error 137) Unclosed quotation mark after the character string ' '' '

    0 0

    Here's an alternative:

    Code:
    DECLARE @exitcode int
    DECLARE @sqlerrorcode int
    DECLARE @sitename nvarchar(16)
    DECLARE @sql nvarchar(1024)

    SET @sitename = '<your value>'

    SET @sql = '-SQL "RESTORE DATABASE ' + @sitename + ' FROM DISK = ''D:\SQLVMDEV10\' + @sitename + '\FULL\*.sqb'' SOURCE = ''' + @sitename + ''' LATEST_FULL
       WITH MOVE DATAFILES TO ''G:\VirtualRestore'' , MOVE LOGFILES TO ''G:\VirtualRestore'' ,
       MAILTO = ''ed.watson@swfwmd.state.fl.us'', RECOVERY, DISCONNECT_EXISTING,
       REPLACE , CHECKDB = ''ALL_ERRORMSGS, DATA_PURITY, EXTENDED_LOGICAL_CHECKS'', DROPDB'

    EXEC master..sqlbackup @sql, @exitcode OUT, @sqlerrorcode OUT


    Note that the SOURCE and LATEST_FULL options must come immediately after the DISK value.

    0 0

    Hello,
    I am receiving the following errors in the sql log.

    12/14/2012 2:47:58 AM: Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
    12/14/2012 2:47:58 AM:
    12/14/2012 2:47:58 AM: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
    12/14/2012 2:47:58 AM: SQL error 3254: SQL error 3254: The volume on device 'SQLBACKUP_638113BA-9C82-4D44-96BF-EB8D63C21227' is empty.

    Although the error seems to indicate an issue, the log restore itself seems to have worked fine. When I check the data in the database, it is up to date.

    Below is the full error log from sql backup.

    SQL Backup log file 7.2.1.82
    -SQL "RESTORE LOG [Q2DB_3145] FROM DISK = 'D:\Q2\DBMIncoming1\NEV-DB-002_Q2DB_3145_40529000001080300001_20121213_101511_LOG.sqb' WITH REPLACE, STANDBY = 'D:\Q2\DBMIncoming1\StandByFiles\Q2DB_3145.undo', FILEOPTIONS = 1, ERASEFILES = 1, PASSWORD = 'XXXXXXXXXX', MOVETO = 'D:\Q2\DBMIncoming1\Complete\Q2DB_3145' "

    ----------------------------- ERRORS AND WARNINGS -----------------------------


    12/14/2012 2:47:58 AM: Restoring Q2DB_3145 (transaction logs) from:
    12/14/2012 2:47:58 AM: D:\Q2\DBMIncoming1\NEV-DB-002_Q2DB_3145_40529000001080300001_20121213_101511_LOG.sqb

    12/14/2012 2:47:58 AM: RESTORE LOG [Q2DB_3145] FROM VIRTUAL_DEVICE = 'SQLBACKUP_638113BA-9C82-4D44-96BF-EB8D63C21227' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , STANDBY = N'D:\Q2\DBMIncoming1\StandByFiles\Q2DB_3145.undo', REPLACE

    12/14/2012 2:47:58 AM: Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
    12/14/2012 2:47:58 AM:
    12/14/2012 2:47:58 AM: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
    12/14/2012 2:47:58 AM: SQL error 3254: SQL error 3254: The volume on device 'SQLBACKUP_638113BA-9C82-4D44-96BF-EB8D63C21227' is empty.

    0 0

    I'm new to SQL Backup 7 and configuring my environment for the first time. I launch the application and use the menu to add the local Sql Server database. Immediately after I click the button, I get the following error:

    SQLite cannot rollback - no transaction is active

    Once this happens, the application will not launch until I remove servers.dat.

    SQL Backup 7 was installed by a previous employee who is no longer available to help.

    I Googled and searched the forum and could not find any info that seems relevant.

    Can someone point me in the right direction, please?

    0 0
  • 12/16/12--09:12: RE: Annoying Crash
  • I'm getting the same problem when I use the scroll wheel on my mouse.

    The message in the "powered by {sa}" window reads, "Arithmetic operation resulted in an overflow"

    I click the send error report button each time.

    This happens each and every time with any server expanded (or not) and as soon as the first detent on the scroll wheel is encountered it crashes.

    SQLBackup 7.2.0.286 on Win 7 64-bit

    0 0

    Hi,

    Is there a limit on the number of databases to backup per Instance?

    We have over 1400 databases in an Instance and the backups hang after a period of time. Using v7.2.1.4.

    Thanks.

    Tim Knoob
    Senior Database Administrator
    Kareo

    0 0

    The problem with that is @sitename is the database name, how does it look through all of the database names?

(Page 1) | 2 | 3 | .... | 36 | newer