I'm not sure I understand what you are looking to do exactly. LGTpa37841 has not been implemented but this was a very particular RFE requesting functionality of NMSQL with a third-party application and it states that the issue it has is not present when using only NMSQL.
The NMSQL Administration Guide details how the software backs up and restores the transaction logs:
Let me try to explain better. We are doing a sql server upgrade from 2000 to 2008 at 1800. I have a full backup of the database from 0400 and transaction log backups hourly. At 1000, I start the restore of the full backup and leave the database in norecovery mode. The full database restore finishes at 1400. I now need to apply the the transaction logs created hourly leaving the database in norecovery mode until the final transaction log backup taken at 1800. This allows for a very short downtime at 1800 rather than a long downtime to restore database and all transaction logs or backup and restore database at 1800.
The problem is that at the time of the restore all of the transaction logs have not been created. I would like to know if NMSQL can restore only a transaction log and not the associated full database backup and the transcation logs up to time of restore. What option allows this to occur?
I hope I have explained better what I am trying to do. The goal is to make the downtime as short as possible.
Danne-Murphy
1 Rookie
•
121 Posts
0
August 11th, 2010 06:00
That is along the lines that I am thinking. I am restoring the database now with this command
nsrsqlrc -s legpap01.smh.com -c psfpdbv3 -a PSFPDBV1.smh.com -f -d "MSSQL:FSPRD" -C " " -S norecover -t "Tue Aug 10 20:15:09 2010" "MSSQL:FSPRD"
after this completes, I will try to apply transaction logs with this command
nsrsqlrc -z -s legpap01.smh.com -c psfpdbv3 -a PSFPDBV1.smh.com -f -d "MSSQL:FSPRD" -S norecover -t "Tue Aug 11 06:25:15 2010" "MSSQL:FSPRD"
and then
nsrsqlrc -z -s legpap01.smh.com -c psfpdbv3 -a PSFPDBV1.smh.com -f -d "MSSQL:FSPRD" -S norecover -t "Tue Aug 11 07:25:15 2010" "MSSQL:FSPRD"
and so on until the final transaction log where I will replace norecover with normal.
Does that look to be correct?
coganb
736 Posts
0
August 11th, 2010 04:00
Hi,
I'm not sure I understand what you are looking to do exactly. LGTpa37841 has not been implemented but this was a very particular RFE requesting functionality of NMSQL with a third-party application and it states that the issue it has is not present when using only NMSQL.
The NMSQL Administration Guide details how the software backs up and restores the transaction logs:
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-008-656.pdf?
Are you looking for a particular functionality that is not described in this document?
-Bobby
Danne-Murphy
1 Rookie
•
121 Posts
0
August 11th, 2010 05:00
I am interested in the nsrsqlrc syntax to apply a transaction log to a database that is sitting in norereover mode.
I think you use the -z option, but am not sure of the rest of the syntax. I am looking for example in the nsrsqlrc log file.
Danne-Murphy
1 Rookie
•
121 Posts
0
August 11th, 2010 05:00
Let me try to explain better. We are doing a sql server upgrade from 2000 to 2008 at 1800. I have a full backup of the database from 0400 and transaction log backups hourly. At 1000, I start the restore of the full backup and leave the database in norecovery mode. The full database restore finishes at 1400. I now need to apply the the transaction logs created hourly leaving the database in norecovery mode until the final transaction log backup taken at 1800. This allows for a very short downtime at 1800 rather than a long downtime to restore database and all transaction logs or backup and restore database at 1800.
The problem is that at the time of the restore all of the transaction logs have not been created. I would like to know if NMSQL can restore only a transaction log and not the associated full database backup and the transcation logs up to time of restore. What option allows this to occur?
I hope I have explained better what I am trying to do. The goal is to make the downtime as short as possible.
praviad
21 Posts
0
August 11th, 2010 05:00
Hello Damurphy
I am David Pravia, senior technical support member of EMEA Networker team
I have read the latest description of your issue, please let me know whether the post below would help you to resovle the transaction log restore:
T
o use the command line to restore the file or filegroup, the
transaction log backup must be explicitly performed by using the
nsrsqlsv
command as follows:
nsrsqlsv
[-s NetWorker_server_name] -l incr -R -H dbName
where:
◆
NetWorker_server_name is the hostname of the NetWorker server.
◆
dbName is the name of the database that receives the transaction
log backup.
◆
The -R flag is required so the transaction log is not truncated after
the backup completes.
praviad
21 Posts
0
August 11th, 2010 06:00
-Z
Applies to the backup of up databases for SQL Server 2005, and is usually
used in the online restore scenario from the command line. The
-Z option
specifies that the incremental (transaction log) backup after restore is not
promoted to full backup. Without the
-Z option, the backup is promoted to full.
praviad
21 Posts
0
August 11th, 2010 08:00
Hello
It does look fine for me, yes
Regards
David S Pravia
praviad
21 Posts
0
August 12th, 2010 02:00
Hello Mr Murphy
I am wondering whether your SQL transaction log restore went succesfully
Thanks
David Pravia