DPM 2012 R2 - ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746)
Almost all of our backups are running and completing fine but we have 4 tape job's that will begin to backup then error out at about the same point all the time with the same Error Details (ID 2019 Details: An existing
connection was forcibly closed by the remote host (0x80072746)). All 4 tape job's that fail are on the same 2 clustered servers, but we do have 3 job's on the same server cluster that will complete. Any help would be greatly appreciated, Thanks.
This is a list of our setup:
Single DPM 2012 R2 server running on Windows 2012 R2 Datacenter
2 clustered file servers running Windows 2012 R2 Standard
Data Deduplication is enabled on both file servers
Tape Library is Dell PowerVault TL2000 (LTO5)
Disk storage is Dell PowerVault MD3200 direct attached with about 75TB
March 27th, 2014 8:39pm
Hi,
Same problem here.
Sometimes the backup to tape finished with the error id 2019 and sometimes with 3311.
The specifications are approximatively the same:
DPM 2012 R2 on Windows 2012 R2
Tape Library Dell PowerVault 24T (LTO 4)
Disk Storage EonStor with 10TB
The backup to tape job process 10 servers and the problem appear always on the same server. A Windows 2012 R2 with data deduplication activated. In the past we already had this type of problem, our workaround is to backup the directory in place of the all
disk. In this case we lost the benefit of data deduplication for the backup but it works. This time it's not possible to apply this workaround because the rehydrated data overtake our backup disk capacity :(
It's the second problem with the backup of deduplicated volume. The first one reported the backup to disk as failed and force a consistency check. This problem was solved by Microsoft after
3 months
with the last update.
How can I explain to my boss that we must live without backup of critical datas during this lap of time ? And now another problem to backup to tape....
I seriously investigate other solutions to backup our Datacenter. Veeam seems to work like a charm with all configuration.Since many years I push to work with the same editor for all the
chain of the process, thinking that these guys know the specificity of their product better than others, but it seems that I'm not right.
And please, stop to add a link with "More Information" who redirects to a Page Not Found. It's very frustrating when you have a problem. This link never sends me to a existing page regardless the kind of problem.
Thanks
David
April 15th, 2014 10:44am
Hi,
I am also experiencing the same issue with backing up a deduped volume. The data deduplication volume backs up to disk without error but then fails when being backed up to tape with the same Error Details (ID 2019 Details: An existing connection
was forcibly closed by the remote host (0x80072746)).
Craig
May 20th, 2014 4:31pm
Hello All
Same circumstances and same errors, backing up a volume which we have recently enabled deduplication.
Anyone managed to find a cause/solution?
May 23rd, 2014 7:20am
we have the same issue - opened up a support case by microsoft
May 23rd, 2014 9:40am
We are having the same issue
A Windows 2012 R2 Update 1 Datacenter DPM 2012 R2 server.
Data Deduplication is enabled on a local volume on the host.
Its a 2 TB NAS.
Tape drive is a Dell PowerVault TL2000 LTO 5.
Has anybody has any sort of resolution with the cases that they have opened?
May 29th, 2014 7:39pm
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 6:12am
nope, but a week of pain un-optimizing everything and needing to run multiple consistency checks, and now recovery volumes that are the size of the replica volumes. (seriously hoping we can shrink those one the retention range passes)
extremely disappointed and tainted. the dedup itself worked wonderfully on our FS but DPM didn't like 2 out of the 4 volumes we enabled dedup.
-
Edited by
PCAU
Friday, May 30, 2014 6:15 AM
May 30th, 2014 9:12am
Hi all,
After the last problem with deduplicated volume for synchronisation (Microsoft take 3 month to resolve it) and now a new one to do the backup to tape we have moved to Veeam and all is working well now.
Sorry Microsoft, I'm a supporter of your products, but let us with problem to do a backup since november (first problem, and now tape problem) is not acceptable. You must understand that backup is critical and be more responsive on this kind of problem.
David
May 30th, 2014 9:39am
We are also experiencing this problem on DPM 2012 R2 (RU2) on Server 2012 R2 Update 1 backing up a deduplicated volume on a Server 2012 R2 U1 file server.
Tape drive is a Quantum Superloader3 with an LTO6 drive.
June 5th, 2014 10:08pm
We are also experiencing the same issue with 2 deduped volumes but the rest are fine.
DPM 2012R2 RU2 Server 2012R2 Update 1
June 13th, 2014 12:26pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 3:18pm
I finally found a work around for my environment. Add DWORD entries with names "ConnectionNoActivityTimeout" and "ConnectionNoActivityTimeoutForNonCCJobs" in path "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\Agent" and set the value to 7200 on DPM server. Now recycle the DPMRA service. Worked like a charm.
Now, you may be wondering, why did I set the timeout to such a large value?
Well, it was heavy handed, I tried 900 first, and the problem remained.
At 7200 it went away. A lower value may work just fine in your environments.
-
Edited by
commoner31
Saturday, June 21, 2014 3:18 PM
June 21st, 2014 6:18pm
Microsoft has confirmed that there is an issue and they will work out a solution for a coming up DPM 2012 R2 Update Rollup
Bueschu
June 24th, 2014 11:40am
Guys any update on this issue?
We turned on data deduplication on our production file server last week and now backup to tape job for one of the volumes fails with
ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746)
DPM 2012R2 RU2
Tape Library Dell TL4000 with 2 x LTO6 drives.
Regards, Andrew
July 3rd, 2014 7:08am
Also Have the same issue on DPM 2012 R2 RU2 with File server with Dedup enabled.
Please assist
August 14th, 2014 11:04am
still wating for the update from ms
August 15th, 2014 2:03pm
We are also experiencing the same issue when we enabled deduplication on our file server. Currently running DPM 2012R2 UR3
August 25th, 2014 4:07am
Same here. I tried setting the timeouts as propopsed and even higher values, no help.
September 3rd, 2014 12:17pm
Hi,
For the outlined issue (Tape backup jobs fail with error ID 2019 (0x80072746) I would suggest first ensure we are in supported configuration based on the below matrix. If so then the next best course of action would be
to open a support case for further investigation.
Below table shows supported / unsupported configurations for dedup protection.
Protected Server OS
|
DPM Server OS
|
DPM Versions
|
Dedup protection Supported
|
|
|
|
|
Windows 2012
|
Windows 2012
|
DPM 2012 SP1 / R2
|
Y
|
Windows 2012
|
Windows 2012 R2
|
DPM 2012 R2
|
Y
|
Windows 2012 R2
|
Windows 2012 R2
|
DPM 2012 R2
|
Y
|
Windows 2012 R2
|
Windows 2012
|
DPM 2012 SP1/R2
|
N
|
Windows 2012 R2
|
Windows 2012 R2
|
DPM 2012 SP1
|
N
|
***************
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."
September 4th, 2014 10:13pm
Unfortunately support is useless.
We had an open case and below is the "case closure email"
We ended up switching from volume protection to folder protection which means DPM stores its replica in de-duped state.
Hi Andrew,
It was my pleasure to assist you during the troubleshooting of your DPM issue. This refers to Microsoft support case ID (114070811599411). I am providing you with a summary of the key points of the case for your records. If you have
any questions please feel free to call me. You can reach me using the contact information below and referencing the case ID.
ISSUE: For F\: drive on file server ADL-SRV1 tape backup fails with error" ID 2019 Details: An existing connection was forcibly closed
by the remote host (0x80072746)"
TROUBLESHOOTING: Checked for volume corruption.
CAUSE: Known issue with DPM 2012 R2 - tape backup of - de-dup volumes (Bug).
SOLUTION: work around:
Run the windows power shell command Start-DedupJob X: Type Scrubbing full ReadOnly Where X: is drive letter of deduped volume.
For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.
As per our last discussion, I am closing this support case (114070811599411). The case can be reopened anytime if you have further queries by just dropping an email to me.
I must say that it was a pleasure to work with you.
Thank you for partnering with Microsoft.
September 5th, 2014 3:03am
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 12th, 2014 11:52pm
Thank you for sharing that naydonov.
Any acknowledgement from MS on this "known bug" and/or upcoming resolution, i.e potentially in UR4?
October 13th, 2014 2:38am
I can confirm that our supported configuration:
Protected Server OS: Windows 2012 R2
DPM Server OS: Windows 2012 R2
DPM Server Product: DPM 2012 R2
Supported Configuration: Y
exhibits this problem when attempting to tape a disk replica containing a dedupicated volume.
In light of the useless support (see case 114070811599411 above), logging this with MS is pointless.
Our best bet is to pray that this can be fixed in an upcoming rollup.
time to pull out the prayer mat.
-
Edited by
The Fellenator
Sunday, October 12, 2014 11:53 PM
does eveyone have their prayer mat?
October 13th, 2014 2:52am
Since some of these issues aren't directly the fault of DPM itself, it's possible the solution may come in the form of an update rollup for the operating system instead.
Can anyone confirm whether the October 2014 update rollup for Windows Server 2012 R2 KB2995388, containing included fix KB2959146 for stability in Data Deduplication for Windows Server 2012 R2 fixes this problem as well?
October 16th, 2014 1:10pm
My very first test run with KB2995388 installed on the DPM server when taping a replica of a de-duped volume was successful.
Now to see if this success continues during an overnight taping session of same.
October 21st, 2014 9:43am
Can you confirm your success? because we've got the same issues with tape backups of dedupped data...
I already forwarded your findings to our case at Microsoft, just to see what Microsoft have to say about this..
October 22nd, 2014 9:28am
I'll have to tell you on Monday, this de-duped volume only gets taped once a week on weekends.
October 22nd, 2014 9:43am
Okay, please let me know, thanks in advance !
October 22nd, 2014 10:46am
from my memory of this issue the first few tape backups after a successful replica creation of a deduped volume worked fine. This issue didn't appear until scheduled dedup optimization jobs ran over the course of a few days as the data changed.
Thanks for reporting back The Fellenator, very keen to hear how it progresses although I wish MS would officially acknowledges this issue.
October 23rd, 2014 7:26am
unfortunately, it' still failing to backup to tape, so no change even with KB2995388 installed. :(
October 27th, 2014 3:22am
October 27th, 2014 6:54am
Okay 2 bad, thanks for sharing the test results ..
October 27th, 2014 10:00am
Has anyone been able to test whether DPM 2012 R2 CU4 resolves this problem?
The release notes for KB3009516 don't mention anything tape or de-dupe related as having been fixed, so I'm not hopeful.
Maybe I should have more faith, or at least, point my prayer mat more towards Redmond?
November 5th, 2014 2:59am
CU4 hasn't touched this either.
November 24th, 2014 5:42pm
Has anybody received an update from Microsoft about this issue, by chance? We've been unable to back up our deduplicated volumes for quite some time. Unfortunately removing deduplication is not an option and the workarounds don't work.
December 15th, 2014 8:08pm
Hi @all,
originally, we had one file server with all data on it (deduplicated volume). Then all of a sudden, the error appeared.
After testing several tips without any effort we have moved some data to a new server with a deduplicated volume. Now backup runs smoothly on both Servers without any further errors. Seems as if the amount of data is also crucial for this problem.
January 8th, 2015 12:00pm
I noticed that our latest tape backup went through without failure, but having checked, the data has written over without the de-deduplication savings. So a volume that is on the disk backup as 500GB is going to tape as 700GB+
Very strange.
January 9th, 2015 11:46am
Description of Update Rollup 5 for System Center 2012 R2 Data Protection Manager
https://support.microsoft.com/kb/3021791
Backup job for dedupe-enabled volume on Windows 2012 R2 fails. For example, Data Protection Manager backup might fail for following setup:
- Data Protection Manager2012 R2 is installed on Windows Server 2012.
- Data Protection Manager is protecting a dedupe-enabled volume on Windows Server 2012 R2.
February 11th, 2015 4:57am
Still having the same problem, also with the DPM 2102 R2 Rollup 5 installed. protected and DPM server are all 2012R2. I am the only one left where it does not work?
March 7th, 2015 5:19pm
Nope you are not...
Installed the update, rebooted the server, deployed the agent updates, rebooted all of those too... For nothing... Thanks for keeping us occupied MS... hope we get a real solution soon.
Back to surfing and googling for alternative solutions for me... Glad I've got my backup to disk, hope the building never burns down...
March 12th, 2015 8:27am
Hey MS,
We are getting Similar issue with the below error message:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Log Name: DPM Backup Events
Source: DPM-BackupEvent
Date: 13/03/2015 15:43:27
Event ID: 33223
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: KP1.********.com
Description:
Backup job for datasource: F:\ on production server: f*******com failed.
Backup job failed at: 13/03/2015 15:43:27.
Backup Type: tape backup.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="DPM-BackupEvent" />
<EventID Qualifiers="0">33223</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-13T15:43:27.000000000Z" />
<EventRecordID>588</EventRecordID>
<Channel>DPM Backup Events</Channel>
<Computer>.*******.com</Computer>
<Security />
</System>
<EventData>
<Data>Backup job for datasource: F:\ on production server: *******.com failed.
Backup job failed at: 13/03/2015 15:43:27.
Backup Type: tape backup.</Data>
<Data>33223</Data>
<Data>488bf7fa-1c7c-4343-b5f5-38edc67f1faa</Data>
<Data>00000000-0000-0000-0000-000000000000</Data>
<Data>d9ba874f-b0f2-426f-8161-0fb851780e7d</Data>
<Data>00000000-0000-0000-0000-000000000000</Data>
<Data>2015-03-13T15:43:27</Data>
<Data>failed</Data>
<Data>tape</Data>
<Data>2036</Data>
</EventData>
</Event>
We also notice that MSDPMservice is crashing and below are the logs at the time of failure:
0888 08A8
03/13 16:18:23.154
09 MsdpmService.cs(237)
NORMAL OnStartAsync - Initializing MSDPM
0888 08A8
03/13 16:18:23.233
09 servicemodule.cpp(426)
NORMAL CServiceModule::InitializeSecurity
0888 08A8
03/13 16:18:23.373
09 ApplicationSettings_expanded.cs(3790)
WARNING Failed to detect DC, treating as non dc - retVal:2114
0888 08A8
03/13 16:18:23.389
09 servicemodule.cpp(592)
WARNING InitializeSecurity: Error in obtaining Account Sid for Sql Account (null).
0888 08A8
03/13 16:18:23.545
68 DpmThreadPool.cs(121)
WARNING Caught unhandled exception : System.Configuration.ConfigurationErrorsException: Unable to detect if machine is dc or not
0888 08A8
03/13 16:18:23.545
68 DpmThreadPool.cs(121)
WARNING at Microsoft.Internal.EnterpriseStorage.Dls.Utils.DcDetector.CheckIfMachineIsDc()
0888 08A8
03/13 16:18:23.545
68 DpmThreadPool.cs(121)
WARNING at Microsoft.Internal.EnterpriseStorage.Dls.Utils.ApplicationSettings.CheckIfMachineRoleDc()
0888 08A8
03/13 16:18:23.545
68 DpmThreadPool.cs(121)
WARNING at Microsoft.Internal.EnterpriseStorage.Dls.Utils.ApplicationSettings.GetMSDPMTrustedMachinesAccountName()
0888 08A8
03/13 16:18:23.545
68 DpmThreadPool.cs(121)
WARNING at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CServiceModule.InitializeSecurity(CServiceModule* )
0888 08A8
03/13 16:18:23.561
68 DpmThreadPool.cs(149)
WARNING Attempting to write error to the event log Unable to detect if machine is dc or not
0888 08A8
03/13 16:18:23.686
02 EventManager.cs(143)
NORMAL Logging event to NT log from DpmThreadPool.cs(163): FatalServiceError
0888 08A8
03/13 16:18:23.858
68 DpmThreadPool.cs(170)
WARNING Attempting to invoke Watson
0888 08A8
03/13 16:18:23.873
09 everettexception.cpp(761)
CRITICAL Exception Message = Unable to detect if machine is dc or not of type System.Configuration.ConfigurationErrorsException, process will terminate after generating dump
It seems like its a common issue with all the users around the glob without any resolution. Any formal update on this would be appreciated.
March 14th, 2015 10:41am
We also are having this issue as of last weekend.
March 25th, 2015 9:25am
bump.
March 31st, 2015 9:03am
Hi,
I have talked to MSFT in the context of another error (console crashes after RU5 installation, none of the repair advices worked) and he told me that this is still a known bug but he cannot say if there will be a hotfix or if we have to use the workaround
given by nardonov.
He told me that it could help to deactivate deduplication, create a full backup without dedup and then reactivate dedup - after RU5.
This is of course no easy workaround. I don't know if our server can handle data without dedup or if I have to extend the volume...
In the meantime I will try the PowerShell command.
April 22nd, 2015 8:24am
Has anybody been able to confirm whether UR6 for DPM 2012 R2 resolves this?
https://support.microsoft.com/en-us/kb/3030574
Again I'm hopeful, since improved deduplication support is one of the mentioned fixes....
May 12th, 2015 3:54am
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
2 hours 44 minutes ago
May 18th, 2015 8:26am
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
-
Edited by
Bernie137
Tuesday, May 19, 2015 4:56 AM
May 18th, 2015 12:25pm
File: Win 2012R2, Dedup Enabled
DPM: Win 2012R2, DPM2012R2 with RU6
It is still the same problem with RU6:
(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))
Could anybody explain what I have to do here?
'For DPM replica Perform these steps so that some windows power-shell commands can be ran to detect corruption:
IMPORTANT NOTE: DO NOT LEAVE DEDUP ENABLED ON DPM REPLICA VOLUME.'
yes, the workaround suggested involves checking (and repairing) the integrity of the dedupe chunkstore of the REPLICA. Once this has been completed, the important note is to ensure no actual de-dupe passes are run on the replica itself by the DPM server
on an ongoing basis, so the idea is to ensure all de-dupe related tasks for the volume are disabled. You DONT want it to run de-dupe real-time, and you DONT want it to run a scheduled de-dupe pass either. In my opinion whats happening is that we're
basically running a fancy version of chkdsk /f on the volume involved to repair logical corruption. Immediately after which you should run a DPM consistency check of the volume against the protected server's volume to ensure the contents is made to re-match
exactly afterwards.
May 28th, 2015 4:04am
Even with Win2012R2, DPM2012R2 with UR6, and the protected server also being Win2012R2 and all fully patched, we're still getting the same error about an hour or so in (155GB) when taping the replica (750GB):
"(ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))"
June 1st, 2015 3:59am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
22 hours 4 minutes ago
June 1st, 2015 5:01am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
I also have the exact same problem, Fully updated, works fine on all servers apart from the deduped one
-
Edited by
OSCA Support
Monday, June 01, 2015 9:37 AM
June 1st, 2015 9:00am
We're also continuing to get the same issue on the same operating systems and DPM patching levels as you. It seems that I can occasionally get it to work if I do a consistency check and then re-run the tape job but if it does work, it will be only
once before it goes back to the errors again.
June 3rd, 2015 4:10pm
Hi,
for us, the following PowerShell command did the trick:
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
After that, DPM is able to fully backup all data to tape again. I cannot say whether UR6 does the same thing or makes some corrections concerning this error.
June 10th, 2015 11:05am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
Heiko Bernd
57 minutes ago
vergessen
June 11th, 2015 2:45am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
Heiko Bernd
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
Heiko Bernd
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
Heiko Bernd
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
Heiko Bernd
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
Heiko Bernd
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
HB DBJW
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
HB DBJW
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
HB DBJW
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
HB DBJW
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
HB DBJW
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
Hi,
Sorry, the trick or workaround does not help for us.
Start-DedupJob -Volume <Drive letter>: -Type Scrubbing
Shows on our server:
Type ScheduleType StartTime Progress State Volume
---- ------------ --------- -------- ----- ------
Scrubbing Manual 0 % Queued D:
But backup on tape goes in the known Error 3311.
After starting backup on tape, I see in the DPM Queue the tape backup job and waits 5 minutes but 0 MB transfered. After 5 minutes get error 3311. In the event log of file server find: 8:15:04 service DPMRA is running; 8:20:43 service DPMRA is stopped -thats
all.
-
Edited by
HB DBJW
Thursday, June 11, 2015 6:45 AM
vergessen
June 11th, 2015 6:44am
You have to wait for the job to complete if you did not already do that ;-)
June 11th, 2015 7:28am
No, on the protected server.
What seems strange to me is that backing up the protected server to disk works without any problems, only backing up to tape causes this issue. What is the difference here? Does data have to be "unduplicated" before writing it to tape?
June 17th, 2015 5:23am
No, on the protected server.
What seems strange to me is that backing up the protected server to disk works without any problems, only backing up to tape causes this issue. What is the difference here? Does data have to be "unduplicated" before writing it to tape?
June 17th, 2015 5:23am
did you run this on the DPM server?
June 17th, 2015 7:44am
did you run this on the DPM server?
June 17th, 2015 7:44am
You have to wait for the job to complete if you did not already do that ;-)
The job takes only 10 Seconds and is truly done on protected server before take backup starts.
I think data have to be "unduplicated" before writing it to tape. But "unduplicating" does never start for tape backup.
June 22nd, 2015 8:20am
I am definitely still having this error in my environment. I haven't been able to fully test the "fixes" in UR5 because it broke deduplication on my backups for a FS cluster (which was an exceptionally painful support ticket). I was finally able
to install UR6, but the tape backup issue persists.
June 22nd, 2015 11:04am
I have found a workaround for our environment.
We have a protection group which includes 4 servers for file backup. Two of these servers are 21012r2 with dedup. Only one of them has this problem which i have discriped above. It is his volume D:\
First i have tested the volume C:\ form the same problematic server and tape backup was no problem. Volume C:\ has no dedup enabled. Now I have removed this problematic server volume D:\ complete from the protection group and keeped all data. Next i have
changed the protection group again an choose only all first level subfolders from the volume D:\ but not the root D:\ itself. Now i see all subfolders from volume D:\ in the protection group and backup on tape is NO PROBLEM! In an first test i have choosen
only one subfolder of volume D:\
Maybe is there a problem with the folder "System Volume Information" which now is not included?
Could anyone do a test like me and reporting here?
-
Edited by
HB DBJW
22 hours 10 minutes ago
July 16th, 2015 5:24am
I have found a workaround for our environment.
We have a protection group which includes 4 servers for file backup. Two of these servers are 21012r2 with dedup. Only one of them has this problem which i have discriped above. It is his volume D:\
First i have tested the volume C:\ form the same problematic server and tape backup was no problem. Volume C:\ has no dedup enabled. Now I have removed this problematic server volume D:\ complete from the protection group and keeped all data. Next i have
changed the protection group again an choose only all first level subfolders from the volume D:\ but not the root D:\ itself. Now i see all subfolders from volume D:\ in the protection group and backup on tape is NO PROBLEM! In an first test i have choosen
only one subfolder of volume D:\
Maybe is there a problem with the folder "System Volume Information" which now is not included?
Could anyone do a test like me and reporting here?
-
Edited by
HB DBJW
Thursday, July 16, 2015 9:36 AM
July 16th, 2015 9:20am
I have found a workaround for our environment.
We have a protection group which includes 4 servers for file backup. Two of these servers are 21012r2 with dedup. Only one of them has this problem which i have discriped above. It is his volume D:\
First i have tested the volume C:\ form the same problematic server and tape backup was no problem. Volume C:\ has no dedup enabled. Now I have removed this problematic server volume D:\ complete from the protection group and keeped all data. Next i have
changed the protection group again an choose only all first level subfolders from the volume D:\ but not the root D:\ itself. Now i see all subfolders from volume D:\ in the protection group and backup on tape is NO PROBLEM! In an first test i have choosen
only one subfolder of volume D:\
Maybe is there a problem with the folder "System Volume Information" which now is not included?
Could anyone do a test like me and reporting here?
-
Edited by
HB DBJW
Thursday, July 16, 2015 9:36 AM
July 16th, 2015 9:20am
I have found a workaround for our environment.
We have a protection group which includes 4 servers for file backup. Two of these servers are 21012r2 with dedup. Only one of them has this problem which i have discriped above. It is his volume D:\
First i have tested the volume C:\ form the same problematic server and tape backup was no problem. Volume C:\ has no dedup enabled. Now I have removed this problematic server volume D:\ complete from the protection group and keeped all data. Next i have
changed the protection group again an choose only all first level subfolders from the volume D:\ but not the root D:\ itself. Now i see all subfolders from volume D:\ in the protection group and backup on tape is NO PROBLEM! In an first test i have choosen
only one subfolder of volume D:\
Maybe is there a problem with the folder "System Volume Information" which now is not included?
Could anyone do a test like me and reporting here?
-
Edited by
HB DBJW
Thursday, July 16, 2015 9:36 AM
July 16th, 2015 9:20am
I have found a workaround for our environment.
We have a protection group which includes 4 servers for file backup. Two of these servers are 21012r2 with dedup. Only one of them has this problem which i have discriped above. It is his volume D:\
First i have tested the volume C:\ form the same problematic server and tape backup was no problem. Volume C:\ has no dedup enabled. Now I have removed this problematic server volume D:\ complete from the protection group and keeped all data. Next i have
changed the protection group again an choose only all first level subfolders from the volume D:\ but not the root D:\ itself. Now i see all subfolders from volume D:\ in the protection group and backup on tape is NO PROBLEM! In an first test i have choosen
only one subfolder of volume D:\
Maybe is there a problem with the folder "System Volume Information" which now is not included?
Could anyone do a test like me and reporting here?
-
Edited by
HB DBJW
Thursday, July 16, 2015 9:36 AM
July 16th, 2015 9:20am
HB - I've seen this workaround mentioned before (and have seen it as a "solution" for Microsoft support cases on the issue). The problem with this is that since you're no longer backing up a volume, the backup isn't deduplicated. While this may
work for environments with extra space to allocate toward backups, it most certainly will not in mine. I've had long-fought battles with MS already regarding backups that were being taken as non-optimized after the functionality was broken in UR5.
For what it's worth, the scrubbing dedup job on the source data did NOT fix this issue in my environment.
July 16th, 2015 10:28am
The problem with this is that since you're no longer backing up a volume, the backup isn't deduplicated.
I think a backup on tape could never be deduplicated all files are wriiten nativ on tape and thats the reason why backup on tape is failing. While starting backup for a dedup volume anything takes too long time for "undedup" and reaches a timeout
after round 5 minutes. In different environments is the number of files involved by dedup different. So in some cases backup works fine and other scenarios backup failed.
July 17th, 2015 5:31am
I had the same Problem. After installing DPM 2012 R2 UR6 on the DPM and file server and KB2995388 on the file server, I removed the datasource from the DPM Protection Group, started the scrubbing Job on the file Server and readded the Datasource.
Now the tape backup works properly.
July 28th, 2015 3:14am
I have tried the same in the past and found that the tape jobs may work for a while but they eventually experience the same issues again.
Maybe UR7 will help, though I see no mention of any similar issue in the list of fixes.
July 31st, 2015 1:40pm