Hello,

I did search the forums and the KB, but was unable to find exact wording for support of Sql Express 2008 by DPM 2012.  The server is Standard 2008 R2.  Does anyone know if SQL Express 2008 is supported by DPM?

Thanks!

DPM 2010 backing up a sql 2005 server running on window server 2003. My backups started failing so I tried deleting the protection grop, uninstalling the backup agent, reinstalling the backup agent and recreating the protection group. When trying to recreate the group when I expand the server it does not show the usual all sql server option. I read this may be due to the sqlwriter. I checked the sql server and the sql server vss writer service is running. I trie restarting it but this did not solve my problem. I ran vssadmin list writers and it does NOT show up the list. I read a post about adding the NT AUTHORITY/SYSTEM account to the sysadmin role of the sql server and then restart the service but this did not work. I even removed the NT AUTHORITY/SYSTEM account and re-added it but this did not help. I was going to reinstall the sql writer vss writer service from the cd but it says I have a new version. I am assuming this is due to and update.

Can I reinstall the sqlwriter.msi and then run windows updated without damaging my existing database server? Do you think this will solve the issue.

I am trying to enable protection for SQL Server 2012 Developer Edition (SP1) with DPM 2012, but when I click on the SQL Server in "Available members" in the protection group, DPM enumerates only "All Shares", "All Volumes" and "System protection". I checked the VSS Writer service on the SQL server and it is started. Remote connections to the SQL sever are enabled and other servers use databases on it, so everything is fine with the SQL server. But I am not able to back it up since DPM does not show the instance at all and therefore I can't select the databases. No errors are reported, DPM just shows the above three items and "All SQL Servers" is not among them.

I ran diskshadow and list writers, this is the output:

DISKSHADOW> list writers status

Listing writer status information ...

        * WRITER "Task Scheduler Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
                - Writer instance ID: {1bddd48e-5052-49db-9b07-b96f96727e6b}

        * WRITER "VSS Metadata Store Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
                - Writer instance ID: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

        * WRITER "Performance Counters Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {0bada1de-01a9-4625-8278-69e735f39dd2}
                - Writer instance ID: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

        * WRITER "System Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {e8132975-6f93-4464-a53e-1050253ae220}
                - Writer instance ID: {9685ff73-592a-4ea1-844d-117d28db3605}

        * WRITER "ASR Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
                - Writer instance ID: {925cd5ff-d67e-4243-bf76-69be497f9a87}

        * WRITER "Shadow Copy Optimization Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
                - Writer instance ID: {461977cc-cea0-449c-b108-d15129ec7380}

        * WRITER "COM+ REGDB Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {542da469-d3e1-473c-9f4f-7847f01fc64f}
                - Writer instance ID: {75189190-3be1-4741-bafe-4829a7603463}

        * WRITER "Registry Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {afbab4a2-367d-4d15-a586-71dbb18f8485}
                - Writer instance ID: {639cd590-e6a9-48f9-a969-c195cc3fd03b}

        * WRITER "WMI Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
                - Writer instance ID: {f76a3e7b-504b-4690-8ee3-24be147d85b7}

        * WRITER "IIS Config Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
                - Writer instance ID: {0071d81b-7e04-494e-83bd-079f340907bc}

        * WRITER "BITS Writer"
                - Status: 1 (VSS_WS_STABLE)
                - Writer failure code: 0x00000000 (S_OK)
                - Writer ID: {4969d978-be47-48b0-b100-f328f07ac1e0}
                - Writer instance ID: {4ea02d3c-ac54-490b-94ab-372d58e9a30b}

Number of writers listed: 11

Bit the service is there and running. Can I further investigate the issue? Thanks in advance.

Hi,

I have two questions.

Is it possible to move this folder?

I have a DPM 2012 and when im trying to run the sync the current.log file get very big that is filling up the disk.

The second question is: Does the size of currnet.log file is related to the size of DB or Log? and what is the relation, if its 100 GB DB and 10 GB logfiles what is the size needed by current.log?

Thanks in advance.

Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

System Center 2012
SQL Server 2008 R2
Windows 2008 R2

During prolonged periods we need to suspend backups for specific SQL Servers. How are backups suspended?

Thanks,
Tom Morris

We were running the RC version of 2010. All backups were successful. Upgraded to the full release and now SQL backups are failing on two servers, where they had been successful before. Not receiving any errors in the event log. Closes thing I could find was VSS timeout information alerts. One fo the backups had been going for over 24 hours, so it is as if it loses connection to VSS or something weird happens. Running a vssadmin list writes shows all writers with no errors on the system. SQL 2005 is patched with SP3.

Hi

I have installed 2 new Server 2012 with SQL 2012 Standard Edition. Both Server i can backup successfully. But the SQL Server DB have after about 3 Minutes the same error

Unable to configure protection?

Any Idea?

Thanks for any help

Roendi

I get this error when i try to restore a database from DPM

