I've not worked with Data Domain directly but this sounds familiar with other
MML issues I've seen.
This would seem to indicate a configuration problem on the Data Domain side.
I've seen cases where the media management side has its own retention criteria
set such that backups are expired/deleted pre-maturely.
I've also seen cases where the client can write to the media but cannot read
from it because of how it's configured.
So, I'd look at how the pools (or whatever DD is calling them) are configured
and make sure that your client is able to read and write to them correctly.
RF
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Matt Adams
Sent: Monday, May 09, 2016 10:24 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: DDBoost and RMAN difficulies
I'm having a weird problem with DDBoost and RMAN backups.
Databases are 11.2 and 12.1
DDBoost clients are 1.1.1
Every backup we do seem to be getting marked as EXPIRED immediately. The
backups succeed with no error messages or warnings, but if I do a crosscheck
immediately following the backup, all backup set pieces are marked as EXPIRED.
Anybody seen anything like this before?
Matt
**** This communication may contain privileged and/or confidential information.
If you are not the intended recipient, you are hereby notified that disclosing,
copying, or distributing of the contents is strictly prohibited. If you have
received this message in error, please contact the sender immediately and
destroy any copies of this document. ****
