My previous process for restoring a production CMS content to a development environment was once the DB had been restored & publishing/content re-configured, I would start by republishing all dynamic component templates (leaving the "Republish Only" checked). This would republish all of the components (and their DCPs) that were marked "published" in the production environment.
When I did this in 2009 & 2011, it worked like a charm. Only the components that were intentionally published in the production environment would be published in the development one. With 2013 SP1, however, this seems to have changed.
If I select a Dynamic Component Template, choose to publish it with republish only and look at the items to publish, I see listed components that are not published to either Stage or Live (and never have been) - if I then select Publish, those items are indeed part of the publish transaction. Since I'm in the midst of upgrading from 2011 SP1 to 2013 SP1, I can perform this exact same test on the older environment (exact same data) and those items do not show in the items to publish dialog.
In the 2013 environment, it's not like it's republishing ALL of the unpublished components that match the schemas linked in the dynamic component template - it's still just a handful. The particular component I tracked down was being used in a component list which itself was used on a PAGE that was published... That was the only "published" connection I could find for the component.
Was this an intentional change on the part of SDL? Am I missing some new checkbox that tells it to behave like it used to? Am I looking at a bug here (none of the Hotfixes out there seem to address this)?