Forum Discussion

Alun's avatar
Alun
Level 4
10 years ago

Set SLP final copy expiration date after SLP cancellation

Hi,

I have followed https://www.veritas.com/support/en_US/article.TECH181975 to cancel further processing on an SLP managed duplication (Backup to AdvDisk1, duplicate to AdvDisk2,duplicate to tape for long term retention) as the final copy had been written to tape but was still showing as NOT_STARTED, consequently the re-spawning duplications failed with error 190.

I have run nbstlutil cancel -backupid CLIENT_1448054800 and the image now shows as COMPLETE, however although copies 1 and 2 show the correct expiration dates, copy 3 still shows as NOT_STARTED, its expire time and expire LC time still shows "Tue Jan 19 03:14:07 2038" or infinite.
 The Image's Required Expiration Date shows Thu Jan 01 00:00:00 1970.

I have attached a sanitised version of the nbstlutil list -U -backupid CLIENT_1448054800 for more information.

What further steps do I need to take to ensure that copy 3 expires at the end of the 7 year retention period?

Master Server = Windows Server 2008 R2 SP1 with Veritas Global Cluster

Media Server = Windows Server 2008 R2 SP1

Netbackup version = 7.5.0.7

Thanks,

Alun.

7.5
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • Nicolai's avatar
    Nicolai
    10 years ago

    Try nbstlutil cancel -backupid <backup_id> -force

    Seen in : http://www.veritas.com/docs/000017817

    If that don't work you may need to open a support call with Veritas.

  • Nicolai's avatar
    Nicolai
    Moderator
    10 years ago

    SLP's set the expiration time to infinity until the SLP is fully processes, as a security measures.

    I don't think you will be able to change the expiration time on a copy 3 as it still looking  to be under SLP control.

    Previous thread about same topic :

    https://www-secure.symantec.com/connect/forums/symantec-netbackup-difference-between-nbstlutil-cancel-lifecycle-and-inactive-lifecycle#comment-7809781

    But try the bpexpdate command:

    bpexpdate -recalculate -backupid CLIENT_1448054800 -d 12/01/22 -copy 3

    Please test the command first before using it on data - bpexpdate is not a forgiving command. If you told bpexpdate to expire data, it will do that straight away. 

     

  • Alun's avatar
    Alun
    Level 4
    10 years ago

    Hi Nicolai,

    The use of bpexpdate makes sense but will that change the status of copy 3 from 1 (NOT_STARTED) to 3 (COMPLETE)?

    If not, are you aware of a way to reset this value?

    Thanks,

    Alun.

  • Nicolai's avatar
    Nicolai
    Moderator
    10 years ago

    Try nbstlutil cancel -backupid <backup_id> -force

    Seen in : http://www.veritas.com/docs/000017817

    If that don't work you may need to open a support call with Veritas.

  • mph999's avatar
    mph999
    Level 6
    10 years ago

    I suspect as Nicolai suggests that this will need a bit of manual help via SQL to change the status.

    It might be possible to do it via cat_export / cat_import by exporting the 'header' info for the image, changing it and then importing back, but I would have to test that first.  Else it will be SQL.

  • Nicolai's avatar
    Nicolai
    Moderator
    10 years ago

    Any by SQL Martin mean manual changes to the EMM database. Absolute no-go for mortal end users :-)