Quantcast
Channel: Data Protection Manager - SQL Protection forum
Viewing all 204 articles
Browse latest View live

Problem to backup Database SQL in SIMPLE mode

$
0
0

Hi guys,
I have a problem with protection of SQL DB.
My Database  is configured for use SIMPLE mode, but DPM try to backup the DB as if setting is FULL mode.
At any hour DPM try to create a DB recovery point but this process is failed with this error:

"Execution of SQL command failed for SQL Server 2012 database xxxxx\<nome DB> on <server SQL> with reason : BACKUP LOG is terminating abnormally.
The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
. (ID 30173 Details: Internal error code: 0x80990D18)"

I have tryed to:
1) remove the DB from protection group and re-add the db
2) Set DB to FULL end return to SIMPLE
   Set DB to FULL
   Remove DB from protection group
   SET DB to SIMPLE
  Re-add the DB to protection group

But nothing of this resolve my problem.

Thank tou for any idea.

Fabio

 


Incremental Backups Not Working - DPM 2012 R2

$
0
0

Hi

Having a strange issue where incremental backups in some situations are not working, however the daily full backup is succeeding.

This doesn't seem to be a SQL instance issue, in that within the same protection group, on the same sql instance, the incremental backups are working on other databases.

All of the databases are set to full recovery model, and I'm not seeing any failed jobs (although when I check the jobs, the only scheduled job is the full backup, none for the incremental backups are listed (which isn't the case for the databases that are incrementally backing up).

What am I doing wrong?

How to protect a SQL Failover Cluster with DPM?

$
0
0

It says here: https://technet.microsoft.com/en-us/library/hh780998.aspx that DPM is cluster aware when protecting a SQL cluster and will backup the primary node.  However here: https://technet.microsoft.com/en-us/library/jj860400.aspx it says DPM won't protect SQL server databases hosted on CSVs.

My question is what should we use instead of CSVs for our SQL workloads so that DPM can still protect them?

When installing a SQL failover cluster as far as I know CSVs are the only option.

Domain migrated SQL Server can't be protected by DPM 2012 R2

$
0
0

Hi All,

We have a server that was migrated to a new domain and when I try to setup protection with DPM 2012 R2 I get as far as Select group members and expand the Server and the SQL instance is not showing up.  

I uninstall the old DPM agent on the server and reinstall the new agent pointed to this DPM server and no joy.  I have done the uninstall and reinstall of the agent multiple times, thrown in reboot etc, still no joy.  

Our DBA says the SQL instance is running fine in the new domain and the users can access it, but DPM doesn't see it.  VSSAdmin is clean on both the DPM server and the protected server, all services are running on both.  

It was backed up by the same DPM server when in the old domain and the old protect group was disabled.  I am at a loss and need to get this puppy backed up.  Any ideas?

Thanks, Jeff

dpm 2016 jobs not running even though no errors

$
0
0

I thought everyhting was fine with my dpm 2016 installation since there were not warnings in dashboard, then i notice i had no new recovery points since initial backup.  finally in even viewer i found sql errors saying 

SQL Server Scheduled Job '4c6f1d88-077a-40b2-b527-8632de861bcf' (0x3A5621EF953D3E40B10E1786ADE69770) - Status: Failed - Invoked on: 2017-06-19 13:30:00 - Message: The job failed.  The owner (MICROSOFT$DPM$Acct) of job 4c6f1d88-077a-40b2-b527-8632de861bcf does not have server access.  

So i went in and added the user to the database with read and write roles but now the jobs are failing with this in the event viewer.

SQL Server Scheduled Job 'd11fee45-afba-4021-939f-d431a1f87340' (0x202D66695545804FB853B8E61B05CBC3) - Status: Failed - Invoked on: 2017-06-19 14:00:00 - Message: The job failed.  The Job was invoked by Schedule 222 (Schedule 1).  The last step to run was step 1 (Default JobStep).

 I am not good with sql and cant find any good info that seems to work please help.

"DPM detected changes in existing protected objects" after manual failover - DPM 2016 - SQL Server 2016 Always On Availability Group

$
0
0

After an Always On Availability Group manual failover, on next incremental sync DPM fails with error

"The replica of SQL Server 2016 database <AGName/DBName> on <AG FQDN> is not consistent with the protected data source. 
DPM detected changes in existing protected objects and detected new protectable objects for the data source since it was configured for protection. (ID 30138)"

