RE: Programmatically set SMTP host

March 5, 2013, 11:30 am

≫ Next: SQL Backup Log File name

≪ Previous: RE: File browser unable to access local resource

$

0

0

Peter,

This is what I was looking for, I've tested it out and it seems to work fine.

Thanks for your help.

__________________________________________________________

FYI: For anyone else interested... the SQL Backup GUI must cache the email settings at some level because the only way I can get it to reflect that changes made by the stored proc call is to close out and re-enter the GUI. Even if I forced a refresh on the server it would not reflect the updated value. Thew me off for a minute when I was validating.

Also the actual values seemed to be stored in the registry here:

HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<INSTANCE>\

---

SQL Backup Log File name

March 7, 2013, 4:36 am

≫ Next: RE: SQL Backup Log File name

≪ Previous: RE: Programmatically set SMTP host

$

0

0

Is it possible to change its name from the default? doesnt seem to be an option in the UI.

thanks

RE: SQL Backup Log File name

March 7, 2013, 6:36 pm

≫ Next: RE: Use of file location tags in "Copy backup to network locatio

≪ Previous: SQL Backup Log File name

$

0

0

No, it isn't possible to change the log file name. For backups, the GUID that forms part of the file name represents the backup_set_uuid value in the msdb..backupset table, to allow easy referencing with the SQL Server backup history tables.

It is possible to change the folder though, and you can use tags. E.g. if you wanted to separate the log files by database name, you could use

g:\sql backup\logs\<INSTANCE>\<DATABASE>\

RE: Use of file location tags in "Copy backup to network locatio

March 8, 2013, 6:41 am

≫ Next: How to get this kind of information programmatically?

≪ Previous: RE: SQL Backup Log File name

$

0

0

I'm still digesting most of your post but I did want to mention that the use of the 'Test" button under the Copy to network section doesnt work when you use the file location tags. The process still works but that can be confusing.

How to get this kind of information programmatically?

March 14, 2013, 7:59 pm

≫ Next: Database Help?

≪ Previous: RE: Use of file location tags in "Copy backup to network locatio

$

0

0

When I hover my mouse over a sqb file, I can get some information. See the following image:



How can I get this kind of information programmatically?

Thanks!

Database Help?

March 15, 2013, 1:22 am

≫ Next: RE: How to get this kind of information programmatically?

≪ Previous: How to get this kind of information programmatically?

$

0

0

Hello i am a chartered accountant and i am very poor in IT i dont have the knowledge to maintain database and i need to create it for my clients and payroll management. I am in a big problem my system was crashed but now it is working fine. but i am unable to access my database what to do??

RE: How to get this kind of information programmatically?

March 16, 2013, 12:20 am

≫ Next: RE: Database Help?

≪ Previous: Database Help?

$

0

0

You can get most of the details using this:

Code:

EXEC master..sqlbackup '-sql "RESTORE SQBHEADERONLY FROM DISK = [<your backup file name>]"'

RE: Database Help?

March 18, 2013, 3:07 am

≫ Next: RE: Object Level Recovery error

≪ Previous: RE: How to get this kind of information programmatically?

$

0

0

We can help you if you have a specific SQL Backup error message or error code, the same goes for any of our tools. But it sounds like you need something more general for SQL Server.

This website may help though.
http://www.sqlbackuprestore.com

---

RE: Object Level Recovery error

March 18, 2013, 2:20 pm

≫ Next: SQL Backup 7.3

≪ Previous: RE: Database Help?

$

0

0

It worked fine with a database backup that contained about 2.5GB data.

After creating a new backup of the smaller database, it's behaving itself. I have noticed that using the backup that wasn't working, only stored procedures and tables were showing as being available to restore. In the newer backup, views are shown as well.

I've just now tried again and got it to fail again on the first server with the original database. It seems to be the CHECKSUM setting - when I turn it off, I can do OLR (and views are in the list of objects able to be restored. The 2.5GB database I used as above must've been backed up with CHECKSUM off, to save a bit of time on my slow DEV system - which threw me when OLR started working). Having all other settings the same, when I turn CHECKSUM on, views disappear from the list of recoverable objects and I get the error message reported when I try and restore any of the tables. A full restore of the database (to a different database name at least) works fine.

I tried backing up the bigger databases with CHECKSUM enabled and doing OLR. The first one I tried gave me this error: "Unable to get PFS page for page ID 1:198668" after 50% through importing schema information.

Same error (different page) for another DB I tried (that previously worked when CHECKSUM was not enabled).


Both machines are x86 Windows 2003 R2 Standard Edition with SP2. 1GB RAM, single 2.3Ghz CPU.
Both machines are running SQL Server 2005 Developer Edition with SP4.
Both are VMWare virtual machines on VMWare 5.0.

I tried with x64 SQL 2012 on x64 Windows 2008 R2 Standard Edition SP1 - I get "Unknown database compatibility version 110" error message (regardless of CHECKSUM setting).

I tried with x64 SQL Server 2008 R2 Standard Edition with SP2 on x64 Windows 2008 R2 Standard Edition (no SP). With CHECKSUM on, I got the following error: "Error reading backup objects: Couldn't locate entry for HoBT {34,1} in allocations table". With CHECKSUM off, OLR worked.

SQL Backup 7.3

March 19, 2013, 9:59 am

≫ Next: RE: SQL Backup 7.3

≪ Previous: RE: Object Level Recovery error

$

0

0

We’re pleased to announce that SQL Backup 7.3 has been released and is available to download. This is a minor release and includes new features and bug fixes.

