I was trying to perform this in a single maintenance window, however the restoredata.bat process cumulatively took something like 80 hours - I am unable to sustain this length of down time for a fundamental tool. 

My pre-production server has completed the restoredata.bat and is now 2 weeks behind the production server. If I was to stop the live server, run backupdb.bat and migrate the data over onto the replacement server, run restoredb.bat and start the new server service. Would that confidently put me in a current state for the new server, where i do not miss any updates or new requests?