DPM 2016 Update 2 (5.0.322) - server and agents - on Windows Server 2016 (version 1607), in Hyper-V VM.

Trying to protect SQL Server Enterprise 2016 (13.0.1601.5) on Windows Server 2016 (Version 1607) in Hyper-V VM.  Two instances on two VMs, same domain, using Windows Server Failover Clustering. Availability Group configured for synchronous commit and for backup only of primary.  On each SQL Server host the DPM computer is in the local Users group, which has Access this computer from the NEtwork.  On each SQL instance NT Authority\System and NT Service\DPMRA are in the sysadmin group.  One database in Always On AG, database shows synchronized on both instances. 

Initial replica creation, an express full, and several incremental syncs are completed without error, but after a manual failover of Availability Group the next incremental sync fails with the error listed above.

Suggestions?

thanks!

Martin

SQL Backups will only complete if run manually

$
0
0

Hi Everyone,

We have DPM 2010 installed on a Windows 2008 R2 server (HP Tape Library attached) and we are experiencing an odd issue. We have a few SQL 2005 DB's that will only backup to disk if we run the jobs manually. When they are run according to schedule they consistently fail. I haven't found a similar issue to this in the forums so any help would be great. The recovery model for these DB's are set to simple or bulk-logged.

The description I get for the error is as follows:

Type: Recovery point

Status: Failed
Description: Execution of SQL command failed for SQL Server 2005 database DB Name on domainname with reason : BACKUP LOG is terminating abnormally.
BACKUP LOG cannot be performed because there is no current database backup.
. (ID 30173 Details: Internal error code: 0x80990D18)

Let me know if you need anymore information. Thanks.

Backup of SQL 2016 Cluster within a Windows 2016 server cluster

$
0
0

Ok, so the title of this tells a strange story.  We have a two node windows 2016 server cluster.  Within that cluster, we have a two node SQL 2016 cluster.  Essentially, a clustered cluster.  I'm sure we aren't the only ones to have ever done this.  The SQL cluster works great in this configuration.  The problem I'm having is backing up the SQL databases using DPM 2016.  I can configure the Protection Group without any problems.  It's when DPM actually tries to back up the databases that I  get an error.  It immediately tells me "Unable to configure protection".  Under Monitoring, the failed job has the message "DPM cannot continue protection for SQL server 2016 database <Dbase Name Here> on SQLCLUSTERGROUP.<SQL Cluster Name Here with FQDN>. (ID 30184) 

That ID is useless as the forwardmost tits on a boar hog.  I cannot determine what is causing this issue.  If anyone can help, I'd really appreciate it and thanks in advance if you can help.


Backup Log files they appear they are not backing up or shrinking SCCM2016 SQL 2012

$
0
0

I have several databases on an SQL 2012 server that I am backing up with SCCM 2016.  The log files say they have never been backed up ever (from sql manager). and they are growing out of control. 

How do you backup SQL databases (including the logs) forceing a truncation and shrinking of SQL database transaction logs?

DPM failing SQL backups due to error: "the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)

$
0
0

I ran across this error starting on 6/4/2011 and have been unable to find the root of the problem.  In our environment, we have a DPM 2010 server dedicated to backing up all our SQL envrionment (about 45 SQL Servers total).  All of the SQL environment is backing up fine except for a SQL Cluster Application.  This particular SQL Instances is part of a 6 node failover cluster with 6 SQL Instances distributed amongst them.  The other 5 SQL instances in the cluster are backing up fine; only one instance is failing.  The DPM Alerts section shows this error when attempting to do a SQL backup of one of the databases on this SQL instance:

Affected area: KEN-PROD-VDB001\POSREPL1\master
Occurred since: 6/11/2011 11:00:56 PM
Description: Recovery point creation jobs for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com have been failing. The number of failed recovery point creation jobs = 4.
 If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)
 The DPM job failed for SQL Server 2008 database KEN-PROD-VDB001\POSREPL1\master on SQL Server (POSREPL1) - Store Settings.ken-prod-cl004.aarons.aaronrents.com because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F85)
 More information
Recommended action: This can happen if the SQL Server process is overloaded, or running short of memory. Please ensure that you are able to successfully run transactions against the SQL database in question and then retry the failed job.
 Create a recovery point...
