You can do that in the restore GUI.
Pick your db, the PIT to which you want to restore to. Then SCRIPT & manually add the with move and new db name (ideally you'd do the restore on another server). Make sure you don't select the with replace option. That way you can't accidentally erase the prod db altogether.
Thanks Remi. I'll try that. It was kind of a PITA to do all of the logs by hand, but we did get it done with no data loss.
However restoring by hand is good practice for cases where you don't have the MSDB backup history around. Use the tools, but be sure you can do it without them too.
+100 on this one.
I have designed my whole DR strategy based on the fact that msdb will also be whacked. I rebuild the script solely based on the backup file names.
It's actually just as quick as the GUI, but with the certainty that it can't fail (because I've tested the script and I won't change it without fully retesting). With the GUI you can always forget or add an option by accident that makes the whole thing fail.
I had a real life test run with it 2 weeks ago.
I was out of office, I had never shown how to use the script and I was able to restore the prod DB over the phone on the first try & with minimal downtime without seeing the screen.
I call that a successful 'test' run ;-).
By now I know a monkey with a little training can start the restore of the prod DB in 2 minutes flat (no offense to the IT guys here :hehe:).