Backup Exec D2D Retention Settings

Posted on 2011-10-26
Last Modified: 2012-05-12
I have a question on D2D backups regarding the Backup-To-Disk folder settings under DEVICES and the Media Set settings under MEDIA.

Originally, I had a particular Media Set configured to hold several weeks of data for a job that only runs once a week.  This backup is then immediately written to tape.

Due to disk space issues, I now only want to keep a single day’s worth of D2D data.  Under MEDIA, the overwrite protection was changed to 1 Day with an append period of 0 hours.

After this job ran, I was expecting to only have 1 Days worth of D2D data on hand.  Yet I am still seeing data with dates more than two weeks old within the Backup-To-Disk folder for this job under DEVICES as well as entries from several weeks of backups within the Media set folder for this job under MEDIA.

So it looks like you have to manually delete the old data as it is not auto removed after the retention settings are changed and the backup job is run with these new settings.

Yet I am seeing postings on line that seem to indicate manually deleting D2D data as being a bad idea.

So, how do you get rid of old D2D data after you have decreased your retention settings?

Backup Exec 2010 R3, SP1
2003 Server R2
Question by:acmi

    Accepted Solution

    Okay, so changing the number of days for overwrite protection does not affect the data already present in your D2D folders.

    That only works moving forward.

    So to delete the past, excess data:

    View the various entries in your D2D folder under DEVICES.
    Sort by date to see the entries you want to keep as well as the entries you want to delete.
    Keep in mind, you have to retain the B2Dxxxxxx and IMGxxxxxx files for each D2D backup you want to keep.
    Otherwise, highlight the dates you want to delete and choose ASSOCIATE WITH MEDIA SET
    From here, choose the RETIRED MEDIA option from the drop down list.
    Now choose to delete.

    This effectively removes the data from Backup Exec.

    Now delete the data from the location on your server where you store Backup Exec’s D2D directory:

    Locate the D2D folder in question.
    Sort by date
    Retain the IMGxxxxx directories that match the names of the IMGxxxxx files that you did not retire \ delete from Backup Exec
    Retain the BKF file that matches the backup sets you are retaining (will have similar dates)
    Retain the CFG files
    Delete the remaining IMGxxxxx directories.


    Author Closing Comment

    I answered my own question after getting with Symantec support.

    Featured Post

    Enabling OSINT in Activity Based Intelligence

    Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

    Join & Write a Comment

    Not many admins are aware that GPOs can be activated and deactivated time-based. Time to change that :)
    A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
    This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
    This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

    728 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now