cancel
Showing results for 
Search instead for 
Did you mean: 

NBU 7.0.1 Expired Media not moving back to scratch pool

Jenni
Level 2
Partner Accredited

Since upgrading to NBU 7.0.1 my customer's expired media are not moving back to the scratch pool. (NBU Master Server: Windows 2008)

I checked the emm database config using "C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listsettings -machinename master"
RETURN_UNASSIGNED_MEDIA_TO_SCRATCH_POOL="yes" 

Then I did a spot check of some media that should be expired to make sure that the media’s original pool was scratch media
"C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listmedia -mediaid 001335"
Volume Pool: NetBackup
Previous Pool Name: Scratch

====================================================================
Media GUID:                     85c7e62a-89d3-4f10-b3ad-ee03d63d0c95
Media ID:                       001335
Partner:                        -
Media Type:                     HCART3
Volume Group:                   ---
Application:                    Netbackup
Media Flags:                    1
Description:                    ---
Barcode:                        001335L3
Partner Barcode:                --------
Last Write Host:                deluge
Created:                        10/30/2009 15:09
Time Assigned:                  02/09/2011 17:30
First Mount:                    10/30/2009 19:37
Last Mount:                     02/14/2011 18:16
Volume Expiration:              -
Data Expiration:                02/28/2011 19:10
Last Written:                   02/14/2011 19:00
Last Read:                      -
Robot Type:                     NONE
Robot Control Host:             -
Robot Number:                   -
Slot:                           -
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               24
Maximum Mounts Allowed:         0
Media Status:                   FULL MPX
Kilobytes:                      565012457
Images:                         138
Valid Images:                   138
Retention Period:               1
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             4453036
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    deluge
Server Group:                   NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    1
Volume Pool:                    NetBackup
Previous Pool Name:             Scratch
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -
====================================================================

I tried to manually reassign empty tapes into the scratch pool with "C:\Program Files\Veritas\NetBackup\bin\admincmd>bpexpdate -deassignempty –force"
Deassigned 0 out of 693 media-ids found.

I have been able to get around this by selecting "freeze" and then "unfreeze" on the media and at this point they move to the scratch pool - but the next time they are due to expire again I have the same issue all over again.

I checked the forums and have also tried the following:

C:\Program Files\Veritas\Volmgr\vm.conf updated with
SCRATCH_POOL = Scratch

Checked that $INSTALL\NetBackup\bin\deassign_lock file does not exist

Checked that <install path>\Netbackup\bin\NOexpire file does not exist
 
Ran <install path>\Netbackup\bin\bpdbm -ctime <10-digit number> against the contents of <install path>\Netbackup\bin\bpsched.d\last_time_expired_media
1299023096 = Tue Mar 01 23:44:56 2011

 
Netbackup\bin\bpsched.d\CHECK_EXPIRED_MEDIA_INTERVAL file does not exist - do I need to create this?
 
I'm not sure what to check now, have I forgotton anything or should I log a symantec case?

Thank you
Jenni

3 REPLIES 3

Marianne
Level 6
Partner    VIP    Accredited Certified

Have a look at this TN (with downloadable fix): http://www.symantec.com/docs/TECH138266

Especially this section: Image Cleanup completes (Status 0) but is not cleaning images.

Jenni
Level 2
Partner Accredited

Hi Marianne,

I actually looked at this already but discounted it because my customer is not running any duplications in her environment. Would you recommend that I apply this anyway?

Thank you for your help

Jenni

Marianne
Level 6
Partner    VIP    Accredited Certified

Yes - the EEB fixes two problems:

  1. Duplications fail with Status 191/44/213 after upgrading a Windows Master Server to 7.0.1.
  2. Image Cleanup completes (Status 0) but is not cleaning images.