----The recovery jobs for SQL-1\<dB> that started at Monday, September 19, 2011 5:19:15 PM, with the destination of
SQL-1.<domainname>, have completed. Most or all jobs failed to recover the requested data. (ID: 3111)
Recovery failed for  SQL-1\<DB>on SQL-1.beacon-light.org because a database with the name you specified
already exists on the SQL instance. (ID: 30205)---

I told it to overwrite.  And, there are no jobs or processes running on the database in question.  any idears?

Hello,

After upgrading one of our DPM 2012 SP1 servers, I am getting an Database Auto-Protection failed

With error details:

DPM could not connect to SQL server instance SEVER\MSDPM2010 on protected computer SERVER.domain.com

Can anyone helpt me out?

When attempting to protect a SQL Server AlwaysOn Availability Group (AG) using 2010 Data Protection Manager 2010 (DPM), the job fails on the secondary Replica with the following error:
Type: Replica creation
Status: Failed
Description: The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur.(0x800423F4))

In SQL, AlwaysOn is configured as follows:

Availability Mode: Synchronous Commit
Failover Mode: Automatic
Connections in Primary Role: Allow all connections
Readable Secondary: Yes

Backup Preferences:
Perfer Secondary
Priority: 50 (for each node)
Exclude Replica: False (for each node)

NT AUTHORITY\SYSTEM is the member of sysadmin.

In the Windows Appication Log on the SQL server I found those two events:

1. Event ID: 8229 A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried, the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
   PrepareForSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server Code-Named 'Denali' CTP2:SQLWriter
   Writer Instance ID: {b4c05d47-35b3-45a6-b7bc-5e3b5516b841}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 1508

2. SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1508.

Thread=1772. Client. Instance=. VD=Global\{C39CD2EF-83B6-4C10-A68D-7D152690C5B8}

1_SQLVDIMemoryName_0.

In the VSSADMIN query i got this:
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {b4c05d47-35b3-45a6-b7bc-5e3b5516b841}
   State: [8] Failed
   Last error: Non-retryable error

Thanks in Advance.

I can't find a definitive answer and I'm fairly confident it isn't but... Is SQL 2008 R2 SP2 supported on DPM 2007? We've just upgraded a SQL 2008 R2 server to SP2 and suddenly we cannot protect the databases; they don't even appear as an option to protect.

Cheers

Keith

Hi

I have a problem with a SQL 2008 Server in DPM.
When I create a new Protection Group and browse the SQL Server I receive the Error "DPM could not enumerate SQL Server instances using Windows Management Instrumentation on the protected computer SRV-SQL-001.test.local (ID: 965)"

On the SQL Server in the DPMRACurr.Errlog File are the following entries:

 WARNING Failed: Hr: = [0x8004100e] : unable to connect to the wmi namespace: root\Microsoft\SqlServer\ComputerManagement
wmiqueryhelper.cpp(158) [000000000344EFB8]  WARNING Failed: Hr: = [0x80041010] : unable to execute the WQL query: SELECT * FROM ServerSettings
sqlmirroringhelper.cpp(159) [000000000344F558]  WARNING Failed: Hr: = [0x80041010] : F: lVal : wmiQueryHelper.ExecuteWQLQuery(ssWMIQuery)
sqlmirroringhelper.cpp(75) [000000000344F558]  WARNING Failed: Hr: = [0x80041010] : u: lVal : GetInstanceNamesFromWMI(ssWMINamespace, arrLocalInstanceNames)
neapplicationnamespace.cpp(1582) [0000000000393890]  WARNING Failed: Hr: = [0x80041010] Failed to query SQL instancess from WMI

The WMI Namespace root\Microsoft\SqlServer\ComputerManagement does not exist on the SQl Server. But I think this in normal because the correct namespace for SQL 2008 should be root\Microsoft\SqlServer\ComputerManagement10

It seems like the DPM Agent recognizes the SQL 2008 Server as a SQL 2005.

Because of this error the autoprotection of new Databases doesn't work. How can I fix this error?

Thx

J0fe

Hello all!

I am attempting to automate the process to restoring a production SQL 2008 DB to a DEV environment, based on its recovery point time. Firstly, I am somewhat new to powershell and am unsure if this is even possible. It needs to restore daily. The script is necessary because the staff is small and management doesn't want to enable end-users to perform their own recoveries. Additionally, they do not want to manually execute the restore process as they want the recovery point to be restored at 3AM. Any input is greatly appreciated. 

Got a DPM2010 server and trying to protect my sql server with 4 instances. 3 Instances will get protected. One instance gives the following messages and isn't visible in the modifying or creating a protection group. Messages are listed below. Anyone have experience with this issue?

DPM could not enumerate application component MER1-SRV025\SCCM\master on protected computer mer1-srv025.zorg.local. (ID: 964)

