05-31-2013 11:56 PM
You don't, if expired 'normally' it has gonr for good.
Perhaps you take a disk array across to a new server, the fragments are still on the disk in this example and so could be imported.
It is also possible to expire the images but only from the catalog, without actually deleting the backup data (fragments) on the disk. Again, these could be imported as they haven't actually been deleted.
Martin
@Martin :
Solved! Go to Solution.
06-01-2013 01:04 PM
nbdelete logs into the admin log, so you could look in there.
It runs as part of the image cleanup, so I'm not sure why you are so concerned about it. If the image cleanup has run the disk images have been deleted, simple as that.
Martin
06-01-2013 02:25 AM
Once the image goes past its exxpire time, it is delete from the catalog by bpexpdate.
This runs as part of the NBU cleanup job (every 12 hrs by default)
The cleanup jobs runs multiple commands, bpexpdate is one, and after this run nbdelete -allvolumes, this is the command that actually deletes the fragments from the disk.
As far as I am aware, nbdelete runs straight after bpexpdate, so if the images are not showing in the catalog (bpimagelist command for example) they will have been deleted from the disk.
THe only way to tell for sure, is to look on the disk at OS level, and see if the fragments are there - easy to find as the files contain the backupid.
Martin
06-01-2013 05:47 AM
Thanks Martin,
Please reply to my below query:
@Martin :
06-01-2013 07:46 AM
I did answer, what part is not clear ?
They are deleted when nbdelete is run, during the image cleanup.
If the retention is over then they will be deleted from disk when the next image cleanup runs.
06-01-2013 09:49 AM
How can i check if nbdelete has not run or has run?
06-01-2013 01:04 PM
nbdelete logs into the admin log, so you could look in there.
It runs as part of the image cleanup, so I'm not sure why you are so concerned about it. If the image cleanup has run the disk images have been deleted, simple as that.
Martin