Forum Discussion

Daryl_Kinnaird's avatar
Daryl_Kinnaird
Level 4
15 years ago

Basic Disk cleanup.

netbackup version: 6.5.5

OS version HP-UX 11.23  IA64

I have a basic disk that is not starting an image cleanup when it reaches the highwater mark.  Does anyone know if there is a  command to issue to get an image cleanup to run for the disk? 

7.1.x and Earlier
Backup and Recovery
Managing Backup Devices
NetBackup
Tip-How to
Troubleshooting
  • Marianne's avatar
    Marianne
    15 years ago

    Just to ensure that we're all on the same page - have another look at your last post:

    "I can verify that I don have a 2nd copy "

    I did not want to respond until now because I was hoping someone else understood what 'don' meant...

    If all backups have indeed been duplicated, please test a backup to that specific DSU. Ensure you have bpdm and bptm log directories on the media server. Cleanup attempt should be logged in bpdm. Backup attempt will be logged in bptm.

    If you have other DSU's that are cleaning up successfully, you need to carefully examine the properties from an O/S point of view - there is no logical reason why NBU would treat one DSU differently - unless O/S permissions are preventing the cleanup.

  • Yasuhisa_Ishika's avatar
    Yasuhisa_Ishika
    Level 6
    15 years ago
    Is this configured for disk staging? Have any images been duplicated? Images on non-staging BasicDisk remains for its retention period, and have never gone away.
  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    nbdelete -allvolumes -force

     

    See these posts for reference:

    https://www-secure.symantec.com/connect/forums/cant-delete-disk-pool

    https://www-secure.symantec.com/connect/forums/image-cleanup-error

     

  • Daryl_Kinnaird's avatar
    Daryl_Kinnaird
    Level 4
    15 years ago

    yes disk are set up for staging.  The staging off to tape works fine.  Just no image clean up even though disk was well past its highwater mark. 

     

    I'll give the nbdelete -allvolumes -force a try and see if that will clean up images already moved to tape and drop the percetage down.

  • Daryl_Kinnaird's avatar
    Daryl_Kinnaird
    Level 4
    15 years ago

    Ran the nbdelete -allvolumes -force and it came back with no images to delete.  From what I get from the man page for nbdelete is it is just removing deleted fragments.  Not making space for new images by deleting images that have already been staged to tape.

  • Nicolai's avatar
    Nicolai
    Moderator
    15 years ago

    The DSSU wil delete images already duplicated images when it reaches highwater mark.

    Do you status 129 - Disk volume full ?

  • Daryl_Kinnaird's avatar
    Daryl_Kinnaird
    Level 4
    15 years ago

    We  were getting 129's but since we are using storage unit groups we remvoed the disk not cleaning up space.  That way it would not be used.   I have checked the catalog and compared what is on the disk to see if a 2nd copy exits.  I can verify that I don have a 2nd copy on tape but still no clean up job when it reached the highwater mark to clear space for the backup to write.

  • Nicolai's avatar
    Nicolai
    Moderator
    15 years ago

    Do that DSSU have a a stagning windows defined.  See the admin guide on page 249 "Disk Staging Schedule dialog " of how to do

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    Just to ensure that we're all on the same page - have another look at your last post:

    "I can verify that I don have a 2nd copy "

    I did not want to respond until now because I was hoping someone else understood what 'don' meant...

    If all backups have indeed been duplicated, please test a backup to that specific DSU. Ensure you have bpdm and bptm log directories on the media server. Cleanup attempt should be logged in bpdm. Backup attempt will be logged in bptm.

    If you have other DSU's that are cleaning up successfully, you need to carefully examine the properties from an O/S point of view - there is no logical reason why NBU would treat one DSU differently - unless O/S permissions are preventing the cleanup.