Hello:
I am new to DPM 2012 SP1 and trying to protect our sharepoint 2010 SP1 environments. We have both a test and a production environment. Currently, when I setup protection for our pilot environment, it seems to be connecting to both the production and pilot SQL instances. I suspect that this because both sharepoint environments use the same SQL Alias name, but pointing to different instances.
Does anyone know if this is a problem with DPM 2012 SP1? Do I need to tear down and recreate our test environment using a different alias? It seems a bit absurd that DPM would be unable to handle the same SQL alias name pointing to different SQL instances when they are in different datasources, but absurdities happen everyday.
~joe