DPM could not enumerate application component MER1-SRV025\SCCM\model on protected computer mer1-srv025.zorg.local. (ID: 964)

DPM could not enumerate application component MER1-SRV025\SCCM\msdb on protected computer mer1-srv025.zorg.local. (ID: 964)

DPM could not enumerate application component MER1-SRV025\SCCM\ReportServer$SCCM on protected computer mer1-srv025.zorg.local. (ID: 964)

DPM could not enumerate application component MER1-SRV025\SCCM\ReportServer$SCCMTempDB on protected computer mer1-srv025.zorg.local. (ID: 964)

DPM could not enumerate application component MER1-SRV025\SCCM\SMS_Z00 on protected computer mer1-srv025.zorg.local. (ID: 964)

DPM could not connect to SQL server instance MER1-SRV025\SCCM on the protected computer mer1-srv025.zorg.local. (ID: 966)

DPM 2010 v3.0.7707.0

We recently had to rebuild 1 node of a 2 node cluster.  DPM still thinks the agent is installed but cannot communicate with it.  Is it possible to manually uninstall the agent from the DPM repository without removing all the protection groups?  I'm trying to avoid unprotecting/reprotecting 11 protection groups with 275 protected databases.  I'm assuming this would take quite awhile. 

DPM 2010 v3.0.7707.0

I have a server PS that was originally protected by primary DPM1 and secondary SDPM.  Protection was changed to use primary DPM2. I'm not sure how the protection was changed on the secondary(I wasn't involved), but SDPM still thinks that PS is protected by DPM1. This generates errors on SDPM stating that the datasource is not available on DPM1.  Also in trying to set up secondary protection for PS, it's not listed under the DPM2 in the gui when selecting Group members. Its does, however, show up under DPM1.

In looking at the table tbl_AM_Server on SDPM, the DPMServerID points to DPM1. Is there a proper way to correct this without just updating this table?

Hi,

I have a problem with backup SQL databases with DMP 2012. I don’t know exactly why this stopped to work, but I know, that there is responsible SQL VSS writer.
My environment is:
- DPM 2012
- SQL 2008R2 Express installed on non-domain Server 2008R2, virtualized on Server 2012

DPM agent and communication between servers is OK, because I am able to backup file shares on the same server. I can also see all SQL databases in DPM console, but when I am trying to backup them, I receive “Replica is inconsistent”. I am unable to repair this and if I manually start “Perform Consistency Check”, I receive the following error:
An unexpected error occurred on DPM server machine during a VSS operation. (ID 207 Details: VssError:The shadow copy provider had an error. Check the System and Application event logs for more information.
 (0x80042306))

On SQL server, I looked with vssadmin list writers and SQL writer is listed with status Stable, No Errors.

Can you please help me to solve my issue?

Regards,

Elvis Gustin

I am running DPM 2012 w/SP1 to backup my SQL Server 2008 clustered instances.  I have configured a Self Service Recovery role on the DPM server to allow our SQL administrator to do SQL database restores.  I was able to configure the Self Service Recovery role to include all the SQL instances I am backing up with DPM (non-clustered and clustered).  However, when I use the DPM Self Service Recovery Tool I only see the non-clustered SQL instances and not the clustered ones.

When I created the DPM Self Service role I specified the clustered SQL instances as<FQDN of the resource group>\<SQL virtual name>\<SQL instance>. Otherwise, I would get an error saying that the SQL Instance could not be found.

Anyone know how to get the clustered SQL instances to show up in the DPM Self Service Recovery Tool?

Cheers,

Rene

Hi there,

I am experiencing some difficulties while trying to backup SQL 2008 R2 databases. When I browse the SQL server in "New Protection Group" screen, I can see "All Volumes", "All Shares" and "System Protection" but no SQL instances. 

There is a slight catch which is whenever I remove the databases attached to SQL server, I can see the default databases "Master", "model" and so on. 

Reconnecting the databases will result in disappearance of the instances that were shown in DPM.

I can see the SQL instances on DPM, but all other SQL servers fail to be shown on the "New Protection Group" screen.

any help would be appreciated. 

After moving the database files in SQL (using detach/reattach) is there a way of getting the DPM_SQL_PROTECT to move to the new file location (without unprotecting and re-protecting the datasource).

For example:

Original:

f:\old_DB_location\db.mdf
f:\old_DB_location\db.ldf
f:\old_DB_location\DPM_SQL_PROTECT\all the backup stuff

After detach/reattach:

f:\new_DB_location\db.mdf
f:\new_DB_location\db.ldf
f:\old_DB_location\DPM_SQL_PROTECT\all the backup stuff

Note: if you delete the DPM_SQL_PROTECT folder (when DPM is not running) then on the next synchronisation it gets recreated.

What we want:

f:\new_DB_location\db.mdf
f:\new_DB_location\db.ldf
f:\new_DB_location\DPM_SQL_PROTECT\all the backup stuff