Right click on the backup data that you no longer want, select Delete from Disk.  That should delete the backup chains associated with that previous job.  It’s under the Imported heading, so it appears that this is data that was in the repository without an associated job when the repo was scanned.  The other head, Disk, indicates that the backup data there is associated with an existing backup job.

Additionally you can delete it directly from the disk with delete. If you delete a Job directly, you may see this Disk as (orphaned). You can also delete from there.

Yes, it can be deleted from the disk directly and the repository rescanned to reflect the deletion.  I generally do not recommend deleting directly from the disk due to the possibility if deleting some restore points and invalidating a chain, as well as to alleviate any confusion of naming, etc.  This one looks like it should be pretty clear, but in general, I’d recommend sticking to the console whenever possible.

To be really technical, you can also browse the repository via the Files tab by browsing to the repository server.  That is how I had to delete encrypted restore points in a VCC repo after building a new server and reattaching to the repo, but not having the proper encryption password for the restore points.  When viewing the encrypted restore points, you don’t have the option to Delete from Disk.  The other option would be to delete them from the storage backend, but support for the VCC provider seemed to be having a hard time understanding what I was requesting and pointed me in the general direction of the files tab, but they weren’t very clear of what they were asking me to do.

@dloseke Do you have a screen print of the files table and deletion? Files tab lists the Microsoft Windows server. I just need to delete so that it does not have issues with the current backup job. 

Can I delete from Disk Imported as it lists backup job from Jan. Also the current job is set to Retentions policy 2 restore point. What does that mean I have backup with that job from Oct 5th through Nov 1st.

We deleted jobs from the folder that had older backups. Rename the folder in the backup server so that it will not write jobs to the folder. Job is running to the newer backup job.

@dloseke Do you have a screen print of the files table and deletion? Files tab lists the Microsoft Windows server. I just need to delete so that it does not have issues with the current backup job. 

Can I delete from Disk Imported as it lists backup job from Jan.

Yes, you can delete the restore points from the console in the Imported setting safely without affecting the restore points listed under the Disk heading.  Those are or should reside in different folders in the repository.  I say should because it sounds like you’ve made modifications to the file structure on the back-end of the repository.  If I understand what you’re saying correctly, it sounds like what you did shouldn’t affect anything aside from starting a new backup chain in a new folder.  The renamed folder will likely show up under the Imported heading if I recall correctly.

I’m having a hard time following this.  There’s a lot that can go into how many restore points are retained.  You may have it set to only retain 2 restore points but if you have active or synthetic fulls or GFS retention enabled, you’ll find that you’ll be keeping more than 2 restore points.  If you are only keeping two restore points with no active or synthetic fulls or GFS retention, then you’re in a Forever Forward Incremental configuration and you should enable health checks and defragmentation and compaction of the backup data.  I’m not sure how that correlates with your existing restore points without seeing how things are configured and their connection.