I suggest you schedule the Inventory so you don’t have to do it manually again. Once you do that your storage will reflect the proper usage. Highlight all of your storage repositories, and select Inventory \ Inventory Now. That would be nice here too!īTW, once you enable this option – like I did, all of your storage repositories will still look full. The Welcome to Backup Exec 2014 screen contains three options: Getting Started: This option will provide helpful documentation and links about the product. This will display the installation language selections. I understand in BE 2012 there was an option to say to not delete your last job. Double click on the 'Browser.exe' file from the DVD media to launch a Backup Exec installation. We have 4 external drives that we back-up to. With tapes you have Tape1 Media1 etc and it could essentially work the same with backup-to-disk files but it doesnt seem to want to work the same. Since it deletes everything outside of your policy – once enabled, if you miss backups (lots) and time goes by and the policy says to delete it will even if it is the last job! With backup-to-disk it creates a whole bunch of Media files that seem to be treated differently to tapes. I think the odds are small of this happening but it is possible. However, it is important to understand that once this option is enabled, you could if you have odd schedules or outages, end up with nothing to restore. Now in Data Management you see the option – Allow Backup Exec to delete all expired backup sets. Then you should select the Storage Option. Start by clicking on the Yellow thing in the top left corner, then select Configuration and Settings, followed by Backup Exec Settings – as seen below. I did learn you could change this behavior using a switch in the Settings. So it was not surprising that I was always filling my storage. Meaning by default BE 2014 doesn’t delete any jobs that fall outside of your policy. So a little Google Fu confirmed that between 20 of Backup Exec this occurred. Meaning backup jobs older then my policy were not being cleared. So basically it looked like the policy’s were not working. I also noticed that when I deleted the other hosts that it did not clear up any space. Now backup Exec stores its catalog files under C:Program FilesSymantecBackup ExecCatalogsServer name. The Server is connected to a Dell Powervault 124T with a SCSI interface and i run backups for the server itself and other jobs that backup other servers across the LAN.
And I did not really want to add more storage since I was down to two hosts now. Im running Backup Exec 12.5 on Windows Server 2008 Standard 圆4. But yesterday when they ran out of storage again, I was a little irritated. I was always in a hurry and it is so easy to add a new Storage repository and any of the jobs could use it right away. But with only three or four hosts and not much of a change rate on them, I had attached a number of drives for Storage and they were all full. I am not backing up production data but just protecting my work so no big deal. I did change the policy to retain only 1 week. I have been in a hurry lately, and while working with Backup Exec I have had to keep adding disk as I added hosts.