Using Red Gate for Migration

Compresses, encrypts, secures and monitors SQL Server backups.

Moderators: JonathanWatts, Chris Auckland, eddie davis, Colin Millerchip, Brian Harris, james.billings, RBA, petey

Using Red Gate for Migration

Postby sid.singh » Fri Oct 04, 2013 4:13 pm

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?
sid.singh
 
Posts: 1
Joined: Fri Oct 04, 2013 4:07 pm

Postby petey » Mon Oct 07, 2013 7:58 am

1) Can we restore sql server 2005 red gate backup on sql server 2008 R2 release ?

Yes you can. However, the database cannot be placed in read-only mode, as that requires the database to be upgraded which causes future transaction logs to be non-restorable. The database can only be placed in non-recovery mode.

log shipping via FTP

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:

Code: Select all
EXEC master..sqlbackup '-sql "RESTORE LOG [mydb] FROM DISK = [g:\\backups\\LOG_mydb_*.sqb] WITH NORECOVERY, MOVETO = [g:\\backups\\processed\\]"'

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.
Peter Yeoh
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 7
petey
 
Posts: 2234
Joined: Sun Apr 24, 2005 12:34 pm


Return to SQL Backup 7

Who is online

Users browsing this forum: No registered users and 0 guests