Preview only show first 10 pages with watermark. For full document please download

Creating Effective Retention Policies

   EMBED


Share

Transcript

Barracuda Backup Creating Effective Retention Policies This article refers to the Barracuda Backup Legacy Release firmware or newer. Important Before defining data retention policies, make sure you have a clear understanding of data and email message compliance rules as well as your organization's record retention policies. Use retention policies to define the length of time you retain historic data based on daily, weekly, monthly, or annual time intervals. This allows you to manage data storage and growth. Important Purging applies to historic file revisions only; your current data is never impacted by a retention policy. Use the Barracuda Backup web interface to verify retention policies are in place and enforced. You can create different retention policies for different sets of data including: Files Data backed up by the Barracuda Backup Agent (Exchange, SQL, system state) Email messages How it Works Data is retained based on a traditional grandfather-father-son (daily-weekly-monthly) rotation model. You specify how long to keep daily, weekly, monthly, and yearly backups through data retention policies. When you define a retention policy, begin by selecting either a preset template or a previously defined policy as a starting point. This helps you avoid creating multiple retention policies for the same sets of data. You can create one policy for all of the computers and data sources on a Barracuda Backup Server, or create different policies that include subsets of the data. Revision Timelines Historic data is retained based on your revision timeline settings. Depending on how your data is backed up, revision timelines are treated in the following manner: Data backed up using the Barracuda Backup Agent treats Sunday as the end of week in accordance with the ISO date standard. Data backed up using a NAS protocol considers weeks as 7 day periods beginning each month, and requires a separate timeline for removed data. Retention policies are based on retaining different types of data and different revisions for different periods of time. For example, in the General Documents Revision Template in the table below, all revisions are kept based on daily, weekly, and monthly revisions. The predefined timeline templates use the revision timelines defined in the following table. Revision Template General Documents Keep All Revisions 5 days Creating Effective Retention Policies 1/3 Keep Daily Revisions 1 week Keep Weekly Revisions 1 month Keep Monthly Revisions 1 year Keep Yearly Revisions never Barracuda Backup Dump Files Never 1 week 1 month 3 months Never Financial Data 10 days 2 weeks 2 months 18 months 6 years Keep No Historic Data Never Never Never Never Never Exchange Data 2 weeks Never Never Never Never Virtualization 1 day SQL Server Database Never 2 weeks 1 month Never Never Never Never Never Never Removed Email Timeline You can select how long to retain removed email messages. After the specified period of time, removed messages are purged. You can specify in days, weeks, months, or years, or select never or forever. Creating Effective Retention Policies 2/3 Barracuda Backup Creating Effective Retention Policies 3/3