When we try to set a New Protection, and choose an instance of our SQL Cluster, we only see the system databases, and not the databases we've created.

However, in other instances in the same cluster, we don't have this problem.

Any ideas?

Thanks,

David

Hi,

Are you able to see the SQLServerWriter when you run the command vssadmin list writers from an elevated command prompt on the SQL-server?

If the writer do not appear, please make sure the Run As account for the SQL Server VSS Writer-service has the correct permission on the SQL-instance on the SQL-server.
In case you modify the permissions of the account, don't forget to restart the SQL Server VSS Writer-service for the changes to apply.

//Markus

When I run the command, the writer does appear:

Hi,

 

As previously outlined I would recommend ensuring the SQLServerWriter (Figure 1 below) is listed when you run the command vssadmin list writers from an elevated command prompt on the SQL-server node in the cluster that owns the DBs in question.

DPM relies on the VSS infrastructure to protect data. For SQL Protection we use the SQL VSS Writer, so if the SQLSeverWriter is not being listed when using the above mentioned command we will need to figure out the cause of why SQLSeverWriter is not being listed if you find that it is not.

 

Also the below post may assist if you are facing issues with the SQLServerWriter not being listed.

https://social.technet.microsoft.com/Forums/en-US/f7e85741-c27a-4093-ba85-a9978989c291/sql-cluster-instance-doesnt-appear-on-dpm-2010?forum=dpmsqlbackup

Figure 1:

**********************************************

Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

• Edited by Dwayne Jackson IIMicrosoft employee Wednesday, January 21, 2015 1:07 PM

Hi,

 

As previously outlined I would recommend ensuring the SQLServerWriter (Figure 1 below) is listed when you run the command vssadmin list writers from an elevated command prompt on the SQL-server node in the cluster that owns the DBs in question.

DPM relies on the VSS infrastructure to protect data. For SQL Protection we use the SQL VSS Writer, so if the SQLSeverWriter is not being listed when using the above mentioned command we will need to figure out the cause of why SQLSeverWriter is not being listed if you find that it is not.

 

Also the below post may assist if you are facing issues with the SQLServerWriter not being listed.

https://social.technet.microsoft.com/Forums/en-US/f7e85741-c27a-4093-ba85-a9978989c291/sql-cluster-instance-doesnt-appear-on-dpm-2010?forum=dpmsqlbackup

Figure 1:

**********************************************

Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

• Edited by Dwayne Jackson IIMicrosoft employee Wednesday, January 21, 2015 1:07 PM

Hi,

 

As previously outlined I would recommend ensuring the SQLServerWriter (Figure 1 below) is listed when you run the command vssadmin list writers from an elevated command prompt on the SQL-server node in the cluster that owns the DBs in question.

DPM relies on the VSS infrastructure to protect data. For SQL Protection we use the SQL VSS Writer, so if the SQLSeverWriter is not being listed when using the above mentioned command we will need to figure out the cause of why SQLSeverWriter is not being listed if you find that it is not.

 

Also the below post may assist if you are facing issues with the SQLServerWriter not being listed.

https://social.technet.microsoft.com/Forums/en-US/f7e85741-c27a-4093-ba85-a9978989c291/sql-cluster-instance-doesnt-appear-on-dpm-2010?forum=dpmsqlbackup

Figure 1:

**********************************************

Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

• Edited by Dwayne Jackson IIMicrosoft employee Wednesday, January 21, 2015 1:07 PM

Hi.

My name is Yogev and I am working with David on this issue.

I checked again. It was my mistake and  "SqlServerWriter" appears.

 

I also  verified that the "SQL Server VSS Writer" service is up and running under the Local System account.

Yet, we cannot browse the existing databases and put them into a new protection Group

Any ideas?

The specific instance is hosting the DPM database itself but also other databases from other systems. We also see the problem in other instances in the cluster that are not hosting the DPM database.

Did this ever get solved? I'm having the same problem now.

SC DPM 2012 R2 running on Server 2012 R2

Trying to back up SQL Server 2012 SP2, also running on Server 2012 R2

SqlServerWriter is listed as stable/no error

I only see the system databases from within DPM. None of the other 8 databases on the SQL Server appear.