Media Expiration Dates

If I have understood your question correctly ...

The assign time on a tape, is the date it is first used for a backup.  Once this is 'set' it should never change, until the tape expires.

In more detail.

A tape that is showing in the NBU gui, MUST be in the volume DB.

A tape is only 'moved' into the media database when it is first assigned for backups, or in other words, has data written to it.

Once the tape is expired (backups expire) it is remove from the media DB (will no longer show in bpmedialist command for example) and the assign time is 'removed', until such a time that it is reused.

vmquery commands for example works on the volume DB (is the tape known to NBU)

bpmedialist command works on the media DB (are there images on the tape).

Hope this helps,

Martin

Please show us output of this command for one of the tapes that you've highlighted:

nbemmcmd -listmedia -mediaid <media-id>

If we look at your vault profile, duplicated source tapes will expire within 168 hours.
So, what we see here is duplicated tapes (still showing retention level 5 (which you have customized to infinity) that will expire within 168 hours after duplication.

As per Martin's excellent post, the Assign Time was the first time that original backup was written - nothing to do with your 5 week retention level.
The tapes used for duplication should show retention level 2 (5 weeks) with relevant expiration date.

if the tapes are using for duplication with retenciton of 5 weeks, they should show retention level 2 but they are showing retenction level 5

along with above nbemmcmd command out put asked by Marianne, provide below outputs also

bpimmedia -mediaid <same media iD used in nbemmcmd command>  -L

bpimagelist -backupid <backup id from bpimmedia output> -L

Attached are the outputs. I did not get any output when I ran the bpimagelist cmd.

even the media is showing retenction level as 5 (currentlyinfinity), its showing expire date as 02/15/2013 23:36.

i understand that the retenction level 5 is customized, before customization does it used, and if yes, what was the retenction level set to that?

its not showing any entry, did you open your command promt as Administrator( right click ---> RUn as administrator)?

C:\Users\s-shahid.nawaz.ctr>bpimagelist -backupid nduapp26_1358750209 -L

no entity was found

I get the same result 'no entity found". The retention levels were all mixed for different policies. I am trying to make it consistent. Thanks

What we see in nbemmcmd output is not making sense.

It is quite possible that the retention levels could have been changed since I was trying to make it consistent. What I am trying to do is to calculate the expiration date for my tapes so that I can reuse them for my backups. For example. My daily backup tape for Monday. I load the tapes on Monday morning. The backups are scheduled to start at 8.00 PM on Monday. I have had the problem when the vault was set to start at 5.00 AM on Tuesday that the backups would not finish and the vault would start. I was worried that the vault would not be complete if it is writing at the same time that the backup is running. I moved the time of the vault to start at 10.00 AM.

I am having an issue with understanding the expiration time. I had assumed the since they backup started at 8.00 PM and the expiration was set for 7 days they would expire at 8.00 PM the next Monday. That way if I used the same tapes next Monday they would be good. But I discoverd the the expiration date is calculated from the last write time. For exanple. The backup started at 8.00 PM on Monday and continued till 5.00 AM on Tuesday, then the expiry date for that tape would be next Tuesday at 5.00 AM. That way the tape would not be available for writing  at 8.00 Monday. Does this make sense or am I complicating things. Any clarification would be appreciated. Thanks

The expiration time is calculated from when the backup starts.

Here is a backup from my system