Options
Using Red Gate for Migration
sid.singh
Posts: 2
Hi,
We are using red gate for migration as guys who are hosting our servers currently backup databases using red gate. So we are buying red gate so that we can restore these databases on our environment.
However I had few queries,
1) Can we restore sql server 2005 red gate backup on sql serv 2008 R2 release ?
2) We want to establish log shipping (not ideally) to minimize downtime on cutover date. Since there is no connectivity from source to destination servers, we are planning to ask them to backup the database to an FTP site and then we would pick it up and restore the database. After this they would take backups of transaction logs and keep them on FTP site and we would use scheduled restore option in red gate to restore them to our site. Does it sound like correct approach?
We are using red gate for migration as guys who are hosting our servers currently backup databases using red gate. So we are buying red gate so that we can restore these databases on our environment.
However I had few queries,
1) Can we restore sql server 2005 red gate backup on sql serv 2008 R2 release ?
2) We want to establish log shipping (not ideally) to minimize downtime on cutover date. Since there is no connectivity from source to destination servers, we are planning to ask them to backup the database to an FTP site and then we would pick it up and restore the database. After this they would take backups of transaction logs and keep them on FTP site and we would use scheduled restore option in red gate to restore them to our site. Does it sound like correct approach?
Comments
It can be set up that way, but you would need to set up a FTP task on your own to download the files from the FTP site to a folder that's accessible by your secondary server. SQL Backup cannot retrieve files from FTP sites on its own.
The command to restore transaction logs would look like something like this:
SQL Backup would then attempt to restore every file it finds matching the g:\backups\LOG_mydb_*.sqb pattern, ordered by the backup finish date, and move every successfully restored file to the g:\backups\processed\ folder.
It would be ideal if the FTP task can download files ordered by creation date, but SQL Backup can deal with out-of-order files fine, except that you'll be receiving a lot of warnings that way.
You do not have to worry about SQL Backup attempting to restore files that are being downloaded, as it ignores files where it cannot obtain an exclusive lock.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8