(219) the required storage unit is unavailable

[Hendrik_Bezuide]

I am getting this error when I want to make backups.

1. I did run this command

  nbstlutil stlilist -image_incomplete -U

   Getting this info    

root@erpbkmaster # nbstlutil stlilist -image_incomplete -U
Image erprdn01_1334467820 for Lifecycle prod-disk-to-tape-monthly is IN_PROCESS
  Copy to erpbk-tape-group is NOT_STARTED
Image sapsq1app20_1461910061 for Lifecycle dev-qa-disk-to-tape-daily is NOT_STARTED
  Copy to erpbk-tape-group is NOT_STARTED
Image sapsq1app20_1461910113 for Lifecycle dev-qa-disk-to-tape-daily is NOT_STARTED
  Copy to erpbk-tape-group is NOT_STARTED

 bpexpdate -deassignempty -force

Deassigned 0 out of 462 media-ids found.

2.  When I am on my media server 2 on my nbudisk4 it only shows 272 MB available, in it there ia a lot of old images for 2014

3. When I put this dates in catelog, I can not find the image there.

4. is is on advancedisk

-rw-------   1 root     root        1024 Dec 24  2014 erpqas_1419384005_C1_HDR.1419384005.info
-rw-------   1 root     root       32768 Dec 24  2014 erpqas_1419384005_C1_F1.1419384005.img
-rw-------   1 root     root        1024 Dec 24  2014 erpqas_1419384005_C1_F1.1419384005.info
-rw-------   1 root     root        1024 Dec 30  2014 saprp1ci00_1419969613_C1_HDR.1419969613.img
-rw-------   1 root     root        1024 Dec 30  2014 saprp1ci00_1419969613_C1_HDR.1419969613.info
-rw-------   1 root     root        1024 Dec 30  2014 saprp1ci00_1419969613_C1_F1.1419969613.info
-rw-------   1 root     root     261543690240 Dec 31  2014 saprp1ci00_1419969613_C1_F1.1419969613.img
-rw-------   1 root     root        1024 Mar 24  2015 saprd1ci00z_1427231710_C1_HDR.1427231710.img
-rw-------   1 root     root        1024 Mar 24  2015 saprd1ci00z_1427231710_C1_HDR.1427231710.info
-rw-------   1 root     root        1024 Mar 24  2015 saprd1ci00z_1427231710_C1_F1.1427231710.info
-rw-------   1 root     root     252450701312 Mar 25  2015 saprd1ci00z_1427231710_C1_F1.1427231710.img

5. how can I get rid of this.

[Marianne]

Can you confirm that disk volumes are ALWAYS accessible when Image Cleanup job runs? Image Cleanup job on the master server will expire image catalog and also issue 'nbdelete -allvolumes' to cleanup disk. If media server and/or disk is not available, you should see a non-status 0 exit code for Image Cleanup Job with info in Details tab of the job. You need bpdm log on the media server to trace disk cleanup actions. Problem is that logs are by default kept for 28 days. So, if there was an issue a couple of months or years ago and images have expired on the master server, it will not be easy to find information. Tracing original expiration date will be time consuming: Have a look at the name of the image file on the disk. It should contain the client name and and image number (client-name_10-digit-number) You can check policy for this client and verify retention levels in the policy schedule(s). Next, check the 10-digit number to determine when backup was done: \veritas\netbackup\bin\bpdbm -ctime <10-digit-number> You can now work out from this date and schedule retention level when image expired. You can safely delete these files from backup disk and keep an eye on Image Cleanup jobs and bpdm file to troubleshoot cleanup issues.