New features
• Upload a copy of backups to a SQL Backup Pro Hosted Storage account with the backup wizards or using the COPYTO_HOSTED keyword. For more information, see Backing up to hosted storage.
• Track the progress of uploading backups to hosted storage from the In Progress tab and cancel the upload if required.
• View results of copying backups to hosted storage or a network location from the Activity History and Backup Properties.
• Manage off-site backups from the SQL Backup Pro Hosted Storage website. See http://sqlbackup.red-gate.com

Bugs fixed in 7.3
• SB-5335 - To restore transaction log backups from a folder without removing previously processed backups from that folder, include the MOVETO option in the RESTORE command and specify the same location. This is useful if you are log shipping to multiple standby servers and want to restore backups to each standby server from the same location (rather than copying backups to a different location for each server, then moving the backups to another folder after they have been processed).
• SB-5381 - When editing a scheduled backup job, the job name is only overwritten if the job was created with the default job name. If a non-default name was specified when the job was created, this is not overwritten on editing.
• SB-5428 - The SQL Backup command line interface (SQLBackupC.exe) now works on 64-bit clustered SQL Server instances.
• SB-5434 - If copying to a network share fails, the reason for the failure is given in the text of warning 141.
• SB-5436 - It is now possible to install the server components on a remote machine using the command line if the SQL Backup Agent service account password includes non-ASCII characters.
• SQL Backup should no longer attempt to restore transaction log backups that are currently being written.
• Additional debugging information is written to the log file, SQBCoreService_log.txt, when the -sqbdebug option is used.
• Occasional problems with behavior of the VERIFY option have been resolved.

SQL Backup 7.3 is a free upgrade from versions 7.0, 7.1 and 7.2. To upgrade, from the Help menu select Check for Updates or download a trial from the SQL Backup page and use your serial number to activate.

User interface version: 7.3.0.383 (to check the version number, from the Help menu select About SQL Backup).

Server components version: 7.3.0.57 (to check the version number, from the Edit menu select Properties).

RE: SQL Backup 7.3

March 19, 2013, 1:33 pm

≫ Next: RE: SQL Backup 7.3

≪ Previous: SQL Backup 7.3

$

0

0

Did SB-4934 make it into 7.3? I don't see it listed.

Thanks

Chris

RE: SQL Backup 7.3

March 20, 2013, 7:46 am

≫ Next: Fitted Kitchens London

≪ Previous: RE: SQL Backup 7.3

$

0

0

It would also be nice to see what verify issues have been resolved because my site has had some in the past and for that reason we include the VERIFYINTERVAL = 8 parameter.

Thanks

Chris

Fitted Kitchens London

March 22, 2013, 12:58 am

≫ Next: Fitted Kitchens birmingham

≪ Previous: RE: SQL Backup 7.3

$

0

0

Fitted Kitchens London. Best price fitted kitchens in London. www.solidwoodkitchen.co.uk
£595 for fitted kitchens in London - Fitted Kitchens London

Fitted Kitchens birmingham

March 23, 2013, 12:52 am

≫ Next: RE: Programmatically set SMTP host

≪ Previous: Fitted Kitchens London

$

0

0

Fitted Kitchens birmingham. Best price fitted kitchens in birmingham. www.solidwoodkitchen.co.uk
£595 for fitted kitchens in birmingham - Fitted Kitchens birmingham

RE: Programmatically set SMTP host

March 4, 2013, 7:40 pm

≫ Next: RE: SQL Backup 7.3

≪ Previous: Fitted Kitchens birmingham

$

0

0

Try this:

Code:

EXEC master..sqbutility 1040, 'SMTPHost', 'myhost.smtp.com' EXEC master..sqbutility 1041, 'SMTPPort', 135

---

RE: SQL Backup 7.3

March 25, 2013, 10:29 am

≫ Next: RE: SQL Backup 7.3

≪ Previous: RE: Programmatically set SMTP host

$

0

0

Tom,

Any more details on the verify issues that were fixed?

Thanks

Chris

RE: SQL Backup 7.3

March 25, 2013, 10:35 am

≫ Next: RE: SQL Backup 7.3

≪ Previous: RE: SQL Backup 7.3

$

0

0

Hi Chris,

The verify issue concerned scheduled backup jobs hanging when WITH VERIFY was included in the backup command. The backup was written to disk, but the RESTORE VERIFYONLY process did not complete, causing the job to hang.

I hope that helps. Please let me know if you need more information.

Thanks,

Marianne

RE: SQL Backup 7.3

March 25, 2013, 10:47 am

≫ Next: LogShipping BizTalk databases

≪ Previous: RE: SQL Backup 7.3

$

0

0

Thanks Marianne.

Sounds just like the reason I had included the VERIFYINTERVAL on advice from Pete Yeoh.

Chris

LogShipping BizTalk databases

March 25, 2013, 11:18 am

≫ Next: Hosted Storage

≪ Previous: RE: SQL Backup 7.3

$

0

0

Looking for advice on how to log ship BizTalk databases. They have a special, built-in backup job that does (native) full and log backups, so I do not want to use SQL Backup as Microsoft says it does not support 3rd party backups of BizTalk databases. Is there any way I could use the native log backups that it generates with SQL Backup log shipping job running on the destination server? In other words, can the Restore command handle a native backup? Is there a converter program from native to .sqb? (I know there is one from sqb to native). Thanks.

Hosted Storage

March 25, 2013, 11:18 am

≫ Next: RE: Object Level Recovery error

≪ Previous: LogShipping BizTalk databases

$

0

0

Is there a way to override Hosted Storage backup?