Comments
3 comments
- 
                
                   Guant, Guant,
 When I converted to SQLBackup I migrated each database at a time with the native backup and the SQLBackup jobs both running and once I was happy with the SQLBackup set up I stopped the native ones. Obviously I had to schedule them apart for performance and file access reasons and also for my own reasons I had the backup files generated in a different location. I had this parallel run system for maybe two or three days per database before I switched to solely SQL Backup.
 Good luck with your project.
 Jonathan
- 
                
                   Guant, Guant,
 The other thing to be careful of is that both SQL Backup and Native backups share the same LSN sequence so if you were to do the following:----------------------------------------------------------------------------------> Time SQL Backup: Full Diff Full Diff Full Native: Full Diff Diff Full Diff
 You would need a mixture of SQL Backup and Native backups to do a restore.
 James
- 
                
                   Very good point James, it totally slipped my mind that I ran my native backups with the WITH COPY_ONLY option so as to not break the SQLBackup chain. Very good point James, it totally slipped my mind that I ran my native backups with the WITH COPY_ONLY option so as to not break the SQLBackup chain.
 Essentially my first step was to accept that SQLBackup was my main backup tool and I had the native backups as a safety net.
 Jonathan
Add comment
Please sign in to leave a comment.
Thank you!