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 | .... | 11 | 12 | (Page 13) | 14 | 15 | .... | 36 | newer

    0 0
  • 04/10/13--09:39: RE: Issue with 7.3
  • Quote:
    If the green spinner completes, is it faster from then on or always slow on refresh?


    No idea on speed as it is still spinning with "Retrieving backup history ...". I am beginning to think it's not going to show any history information.

    0 0

    Sorry for the late reply.
    Yes it did.

    0 0

    Embarassed

    I found a log I could look at. It demonstrates that one should always check the easy stuff first. The db's in question have been growing and the destination volume for me test restores didn't have enough room to take the restores anymore.

    Pesky Thurman Unit....

    0 0

    Hi Guys,

    We are planning to use RedGate product for our backup solution. Before we go head with the product, I wud like to know how do I restore a encrypted backup on a different server without REDGATE tools. From time to time we provide production ( sanitised) DB backups for various third parties. how can I ensure that they can restore these backups taken by REDGATE tool.

    Thanks your help
    Murali

    0 0

    Hi, thank you for your forum post.

    In the situation where you need to restore a backup file created by SQL Backup onto a machine that does not have our software installed. Simply use the conversation tool available in your SQL Backup install folder. The tool is called SQBConverter.exe by default installed when you install the SQL Backup GUI in this path:
    C:\Program Files\Red Gate\SQL Backup 7 - 32-bit machine
    C:\Program Files (x86)\Red Gate\SQL Backup 7 - 64-bit machine


    Or download the stand-alone conversion tool available on this web PAGE. Scroll down the page and locate the SQL Backup to MTF Convertor.

    Run the tool, specify the path to the backup file you wish to convert, as the backup file is encrypted, enter the password and convert the backup. This process creates a *.bak file that you can then use native SQL Server restore tools to restore the file.

    Please note, depending on the number of threads used to create the original sqb, the conversion process will create a *.bak file corresponding to each thread.

    For example, a sqb file created using 3 threads will create 3 bak files.

    Many Thanks
    Eddie

    0 0

    thank you for the info!

    would it be possible to add this option in the GUI? it would be more straightfoward to change the option there than edit the registry manually. Just a suggestion!

    alex

    0 0

    here's another weird bug (maybe its the reliated with the one you have mentionned).

    If i go see the properties of a successful backup and a successful COPYTO network, i will see the word "Successful" in the Copy To Network column.

    1. now, do the same thing on a item that the COPYTO have failed. I will get the value "N/A" or sometimes "FAILED" in that column.

    2. go to another successful COPYTO backup and it will still show "NA" or FAILED". Close and reopen and it will now show "successful" value.


    i have emailed you a few log files that i have. Hope it will help.

    0 0

    i have also included another bug in the email:

    When a « transaction log » backup with copyto option enabled is made and the backup & copyto is successful, i get the icon of the network, the property window is show the good information but the log file is missing information about the copyto task!

    0 0

    i just totally forgot to answer your questions. Here it is:

    Quote:
    So if I have understood correctly the first database that you highlighted in your first screen shot listed, in fact had a successful COPYTO action despite the being no icon to indicate that a COPYTO action had taken place in the 'Copy to Network' column?


    exactly, the COPYTO icon is missing and in the property window, it say "N/A". The log file is OK since that say that the copyto have worked.

    Quote:
    The remaining two databases have the Copy To Network icon to indicate that the COPYTO keyword was selected but the copy process failed and therefore should have included a yellow warning triangle icon in the outcome column?


    not exactly. The COPYTO have worked, the icon is there, the log file say that the COPY have worked too but in the property window, it tell me "FAILED" instead of "SUCCESSFUL".


    and about this quote:
    Quote:
    In the fourth column, indicates that the option to copy the backup to a network location was selected. The Outcome column indicates whether this was successful.


    i would suggest to not only have the icon to say "option On or Off" but maybe have the icon with a yellow exclamation to say if something wrong happend to that option? That way, we can quickly scan the history and check if i have an icon of COPYTO that have worked or not, a "copy to cloud" problem or something like that.

    0 0
  • 04/11/13--13:02: RE: Issue with 7.3
  • I do not meant to hijack smccreadie's thread. Sorry ... but thought I do a quick update.

    The spinning green thing did not stop - waited till the end of yesterday and close out the app.
    This morning launched SQL Backup again, and server starts spinning, so did Activity History. Waited for about an hour - it did not stop, so I close out the app.
    Did not bother to try Restore or Backup. Doing it the old fashion tsql way. Unfortunately, until the fix for this issue, SQL Backup tool is pretty much useless to me now.

    0 0
  • 04/12/13--02:45: RE: Issue with 7.3
  • Hi,

    Apologies that you are experiencing what I can appreciate is a very frustrating issue. We are investigating the causes of this behaviour; there are a couple pieces of information that will be useful to us to help diagnose and hopefully resolve this for you and others.

    The SQL Backup UI logs its activity to:
    C:\Users\USER.NAME\AppData\Local\Red Gate\Logs\SQL Backup
    If you could email me the log created during the upgrade I can see which steps took the longest or didn't complete (if you can remember the date, otherwise please send all recent logs).

    Also, there are UI cache files stored in
    C:\Users\USER.NAME\AppData\Local\Red Gate\SQL Backup\Server Data
    which I can examine. If you want, you can delete the files in this directly and the UI will sync history afresh - this could be speed things up if the cache is particularly fragmented due to the upgrade (the first load may slow, but once the history cache is written it should be faster next time).

    If it is still slow, then please delete or rename the data.sdf file from the machine hosting SQL Server (C:\ProgramData\Red Gate\SQL Backup\Data\{INSTANCE}).

    Wiping the data.sdf isn't really a fix, since you lose some of the details in the activity history, but if you are blocked then this may be the best option.

    Regards,

    Robin Anderson
    Developer, SQL Backup
    robin.anderson@red-gate.com

    0 0

    I'm wanting to run backups (EXECUTE master..sqlbackup ....) in SSMS but I do not want any datasets to be returned. I know you can omit the 2nd dataser by using the SINGLERESULTSET parameter but I also want to omit the first dataset. Is this possible?

    0 0

    Hi,

    Whilst I don't think SQL Backup doesn't have option to inhibit all result sets, you can hide its output by wrapping it in an sp_executesql command like so:

    declare @sql nvarchar(2000)
    set @sql = N'SELECT 1'
    create table #temp (dummy nvarchar(max))
    insert into #temp exec master..sp_executesql @sql

    Where 'select 1' is your backup command and the temporary table schema matches the output format of SQL Backup, which I think it a single column of nvarchar.

    Regards,

    0 0

    Many thanks for the reply. This has resolved my problem.

    Jon.

    0 0

    Hi,

    I created a new scheduled backup job. And I selected "Include these: All". This selected all of my existing databases, User and System. The backup job works as expected.

    Now, we have a web application that automatically creates databases when someone (application user) creates a new project through the application GUI. Also, after "n" number of days of inactivity, the application knows to detach the inactive databases.

    My question is: Does the backup job know to include the newly created databases? And does it know not to backup the detached databses? Or do I need to always be updating my backup job to make sure any changes (additions, deletions) need to be accounted for?

    thanks
    Hani

    0 0

    Hi,

    Your backup job will backup all currently attached databases if you select 'all'. So this will take account of new DBs and forget detached ones. To confirm this absolutely, you can check the 'script' tab on the final step of the scheduled backup wizard to ensure the BACKUP DATABASES [*] syntax is used. If you've already created the job, you can inspect the SQL Server agent step via SSMS.

    For reference: https://documentation.red-gate.com/display/SBU73/The+BACKUP+command#TheBACKUPcommand-BACKUPDATABASEargument

    Regards,

    0 0

    Perfect! Thanks!

    0 0
  • 04/18/13--09:18: SQL Backup 7.3.1.1
  • The latest version for SQL Backup is 7.3.1.1. This is a patch release to fix a problem in the Activity History which causes it to load much more slowly than usual, or to fail to load, after upgrading the graphical user interface to 7.3.0.383 (SB-5477).

    To upgrade to the latest version, from the Help menu select Check for Updates, or download a trial from the SQL Backup Pro page and use your serial number to activate.

    After upgrading the graphical user interface, you will not need to upgrade the server components.

    0 0
  • 04/18/13--09:22: RE: Issue with 7.3
  • Hi,

    We have released a patch to address this issue, version 7.3.1.1. You can download this using Check for Updates (from the Help menu in the SQL Backup GUI) or by downloading the installer from the SQL Backup page.

    If you have already upgraded to SQL Backup 7.3, you will not need to upgrade your server components again.

    Thanks,

    Marianne

    0 0

    Using SQLBackup 7.3.1.1
    I'm trying to restore some archived data (2012) to the current production database. Running through the GUI and it seems like the only options are Overwrite Existing Database or Create New Database

    Is there a capability within SQLBackup to restore append to the current prod db like in Oracle's imp/exp utility?

older | 1 | .... | 11 | 12 | (Page 13) | 14 | 15 | .... | 36 | newer