User profile for jerryhung

Thanks I figured out how to do those in GUI BACKUP * for FULL backup BACKUP * exclude master for all DIFF backup However, the GUI is still not "smart" enough to interept BACKUP * for TLOG backup at run-time, where it ONLY backs up databases in full recovery mode I guess it's not a big deal since I will get an ERROR email if a database recovery mode is changed out of FULL mode, however it is cumbersome to REMEMBER to add new FULL-recovery-mode databases into the TLOG backup job / comments

Thanks I figured out how to do those in GUIBACKUP * for FULL backupBACKUP * exclude master for all DIFF backup However, the GUI is still not "smart" enough to intereptBACKUP * for TLOG backup at ru...

0 votes

Thank you, that answered my question I would just change the JOIN condition filter / comments

Thank you, that answered my question I would just change the JOIN condition filter

0 votes

Brian Donahue wrote: Hi Jerry, SQL Backup uses the SQL VDI as an interface to get the backup data, so the updates to the backup history tables in MSDB are still done by SQL Server in exactly the same way as when you do the backup natively. That is great news to hear Brian I look forward to testing it and confirm back here shortly / comments

Brian Donahue wrote: Hi Jerry, SQL Backup uses the SQL VDI as an interface to get the backup data, so the updates to the backup history tables in MSDB are still done by SQL Server in exactly the ...

0 votes

I just did some testing with my Differential backup to confirm (should've done so yesterday) 1. Copy to network does not generate additional entries in msdb.dbo.backupset 2. Multi-thread does not create additional entries in msdb.dbo.backupset either However, it does generate more entries (3 threads = 3 entries, 2 threads = 2 entries) in the msdb.dbo.backupmediafamily, where I get my physical_device_name They would be using the same media_set_id, but different sequence # and GUID media_set_id family_sequence_number media_family_id 3600 1 1A8CA95E-0000-0000-0000-000000000000 3600 2 5E49F657-0000-0000-0000-000000000000 My question is just if that is expected/correct behaviour? If that's supposed to happen, I guess I just need to SELECT DISTINCT or remove duplicate file path by selecting family_sequence_number = 1 SELECT TOP 100 a.backup_finish_date ,CASE a.[type] WHEN 'D' THEN 'FULL' WHEN 'I' THEN 'DIFF' WHEN 'L' THEN 'Trans Log' ELSE a.type END AS backuptype ,a.server_name ,a.database_name ,a.recovery_model AS database_recovery_model ,b.physical_device_name FROM msdb.dbo.backupset a (NOLOCK) LEFT JOIN msdb.dbo.backupmediafamily b (NOLOCK) ON a.media_set_id = b.media_set_id WHERE 1 = 1 ORDER BY a.backup_finish_date DESC SELECT TOP 1000 * FROM msdb.dbo.backupmediafamily b (NOLOCK) WHERE physical_device_name LIKE '%sqb%' ORDER BY physical_device_name media_set_id family_sequence_number media_family_id media_count logical_device_name physical_device_name device_type physical_block_size mirror 3600 1 1A8CA95E-0000-0000-0000-000000000000 1 Red Gate SQL Backup (6.2.0.134):00000000003400000000000000026A000000145D000000000104 E:\Backup\AdventureWorks\DIFF_REPORTINGSERVICE_AdventureWorks_20091104_152716.sqb 7 65536 0 3600 2 5E49F657-0000-0000-0000-000000000000 1 Red Gate SQL Backup (6.2.0.134):00000000003400000000000000026A000000145D000000000104 E:\Backup\AdventureWorks\DIFF_REPORTINGSERVICE_AdventureWorks_20091104_152716.sqb 7 65536 0 / comments

I just did some testing with my Differential backup to confirm (should've done so yesterday) 1. Copy to network does not generate additional entries in msdb.dbo.backupset 2. Multi-thread does not c...

0 votes

So indeed SQL Backup does update the MSDB tables However, I noticed this odd behaviour, and I want to confirm 1. Does it insert 1 row PER THREAD? e.g. I had 3 thread for the DIFF backup and it created 3 rows? 2. Does it insert 1 extra row if I chose the Network Copy/Mirror option? I changed thread=1, but still see 2 rows in msdb.dbo.backupset like below E:\Backup\msdb\DIFF_REPORTINGSERVICE_msdb_20091103_203603.sqb E:\Backup\msdb\DIFF_REPORTINGSERVICE_msdb_20091103_203603.sqb / comments

So indeed SQL Backup does update the MSDB tables However, I noticed this odd behaviour, and I want to confirm1. Does it insert 1 row PER THREAD? e.g. I had 3 thread for the DIFF backup and it crea...

0 votes

I just did a test restore, and by default SQL Backup 6.2 picked the nested "C:\Program Files\.........." directory instead of the E:\MSSQL\DATA and E:\MSSQL\LOG directories specified in the "Database Settings" / comments

I just did a test restore, and by default SQL Backup 6.2 picked the nested "C:\Program Files\.........." directory instead of the E:\MSSQL\DATA and E:\MSSQL\LOG directories specified in the "Databa...

0 votes

This has been corrected in SQL Backup 6.4 I just upgraded all my production from 6.3 to 6.4 and Registry Replication has re-surfaced in the SQLBackupAgent HOWEVER............ the error continues non-stop UNTIL a restart of SQLBackupAgent (take offline, bring online), keep that in mind!!! I had to do this for 2 * 4 clusters we have [image] Cluster service failed to save the registry key Software\Red Gate\SQL Backup\BackupSettingsGlobal\DBXXXX01 when a resource was brought offline. The error code was 1018. Some changes may be lost. / comments

This has been corrected in SQL Backup 6.4 I just upgraded all my production from 6.3 to 6.4 and Registry Replication has re-surfaced in the SQLBackupAgent HOWEVER............ the error continues no...

0 votes

RBA wrote: A fix for this problem has been discovered and will be included in the next release, due this quarter. We are currently undergoing release testing, however, if you would like to receive the patch early please get in touch via private message or email (robin.anderson@red-gate.com). Regards, Great news, eager to wait for the new release!! / comments

RBA wrote: A fix for this problem has been discovered and will be included in the next release, due this quarter. We are currently undergoing release testing, however, if you would like to receiv...

0 votes

I found this post via Google search I just noticed this error on our Windows 2003 Enterprise R2 x64, SQL Backup 6.3.048 (so far, 2 clusters have the error and 3 don't) Interesting... they're all SQL 2005 Standard I'm gonna remove the registry replication from those failed ones / comments

I found this post via Google search I just noticed this error on our Windows 2003 Enterprise R2 x64, SQL Backup 6.3.048 (so far, 2 clusters have the error and 3 don't) Interesting... they're all SQ...

0 votes

Thanks Tanya (and David for the email notification) Congrats on a new 4.x version, WOO HOO! Felt like 3.8/3.9 was eternity While not wanting to affect my current 3.9 setup (which works great), gotta find a new environment to test this out Question - how long is the build good for? expiry date? Thanks, keep up the good work / comments

Thanks Tanya (and David for the email notification) Congrats on a new 4.x version, WOO HOO! Felt like 3.8/3.9 was eternity While not wanting to affect my current 3.9 setup (which works great), gott...

0 votes

How can we help you today?

jerryhung

Comments