I would run a DBCC CHECKDB against the restored copy (probably off hours, as this will hit the disk pretty hard), just to be sure everything is correct with the restored copy. I would be much more concerned over the root cause of the database going to a restoring state. Without knowing that, this particular database could surprise you at just about any time.