Unsolved
This post is more than 5 years old
1 Rookie
•
18 Posts
0
746
April 19th, 2018 12:00
DD2500 - Source and Destination have Different Used %
Good afternoon!
We've accidentally come across an issue in the past week, and are having some difficulty pinning down the cause/resolution.
As a quick summary, our DD2500 units (with a single Replication Context between them) have different Utilized Capacities, even though the number, size, and percent utilized on our Virtual Tapes are the same between the two.
Here's the full breakdown:
- For the past couple of months, we've been at- or near-capacity on our Data Domains.
- About two weeks ago, we had a network issue that caused our Source and Destination DDs to lose connection to each other for a period of time. As a result, the replication context more or less lost its mind, and the Destination indicated that it was "full". To try and resolve this issue, we performed a Replication Break/Resync.
- After the Resync completed, the Source Data Domain is showing ~90% used capacity... however, the Destination device is showing ~40% used.
- We checked all of the tapes - both within the Data Domain interface and on the AS400 unit that is being backed up - and found that the Source and Destination have the exact same number of tapes, with each tape reporting the exact same Used Percentage and the exact same data.
- As an addendum - neither the Source nor the Destination Device has any other data being stored on it; just our AS400 Backups.
Has anyone else experienced this issue before? If so, how did you resolve it?
Otherwise, any ideas?
Thanks!
No Events found!


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
April 23rd, 2018 11:00
Destination is expected to be less a bit than source, but this is way too much indicating some split brain between perhaps cache tables. I would suggest to open a support ticket with engineering.
zwoodcock_370587
1 Rookie
•
18 Posts
0
April 25th, 2018 07:00
We have opened a ticket, but haven't received any response... probably because I wasn't informed until after I opened the ticket that we did not renew our support contract.
After some more digging, it appears that the devices are getting VASTLY different Compression Factors - the Source is showing 82.2% while the Destination is showing 90%. That difference accounts for all of the "ghost data" we're seeing on the Source.
At this point, I'm not sure if there is anything we can do without Support's assistance... but that's not likely to happen.