Resolution: To dismiss the alert, click below
 Inactivate alert

I have checked the cluster node this particular SQL instance is running on using Perfmon and the machine is nowhere near capacity on CPU, memory, network, or Disk I/O.  I have failed this SQL Application to another node in the cluster and receive the same error (this other node has another clustered SQL application on it that is actively running as well as backing up fine).  The only thing that I am aware of that has changed is that we installed SP2 for SQL 2008 about 2 weeks prior to when the failures started to occur.  However, we updated all six clustered SQL Instances at the same time and only this one is having this issue so I don't believe that caused the problem.  We are running SQL 2008 SP2 (version 10.0.4000.0) on all clustered instances along with DPM 2010 (version 3.0.7696.0) on this particular DPM server that has the issue.

One last thing, I have also noticed errors in the event log pertaining to the same SQL backups that are failing (but the time stamps are not concurrent with each backup attempt):

Log Name:      Application
Source:        MSDPM
Date:          6/13/2011 1:09:12 AM
Event ID:      4223
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      KEN-PROD-BS002.aarons.aaronrents.com
Description:
The description for Event ID 4223 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.

Problem Details:
<DpmWriterEvent><__System><ID>30</ID><Seq>1833</Seq><TimeCreated>6/13/2011 5:09:12 AM</TimeCreated><Source>f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp</Source><Line>815</Line><HasError>True</HasError></__System><DetailedCode>-2147212300</DetailedCode></DpmWriterEvent>


the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSDPM" />
    <EventID Qualifiers="0">4223</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-06-13T05:09:12.000000000Z" />
    <EventRecordID>68785</EventRecordID>
    <Channel>Application</Channel>
    <Computer>KEN-PROD-BS002.aarons.aaronrents.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DPM writer was unable to snapshot the replica of KEN-PROD-VDB001\POSREPL1\model. This may be due to:
1) No valid recovery points present on the replica.
2) Failure of the last express full backup job for the datasource.
3) Failure while deleting the invalid incremental recovery points on the replica.

Problem Details:
&lt;DpmWriterEvent&gt;&lt;__System&gt;&lt;ID&gt;30&lt;/ID&gt;&lt;Seq&gt;1833&lt;/Seq&gt;&lt;TimeCreated&gt;6/13/2011 5:09:12 AM&lt;/TimeCreated&gt;&lt;Source&gt;f:\dpmv3_rtm\private\product\tapebackup\dpswriter\vssfunctionality.cpp&lt;/Source&gt;&lt;Line&gt;815&lt;/Line&gt;&lt;HasError&gt;True&lt;/HasError&gt;&lt;/__System&gt;&lt;DetailedCode&gt;-2147212300&lt;/DetailedCode&gt;&lt;/DpmWriterEvent&gt;
</Data>
    <Binary>3C00440070006D005700720069007400650072004500760065006E0074003E003C005F005F00530079007300740065006D003E003C00490044003E00330030003C002F00490044003E003C005300650071003E0031003800330033003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E0036002F00310033002F003200300031003100200035003A00300039003A0031003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0066003A005C00640070006D00760033005F00720074006D005C0070007200690076006100740065005C00700072006F0064007500630074005C0074006100700065006200610063006B00750070005C006400700073007700720069007400650072005C00760073007300660075006E006300740069006F006E0061006C006900740079002E006300700070003C002F0053006F0075007200630065003E003C004C0069006E0065003E003800310035003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C00440065007400610069006C006500640043006F00640065003E002D0032003100340037003200310032003300300030003C002F00440065007400610069006C006500640043006F00640065003E003C002F00440070006D005700720069007400650072004500760065006E0074003E00</Binary>
  </EventData>
</Event>

Any help would be greatly appreciated!

SCDPM 2016 and SQL 2017

$
0
0

Dear Tech-net Community,

I have SCDPM 2016 UR2 on Win2012 R2, dose anyone know if SCDPM 2016 supports backup of SQL 2017?

Thank you

DPM could not enumerate SQL Server instances using Windows Management Instrumentation

$
0
0

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

VM or SQL backup or both?

$
0
0

Hi

Very general question but what is best practice? To back up the VM or the SQL data on that VM... or backup both VM and SQL at the same time? But I believe both is just effectively backing up your data twice?

Thanks in advance.

how to protect SQL 2012 on Windows 2012 R2,but the log and data are not in the same location

$
0
0

