restoring to new db putting old db into restore The image below says it all.  I need to get some data out of a back-up that's two weeks old, so I restored to a new db called ETLFix.  However, when I started the restore my production DB, ETL went into restore as well. 

I suspect this because I restored ETLFix from a two week old .bak and an notification went off saying that the back-up chain is broken for ETL.  Another way to say it is, ELT thinks it's in restore because it learned an old .bak was read.  

How to I get my ETL production db out of restore, and keep this from happening in the future?
Try this statement:

RESTORE DATABASE ETL WITH RECOVERY

Since this is your prod environment, be very careful in doing your due diligence to be sure you're doing no harm that cannot easily be fixed.

Also, check the Options tab to see if "Take a tail-log backup before restore" is checked. If it's checked, then un-check it. Starting in 2016 (I think), if you're restoring over an existing database, then SSMS defaults to taking a tail log backup. In my quick test just now (restoring to a new name from a backup of an existing database), SSMS still defaults to take a tail-log backup prior to restore. Get in the habit of always checking the Options tab.

Hope that helps.