Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Restoring MS SQL Transaction log to mirror server

Created: 11 Jul 2014 • Updated: 07 Sep 2014 | 3 comments

I need to restore a transaction log from one MS SQL server to a 2nd MS SQL server that is being set up as mirror server to the 1st SQL Server.  How do I accomplish this action.  I looked for an option within the NetBackup client on both the primary and mirror SQL servers that would allow me to restore the necessary transaction log file from the primary server to the mirror SQL server but I did not see that option available.

According to the DBAs they need the transaction logs to complete the setup of the mirroring of the database between servers.

My environment is as follows:

Windows 2008 R2 SP1 Datacenter for Master server host OS

NetBackup 7.5.0.7 Master Server

Master Server Policy has MS SQL transaction log backups every hour

Master Server Policy has MS SQL Full backups every night.

Client MS SQL server are running Windows 2008 R2 SP1 Enterprise with NetBackup 7.5.0.7 client software

The primary MS SQL server is in production at the present time and we did not want to overwrite production files inadvertently.

I looked at the following articles but did not find a solution that worked.

http://www.symantec.com/connect/forums/netbackup-75-v-ray-technology-sql-vms-and-transaction-logs - V-Ray currently not utilized for these MS SQL servers as they were originally backed up with version 6.5.6 when the policy was created for the servers.

https://www-secure.symantec.com/connect/forums/sql-2008-transaction-logs-backup

http://www.symantec.com/connect/articles/how-backup-and-restore-microsoft-sql-server-backup-netbackup - this article seemed to be the closest to what we are trying to accomplish but we couldn't get it to work.

Operating Systems:

Comments 3 CommentsJump to latest comment

Riaan.Badenhorst's picture

To restore to an alternate server or location you'll need to create a move script

http://www.symantec.com/docs/TECH15709

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

BR549's picture

I ran across the following article which also talks about building a move script to move the database.

http://www.symantec.com/docs/TECH35995

The individual creating the mirror had already copied the desired database to the destination server and was trying to just copy the transaction logs to allow him to complete the mirroring process, at least that's what I recall of the initial conversation.  After talking with Symantec Tech Support that option does not appear to be feasible as they indicated that the database plus all of the transaction logs since the last full database backup needed to be restored together.

The technician is working on a test restore to see if it will meet their needs by renaming the destination files in the script that is built when requesting a full restore of the database.  I am waiting to hear back regarding the test restore at this time.

BR549's picture

The client had the transaction logs backing up every hour and the attempt to move the database job took over 1 hour to complete which caused the move to fail.  The client had me temporarily change the transaction log backups to every 8 hours and was able to successfully move the database and establish the mirroring desired.

Once the mirror was established the client had me revert back to hourly backup of the transaction logs.