Back up sql server with dpm2012 R2, but the log and data are not in the same location,please help me to fix it,thanks.

error:

3B01194 09/1006:19:04.13631dllmain.cpp(37)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALSQLWriterHelperPlugin: DLL_PROCESS_ATTACH
13B01194 09/1006:19:04.13631sqlmirroringpluginhelper.cpp(116)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALunique logical path : VM-DBCENTER
13B01194 09/1006:19:04.13631sqlmirroringpluginhelper.cpp(193)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALvss logical path : VM-DBCENTER
13B01194 09/1006:19:04.18331sqlmirroringpluginhelper.cpp(375)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALExecuting SQLQuery SELECT mirroring_role                                 FROM sys.database_mirroring                                WHERE database_id =                                 (SELECT database_id FROM sys.databases WHERE name=N'netdb')
13B01194 09/1006:19:04.18331vssbaserequestor.cpp(51)[0000000000E76970]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCVssBaseRequestor: constructor [0000000000E76970]
13B01194 09/1006:19:04.18331vsssnapshotrequestor.cpp(104)[0000000000E76970]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCVssSnapshotRequestor::CVssSnapshotRequestor [0000000000E76970]
13B01194 09/1006:19:04.18331sqlmirroringpluginhelper.cpp(116)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALunique logical path : VM-DBCENTER
13B01194 09/1006:19:04.18331sqlmirroringpluginhelper.cpp(193)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALvss logical path : VM-DBCENTER
13B01194 09/1006:19:04.18331sqlwriterhelperplugin.cpp(3844)[0000000000ED4BB0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALExecuting SQLQuery to get Volume Names - SELECT type, physical_name                                 FROM sys.master_files                                     WHERE database_id = (SELECT database_id FROM sys.databases WHERE name=N'netdb')
13B01194 09/1006:19:04.18331sqlwriterhelperplugin.cpp(3856)[0000000000ED4BB0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALGoing to Add Volume For File - D:\netdb\Data\netdb.mdf
13B01194 09/1006:19:04.18331sqlwriterhelperplugin.cpp(3990)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALssLocalVolumeGuid = [\\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\], ssClusterVolGuid=[\\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\]
13B01194 09/1006:19:04.18331sqlwriterhelperplugin.cpp(3856)[0000000000ED4BB0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALGoing to Add Volume For File - D:\netdb\Log\netdb_log.ldf
13B01194 09/1006:19:04.18331sqlwriterhelperplugin.cpp(3990)615E7BF9-F1F8-4128-A0CF-812BB4F83AEB NORMALssLocalVolumeGuid = [\\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\], ssClusterVolGuid=[\\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\]
13B01194 09/1006:19:04.19931sqlwriterhelperplugin.cpp(4119)[0000000000ED4BB0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALExecuting SQLQuery SELECT type, physical_name                                 FROM sys.master_files                                WHERE database_id =                                 (SELECT database_id FROM sys.databases WHERE name=N'netdb')
13B01194 09/1006:19:04.19931sqlwriterhelperplugin.cpp(3783)[0000000000ED4BB0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALSQL scratch space for instance - VM-DBCENTER, db - 'netdb' is 'D:\netdb\Log\DPM_SQL_PROTECT\VM-DBCENTER\netdb_log.ldf'
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(32)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCUsnJournalHelper::ActivateJournal Volume Path = \\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\, max size = 0x0000000012C00000, alloc delta = 0x0000000001E00000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(526)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCUsnJournal::GetVolumeHandle Volume Path = \\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(544)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCUsnJournal::GetVolumeHandle Volume Path = \\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}, Volume Handle = 820
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(123)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALUsnJournalID    = 0x01D3D7BEB07743FE
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(124)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALFirstUsn        = 0x0000000000000000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(125)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALNextUsn         = 0x00000000002C0918
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(126)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALLowestValidUsn  = 0x0000000000000000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(127)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALMaxUsn          = 0x7FFFFFFFFFFFFFFF
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(128)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALMaximumSize     = 0x0000000012C00000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(129)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALAllocationDelta = 0x0000000000000000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(159)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALNeed to reset USN true
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(526)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCUsnJournal::GetVolumeHandle Volume Path = \\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(544)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCUsnJournal::GetVolumeHandle Volume Path = \\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}, Volume Handle = 820
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(466)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALCUsnJournalHelper::GetNextUsnInternal(vol:820)
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(488)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALUsnJournalID    = 0x01D3D7BEB07743FE
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(489)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALFirstUsn        = 0x0000000000000000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(490)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALNextUsn         = 0x00000000002C0918
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(491)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALLowestValidUsn  = 0x0000000000000000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(492)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALMaxUsn          = 0x7FFFFFFFFFFFFFFF
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(493)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALMaximumSize     = 0x0000000012C00000
13B01194 09/1006:19:04.19918usnjournalhelper.cpp(494)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALAllocationDelta = 0x0000000000000000
13B01194 09/1006:19:04.19931filterwrapper.cpp(48)[00000000037DEF70]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBNORMALLoaded DPMFSFilterWrapperDLL.dll
13B01194 09/1006:19:04.19905fsmtransition.cpp(111)[0000000000ED4180]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNINGFailed: Hr: = [0x801f000f] HasEventErrorCode: completion: 0xa10c, signature: 0xaabbcc00
13B01194 09/1006:19:04.19931aasubtask.cpp(906)[0000000000ED1590]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNING<?xml version="1.0"?>
13B01194 09/1006:19:04.19931aasubtask.cpp(906)[0000000000ED1590]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNING<Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2145452017" Reason="Error" CommandID="RAConfigureDeltaTracking" CommandInstanceID="96fe1088-65f4-4c31-af1b-c8b1eddec4fc" GuidWorkItem="987ecc0f-fc48-41d0-9f17-3007f54d1fef" TETaskInstanceID="615e7bf9-f1f8-4128-a0cf-812bb4f83aeb"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="998" DetailedCode="-2145452017" DetailedSource="2"/><RAStatus><RAConfigureDeltaTracking xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/StatusMessages.xsd"><ConfigureInfo><SqlConfig xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/CommonTypes.xsd"><ScratchSpaceLocation>D:\netdb\Log\DPM_SQL_PROTECT\VM-DBCENTER\netdb_log.ldf</ScratchSpaceLocation><TruncateDbLog>false</TruncateDbLog><VolumeConfig><JournalId>131686028128240638</JournalId><VolumeName>\\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\</VolumeName></VolumeConfig></SqlConfig></ConfigureInfo></RAConfigureDeltaTracking></RAStatus></Status>
13B01194 09/1006:19:04.19903runtime.cpp(1392)[000000000099C5D0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBFATALSubtask failure, sending status response XML=[<?xml version="1.0"?>
13B01194 09/1006:19:04.19903runtime.cpp(1392)[000000000099C5D0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBFATAL<Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2145452017" Reason="Error" CommandID="RAConfigureDeltaTracking" CommandInstanceID="96fe1088-65f4-4c31-af1b-c8b1eddec4fc" GuidWorkItem="987ecc0f-fc48-41d0-9f17-3007f54d1fef" TETaskInstanceID="615e7bf9-f1f8-4128-a0cf-812bb4f83aeb"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="998" DetailedCode="-2145452017" DetailedSource="2"/><RAStatus><RAConfigureDeltaTracking xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/StatusMessages.xsd"><ConfigureInfo><SqlConfig xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/CommonTypes.xsd"><ScratchSpaceLocation>D:\netdb\Log\DPM_SQL_PROTECT\VM-DBCENTER\netdb_log.ldf</ScratchSpaceLocation><TruncateDbLog>false</TruncateDbLog><VolumeConfig><JournalId>131686028128240638</JournalId><VolumeName>\\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\</VolumeName></VolumeConfig></SqlConfig></ConfigureInfo></RAConfigureDeltaTracking></RAStatus></Status>
13B01194 09/1006:19:04.19903runtime.cpp(1392)[000000000099C5D0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBFATAL]
13B01194 09/1006:19:04.23031filterwrapper.cpp(302)[0000000000ED54D0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNINGFailed: Hr: = [0x801f000f] : Volume Name = \??\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\
13B01194 09/1006:19:04.23031filterwrapper.cpp(81)[0000000000ED54D0]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNINGFailed: Hr: = [0x801f000f] : Encountered Failure: : lVal : EnsureFilterIsAttached(strVolume)
13B01194 09/1006:19:04.23031configuredeltasubtask.cpp(587)[0000000000ED1590]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNINGFailed: Hr: = [0x801f000f] : Volume Name = \\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\
13B01194 09/1006:19:04.23031configuredeltasubtask.cpp(405)[0000000000ED1590]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNINGFailed: Hr: = [0x801f000f] : VolumePath \\?\Volume{6c632aa3-2069-47ba-b4fc-fbeb45b2e22e}\
13B01194 09/1006:19:04.23005fsmstate.cpp(167)[0000000000ED2570]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNINGFailed: Hr: = [0x801f000f] : Encountered Failure: : lVal : pTransition->Execute(pEvent)
13B01194 09/1006:19:04.23005genericfsm.cpp(225)[0000000000EBAE10]615E7BF9-F1F8-4128-A0CF-812BB4F83AEBWARNINGFailed: Hr: = [0x801f000f] : Encountered Failure: : lVal : m_pCurrentState->SendEvent(pEvent, pNextState)


北京老马

Database backup issue in DPM

$
0
0

Hi,

I have installed dpm 2016 and SQL 2016 in another server.After creating the protection group databases(Single instance) is showing unable to creating protection(NT AUTHORITY\SYSTEM have sysadmin privileges).

Please suggest


Harsha


Specify alternate recovery destination takes a long time to populate

$
0
0

Hello,

I am in the process of trying to recover some databases to an alternate location.  The process goes fine until the Specify Alternate Recovery Destination screen.  When I try to expand the servername, it takes about 10 minutes to populate, after which I see the Volumes and Shares.  Is there any tweaks I need to do to my setup to have it remember locations?

DPM Consistency Check and SQL Express Full Backup

$
0
0

Team,

Thanks in advance, I've gone through multiple questions on the forums related to CC but still I'm little confused with CC and Express Full Backup of a SQL Database. So first let me share my thought what Consistency check does.

After the protection group has been created an initial replica job is triggered which will create a replica of the protected SQL DB on the DPM Storage pool. After the initial replica is created, my 15 minutes cycle of Incremental sync gets triggered which will bring only the log files of the SQL and will save it on the storage pool ( (Q1) I'm not sure if it is saved separately than the replica)

As the 15 minutes cycle only brings the changed block from the replica, DPM doesn't know if the blocks which DPM isn't bring has changed or not hence we've to perform the consistency check so that the Database replica should be similar on the DPM Storage pool.

(Q2 ) So if CC job does that then what does Daily Express Full Backup Does? It brings the changed block of the SQL DB/ MDF and then make the replica on the storage pool of DPM the same as the protected DB. Am i correct? or is there anything extra done by Express Full Backup. If Express Full Backup does only this then why I need to automatically check for Database consistency check? I will only use the first option of CC which says that run the CC once DPM finds any inconsistencies.

Is it possible to offset the recovery point creation time?

$
0
0

DPM 1807

I am creating SQL recovery points every 15 minutes. Due to starting at the top of the hour, DPM is seeing contention with some of our other jobs that are time dependant. Is it possible to offset the creation time so it starts with a 10 minute offset. So the recovery points would be about ~1:10a, ~1:35, ~1:40, etc. 

~joe

SQL Server version for DPM?

$
0
0
We are going to install Microsoft DPM 2019.  Do we need to purchase a separate license of DPM or can we use a runtime  SQL?  I have read the  following docs and am not clear.

https://docs.microsoft.com/en-us/system-center/dpm/install-dpm?view=sc-dpm-2019

https://docs.microsoft.com/en-us/system-center/dpm/prepare-environment-for-dpm?view=sc-dpm-2019#sql-server-database


https://www.ctm-computer.de/wp-content/uploads/sltsqlserver2016_standardandenterpriseservercal_runtime_.pdf

https://community.spiceworks.com/topic/384234-does-sql-server-come-free-with-data-protection-manager-2012-dpm-2012


I am hoping somebody here who is running DPM can provide us an answer from his/her experience.

New elements in group protection.

$
0
0

Hello!

I have installed DPM 2019 on WS 2019. I configured some VMs and MS SQL servers. What happen if in one of MS SQL instance someone add a new database?  For test I added new database and it event not listed in protection item of that group. In configuration of protection group is button "refresh", but it is greyed out in MS SQL. 
Does DPM is that clever and can add newly added item by self to protection? Maybe require is to config something yet? 

Your faithfully,
PK.


Viewing all 204 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>