After the absolute shambles that is the 6.7 release, we have identified there is a need to bulk out the dataset in Dev as some of the craziness in 6.7 didn't show up for us until we were dealing with Prod and it's much larger dataset (such as the inability to search/sort/filter the tables in reclaim capacity view...)
Are there generally any issues to be found if we pointed additional vrops instance to vcenter, so have both dev and prod vrops pulling in the same data?
Is there a way to reduce how often the dev instance would collect data in order to reduce load on vcenter?
In prior releases there was no issue with having multiple vROps collecting from the same vCenter. I'd assume that this should still be okay with 6.7. I think that only one of them will be registered as a vCenter extension (visible in the web client), but both can be collecting from it. You can change the collection interval on the adapter instance. In the Inventory Explorer find the adapter instance for the vCenter instance that you want to change and click the edit object button on the toolbar. The collection interval can be changed there.
I do not believe it is possible for multiple vROps instances to collect from the same vCenter server.
On my last install when creating a new vCenter collector, vROps warned me that it would unregister the older vROps from the VC before continuing.