Barracuda Backup Administrator's Guide v42

1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
1.1 What's New in Barracuda Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 What's New in Barracuda Cloud-to-Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Supported Servers and Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.1 Microsoft Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3.1.1 Best Practices for Microsoft Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3.2 Microsoft Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3.2.1 Best Practices for Microsoft Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3.3 Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.3.1 Best Practices for Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.3.2 Microsoft SQL Server Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.3.4 Microsoft SharePoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.3.5 Microsoft Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.3.6 Microsoft Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.3.7 Microsoft Office 365 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.3.7.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.3.7.1.1 Why You Need to Back Up Office 365 Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.3.7.1.2 How to Determine Amount of Storage Used in Office 365 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.3.7.1.3 How to Reauthorize an Office 365 Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.3.7.1.4 Understanding Cloud-to-Cloud Backup Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.3.7.1.5 How to Schedule an Office 365 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.3.7.1.6 Cloud-to-Cloud Backup Overview - Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.3.7.1.7 Getting Started with Cloud-to-Cloud Backup - Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.3.7.2 Cloud-to-Cloud Office 365 Exchange Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.3.7.2.1 Understanding What Exchange Online Data is Backed Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.3.7.2.2 How to Configure Impersonation for Exchange Online Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.3.7.2.3 How to Configure an Exchange Online Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.3.7.2.4 How to Schedule an Exchange Online Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1.3.7.2.5 How to Restore an Exchange Online Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
1.3.7.2.6 How to Download an Exchange Online Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
1.3.7.3 Cloud-to-Cloud Office 365 OneDrive for Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1.3.7.3.1 Understanding What OneDrive for Business Data is Backed Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
1.3.7.3.2 How to Configure Impersonation for OneDrive for Business Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1.3.7.3.3 How to Configure a OneDrive for Business Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
1.3.7.3.4 How to Schedule a OneDrive for Business Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1.3.7.3.5 How to Download a OneDrive for Business Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1.3.7.3.6 How to Restore a OneDrive for Business Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
1.3.7.4 Cloud-to-Cloud Office 365 SharePoint Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
1.3.7.4.1 Understanding What SharePoint Online Data is Backed Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
1.3.7.4.2 How to Configure Site Collection Administration for SharePoint Online Data Sources . . . . . . . . . . . . . . . . . . . 67
1.3.7.4.3 How to Configure a SharePoint Online Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.3.7.4.4 How to Schedule a SharePoint Online Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
1.3.7.4.5 How to Download a SharePoint Online Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
1.3.7.4.6 How to Restore a SharePoint Online Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1.3.8 Microsoft Windows Small Business Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
1.3.9 Windows Client Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
1.3.10 VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
1.3.10.1 Best Practices for VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
1.3.11 Linux Systems, Macintosh OS X, AIX, Unix, and Novell NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
1.3.12 GroupWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
1.3.13 IBM Domino Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
1.3.14 MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
1.3.15 Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
1.3.16 FirstClass Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
1.3.17 Network Addressable Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
1.3.18 SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
1.4 Deployment Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
1.4.1 Barracuda Backup Deployment Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
1.4.2 Site-to-Site Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
1.4.2.1 Configuring Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
1.4.3 Site-to-Cloud Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
1.4.4 Cloud-to-Cloud Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
1.4.5 Local Control Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
1.4.5.1 Understanding Local Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
1.4.5.2 Configuring Email Notifications for Local Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
1.4.5.3 Configuring Backup Alerts and Reports in Local Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
1.4.5.4 How to Add a Replication Target in Local Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
1.4.6 Barracuda Cloud Storage Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
1.4.7 Virtual Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
1.4.7.1 Understanding Barracuda Backup Vx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
1.4.7.2 Deploy Barracuda Backup Vx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
1.4.7.3 How to Expand Barracuda Backup Vx Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
1.4.7.4 Barracuda Backup Vx Replication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
1.4.7.4.1 How to Set Up a Barracuda Receiver Vx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
1.4.7.5 How to Migrate a Barracuda Backup Vx to New Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
1.4.8 Public Cloud Hosting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
1.4.8.1 Amazon Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
1.4.8.1.1 Replication to Amazon Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
1.4.8.1.2 Restore to Amazon Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
1.4.8.1.3 Replication and Restore to Amazon Web Services FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
1.5 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
1.5.1 Step 1 - How to Install the Barracuda Backup Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
1.5.1.1 How to Add Customers to the Partner Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
1.5.2 Step 2 - How to Configure Barracuda Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
1.5.3 Step 3 - How to Configure Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
1.5.4 Step 4 - Data Backup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
1.5.5 Energize Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
1.6 Appliance Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
1.6.1 Dashboard Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
1.6.1.1 Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
1.6.1.2 How to Monitor Backup Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
1.6.1.3 How to Unlink a Barracuda Backup Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
1.6.1.4 Task Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
1.6.2 Backup Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
1.6.2.1 Understanding Source-Based Deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
1.6.2.1.1 Barracuda Agent versus File Share Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
1.6.2.2 Understanding Data Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
1.6.2.3 Backing Up Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
1.6.2.3.1 Supported Data Sources by Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
1.6.2.3.2 Maximum Number of Simultaneous Backup Jobs by Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
1.6.2.3.3 Microsoft Exchange Server and Exchange Server DAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
1.6.2.3.4 Microsoft Hyper-V Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
1.6.2.3.5 Microsoft SQL Server Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
1.6.2.3.6 VMware Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
1.6.2.3.7 How to Back Up Microsoft Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
1.6.2.3.8 How to Back Up MySQL Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
1.6.2.3.9 Understanding IBM Domino Server Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
1.6.2.3.10 How to Configure GroupWise Message-Level Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
1.6.2.3.11 How to Set Up a Root Account to Back Up Macintosh OS X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
1.6.2.3.12 How to Back Up Linux/UNIX Data Using SSHFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
1.6.2.3.13 Understanding Changed Block Tracking on Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
1.6.2.3.14 How to Enable Changed Block Tracking through the Barracuda Backup Web Interface . . . . . . . . . . . . . . . . . 266
1.6.2.3.15 How to Back Up Network Addressable Storage - NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
1.6.2.3.16 How to Back Up FirstClass Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
1.6.2.3.17 How to Back Up NFS Mounts with the Barracuda Backup Agent (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
1.6.2.3.18 How to Back Up NSS Mounts with the Barracuda Backup Agent (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
1.6.2.3.19 How to Back Up an Oracle Database on Linux Using RMAN and Barracuda Backup . . . . . . . . . . . . . . . . . . . 272
1.6.2.3.20 How to Back Up an Oracle Database on Microsoft Windows Using RMAN and Barracuda Backup . . . . . . . . 274
1.6.2.3.21 How to Configure an Agent-Based Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
1.6.2.3.22 How to Back Up Lustre Mounts with the Barracuda Backup Agent (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
1.6.2.3.23 How to Back Up the Barracuda Message Archiver with Barracuda Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
1.6.2.4 Replication Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
1.6.2.4.1 Configuring a Replication Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
1.6.2.4.2 How to Temporarily Disable a Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
1.6.2.4.3 Managing the Data Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
1.6.2.4.4 How to Set Rate Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
1.6.2.4.5 How to Set an Alternate Rate Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
1.6.2.4.6 Understanding the Data Replication Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
1.6.2.5 Schedules Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
1.6.2.5.1 Granular Scheduling - Keep or Remove Data Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
1.6.2.6 Rate Limit Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
1.6.2.7 Exclusions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
1.6.2.7.1 How to Create Directory-Level Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
1.6.2.7.2 How to Exclude a Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
1.6.2.7.3 Sample Exclusion Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
1.6.2.8 Retention Policies Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
1.6.2.8.1 Understanding Retention Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
1.6.2.8.2 How to Create Retention Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
1.6.2.8.3 Understanding Barracuda Offsite Vaulting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
1.6.2.8.4 Creating Effective Retention Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
1.6.2.8.5 Retention Policy Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
1.6.2.9 Watched Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
1.6.3 Restore Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
1.6.3.1 VMware Server Recovery and Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
1.6.3.1.1 How to Restore a Virtual Machine to its Original Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
1.6.3.1.2 How to Restore a Virtual Machine to a Different Host Protected by Barracuda Backup . . . . . . . . . . . . . . . . . . . 325
1.6.3.1.3 How to Restore a Virtual Machine to an Alternate VMware Host not available through the Barracuda Backup
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
1.6.3.1.4 VMware Data Recovery Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
1.6.3.1.5 How to Restore VMware Guest Systems Using LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
1.6.3.1.6 How to vMotion a LiveBooted Virtual Machine from Barracuda Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
1.6.3.2 Microsoft Exchange Server Recovery and Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
1.6.3.2.1 How to Restore a Microsoft Exchange Server 2013 and Higher Database to a Recovery Database . . . . . . . . . 334
1.6.3.2.2 How to Restore a Microsoft Exchange 2010 Server by Overwriting an Existing Database . . . . . . . . . . . . . . . . 338
1.6.3.2.3 How to Restore a Microsoft Exchange 2010 Server to a Recovery Database . . . . . . . . . . . . . . . . . . . . . . . . . . 341
1.6.3.3 Microsoft SQL Server Database Recovery and Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
1.6.3.3.1 How to Restore a Microsoft SQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
1.6.3.3.2 How to Restore a SQL Server 2008 Master Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
1.6.3.3.3 How to Restore a Microsoft SQL Database to a Point-in-Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
1.6.3.3.4 How to Restore a Microsoft SQL Server Database to a Flat File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
1.6.3.3.5 How to Restore Microsoft SQL Server 2012 and Above Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
1.6.3.3.6 How to Restore Microsoft SQL Server 2012 Database to a File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
1.6.3.4 Microsoft Hyper-V Recovery and Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
1.6.3.4.1 How to Restore a Microsoft Hyper-V Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
1.6.3.5 Microsoft Windows Server Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
1.6.3.5.1 How to Restore a Microsoft Server 2012 Active Directory Object from the Active Directory Recycle Bin . . . . . 369
1.6.3.5.2 How to Enable Active Directory Recycle Bin on Windows Server 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
1.6.3.5.3 How to Restore a Microsoft Server 2008 R2 Active Directory Object from the Active Directory Recycle Bin . . . 373
1.6.3.5.4 How to Enable Active Directory Recycle Bin on Windows Server 2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
1.6.3.6 Barracuda LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
1.6.3.6.1 Understanding LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
1.6.3.6.2 Getting Started with LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
1.6.3.6.3 Understanding the LiveBoot Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
1.6.3.6.4 How to Add a Virtual Machine to LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
1.6.3.6.5 How to Manage LiveBoot Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
1.6.3.6.6 How to Restore a LiveBoot Virtual Machine to Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
1.6.3.6.7 How to Boot a VMware Guest System as a Clone Using LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
1.6.3.6.8 How to Shut Down and Destroy a Virtual Machine Recovered Using LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . 386
1.6.3.7 Barracuda Cloud LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
1.6.3.7.1 Understanding Cloud LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
1.6.3.7.2 Getting Started with Cloud LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
1.6.3.7.3 Understanding Cloud LiveBoot Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
1.6.3.7.4 How to Add a Virtual Machine to Cloud LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
1.6.3.7.5 How to Manage Cloud LiveBoot Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
1.6.3.7.6 How to Restore a Cloud LiveBoot Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
1.6.3.7.7 How to Download or Destroy a Virtual Machine from Cloud LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
1.6.3.7.8 Troubleshooting Cloud LiveBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
1.6.3.8 Restore Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
1.6.3.8.1 Understanding Restore Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
1.6.3.8.2 How to Search for Items Using the Restore Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
1.6.3.8.3 How to Restore Data Using the Restore Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
1.6.3.9 Restoring from Local and Offsite Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
1.6.3.10 How to Recover Backed Up Data Using the Download Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
1.6.3.10.1 Example - Restore Data Using the Local Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
1.6.3.11 How to Restore from a Replication Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
1.6.3.12 How to Restore SharePoint Objects Using Kroll Ontrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
1.6.3.13 Restoring Windows System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
1.6.3.13.1 How to Restore Windows Server 2008 and 2012 System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
1.6.3.13.2 How to Restore Windows Server 2008 Domain Controller System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
1.6.3.14 How to Restore Exchange and GroupWise Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
1.6.3.15 How to Restore a Windows System to Bare Metal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
1.6.3.15.1 How to Create a Bootable USB Flash Drive from the Bare Metal Restore Live CD ISO . . . . . . . . . . . . . . . . . 437
1.6.3.16 How to Restore a Linux Server Using Bare Metal Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
1.6.3.17 How to Restore a File or Folder within a VMDK using LiveBrowse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
1.6.3.18 How to Browse Hyper-V VHD and VHDX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
1.6.3.19 How to Perform a Physical to Virtual Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
1.6.3.20 On-Demand Purging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
1.6.3.21 How to Restore a SQL Instance after a Bare Metal Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
1.6.3.22 Recovering Data After a Ransomware Attack - Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
1.6.4 Reports Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
1.6.4.1 How to Configure Daily Summary Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
1.6.4.2 How to Download a Detailed Backup Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
1.6.4.3 How to Generate a Large Items Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
1.6.4.4 How to Manually Send a Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
1.6.4.5 Understanding Audit Logging in the Cloud UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
1.6.5 System Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
1.6.5.1 Firmware Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
1.6.5.1.1 Firmware Upgrade Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
1.6.5.1.2 How to Manually Upgrade Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
1.6.5.1.3 How to Upgrade Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
1.6.5.1.4 How to Upgrade Firmware on a Local Control Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
1.6.5.2 Barracuda Backup Appliance Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
1.6.5.2.1 How to Update Appliance Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
1.6.5.3 Software Downloads Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
1.6.5.4 Advanced Graphs Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
1.6.6 Admin Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
1.6.6.1 Users Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
1.6.6.1.1 Managing Your Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
1.6.6.1.2 Managing User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
1.6.6.1.3 How to Set User IP Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
1.6.6.1.4 How to Set Product Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
1.6.6.2 Email Notifications Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
1.6.6.3 Display Groups Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
1.6.6.4 Link a Backup Appliance Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
1.6.6.4.1 How to Link a Barracuda Backup Product as a User or Reseller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
1.6.6.4.2 How to Manage Accounts and Barracuda Backup Appliances as a Reseller . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
1.6.6.5 AWS Credentials Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
1.7 Cloud Backup Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
1.7.1 Status Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
1.7.2 Backup Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
1.7.2.1 Retention Policies Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
1.7.2.2 Schedules Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
1.7.3 Restore Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
1.7.3.1 How to Restrict Search to Current Folder in Restore Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
1.7.4 Reports Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
1.7.5 System Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
1.7.6 Admin Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
1.7.6.1 Users Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
1.7.6.2 Email Notifications Page - Cloud Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
1.8 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
1.8.1 Backup Security and Site-to-Site Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
1.8.2 Barracuda Cloud Storage Standards and Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
1.8.3 Policy-Based Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
1.8.4 How to Secure Your Barracuda Backup Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
1.8.5 Barracuda Backup Login Authentication Using Multi-Factor Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
1.8.6 File Encryption Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
1.9 System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
1.9.1 Barracuda Backup Replacement and Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
1.9.2 Barracuda Backup Replacement and Data Migration FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
1.9.3 Site-to-Site and Site-to-Vx Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
1.9.4 Replacing a Failed Barracuda Backup Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
1.9.5 How to Shut Down a Barracuda Backup Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
1.9.6 How to Wipe a Barracuda Backup System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
1.9.7 Barracuda Backup Panel Indicators, Ports, and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
1.9.8 Barracuda Backup Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
1.9.9 How to Physically Install the Barracuda Backup Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
1.9.10 Barracuda Backup Network Interface Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
1.9.11 Barracuda Backup Data Transfer IP Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
1.9.12 Understanding the Barracuda Backup Service Data Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
1.9.13 System, Platform, and Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
1.9.14 How to Open a Support Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
1.10 Troubleshooting and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
1.10.1 Understanding Why the Barracuda Backup Agent Moves to a New Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
1.10.2 Understanding Why Data is not Replicating to an Offsite Barracuda Backup Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
1.10.3 How to Troubleshoot Using the Barracuda Backup Agent (Windows) Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
1.10.4 How to Resolve Low Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
1.10.5 How to Change the Barracuda Backup Agent Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
1.10.6 How to Change the Barracuda Linux Backup Agent Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
1.10.7 How to Change the SQL Recovery Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
1.10.8 How to Resolve "Error with SQL authentication" Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
1.10.9 How to Resolve Microsoft Exchange 2010 Large Message Restore Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
1.10.10 How to Resolve Snapshot Backup Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
1.10.11 How to Resolve "Agent database moved to different location" Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
1.10.12 How to Resolve "Error Creating Snapshot" Error During ESX/ESXi Virtual Machine Backup . . . . . . . . . . . . . . . . . . . . . . 579
1.10.13 How to Resolve "Error Reading Object" Error During ESX or ESXi Virtual Machine Backup . . . . . . . . . . . . . . . . . . . . . . 580
1.10.14 How to Resolve "Error Removing Snapshot" Error During ESX/ESXi Virtual Machine Backup . . . . . . . . . . . . . . . . . . . . . 581
1.10.15 How to Resolve VMware Guest Machine Backup Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
1.10.16 How to Resolve Slow Incremental Backup with VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
1.10.17 How to Resolve "Failed to connect to backup agent software" Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
1.10.18 How to Resolve "Incremental backups cannot be performed while circular logging is enabled" Error . . . . . . . . . . . . . . . . 586
1.10.19 How to Resolve "An error occurred during agent backup initialization" Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
1.10.20 How to Resolve "Unable to back up virtual machines with independent disks" Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
1.10.21 How to Resolve "VMDK is larger than the maximum size supported by datastore" Error . . . . . . . . . . . . . . . . . . . . . . . . . 590
1.10.22 How to Resolve "Error backing up selected object" Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
1.10.23 How to Check Volume Shadow Copy Services Driver State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
1.10.24 Monitoring Windows System Performance During Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
1.10.25 How to Increase Backup Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
1.10.26 How to Move the VSS Snapshot Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
1.10.27 Troubleshooting Exchange Server 2010 DAG Backup Log Files do not Truncate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
1.10.28 Understanding "Unable to Quiesce Disk" Warning During ESX/ESXi Virtual Machine Backup . . . . . . . . . . . . . . . . . . . . . 601
1.10.29 How to Resolve Message-Level Backup Errors in Microsoft Exchange 2010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
1.10.30 Troubleshooting Exchange Server 2010 Log Truncating Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
1.10.31 How to Resolve "A Volume (drive) that was previously backed up is no longer there and being backed up" Warning . . . 606
1.10.32 How to Resolve "An error occurred during agent backup initialization" Error - Event ID 8193 - Diff Area . . . . . . . . . . . . . 607
1.10.33 How to Resolve Hyper-V Error During Backup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
1.10.34 How to Resolve "File System Snapshot released, this backup is invalid" Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
1.10.35 How to Resolve "Error opening object" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
1.10.36 Resolve the "Failure while using USN journal" Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
1.10.37 Resolve the "EWS connection error" for Specific Users in Message-Level Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
1.10.38 Understanding Why WindowsApps Folder Restore Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
1.10.39 Understanding Why VMware Virtual Machine Returns Incorrect Changed Sectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
1.11 Agents and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
1.11.1 Barracuda Backup Agent (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
1.11.1.1 How to Install and Use the Barracuda Backup Agent (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
1.11.1.2 How to Silently Install, Upgrade, or Remove the Barracuda Backup Agent (Windows) . . . . . . . . . . . . . . . . . . . . . . . 622
1.11.1.3 Understanding the Barracuda Backup Agent (Windows) File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
1.11.1.4 How to Manually Move the Barracuda Backup Agent (Windows) Database to an Alternate Location . . . . . . . . . . . . 625
1.11.2 Barracuda Backup Agent (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
1.11.2.1 How to Install and Use the Barracuda Backup Agent (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
1.11.2.2 How to Manually Move the Barracuda Backup Agent (Linux) Database to an Alternate Location . . . . . . . . . . . . . . . 630
1.11.3 Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
1.11.3.1 Understanding the Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
1.11.3.2 Understanding the Backup Export Tool Master Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
1.11.3.3 How to Install and Configure the Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
1.11.3.4 How to Manually Export Data Using the Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
1.11.3.5 How to Schedule Automatic Data Export Using the Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
1.11.3.6 How to Restore Exported Data Using the Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
1.11.3.7 Backup Export Tool Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
1.11.3.8 Backup Export Tool Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
1.11.3.9 Configuring Encryption and Compression in the Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
1.11.3.10 Configuring Backup Schedule Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
1.11.3.10.1 Scheduling Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
1.11.3.10.2 Media Rotation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
1.11.3.10.3 Schedule Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
1.11.3.10.4 Mode Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
1.11.3.10.5 Media Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
1.11.3.10.6 Running Jobs in Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
1.11.3.11 Managing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
1.11.3.11.1 Device Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
1.11.3.11.2 Device Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
1.11.3.11.3 Sharing Storage Devices on a SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
1.11.3.11.4 Working with Tape Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
1.11.3.12 How to Schedule Restore and Verify Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
1.11.3.13 Advanced Restore and Verify Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
1.11.3.14 How to Test Your Setup with the Barracuda Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
1.11.3.15 How to Export Data to AWS Storage Gateway-VTL Using the Backup Export Tool . . . . . . . . . . . . . . . . . . . . . . . . 706
1.11.3.16 How to Restore Archived Data from an AWS Storage Gateway Using the Backup Export Tool . . . . . . . . . . . . . . . 712
1.11.3.17 Understanding AWS Storage Gateway-VTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
1.11.4 Barracuda Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
1.12 Online Service Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Barracuda Backup Administrator's Guide - Page 7
Overview
The Barracuda Backup is an affordable solution that combines on-premises backup and unlimited cloud storage to efficiently protect your data.
Quickly and securely store data in the cloud or multiple offsite locations. Barracuda Backup removes duplicate data inline at the block level to
reduce traditional backup storage requirements up to 25 times, while reducing backup windows and bandwidth requirements.
If you have deployed Barracuda Essentials for Office 365 Complete Protection and Compliance, see Barracuda Cloud Backup.
Where to Start
Use the Barracuda Backup Quick Start Guide included with your device, or for detailed installation and configuration steps, go to the Getting
Started section.
Deployment
Select your deployment based on your environment and data sources:
Supported Servers and Data Types
Key Features
See What's New in Barracuda Backup for a list of new features by firmware version.
Web Interface
Appliance Web Interface
Cloud Backup Web Interface
Agents, Tools, and Mobile Access

Barracuda Backup Agent (Windows)
Barracuda Backup Agent (Linux)
Backup Export Tool
BCC iOS Mobile App for iPhone and iPod Touch
BCC Mobile App for iPad
Barracuda Networks Android Mobile Application
Troubleshooting
See the Troubleshooting and error messages section.
Copyright © 2015, Barracuda Networks Inc.

What's New in Barracuda Backup
What's New in Version 6.4.02
The following new major features are added to Barracuda Backup version 6.4.2
Replication and Restore to Amazon Web Services (AWS)

Replication to AWS (S3) – Barracuda Backup now supports replication to AWS as replication option in addition to Barracuda
Cloud
Restore to AMI – Restore Barracuda Backup virtual image backups to an AWS EC2 instance
Enhancements
Open support tunnel from the web UI [BNBS-28823]

SMB versions 2 and 3 support [BNBS-28423]
Cloud LiveBoot HyperV: VHDX Generation 2 support [BNBS-27388]
Link to purge items directly from the Large Items report [BNBS-27013]
Resolved
Backup jobs fail due to other process [BNBS-29081]

Multi-select restore fails without timestamp [BNBS-28587]
Warn before offsite vaulted data is removed by a user [BNBS-28573]
Once enabled, Offsite Vaulting cannot be disabled. [BNBS-28571]
Backup schedules skipped intermittently [BNBS-28557]
Summary reports not sending for some schedules [BNBS-27904]
LiveBrowse not working with vhdx files [BNBS-27592]
Show custom retention policies in the web UI [BNBS-26935]
The following new major features are added to Barracuda Backup version 6.4
New Barracuda Backup Dashboard and Overview pages

Physical Barracuda Backup to Receiver Vx Replication
Available on Barracuda Backup models 190 through 690
Receiver Vx can be provisioned directly from within the web UI
Priced as an additional subscription added to the Barracuda Backup
Enhancements
HTTPS support for uploading a CA-signed certificate in Local UI

Virtual Barracuda Backup can now replicate to and from a physical Barracuda Backup
Resolved
Summary reports display incorrect share names [BNBS-27913]

VSS SQL Backup does not fail when Differential chain is broken, causing incomplete revisions [BNBS-14279]
Message Level schedules shown in duplicate [BNBS-22684]
Cloud LiveBoot list of virtual machines does not always load [BNBS-27669]
Uncaught Message-level exception causes backup failure [BNBS-27371]
User roles created in the web UI do not sync locally for Helpdesk and Overview users [BNBS-28391]
VSS SQL Backup does not fail when Differential chain is broken, causing incomplete revisions [BNBS-14279]
Summary reports not sending for some schedules [BNBS-27904]
Bare Metal Restore ignores drive selections [BNBS-16441]
Sending multiple email alerts after firmware upgrade [BNBS-27633]
Bare Metal Restore ignores drive selections [BNBS-16441]
Uncaught message-level errors cause backup failure [BNBS-27170]
Agent fails on VSS components containing relative paths [BNBS-27304]
"No disks found" for LiveBoot causes boot failure [BNBS-27861]
The following new major features are added to Barracuda Backup version 6.3.04
Cloud LiveBoot updated web interface and support for Microsoft Hyper-V
LiveBoot updated web interface
Added Helpdesk and Status user roles
Support for VMware vSphere version 6.5

What's New in Version 6.3
Performance enhancements
New Backup Agent introduces multi-streaming improving initial backup and restore times
New replication queueing system eliminates bottlenecks with highly transactional data sets
File shares backups with large directory trees spawn streams more efficiently
Backup Export Tool expanded functionality
Archive to AWS Storage Gateway-VTL
Added support for VMware image exports
Barracuda Cloud-to-Cloud Backup for Office 365
Microsoft SharePoint Online
Other enhancements
Multi-account management view switcher
Hyper-V restores to an alternate host
SQL VDI flat file restores from web UI
Ability to boot a virtual machine Clone using Barracuda LiveBoot
On-Demand Purging
Granular Scheduling – Item selection has moved to the backup schedule which allows you to granularly select specific sets of data to
back up and the ability to configure multiple schedules for each source, each with different sets of data selected
Keep or Remove Data Options in Granular scheduling
Manually Send a Summary Report
Configure Daily Summary Reports
Download a Detailed Backup Report
Configure Agent-Based Data Sources
New VMware Data Source Configuration
Barracuda introduces Cloud-to-Cloud Backup for Microsoft Office 365

Go to https://www.barracuda.com/directtocloud to learn more and sign up for a risk-free trial
Back up historical revisions to external media using Yosemite Server Backup
Support physical to virtual restores to VMware and Hyper-V with the Barracuda Backup Agent
Backup Export Tool allows you to export historical revisions of data backed up and stored on a Barracuda Backup appliance
Barracuda Cloud-to-Cloud Backup for Office 365
Microsoft OneDrive for Business
Microsoft Exchange Online
New web interface look and feel

Improved Hyper-V Support
Browse Hyper-V VHD files through the Restore Browser
Local Control
Manage Barracuda Backup in a cloudless state
Replicate data from one or more Local Control appliances
Configure alternate rate limits
SMTP Server configuration
Generate large item reports
Offsite Vaulting
Store older backup data revisions offsite
Specify monthly and yearly offsite retention policies
Granular SharePoint Restores
Use Kroll Ontrack to restore SharePoint objects

Kroll Ontrack
You must have an active Kroll Ontrack license.
Continuing support for Microsoft applications:

Microsoft SQL Server 2012
Microsoft Exchange 2013
Microsoft Windows 8 / 2012 (including ReFS)
Microsoft Hyper-V 2012 Standalone
Microsoft Hyper-V 2012 Clustering
Microsoft Hyper-V 2008R2 Clustering
Introduction of the Barracuda Backup Agent (Linux):
Adds ACL protection
Adds alternate stream protection
Adds extended attributes protection
Parallel VMware Backups:
Multiple guests on the same host will be backed up concurrently
Improved Restore Browser:
Adds ability to search for items
Adds ability to select multiple items for restore
Advanced Graphs
Barracuda LiveBoot in the Cloud for VMware:

Instantly boot to your VMware virtual machine using Barracuda Networks' deduplicated cloud storage.
Centralized management of LiveBoot instances
The following feature has been deprecated in version 5.2
Watched Files – The seldomly used Watched Files feature has been deprecated in versions 5.2, and will not be supported for new
Barracuda Backup Servers. Note that existing Watched File Rules will continue to function as expected.
Backup Analytics:
View a detailed list of large items by source or file name in the REPORTS > Large Items page.
Barracuda LiveBoot for VMware:

Instantly boot to your VMware environment any backed up snapshot using de-duplicated storage on Barracuda Backup Server
Barracuda LiveBrowse for VMware:
View and traverse file structure inside all backed up VMware snapshots
Download Files and Directories within VMware snapshots
Improved Restore Browser:
Cloud UI Restore Browser displays in the Barracuda Backup web interface
Download file system directories as ZIP files
Download email mailboxes and folders as ZIP files
Reporting:
Cloud UI Reports available in the Barracuda Backup web interface
Size, Duration, Speed, and Type details are included in Reports
Enhanced Backup and Restore reporting data organization

What's New in Barracuda Cloud-to-Cloud Backup
What's New in Cloud-to-Cloud Backup (August, 2017)
The following new major features are added
Option to limit Restore Browser searches to the current working folder. [CCB-964]
Enhancements
OneDrive for Business restores are no longer limited to 1 GB [CCB-598]
Resolved
Fixed issue preventing backup of certain OneDrive for Business profiles due to "Bad User" error [CCB-902]
Fixed issue preventing backup of folders under Wiki pages in SharePoint Online [CCB-1001]
Fixed issue where backup schedules include unlicensed Exchange Online mailboxes [CCB-1230]

Barracuda Networks recommends ensuring the latest hotfixes, patches, and updates are installed on your data sources.
In this Section
Microsoft Exchange
Microsoft Hyper-V
Microsoft SQL Server
Microsoft SharePoint
Microsoft Active Directory
Microsoft Windows Server
Microsoft Office 365
Microsoft Windows Small Business Server
Windows Client Operating Systems
VMware
Linux Systems, Macintosh OS X, AIX, Unix, and Novell NetWare
GroupWise
IBM Domino Server
MySQL
Oracle Database
FirstClass Mail
Network Addressable Storage
SAP
Related Articles
Supported Data Sources by Version

Maximum Number of Simultaneous Backup Jobs by Model
Backing Up Data Sources
How to Back Up the Barracuda Message Archiver with Barracuda Backup
Backup Export Tool for export of historical revisions of backed up data

Microsoft Exchange
As of April 11, 2017, Microsoft no longer issues security updates for Exchange Server 2007. Without security updates, Essentials for
Email Security can no longer support Exchange Server 2007. For migration details, refer to the Microsoft TechNet article Understandin
g Upgrade from Exchange 2007 to Exchange 2010.
Microsoft Exchange Server Backup
How to Back Up Microsoft Exchange Server 2013 and Higher

How to Set Up Microsoft Server 2013 Message-Level Backup
How to Set Up Microsoft Exchange Server 2010 Message-Level Backups
How to Set Up Microsoft Exchange Server 2013 or Higher Message-Level Backup
How to Add Conditional Forwarders when Setting up Message-Level Backup for Multiple Domains
How to Back Up Microsoft Exchange Server 2010, 2013, and 2016 DAG
How to Back Up Microsoft Exchange Server 2010 and 2013 DAG Passive Database
Microsoft Exchange Server Restore
Microsoft Exchange Server Recovery and Restoration

How to Restore a Microsoft Exchange Server 2013 and Higher Database to a Recovery Database
How to Restore a Microsoft Exchange 2010 Server by Overwriting an Existing Database
How to Restore a Microsoft Exchange 2010 Server to a Recovery Database
How to Restore Microsoft Exchange Messages
Microsoft Exchange Server Troubleshooting
How to Resolve Microsoft Exchange 2010 Large Message Restore Errors

How to Resolve "Incremental backups cannot be performed while circular logging is enabled" Error
Troubleshooting Exchange Server 2010 Log Truncating Issues
Troubleshooting Exchange Server 2010 DAG Backup Log Files do not Truncate
How to Resolve Message-Level Backup Errors in Microsoft Exchange 2010
Microsoft Exchange Server Database Availability Group Backup
How to Back Up Microsoft Exchange Server 2010, 2013, and 2016 DAG Passive Database
Microsoft Exchange Server Database Availability Group Troubleshooting
Related Articles
Best Practices for Microsoft Exchange


Best Practices for Microsoft Exchange

This article refers to the Barracuda Backup Legacy Release firmware or newer.
Best Practice
Use these tips and recommendations to efficiently protect your Microsoft Exchange environment using Barracuda Backup. For detailed
Exchange backup configuration, restoration, and troubleshooting details, refer to the Microsoft Exchange section of Barracuda
Campus.
Barracuda Backup provides two different types of Microsoft Exchange backups:
1. Native Backup (Entire Exchange server and databases) – To protect the entire Microsoft Exchange Server and the Exchange
databases, install the Barracuda Backup Agent. Microsoft Exchange protection is achieved by leveraging Microsoft Volume Shadow
Copy Service (VSS) and the Exchange VSS Writer. This level of protection is designed to rebuild your entire Microsoft Exchange Server
or to provide the ability to restore an entire Exchange database either by overwriting an existing database or by restoring to a Recovery
Database. This is the primary backup and recovery method for Microsoft Exchange.
2. Message-Level Backup – Message-level backup provides a quick way to restore individual email messages to the original location or to
an alternate mailbox. Message-level backup is not intended to be a disaster recovery option for your Microsoft Exchange environment
and is used in conjunction with Agent-level Microsoft Exchange environment backups. Message-level backups are configured as a
separate data source from your agent-based Exchange Server backup. Message-level backups leverage Microsoft Exchange Web
Services (EWS) and are configured on the Exchange Client Access Server (CAS).
Each backup method provides its own advantages and disadvantages. The best practices in this guide are designed to help you find the best
level of protection for your Microsoft Exchange environment and to meet your recovery objectives.
Microsoft Exchange Server Protection
Best Practice
Document the Exchange Server configuration in detail and any subsequent changes including all applied hotfixes and service packs.
Additionally, it is highly recommended that you familiarize yourself with the Microsoft documentation for Exchange database
management, disaster plans, and recovery.
The Barracuda Backup Agent must be installed on each Exchange server

Microsoft Volume Shadow copy Service (VSS) and VSS Writer must be enabled
Ensure that Exchange is not being backed up by more than one backup solution; using more than one backup solution can cause issues
with Transaction Log backups and possibly result in data corruption
Circular logging must be disabled if you want to do the following:
Run incremental backups
Recover data up to the point of failure
Allow sufficient disk space for maintenance and recovery procedures, e.g., allow additional disk space for a recovery database
Attempt to keep moderate-sized Exchange databases; if databases are large, backup and recovery times will increase
Perform test restores periodically to ensure that disaster recovery and data recovery scenarios produce the expected results
Verify that backups have completed successfully before attempting any maintenance within the Exchange environment
With Barracuda Backup, you can:
Select individual or multiple databases for backup

Protect Exchange database availability groups (DAGs)
Install the Barracuda Backup Agent on each node

By default, only the active database is backed up on each node
Passive database backup can be optionally configured
For details on backing up Exchange DAGs, refer to:
Perform regular Complete Exchange database backups weekly through Backup Schedules:
Set your Backup type to Smart mode to allow Barracuda Backup to automatically determine whether Complete or Log backup is
appropriate
Create two schedules for your Exchange server; create one schedule to back up once weekly using Complete backup mode, and create
a second schedule to back up daily using Log backup mode

Transaction log truncation occurs after every backup, Complete or Log.
Important
In Exchange 2010 and later, log truncation occurs on both Complete and Log backups. However, if the Exchange 2010 or
later database is part of a DAG, the logs are truncated only up to the earliest checkpoint of the database replica on any node.
Barracuda Backup provides the following Microsoft Exchange recovery options:
Overwrite an existing database

Restore to a Recovery Database
When restoring to an Exchange server that is not the source server, ensure the following:
The recovery server is in a different Active Directory (AD) forest than the source server;
The recovery server has the same Organization and Administrative Group names as the source server; and
The database already exists on the recovery server and has the same name as the original database.
Message-Level Exchange Protection
Restore individual email messages without having to restore or mount the Exchange database
Email messages can be restored to the original mailbox or to an alternate mailbox
Use Message-level backup in conjunction with agent-level protection of the Exchange environment only
Message-level backup is not intended to recover corrupted or deleted user mailboxes, instead, use an Exchange Recovery Database in
this scenario
Message-level backups do not contain Exchange items such as Contacts, Calendars, and Tasks
Configure message-level backups as a separate data source from your Agent-based Exchange Server backup
Message-level backups leverage Microsoft EWS
Message-level backups are configured from the Exchange CAS
A service account with an Exchange mailbox and SMTP address is required
For more information on message-level backup, see:

How to Set Up Microsoft Exchange Server 2010 Message-Level Backup

Microsoft Hyper-V
Microsoft Hyper-V Backup
How to Set Up Microsoft Hyper-V Virtual Machine Backups

How to Set Up Hyper-V Clustering
How to Exclude Individual Virtual Machines from a Hyper-V 2008 Cluster Backup
Microsoft Hyper-V Backup Containers
Microsoft Hyper-V Restoration
How to Restore a Microsoft Hyper-V Virtual Machine
VHD and VHDX Files
How to Browse Hyper-V VHD and VHDX Files

How to Convert and Replace a Barracuda Virtual Appliance VHD File with a VHDX Format File
Amazon Web Services Replication and Restore
Replication to Amazon Web Services

How to Configure Amazon Web Services Replication and Restore
How to Configure Amazon Web Services as a Replication Target
Learn about Amazon S3
Learn about AWS CloudFormation
Restore to Amazon Web Services
How to Configure the AWS Import Service Role
How to Restore VMware and Hyper-V Virtual Machines to Amazon Web Services
Launch an EC2 Instance
Amazon EC2 Instances and AMIs
Amazon Machine Images (AMI)
Understanding Amazon EC2
Replication and Restore to Amazon Web Services FAQ
Troubleshooting
How to Resolve Hyper-V Error During Backup Selection
Related Articles
Best Practices for Microsoft Hyper-V


Best Practices for Microsoft Hyper-V

Use these tips and recommendations to efficiently protect your Microsoft Hyper-V environment using Barracuda Backup. For
detailed Hyper-V backup configuration, restoration, and troubleshooting details, refer to the Microsoft Hyper-V section of Barracuda
Campus.
Best Practice
Document the Microsoft Hyper-V configuration in detail and any subsequent changes including all applied hotfixes and service packs.
Additionally, it is highly recommended that you familiarize yourself with the Microsoft Hyper-V documentation for management, disaster
plans, and recovery.
Barracuda Backup provides three methods to protect your virtual environment:
1. Host-based (Agentless) protection;

2. Guest-level (Agent) protection; and
3. Hybrid host- and guest-level protection.
level of protection for your virtual environment and to meet your recovery objectives.
Host-Based (Agentless) Protection
The Barracuda Backup Agent must be installed on each Hyper-V host machine
Provides image-based agentless protection of guest virtual machines (VMs)
Barracuda Backup Agent provides source-based deduplication and incremental forever backups of guest VMs
Quick and easy to configure, no need to add VMs as individual sources
Automatically detects new and removed VMs
Provides granular file/directory recovery via VHD Browsing
Preferred method of protection for quick disaster recovery and to meet stringent recovery time objectives
Provides recovery of entire VM to original or rebuilt Hyper-V host
Download individual virtual disks
You cannot exclude individual files or directories from backup
Can cause an increased storage footprint due to image-based backup method, better for short-term retention
Protect Microsoft applications running on VMs using the Barracuda Backup Agent as separate sources in conjunction with host-based
backups, including:
Microsoft Exchange Server – Only databases must be protected using the Barracuda Backup Agent. If you are using
host-based VM backup in conjunction with Agent backup, you do not need to include the File System and System State with the
Agent backup.
Microsoft SQL Server – Only databases must be protected using the Barracuda Backup Agent. If you are using host-based VM
backup in conjunction with Agent backup, you do not need to include the File System and System State with the Agent backup.
Microsoft Active Directory – Databases and System State must be protected using the Barracuda Backup Agent.
Guest-Level (Agent) Protection
Provides incremental forever file-level protection of guest VMs using the Barracuda Backup Agent
Backups treat each VM like a physical client
Application-consistent protection for Microsoft applications, including:
Microsoft Exchange Server
Exclude any file, file type, or directory
Run pre- and post-backup scripts
Provides more granular recovery options including:
Restore files and directories to any client running the Barracuda Backup Agent
Designate the path where files are restored
Download individual files and directories (locally and cloud)
Complete system restore through:
Bare metal restoration to a new computer without a pre-installed operating system
Restore the entire file system or individual volumes to a target system with a pre-installed operating system
Provides a smaller storage footprint due to file-level backup and deduplication; this is potentially a better option for servers needing to
adhere to longer retention policies, such as a file server needing to retain historical revisions for several years

Microsoft SQL Server Backup
How to Back Up Microsoft SQL Server Databases

Understanding VSS and VDI SQL Database Backup
How to Enable VDI Incremental Backups for Microsoft SQL Server
Microsoft SQL Server Restore
How to Restore a Microsoft SQL Database

How to Restore a SQL Server 2008 Master Database
How to Restore a Microsoft SQL Database to a Point-in-Time
How to Restore a Microsoft SQL Server Database to a Flat File
How to Restore Microsoft SQL Server 2012 Database to a File System
How to Restore Microsoft SQL Server 2012 and Above Databases
How to Restore a SQL Instance after a Bare Metal Restore
Microsoft SQL Server Troubleshooting
How to Change the SQL Recovery Model

How to Resolve "Error with SQL authentication" Warning
Related Articles
Best Practices for Microsoft SQL Server

Microsoft SQL Server Key Terms

Best Practices for Microsoft SQL Server

Use these tips and recommendations to efficiently protect your Microsoft SQL Server environment using Barracuda Backup. For
detailed SQL Server backup configuration, restoration, and troubleshooting details, refer to the Microsoft SQL Server section of
Barracuda Campus.
Best Practice
Document the SQL Server configuration in detail and any subsequent changes including all applied hotfixes and service packs.
Additionally, it is highly recommended that you familiarize yourself with the SQL Server documentation for database management,
disaster plans, and recovery.
Microsoft SQL Server Protection
The Barracuda Backup Agent must be installed on each SQL server

SQL backups leverage Microsoft's Volume Shadow Copy Service (VSS) and Virtual device Interface (VDI) technologies
Perform test restores periodically to ensure disaster recovery and data recovery scenarios produce expected results
Ensure that SQL is not being backed up by more than one backup solution; using more than one backup solution can cause issues with
Log backups and possibly result in data corruption
Verify backups complete successfully before attempting any maintenance within the SQL environment
If point-in-time restores are required, the database must be set to use the Full Recovery Model and the Barracuda Backup Agent must be
set to perform SQL VDI backups which performs full and transaction log backups
When databases are set to use the Simple Recovery Model:
Full and differential backups can be performed
Transaction log backups cannot be performed
By default, the Barracuda Backup Agent users the Local System account to back up SQL databases
If SQL is configured to use Mixed Mode Authentication and the Local System account is denied access, the Microsoft SQL Server
Requires Authentication option must be selected and credentials for the account specified
If SQL is configured to use a Maintenance Plan for backups, there are two options:
The Maintenance Plan must be disabled to allow Barracuda Backup to back up the SQL database to avoid backup failure
Continue to use Maintenance Plans and deselect the Microsoft SQL portion when configuring the SQL server source. Continue
to back up File Systems and System State; files created by the Maintenance Plan are backed up as part of the File System
backup
Barracuda Backup provides the ability to:
Select individual or multiple databases for backup

Protect Microsoft SQL failover clusters
Perform regular Complete SQL database backups weekly through Backup Schedules:
Set your Backup type to Smart mode to allow Barracuda Backup to automatically determine whether Complete or Log backup is
appropriate
Create two schedules for your SQL server; create one schedule to back up once weekly using Complete backup mode, and create a
second schedule to back up daily using Log backup mode
Transaction log truncation occurs after every Log backup when using Complete Recovery Model and VDI.
If multiple backups are performed throughout the day, a nightly or every other day Complete backup is recommended
Barracuda Backup provides the following Microsoft SQL recovery options:
Restore a database to any available SQL server with the same or greater version of Microsoft SQL installed
A database can be renamed and restored to a specific alternate path
With VDI, any database can be restored to a flat file, .bak and .trn, and recovered using SQL Management Studio
With VSS, any database can be restore to a file system, .mdf and .ldf, and attached using SQL Management Studio
Point-in-time restores can be done on any database using Full Recovery Model and backed up using Microsoft VDI
When restoring an SQL Differential or Transaction Log backup:
All previous backups in the backup chain are restored sequentially

When restoring a transaction backup, all required transaction backups are automatically restored along with the corresponding Full
backup
It is unnecessary to perform multiple restores to get back to a certain backup revision
Granular restore of Microsoft SQL Server database record is not supported.


Microsoft SQL Server Key Terms

Table 1. Microsoft SQL Server Terminology.
Term Description
Recovery Point Objective The maximum acceptable amount of data (time period) that can be
lost in the event of an incident, that is, is it acceptable to recover back
to the backup from the previous night or do you need to recover back
no later than 15 minutes prior to the failure?
Transaction Logs Per database log that records all transactions and database
modifications made by each transaction. These are used to roll back
changes as well as recover to a precise point in the case of a restore.
Simple Recovery Model Setting made per database within SQL. When a database is in
Simple Recovery Model, transaction logs are automatically
truncated/reclaimed to keep logs small but prevents Transaction Log
backups. This means the database can only be recovered back to
the time of the last Full or Differential backup.
Full Recovery Model Setting made per database within SQL. When a database is in Full
Recovery Model, transaction logs are maintained by the database
and only truncated/reclaimed when a Transaction Log backup is
performed. This means the database can be recovered back to any
point in time covered by the backed up transaction logs.
Full Database Backup Backup of the entire database. Full database backups represent the
database at the time the backup finished.
Transaction Log / Incremental Database Backup Backup of the transaction logs since the last transaction log backup
and truncates those logs preventing them from continuing to grow
and consume disk space.
Differential Database Backup Backup of the data that has changed since the last full backup. A
differential backup is completely independent of the transaction logs.
Log Truncation When a database is set to Full Recovery Model, SQL stores all
transactions performed on the database in a log. Log Truncation is
the process of marking a set of transactions as backed up and no
longer needed so the space can be reclaimed and reused for other
transactions. This is a crucial process to ensure the transaction log
does not continue to grow and consume too much disk space.
Maintenance Plan Maintenance plans can be created directly in Microsoft SQL for
running regularly scheduled flat file backups and other maintenance
on databases. It is important to know if there are already
maintenance plans in place before configuring another type of
database backup, such as the Barracuda Agent backup as they can
interfere with one another likely causing failed or corrupt backups.
Table 2. Microsoft SQL File Extensions.
File Extension Description
.mdf Primary active database file which contains the schema and data.
.ldf Current active logs.
.bak Typical extension used for a Full Database flat file backup.
.trn Typical extension used for a Transaction Log flat file backup.

Microsoft SharePoint Restore
How to Restore SharePoint Objects Using Kroll Ontrack

Restore a SQL SharePoint Database
Related Articles

Microsoft Active Directory Backup
How to Back Up Microsoft Active Directory
Microsoft Active Directory Restore
How to Restore a Microsoft Server 2012 Active Directory Object from the Active Directory Recycle Bin
How to Enable Active Directory Recycle Bin on Windows Server 2012
How to Restore a Microsoft Server 2008 R2 Active Directory Object from the Active Directory Recycle Bin
How to Enable Active Directory Recycle Bin on Windows Server 2008 R2

As of July 14, 2015, Microsoft will no longer issue security updates for Windows Server 2003. Without security updates, Barracuda
Backup can no longer support Windows Server 2003. For migration details, refer to the Microsoft website: https://www.microsoft.com/e
n-us/server-cloud/products/windows-server-2003/
How to Restore Windows Server 2008 and 2012 System State

How to Restore Windows Server 2008 Domain Controller System State
Microsoft Windows Server Active Directory
Microsoft Windows Server Troubleshooting
Monitoring Windows System Performance During Backup
Related Articles


Microsoft Office 365
Barracuda Cloud-to-Cloud Backup for Office 365 protects Exchange Online, OneDrive for Business, and SharePoint Online data by backing it up
directly to Barracuda Cloud Storage. Barracuda Cloud-to-Cloud Backup for Office 365 can be used as an add-on to an on-premises Barracuda
Backup appliance or as a standalone subscription without an appliance. For Exchange Online, Barracuda Cloud-to-Cloud Backup protects all
email messages, including all attachments, as well as the complete folder structure of each users’ mailbox. In OneDrive for Business, all files
under the Documents Library, including the entire folder structure, are protected. For SharePoint Online, protects Online files and folders in Docu
ment Libraries, Site Assets, Site Pages, Picture Libraries, and Form Templates in Team Sites, Public Sites, Wiki Sites, and Publishing Sites .
If you have installed Barracuda Essentials for Office 365 - Complete Protection and Compliance, see Barracuda Cloud-to-Cloud
Backup for Office 365.
General Information
Why You Need to Back Up Office 365 Data Sources

How to Determine Amount of Storage Used in Office 365
How to Reauthorize an Office 365 Share
Understanding Cloud-to-Cloud Backup Retention
How to Schedule an Office 365 Backup
Cloud-to-Cloud Backup Overview - Video
Getting Started with Cloud-to-Cloud Backup - Video
Cloud-to-Cloud Office 365 Exchange Online
Understanding What Exchange Online Data is Backed Up

How to Configure Impersonation for Exchange Online Data Sources
How to Configure an Exchange Online Data Source
How to Schedule an Exchange Online Backup
How to Restore an Exchange Online Data Source
How to Download an Exchange Online Data Source
Cloud-to-Cloud Office 365 OneDrive for Business
Understanding What OneDrive for Business Data is Backed Up

How to Configure Impersonation for OneDrive for Business Data Sources
How to Configure a OneDrive for Business Data Source
How to Schedule a OneDrive for Business Backup
How to Download a OneDrive for Business Data Source
How to Restore a OneDrive for Business Data Source
Cloud-to-Cloud Office 365 SharePoint Online
Understanding What SharePoint Online Data is Backed Up

How to Configure Site Collection Administration for SharePoint Online Data Sources
How to Configure a SharePoint Online Data Source
How to Schedule a SharePoint Online Backup
How to Download a SharePoint Online Data Source
How to Restore a SharePoint Online Data Source
Barracuda Essentials for Office 365 - Complete Protection and Compliance
Barracuda Cloud-to-Cloud Backup

Web Interface
O365

General Information
In this Section

See Also
Complete Protection for Office 365 with Barracuda Cloud-to-Cloud Backup White Paper


According to a January 2013 survey by Aberdeen Group, the number one cause of data loss in a SaaS deployment, such as Microsoft Office 365,
is accidental data deletion. In fact, about 70 percent of all lost data is due to either accidental or malicious deletion of data by end-users. Other
ways that data can be lost include misconfiguration, client sync issues, and most recently the widespread presence of malware and ransomware,
which can render data unusable.
Microsoft’s primary focus within Office 365 is ensuring that service and data availability are not disrupted. While Microsoft does a great job of
reducing the risk of downtime, this does not reduce the risk of data loss. In fact, Microsoft’s options for data recovery are quite limited, but they do
provide some basic safety measures.
Use of Recycle Bins and Retention
Recently deleted content from Exchange Online, OneDrive for Business, and SharePoint Online is not deleted immediately. Instead, the deleted
content goes through a set of Recycle Bins, each with their own retention policies, before it is deleted permanently. The Recycle Bins act as a
safety net for deleted content. While data can be recovered from these Recycle Bins, the retention for each is limited and once the data is out of
retention, the data is gone forever.
Table 1. Recycle Bins and Retention.
Microsoft Solution Recovery Feature Maximum Retention Period
SharePoint Online Site Recycle Bin 93 days
Second Stage Recycle Bin 93 days
Exchange Online Deleted Items No maximum (configurable)(1)
Recoverable Items Up to 30 days(2)
OneDrive for Business Site Recycle Bin 93 days
Second Stage Recycle Bin 93 days
Notes:
(1) Default retention is 30 days.
(2) Default retention is 14 days.
Document Versioning
If the Document Versioning feature is turned on, OneDrive for Business retains a number of previous versions for each file that has been
modified, and end users are then able to restore back to any of these previous versions. However, this does not provide protection against
intentional or accidental deletion since all versions of a document are deleted when the current version is deleted.
High Availability and Site Collection Backups
Microsoft uses Database Availability Groups (DAGs) to protect Exchange Online data. While DAGs do a great job of ensuring uptime and
preventing catastrophic disasters, they do not protect against mailbox corruption, nor can they restore individual email-related items or entire
mailboxes to a point in time. For SharePoint Online and OneDrive for Business, Microsoft takes backups of site collections every 12 hours and
keeps these backups for 14 days. IT administrators have no control over these backups or restores. If a restore is necessary, it can only be
initiated by contacting Office 365 support. You also cannot restore a single item, document, asset, or library. A full restore of a site collection is
the only option.
Mailbox and Account Retention
When an employee leaves an organization, all data in that user's Exchange Online mailbox and OneDrive for Business account is permanently
deleted 30 days after their account is deleted. To retain this data for future reference or use, it must be backed up or moved elsewhere. Exchange
Online mailboxes can be kept for longer periods of time by configuring an In-Place Hold before the account is deleted; however, this is a premium
feature not available in some Office 365 plans.
Microsoft does all they can to put safeguards in place to prevent their customers from losing data, but Microsoft Office 365 does not specialize in
data backup and recovery. Seeking an additional layer of protection against accidental or malicious data loss, organizations have begun to use
third-party backup solutions that offer enhanced protection of Office 365 data, longer retention periods, and more robust recovery options.
Complete Protection with Barracuda Cloud Backup
Barracuda Backup is the leading integrated backup appliance in the world according to IDC's Purpose-Built Backup Appliance Tracker. Barracuda
Backup was built from the ground up around the cloud with features like built-in cloud replication and management. With a strong legacy in
on-premises physical and virtual server protection, Barracuda Backup now includes Cloud-to-Cloud Backup for Office 365. Cloud-to-Cloud
Backup protects Exchange Online, SharePoint Online, and OneDrive for Business data by backing it up directly to Barracuda Cloud Storage.
Cloud-to-Cloud Backup for Office 365 can be used as an add-on to on-premises Barracuda Backup devices or as a standalone subscription.

Exchange Online
In backing up Exchange Online, Barracuda Cloud-to-Cloud Backup protects all email messages, attachments, and the complete folder structure
of each user mailbox. Messages, folders, or entire mailboxes can be restored back to the original account, a different account, or exported via the
download feature.
OneDrive for Business
When backing up OneDrive for Business using Barracuda Cloud-to-Cloud Backup, all files under the Documents Library, including the entire
folder structure, are protected. Just like with Exchange Online, files, folders, or entire accounts can be restored back to the original account, a
different account, or exported via the download feature.
SharePoint Online
Barracuda Cloud-to-Cloud Backup provides complete protection of SharePoint Online. With item-level recovery options, items can be restored
back directly into SharePoint Online from the backups of Document Libraries, Site Assets, Site Pages, Picture Libraries, and Form Templates in
Team Sites, Public Sites, Wiki Sites, and Publishing Sites. Barracuda Cloud-to-Cloud Backup for Office 365 eliminates the risk of lost content due
to accidental or malicious deletion. You can also retain email messages and files indefinitely if users were to leave your organization—all without
having to purchase additional licenses.
Cloud-to-Cloud Backup Features
Automated and on-demand backups – Microsoft Office 365 backups can be fully automated by creating customizable backup
schedules to back up data when you want or you can choose to run backups on-demand at any given time. Optionally, backup schedules
can be repeated throughout the day as necessary to protect critical data. All Exchange Online, SharePoint Online, and OneDrive for
Business data is deduplicated and compressed for maximum storage efficiency and reduced backup windows before being stored in the
Barracuda Cloud.
Quick and easy restore – All Office 365 data backed up to the Barracuda Cloud is accessible, searchable, and retrievable from
anywhere with an Internet connection. By selecting specific dates from a built-in calendar, point-in-time recovery of data–mailboxes,
folders, files, sites, libraries, and email messages–can be achieved. Files or email messages can be restored back to the original user
account and location, to a different location within the account, or a completely different user account. Items backed up from SharePoint
Online sites can be recovered back to their original location. If you are looking for a specific file or message but are unsure of its location,
use the search feature to quickly and easily find the item, as well as where it can be restored or downloaded. Downloading folders puts
them into a compressed ZIP file for quick downloads, while email messages are downloaded using the industry-standard EML format.
Files are downloaded using their same file format (unless multiple files are selected), then they are put into a ZIP file for easier access.
Reporting and statistics – For IT Administrators, detailed reporting and audit logging are a key component of a backup solution.
Barracuda Cloud-to-Cloud Backup provides backup status and health monitoring for each backup source. Automated email alerts are
delivered after each backup to specified email recipients containing a summary of the backup and detailed information about which email
messages, folders, and files were added, modified, and removed since the last backup. On the Status page, graphs show the number of
items added and amount of data backed up each day. Storage statistics and graphs detail how much data has been backed up overall
and the storage efficiency, as well as how much data is actually being stored in the Barracuda Cloud after deduplication and
compression. An Audit Log tracks and provides details about every action performed within the Cloud-to-Cloud Backup interface.
Usability – Barracuda Backup has always been known for ease of use, and the Cloud-to-Cloud Backup features are no exception.
Existing Barracuda Backup users will feel right at home with this new functionality, and new users will be able to learn it within minutes.
The Cloud-to-Cloud Backup service is listed among other Barracuda Backup appliances in Barracuda Cloud Control for easy access and
management.
Administration and policy management – All Barracuda Backup appliances and Cloud-to-Cloud Backup services can be managed
through a single pane of glass with Barracuda Cloud Control—Barracuda’s cloud-hosted centralized management interface. Barracuda
Cloud Control can be accessed from anywhere with an Internet connection, making it possible to access and recover your organization’s
data at a moment’s notice. By downloading the Barracuda Cloud Control Mobile App, you can view the health status of your backups and
backup appliances from your Apple iOS or Android mobile devices. Barracuda Cloud Control also provides role-based administration,
allowing you to add and remove users, assign product entitlements, and control access to what functions they can perform in Barracuda
Backup and Cloud-to-Cloud Backup. Creating flexible and fully customizable retention policies is easy by allowing you to specify how
long to keep your organization’s historical data. Create global retention policies for all Office 365 data or get more granular by creating
different policies for different users or sets of data. A handy retention calendar visually lays out what your retention timeline will look like
on-the-fly.
Security – One of the largest concerns for organization’s looking to protect their data in the cloud is security. With Barracuda Backup, all
Office 365 data is encrypted in-transit with 128-bit SSL encryption, the same level of security used by most banks and financial
institutions. Data stored in the Barracuda Cloud is encrypted at-rest using 256-bit AES encryption. Barracuda Cloud Storage regularly
undergoes third-party audits and is SSAE 16 Type II certified. Additional layers of protection included in Barracuda Cloud Control are
multifactor authentication, IP address login restrictions, and role-based administration. See the Barracuda website for more information.
With Barracuda Cloud-to-Cloud Backup, you still own your data even though it is in Office 365. Although Microsoft does their best to manage your
data effectively, you remain ultimately responsible for the protection of that data, just as you did before you moved to Office 365. Mistakes
happen—users accidentally delete or overwrite important data. There are also instances when disgruntled employees or hackers take malicious
action in deleting or corrupting data. Therefore, you need to ensure you have an effective backup and recovery solution in place. Barracuda
Cloud-to-Cloud Backup provides complete protection for your entire Office 365 environment.


Office 365 Exchange Online
Use the following steps to determine the amount of storage used in Office 365 Exchange Online:
1. Log in to your Office 365 environment as administrator, and select Admin > Reports:
2. In the Mail section, click Mailbox Usage:
3. In the Mailbox usage graph, click the Total number of users column:
4.

4. The list of users displays; click download csv file to download the list to your local system as a .csv file:
5. Navigate to and open the downloaded .csv file in Microsoft Excel.

6. create a formula in Excel to calculate the sum of the Space used (KB) column:
7. Convert the sum from KB to either GB or TB depending on your preference. This amount is the total storage used by each end-user
mailbox.
Office 365 OneDrive for Business
Use the following steps to determine the amount of storage used in Office 365 OneDrive for Business:
1. Log in to your Office 365 environment as administrator, and select Admin > Reports:

2. In the OneDrive for Business section, click OneDrive for Business storage:
3. The OneDrive for Business storage graphs display the amount of storage used in MB for a 12-, 24-, or 52-week, period:

SharePoint Online
1. Log in to your Office 365 environment as administrator, and go to the SharePoint admin center.
2. In the left pane click site collections.
3. In the Site Collections table, review Percent Used.


Use the following steps to reauthorize an Office 365 share:
1. Log in to Barracuda Backup, and select the Cloud-to-Cloud Backup Source in the left pane.
2. Go to Backup > Sources.
3. On the Sources page, navigate to Office 365, and click Edit to the right of the data source.
4. In the Authorization section, click Reauthorize your <data source> account.


Use retention policies to define the length of time you retain historic data based on daily, weekly, monthly, or yearly time intervals. Create
retention policies for different sets of data.
Data backed up using Barracuda Cloud-to-Cloud Backup retention treats Sunday as the end of the week in accordance with the ISO data
standard. Revision data is retained based on the date the file is removed. For example, if a file was backed up on January 1 and the retention
policy is configured to hold onto data for 7 daily revisions, if the file is modified or removed at any point, the revision is held onto for 7 additional
days after this action.
To retain weekly, monthly, and yearly revisions, Barracuda Cloud-to-Cloud Backup ages forward files that are not created specifically at the end
of the week, month, or year to be recoverable as part of these revisions.
Retention Policy
You can create one policy for all data sources or create multiple policies for different sets of data. Use the Backup > Retention Policies page to
define content retention rules:
Policy name – Enter a name to identify the policy.

Items to retain – Displays all data sources. Select all of the items you want to include in the retention policy, or click Apply to all to
apply the retention policy to all Barracuda Cloud-to-Cloud Backup data sources.
Retention timeline – Define how historic data is retained.
Timeline templates – Select from the pre-defined templates which you can modify, or create your own custom timeline. The Re
visions timeline and Retention Calendar display the timeline based on the selected template.
Revisions timeline – Define how long to keep daily, weekly, monthly, and yearly backups.
Keep all revisions for – Specify the number of day(s) to keep all content revisions, or select never or forever.
This feature allows you to keep revisions when you have multiple backups per day.
Keep daily revisions for – Specify how long to keep daily revisions. Specify a number of day(s), never, or forever.
Keep weekly revisions for – Specify how long to keep weekly revisions. Specify a number of week(s), never, or forev
er.
Keep monthly revisions for – Specify how long to keep monthly revisions. Specify a number of month(s), never, or fo
rever.
Keep yearly revisions for – Specify how long to keep yearly revisions. Specify a number of years(s), never, or foreve
r.
Retention Calendar – Display the timeline based on the values in the Revisions timeline. Click Show previous years to view
prior year retention timelines.


Use the following steps to schedule an Office 365 backup:
2. Go to Backup > Schedules.
3. On the Schedules page, click Add a Schedule in the upper right-hand corner.
4. Enter a name for your schedule in the Schedule name field:
5. In the Identify the data sources section, select the data to be backed up using this schedule. You can select Apply to all computers
and data sources for this Barracuda Cloud to Cloud Backup or you can granularly select data down to a specific file or folder.
6. In the Schedule Timeline section, select the days you want the schedule to run. If you are creating a one-time only backup schedule,
deselect all days:
7. In the Daily Backup Timeline section, enter a start time for your backup schedule. To repeat a backup schedule throughout a 24-hour
period, select the Repeat option and specify the frequency of the backup and the end time. A backup schedule cannot span multiple
days:
8. Once you have configured your backup schedule, click Save.

9. The backup schedule is now listed on the Schedules page and specifies the days and times that it is to run. To run a backup
on-demand, click Run Backup Now, to edit the schedule click Edit, or to delete a schedule, click Remove:


Watch this video for a quick overview of cloud-to-cloud backup:


Watch this video for an overview of setting up a Barracuda Cloud-to-Cloud Backup data source:

In this Section

See Also
O365


For Exchange Online, Barracuda Cloud-to-Cloud Backup protects all email messages, attachments, and the complete folder structure of each
users’ mailbox. You can restore messages, folders, or entire mailboxes back to the original account or export via the download feature.
Exchange Online Mailbox Barracuda Cloud-to-Cloud Backup
O365

O365
This article applies to Barracuda Cloud-to-Cloud Backup and Microsoft Office 365.
In order for Barracuda Cloud-to-Cloud Backup to access user mailboxes for backup, you must create a new service account with administrative
privileges and apply the impersonation role to that account.
To configure impersonation within Exchange Online:
Step 1. Create a New Service Account
1. Log in to your Office 365 Management Panel using an account with administrative privileges, and click users and groups in the left
pane.
2. Click the + symbol to create a new account.
3. In the details page, enter the details for the new service account, and click next.
4. In the settings page, select Yes to assign administrator permissions, and from the drop-down menu, select Global administrator.
Optionally, you can add an alternate email address and location. Click next.
5. In the assign licenses page, make no changes. Click next.
6. In the send results in email page, click Create. The service account details are sent to the admin.
7. To activate the account, log in to your Office 365 Management Panel using the new service account, and update the password.
Step 2. Create Impersonation Role
Option 1. Manually Set Up Impersonation

Click here to expand...
1. Log in to your Office 365 Management Panel using an account with administrative privileges, and go to permissions > admin roles.
2. Click the + symbol. In the new role group dialog box, type BarracudaBackupImpersonation in both the Name and Description
fields:

3. Scroll down to Roles, and click the + symbol.

4. From the list, select ApplicationImpersonation, and click add:
5.

5. Click OK.
6. Scroll down to Members, select the service account created in Step 1: Create a New Service Account, and click add.
7. Click OK. Click Save to save your settings and close the Role Group window. The Impersonation role is now listed in Admin Roles.
Option 2. Set Up Impersonation via PowerShell

Use the following steps to assign the ApplicationImpersonation role using PowerShell:
1. At the PowerShell command prompt, enter the following command:

New-ManagementRoleAssignment –name:impersonationAssignmentName –Role:ApplicationImpersonation
–User:serviceAccount
Where:
name is the friendly name of the role assignment. Each time you assign a role, an entry is made in the role-based access control (RB
AC) roles list. You can verify role assignments by using the Get-ManagementRoleAssignment cmdlet found in the Microsoft Dev
Center article How to: Configure impersonation.
Role is the RBAC role to assign. When you set up impersonation, you assign the ApplicationImpersonation role.
User is the service account.
2. Press Enter.
365


This article applies to Barracuda Cloud-to-Cloud Backup and Microsoft Exchange Online.
To complete the steps in this article, the impersonation role must be applied to a service account with administrative privileges or
another user account with administrative privileges. For details on enabling impersonation for the Microsoft Office 365 Administrator
Account, see How to Configure Impersonation for Exchange Online Data Sources.
Use the following steps to set up Exchange Online backup:
1. Log in to Barracuda Backup, and select the Cloud Source in the left pane.
2. On the Status page, click Exchange Online:
3. The Data Sources page displays. Click Add a Cloud Provider, and enter the following details:
a. In the Cloud Provider description field, enter a name to represent the data source.
b. From the Cloud Provider type drop-down menu, select Microsoft Office 365.
c. Click Save.
4. The Add a Cloud Data Source dialog box displays:
a. From the Data Type drop-down menu, select Exchange Online:
b. Enter Your Office365 domain URL.
The URL is available once you log in to Exchange Online.
c. Click Authorize.
If you are not currently logged into the Exchange Online account, the Microsoft login page displays. Enter your
Exchange Online administrator login information, and then click Sign in.
5. In the Exchange Online page, click Accept to authorize Barracuda to back up data from Exchange Online:

6. The Edit Exchange Online page displays.

a. Enter a name to identify the data source in the Data Description field.
b. In the Add to schedule section, click the drop-down menu, and then click Add New:
7. The Add New Schedule dialog box displays:
8. Enter a name to represent the schedule, and click OK. The Edit Exchange Online page is updated with the new schedule name.
9. Click Save. The Edit Backup Schedule page displays.
10. In the Items to Back Up section, select individual items to back up, or click Apply to all computers and data sources for this
Barracuda Backup Cloud Service to back up everything in Exchange Online.
11. In the Schedule Timeline section, select the day you want the schedule to run.
12. In the Daily Backup Timeline, specify the time of day the schedule is to run:

13. Click Save. Exchange Online is backed up based on your data source and schedule settings.


deselect all days:
days:



This article applies to Barracuda Cloud-to-Cloud Backup and Microsoft® Exchange Online.
Use the following steps restore an Exchange Online backup:
1. Log in to Barracuda Backup, click the Backup tab, and select the Cloud-to-Cloud Backup Source.
2. Click Restore > Restore Browser.
3. Click Exchange Online, and then select the user mailbox from which to restore data:
4. Select the folder from which to restore data:
5. Locate the email or folder to restore, or use the search field to locate the desired data:
6. The default view displays data that was present during the last backup.
7. To find a historical email or folder revision from a previous date, click Change Date in the left pane:
8. Use the calendar to select the desired day to view data available for restore from that date.
9. Once you locate the email(s) or folder to restore, click Restore to the right of a single item,
or click Restore selected items if you selected multiple items:

10. The Restore dialog box displays. Select to restore to the Original Location and Original Path,
or click Specify New Path and specify a different user and path:
11. Click Start Restore. A notification displays that the restore is in progress:
12. To view restore status, go to the Reports > Restore page.

13. Verify the messages or folders have been restored in the user's Exchange Online mailbox.


This article applies to Barracuda Cloud-to-Cloud Backup and Microsoft Exchange Online.
Use the following steps to restore an Exchange Online backup:
1. Log in to Barracuda Backup, and click Office 365 Backup in the left pane.
2. Click Restore > Restore Browser.
3. Click Exchange Online in the left pane, and then select the user mailbox you want to download:
4. Select the folder from which to download data:
5. Locate the email or folder to download, or use the search field to locate the desired data:
6. The default view displays data that was present during the last backup. To find an historical email or folder revision from a previous date,
click Change Date in the left pane:
7. Use the calendar to select the desired day to view data available for download from that date.
8. Once you locate the email(s) or folder to download, click Download to the right of a single item, or click Download selected items if you
selected multiple items:

9. The Save As dialog box displays. Navigate to and select the location where you want to download the file or .zip file if you selected a
folder or multiple files:
10. Click Save.

In this Section

O365
See Also


When backing up OneDrive for Business using Barracuda Cloud-to-Cloud Backup, all files under the Documents Library, including the entire
folder structure, are protected. Just like with Exchange Online, files, folders, or entire accounts can be restored back to the original account, a
different account, or exported via the download feature.
OneDrive for Business Mailbox Barracuda Cloud-to-Cloud Backup
O365


This article applies to Barracuda Cloud-to-Cloud Backup and Microsoft OneDrive for Business.
Before Getting Started
Download and install the SharePoint Online Management Shell from the Microsoft Windows Download Center to a windows computer with
PowerShell installed, and download the AdminRights.ps1 script to the same Windows computer where you installed SharePoint Online
Management Shell.
Alternatively, after downloading and installing the SharePoint Online Management Shell, you can follow the steps in the Microsoft support article
Assign eDiscovery permissions to OneDrive for Business sites.
In order for Barracuda Cloud-to-Cloud Backup to access OneDrive user accounts for backup, you must create a new service account with
administrative privileges, and then assign that account SharePoint Site Collection Administrator privileges.
Step 1. Create a New Service Account
1. Log in to your Office 365 Management Panel using an account with administrative privileges, and click users and groups in the left
pane.
2. click the + symbol to create a new account.
3. In the details page, enter the details for the new service account, and click next.
4. In the settings page, select Yes to assign administrator permissions, and from the drop-down menu, select Global administrator.
Optionally, you can add an alternate email address and location. Click next.
5. In the assign licenses page, make no changes. Click next.
6. In the send results in email page, click Create. The service account details are sent to the admin.
7. To activate the account, log in to your Office 365 Management Panel using the new service account, and update the password.
Step 2. Configure Permissions
Use this step to configure permissions for current users.
There are two options you can use to give the service account created in Step 1. Create a New Service Account access to user accounts:
Option 1 – Run a SharePoint Online Management Shell script to automatically apply the proper permissions to each user account; this is
the preferred and fastest. If you have multiple users, this is also the easiest method.
or
Option 2 – Manually configure each user account from within the Microsoft SharePoint Admin Center. If you have only a few users, this
is the easiest method.
Option 1. Configure Permissions Using a SharePoint Online Management Shell Script
1. Download and open the AdminRights.ps1 script using a text editor such as Notepad.
2. Navigate to and edit the following four variables:
$o365login – Replace with your Office 365 service account or administrator account username.
$o365pw – Replace with your Office 365 service account or administrator account password.
$spAdminURL – Replace with the same URL used in your organization's OneDrive URL, but suffixed with -admin
$spMyURL – Replace with the same URL used in your organizations’ OneDrive URL, but suffixed with -my
3. Save and close the script.
4. Locate the SharePoint Online Management Shell installed in Step 1, then right-click and click Run as administrator.
5. Change your working directory within the SharePoint Online Management Shell to the location where you saved the AdminRights.ps1 s
cript:
6. Run the following command:

Set-ExecutionPolicy Unrestricted
7. Run the following command to run the AdminRights.ps1 script:

7.
.\AdminRights.ps1
8. Press Enter to exit the script.

9. Exit SharePoint Online Management Shell.
You must complete the steps in Option 1 each time you add new users.
Option 2. Configure Permissions from the Microsoft SharePoint Admin Center
1. Log in to your Office 365 Management Panel using the service account created in Step 1. Create a New Service Account.
2. In the left pane click Admin centers > SharePoint, and click user profiles.
3. Click Manage User Profiles:
4. In the Find profiles field, type the name of a user who's OneDrive for Business data is to be backed up, and then click Find:
5.

5. Click the user's Account name, and then click Manage site collection owners:
6. The site collection owners dialog box displays. In the Site Collection Administrators field, add the service account with administrative
privileges or another account with administrative privileges:
Type the account name, and then click the Verify User ( ) icon, or
Click the Directory ( ) icon, and navigate to and select the account from the directory:
7. Click OK. The service account or administrative account added as the user's Site Collection Administrator can now view the user's entire
OneDrive account.
8. Repeat Steps 3 through 7 for each user who's OneDrive for Business data is to be backed up with Barracuda Cloud-to-Cloud Backup.
Step 3. Set Up Impersonation Permissions
Use these steps when adding all future users.
Complete the following steps to set up impersonation permission for the service account on all newly created OneDrive users:
1. Log in to your Office 365 Management Panel using the service account created in Step 1. Create a New Service Account.
2. In the left pane click Admin centers > SharePoint, and click user profiles.
3. In the My Site Settings section, Click Setup My Sites.
4. In the My Site Secondary Admin section, click Enable My Site secondary admin.
5. In the Secondary admin field, type the username of the newly created service account.
6. Click OK.
O365


Before getting started, you must add the Barracuda Backup administrator account as a Site Collection Administrator in OneDrive .
Use the following steps to set up OneDrive backup:

2. In the Status page, click OneDrive for Business:
b. From the Cloud Provider Type drop-down menu, select Microsoft Office 365.
c. Click Save.
4. The Add a Cloud Data Source page displays:
a. From the Data Type drop-down menu, select OneDrive for Business.
b. In the Your OneDrive URL field, enter the first part of your OneDrive for Business URL; the URL is available once you log in to
OneDrive for Business. Note that the https:// portion is not required. For example, type mydomain-my.sharepoint.com.
c. Click Authorize.
d. If you are not currently logged in to the OneDrive for Business account, the Microsoft login page displays:
e. Enter your OneDrive for Business administrator login information, and click Sign in.
5. The Edit OneDrive for Business page displays.

6. The Add New Schedule dialog box displays. Enter a name to represent the schedule:
7. Click OK. The Edit OneDrive for Business page is updated with the new schedule name.
9. In the Items to Back Up section:
a. Select individual items to back up, or
b. To back up everything on OneDrive, click Apply to all computers and data sources for this Barracuda Backup Cloud
Service.
12. Click Save. OneDrive is backed up based on your data source and schedule settings.
O365



deselect all days:
days:



Use the following steps to download OneDrive for Business data:
2. Go to Restore > Restore Browser.
3. From the Restore Browser, click OneDrive for Business in the left pane,
and select the user account from which to download data:
4. Navigate through the folder structure to locate the file or folder you want to download,
or use the search field to locate the desired data:
5. The default view displays data that was present during the last backup.
To find an historical revision of a file or folder, click Change Date in the left pane:
7. Once you locate the file(s) or folder to restore, click Download to the right of a single item,
or click Download selected items if you selected multiple items:
8. The Save As dialog box displays. Navigate to and select the location where you want to download the file
or .zip file if you selected a folder or multiple files:

9. Click Save.
O365


Use the following steps to restore OneDrive for Business data:
2. Click the Restore tab, and then click Restore Browser.
3. Click OneDrive for Business in the left pane, and then select the user account from which to restore data:
4. Navigate through the folder structure to locate the file or folder you want to restore,
or use the search field to locate the desired data:
5. The default view displays data present during the last backup. To find a historical revision of a file or folder, click Change Date in the left
pane:
7. Once you locate the file(s) or folder to restore, click Restore to the right of a single item, or click Restore selected items if you selected
multiple items:
8. The Restore dialog box displays. Select to restore to the Original Location and Original Path, or click Specify New Path and specify a
different user and path:


11. Verify the files or folders have been restored in the user's OneDrive for Business account.
O36

In this Section

O365
See Also


Barracuda Cloud-to-Cloud Backup provides complete protection of SharePoint Online. With item-level recovery options, items can be restored
directly into SharePoint Online from the backups of Document Libraries, Site Assets, Site Pages, Picture Libraries, and Form Templates in Team
Sites, Public Sites, Wiki Sites, and Publishing Sites.
Barracuda Cloud-to-Cloud Backup for Office 365 eliminates the risk of lost content due to accidental or malicious deletion. You can also retain
email messages and files indefinitely if users were to leave your organization—all without having to purchase additional licenses.
O365

O36
This article applies to Barracuda Cloud-to-Cloud Backup and Microsoft SharePoint Online.
In order for Barracuda Cloud-to-Cloud Backup to access SharePoint sites, you must create a primary site collection administrator.
You must complete the following steps for each SharePoint Site Collection you want to back up.
To configure the primary site collection administrator for SharePoint Online:
1. Log in to your Office 365 Management Panel using an account with administrative privileges, and go to the Office 365 admin center.
2. In the left pane click Admin centers > SharePoint.
3. Hover over and select the site collection you want to add the administrator to.
4. Click Owners > Manage Administrators:
5. The manage administrators page displays. In the Site Collection Administrators section, enter the name of the administrator you
want to add as a Site Collection Administrator, and click the Check Names ( ) icon to verify the user name is valid. For example, Shar
ePoint Service Administrator:
6. Click OK to save your changes and add the selected administrator as the Site Collection Administrator.



To complete the steps in this article, you must configure a primary site collection administrator. For details, see How to Configure Site
Collection Administration for SharePoint Online Data Sources.
Use the following steps to set up SharePoint Online backup:
1. Log in to Barracuda Backup, and select the Cloud Source in the left pane.
2. In the Status page, click SharePoint Online:
b. From the Cloud Provider type drop-down menu, select Microsoft Office 365.
c. Click Save.
4. The Add a Cloud Data Source dialog box displays:
a. From the Data Type drop-down menu, select SharePoint Online.
b. Enter Your SharePoint URL.
The URL is available once you log in to SharePoint Online.
c. Click Authorize.
If you are not currently logged in to the SharePoint Online account, the Microsoft login page displays. Enter your Shar
ePoint Online administrator login information, and then click Sign in.
5. In the SharePoint Online page, click Accept to authorize Barracuda to back up data from SharePoint Online:

6. The Edit SharePoint Online page displays. Complete the following:

7. The Add New Schedule dialog box displays. Enter a name to represent the schedule:
8. Click OK. The Edit SharePoint Online page is updated with the new schedule name.
10. In the Items to Back Up section, select individual items to back up, or click Apply to all computers and data sources for this

10.
Barracuda Backup Cloud Service to back up everything in SharePoint Online.
13. Click Save. SharePoint Online is backed up based on your data source and schedule settings.


deselect all days:
days:



Use the following steps to download SharePoint Online data:
2. Click the Restore tab, and then click Restore Browser.
3. From the Restore Browser, click SharePoint Online in the left pane, and select the data you want to download:
4. Navigate through the folder structure to locate the file or folder you want to download, or use the search field to locate the desired data:
5. The default view displays data that was present during the last backup. To find an historical revision of a file or folder, click Change Date
in the left pane:
7. Once you locate the file(s) or folder to restore, click Download to the right of a single item, or click Download selected items if you
selected multiple items:

7.
8. The Save As dialog box displays. Navigate to and select the location where you want to download the file or .zip file if you selected a
folder or multiple files.
9. Click Save.
O36


Use the following steps to restore SharePoint Online data:
3. Click SharePoint Online in the left pane, and select the Site from which to restore data:
4. Navigate through the folder structure to locate the file or folder you want to restore, or use the search field to locate the desired data:
5. The default view displays data present during the last backup. To find a historical revision of a file or folder, click Change Date in the left
pane:
7. Once you locate the file(s) or folder to restore, click Restore to the right of a single item, or click Restore selected items if you selected
multiple items:

7.
8. The Restore dialog box displays. Select to restore to the Original Location and Original Path:

11. Verify the files or folders have been restored in the SharePoint Online Site.

Microsoft Windows Small Business Server
Microsoft Windows Small Business Server Backup

How to Install and Use the Barracuda Backup Agent (Windows)
Microsoft Windows Small Business Server Restore
How to Restore a Windows System to Bare Metal
Microsoft Windows Small Business Server Troubleshooting
How to Check Volume Shadow Copy Services Driver State

How to Troubleshoot Using the Barracuda Backup Agent (Windows) Log File
Related Articles
Understanding the Backup Export Tool Master Server


Windows Client Operating Systems
Microsoft Windows Client Operating Systems Backup

Microsoft Windows Client Operating Systems Restore
Microsoft Windows Client Operating Systems Troubleshooting
How to Resolve Snapshot Backup Errors

Understanding Why WindowsApps Folder Restore Failed
Related Articles

File Encryption Support
System, Platform, and Software Compatibility

VMware
VMware has reported an issue with ESXi version 6.0.x where incorrect changed sectors are returned. When a virtual machine (VM) is
running ESXi 6.0.x and Changed Block Tracking (CBT) is enabled, some change areas in data are not reported. When this occurs, that
data is not recognized as changed and is not backed up; current and past incremental backups are potentially compromised. For more
information, see the VMware knowledgebase solution Backing up a Changed Block Tracking enabled virtual machine in ESXi 6.0.x
returns incorrect changed sectors (2136854).
This issue is resolved in VMware ESXi 6.0 patch ESXi600-201511001. For more information, see VMware ESXi 6.0, Patch Release
ESXi600-201511001 (2137545).
VMware Backup
VMware Data Recovery Backup and Restore Permissions

VMware Support Statement
Understanding Which Ports to Open for VMware Accessibility
Understanding Virtual and Physical RDM with Barracuda Backup
How to Set Up a VMware Server and Guests
Network Driver Best Practice for Agent Backup of VMware Virtual Machines
How to Set Granular Retention for VMware and File Share Backups
Understanding Changed Block Tracking on Virtual Machines
How to Enable Changed Block Tracking through the Barracuda Backup Web Interface
VMware Restoration
How to Restore a Virtual Machine to its Original Location

How to Restore a Virtual Machine to a Different Host Protected by Barracuda Backup
How to Restore a Virtual Machine to an Alternate VMware Host not available through the Barracuda Backup Service
VMware Data Recovery Licenses
How to Restore VMware Guest Systems Using LiveBoot
How to vMotion a LiveBooted Virtual Machine from Barracuda Backup
How to Restore a File or Folder within a VMDK using LiveBrowse
Amazon Web Services Replication and Restore

How to Configure the AWS Import Service Role
How to Restore VMware and Hyper-V Virtual Machines to Amazon Web Services
VMware Troubleshooting
Understanding Why VMware Virtual Machine Returns Incorrect Changed Sectors

How to Resolve "VMDK is larger than the maximum size supported by datastore" Error
How to Resolve "Error Creating Snapshot" Error During ESX/ESXi Virtual Machine Backup
How to Resolve "Error Reading Object" Error During ESX or ESXi Virtual Machine Backup
How to Resolve "Error Removing Snapshot" Error During ESX/ESXi Virtual Machine Backup
Understanding "Unable to Quiesce Disk" Warning During ESX/ESXi Virtual Machine Backup
How to Resolve VMware Guest Machine Backup Issues
How to Resolve Slow Incremental Backup with VMware
Related Articles

Best Practices for VMware

How to Boot a VMware Guest System as a Clone Using LiveBoot
How to Shut Down and Destroy a Virtual Machine Recovered Using LiveBoot


This article refers to Barracuda Backup Legacy Release firmware or newer.
Use these tips and recommendations to efficiently protect your VMware environment using Barracuda Backup. For detailed
VMware backup configuration, restoration, and troubleshooting details, refer to the VMware section of Barracuda Campus.
Best Practice
Document the VMware configuration in detail and any subsequent changes. Additionally, it is highly recommended that you familiarize
yourself with the VMware documentation for management, disaster plans, and recovery.
Barracuda Backup provides three methods to protect your virtual environment:
1. Host-based (Agentless) protection;

2. Guest-level (Agent) protection; and
3. Hybrid host- and guest-level protection.
level of protection for your virtual environment and to meet your recovery objectives.
Host-Based (Agentless) VMware Protection
Requires VMware vStorage APIs for Data Protection (VADP); VADP is included with all licensed vSphere editions: Standard, Enterprise,
and Enterprise Plus
Provides image-based agentless protection of guest virtual machines (VMs)
Quick and easy to configure, no need to add VMs as individual sources:
Configure vCenter server as a source if managing multiple ESX servers in a cluster
Use ESX servers as a source if standalone or not managed by vCenter
Automatically detects new and removed VMs
Provides granular file/directory recovery via VMDK Browsing
Preferred method of protection for quick disaster recovery and to meet stringent recovery time objectives
Use LiveBoot to instantly spin up a VM on an ESX server
Use Cloud LiveBoot to spin up a VM in Barracuda Cloud Storage
Quicker and easier method of data restoration, including:
Restore to any ESX server
Choose destination datastore
Overwrite or rename the existing VM
Download individual virtual disks
Uses VMware's Changed Block Tracking (CBT) for incremental forever backups
Host-based VM backups do not include the following as VMware cannot snapshot:
Physical Raw Disk Mapping (RDM) devices
Independent disks
Barracuda LiveBrowse does not support Windows Dynamic Disk partitions; to restore files and folders from a VMDK, back up these disks
using the Barracuda Backup Agent
You cannot exclude individual files or directories from backup
Can cause an increased storage footprint due to image-based backup method, better for short-term retention
Protect Microsoft applications running on VMs using the Barracuda Backup Agent as separate sources in conjunction with host-based
backups, including:
Microsoft Exchange Server – Only databases must be protected using the Barracuda Backup Agent. If you are using host-based
VM backup in conjunction with Agent backup, you do not need to include the File System and System State with the Agent
backup.
Microsoft SQL Server – Only databases must be protected using the Barracuda Backup Agent. If you are using host-based VM
backup in conjunction with Agent backup, you do not need to include the File System and System State with the Agent backup.
Microsoft Active Directory – Databases and System State must be protected using the Barracuda Backup Agent.
Guest-Level (Agent) VMware Protection
Provides incremental forever file-level protection of guest VMs using the Barracuda Backup Agent
Backups treat each VM like a physical client
Application-consistent protection for Microsoft applications, including:
Exclude any file, file type, or directory
Run pre- and post-backup scripts
Back up Physical RDM devices
Back up Independent disks

Provides more granular recovery options including:

Restore files and directories to any client running the Barracuda Backup Agent
Designate the path where files are restored
Restore files and directories to a Barracuda Copy account
Download individual files and directories (locally and cloud)
Complete system restore through:
Bare metal restoration to a new computer without a pre-installed operating system
Restore the entire file system or individual volumes to a target system with a pre-installed operating system
Provides a smaller storage footprint due to file-level backup and deduplication; this is potentially a better option for servers needing to
adhere to longer retention policies, such as a file server needing to retain historical revisions for several years
Does not provide instant recovery via LiveBoot or Cloud LiveBoot

Linux Systems, Macintosh OS X, AIX, Unix, and Novell NetWare
System Backup
How to Set Up a Root Account to Back Up Macintosh OS X

How to Back Up Linux/UNIX Data Using SSHFS
How to Back Up NFS Mounts with the Barracuda Backup Agent (Linux)
How to Back Up NSS Mounts with the Barracuda Backup Agent (Linux)
How to Back Up an Oracle Database on Linux Using RMAN and Barracuda Backup
How to Create a Pre- or Post-Agent Backup Command Batch File or Script
System Restoration
How to Restore a Linux Server Using Bare Metal Restore
Troubleshooting
How to Change the Barracuda Linux Backup Agent Port Number
Related Articles

Barracuda Agent versus File Share Backup

GroupWise
The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Novell NetWare Server and
GroupWise 8 and 2012, except where noted.
GroupWise Backup
How to Configure GroupWise Message-Level Backups
GroupWise Restoration
How to Restore Exchange and GroupWise Messages
Related Articles

Barracuda GroupWise Trusted Application Key Generator

IBM Domino Server
IBM Domino Backup
Understanding IBM Domino Server Backup


MySQL
MySQL Database Backup
How to Back Up MySQL Databases
Related Articles

Oracle Database
Oracle Database Backup
How to Back Up an Oracle Database on Microsoft Windows Using RMAN and Barracuda Backup

FirstClass Mail
FirstClass Mail Backup
How to Back Up FirstClass Mail

System Backup
How to Back Up Network Addressable Storage - NAS
Related Articles

SAP
SAP is enterprise resource planning (ERP) software that uses a backend database to store data. Barracuda Backup can back up these backend
databases including:

Oracle Database
MySQL

Deployment Options
In this Section
Barracuda Backup Deployment Template

Site-to-Site Deployment
Site-to-Cloud Deployment
Cloud-to-Cloud Deployment
Barracuda Cloud Storage Deployment
Local Control Deployment
Virtual Deployment
Public Cloud Hosting
Related Articles
Barracuda Backup Replacement and Data Migration

Back Up Data Sources
Restore Data Sources

Barracuda Backup Deployment Template
The articles in this section refer to Barracuda Backup firmware version 6.4 or newer.
Configuration Guidelines
This article is intended as a configuration guideline; your deployment will be specific to your environment. Review any administrative
changes with your IT team before proceeding.
This template is a based on a typical onsite deployment of the Barracuda Backup appliance, and describes the initial setup.
You may need configuration access to the servers you intend to add as Backup source devices. If deemed necessary, you may also need
permissions to make firewall changes. To facilitate your deployment, collect the information about your data sources and environment as shown
in Table 1.
Table 1. Data Source Details.

Systems Details
Server Operating Systems Total number of each type of system

Whether system is physical or virtual, and if virtual, are they
clustered
If you are running Microsoft Exchange Version of each database

Number of databases running each version
If you are running Microsoft SQL Version of each database

If you are running any other messaging Type of messaging or database system
or database system Version of each database
Other environments RIS/PACS

Enterprise Vault
Check warehousing/storage (financial)
Imaging systems storage
Source code repositories
DFS servers (4+ TB)
Data Details
Data Retention Expected retention period on backup data

List exceptions
Message-level backups or email archiving Determine if email retention period differs from standard
backup retention schedule
Raw data Total approximate raw data expected to back up in TB
Network Information Details
Data Replication (provide bandwidth details) Barracuda Cloud Control

Another Barracuda Backup device (Private Cloud)
Connection Wan or low bandwidth
Firewall or QoS device Note any servers separated from the Barracuda Backup appliance
through a Firewall or QoS device (either network device or local
host based system)
Internal network 10.128.0.0/9 subnet
Internal connection Do internal connections from the Barracuda Backup appliance to

the network use 10GB fiber?

Alternative Backup Software/Conflicts Details
Other Backup Systems Note any servers with a backup agent or other backup product
Note whether another backup solution will be running in
parallel with the Barracuda Backup appliance
Physically Install and Configure the Barracuda Backup Appliance
The following instructions apply to Barracuda Backup appliance models 390 and above; model 190 is a desktop unit.
Verify Equipment
To install and configure, you need the following:
Barracuda Backup appliance, AC Power Cord (included)

Serial number and linking code (on back of this guide)
Connectivity and access information for servers to back up
VGA Monitor (recommended)
USB or PS2 Keyboard (recommended)
For Ethernet models, an Ethernet connection is required*
For LC Fiber models, an LC SFP or SFP+ connection is required*
*Cabling differs based on the appliance model. For more information see Barracuda Backup Hardware Specifications.
Installation
Physically install the Barracuda Backup appliance using the following steps:
1. Fasten the Barracuda Backup appliance to a 19-inch rack or place it in a stable location.
2. Connect an Ethernet cable from your network switch to the Ethernet port on the back panel of the appliance, and any additional cables
as necessary.
3. Connect a standard VGA monitor, PS2/USB keyboard, and an AC power cord to the Barracuda Backup appliance.
4. Press the Power button on the front panel to turn on the appliance.
By default, your Barracuda Backup appliance is configured to obtain an IP address on your network using DHCP; if DHCP is acceptable, proceed
to the section Firewall Ports, however, if you need to specify a static IP address, connect a monitor and keyboard to the Barracuda Backup
appliance using the instructions in the article Barracuda Console.
Firewall Ports
If the Barracuda Backup appliance is located behind a corporate firewall, you may need to open the following ports to allow communication
between the appliance and Barracuda Networks: Ports 80/443, 1194, and 5120-5129 outbound for TCP/UDP are required for communication.
Ports 5120-5129 are used to replicate data to Barracuda Cloud Storage. Barracuda Backup uses these ports to securely transfer data over the
Internet to the offsite storage location. Contact Barracuda Technical Support to restrict outbound network traffic on these ports to only reach
Barracuda Networks. By default, your Barracuda Backup appliance is configured to obtain an IP address on your network using DHCP. To
specify a static IP, use the console administration interface.
Create a Barracuda Cloud Control Account
You must have a Barracuda Cloud Control account to use Barracuda Backup. If you do not already have an account, follow these steps:
1. Log in to http://login.barracudanetworks.com/.
2. If you do not have an account, click Create a User, follow the account creation instructions, and log in.
Standard Activation
Local Control
If you plan to manage your Barracuda Backup appliance independently of Barracuda Networks Cloud, refer to Understanding Local
Control.
Use the following steps to link your Barracuda Backup Appliance:

1. Go to http://login.barracudanetworks.com/, and log in.
2. Once logged in, click Backup in the left pane. If this is your first time linking a Barracuda Backup appliance, click Start Backup
setup; otherwise, click the Backup ( ) tab, and go to Admin > Activate Backup Product.
3.

3. Enter the Serial number and Linking code from the sticker on the back of the Quick Start Guide included with the appliance, and
indicate your Identity. Click Continue.
4. Enter your Location and Time Zone.
To manage the appliance independently of Barracuda Cloud Control (conectionless), turn on Locally control device unde
r Device Management, and proceed to Step 6 below.
5. Select Replicate data to Barracuda Cloud Storage, select the Storage Amount and Subscription Period if you intend to
replicate data to Barracuda Cloud Storage; no Cloud Storage subscription is required for site-to-site replication.
6. Enter your Billing Information, and read and accept the Terms and conditions.
7. Click Activate Barracuda Backup.
Reseller Activation
Use the following steps to link customer Barracuda Backup Appliances:

1. Go to http://login.barracudanetworks.com/, and log in using a registered reseller account.
2. Once logged in, click Backup in the left pane. If this is your first time linking a Barracuda Backup appliance, click Start Backup
setup; otherwise, click the Backup ( ) tab, and go to Admin > Activate Backup Product.
select I am a reseller, and this Barracuda Backup appliance is for a client as the Identity. Click Continue.
4. Enter the Location and Time Zone for the appliance.
5. Select Replicate data to Barracuda Cloud Storage, select the Storage Amount and Subscription Period if you intend to
8. The end-user is sent an email verifying the serial number is to be added to their account.
9. Once verified, both the end-user and reseller can access the Barracuda Backup appliance.
Verify Connection
The Barracuda Backup appliance you have just installed, powered on, and linked, should be listed in the left pane with a green indicator ( ) to
the left of its name. If the status for your Barracuda Backup appliance is green, continue to the next step. Otherwise, return to the setup steps to
fix the network settings and connectivity for your appliance, or contact Barracuda Networks Technical Support for additional direction.
Update Appliance Settings and Firmware
From the System > Barracuda Backup Appliance Settings page, you can add and update Barracuda Backup appliance settings including:
Backup Appliance Name – Name used to identify the currently selected Barracuda Backup appliance in the web interface
Backup Appliance Time Zone – The time zone where the currently selected Barracuda Backup appliance is located
Backup Appliance Location – The physical location of the Barracuda Backup appliance including city, state, and country
Backup Appliance Display Group – The display group in which the Barracuda Backup appliance resides
Manage your display groups – Click to add or remove a display group in the Admin > Display Groups page
Backup Export Tool Settings – Set up the Backup Export Tool.
When you log in to Barracuda Backup, if there is a newer version of firmware available, a notification banner displays across the top of the page.
To update the firmware, go to the System > Firmware Settings page, and click Upgrade Now to immediately begin the firmware upgrade, or
click Dismiss to hide the banner until the next time you log into the web interface.
From the System > Firmware settings page, you can select the firmware upgrade policy:
1. Current Installed Version – Displays the currently installed firmware version
2. Firmware Upgrade Policy – Select the release stage you want to update to the latest firmware
3. Firmware Available – Specifies the latest firmware version available based on the selected Upgrade Policy
4. Check for new firmware – Click for firmware availability
5. Upgrade Now – If a newer version of firmware is available, click Upgrade Now to upgrade the firmware
6. Release Notes – Review release notes by version
Additional Information
For additional information, refer to the Barracuda Backup Appliance Settings Page .

Configure Backup Source Devices
Use the following steps to set up systems located on the same network as your Barracuda Backup appliance as backup source devices.
For additional details on configuring backups and a list of supported data types, refer to the article How to Configure Backups.
For more information on setting up specific Backup Source Devices, for example, Microsoft Exchange Server 2010, refer to the
section Backing Up Data Sources.
1. Log in to the Barracuda Backup appliance.

2. For Linux and Windows data sources, install the Barracuda Backup Agent available on the System > Software Download page.
3. Go to Backup > Sources, and click Add a Computer.
4. Enter the backup source details:
a. Enable backups – Enable backups based on a configured backup schedule.
b. Computer description – Name to identify the server.
c. Computer name – FQDN or IP address; must be resolvable on your local network.
d. Computer type – Data source device type.
e. The requested connection information is based on the selected Computer Type. For network file shares, select Enable File
Share Backups, and enter your credentials.
5. Click Save. Specify the data source details in the Add Data Source page.
6. In the Add to Schedule section, select an existing schedule from the drop-down menu, or click Add New to create a new schedule.
7. Click Save. The Edit Backup schedule page displays.
8. Choose Select all items to back up the entire computer, or choose Select specific items to select individual items for backup.
9. Specify the time of day the schedule is to run, and click Save.
For Windows-based agent shares, if you want to be able to do a bare metal recovery, make sure to back up all system
volumes and system state.
Connection Information
Requested connection details are based on the selected Server Type.

The Barracuda Backup Agent (Windows) is enabled by default for Windows Servers; install the Agent from the Syste
m > Software Downloads page in the web interface.
To back up network file shares, turn on Enable File Share Backups, and enter your credentials.
Authentication and System Configuration Notes

Backups for Mac OS X/Linux/UNIX (SSH Connections)
Barracuda Backup uses an SSH (Secure Shell) client to access data contained on Mac OS X or Linux / Unix based computers
running an SSH daemon. The SSH client uses public key cryptography to establish a secure connection to the SSH daemon.
You must configure SSH access to any Mac OS X or Linux / UNIX computer you want to back up. Follow the on-screen instructions
on the Backup > Sources > Add Computer page according to the operating system.
Directory-Based File Shares
When you back up a file share you must specify the share name on the network before you can select the folders to be backed up.
On a Windows machine, a share name can be a drive volume such as "C$", or a folder and its associated subfolders such as "My
Documents". At a minimum you will need Read access to the data that you are backing up and Change Access or Full Control to the
shares in order to perform a restore. For Mac OS X and Linux / Unix-based computers with SSH connections, the share name
should be the entire path to the directory you would like to back up, e.g., /home/<user>.
When you select folders for backup you should begin by selecting the folders at the top of the folder tree hierarchy, and then
deselect folders lower in the hierarchy that you do not want to back up. You can also specify an optional exclusion rule, which is
applied when the backup runs to rule out files that do not meet your back up criteria.
Message-Level Backup: Microsoft Exchange and Novell GroupWise
When you select the Message-Level Backup data type, you must supply the authentication information to access your mail server
before you can select which mailboxes to back up. In addition to the authentication information provided on the Barracuda
Backup web interface, you must configure the Message-Level settings on your Exchange or GroupWise server.
For Microsoft Exchange servers, refer to Exchange Message-Level Backups for detailed instructions for configuring message-level
backups.
For GroupWise, refer to GroupWise Message-Level Backups for detailed instructions for configuring message-level backups.
Supported Data Types

For additional information, refer to the Supported Data Types section.

Backup Schedules
Once you configure computers and data sources, create granular backup schedules. Select specific sets of data to back up and configure
multiple schedules for each source, each with different sets of data selected. See the Schedules Page for more information.
To create a backup schedule:

Go to the Backup > Schedules page of the Barracuda Backup web interface. Click Add a Schedule and fill in the information on the Add
Backup Schedule page:
Schedule Name – Enter a label to identify the backup schedule.

Items to Back Up – Turn Apply to All Computers and Data Sources for this Barracuda Backup Appliance on to back up all
content, or turn off, then expand and select the items you want to back up.
Schedule Timeline – Turn on the days you want the back up to run.
Daily Backup Timeline – Enter the start time; turn on Repeat if you want to specify a time period and end date to repeat the
backup.
If the backup schedule is for Microsoft SQL or Microsoft Exchange, you must specify the type of backup to run:
Complete – This backup type performs a full backup of data, including the transaction logs.
Log – This backup type only backs up transaction logs created since the last full backup.
Smart – This backup type is a combination of the full backup and the transaction log backup, minimizing the impact of backups on
network resources necessary to transfer data offsite. Barracuda Networks recommends this backup type for SQL and Exchange
servers.
With the Smart Backup type, threshold values are used to determine when to switch between full and log backups. The minimum threshold
value specifies how many days Barracuda Backup continues to back up transaction logs before another full backup is run. After the minimum
threshold value is met, Barracuda Backup determines whether to perform another backup based on the binary data queue. If the binary data
queue size exceeds 1 GB, Barracuda Backup continues the transaction log backup until:
the maximum threshold level is met, or

the queue size drops below 1 GB
Set the Backup Rate Limit (Optional)
Rate limits control the data replication rate to Barracuda Cloud Storage or other offsite storage locations. You can limit Internet bandwidth
consumption during peak usage times, and schedule backups for non-peak hours.
Your initial offsite backup may take on the order of days to complete but all of the data is backed up locally on the Barracuda Backup appliance
during this period. After the initial large transfer is complete, replicating your data offsite should complete with only a few hours of transfer each
day. By default, Barracuda Backup is configured to run full speed data transfers at night so that bandwidth is not affected while most people are
at work. An alternate rate limit allows you to adjust the limit speed and time interval.
The length of transfer time it will take to get your data offsite is impacted by the compression and deduplication rates on your data, the uplink
speed of your Internet connection, the amount of data that changes every day, and any speed limits you apply to Barracuda Backup.
To set the backup rate limit:

1. Go to the Backup > Replication page, and click Add a Target.
2. In the Add Replication Target, enter the Replication Target Information.
3. In the Rate Limit section, the following options are available:
Option Settings Details
Default Rate Limit Full Speed – Uses 100% of Specify the default rate limit.
available bandwidth
Kb/s or Mb/s – Specify the rate
limit in Kilobits or Megabits per
second
Alternate Rate Limit Full Speed – Uses 100% of You can optionally create an alternate
available bandwidth rate limit which is maintained only during
Kb/s or Mb/s – Specify the rate the specified time periods:
limit in Kilobits or Megabits per
From/To – Specify the start and
second
end time (24 hour format)
On – Select the days on which the
alternate rate limit applies
4.

4. Click Save.
Exclude Files from a Backup (Optional)
You can create exclusion rules that use pattern matching to identify directory or file names that are not to be backed up. Files which are typically
excluded from backups include temporary files, music, movies and other files which are not essential for business needs.
Use the following steps to create an exclusion rule:

1. Go to the Backup > Exclusions page of the Barracuda Backup web interface. Click Add an Exclusion.
2. Fill in the information on the Add an Exclusion page:
Exclusion Rule Name – Enter a descriptive label to identify the exclusion rule.
Add Exclusions to Reports – Turn on to include exclusions in reports, and turn off if you do not want to include exclusions
in the reports.
Apply Recursively to Sub Directories – Specify whether to apply the exclusion rule recursively to sub directories.
Where to Exclude – Turn Apply to All Computers and Data Sources for this Barracuda Backup Appliance on to apply
the exclusion rule to all computers and data sources for the selected Barracuda Backup appliance, or turn off, then expand
and select the items to which to apply the exclusion rule.
3. In the What to Exclude section, specify what to exclude:
From the Preset Expressions menu, select the content you want to exclude, for example, Video files, then click Add.
In the Expressions field, enter a search string to exclude, for example, *.mp3, then click Add.
4. Click Save at the top of the page to add the exclusion rule.
To edit an existing exclusion rule, go to the Backup > Exclusions page of the Barracuda Backup web interface, and click Edit following the
exclusion rule you want to edit. Make the necessary changes, then click Save.
To delete an exclusion rule, go to the Backup > Exclusions page of the Barracuda Backup web interface, and click the Remove following
the exclusion rule you want to remove. Click OK to remove the rule.
Create Data Retention Policies
Data is retained based on a traditional grandfather-father-son (daily-weekly-monthly) rotation model. You can specify how long to keep daily,
weekly, monthly, and yearly backups by creating data retention policies. Different retention policies can be created for different sets of data
including files, data backed up by the Barracuda Backup Agent (Exchange, SQL, System State), and email messages.
You can create one policy for all of the computers and data sources on a Barracuda Backup appliance or multiple policies that each include some
subset of the data.
To set retention policies:

1. Go to Backup > Retention Policies, click Add a Retention Policy, and enter a name to identify the policy.
2. In the Items to Retain section, specify the data sources to which the retention policy applies; the Retention Timeline section
displays. Select a timeline template on which to base your retention policy, or specify your own revision timeline.
3. If applicable, specify the Email Message Timeline.
4. Click Save.
When data is removed according to a retention policy, it is deleted from both the local Barracuda Backup appliance and the offsite storage
locations. Removed files that have been backed up using Network File Shares Protocol or SSHFS may be retained for a longer period of
time, according to the configuration. Otherwise, once your data has been purged, it is gone forever. Purging applies to historic file revisions
only; your current data is not impacted by a retention policy.
Your initial backup takes some time to complete; you can view backup status in the Reports > Backup page.
Replicate Data to another Barracuda Backup
Before configuring a backup destination, verify the following:
1. Make sure that your retention policies are configured before configuring replication. Otherwise you may waste bandwidth copying data
that does not need to be replicated.
2. Verify Internet connectivity between the local and remote Barracuda Backup appliance(s). Configuring a secure VPN connection
between multiple Barracuda Backup appliances ensures the highest level of security possible.
3. You must have the serial number and replication code of the destination Barracuda Backup appliance. Go to the destination Barracuda
Backup appliance, and go to the Backup > Replication page. The serial number and replication code display at the top right of the
page.

Important
Only the Barracuda Backup appliance 490 and higher can act as a backup to other Barracuda Backup appliances, although
any Barracuda Backup appliance can send data.
Data can be backed up to both a second Barracuda Backup appliance and to Barracuda Cloud Storage. Data that is backed
up on a second Barracuda Backup appliance cannot be backed up yet again onto another Barracuda Backup appliance.
For every Terabyte of data replicated, Barracuda Networks recommends a 1.5 Mbps or T1 connection.
You must have the serial number and replication code of the destination. These can be found by selecting the destination
Barracuda Backup appliance and looking at its Backup > Replication page.
Barracuda Backup appliances that are used to back up the data from one or more Barracuda Backup appliances are known as destinations. Data
from one Barracuda Backup appliance can be replicated to one or more destinations.
To configure data replication,
1. Log in and select the Barracuda Backup appliance to which you want to add a replication destination, and go to the Backup >
Replication page.
2. To add a replication destination, click Add a Target.
3. In the Add Replication Target page, enter the target Barracuda Backup details in the Replication Target Information section.
4. In the Rate Limit section, select the Default Rate Limit; by default, Barracuda Backup uses Full Speed as the default rate limit.
5. Optionally, you can enable an Alternate Rate Limit.
6. Click Save.
Once a target is added, it appears in the Sending Data To table. If the status displays as online ( ), the two systems are able to
communicate with each other.
On the Backup > Replication page, there is a global flag to replicate all data to either Barracuda Cloud Storage or to Barracuda Backup
appliances.
If you want to send data from diverse sources to both of these options, then do not set this flag on any items in the Target List. Instead, edit each
data source on the Backup > Sources page, and specify where its data is to be replicated.
This option is not available in Local Control.
Edit Replication Settings
To edit the replication target settings, click Settings in the Target List. In the Replication Target Settings list, you can modify the destination IP
address, disable data replication, modify rate limits, and specify whether to send all data on the Barracuda Backup appliance to this target.
Remove a Barracuda Backup Appliance
To permanently remove a replication destination, click Remove in the Target List.
Disable Replication
Click Disable all Replication to <target> to temporarily disable data replication for up to 24 hours.
Send Data To/Receiving Data From
Destination Barracuda Backup appliances display in the Sending Data To table. If a Barracuda Backup appliance is acting as a destination for
another Barracuda Backup appliance, it displays in the Receiving Data From table.
View Reports
Barracuda Backup provides detailed reports including:

Backup Reports – From the Reports > Backup page, you can view detailed reports for each backup that is run including any back
up process that is currently running. Backup reports include details about the backup such as when the backup started, duration,
size, if there were any errors or warnings, and any new, changed, or removed items. Reports also include links to each backed up
file to view or download the item from the report.
Click Details to view recent activity in chart form. You can also view a list of backed up files including the number of new, changed,
and removed files, as well as a list of any errors encountered during backup.
If a backup is currently in progress, the Reports > Backup page displays this information and allows you to cancel the backup.
Click View Past Reports to access archived backup reports in the Backup (Archived) page. You can specify the number of reports
you wish to display on the page, or enter a date range and click Update to display the archived reports.
Restore Report – View restoration details in the Reports > Restore page. Click Details to view all details for the selected
restoration including any encountered errors. Expand the detail tabs to view specific file errors and a list of restored files.

Large Items Report – View a detailed list of large items by source or file name in the Reports > Large Items page. From the Sourc
es drop-down menu, you can select to view large items by individual sources or for All sources. To further refine the report, enter a
string in the Filename contains field, and click Filter. The report displays only those large items matching the filename content for
the selected Source.
Audit Log – View a report of all activities in the Barracuda Backup web interface by time and date, by user, and by action. Logged
activities include log on authentication, firmware update, changes to settings, changes to account information, and more.
Create Display Groups
If you have multiple Barracuda Backup appliances, you can manage them through display groups. Go to the Admin > Display Groups page, and
follow the on-screen instructions.
For additional information, refer to Display Groups Page.

Site-to-Site Deployment
This article assumes each Barracuda Backup appliance in the deployment is physically installed and connected to the network.
In a site-to-site deployment, a Barracuda Backup appliance acts as a backup or "private cloud" to replicate data from one or more Barracuda
Backup appliances. Each Barracuda Backup appliance can send data to one or more other Barracuda Backup appliances. In the following image,
a target Barracuda Backup appliance acts as a backup to two other Barracuda Backup appliances:
CONFIGURE THE BARRACUDA BACKUP APPLIANCE
Use the following steps to configure your Barracuda Backup appliance.
1. Go to the following URL: http://login.barracudanetworks.com/

2. Complete the fields on the Create New Account page, and click Submit.
Configure the IP Address and Network Settings
By default, the Barracuda Backup appliance is configured to obtain an IP address on your network using DHCP. If you want to assign it a static IP
address instead, you can configure it using the console administration interface. If not, skip the following steps:
To configure the Barracuda Backup appliance to use a static IP address:
1. Connect a monitor and keyboard to the Barracuda Backup appliance.

2. Use your arrow keys to highlight the DHCP/Static field.
3. Using the spacebar select Static for your IP address assignment preference.
4. Enter the IP Address, Netmask, Default Gateway, Primary DNS Server, and Secondary DNS Server (optional) as appropriate for your
network.
5. Click Enter on the Commit Changes box.
Once changes are committed, the Barracuda Backup appliance attempts to connect to Barracuda Networks.
The LAN and Internet boxes on the console administration interface are green when the Barracuda Backup appliance is determined to be online.
The Barracuda box remains red until it is linked to an account later in the installation process.
Configure Your Corporate Firewall
between the Barracuda Backup appliance and the Internet. In site-to-site deployment, you can specify the ports to use for replication on the Back
up > Replication page, or optionally, you can replicate over ports 5120-5129.
Ports 80, 443, 1194, and 5120-5129 outbound for both TCP and UDP traffic. The ports are used to transfer data to either Barracuda
Cloud Storage or to another Barracuda Backup appliance over the Internet. In site-to-site deployment, data can be replicated either over
ports 5120-5129 or over a set of ports you specify on the Backup > Replication page.
Cloud Replication

If you would like to restrict the outbound network traffic on these ports to Barracuda Cloud Storage, contact Barracuda
Networks Technical Support for a list of the IP addresses to allow.
Link Your Appliance
Your Barracuda Backup appliance must be linked to your Barracuda Cloud Control Account before you can initiate data backups.
To link your Barracuda Backup appliance:
1. Go to http://login.barracudanetworks.com/, and log in using your Barracuda Cloud Control credentials.

2. Once logged in, click Backup in the left pane. If this is your first time linking a Barracuda Backup appliance, click Start Backup setup;
otherwise, click the Backup ( ) tab, and go to Admin > Activate Backup Product.
5. Select Replicate data to Barracuda Cloud Storage, select the Storage Amount and Subscription Period if you intend to replicate
data to Barracuda Cloud Storage; no Cloud Storage subscription is required for site-to-site replication.
8. The linking process may take a few minutes to complete. Wait until the Dashboard page displays. A green light displays next to the
appliance name indicating it is successfully linked to your account.
Add the Appliance Name and Location
Use the System > Barracuda Backup Appliance Settings page to view or modify the Barracuda Backup appliance details including name, time
zone, physical location, and display group:
Barracuda Backup Appliance Name – Name used to identify the currently selected Barracuda Backup appliance in the web interface
Barracuda Backup Appliance Location – The physical location of the Barracuda Backup appliance including city, state, and country
Barracuda Backup Appliance Display Group – The display group in which the Barracuda Backup appliance resides
Create Display Groups (Optional)
If you have multiple Barracuda Backup appliances, you can manage them by creating display groups on the Admin > Display Groups page.
See the Display Groups Page for more information.
CONFIGURE DATA SOURCES
This section describes how to configure backups.
Add Systems and Select Data Sources
There may be more than one data source on each server, and each can have unique back up characteristics.
See Backup Up Data Sources for details by data source type.
See Data Backup Tasks for step-by-step instructions on setting up data sources.
Create Backup Schedules
multiple schedules for each source, each with different sets of data selected. See the Schedules Page for more information.
See the Schedules Page for more information.

including files, data backed up by a Barracuda Backup Agent, and email messages.
subset of the data.
See the Retention Policies Page for more information.
See Creating Effective Retention Policies for revision timelines, removed file rules, and removed email timelines.
Modify Replication Rate Limit (Optional)
See the Rate Limit Page for more information.
excluded from backups include temporary files, music, movies and other files which are not essential for business needs in the Backup >
Exclusions page.
See the Exclusions Page for more information.
Check Backup Reports

View reports on an ongoing basis as needed. The Reports > Backup page contains detailed backup reports. A list of in progress backups
displays at the top of the page, and once a backup is complete, a detailed report displays in a table by device. Click Details following the report
you want to view.
See the Reports Page for more information.
SECURE APPLIANCE
This section describes how to secure your Barracuda Backup appliances.
Communication and Configuration
Administration and backup configuration that is set using the Barracuda Backup web interface is sent to the Barracuda Backup appliance via a
256-bit encrypted VPN tunnel. The Barracuda Backup appliance uses HTTPS port 1194 to send status updates to Barracuda Backup. Data
transfers are initiated by the Barracuda Backup appliance rather than by Barracuda Cloud Storage or a remote Barracuda Backup appliance.
Data Transmission and Storage
Data transferred between your network and Barracuda Cloud Storage, or between your network and a remote Barracuda Backup appliance, is
always encrypted. File parts are AES 256-bit symmetrically encrypted before they are stored, and they remain encrypted until a restore is
requested.
Management Access
Monitor Activity – You can check the user activity page periodically for authentication attempts, changes to settings, and updates to
account information. Go to the Admin > User page to see all activity for an account, including logins and when a user has enabled or
disabled replication.
Restrict Logins by IP Address – You can restrict access to Barracuda Backup to one or more IP addresses. On the Admin > Users pa
ge, click Edit to edit a user account; enter an IP address or a range.
Secure Network Access – HTTPS is used for secure web browser communication with Barracuda Backup unless logging in to the local
web interface.

Encryption
Data transfers from the local Barracuda Backup appliance to a receiving Barracuda Backup appliance are always encrypted. Data is stored
compressed and encrypted at rest on the receiving Barracuda Backup appliance; the local Barracuda Backup appliance does not store in an
encrypted or compressed state. Barracuda Backup utilizes an aggressive combination of symmetrical and asymmetrical encryption. The United
States government recently approved 192-bit AES encryption as the preferred method for protecting top-secret information. The Barracuda
Backup solution starts with even higher 256-bit AES encryption. In addition, Barracuda Networks has developed a proprietary advanced digital
cataloging system that breaks down your data into small pieces and tracks the changes of these parts over time, and strips the original meta
identifiers from your files.
As data is transmitted to the remote Barracuda Backup appliance, your symmetrically-encrypted data parts are compressed and sent over your
Internet connection with an asymmetrically-encrypted key.
CONFIGURE REPLICATION
This section describes how to configure replication.
Important
Replication page.
6. Click Save.
appliances.
Disable Replication

See the Replication Page for more information.
RESTORE DATA FROM REPLICATION DESTINATIONS
Only the Barracuda Backup appliance 490 and higher can act as a backup to other Barracuda Backup appliances, although any
Barracuda Backup appliance can send data.
To restore from a replication destination,
1. Log into the Barracuda Backup web interface, and select the receiving Barracuda Backup Server from which to restore.
2. Go to the Restore > Restore Browser page, and in the left pane select the sending Barracuda Backup appliance from which you are
receiving data:
3. Expand the sending Barracuda Backup appliance to review its backup sources, and click on the server or computer from which to
restore; the contents displays in the right pane:
4. In the Contents section, click Restore next to the file or directory you wish to restore; the Restore window displays.
5. In the Restore to field, enter the hostname or IP address of the restore to location. In the Path section, select the Original Path, or
designate a new location.
6. Click Start Restore. Once the restore is complete, go to Reports > Restore to verify the restore completed successfully.

Configuring Replication
Any Barracuda Backup appliance can send data to another Barracuda Backup appliance, however, only Barracuda Backup
appliance 490 and higher can act as a backup to other Barracuda Backup appliances. When backing up to a second Barracuda
Backup appliance, both appliances must be on the same firmware version.
See also: How to Configure Amazon Web Services as a Replication Target
Do not configure more Backup senders to Backup receivers than would exceed the internal capacity. For example, if you have a
Barracuda Backup 890 with an internal capacity of 16 TB, and you want to configure this system to receive data from multiple
Barracuda Backup 390 appliances which have an internal capacity of 2 TB, the total amount of Barracuda Backup 390 appliances
sending to the Barracuda Backup 890 should not be more than 8.
Before Starting Replication
Verify Internet connectivity between the local and remote Barracuda Backup Server(s). Configuring a secure VPN connection between multiple
Barracuda Backup Servers ensures the highest level of security possible.
Verify Retention Policies
Make sure that your retention policies are configured before configuring replication. Otherwise you may waste bandwidth copying data that does
not need to be replicated. On the Barracuda Backup Server, go to the Backup > Retention Policies page and verify that the retention policies
are configured before configuring replication to avoid copying data that does not need replication.
Verify Internet connectivity between the local and remote Barracuda Backup Server(s). Configuring a secure VPN connection between multiple
Barracuda Backup Servers ensures the highest level of security.
Configure Destinations
Barracuda Backup Servers that are used to back up the data from one or more Barracuda Backup Servers are known as destinations. Data from
one Barracuda Backup Server can be replicated to one or more destinations.
Note: Before you can configure a destination, you must have the target Barracuda Backup Server serial number and replication code. To locate
these values, select the target Barracuda Backup Server in the list, and go to the Backup > Replication page. The serial number and replication
code display to the right of the target Barracuda Backup Server name.
1. Select the Barracuda Backup Server in the list, and go to the Backup > Replication page.
2. Click the Add a Target link.
3. Enter the target Barracuda Backup Server IP address or hostname, serial number, and replication code. Click Save.
4. The server displays in the Sending Data To table.
Once the status displays as Online the two systems are able to communicate with each other.
Specify Data Replication Destination
1. Select the Barracuda Backup Server in the list, and go to the Backup > Replication page.
2. In the Sending Data To table, in the Global Setting column, you specify whether to replicate all data to Barracuda Cloud Storage or to a
Barracuda Backup Servers. To send data from diverse sources to both of these options, do not turn on the flag. Instead, edit each data
source on the Backup > Sources page, and specify where its data is replicated.
Remove a Destination
1. Select the Barracuda Backup Server in the list, and go to the the Backup > Replication page.
2. In the Sending Data To table, click on the Remove link beside the destination Barracuda Backup Server.
Loss of Communication
If there is a loss of communication between the Barracuda Backup Server and its back up destinations, the data to be be backed up is queued
and errors are generated. Data is queued until the issue is resolved. The queue size in the table on the Backup > Replication page indicates
how much data is waiting to be replicated. Not all of this data is actually copied to the destination; some of it is deduplicated as the replication
proceeds. Only those parts that are not already stored in the remote location are sent over the Internet.

Site-to-Cloud Deployment
Barracuda Cloud Storage subscription plans provide diverse offsite storage that scales to meet your changing data requirements. Barracuda
Cloud Storage includes secure backup to two separate data centers. Storage is allocated in 200 gigabyte increments and is all disk-based. The
following image shows two Barracuda Backup appliances replicating data to Barracuda Cloud Storage:
CONFIGURE THE BARRACUDA BACKUP APPLIANCE
Use the following steps to configure your Barracuda Backup appliance.
1. Log in to https://login.barracuda.com.
2. If you do not have an account, click Create a User, follow the account creation instructions, and log in.
Configure IP Address and Network Settings
address instead, you can configure it using the console administration interface. If not, skip the following steps:

2. Use your arrow keys to highlight the DHCP/Static field.
3. Using the spacebar select Static for your IP address assignment preference.
4. Enter the IP Address, Netmask, Default Gateway, Primary DNS Server, and Secondary DNS Server (optional) as appropriate for your
network.
5. Click Enter on the Commit Changes box.
Once changes are committed, the Barracuda Backup appliance attempts to connect to Barracuda Networks.
The LAN and Internet boxes on the console administration interface are green when the Barracuda Backup appliance is determined to be online.
The Barracuda box remains red until it is linked to an account later in the installation process.
Configure Corporate Firewall
between the Barracuda Backup appliance and the Internet.
Ports 80, 443, 1194, and 5120-5129 outbound for both TCP and UDP traffic. The ports are used to transfer data to either Barracuda
Cloud Storage or to another Barracuda Backup appliance over the Internet. In site-to-site deployment, data can be replicated either over
ports 5120-5129 or over a set of ports you specify on the Backup > Replication page.
Cloud Replication
If you would like to restrict the outbound network traffic on these ports to Barracuda Cloud Storage, contact Barracuda

Networks Technical Support for a list of the IP addresses to allow.
Link Appliance
Your Barracuda Backup appliance must be linked to your Barracuda Cloud Control Account before you can initiate data backups.
To link your Barracuda Backup appliance:
1. Log in to https://login.barracuda.com using your credentials.

5. Select Replicate data to Barracuda Cloud Storage, select the Storage Amount and Subscription Period if you intend to replicate data to
Barracuda Cloud Storage.
8. The linking process may take a few minutes to complete. Wait until the Dashboard page appears, indicating that the Barracuda Backup
appliance is successfully linked to your account. A green light next to the Barracuda Backup appliance name on the Dashboard page
indicates it is successfully connected.
Add the Server Name and Location
Define Display Groups (Optional)
If you have multiple Barracuda Backup appliances, you can manage them by creating display groups on the Admin > Display Groups page.
See the Display Groups Page for more information.
CONFIGURE DATA SOURCES
This section describes how to configure backups.
Add Systems and Select Data Sources
Set up your data sources on the Backup > Sources page, and specify that you want to Replicate to Barracuda Cloud Storage on the Add
Data Source page. You may have more than one data source on each server, and each can have unique back up characteristics. For set up
details by data source type, see Backup Up Data Sources.
See Data Backup Tasks for more information.
Note that schedules are automatically created (with the default set to back up every day at 8:00PM) when a data source is created exc
ept if a schedule specifying all data sources already exists.
Now that you have configured your computers and data sources, you can create backup schedules, either individually or for all sources. If no
schedule is created for a data source then it will not be backed up.

See the Schedules Page for more information.
including files, data backed up by a Barracuda Backup Agent, and email messages.
subset of the data.
See the Retention Policies Page for more information.
See Creating Effective Retention Policies for revision timelines, removed file rules, and removed email timelines.
Modify Your Backup Rate Limit (Optional)
See the Rate Limit Page for more information.
excluded from backups include temporary files, music, movies and other files which are not essential for business needs in the Backup >
Exclusions page.
See the Exclusions Page for more information.
you want to view.
See the Reports Page for more information.
SECURE THE APPLIANCE
This section describes how to secure your Barracuda Backup appliances.
256-bit encrypted VPN tunnel. The Barracuda Backup appliance uses HTTPS port 1194 to send Status updates to Barracuda Backup. Data
transfers are initiated by the Barracuda Backup appliance rather than by Barracuda Cloud Storage.
Data transferred between your network and Barracuda Cloud Storage is always encrypted. File parts are AES 256-bit symmetrically encrypted
before they are stored, and they remain encrypted until a restore is requested.
Management Access
account information. Go to the Admin > User Activity Reports page to see all activity for an account, including logins and when a user
has enabled or disabled replication.

ge, click the Edit graphic ( ) to edit a user account; enter an IP address or a range.
Secure Network Access – HTTPS is always used for secure web browser communication with Barracuda Backup.
Encryption
Data transfers between the local Barracuda Backup appliance and a remote Barracuda Backup appliance are always encrypted. Data is stored
compressed and encrypted at rest. Barracuda Backup utilizes an aggressive combination of symmetrical and asymmetrical encryption. The
United States government recently approved 192-bit AES encryption as the preferred method for protecting top-secret information. The
Barracuda Backup solution starts with even higher 256-bit AES encryption.
In addition, Barracuda Networks has developed a proprietary advanced digital cataloging system that breaks down your data into small pieces
and tracks the changes of these parts over time, and strips the original meta identifiers from your files.
CONFIGURE REPLICATION
This section describes how to configure replication to Barracuda Cloud Storage.
Globally Replicate Data
You can select to globally replicate all data from all data sources for the currently selected Barracuda Backup appliance to Barracuda Cloud
Storage on the Replication page:
1. Select the Barracuda Backup appliance in the left pane, and then go to the Backup > Replication page.
2. In the Sending Data To section, toggle Send All Local Backups to On:
Selectively Replicate Data
You can specify which data sources are replicated to the cloud for the currently selected Barracuda Backup appliance:
1. Select the Barracuda Backup appliance in the left pane, and then go to the Backup > Replication page.
2. In the Sending Data To section, set Send All Local Backups to Off.
3. Go to the Backup > Sources page, and click Edit next to the data sources listed in the right section of the page.
4. On the Edit page, turn on Replicate to Barracuda Cloud Storage, and then click Save.
Data Sources
You can specify Replicate to Barracuda Cloud Storage when setting up your data sources as described in the section Add
Systems and Select Data Sources.
See the Replication Page for more information.

Cloud-to-Cloud Deployment
Cloud-to-Cloud Deployment Options


Local Control Deployment
The articles in this section refer to Barracuda Backup Legacy Release firmware or newer.
See also: Understanding Local Control
Local Control is not supported for Barracuda Backup Vx.
Enable Local Control to manage your Barracuda Backup Server independently of Barracuda Networks Cloud in a "connectionless" state. You
enable Local Control during the Barracuda Backup appliance linking process. For more information, see the Backup Quick Start Guide included
with the device.
Warning
Once you enable Local Control during the Barracuda Backup linking process, it can only be undone by wiping the unit completely and
relinking the device. For more information, see How to Wipe a Barracuda Backup System.
Before getting started, verify you have a Barracuda Cloud Control Account that you have the necessary equipment.
Initial configuration requires an Internet connection using ports 80/443 TCP and 1194 TCP/UDP to activate your Barracuda Backup
appliance. Once activated through the linking process, the appliance goes into an offline state and an Internet connection is no longer
required.
Use the following steps to enable Local Control to manage the appliance independently of Barracuda Cloud Control:
1. Go to https://login.barracuda.com/, and log in with your credentials.

4. Enter the appliance Location and Time Zone.
5. Turn on Enable Local Control. under Device Management.
Important: Replication is limited to site-to-site.
6. Enter your Billing Information and read and accept the Terms and conditions.
7. The linking process may take a few minutes to complete. Wait until the Dashboard page appears, indicating that the Barracuda Backup
appliance is successfully linked to your account. A green light next to the Barracuda Backup appliance on the Dashboard page indicates
that your Barracuda Backup appliance is successfully connected.
Continue with Barracuda Backup Configuration.

Understanding Local Control

Enable Local Control to manage your Barracuda Backup Server independently of Barracuda Networks Cloud in a "connectionless" state.
Warning
Once you enable Local Control during the Barracuda Backup linking process, it can only be undone by wiping the unit completely and
relinking the device.
Firmware Updates
Before enabling Local Control, to receive firmware update notifications, you must configure an email contact within Barracuda Cloud Control. This
is usually the email account you use when setting up your Barracuda Cloud Control account.
Permissions
To manage a Local Control appliance, a user must have Account Administrator or Operator permissions.
Support
When Local Control is enabled, you can open a support tunnel for remote diagnostics and technical support services over TCP port 22 outbound.
Go to the System > Device Information page, and in the Server Actions section, click Open Support Tunnel:
Options
When Local Control is enabled, you can access the following options through the local web interface:
Backup Schedules
Retention Policies
File and Directory Exclusions
Data Sources
Large Item Reports
Audit Logs
Data Replication to a Second Appliance
Manual Firmware Upgrades
Local User Accounts
Email Notifications
Local Control does not support the following options:
Centralized Administration
Barracuda Cloud Storage
Cloud LiveBoot
Restore to Copy
Offline Notifications
Multi-Factor Authentication
Display Groups
User Synchronization
Advanced Graphs
Backup Summary Reports
Barracuda Backup Vx deployment

Configuring Email Notifications for Local Control

Before enabling Local Control, to receive firmware update notifications, you must configure an email contact within Barracuda Cloud Control.
Upgrade Firmware on a Local Control Appliance

Configure Backup Alerts and Reports in Local Control

Configuring Backup Alerts and Reports in Local Control

To enable email notifications for backup alerts and reports, you must first configure SMTP on the Local Control Barracuda Backup appliance.
Configure SMTP Settings
Configure SMTP settings using the following steps:
1. Log in to your Barracuda Backup appliance using the device IP address.

2. Go to System > Barracuda Backup Appliance Settings.
3. In the SMTP Settings section, select whether to use DNS or to designate a Smart Host.
a. Use DNS – Select Use DNS, and then enter your SMTP domain in the SMTP Domain field:
b. Use Smart Host – Select Use Smart Host, and then enter your SMTP Smart Host Hostname and specify the Port over which
you want to connect:
4. To test your SMTP configuration, enter a valid email address, and click Send Test Email:

Configure Email Notifications
Use the following steps to configure email notifications:
1. Log in to your Barracuda Backup appliance using the device IP address.

2. Go to Admin > Email Notifications.
3. In the Add a recipient section, enter a valid email address in the Email Address field, and specify whether the recipient is to receive
reports, and/or alerts:
a. Send reports – A report for each backup job is sent.
b. Send alerts – Alerts are sent if a backup job has errors or if the Barracuda Backup appliance is offline.
4. Click Save to add the recipient:

How to Add a Replication Target in Local Control

You can replicate data from one or more Local Control appliances to one or more destinations using the
following steps:
1. Log in to Local Control, go to the Backup > Replication page, and click Add a Target:
2. Add Replication Target displays. Enter the Replication Target Information:

a. Destination IP Address – Enter the IP address or hostname of the destination.
b. Serial Number– Enter the destination serial number.
c. Replication Code – Enter the destination replication code found on the Backup > Replication page in the web interface.
3. Click Save. The target displays in the Sending Data To section:
The Status field displays as Online within 5-10 minutes once connection is established. Refresh the page to update the Statu
s.

Barracuda Cloud Storage Deployment
You can deploy a Barracuda Backup appliance with backups stored on Barracuda Cloud Storage. In the following image, a Barracuda Backup ap
pliance is located in a network and its backups are stored in Barracuda Cloud Storage:
Storage Plans
Barracuda Cloud Storage is available through either a subscription plan or by purchasing Unlimited Cloud Storage. You can enable offsite
vaulting which leverages Barracuda's Cloud Storage service to offload up to 12 monthly and 7 yearly revisions to strictly cloud storage, freeing up
disk space on your local Barracuda Backup Server.
No Transfer Fees
There are no data transfer fees, for example, PUTS, GETS, UPLOAD, DOWNLOAD, with Barracuda Cloud Storage for both the Cloud
Storage Subscription and Unlimited Cloud Storage.
Cloud Storage subscription – Barracuda Cloud Storage subscription plans provide diverse offsite storage options that scale to meet
your changing data requirements. Storage plans are purchased in 200 GB increments and are all disk-based, allowing you to scale up or
down depending on your organization's needs.
Unlimited Cloud Storage – Unlimited Cloud Storage allows you to store all of your content without having to manage storage usage
limits.
Unlimited Cloud Storage is limited by the maximum capacity of the appliance. Replication from box-to-cloud and box-to-box is
simply a mirror of the data backed up on the source, with the exception of offsite vaulting. If offsite vaulting is configured, it is
possible for more data to be stored in the cloud or on another appliance configured as a replication target. Keep in mind that
data replicated to Barracuda Cloud Storage or to a secondary appliance is stored in a compressed state so the actual usage is
less than what is stored on the source appliance.
Unlimited Cloud Storage mirrors content offsite based on your retention policies. As noted above, you can enable offsite vaulting to purge data
from the local cache.
Contact your Barracuda Sales Representative for subscription plan and Unlimited Cloud Storage pricing.

Virtual Deployment
Do not use snapshots on the Barracuda Backup Vx appliance. Even if data is not being replicated to the Barracuda Cloud,
configuration data is still sent to Barracuda so that the unit can be managed. Reverting to a previous state using snapshots can
potentially cause loss of data and unit corruption. Independent disks (persistent mode) are the default selection and highly
recommended to avoid snapshots.
Requirement
This virtual appliance requires a 64-bit capable host.
The Barracuda Backup Vx enables you to build a highly secure and scalable application infrastructure, and can be deployed in supported
VMware vSphere and Microsoft Hyper-V environments.
Choosing the Right Platform
Before deploying Barracuda Backup Vx in a virtual environment, consider the following factors:
Barracuda Backup utilizes memory (RAM) for database queries during backup, restore, and offsite replication. For this reason,
Barracuda highly recommends following the recommended minimum resources for memory as described below.
Barracuda uses CPU resources for hashing blocks during deduplication, compression for offsite replication, and data
rehydration during restoration. It is imperative that the recommended number of cores is allocated for the virtual appliance as
described below.
At minimum, memory resources must be dedicated (reserved). It is also recommended that the CPU be dedicated to
Barracuda Backup Vx and not shared with other virtual machines on the host. This aligns with VMware and Microsoft’s
recommendations for virtualized Microsoft Exchange Server and SQL Server implementations.
A separate data store is recommend for use with the virtual appliance due to disk I/O constraints or an entirely separate
storage server/environment altogether from the production environment.
Other system components such as network and storage must be sized accordingly to prevent them from becoming a
bottleneck.
It is important that snapshots are not used on the Barracuda Backup Vx. Even if data is not replicated to the Barracuda Cloud,
configuration data is still sent to Barracuda so that the appliance can be managed. Reverting to a previous state using
snapshots can potentially cause loss of data and appliance corruption. Independent disks (persistent mode) are the default
selection and highly recommended to avoid snapshots.
If the above considerations are acceptable and supported by your environment, then it is likely that virtualizing Barracuda Backup is a
good fit for the organization.
Storage System Requirements
Any storage infrastructure consisting of Local/Direct-Attached, SAN, and NAS;

Storage with inadequate throughput, read, and write speeds will suffer;
Servers with software RAID, slow NAS, and low-RPM drives will yield poor performance
Table 1. VMware and Hyper-V System Requirements.
Image Type Supported Hypervisors
OVF VMware ESX and ESXi (vSphere Hypervisor) versions 4.x, 5.x, and
6.x
VHD Microsoft Hyper-V 2008, 2008 R2, 2012, 2012 R2, and 2016
Before deploying the Barracuda Backup Vx, verify your host has sufficient resources. If minimum required resources are not available, the
Barracuda Backup Vx may be negatively impacted or the deployment may fail entirely. Size for capacity and performance. Tasks such as backup,
offsite replication, data restoration, and purging can use a significant amount of system resources. When considering Barracuda Backup Vx
deployment, take into account the use cases in addition to needed storage.
Table 2. vCPU Recommendations.
Backup Volume Minimum Recommended vCPUs High Performance Recommended vCPUs
0-2 TB 1 vCPU 2 vCPUs

2-6 TB 2 vCPUs 4 vCPUs
32-100 TB 16 vCPUs 32+ vCPUs
Table 3. RAM Recommendations.
Backup Volume Minimum Recommended RAM High Performance Recommended RAM
0-1TB 2 GB 4 GB
1-4 TB 4 GB 8 GB
4-12 TB 8 GB 16 GB
12-16 TB 16 GB 32 GB
16-24 TB 32 GB 64 GB
24-48 TB 64 GB 128 GB
48-100 TB 128 GB 256+GB
Next Step
Deploy Barracuda Backup Vx.
See Also
Barracuda Backup Vx Replication Options

How to Migrate a Barracuda Backup Vx to New Storage

Understanding Barracuda Backup Vx

The Barracuda Backup Vx is a pre-configured, software-based virtual appliance that provides comparable functionality to the Barracuda Backup
physical appliance:
The Barracuda Backup Vx allows customers to deploy the Barracuda Backup product on their own infrastructure using their own storage;
The Barracuda Backup Vx is licensed per CPU socket or physical server as an annual subscription with no upfront hardware costs;
The Barracuda Vx helps fully virtualized customers more effectively use and deploy Barracuda Backup to protect their virtual
environment without deploying a physical appliance.
Functionality Differences
While the software and general functionality is the same between the physical and virtual appliances, there are some important differences
between the two deployment models:
Barracuda Backup Vx protects all of the same environments as the physical Barracuda Backup appliance including virtual and physical
servers, however, Barracuda Backup Vx can only be deployed on VMware ESXi and Microsoft Hyper-V.
Barracuda Backup Vx is deployed on customer infrastructure; the customer must provide a hypervisor (VMware or Hyper-V), the
computer environment, and storage.
Barracuda Backup Vx is licensed by the number of physical CPU sockets for virtual hosts that need protection or by the number of
physical machines.
Barracuda Backup Vx is an annual subscription. Unlike the physical appliance, customers do not need to pay for the appliance plus
annual subscriptions. With Barracuda Backup Vx, they only pay the subscription price.
For offsite replication and disaster recovery, Barracuda recommends customers replicate to Barracuda Cloud Storage. A metered cloud
storage subscription plan is available for the Barracuda Backup Vx. Note that the metered cloud pricing is only for the Barracuda Backup
Vx, it cannot be applied to a physical Barracuda Backup appliance.
Each Backup Vx includes a second license for a Receiver Vx for basic replication. The Receiver Vx can only be used for receiving and
storing data replicated from the Backup Vx and cannot be used to backup data.
Customers may also elect to replicate data to a physical Barracuda Backup appliance.
Barracuda Backup Vx can scale up to a larger capacity at any time simply by expanding the virtual disk size; no data migration is
necessary.
Determine if the Barracuda Backup Vx Suits Your Environment
Barracuda Backup Vx protects all of the same environments as the physical Barracuda Backup appliances including both virtual and physical.
To determine if Barracuda Backup Vx suits your environment, consider the questions in Table 1.
Table 1. Determine if Barracuda Backup Vx Suits Your Environment.
Are you using either VMware or Hyper-V for your virtual Barracuda Backup Vx can be deployed to both VMware and Hyper-V,
environment? but cannot be deployed to Citrix XenServer or Red Hat KVM.
Do you have either a dedicated virtual host or enough leftover Refer to the Backup Vx System Requirements for exact
resources (CPU, RAM) to add a virtual appliance to your current specifications.
virtual infrastructure?
Do you have enough storage attached to your virtual environment to Refer to the Backup Vx System Requirements for exact
back up your current data set? specifications.
How much data do you need to back up? A single Barracuda Backup Vx is best suited to backup up to 20 TB.
For data sets over this size, involve a Barracuda Sales Engineer.
If you meet these requirements, then you are most likely a good candidate for the Barracuda Backup Vx. If you do not have enough computer
resources or storage, then a physical Barracuda Backup appliance is most likely the best option.
Licensing
Barracuda Backup Vx is licensed per socket for virtual and per server for physical, and is based on what it is protecting, not what it is running
on:
Per Socket – Total number of physical CPU sockets on the physical hypervisor hosts on which the virtual servers are running
Per Server – Total number of physical servers (no additional charge per-application)
Socket-based pricing is licensing based on the number of physical CPU sockets in a server or virtual machine (VM) host that is being backed up.
A CPU socket is a physical connector and chip located on a computer’s motherboard. A CPU core is a logical representation of a CPU.
Socket-based licensing refers to the number of physical CPUs.
With current VM environments, both the number of VMs and the amount of storage used are highly variable, whereas the physical host tends to
stay the same for a relatively long period of time. Customers can license the backup software based on the more stable/predictable physical
characteristics of the host. Additionally, both VMware vSphere and Microsoft Windows Server license based on CPU sockets, so administrators

are already familiar with the process and are more aware of what processing resources they have in their virtual environment.
The Barracuda Backup Vx is now licensed based on CPU sockets to better match customer purchasing behavior, and better compete with other
backup solutions in the market.
To protect non-virtual servers with Barracuda Backup Vx, you can license the product based on the number of physical machines that need
protection. For physical devices, one device equals the same price as one CPU socket. This also includes NAS devices.
To determine the best way to license the Barracuda Backup Vx, gather the following information:
What are the total number of physical CPU sockets for the virtual hosts you plan to protect with the Barracuda Backup Vx?
How many physical servers do you plan to protect with the Barracuda Backup Vx?
Do you have any NAS devices that you plan to protect with the Barracuda Backup Vx? If so, how many? Note that a NAS device is
equivalent to one physical server.
Example 1. Single Virtual Host.
In this example, you want to back up the following in your environment:
One virtual host (hypervisor) containing two physical CPU sockets

Three physical servers
You need a total of five licenses:
Determine the Number of Sockets
The number of CPU sockets for each host is tracked in VMware vSphere and by each Microsoft Hyper-V host.
For VMware, open the vSphere Client, click the vCenter server, and click the Hosts tab:
For Hyper-V, go into each host and look for the number of physical processors in either Task Manager or Device Manager. A third-party
tool may also contain hardware information for each host.
Replication

You can replicate data to multiple locations using a Barracuda Backup Vx. For example, if you want a copy of your data at a secondary location
within your organization and another copy of the same data within Barracuda Cloud Storage, then replication and bandwidth rate limits are
configured for both locations.
Table 2 lists the Barracuda Backup Vx supported replication options.
Table 2. Barracuda Backup Vx Replication Options.
Replication Target Direction Type Licensing
Barracuda Cloud Storage One way Site-to-cloud $799 per TB per year
Receiver Vx (1) One way Site-to-site Included
Backup Vx (2) Bi-directional Site-to-site (3) Included
Backup Appliance (3) Bi-directional Site-to-Site (3) Included
Notes:
(1)The Barracuda Backup Receiver Vx is included at no additional cost with the Barracuda Backup Vx as a dedicated virtual replication target.
The Barracuda Backup Receiver Vx does not support local backups and can only receive data from one sender.
(2) Twoor more virtual appliances that are backing up data are capable of bi-directional replication amongst each other, similar to a site-to-site
deployment among physical Barracuda Backup appliances.
(3) For site-to-site replication instead of cloud storage, Barracuda provides a free Receiver Vx for offsite storage with limited functionality.
(4) Replication from physical Barracuda Backup appliances to the Barracuda Backup Vx is limited to 1:1 replication.
A separate subscription is available to enable replication from a physical appliance to a dedicated Barracuda Backup Receiver Vx is available.
Replication from physical appliances to a dedicated Barracuda Backup Receiver Vx is limited to models 190-690 for one-to-one replication. You
cannot replicate multiple physical appliances to a Barracuda Backup Receiver Vx.
For MSPs, Barracuda's strategy is to build the best cloud infrastructure. Additionally, if an MSP wants to replicate customer data to a single, very
large Barracuda Backup Vx and host their own cloud, then:
Data replication to a Receiver Vx is limited to 1:1

Site-to-site replication is not as good as replication to Barracuda Cloud Storage
Additional notes:
A Barracuda Backup Receiver Vx cannot back up data, only a licensed Barracuda Backup Vx can back up data. The Barracuda Backup
Receiver Vx can only receive data from a single, licensed Barracuda Backup Vx or from a single physical appliance (models 190-690)
with a Virtual Receiver subscription.
The Unlimited Cloud Storage plan is not available with the Barracuda Backup Vx
Replication among Barracuda Backup Vx appliances is limited to 1:1
LiveBoot with Receiver Vx
You can perform a direct restore from a Barracuda Backup Receiver Vx to a restoration target. Additionally, you can LiveBoot VMware machines
from the Barracuda Backup Receiver Vx to a local VMware environment.
Deployment
To deploy the Barracuda Backup Vx,
1. Download the Vx image from Barracuda, and import the image into your VMware or Hyper-V virtual environment.
2. Once imported, go to the Barracuda online evaluation request form to obtain an evaluation license and verify the evaluation instance can
be converted to a fully licensed Vx at the time of purchase.
3. Once complete, configure the amount of disk space, memory, CPU, and network interfaces you want to use.
For more information, see the following:
Barracuda Backup Virtual Deployment

Barracuda Backup Virtual Appliance White Paper
Barracuda Virtual Deployment Options
Once the Barracuda Backup Vx is provisioned, you can link to Barracuda Cloud Control and configure backups in the same manner as the
physical appliance. Note that you use the same image (OVD or VHD) to provision both the Barracuda Backup Vx and (optional) Receiver Vx. To
download the image:
Barracuda Downloads

Link the Barracuda Backup Vx and Receiver Vx
Barracuda provides you with the serial number, linking code, and license token for the Barracuda Backup Vx. See Barracuda Backup Virtual
Deployment for more information.
Note that the Barracuda Backup Receiver Vx must be provisioned and linked after the Barracuda Backup Vx as the Receiver Vx
inherits its subscription status from the Barracuda Backup Vx. See How to Set Up a Barracuda Receiver Vx for more information.
Upgrade Storage
Upgrade storage on your Barracuda Backup Vx by expanding the virtual disk the Vx is using to store data. For details, see the Barracuda Backup
Virtual Appliance White Paper.
Migrate from a Physical Appliance
The migration process is identical to migrating between different physical models. For details, see:
Site-to-Site and Site-to-Vx Migration Process

Migrate to New Storage
For details, see How to Migrate a Barracuda Backup Vx to New Storage.

Deploy Barracuda Backup Vx
potentially cause loss of data and unit corruption. Independent disks are the default selection and highly recommended to avoid
snapshots.
Size for both capacity and performance based on your use case and environment. Tasks such as backup, offsite replication, data
restoration, and purging can use a significant amount of system resources.
Verify your host has sufficient resources.
Table 1. vCPU Recommendations.
Backup Volume Minimum Recommended vCPUs High Performance Recommended vCPUs
0-2 TB 1 vCPU 2 vCPUs
32-100 TB 16 vCPUs 32+ vCPUs
Table 2. RAM Recommendations.
Backup Volume Minimum Recommended RAM High Performance Recommended RAM
0-1TB 2 GB 4 GB
1-4 TB 4 GB 8 GB
4-12 TB 8 GB 16 GB
12-16 TB 16 GB 32 GB
16-24 TB 32 GB 64 GB
24-48 TB 64 GB 128 GB
48-100 TB 128 GB 256+GB
Storage System Requirements
Any storage infrastructure consisting of Local/Direct-Attached, SAN, and NAS;

Storage with inadequate throughput, read, and write speeds will suffer;
Servers with software RAID, slow NAS, and low-RPM drives will yield poor performance
Step 1. Deploy Vx Images
Barracuda offers the following types of images for the Barracuda Backup Vx deployment. Follow the instructions for your hypervisor to deploy the
Barracuda Backup Vx appliance.
Image Type Supported Hypervisors
OVF VMware ESX and ESXi (vSphere Hypervisor) versions 4.x, 5.x, and
6.x
VHD Microsoft Hyper-V 2008, 2008 R2, 2012, 2012 R2, and 2016
VMware vSphere Deployment

Click here to deploy the OVF template...
1.

1. Go to https://barracuda.com, and select Backup from the Products drop-down menu.

2. Click Models/Editions, and select Virtual from the Deployment options drop-down menu.
3. Click Free Eval Unit or Purchase, fill out the form, and submit your request.
4. An email is sent to the specified email address.
5. Follow the instructions in the email to download and extract the Barracuda Backup Vx .zip archive to a location accessible from a
machine running vSphere.
Make note of your license token for use during configuration and activation.
6. Launch vSphere Client, and from the File menu, click Deploy OVF Template:
7. The vSphere Client launches the Deploy OVF Template wizard.

8. Click Browse, navigate to the extracted folder, and locate the Barracuda Backup Vx .ovf file (for example,
BarracudaBackupService-vm4.2.4-fw6.2.00.10159-20150807-5x.ovf):
9. Click Next. In the wizard, complete the following:

Review appliance information and the ESX version
Name the appliance and define a location where the virtual machine is to be created
Select the datastore where the VMDK file is to be stored; a dedicated disk store is recommended
Select the disk format as Thick Provisioned Lazy Zeroed
Virtual drives must be thick provisioned; thin provisioned discs will cause unexpected behavior and the virtual
device will not operate properly.
10. Review your settings, and click Finish to deploy the appliance.
11. After deployment is complete, locate the appliance within the appropriate data center, host, or resource pool.
Allocate Space
1. With the Barracuda virtual appliance powered off, right-click the appliance, and click Edit Settings.
2. Edit the CPU, Memory, and Hard disk 1 Provisioned Size settings based on the recommendations in Tables 1 and 2 above.
Barracuda recommends using the default options Thick Provision Lazy Zeroed for the disk provisioning, and Independe
nt (Persistent) as the mode to achieve the best performance from your virtual appliance and to prevent snapshots from
occurring.

3. Click OK. Once the hardware settings are defined, power on the virtual appliance. The appliance is prepared for use; this may take
several minutes.
4. Using your keyboard arrows, select Yes to format and partition the additional disk space provisioned above in Step 2:
5. The Barracuda Backup Vx expands and formats its partition space. Once formatting is complete, the appliance reboots:

Microsoft Hyper-V Deployment

Click here to import virtual machine...
1. Go to https://barracuda.com, and select Backup from the Products drop-down menu.
2. Click Models/Editions, and select Virtual from the Deployment options drop-down menu.
3. Click Free Eval Unit or Purchase, fill out the form, and submit your request.
4. An email is sent to the specified email address.
5. Follow the instructions in the email to download and expand the Barracuda Backup Vx .zip archive to a location accessible from a
machine running Hyper-V.
6. Navigate to and expand the Barracuda Backup Vx .zip folder.
7. Launch the WinServerSetup.bat file located in the extracted folder. This batch file corrects a compatibility issue and takes less than
a minute to run.
Make note of your license token for use during configuration and activation.
8. In Hyper-V Manager, right-click the VM host, select Import Virtual Machine, and click Next.
9. Navigate to and select the HyperV folder from the extracted .zip archive, click Select Folder:
10. Click Next. On the Select Virtual Machine page, click on the virtual machine to import:

10.
11. Click Next. Select Copy the virtual machine (created a new unique ID):
12. Click Next. Select whether to use the default location for configuration files, storage, and network settings for the VHD, or define
custom settings. Click Next.
13. On the Summary page, verify that all the settings are correct:

14. Click Finish.

15. Right-click the Barracuda Backup Vx, and click Settings. Define the Memory and Processor settings based on the
recommendations in Tables 1 and 2 above:
a. Click Hard Drive under Virtual hard disk, and click Edit:
b. Click Next. Select the Expand action:

c. Click Next. Specify the virtual hard disk size:
d. Click Next, and click Finish.

e. In the VM Settings window, click Apply:

16. Click OK to finish editing the VM.

17. Power on the virtual appliance. The appliance is prepared for use; this may take several minutes.
18. Using your keyboard arrows, select Yes to format and partition the additional disk space provisioned above in Step 9:
19. The Barracuda Backup Vx expands and formats its partition space. Once formatting is complete, the appliance reboots:

To take advantage of Microsoft's VHDX support on Hyper-V 2012, 2012 R2, and 10, follow the instructions in How to Convert and
Replace a Barracuda Virtual Appliance VHD File with a VHDX Format File.
Step 2. Configure Your Firewall
If your Barracuda Backup Vx is located behind a firewall, open the following ports:
Port Direction Protocol Description
80 Out TCP/UDP Health monitoring
443 Out TCP/UDP Health monitoring
1194 Out TCP/UDP Configuration/management
5120 Out TCP/UDP Barracuda Backup Agent
5121-5129 Out TCP/UDP Offsite replication
Step 3. Start Your Virtual Appliance, Configure Network, and Enter License
If you did not recieve your Barracuda Vx license token via email or from the website when you downloaded the Barracuda Backup Vx package,
request an evaluation on the Barracuda website at https://www.barracuda.com/purchase/evaluation or purchase one from https://www.barracuda.
com/purchase/index. The license token looks similar to the following: 01234-56789-ACEFG.
In your hypervisor client, start the virtual appliance and allow it to boot up, then complete these steps:
1. From the console, log in as admin with the password admin.
2. Use your keyboard arrows to select TCP/IP Configuration, enter your network settings, and then select Save:
3. Use your keyboard arrows to select Licensing, enter your Barracuda license token, and then select Save:

4. Type YES, and press Enter to apply the license and provision the virtual machine (VM):
5. Wait for the provisioning to complete; this may take several minutes.
6. Once the license is installed, press Enter to reboot the VM.
7. Once rebooted, verify both Local and Internet values are Up; Cloud changes to Up once the appliance is linked in the next step:
Step 4. Link the Appliance
1. Log in to https://login.barracudanetworks.com. If you do not have an account, click Create a User, follow the account creation
instructions, and log in.
2. Follow the online instructions to link your appliance.
Step 5. Configure Network Settings

By default, the Barracuda Backup appliance is configured to obtain an IP address on your network using DHCP. If you want to assign it a
static IP address instead, you can configure it using the console administration interface. If not, proceed to the section Configure Your
Corporate Firewall:

2. Use your Arrow keys to highlight the TCP/IP Configuration field.
3. Press Enter to access the right pane.
Do not select Use DHCP in the right pane before saving. Doing so fetches and immediately applies the network settings
via DHCP.
4. Use the Arrow keys to select and enter the IP Address, and then press Enter to move to the next option.
5. Enter the remaining settings as appropriate for your network.
6. Use the Arrow keys to navigate to Save, and press Enter.
In the Network Status section, Local and Internet should display as Up while Cloud displays as DOWN until the appliance is linked to an
account later in the installation process.
For additional information, refer to the article Barracuda Console.
Verify Connection to Barracuda Networks

Once you log in to the web interface, the Barracuda Backup appliance you have just installed, powered on, and linked, should be listed in the
left pane with a green status light to the right of its name. If the status for your Barracuda Backup appliance is green, continue to the next
step. Otherwise, verify network settings and appliance connectivity, or contact Barracuda Networks Technical Support for additional direction.
Enter Server Name and Location
In the System > Barracuda Backup Appliance Settings page, enter a name for your Barracuda Backup appliance, the associated time
zone, and server location.
Define Display Groups
If you have multiple Barracuda Backup appliances, you can manage them through display groups:
1. Log in to Barracuda Backup, and go to the Admin > Display Groups page.
2. All display groups active on your account display in the Current Display Groups section.
3. To add a new display group, enter a name for the group of devices, and then click Add. For example, if you want to group all
Barracuda Backup Servers by location, you might create groups by geographic location: Engineering - Asia, Engineering - US,
Engineering - Europe.
4. The display group name appears in the Current Display Groups section.
5. To remove a display group, click Remove to the right of the group name you wish to remove; click OK to remove the group.
If you delete a display group that contains devices, those devices are moved to the default group.
Add a Barracuda Backup Appliance to a Group
Once you create display groups, you can add a Barracuda Backup appliance to the group using the following steps:
1. In the left pane, select the desired Barracuda Backup, and go to the System > Barracuda Backup Appliance Settings page.
2. In the Backup Appliance Display Group section, select the desired display group name from the Current Display Group drop-do
wn menu.
3. To add or remove display groups, click Manage your display groups; the Admin > Display Groups page displays.
4. Click Save.
Next steps:
VMware Backup

How to Expand Barracuda Backup Vx Capacity
snapshots.
Expand Barracuda Backup Vx Capacity for VMware
1. With the Barracuda virtual appliance powered off, right-click the appliance, and click Edit Settings.
2. In the Hardware tab, click Hard disk 1.
3. Change the Provisioned Size to the desired capacity:
Virtual drives must be thick provisioned; thin provisioned discs will cause unexpected behavior and the virtual device will not
operate properly.
4. Increase the amount of Memory or the number of CPUs to match the new disk capacity; refer to the Virtual Deployment Guide for
minimum recommendations.
5. Click OK to configure the VM.
6. Power on the VM. The additional disk space is detected; select Yes to format and use it:
7.

7. The additional disk space is formatted and the disk resized; this may take several minutes.
8. Once formatting and resizing is complete, the appliance reboots:
Expand Barracuda Backup Vx Capacity for Hyper-V
1. With the Barracuda virtual appliance powered off, right-click the appliance, and click Settings.
2. In the Hardware section, click Hard Drive.
3. Under Virtual hard disk, click Edit:
4. Click Next. Choose Expand as the action:

5. Click Next. Specify the new disk size:
6. Click Next, and click Finish.

7. Increase the amount of Memory or the number of CPUs to match the new disk capacity; refer to the Virtual Deployment Guide for
minimum recommendations.
8. Click OK to reconfigure the VM.
9. Power on the VM. The additional disk space is detected; select Yes to format and use it.
10. The additional disk space is formatted and the disk resized; this may take several minutes.
11. Once formatting and resizing is complete, the appliance reboots:

11.

Barracuda Backup Vx Replication Options
snapshots.
The Barracuda Backup Vx appliance can replicate data to Barracuda Cloud Storage for offsite disaster recovery or site-to-site for basic software
replication to a virtual or physical Barracuda Backup appliance.
Table 1. Barracuda Backup Vx Replication Options.
Barracuda Backup Vx can replicate to one or more destinations.
Replication Target Direction Type
Barracuda Cloud Storage One way Site-to-cloud
Barracuda Backup Appliance One way Site-to-site
Barracuda Backup Vx Bidirectional Site-to-site
Barracuda Receiver Vx One way Site-to-site
Barracuda Cloud Storage
No additional configuration is necessary to set up Barracuda Cloud Storage. Each Barracuda Backup Vx is preconfigured with Barracuda Cloud
Storage as a target within Backup > Replication and is enabled by default for users who have either purchased or are evaluating the service:
Data replicated to Barracuda Cloud is stored encrypted on geographic and locally redundant storage with billing applied against the amount of
storage hosted offsite, after deduplication and compression. Leverage Barracuda's scalable cloud architecture to avoid the complexity and risk of
allocating and managing offsite storage sites. Contact your Barracuda partner or Barracuda sales representative for more information.
Barracuda Backup Appliance
You can configure the Barracuda Backup Vx appliance to replicate one-way to a Barracuda Backup appliance, model 490 and above, for
site-to-site replication.
Use this option in multi-site environments with mixed physical and virtual Barracuda Backup appliances or in an environment with a physical
Barracuda Backup appliance and two or more locations. Ensure that the Barracuda Backup appliances have suitable storage and are sized
appropriately to host data being replicated to it as well as the data locally backed up to the appliance.
Barracuda Backup Vx
You can configure the Barracuda Backup Vx appliance to replicate bidirectionally to another Barracuda Backup Vx or to a Barracuda Backup
appliance.
Use this option in environments where two or more sites host primary backed up data, and where site-to-site replication is preferred. This is the
recommended method for site-to-site replication for the Barracuda Backup Vx as the virtual appliance storage can be scaled to meet storage
demands over time.
Each Barracuda Backup Vx can be set up as a replication target for one-to-one replication between virtual appliances or to a physical device as a
replication pair. Note that many-to-one replication is not available with the Barracuda Backup Vx appliance.
For optimum performance, ensure that the appliance at each location is set up with the minimum system requirements. See Configuring a

Replication Destination for details on setting up a site-to-site replication target.
Barracuda Receiver Vx
The Barracuda Receiver Vx is included with the Barracuda Backup Vx subscription for basic software replication and can be set up as a
replication target and can perform restores. With a Receiver Vx subscription, you can pair a physical appliance and a Barracuda Receiver Vx,
one-to-one. Replication from physical appliances to a Receiver Vx is limited to Barracuda Backup models 190 through 690.
Use this option in environments where an offsite location can host the virtual appliance as a storage target but does not have primary data to
back up, or in environments where you want to replicate the Barracuda Backup Vx within the same site. You can use the Barracuda Receiver Vx
in conjunction with Barracuda Cloud Storage for two offsite copies. The Barracuda Receiver Vx has the same benefits as the Barracuda Backup
Vx. You can add the Barracuda Receiver Vx to a physical appliance.
See How to Set Up the Barracuda Receiver Vx for additional information.

How to Set Up a Barracuda Receiver Vx

Barracuda Backup Vx includes one-way basic software replication to a Barracuda Receiver Vx. A single Barracuda Receiver Vx
license is included with each Barracuda Backup Vx subscription for one-way replication.
Also see: Barracuda Backup Vx Replication Options.
You can use the Barracuda Receiver Vx as a replication target and for restores. With a Receiver Vx subscription, you can pair a physical
appliance and a Barracuda Receiver Vx, one-to-one. Replication from physical appliances to a Receiver Vx is limited to Barracuda Backup
models 190 through 690. Additionally, it can be used for site-to-site replication or in conjunction with Barracuda Cloud Storage for multiple offsite
copies.
To generate a license, link to your account, and provision the Barracuda Receiver Vx:
1. Log in to Barracuda Backup, go to the Backup > Replication page, and click Add Target.
Once you click Activate, the Barracuda Receiver Vx license token for provisioning your virtual machine is generated, and then
activates and links the system to your Barracuda Cloud Control account.
2. In the Site-to-Site Replication section, click Activate:
3. The confirmation dialog box displays:
4. Click Proceed to activate and link the Barracuda Receiver Vx to your account. The license token displays on-screen.
5. Use the license token to provision your Barracuda Receiver Vx using the same virtual image used to deploy the Barracuda Backup Vx:
6. After provisioning the Barracuda Receiver Vx and booting the system, configure replication settings on the Backup > Replication > Add
Target page using the destination IP address, serial number, and replication code. This information is located on the Barracuda Receiver
Vx Replication page:
7. The Barracuda Backup Vx is now ready to replicate data.

How to Migrate a Barracuda Backup Vx to New Storage

This article refers to Barracuda Backup version 6.3 and higher, and VMware vSphere 4.1 or higher, and vmWare VMotion.
Step 1. Shut Down the Barracuda Backup Vx
Select the manner in which to shut down the server.
Local User Interface
1. Log in to the local user interface, and click System > Device Information.
2. Scroll down to Server Actions, and click Shut Down:
Local Console
1. Log in to the local console.

2. Arrow down to System, and press Enter.
3. Arrow down to Shutdown, and press Enter.
4. When prompted, type: YES
Step 2. Migrate the Barracuda Backup Vx to New Location
Select the manner in which to migrate the VM.
Migrate via Storage vMotion
1. Log in to VMware via vSphere or the web client, and locate the Barracuda Backup virtual machine (VM).
2. Right-click the VM, and click Migrate:

3. In the Select Migration Type page, select Change datastore or Change both host and datastore:
4. Click Next. In the Storage page, select storage/datastore:
5. Click Next. Verify the configuration, and click Finish.

6. The Status indicator displays the relocation progress:
7. Allow the relocation to complete.
Manually Migrate the VM
1.

1. Log in to VMware via vSphere or the web client, and locate the Barracuda Backup VM.
Verify the datastore where the VM is located.
2. Right-click the VM, and click Remove from inventory:
3. Click on the host. Click the Configuration tab, and click Storage:
4. Right-click the Datastore, click Browse datastore.

5. Right-click the VM folder, and click Move to:

6. Select the datastore where you want to move the VM folder, and click Move.
7. Right-click the new datastore, click Browse Datastore, and open the VM folder:
8. Right-click the .vmx file in the VM folder, click Add to Inventory, and select a host:

9. Click Next, and then click Finish.
The VM is now ready to restart.

Public Cloud Hosting
In this Section
Amazon Web Services

Amazon Web Services
Amazon Web Services

How to Configure the Amazon Web Services Import Service Role
How to Restore VMware and Hyper-V Backups to Amazon Web Services


The Barracuda Backup on Amazon Web Services (AWS) is a complete and affordable data replication solution designed for optimizing data
replication in the AWS public cloud service. AWS replication provides easy access to your data and supports archival compliance requirements.
To replicate data to AWS, you must have an AWS Replication subscription and an AWS account.
To learn more or purchase an AWS Replication subscription, contact Barracuda at sales@barracuda.com.
In this Section


This article refers to the Barracuda Backup firmware version 6.4 or newer, VMware and the vSphere Data Recovery API, supported
versions of Microsoft Hyper-V, and Amazon Web Services (AWS).
Use the steps in this article to set up Amazon Web Services (AWS) replication.
Replication and Restore to AWS require a Barracuda Backup AWS Replication subscription.
Step 1. Download the CloudFormation Template
1. Log in to your Barracuda Backup appliance, and go to the Admin > AWS Credentials page.
2. Under STEP 1 of the Add AWS Account wizard, click Download to save the Barracuda CloudFormation template to your local system:
Watch the Step 1 Download the CloudFormation Template video:
Step 2. Upload Template to Amazon Web Services
1. Log in to AWS services using your account credentials.

2. Click Services, and navigate to and select CloudFormation.
3. Click Create Stack. In the Choose a template section, click Upload a template to Amazon S3:
4.

4. Click Choose File, and navigate to and select the CloudFormation template saved to your local system in Step 1. Click Next.
5. On the Specify Details page, enter a name to represent the AWS resources in the Stack name field. Click Next.
6. On the Options page, click Next.
7. On the Review page, select I acknowledge that AWS CloudFormation might create IAMresources, and then click Create to create
an IAM role in your AWS account.
8. Once the stack is created, it displays in the table with a status of CREATE_COMPLETE:
Watch the Step 2 Upload Template to Amazon Web Services video:
Step 3. Configure an Amazon Web Services Import Service Role
Before you can restore VMware and Hyper-V virtual machine (VM) backups to AWS, you must first create a service role named vmimport.
This step is only necessary if you plan to restore VMware or Hyper-V machines to an AWS Amazon Machine Image (AMI).
Amazon Elastic Compute Cloud (EC2) and Amazon Simple Storage Service (S3) instances are typically separate. AWS requires a role
to allow EC2 to access your S3 storage. AWS uses the vmimport service role to provide permissions between EC2 and S3. This step
assumes you have not set up the vmimport service role. If you previously set up the vmimport role, you must grant Barracuda Networks
access to replicate Barracuda Backup data to AWS.
To create the service role:
1. Click the following hyperlink: https://console.aws.amazon.com/cloudformation/home?#/stacks/new?stackName=barracuda-vmimport-sta

ck&templateURL=https://s3.us-east-2.amazonaws.com/barracuda-templates/vmimport.template
2. On the Select Template page, verify that Specify an Amazon S3 template URL is selected and that the URL in the text box matches
the URL in the following images:

3. On the Select Template page, click Next.

4. On the Specify Details page, click Next.
6. On the Review page, select I acknowledge that AWS CloudFormation might create IAM resources with custom names, and then
click Create to create the vmimport role in your AWS account:

Watch the Step 3 Create a Service Role in Amazon Web Services video:
Step 4. Add AWS Credentials
1. After creating the two AWS CloudFormation stacks in Steps 2 and 3 above, select the newly created IAM role created in Step 2:
2. Click the Resources tab below the table and click the link in the Physical ID field:
3. On the Summary page, copy the Role ARN to your clipboard:
4. Return to the Admin > AWS Credentials page in the Barracuda Backup web interface.
5. Click STEP 3 in the Add AWS Account wizard:

6. Enter an Account Name and paste the Role ARN that was copied from step 4 into the IAM Role (ARN) field.
The Account Name can be anything; this name is used in Barracuda Backup to easily identify your AWS IAM Role (ARN).
7. Click Verify, and click Add if the verification was successful:
If verification fails, verify that you pasted the complete Role ARN into the IAM Role (ARN) field and that all steps above were
completed properly. If verification continues to fail, contact Barracuda Networks Technical Support.
8. The AWS Account should now be successfully added to Barracuda Backup:
Watch the Step 4 Add AWS Credentials video:

To complete replication to AWS, go to How to Configure Amazon Web Services as a Replication Target.

You must complete the steps in How to Set Up Amazon Web Services before you can replicate data to Amazon Web Services
(AWS).
How to Replicate Data to Amazon Web Services Video
Important
Use the following steps to set up replication to AWS:
1. Log in to your Barracuda Backup appliance, and go to the Backup > Replication page.
2. Scroll down to AWS (Amazon Web Services), and click Configure now.
At this time, only North American (U.S. and Canada) regions are supported. Barracuda automatically creates an S3 Bucket
and name.
3. The AWS Replication dialog displays. Select your preconfigured AWS Account and the AWS Region where you want your replicated
data to be stored.
4. Read and accept the S3 Bucket agreement, and click Done:
5. The AWS replication target should now be configured. Click on the Settings ( ) icon to edit the bandwidth rate limit:

See How to Set Rate Limits for more information.


Restore Barracuda Backup virtual image backups to an Amazon Web Services (AWS) instance.
In this Section


This article assumes you have replicated data to AWS:

Note that the videos in this article do not contain audio.
Important
Virtual machines (VMs) must be fully replicated to Amazon Web Services before restore
Hyper-V VMs with VHDX files are not supported
Hyper-V generation 2 VMs are not supported
VMware UEFI-boot VMs are not supported
Restore VMware or Hyper-V Backups to Amazon Web Services Video
Restore VMware or Hyper-V Backups to Amazon Web Services
Use the steps in this section to restore either a VMware or Hyper-V backup.
1. Log in to the Barracuda Backup web interface, and go to the Restore > Restore Browser page.
2. Expand the VMware data source or the Hyper-V data source in the left pane, and continue to navigate until you find the VM you want to
restore.
3. Click on the VM, and click View all revisions up to at the top of the page:
4. All available revisions display. Click Restore to the right of the revision you want to restore.
5. In the Restore dialog box, in the Restore to section, select AWS Account, and select the AWS account to restore to from the
drop-down menu:

6. Specify the AWS Region, and enter a name to identify the AMI in the AMI Name field:
7. Click Start Restore. Go to the Reports > Restore page to monitor the progress of the restore:
During the restore process, Barracuda Backup creates a temporary S3 bucket in the specified account where the virtual
machine image(s) will be reconstructed. After the image(s) are reconstructed, they are imported into EC2 as AMIs and the
temporary S3 bucket is deleted.
8. Once the AMI is created, it is accessible from within AWS and can be launched as an EC2 instance:

8. Barracuda Backup Administrator's Guide - Page 161


Before you can restore VMware and Hyper-V virtual machine (VM) backups to Amazon Web Services (AWS), you must first create the service
role vmimport.
You must configure the AWS Import Service Role to restore VMware or Hyper-V machines to an AWS Amazon Machine Image (AMI).
If you completed Step 3. Create a Service Role in Amazon Web Services in the article How to Configure Amazon Web Services
Replication and Restore, then you have already configured the AWS Import Service Role.
Amazon Elastic Compute Cloud (EC2) and Amazon Simple Storage Service (S3) instances are typically separate. AWS requires a role
to allow EC2 to access your S3 storage. AWS uses the vmimport service role to provide permissions between EC2 and S3. This step
assumes you have not set up the vmimport service role. If you previously set up the vmimport role, you must grant Barracuda Networks
access to replicate Barracuda Backup data to AWS.
To create the service role:
1. Click the following hyperlink: https://console.aws.amazon.com/cloudformation/home?#/stacks/new?stackName=barracuda-vmimport-sta

ck&templateURL=https://s3.us-east-2.amazonaws.com/barracuda-templates/vmimport.template
2. On the Select Template page, verify that Specify an Amazon S3 template URL is selected and that the URL in the text box matches
the URL in the following images:
3. On the Select Template page, click Next.

4. On the Specify Details page, click Next.
6. On the Review page, select I acknowledge that AWS CloudFormation might create IAM resources with custom names, and then
click Create to create the vmimport role in your AWS account:



Replication and Restore General FAQ
Question Answer
What is Replication to Amazon Web Services (AWS)? Barracuda’s current replication technology lets customers send data
to the Barracuda Cloud or another Barracuda Backup appliance for
offsite replication, but customers who are adopting public cloud are
looking for the flexibility to replicate data to public cloud with that
same simplicity.
With a Barracuda Backup AWS Replication subscription, Barracuda

Backup can replicate data securely and efficiently from an
on-premises physical or virtual Barracuda Backup appliance to the
AWS public cloud. This adds more deployment options and flexibility
for customers replicating data as can choose to replicate to the
Barracuda Cloud, a remote physical appliance, a remote virtual
appliance, or the AWS public cloud target.
Note that you are sending data to your own AWS account, therefore
you must have both an AWS Replication subscription and an AWS
account to replicate data.
What is Restore to Amazon Machine Image (EC2)? The Restore to Amazon Machine Image (AMI) feature allows
customers to convert their backed up VMware and certain types of
Hyper-V virtual machines (VMs) to an AMI, where they can be
launched as an Amazon EC2 instance. This feature is available for
customers with an active Barracuda Backup AWS Replication
subscription and who have replicated data to AWS. For more details
on the types of images and requirements, see the sections below:
How does Restore to AMI (EC2) work?

What are the requirements and limitations for Restore to AMI?
What is an AMI? An AMI provides the information required to launch an instance,

which is a virtual server in the cloud. You specify an AMI when you
launch an instance, and you can launch as many instances from the
AMI as needed. You can also launch instances from as many
different AMIs as you need.
An AMI includes the following:
A template for the root volume for the instance (for example, an
operating system, an application server, and applications)
Launch permissions that control which AWS accounts can use
the AMI to launch instances
A block device mapping that specifies the volumes to attach to
the instance when it is launched
What is Amazon EC2? Amazon Elastic Compute Cloud (Amazon EC2) provides scalable
computing capacity in the AWS cloud. Using Amazon EC2 eliminates
the need to invest in hardware up front, so you can develop and
deploy applications faster. You can use Amazon EC2 to launch as
many or as few virtual servers as you need, configure security and
networking, and manage storage. With Amazon EC2, you to scale up
or down to handle changes in requirements or spikes in popularity,
reducing your need to forecast traffic.

What is Amazon S3? Amazon Simple Storage Service (Amazon S3) makes it simple and
practical to collect, store, and analyze data—regardless of format—all
at massive scale. Amazon S3 is object storage built to store and
retrieve any amount of data from anywhere—web sites and mobile
apps, corporate applications, and data from the IoT sensors or
devices. It is designed to deliver 99.999999999% durability, and has
many customers each storing billions of objects and exabytes of
data. You can use it for media storage and distribution, as the "data
lake" for big data analytics, as a backup target, and as the storage
tier for serverless computing applications. It is ideal for capturing data
like mobile device photos and videos, mobile and other device
backups, machine backups, machine-generated log files, IoT sensor
streams, and high-resolution images, and making it available for
machine learning to other AWS services and third-party applications
for analysis, trending, visualization, and other processing.
Who is Replication to AWS designed for? Barracuda Backup AWS Replication is designed for customers who
are adopting public cloud and wish to replicate their on-premises
backup data to AWS for disaster recovery.
Why is Barracuda offering Replication to AWS? Barracuda is offering replication to AWS to provide existing and new
Barracuda Backup customers with more deployment options and
flexibility, as can choose to replicate to the Barracuda Cloud, a
remote physical appliance, a remote virtual appliance, or the AWS
public cloud target.
What are the differences between Barracuda Cloud and Replication While the software and general functionality is the same between the
to AWS? Barracuda Cloud and AWS Replication, there are some important
differences between the two deployment models:
1. The Replication to AWS option is essentially a new "region" of

Barracuda Cloud deployed in public cloud (AWS).
2. Customers can choose to replicate their on-premises backup
data to this "region" by purchasing a Barracuda Backup AWS
Replication subscription, similar to purchasing a Barracuda
Cloud Storage subscription.
3. The primary difference between Barracuda Cloud Storage and
data stored in AWS is that customer binary data is physically
stored in an AWS S3 bucket in the customer’s account when
replicating to AWS, as opposed to Barracuda Cloud Storage.
4. When replicating data to AWS, the customer can restore
VMware and Hyper-V virtual machines to an AMI. This is a
feature that is only available to customers with a Barracuda
Backup AWS Replication subscription.
How does Replication to AWS work? Replication of backed up data to AWS works very similarly to data
replicated to Barracuda Cloud Storage. The key difference is that
data replicated to AWS is stored in the customer’s AWS S3 bucket.
Barracuda Backup physical or virtual appliance is installed

on-premises and backing up data.
Customer binary data is stored in the customer’s AWS S3
bucket.
Metadata is stored on Barracuda’s AWS cloud infrastructure.
Barracuda Backup devices, including ones replicating to AWS,
are managed from the Barracuda Cloud using Barracuda Cloud
Control.
At this time, Barracuda Backup devices only support replication
to a single "cloud" replication destination at a time. A Barracuda
Backup device can only replicate to the Barracuda Cloud or to
AWS, not both.

Can I replicate to multiple clouds at the same time? No. Barracuda Backup devices only support data replication to one
form of cloud storage (Barracuda Cloud or AWS) at a time.
Barracuda Backup devices are still capable of replicating to multiple
destinations. These destinations include physical and virtual
appliances. For example, a Barracuda Backup device can replicate to
both the Barracuda Cloud and another Barracuda Backup physical or
virtual device, but not to both the Barracuda Cloud and AWS.
Can I migrate my data from the Barracuda Cloud to AWS? Yes. Barracuda Networks Technical Support can assist with the data
migration process and AWS configuration.
Where is my data stored when using Replication to AWS? Backup metadata is stored in Barracuda’s AWS account in Amazon’s
US East (Ohio) region. Binary backup data is stored in an S3 bucket
in the customer’s AWS account.
Where is Replication to AWS supported? At this time, Barracuda Backup AWS Replication is only supported in
North America.
Which AWS regions are supported? Barracuda Backup metadata lives in the US East (Ohio) region for all
customers. Currently, all customer binary data is also located in the
US East (Ohio) region in the customer’s S3 bucket. This is subject to
change.
What is the data path for data replicated to AWS? All data replicated to AWS from a Barracuda Backup device travels
through the US East (Ohio) region of AWS. Backup metadata lives in
the US East (Ohio) region, while binary backup data comes to rest in
the customer’s selected AWS account, region, and S3 bucket.
No customer binary data is stored within Barracuda’s AWS account

in the US East (Ohio) region.
Is data replicated to AWS encrypted? Yes. Data transferred between your network and Barracuda Cloud
Storage, or between your network and a remote Barracuda Backup
appliance, or between your network and Amazon Web Services, is
always encrypted. File parts are AES 256-bit symmetrically encrypted
before they are stored, and they remain encrypted until a restore is
requested.
Is data deduplicated in AWS? Yes. Backup data replicated to AWS from an on-premises Barracuda
Backup device is deduplicated within the S3 bucket where the data is
stored. Data replicated from multiple Barracuda Backup devices to
the same S3 bucket is deduplicated globally.
Can I use AWS S3 Infrequent Access or Glacier storage to store my AWS S3 Infrequent Access and Glacier storage are not supported
data? and not recommended for use at this time. Moving replicated binary
data to these storage classes may cause issues that negatively
impact restore functionality and recovery times, especially with
Glacier storage since the recovery times are lengthy per Amazon
documentation.
Can I tier my data, using different forms of storage, that is replicated No. Only Amazon S3 Standard storage is supported at this time.
to AWS?
AWS S3 Infrequent Access or Glacier storage are not supported and
not recommended for use at this time. Moving replicated binary data
to these storage classes may cause issues that negatively impact
restore functionality and recovery times.
How does Restore to AMI (EC2) work? VMware and Hyper-V VMs that are replicated to an AWS S3 bucket
can be restored from the Barracuda Backup web interface as an AMI.
From within AWS, the AMI can be launched as an EC2 instance.
The process of restoring the VMware or Hyper-V virtual machine

from Barracuda Backup is the same as restoring the virtual machine
to an on-premises destination. After navigating through the
Barracuda Backup Restore Browser and selecting a VM to restore,
choose the Restore to AMI option in the Restore to section. The
article How to Restore VMware and Hyper-V Backups to Amazon
Web Services details the process.

What are the requirements and limitations for Restore to AMI? Restore to AMI supports VMware and Hyper-V VM images only
VMs must be fully replicated to AWS before restores can be
initiated
VMware UEFI-boot VMs are not supported
Hyper-V Generation 2 VMs are not supported
Hyper-V VMs with VHDX files are not supported
What is the data path for data restored from AWS? All data restored from a customer S3 bucket in AWS back
on-premises to a target or Barracuda Backup device travels through
the Barracuda Cloud/AWS infrastructure in US East (Ohio) region of
AWS first. Transfer fees between regions apply.
Example: The customer chooses the US West (Oregon) region for

their S3 bucket. Upon a restore from the cloud, the data must travel
from the US West (Oregon) region to the US East (Ohio) region,
which incurs AWS S3 region transfer fees.
Does restored data come directly from AWS S3 storage? In most cases, data is restored directly from the on-premises
Barracuda Backup device when a restore is initiated from the
Barracuda Backup cloud web interface. The only times when that is
not the case is when the data is no longer present on the
on-premises Barracuda Backup device. Here are the cases where
data may not be present locally:
The data has been removed from the on-premises Barracuda

Backup device and "vaulted" using the Offsite Vaulting feature.
The download feature in the cloud web interface has been used
to recover data. All downloads initiated from the cloud web
interface pull data directly from the replication target, in this case
AWS.
In a disaster recovery or hardware replacement scenario where
a replacement on-premises Barracuda Backup device needs to
be populated with the data stored in AWS.
Can a reseller or managed services provider (MSP) replicate client Yes. Any AWS account can be configured within the Barracuda
data to their own AWS account and S3 bucket? Backup web interface and used to replicate backup data to.
-Licensing FAQ
Question Answer
How is AWS Replication licensed? Barracuda Backup AWS Replication is licensed as a subscription,
based on the Barracuda Backup appliance model, or the number of
sockets for a virtual Barracuda Backup appliance.
Barracuda Backup Appliance – Subscription is based on the

model it is attached to
Barracuda Backup Vx – Subscription is based on the cost of the
total number of licensed sockets/servers
What does my Barracuda Backup AWS Replication subscription The AWS Replication subscription from Barracuda covers
provide? management, deduplication, compression, and egress fees from data
leaving AWS.
The customer needs to pay AWS S3 storage fees, transfer fees if

they apply, and the Replication to AWS subscription from Barracuda.
How much data can I replicate to AWS with a subscription? The amount of data that can be replicated is technically unlimited;
however, the amount of data that can actually be sent offsite is
limited by the size/model of the Barracuda Backup appliance.
For Barracuda Backup Vx appliances, the amount of data that can be

replicated offsite to AWS is unlimited.
Is there a separate license or subscription for the Restore to AMI No. This is a free feature only available for customers with an AWS
(EC2) feature? Replication subscription from Barracuda.
-Deployment FAQ

Question Answer
What environments are supported by Barracuda Backup AWS Barracuda Backup with AWS Replication protects all the same
Replication? environments as a Barracuda Backup with Barracuda Cloud storage.
How is AWS Replication configured? See the following articles to configure AWS replication:
How to Configure Amazon Web Services Replication and

Restore
What is an AWS CloudFormation Template? AWS CloudFormation simplifies provisioning and management on
AWS. You can create templates for the service or application
architectures you want and have AWS CloudFormation use those
templates for quick and reliable provisioning of the services or
applications (called "stacks"). You can also easily update or replicate
the stacks as needed.
What access/permission is the CloudFormation template giving Currently the CloudFormation templates give Barracuda Backup full
Barracuda? access to S3 to create the bucket for replication and full access to
EC2 for the Restore to AMI feature.
Do I need to create an S3 bucket to replicate data to? No. During the AWS Replication setup process, Barracuda Backup
automatically creates a new S3 bucket in your AWS account that is
used to store replicated data. The Barracuda Backup S3 bucket looks
similar to this: barracuda-bbs-1240749-b62e9951-e9f2-407e-a2c6-
463fed5df743.
How do I restore a VM to an AWS AMI (EC2)? See the article How to Restore VMware and Hyper-V Backups to
Amazon Web Services for steps to restore a VMware or Hyper-V VM
to an AWS AMI (EC2).

Getting Started
Recommended Steps
Step 1 - How to Install the Barracuda Backup Appliance

Step 2 - How to Configure Barracuda Backup
Step 3 - How to Configure Backups
Step 4 - Data Backup Tasks
Energize Updates
Alternatively, you can view the Barracuda Backup Quick Start Guide.

Step 1 - How to Install the Barracuda Backup Appliance
Before installation, determine the best type of deployment for your Barracuda Backup appliance; refer to the Deployment section for
a list of options.
Before you can connect your Barracuda Networks products to Barracuda Cloud Control, you must first create an account:
1. If you do not have an account, go to https://login.barracuda.com/ and click Create a user.

2. Enter your name, email address, and company name, and specify if this is a partner account. Click Create User.
3. Follow the instructions emailed to the entered email address to log in and create your Barracuda Cloud Control account.
4. After submitting your new account information, the Account page displays your account name, associated privileges, and username.
Verify the Equipment
Verify you have the necessary equipment:
Barracuda Backup appliance (check that you have received the correct model) and AC power cable (included)
Barracuda Backup appliance serial number and linking code (available on both the side of the Barracuda Backup appliance and the
Barracuda Backup Quick Start Guide included with the appliance)
Connectivity and access information for all data sources you want to back up
VGA Monitor and USB or PST 2 keyboard (recommended/customer supplied)
*Cabling differs based on the appliance model. For more information, refer to Barracuda Backup Hardware Specifications.
Activate Backup Product
Important
If you are an Intronis customer, contact Intronis before proceeding.
Once your account is paid for, you must activate Barracuda Backup to initiate backups.
If you are linking a Barracuda Backup Virtual Appliance (Vx), it is crucial that the Barracuda Backup Vx that will be performing backups
be linked to your Barracuda Cloud Control account before you link the receiving unit. Attempting to link the receiving unit first can cause
linking issues for your entire Vx deployment.
To activate your appliance:
1. Go to https://login.barracuda.com/, and log in. If you do not have an account, click Create a User, follow the account creation
instructions, and log in.
2. Click Backup in the left pane. If this is your first time activating a Barracuda Backup appliance, click Start Backup Setup; otherwise,
click the Backup tab, and go to Admin > Activate Backup Product.
3. On the Validation page, enter the Serial number and the Linking code from the sticker on the back of the Quick Start Guide, indicate
your Identity, and click Continue.
To manage the appliance independently of Barracuda Cloud Control (conectionless), turn on Locally control device under De
vice Management, and proceed to Step 6 below.
5. Select Replicate data to Barracuda Cloud Storage, select the Storage Amount and Subscription Period if you intend to replicate
data to Barracuda Cloud Storage; no Cloud Storage subscription is required for site-to-site replication.
Important
Replication is limited to site-to-site.
6. Enter your Billing Information. Read and accept Terms and conditions.
7. Click Activate Backup Product.
8. The linking process may take a few minutes to complete. Wait until the Dashboard page displays. A green indicator displays next to the
appliance name indicating it is successfully linked to your account.
Physically Install the Appliance
1.

1. Fasten the Barracuda Backup appliance to a standard 19-inch rack or other stable location.
Caution
Do not block the cooling vents located on the front and rear of the appliance.
2. Connect an Ethernet cable from your network switch to the Ethernet port on the back panel of the appliance, and any additional cables
as necessary.
3. Connect a standard VGA monitor, PS2/USB keyboard, and an AC power cord to the Barracuda Backup appliance.
4. Press the Power button on the front panel to turn on the appliance.
Continue with Step 2 - How to Configure Barracuda Backup.

How to Add Customers to the Partner Tab

This article applies to Partner or Reseller accounts only, and assumes you have completed the initial appliance setup.
Use the following steps to add customers to the Partner tab in Barracuda Cloud Control:
1. Log in to https://login.barracuda.com/ using your partner login credentials, and click Home in the left pane.
2. Go to Partner > Customer Accounts, and click Manage Customer Accounts.
3. In the Manage Customer Accounts page, click Add Customer. The Add Customer Account dialog box displays.
4. Enter the Customer Account Name, the Customer Admin Name, the Customer Admin Email Address, and click Check for
Availability.
5. The Partner Admins and Entitlements sections now display. Click on a partner administrator name, and select the associated
entitlements for that user. Complete this step for each partner administrator who is to have access to this customer account.
6. Click Create Customer. The customer is added to the Manage Customer Accounts list in the Partner tab.
7. Once the customer is created, your partner information is added to their Admin > Users page when they log in to Barracuda Cloud
Control.

Step 2 - How to Configure Barracuda Backup
Before configuring the IP address and network settings, complete Step 1 - How to Install a Barracuda Backup Server.
Deployment Options
Determine the best deployment for your environment before proceeding:
Cloud Deployment – If the appliance is located behind a corporate firewall, you may need to open the following ports to allow
communication between the appliance and Barracuda Networks; note that there cannot be any restrictions on these ports:
Ports 80/443, 1194, and 5120-5129 outbound for both TCP and UDP are required for communication. Ports 5120-5129 are used
to replicate data to Barracuda Cloud Storage. Barracuda Backup uses these ports to securely transfer data over the Internet to
the offsite storage location. Contact Barracuda Technical Support to restrict outbound network traffic on these ports to only reach
Barracuda Networks.
Depending on your environment, you may need to remove restrictions on additional ports. Contact Barracuda
Technical Support if you need additional direction.
By default, your Barracuda Backup appliance is configured to obtain an IP address on your network using DHCP. To specify a
static IP, use the console administration interface using the steps in the section Configure the IP Address and Network
Settings below.
Local Control (Connectionless) Deployment – (Not supported for Barracuda Backup Vx) Initial configuration requires an Internet
connection using ports 80/443 TCP and 1194 TCP/UDP to activate your Barracuda Backup appliance. Once activated through the linking
process, the appliance goes into an offline state and an Internet connection is no longer required. Complete the linking process in the
section Link Your Barracuda Backup Appliance to an Account below, and then proceed to Understanding Local Control to complete your
deployment.
Configure IP Address and Network Settings (Cloud Deployment Only)
address instead, you can configure it using the console administration interface. If not, proceed to the section Configure Your Corporate Firewall:

2. Use your Arrow keys to highlight the TCP/IP Configuration field.
3. Press Enter to access the right pane.
Do not select Use DHCP in the right pane before saving. Doing so fetches and immediately applies the network settings via
DHCP.
4. Use the Arrow keys to select and enter the IP Address, and then press Enter to move to the next option.
5. Enter the remaining settings as appropriate for your network.
6. Use the Arrow keys to navigate to Save, and press Enter.
In the Network Status section, Local and Internet should display as Up while Cloud displays as DOWN until the appliance is linked to an
account later in the installation process.
For additional information, refer to the article Barracuda Console.
Verify Connection to Barracuda Networks (Cloud Deployment Only)
Once you log in to the web interface, the Barracuda Backup appliance you have just installed, powered on, and linked, should be listed in the left
pane with a green indicator ( ) to the left of its name. The Dashboard page displays a green light next to the appliance name indicating it is
successfully linked to your account. If the indicator light is not green, verify network settings and appliance connectivity, or contact Barracuda
Networks Technical Support for additional direction.
Enter Server Name and Location
In the System > Barracuda Backup Appliance Settings page, enter a name for your Barracuda Backup appliance, the associated time zone,
and server location.
Define Display Groups

3. To add a new display group, enter a name for the group of devices, and then click Add. For example, if you want to group all Barracuda
Backup Servers by location, you might create groups by geographic location: Engineering - Asia, Engineering - US, Engineering -
Europe.
5. To remove a display group, click Remove to the right of the group name you want to remove; click OK to remove the group.
Add a Barracuda Backup Appliance to a Group
1. In the left pane, select the desired Barracuda Backup, and go to the System > Barracuda Backup Appliance Settings page.
2. In the Backup Appliance Display Group section, select the desired display group name from the Current Display Group drop-down
menu.
3. To add or remove display groups, click Manage your display groups; the Admin > Display Groups page displays.
4. Click Save.
Continue with Step 3 - How to Configure Backups.

Step 3 - How to Configure Backups
Before configuring the web interface, complete Step 2 - How to Configure Barracuda Backup.
You can configure where your data is backed up and in what manner. This article refers to data sources, which are subsets of data on each
server that is to be backed up.
Where Data is Backed Up
You configure how and when your data is to be backed up. All data is first backed up to a local Barracuda Backup appliance. If you have more
than one local Barracuda Backup appliance, you must decide which one backs up which systems.
Data on the local Barracuda Backup appliance can then be backed up, or replicated, to another Barracuda Backup appliance in a remote
location, to the Barracuda Cloud Storage, or to a combination of the two. See Site-to-Site Deployment or Site-to-Cloud Deployment for
deployment options. The location of the replicated data is specified for each data source. You can also choose to not replicate the backed up
data.
Configuration Details
For system-specific configuration details, refer to Backing Up Data Sources.
Choose the method for backing up data based on the type of data. The Barracuda Backup appliance supports the following data sources:

Microsoft Exchange Server and Exchange Server DAG
VMware Backup
How to Configure an Agent-Based Data Source
How to Back Up Lustre Mounts with the Barracuda Backup Agent (Linux)
Review the following sections for more information about specific data types.
Microsoft Server Applications
The Barracuda Backup Agent (Windows) provides application-aware backups for Microsoft SQL Server, Microsoft Exchange Server (including
message-level backup of mailboxes and messages), Microsoft System State, and Microsoft Hyper-V Server. The Agent also provides support for
open file backups, and file attributes and permissions.
Install the Agent on every Microsoft Server that you want to back up; you can download and install the Barracuda Backup Agent (Windows) from
the System > Software Downloads page. Data sources that can be backed up using the Agent are automatically detected after the computer is
identified on the Backup > Sources page.
The Agent searches the NTFS change journal to track modified, added, or deleted files rather than searching the entire volume to improve Agent
backup speed.

Microsoft Exchange Storage Group Backup
Microsoft Exchange uses transaction logging to commit new and changed data to the database, and to ensure that records of the transactions
exist if a store is damaged between backups. The Exchange storage group, and its associated transaction logs, is the most important data to
back up on your Exchange Server to ensure your email database is available in the event it becomes damaged or unrecoverable. If you must
rebuild a server, you can use the latest transaction log files plus the last full backup to recover your database.
The Barracuda Backup Agent (Windows) backs up and restores the entire storage group; it allows for the storage group to be restored to a
storage group or to an alternate Microsoft Exchange Server.
Microsoft Exchange Server Message-Level Backups
Message-level backup provides a quick way to restore single email messages to the original location or to an alternate mailbox. Message-level
backup is not intended to be a disaster recovery option for your Microsoft Exchange environment. The Barracuda Backup Agent (Windows) allow
s you to back up the entire Exchange Information Store and should be used for disaster protection.
Novell GroupWise Message-Level Backup
Barracuda Backup connects directly to Novell GroupWise to back up individual emails stored within user mailboxes.
The Barracuda Backup Agent (Windows) provides a complete backup of the Microsoft SQL Server Backup including the master, user, model,
msdb, and pubs databases.
Barracuda Networks recommends that all of the Microsoft SQL Server user databases be configured for full recovery model so that transaction
logs can be backed up. This allows you to restore a user database to any point of time that is contained within a transaction log backup.
Some versions of the Microsoft SQL Server, such as SQL Express database, do not support full recovery model. If the full recovery model cannot
be used, the Barracuda Backup Agent (Windows) performs full backups of the database each time a backup runs.
The Microsoft article Recovery Models (SQL Server), provides more information about the Microsoft SQL Server and its three database recovery
models, and how to change the recovery model of a database.
Important
Do not use other methods to back up Microsoft SQL Server databases, such as Microsoft or third-party utilities, when using the
Barracuda Backup Agent (Windows). If you use more than one backup method on the same database, one or more of those methods
causes the Microsoft SQL Server to truncate the transaction logs. This forces a full backup of the database every time, and can result
in data that cannot be restored.
Barracuda Networks recommends that you back up the master database each time it is changed. The master database contains configuration
information that is required to restore an instance of SQL Server.
Microsoft Hyper-V Virtual Machines
The Barracuda Backup Agent (Windows) provides application-aware backups for Microsoft Hyper-V hypervisor-based virtualization systems, and
provides support for open file backups, file attributes, and permissions as well as automatic data source detection.
Windows System State Backup
The Barracuda Backup Agent (Windows) can back up and restore the Microsoft Windows System State. Microsoft Windows System State
backups allow backup of critical system related components, including the local Registry, COM+ Class Registration Database, the System Boot
Files, Active Directory Database Files (NTDS.DIT) for Domain Controllers, and the SYSVOL folder. A System State backup can be used to
recover to a known good system state after a hardware or software crash.
System State data might not include all of the information required to recover a system from a failure. Barracuda Networks recommends that all
boot and system volumes be backed up in addition to System State.
VMware Host Storage
Add VMware host storage, including host configuration and virtual machine images, as data sources for backup and restoration through
Barracuda Backup. You must be running a licensed copy of ESX, ESXi, or vCenter version 4.0 or later, and the VMware license must include
access to the vSphere Data Recovery API. For details on CBT, refer to the article Understanding Changed Block Tracking on Virtual Machines.
Note that the entire VMware image is backed up each time back up is run.
Linux File Systems using the Barracuda Backup Agent (Linux)
Use the Barracuda Backup Agent (Linux) to back up Linux file systems such as Red Hat, Ubuntu, or SUSE. The Agent can back up open files,
permissions, soft and hard links, and supports multiple data streams. Barracuda Backup Agent (Linux) supports:

Kernel 2.6.16 and higher

glibc version 2.2.5 for 32-bit binary
Linux Systems, Macintosh OS X, AIX, Unix, and Novell NetWare using File Share
Linux Systems with Kernel versions below 2.6.16, Mac OS X, AIX, Unix Systems, and Novell NetWare systems are backed up using File Share.
This method refers to the mechanism that uses standard network protocols, such as CIFS/Samba or SSHFS, to access your servers.
Note that for Linux Systems with Kernel versions 2.6.16 and higher you can use the Barracuda Backup Agent (Linux). For all other versions, use
the File Share method.
You can back up network addressable storage (NAS) data sources with CIFS and back up access control lists (ACL).
Continue with Step 4 - Data Backup Tasks or go to Backing Up Data Sources.

Step 4 - Data Backup Tasks
Before configuring the web interface, complete Step 3 - How to Configure Backups.
Perform the tasks in this article to configure your data for backup.
Identify Systems to be Backed Up
For each local Barracuda Backup appliance, identify the data sources that are to be backed up. There may be more than one data source on
each server, and each can have unique backup characteristics.
1. Log in to Barracuda Backup, and select the associated Barracuda Backup appliance in the left pane.
2. Go to the Backup > Sources page, and click Add Computer to identify the system; when you enter a set of user credentials on this
page, the specified username is used for network file systems and must have at least read access to the data you intend to back up.
For Microsoft Windows and Novell Netware, you must enter both a username and password. For Mac OSX, Linux and UNIX (SSHFS),
enter a username after you set up your SSH key.
Alternately, you can download the Barracuda Backup Agent software from the System > Software Downloads page, and
install it on every computer to be backed up. For more information, refer to Barracuda Backup Agent (Windows) and Barracuda
Backup Agent (Linux).
Note that you must have 1 GB of free space to install the Barracuda Backup Agent software.
3. Once a computer is added, click Save. The Add Data Source page displays. Enter the data description and select the appropriate data
type. For Windows-based agent shares, if you want to be able to do a bare metal recovery, make sure to back up all system volumes
and system state.
4. Turn on Replicate to Other Barracuda Backup appliances, and click Save.
5. Complete steps 1 through 4 for each system and data source you want to back up.
If this is a Mac, UNIX, or Linux system, follow the instructions on the Add Computer page to install a public key so
that the Barracuda Backup appliance is able to securely connect to it, then you can configure the data sources.
If this is a Novell Netware system, enter the system information on the Add Computer page. When that is done, on
the Add Data Source page you will be able to specify the data location. CIFS or SSHFS is used to back up the
Netware data.
For all systems, when you enter a set of user credentials on this page, the specified username is used for network
file systems and must have at least read access to the data you intend to back up. For Microsoft Windows and
Novell Netware you must enter both a username and password. For Mac OSX, Linux and UNIX (SSHFS), you only
need to enter a username after you set up your SSH key.
For Active Directory users, add the domain and then a \ in the username field. For example:
Username = cuda\jsmith
Select Type of Data to be Backed Up
After a computer has been added, select the data source(s) to be backed up on that computer:
1. From the Backup > Sources page, click Add Data Source next to the associated device from which you want to back up.
2. On the Add Data Source page, select the appropriate data type. For Windows-based agent shares, if you want to be able to do a bare
metal recovery, make sure to back up all system volumes and system state.
3. To replicate to Barracuda Cloud Storage, turn on Replicate to Barracuda Cloud Storage; if you have globally selected to replicate all
data to Barracuda Cloud Storage for this Backup Server, this option is automatically turned On.
4. Continue with the configuration information and save the changes.
Authentication and System Configuration Notes

Backups for Mac OS X/Linux/UNIX (SSH Connections)
Barracuda Backup uses an SSH (Secure Shell) client to access data contained on Mac OS X or Linux / Unix based computers
running an SSH daemon. The SSH client uses public key cryptography to establish a secure connection to the SSH daemon.
You must configure SSH access to any Mac OS X or Linux / UNIX computer you want to back up. Follow the onscreen instructions
on the Backup > Sources > Add Computer page according to the operating system.
Directory-Based File Shares
When you back up a file share you must specify the share name on the network before you can select the folders to be backed up.
On a Windows machine, a share name can be a drive volume such as "C$", or a folder and its associated subfolders such as "My
Documents". At a minimum you will need Read access to the data that you are backing up and Change Access or Full Control to the
shares in order to perform a restore. For Mac OS X and Linux/Unix-based computers with SSH connections, the share name should
be the entire path to the directory you would like to back up, e.g., /home/<user>.

When you select folders for backup you should begin by selecting the folders at the top of the folder tree hierarchy, and then
deselect folders lower in the hierarchy that you do not want to back up. You can also specify an optional exclusion rule, which is
applied when the backup runs to rule out files that do not meet your back up criteria.
Message-Level Backup: Microsoft Exchange and Novell GroupWise
When you select the Message-Level Backup data type, you must supply the authentication information to access your mail server
before you can select which mailboxes to back up. In addition to the authentication information provided on the Barracuda
Backup web interface, you must configure the Message-Level settings on your Exchange Server or GroupWise Server.
For Microsoft Exchange servers, refer to Exchange Message-Level Backups for detailed instructions for configuring message-level
backups.
For GroupWise 8 and above, refer to GroupWise Message-Level Backups for detailed instructions for configuring message-level
backups.

For additional information, refer to the Supported Data Types section.
Note that schedules are automatically created (with the default set to back up every day at 8:00PM) when a data source is created exc
ept if a schedule specifying all data sources already exists.
In version 6.2 and higher schedules are part of data source item selection. For this reason, if you did not configure schedules in version
6.1 and earlier, a schedule is automatically created when you upgrade to version 6.2.
For more information on schedules, see the Schedules Page.
Now that you have configured your computers and data sources, you can create backup schedules, either individually or for all sources. If no
schedule is created for a data source then it will not be backed up.
To create a backup schedule:

Go to the Backup > Schedules page of the Barracuda Backup web interface. Click Add a Schedule and fill in the information on the Add
Backup Schedule page:

Apply to All Computers and Data Sources for this Barracuda Backup
Items to Back Up – Turn
appliance on to back up all content, or turn off, then expand and select the items you want to back up.
Schedule Timeline – Turn on the days you want the back up to run.
Daily Backup Timeline – Enter the start time; turn on Repeat if you want to specify a time period and end date to repeat the
backup.
If the backup schedule is for Microsoft SQL or Microsoft Exchange, you must specify the type of backup to run:
Smart – This backup type is a combination of the full backup and the transaction log backup, minimizing the impact of backups on
network resources necessary to transfer data offsite. Barracuda Networks recommends this backup type for SQL and Exchange
servers.
With the Smart backup type, threshold values are used to determine when to switch between full and log backups. The minimum threshold
value specifies how many days Barracuda Backup continues to back up transaction logs before another full backup is run. After the minimum
threshold value is met, Barracuda Backup determines whether to perform another backup based on the binary data queue. If the binary data
queue size exceeds 1 GB, Barracuda Backup continues the transaction log backup until:
the maximum threshold level is met, or

the queue size drops below 1 GB
Modify Replication Rate Limit (Optional)
Your initial offsite backup may take on the order of days to complete but all of the data is backed up locally on the Barracuda Backup appliance

The length of transfer time it will take to get your data offsite is impacted by the compression and de-duplication rates on your data, the uplink
To adjust the backup rate limit:

1. On the Backup > Rate Limit page, select a Barracuda Backup appliance on the left menu and create or edit the rate limit.
2. You can specify a default rate limit and an alternate rate limit which is maintained only during the specified time periods.
Exclude Files from Backup (Optional)

1. Go to the Backup > Exclusions page of the Barracuda Backup web interface. Click Add an Exclusion.
Add Exclusions to Reports – Turn on to include exclusions in reports, and turn off if you do not want to include exclusions
in the reports.
Where to Exclude – Turn Apply to All Computers and Data Sources for this Barracuda Backup appliance on to
apply the exclusion rule to all computers and data sources for the selected Barracuda Backup
appliance, or turn off, then expand and select the items to which to apply the exclusion rule.
3. In the What to Exclude section, specify what to exclude:
From the Preset Expressions menu, select the content you want to exclude, for example, Video files, then click Add.
To edit an existing exclusion rule, go to the Backup > Exclusions page of the Barracuda Backup web interface, and click Edit following the
exclusion rule you want to edit. Make the necessary changes, then click Save.
To delete an exclusion rule, go to the Backup > Exclusions page of the Barracuda Backup web interface, and click the Delete icon following
the exclusion rule you want to remove. Click OK to remove the rule.
Data is retained based on a traditional grandfather-father-son (daily-weekly-monthly) rotation model. You can
specify how long to keep daily, weekly, monthly, and yearly backups by creating data retention policies.
Different retention policies can be created for different sets of data including files, data backed up by the Barracuda
Backup Agent (Exchange, SQL, System State), and email messages.
subset of the data.

1. Go to the Backup > Retention Policies page, click Add a Retention Policy, and enter a name to identify the policy.
3. Click Save.
Your initial backup takes some time to complete; you can view backup status in the Reports > Backup page.
you want to view.

Energize Updates
Energize Updates protects your data, and includes:
Basic support – 24x7 email support and phone support between the hours of 9 a.m. and 5 p.m. Monday through Friday in the US (Pacific
Time), Japan, China, Austria and the United Kingdom time zones.
Firmware Maintenance – New firmware updates with feature enhancements and bug fixes.
Security Updates – Patch or repair security vulnerabilities.
Early Release Firmware – Optional participation in the Barracuda Early Release Firmware program.
Allowing subscriptions to expire can lead to a single point of failure in your backup data.
, replication and in-product behavior is affected. Barracuda does not hold data in the event of Energize Updates expiry.
I think we should pull away from the security aspect and focus on data protection.
We need to state what the implications of expiring EU are for backup (i.e. replication, in-product behavior).
We might also want to add a note that we will not hold their data hostage in the event of expiry.
I think the biggest consequence of not renewing properly is continuity next to single point of failure.
Missing a firmware update or more puts you behind, and the farther behind you are, the harder it is to get back up to speed.
They want support to be available to them, and losing support is a real issue for some customers.
Additionally, subscriptions expiring can lead to a single point of failure in their backup.
And, if that point fails, they won’t have support to help them.
Purchase Energize Updates Subscription
An Energize Updates Subscription is mandatory with the purchase of a Barracuda Backup appliance to provide complete data protection.
Purchase subscriptions for one, three, or five year terms.
Hardware Refresh
Refresh your hardware at any time through the Barracuda Hardware Refresh Program. Any unused portion of your Energize Updates
Subscription is automatically transferred to the new Barracuda Backup appliance.
Subscription Activation and Expiration
The Energize Update Service begins on the date the Barracuda Backup appliance is activated and expires based on the purchased service plan.
For example, exactly one year, three years, or five years from the delivery date.
Subscription Upgrade
You can upgrade from your purchased service plan. You have 60 days from the date of purchase, either initial purchase or renewal purchase, to
extend your subscription period.
An Energize Updates Subscription belongs to the original purchaser and cannot be transferred under any circumstances.
Subscription Renewal - Before Expiration
Before the subscription expires,
Purchased directly from Barracuda Networks – Contact Barracuda Networks at (408) 342-5400 or 1 (888) Anti-Spam,
Monday-Friday, 9 a.m. - 6 p.m. (PT) to renew. You must have your product serial number available.
Purchased from a Reseller – Contact your Reseller who will coordinate your renewal.
Subscription Renewal - Expired

Avoid allowing your subscription to lapse; doing so places your company’s passwords, usernames, intellectual property and your
employee’s personal and banking information at risk. Without receiving updates your network and users are no longer protected from
any future viruses, spyware, malware, and spam. Additionally, you will not have access to the Barracuda support team.
Renew Your Subscription
If your Subscription does lapse, you can still renew. However, it is important to note that the renewal starts from the expiration of the previous
subscription term. For example, if you allow your Subscription to lapse for four months and then renew the Subscription for a one year term, you
will have eight months on your subscription renewal. Once your Subscription is renewed, all updates, patches, and firmware releases you missed
during the lapsed time period are applied, ensuring you get what you paid for: a 12 month subscription of updates and firmware releases.

Appliance Web Interface

This section describes each page in the Barracuda Backup appliance web interface. For Barracuda Cloud-to-Cloud Backup web interface, see Cl
oud Backup Web Interface.
In this Section
Dashboard Page
Backup Page
Restore Page
Reports Page
System Page
Admin Page

Dashboard Page
The Backup Dashboard displays an aggregate view of all units on a Barracuda Backup account. This view changes during Barracuda Backup
appliance selection to view specific detail about a selected unit.
The multi-appliance dashboard displays irrespective of the firmware version running on the appliances.
The single appliance dashboard displays on appliances upgraded to firmware version 6.4; older firmware versions will continue
to display the existing Status page.
What's New
The new Barracuda Backup Dashboard includes the following features and improvements:
Modern look and feel

Improved page load speed and performance
Relevant, easy to understand information
New additions to the dashboard:
Storage efficiency
Subscription information
Backup reports
Storage allocation
Current tasks
Updates include improved backup health, storage, system health, offsite transfer remaining, and offsite transfer efficiency reporting
Figure 1. Multiple Appliance Dashboard Display.
Figure 2. Single Appliance Dashboard Display.

MULTI-APPLIANCE DASHBOARD
Backup Health Overview
The Backup Health graph shows the current status of each source configured across all Barracuda Backup devices. If the last backup that ran for
a source was successful, it counts in the green success portion of the graph. If a source had a backup failure, it counts in the red failure portion of
the graph. An inactive source is a source that is currently turned off on the Sources page.
Figure 3. Backup Health Graph.
Storage Overview
The Storage graph shows the amount of storage currently being used by all Barracuda Backup devices in this view.
To view the amount of storage consumed in aggregate in the Barracuda Cloud, click Cloud below the Storage graph.
Figure 4. Storage Graph.

Storage Efficiency Overview
The Efficiency graph shows the amount of storage currently being used by all Barracuda Backup devices in this view and the amount of storage
saved by Barracuda Backup deduplication and compression.
To view the storage efficiency in aggregate in the Barracuda Cloud, click Cloud below the Efficiency graph.
Figure 5. Storage Efficiency Graph.
Devices Overview
The devices table shows all of the Barracuda Backup devices in the current view. Each column is sortable and health information is highlighted
for effect.
Figure 6. Devices.

SINGLE APPLIANCE DASHBOARD
Backup Health
The Backup Health graph shows the current status of each source you have configured in Barracuda Backup. If the last backup that ran for a
source was successful, it counts in the green success portion of the graph. If a source had a backup failure, it counts in the red failure portion of
the graph. An inactive source is a source that is currently turned off on the Sources page.
To view which sources have failed, click the link below the Backup Health graph.
Figure 7. Backup Health Graph.
Storage
The Storage graph shows the amount of storage currently being used by your Barracuda Backup device.
To view the amount of storage consumed in the Barracuda Cloud or the amount of storage used on a Barracuda Backup replication partner, click
on the links below the Storage graph.
Figure 8. Storage Graph.

Storage Efficiency
The Efficiency graph shows the amount of storage currently being used by your Barracuda Backup device and the amount of storage saved by
Barracuda Backup deduplication and compression.
To view the storage efficiency in the Barracuda Cloud or on a Barracuda Backup replication partner, click on the links below the Efficiency graph.
Figure 9. Storage Efficiency Graph.
Subscriptions
View your subscription status.
Figure 10. Subscriptions.

System Health
Figure 11. System Health.
Backup Reports
Backup Reports shows the last five backup schedules that have run or are currently running. To view more backup reports, click View all in the
upper right-hand corner. To view more details about a specific backup report shown in this widget, click the backup schedule name.
Figure 12. Backup Reports.
Storage Allocation
The Storage Allocation graph shows a breakdown of the storage currently being used by your Barracuda Backup device. The total amount of
consumed storage is broken down into 6 possible data types:
System – The amount of storage consumed by the operating system, Barracuda Backup software, and associated databases
VMware – The amount of storage consumed by backed up VMware data sources
Agent – The amount of storage consumed by data sources backed up with a Barracuda Backup Agent
File Share – The amount of storage consumed by data sources backed up using the file sharing protocols CIFS and SSHFS
Message-Level – The amount of storage consumed by the Microsoft Exchange Message-Level backup
Received – The amount of storage consumed by data received from other Barracuda Backup devices (replication partners)
Figure 13. Storage Allocation Graph.

Current Tasks
Current Tasks shows you which core Barracuda Backup processes are currently running. The 5 processes are as follows:
Backup – Data is currently being backed up
Replication – Data is being replicated offsite to one or more locations or data is being received from one or more Barracuda Backup
devices
Purge – Data that is outside of retention is being removed from the device, freeing up disk space
Restore – Data is currently being restored
LiveBoot – A virtual machine has been booted either locally (LiveBoot) or in the cloud (Cloud LiveBoot)
Figure 14. Current Tasks.
Transfer Remaining
The Transfer Remaining graph shows you how much data is currently in queue and in the process of being sent offsite.
Figure 15. Transfer Remaining Graph.

Transfer Efficiency
The Transfer Efficiency graph shows you how much bandwidth is currently being used to send data offsite.
Figure 16. Transfer Efficiency Graph.

Status Page
This article refers to the firmware releases 6.1 through 6.3.04 only. If you are running firmware version 6.4 or higher, see Dashboar
d Page.
The multi-appliance dashboard displays irrespective of the firmware version running on the appliances.
The single appliance dashboard displays on appliances upgraded to firmware version 6.4; older firmware versions will
continue to display the existing Status page.
The Status page provides an overview of the performance and health of your Barracuda Backup and data sources.
Device Status and Status Indicators
Linked Barracuda Backup appliance status displays in the left pane. Click on an appliance in the left pane to view detailed health status for local
and offsite backups, agents, and data sources in the right pane of the web interface. Mouse-over an indicator in the right pane to see details.
Backup Appliance, Local Backup
Green light Indicates that your appliance is online and no errors were encountered as a result of your backup
Red light indicates a local appliance is offline or an error was generated during a backup
Mouse over Local Backup in the Status section in the right pane to view additional details:
If an error occurs, a link to the Reports page displays. Details may include whether:
Appliance is online and reporting or offline

An error was encountered
One or more data sources is offline
An error was reports by at least one data source
A hard drive issue was encountered
A memory issue was encountered
Replication
Green light indicates all replication targets are online and reporting including data replication period
Red light indicates replication target is offline or a data replication issues was encountered, for example, a bandwidth issue
Mouse-over Replication in the Status section in the right pane to view additional details:
For example, if a bandwidth issue is suspected, a link to the Rate Limit setup displays.
Data Sources
Green light indicates no issues reported by data source

Red light indicates an error was encountered on the Barracuda Backup appliance; click Backup Reports to view details or click the data
source name to go to the Backup > Sources page for the selected appliance and adjust the data source.
Backup Activity Section

These two graphs display backup activity for local locations and cloud storage, indicating the size and the number of backup items and data
added by date including the number of files and messages backed up. Click on a graph to view a larger display of the data.
Storage Efficiency Statistics
This section displays storage efficiency statistics:
Table 1. Storage Efficiency Statistics.
Table Value Description
Raw Data Total amount of data sent to Barracuda Backup including revisions.
Items Total items sent to Barracuda Backup.
Messages Total messages sent to Barracuda Backup.
Actual Storage The amount of actual storage space being used.
Snapshot The amount of space that would be required to back up your data
Equivalent based on your retention
policies projected over the next three years, without deduplication
and compression.
Deduplication The overall amount of space savings calculated by dividing raw data
Ratio by actual storage space.
Backup Displays performance statistics for the Barracuda Backup appliances,

Statistics including percentage of
CPU, Disk, and Ethernet usage. Performance statistics displayed in
red signify that the value
exceeds the normal threshold. These values fluctuate based on the
amount of data that is
being backed up, but if any setting remains consistently red for a long
period of time, contact
Barracuda Networks Technical Support.
Storage History
If you have one Barracuda Backup appliance selected in the left pane of the web interface, this table displays the Storage History for that
Barracuda Backup appliance. View current, historic, and actual data storage size on the local and cloud locations by date.

Table 2. Storage History.
For local storage, stored content displays in GB by:
Raw Historic Represents all content up to the current date that has been sent to
the Barracuda Backup.
Raw Current Represents current content sent to the Barracuda Backup before
deduplication processing.
Actual Storage Represents the total content currently stored on Barracuda Backup.
For cloud storage, stored content displays in GB by:
the Barracuda Backup.
Raw Current Represents current content sent to the Barracuda Backup before
deduplication processing.
Actual Storage Represents the total content currently stored on Barracuda Backup.
Plan Size Indicates total data storage based on your subscription plan size
Transfer History
If you have one Barracuda Backup appliance selected in the left pane of the web interface, this table displays efficiency of your data transfer to
the cloud and the size of the file parts yet to be transferred offsite, organized by date, for that Barracuda Backup appliance.
Site-to-Cloud
These graphs provide a detailed look at data replication from the appliance to the cloud including efficiency of your data transfer and the size of
the file parts yet to be transferred offsite, Ethernet usage for inbound and outbound traffic, and transfer efficiency:
Site-to-Site
These graphs provide a detailed look at data replication from the appliance to the replication target including Ethernet usage for inbound and
outbound traffic and transfer efficiency. Note that the Replication Target graphs display only if you have set up a data replication target.
Table 3. Transfer History.
Cloud Transfer Displays any content waiting to transfer to the Barracuda Cloud
Remaining Storage in bytes.

Cloud Bandwidth Represents all content up to the current date that has been sent to
Efficiency the Barracuda
Backup based on the maximum data transfer rate of your connection.
To limit Internet bandwidth consumption during peak usage times, set

rate limits
and schedule backups for non-peak hours.
Effective Bandwidth – Amount of bandwidth that would have

been required
without deduplication and compression.
Actual Bandwidth – Amount of bandwidth consumed to
replicate data to the
cloud.
Table 4. Replication Target Ethernet Usage and Transfer Efficiency.
Inbound Traffic Ethernet usage for inbound traffic.
Outbound Traffic Ethernet usage for outbound traffic.
Effective Bandwidth Amount of bandwidth that would have been required without
deduplication
and compression.
Actual Bandwidth Amount of bandwidth consumed to replicate data offsite.
Mobile Access
You can also view Barracuda Backup appliance status using Barracuda Networks Mobile Applications:
BCC iOS Mobile App for iPhone and iPod Touch

BCC Mobile App for iPad
Barracuda Networks Android Mobile Application

How to Monitor Backup Status

To check whether a Barracuda Backup appliance is operating correctly, click on the appliance name in the left pane, and click Dashboard.
The Dashboard page displays the following Barracuda Backup appliance statistics:
Current status of each data source configured on the appliance

Amount of storage currently being used by the appliance
Subscription status
System health including memory, disk, replication, and whether your firmware is up-to-date
Last five backup schedules that have run or are currently running
Storage allocation including system, VMware, Agent, file share, message-level, and data received from other appliances (replication
partners)
Core Barracuda backup processes currently running
Data currently in the queue and in the process of being sent offsite
Bandwidth currently being used to send data offsite
The Transfer Remaining section displays the amount of bytes remaining to be transferred. If there is a large amount of data (80 GB or
more),check the following, all available under the Backup tab:
Adjust the rate limit

Check the amount of data being backed up nightly to ensure the Barracuda Backup Server is doing transaction log backups for
Exchange and SQL
Check retention policies to ensure that too much historic data is not being transferred
To check the status of all your Barracuda Backup appliances at once, click Backup at the top of the left pane, and click the Dashboard page:
If you mouse over the various indicators, additional details display.

How to Unlink a Barracuda Backup Appliance

The articles in this section refer to Barracuda Backup Legacy Release firmware or newer. Use these steps to unlink a Barracuda
Backup appliance even if Local Control is enabled.
If you need to link a Barracuda Backup appliance to a different account, use the following steps to unlink the a
ppliance from the current account:
1. Enter the Barracuda Backup IP address to log in to the local web interface.
2. Go to the System > Device Information page, and in the Server Actions section, click Wipe Barracuda Backup Appliance:
3. The message Wipe Started Successfully displays in the web interface; a warning message displays:
4. Click OK to complete the unlinking process. Once the Barracuda Backup appliance is unlinked from the account, the Backup Server
Wipe Successful page displays, including the Serial Number and Linking Code.
5. Make note of the serial number and linking code. You can now link the Barracuda Backup appliance to a new account. For details, see H
ow to Link a Barracuda Backup Product as a User or Reseller.

Task Messages
The articles in this section refer to Barracuda Backup Legacy Release firmware or newer. Use these steps to view the Task
Manager even if Local Control is enabled.
Use the following steps to view running and queued tasks in the Barracuda Backup local web interface:
1. Open a web browser, and enter the Barracuda Backup Server IP address to log in to the Barracuda Backup local web interface.
2. Go to the System > Device Information page. In the Task Manager section, Running Tasks and Queued Tasks display:
3. Click Details to toggle additional information on or off.
Processes and Services
The following table describes the processes and services that display on the System page:
Backup Daemon responsible for performing backup functions.
Restore Daemon responsible for performing restore functions.
Netclient Process used to replicate data to another location.
Netserver Process that receives data from netclient for box-to-box replication.
Purger Deletes files that fall outside of the retention policy, and shares
removed from the configuration.

Backup Page
Use the Backup page to manage how data is backed up. From this page you can back up data locally then replicate the data offsite with
complete control over where data is stored. Barracuda Backup offers a full line of servers for local backup that can be configured to support
offsite replication to the cloud, private locations, or a combination of both.
Sources Page
Use this page to configure where data is backed up and in what manner:
Identify systems to be backed up

Select the type of data to be backed up
Specify where data is backed up
See Also
How to Configure Backups

Data Backup Tasks
Barracuda Backup Agent
Barracuda Linux Backup Agent
Replication Page
Configure backup data replication to one or more other Barracuda Backup appliances. From this page you can view:
Target List – Displays where data from the selected Barracuda Backup appliance is sent
Source List – Displays a list of devices sending data to the selected Barracuda Backup appliance
Rate Limits – Specify the data replication rate

See Also

Getting Started with Replication
Configuring a Replication Destination
How to Temporarily Disable a Destination
Managing the Data Queue
How to Configure Barracuda Backup
Setting Up Rate Limits
Rate Limits in Local Control
Schedules Page
Use this page to create backup schedules.
See Also

Backup Schedules
Exclusions Page
Create (optional) exclusion rules that use pattern matching to identify directory or file names you do not want to back up.
Files typically excluded from backups include temporary files, music, movies and other files which are not essential for business needs.
See Also
Backup Exclusions
Retention Policies
Specify how long to keep daily, weekly, monthly, and yearly backups by creating data retention policies.
Different retention policies can be created for different sets of data including files, data backed up by the Barracuda Backup Agent (Exchange,
SQL, System State), and email messages.
subset of the data.
See Also
Backup Retention Policies

Creating Effective Retention Policies

Understanding Source-Based Deduplication

Barracuda's source deduplication method deduplicates local data on the client-side, removing redundancies from the data before transmission,
and then sends that data to the Barracuda Backup appliance in deduplicated form, minimizing LAN bandwidth and data sent to the local server.
Source deduplication is implemented through the Barracuda Backup Agent. During agent installation, a small database is created on the server to
keep track of data chunks so only unique data is compressed and sent to the Barracuda Backup appliance for processing, reducing network
traffic and the backup window, as shown in Figure 1.
Figure 1. Source Deduplication.
For VMware backups, Barracuda leverages VMware’s vStorage APIs for Data Protection (VADP) to back up virtual disks, utilizing Changed Block
Tracking (CBT) to send only unique chunks to Barracuda Backup, as shown in Figure 2.
Figure 2. Changed Block Tracking.
With source deduplication, organizations running Microsoft Hyper-V also benefit from Barracuda Backup. The Barracuda Backup Agent reduces
the backup window by minimizing the amount of data sent to the Barracuda Backup appliance by deduplicating the VHD files on the host server.

Barracuda Agent
Use the Barracuda Backup Agent to back up open files, permissions (ACLs), and applications. The Agent uses source-based deduplication wher
e data is deduplicated at the source using a tracking database, and sent to the Barracuda Backup appliance in a compressed and deduplicated
form. Source-based deduplication significantly decreases backup windows while minimizing the amount of bandwidth consumed on the LAN and
data stored on the backup server. Note that data is not compressed when stored on the appliance.
For organizations using NFS (NAS or SAN), you can implement a Linux system that can run the Barracuda Linux Backup Agent. With the NFS
mounted on the Linux system, the Linux Agent is able to protect open files and ACLs while offering source-based deduplication for efficient
backups. Only unique data is sent to Barracuda Backup in a compressed and deduplicated state, reducing network bandwidth consumption and
backup times.
File Share Backup
Use File Share (CIFS) backup for data share on your server that are to be directly backed up, for example, Network Addressable Storage (NAS)
or Linux/UNIX data using SSHFS. With CIFS, the share is mounted and backed up from the Barracuda Backup Server. Note that file share
backups are unable to back up open or locked files.
Barracuda Backup is able to achieve fast and efficient backups, along with ACL protection, by combining the CIFS protocol with multi-threaded
backups and inline deduplication, without the need for additional hardware or complex NDMP accelerators. Barracuda’s multi-threaded backups
significantly reduce backup windows, while providing file-level protection. Inline deduplication ensures that only new or modified data is written to
disk, creating incremental backups that can be significantly faster than NDMP. This incremental-forever backup method also limits the amount of
local network traffic and storage needed. Backups can be performed quickly, during non-business hours, leaving otherwise open files, available
for backup.

Understanding Data Verification

Barracuda Backup has built-in inline data verification that performs multiple checks throughout the backup and replication processes to ensure
data is never corrupted or missing. Each block of data is assigned a unique hash identifier (digital fingerprint) using MD5 and SHA1 checksums.
Each hash identifier is stored in a database on the local appliance. As the backup runs, each calculated hash value is compared to block values
that have already been processed. If the value is unique, the block is stored on the appliance, as shown in Figure 1.
Figure 1. Data Verification.
For duplicate hash values, only a small pointer is sent to the appliance. This ensures that data is deduplicated before it is written to disk and that
the data integrity has been verified. If an inconsistent or corrupted block is found during the backup process, the job fails and a notification
displays in the backup report. This same data verification method is used when replicating to another Barracuda Backup appliance or to
Barracuda Cloud Storage. Each hash identifier is stored in a queue to be sent offsite. When the hash value is sent, it is compared to the content
already stored on the appliance or in the cloud. If a discrepancy occurs during the replication process, the block of data fails and a new part is
queued and replicated.

In this Section

VMware Backup
Related Articles

Backing Up The Barracuda Message Archiver Data Partition


Barracuda Backup supports the following data sources by version:

2010, 2013, 2016
Exchange Server 2016 Message-Level Support in Barracuda Backup firmware version 6.3.01 and higher.
2010 and 2013 in a Database Availability Group (DAG)

2008, 2008 R2, 2012, 2012 R2, and 2016
Microsoft does not support running Windows Server 2008/2008 R2 on Hyper-V Gen 2 virtual machines. Therefore,
Windows Server 2008/2008 R2 physical machines with UEFI cannot be restored to Hyper-V.
2003, 2007, 2010, 2013, 2016
2008, 2008 R2, 2012, 2012 R2, 2014, 2016
2005 SP1 or higher databases
2008, 2008 R2, 2012, 2012 R2, and 2016
Microsoft Small Business Server
2008 and 2011
Windows Client Operating Systems (OS)
Windows Vista, Windows 7, Windows 8, and Windows 10
VMware Backup
VMware ESX/ESXi 4.0 and higher
vCenter Server 4.0 or higher with vSphere
Mac OS X
SSHFS
Linux/Unix
SSHFS
Barracuda Backup Agent
NFS Mounts
Novell NetWare Server and GroupWise
Versions 8 and 2012


Each Barracuda Backup Server has a maximum number of simultaneous backups that can run across all connectors. Familiarize yourself with
this limit to assist when scheduling backups.
The following table lists the total simultaneous backups by connector and total across all connections:
Model Microsoft GroupWise File Share(3) Barracuda VMware Server( Total Across all
Exchange Server(2) Backup Agent(4) 5) Connections(6)
Server(1)
190 3 3 3 3 3 5
290 3 3 3 3 3 5
390 3 3 3 5 5 10
490 4 4 4 7 7 10
690 7 7 8 8 8 12
790 7 7 8 8 8 12
890 10 10 10 10 10 15
895 10 10 10 10 10 15
990 12 12 15 15 15 25
995 12 12 30 40 20 60
1090 12 12 30 40 20 60
Notes:
(1) Maximum number of Exchange connectors (message-Level only).
(2) Maximum number of GroupWise connectors (message-Level only).
(3) Maximum number of File Share connectors (non-Agent based backup, for example, CIFS/SMB/SSHFS).
(4) Maximum number of Barracuda Backup Agent connectors (data source).
(5) Maximum number of VMware connectors (data source).
(6) Total number of backup jobs across all connectors.

In this Section



This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010.
For details on setting up Microsoft Exchange Server 2013 message-level backup, refer to the article How to Set Up
Microsoft Exchange Server 2013 or Higher Message-Level Backup
Also see How to Add Conditional Forwarders when Setting up Message-Level Backup for Multiple Domains
Message-Level Backup
Message-level backup provides a quick way to restore single email messages to the original location or to an alternate mailbox.
Message-level backup is not intended to be a disaster recovery option for your Microsoft Exchange environment. The Barracuda
Backup Agent (Windows) allows you to back up the entire Exchange Information Store and should be used for disaster protection.
Requirements
You must complete these steps using the Client Access Server (CAS) role.
You must be running Microsoft Exchange Server 2010.
In addition, you must have the following:
Outlook Web Access (with WebDAV enabled)

Primary and Secondary DNS setting on the Barracuda Backup Server must be DNS servers which participate in Active Directory (AD)
Service account for access that has an Exchange mailbox and SMTP address
Barracuda Backup Server DNS Settings
For Exchange messagelevel backups to work properly, it is very important that DNS is set up correctly. DNS servers on the Barracuda Backup
Server must be DNS servers that participate in AD. The simplest way to determine which DNS servers to use is to use the IP addresses of your
AD Domain Controllers.
Step 1. Determine the Exchange Server Version and Build
Before setting up your Exchange Server, it is important to know what version, including the build number, is running to verify your Exchange
Server is running the minimum requirement for Exchange messagelevel backups. Locate the version and build number for your Exchange Server,
then refer to the Microsoft knowledgebase article Build numbers and release dates for Exchange Server to verify you are running the correct
version, and if applicable, service pack:
Exchange Server 2010 Version and Build
Use the following steps to determine the version number.
1. Open the Exchange System Manager on the Exchange Server, expand Server Configuration, and click Mailbox; the Exchange Server
version displays in the center pane:
2. Open the Microsoft knowledgebase article Build numbers and release dates for Exchange Server to determine the version the Exchange
Server is running.
3. Proceed to Step 2.
Step 2. Set Up Your Exchange Server
Use the following steps to set up your Exchange Server 2010 to do message-level backups.
1. Create an account to be used by Barracuda Backup to access emails in each mailbox:
Service Type Account

It is strongly recommended that you use a service type account and not your administrator account to prevent inherited deny

permissions from causing issues. This service account requires an Exchange mailbox and SMTP address and must be a
member of one of the Domain Users group; adding the service account to any administrative groups may cause issues with
access to user mailboxes.
2. To assign the service account impersonation rights for Exchange, open the Exchange Management Shell, and run the following
command, replacing <ServiceAccount> with the Service Account username:
New-ManagementRoleAssignment -Name:BarracudaBackup -Role:ApplicationImpersonation -User:<ServiceAccou
nt>
3. Depending on replication policies and Exchange Serer activity, it may be helpful to perform a group policy update on the Exchange
Server to help replicate permissions. To do so, run the following command from the command line:
gpupdate /force

4. Proceed to Step 3 to complete the set up.

Step 3. Add the Exchange Server to the Barracuda Backup Web Interface
Once you set up your Exchange installation to allow the Barracuda Backup Server to access it, use the following steps to add the Exchange
Server to the web interface:
1. Log in to Barracuda Backup, and go to on the Backup > Sources page.

2. Click Add a Computer; in the Add a Computer page, add the Exchange Server details:
Computer description – Enter a name to identify the server.
Computer name – Enter the fully qualified domain name (FQDN) or IP address of the Hyper-V Server.
Computer type – Select Microsoft Windows from the drop-down menu.
3. Click Save.
4. In the Add Data Source page, select Message-Level Backup (Exchange) as the Data Type. In the Message-Level Backup(Exchang
e) Information section, select Exchange Server 2010, and enter the server details.
Base DN Field
The Base DN field is optional; enter the Base Distinguished Name only if directed to do so by Barracuda Networks Technical
Support.
5. Click Test Exchange Connectivity to verify Barracuda Backup can connect to the Exchange Server using the entered login credentials.
6. In the Add to Schedule section, select the backup schedule to add the message-level backup to from the drop-down menu, or click Add
New to create a new schedule.
7. In the Barracuda Backup Appliances section, specify whether to replicate to another appliance.
8. Click Save at the top of the page.
9. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the message-level source to
back up all mailboxes, or select specific mailboxes.
10. Complete the backup schedule by selecting the days and start time for the backup, and click Save.

This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2013 or higher.
You must complete these steps using the Client Access Server (CAS) role. If you are setting up message-level backup for multiple
domains, also see How to Add Conditional Forwarders when Setting up Message-Level Backup for Multiple Domains.
Backup Agent allows you to back up the entire Exchange Information Store and should be used for disaster protection.
Step 1. Create an Account On the Exchange Server
Use the following steps to create an account to be used by Barracuda Backup:
Barracuda Networks recommends using a service-type account rather than an administrator account.
1. Log in to Exchange, click the down arrow next to the plus + symbol, and click User mailbox to create an account to be used by
Barracuda Backup to access the emails in each mailbox:
2. In the new user mailbox window, enter the required fields to create the new mailbox to be used by Barracuda Backup:
3. Click save. Open Active Directory Users and Computers, locate the new user created in the previous step, and open Properties:

3.
4. Click the Member Of tab, add the new user as a member of the Domain Users group, and remove any other groups listed here; this is
required:
5. Click Apply, and click OK to close the Properties dialog box.

Step 2. Assign Impersonation Rights to the Account
To assign the account impersonation rights for Exchange:
1. Open the Exchange Management Shell and run the following command, replacing <ServiceAccount> with the Service Account
username created in the previous section:

New-ManagementRoleAssignment -Name:BarracudaBackup -Role:ApplicationImpersonation -User: <ServiceAcco

unt>
2. Optional. It is good practice to perform a group policy update on the Exchange Server to replicate permissions. Run the following
command either using PowerShell or at a command line:
gpupdate /force
Step 3. Add the Exchange Server Data Source to Barracuda Backup
This section assumes you have configured an Agent backup for your Exchange Server. If you have not added the server to Barracuda Backup,
complete the steps in the article How to Back Up Microsoft Exchange Server 2013 and Higher before continuing.
1. Log in to the Barracuda Backup web interface, select the desired appliance in the left pane, and go to the BACKUP > Sources page.
2. Locate the previously configured Exchange (CAS) server, and click Add Data Source.
3. Enter the Data Source details:
a. Data Description – Enter a label to identify this data source.
b. Exchange Version – Select Exchange 2013 or Exchange 2016 from the drop-down menu.
c. Username / Password – Enter the username and associated password for the user created in Step 1. Create an Account On
the Exchange Server.
d. Windows Domain Name – Enter the domain for this Exchange Server.
e. Base DN (Optional) – If directed to do so by Barracuda Networks Technical Support, enter the LDAP Base Distinguished Name
of your Active Directory (AD), for example, DC=domain,DC=local
4. Click Test Exchange Connectivity to verify Barracuda Backup can connect to the Exchange Server using the entered login credentials.
5. In the Add to Schedule section, select the backup schedule to add the message-level backup to from the drop-down menu, or click Add
New to create a new schedule.
6. In the Barracuda Backup Appliances section, specify whether to replicate to another appliance.
8. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the message-level source to
back up all mailboxes, or select specific mailboxes.
9. Complete the backup schedule by selecting the days and start time for the backup, and click Save.

Backup Agent allows you to back up the entire Exchange Information Store and should be used for disaster protection.
You must create a conditional forwarder when configuring multiple domains for message-level backup.
Complete the following steps for each domain configured for message-level backup:
1. Log in to the original DNS server configured on the Barracuda Backup appliance, and open the DNS Manager.
2. Right-click Conditional Forwarder, and click New Conditional Forwarder:
3. The Edit Conditional Forwarder dialog box displays; enter the DNS Domain.
4. Click in the IP addresses of the master servers section, and enter the IP Address.
5. Select Store this conditional forwarder in Active Directory:
6. Click OK.
Refer to the following articles for additional configuration details:

How to Set Up Microsoft Exchange Server 2010 Message-Level Backup


This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010, 2013, and 2016
DAG.
Step 1. Install the Barracuda Backup Agent
Use the following steps to install the Barracuda Backup Agent (Windows) on all Exchange Servers configured in DAG:
1. Log in to Barracuda Backup web interface, and select the associated Barracuda Backup appliance in the left pane.
2. Go to the System > Software Downloads page.
3. Download and install the Barracuda Backup Agent (Windows) on all Exchange Servers configured in DAG.
Step 2. Set Up the Exchange Servers
Use the following steps to set up the Exchange Server backup on the Barracuda Backup appliance:
1. Log in to the Barracuda Backup web interface, and select the associated Barracuda Backup appliance in the left pane.
2. Go to the Backup > Sources page, and click Add a Computer to identify the system.
3. Enter the following Exchange Server details:
a. Computer description – Enter a name to identify the server on the Backup > Sources page.
b. Computer name – Enter the fully qualified domain name (FQDN) or IP address of the Hyper-V Server.
c. Computer type – Select Microsoft Windows from the drop-down menu.
4. Click Save. The Add Data Source page displays.
6. In the Agent Software section, click Test Software Connectivity to verify connection to the Backup Agent.
7. Select whether to replicate to Barracuda Cloud Storage.
8. Select whether to replicate data to another Barracuda Backup appliance.
9. Click Save.
10. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the data source to back up all
content, or click and expand the data source to granularly select specific sets of data to back up; note that you can configure multiple
schedules for each source, each with different sets of data.
12. Repeat for each Exchange Server configured in DAG.

This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010, 2013, and 2016
DAG.
This article assumes that you have the Barracuda Backup Agent (Windows) installed on the Exchange Server.
You must complete both Step 1 and Step 2 to back up the passive database.
Step 1. Configure the Barracuda Backup Agent
Use this section to configure the Barracuda Backup Agent (Windows) to detect passive databases.
1. Log in to the Exchange Server where the passive database to be backed up resides.
2. Go to Start > Administrative Tools > Services to open the Services console.
3. Right-click the Barracuda Backup Agent service, and click Stop:
4. On the Exchange Server, navigate to the Barracuda Backup Agent installation directory; the default location is C:\Program
Files\Barracuda\Barracuda Backup Agent\config:
5. Open the config folder, and open config.ini file with a text editor such as Notepad.
6. Add the following content beneath the configuration section:
[Windows Agent Manager.Microsoft Exchange Replication]

enableReplicationService=true
7. Save the file and close Notepad.

8. In the Services Console, right-click the Barracuda Backup Agent service, and click Start to restart the service:
Step 2. Configure the Data Source
Use this section to configure data sources on the Barracuda Backup appliance.
2. Go to the Backup > Schedules page, and click Add a Schedule.
3. Add a Schedule name, and click Select Specific Items. Navigate to and expand Microsoft Exchange Replication, and select the
passive database.
4. Click Save. The Exchange Server passive database is added as a data source.


This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2013 and higher.
Use the following steps to install the Barracuda Backup Agent (Windows) on the Exchange Server:
2. Go to the System > Software Downloads page.
3. Download and install the Barracuda Backup Agent (Windows) on the Exchange Server; you do not need to reboot.
Step 2. Set Up the Exchange Server
Use the following steps to set up an Exchange backup on the Barracuda Backup appliance:
2. Go to the Backup > Sources page, and click Add a Computer.
3. Enter the following backup source information:
c. Computer name – Enter the FQDN or IP ad dress; must be resolvable on your local network.
d. Computer type – Data source device type. Select Microsoft Windows.
e. For network file shares, select Enable File Share Backups, and enter your credentials.
Click Save.
6. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the Exchange Server data
source to back up all content, or click and expand the data source to select individual items for back up.
7. Click Save. The Exchange Server is added as a data source:

In this Section

Additional Resources
How to Convert and Replace a Barracuda Virtual Appliance VHD File with a VHDX Format File


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and supported versions of Microsoft
Hyper-V.
The Barracuda Backup Agent provides application-aware backups for Microsoft Hyper-V hypervisor-based virtualization systems and provides
support for open file backups, file attributes, and permissions, as well as automatic data source detection.
Hyper-V 2012 Management Console

Hyper-V 2012 Management Console tasks are disabled during backups.
Use the following steps to install the Barracuda Backup Agent (Windows) on the Hyper-V Server.
2. Go to the System > Software Downloads page, and download Barracuda Backup Agent (Windows).
3. Copy the Barracuda Backup Agent (Windows) to each Hyper-V server.
4. Double-click the Agent executable to launch the installer.
5. Follow the onscreen prompts to install the Agent.
Step 2. Set Up Online Backup
In the Hyper-V console, navigate to the Settings on each virtual machines (VMs), and under Integrations settings, select Backup (Volume
Snapshot); if you do not turn on this option, the default backup is set to Saved State which can cause issues during restoration.
An Online Backup backs up the VM by building an .avhd snapshot file by using the guests operating system (the VM) VSS writers to
read the files internally without having to pause the system. Conversely, a Saved State backup uses the host system (physical
machine) VSS writers only and pauses the guest system to build a backup.
The Saved State backup is not recommended as it temporarily stops the VM to back it up, which can cause issues when restoring
virtual SQL or Exchange environments from such a backup.
Step 4. Add the Hyper-V Server
Use the following steps to add Hyper-V Server data sources:
1. Once the agent is installed, select the Barracuda Backup appliance in the left pane, and on the Backup > Sources page, click Add a
Computer.
Enter the following details for the Hyper-V Server:
4. In the Add to Schedule section, select a schedule from the drop-down menu.
8. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the Hyper-V data source to
back up all content, or click and expand the data source to select individual items and/or VMs for back up.
9. Click Save.


Hyper-V. This article assumes Hyper-V is installed and configured.
The Barracuda Backup Agent provides application-aware backups for Microsoft Hyper-V hypervisor-based virtualization systems and provides
support for open file backups, file attributes, and permissions, as well as automatic data source detection.
CSV Utilization, Hyper-V 2008 R2 and Higher

Because of the Microsoft feature Redirected access, in cases where cluster shared volumes (CSVs) are being utilized, you must
stagger backup schedules, or schedule backups for each source/host at separate times. For more information, refer to the Microsoft
TechNet article Event ID 5136 - Cluster Shared Volume Functionality.
Use the following steps to install the Barracuda Backup Agent on the Hyper-V Server.
2. Go to the System > Software Downloads page, and download Barracuda Backup Agent (Windows).
3. Copy the Barracuda Backup Agent (Windows) to each Hyper-V server.
4. Double-click the Agent executable to launch the installer.
5. Follow the onscreen prompts to install the Agent.
Step 2. Set Up Online Backup
In the Hyper-V console, navigate to the Settings on each virtual machines (VMs), and under Integrations settings, select Backup (Volume
Snapshot); if you do not turn on this option, the default backup is set to Saved State which can cause issues during restoration.
An Online Backup backs up the VM by building an .avhd snapshot file by using the guests operating system (the VM) VSS writers to
read the files internally without having to pause the system. Conversely, a Saved State backup uses the host system (physical
machine) VSS writers only and pauses the guest system to build a backup.
The Saved State backup is not recommended as it temporarily stops the VM to back it up, which can cause issues when restoring
virtual SQL or Exchange environments from such a backup.
Step 3. Add the Hyper-V Server
Use the following steps to add Hyper-V server data sources:
1. Once the agent is installed, select the Barracuda Backup appliance in the left pane, and on the Backup > Sources page, click Add a
Computer.
2. Enter the following details for the Hyper-V Server:
4. In the Add to Schedule section, select a schedule from the drop-down menu.
7. Select whether to replicate data to another Barracuda Backup appliance. Click Save.
8. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the Hyper-V data source to
back up all content, or click and expand the data source to select individual items and/or VMs for back up.
Important
In cases where VMs have the potential of moving between hosts, you must:
Select the Hyper-V data source rather than individual items to select the entire host
Edit the Barracuda Agent config.ini file to exclude certainly virtual machines
9. Click Save.
10. Repeat steps 1 through 6 for each host in the cluster.

The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Microsoft Hyper-V 2008 and 2008
R2 hypervisor-based virtualization systems. This article assumes Hyper-V is installed and configured.
In some instances it may be necessary to exclude certain virtual machines from backup when implementing a clustered Hyper-V environment. To
do so, you must configure the Barracuda Backup Agent (Windows) to ignore those virtual machines you wish to exclude from backup.
Use the following instructions to edit the Barracuda Backup Agent on the Hyper-V Server:
1. On the Hyper-V Server where you installed the Barracuda Backup Agent (Windows), open Services.
2. Right-click on the Service Barracuda Backup Agent, and click Stop. The Service is now stopped.
3. Open the config.ini file in a text editor such as Notepad; the file is located in the following directory: /Program
Files/Barracuda/Barracuda Backup Agent/config/config.ini
4. Add the following lines to the end of the file:
ignorelist=VMname1,VMname2,VMname3
For example:
5. Save and close the file.

6. Open Services once again.
7. Right-click on the Service Barracuda Backup Agent, and click Start. The Status field should display as Started.


Hyper-V.
The following table describes the containers available on the Hyper-V administration console in the Selection pane:
Container Contents Description
Microsoft Hyper-V Initial Store When container is selected for backup, the
Hyper-V Virtual Machines (VMs) backup job includes the application,
configuration settings, and all VMs.
Initial Store Virtual Server application configuration When container is selected for backup, the
settings backup job includes a single XML file
containing the Hyper-V authorization
configuration.
Virtual Machines VMs When a single VM is selected, the backup is

a full image backup of the entire VM,
When a single VM is selected, the file including:
system displays in the results pane,
however, you cannot select individual files to VHD files
include/exclude from a backup: AVHD files
Differencing disks
Hyper-V managed snapshots

In this Section

How to Configure Availability Group Listener Source

The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server running the Ba
rracuda Backup Agent (Windows).
Add the SQL Server as a Data Source
Use the following steps to configure the SQL Server and data sources using the Barracuda Backup Agent (Windows):
1.Log in to Barracuda Backup, and select the associated Barracuda Backup appliance in the left pane.
2.Go to the System > Software Downloads page.
3.Download and install the Barracuda Backup Agent (Windows) on the SQL Server.
4.Go to the Backup > Sources page, and click Add a Computer to identify the system.
5.Enter the details for your SQL Server, and click Save.
6.In the Add Data Source page, click Test Software Connectivity to verify the Barracuda Backup appliance can connect to the Agent
installed on the SQL Server.
7. If the local system account is not a member of the SysAdmin role in SQL, select Microsoft SQL Server Requires Authentication, and
enter the associated credentials.
11. Click Save.
content, or click and expand the data source to granularly select specific sets of data to back up.
14. Click Save. The SQL Server is added as a data source.
Backup Schedules
Create backup schedules for selection when adding a data source using the following steps:
2. Go to the Backup > Schedules page. Click Add a Schedule and fill in the information on the Add Backup Schedule page:
Items to Back Up – Turn on Apply to All Computers and Data Sources for this Barracuda Backup Server to back up
all content, or turn this option off to expand and select individual items for backup.
Schedule Timeline – Turn on the days on which the back up is to run.
Daily Backup Timeline – Enter the start time; turn on Repeat if you wish to specify a time period and end date to repeat the
backup.
3. If the backup schedule is for Microsoft SQL or Microsoft Exchange, you must specify the type of backup to run:
Smart – This backup type is a combination of the full backup and the transaction log backup, minimizing the impact of
backups on network resources necessary to transfer data off site. Barracuda Networks recommends this backup type for
SQL and Exchange servers.
With the Smart Backup type, threshold values are used to determine when to switch between full and log backups. The
minimum threshold value specifies how many days Barracuda Backup continues to back up transaction logs before another
full backup is run. After the minimum threshold value is met, Barracuda Backup determines whether to perform another
backup based on the binary data queue. If the binary data queue size exceeds 1 GB, Barracuda Backup continues the
transaction log backup until the maximum threshold level is met, or the queue size drops below 1 GB.
Backup Rate Limit (Optional)
Your initial offsite backup may take on the order of days to complete but all of the data is backed up locally on the Barracuda Backup Server
The length of transfer time it will take to get your data offsite is impacted by the compression and de-duplication rates on your data, the uplink
For details, see:
How to Set Rate Limits

How to Set an Alternate Rate Limit (Local Control)
Data Retention Policies

including files, data backed up by the Barracuda Backup Agent (Exchange, SQL, System State), and email messages.
You can create one policy for all of the computers and data sources on a Barracuda Backup Server or multiple policies that each include some
subset of the data.

1. Log in to the Barracuda Backup web interface, and select the associated Barracuda Backup Server in the left pane.
4. Click Save.
When data is removed according to a retention policy, it is deleted from both the local Barracuda Backup Server and the offsite storage
Backup Reports
View reports on an ongoing basis as needed. The Reports > Backup page contains detailed backup reports. A list of in-progress backups
you want to view, or click Download to save the file to your local system as a .csv file.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server 2012 and higher
databases.
For Microsoft SQL Server 2012 and higher, the Barracuda Backup Agent leverages Microsoft VSS. With Microsoft VSS, Barracuda Backup
performs full and differential database backups. You can also configure the Barracuda Backup Agent to use Microsoft VDI which provides the
ability to perform full and incremental backups. To enable Microsoft VDI for use with SQL Server 2012 and higher databases, edit the Agent's
configuration file.
Backup Recommendations
Barracuda recommends the following backup configurations for all versions of Microsoft SQL Server.
Simple Recovery Model
If the Microsoft SQL Server databases in your environment are configured to use the simple recovery model, Barracuda recommends configuring
the Barracuda Backup Agent to use Microsoft VSS. Using Microsoft VSS in conjunction with the simple recovery model allows you to perform full
and differential backups while benefiting from Barracuda’s source-based deduplication.
Full Recovery Model
If the Microsoft SQL Server databases in your environment are configured to use the full recovery model, Barracuda recommends configuring the
Barracuda Backup Agent to use Microsoft VDI. Using Microsoft VDI in conjunction with the full recovery model allows you to perform full and
incremental backups while allowing you to perform point-in-time restores. For details on modifying the Barracuda Backup Agent configuration file
to enable Microsoft VDI backups, refer to How to Enable VDI Incremental Backups for Microsoft SQL Server.
Barracuda supports SQL Server backup via VSS or VDI, however, you cannot combine these two solutions.


This article refers to version 6.3 or higher, and Microsoft SQL Server 2012 and 2012 R2 databases.
In Barracuda Backup versions prior to 5.4, the Barracuda Backup Agent utilized the Microsoft SQL Server Virtual Device Interface (VDI)
to implement SQL database backup and restore operations. The VDI technology provides the ability to backup and restore full and
incremental backups of the SQL databases and is enabled by default on the Barracuda Backup Agent. In version 5.4 and higher, the
Barracuda Backup Agent can leverage VSS for other versions of Microsoft SQL Server. With Microsoft VSS, Barracuda Backup is able
to perform full and differential database backups. However, you can enable the Barracuda Agent to use the former Microsoft SQL
Server object to back up SQL Server 2012 and later databases.
Requirements
Verify the following is true on the Microsoft SQL Server:
Barracuda Backup Agent is installed, and

The SQL Server has been added as a Barracuda Backup data source.
Edit the Barracuda Backup Agent
Use the following instructions to edit the Barracuda Backup Agent installed on the SQL Server to use the former Microsoft SQL Server object:
1. On the Microsoft SQL Server where the Barracuda Backup Agent is installed, open the Services console.
3. Open the config.ini file in Notepad as an administrator; the default file location is C:/Program Files/Barracuda/Barracuda Backup
Agent/config/config.ini
4. Set vssSqlVersion=20 under the configuration section in the file. For example:
[installControl]
buildNumber=89742
installedVersion=6.3.00-dbg
[configuration]
nodeGuid={00001001-B0C179DB-B0C179DB-B0C179DC}
vssSqlVersion=20

8. Once the service is restarted, go to the data source schedule.
9. Select the parent object that includes the new container for SQL, or, if you are not backing up the entire parent object, clear Microsoft
SQL and select Microsoft SQL server:

VDI is now enabled to implement incremental SQL database backup and truncate log files.

How to Configure Availability Group Listener Source
The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server 2012 and
higher.
Barracuda Recommendations
Use an availability group listener as the source for all SQL availability group database backups;
Set up a backup source that uses the FQDN or IP Address of the availability group listener; and
Use VDI on all servers in the availability group for log truncation; for VDI configuration details, refer to How to Enable VDI
Incremental Backups for Microsoft SQL Server.
Availability Group Roles
Availability group servers, referred to as replicas, have one of two roles: primary or secondary. When using an availability group listener as a
backup source, the Barracuda Backup appliance always performs a database backup on the primary regardless of the intended backup server
specified in the availability group settings.
Configure SQL Server Hosting AlwaysOn
Use the following steps to configure a SQL server hosting AlwaysOn:
1. Log in to Barracuda Backup, and select the associated Barracuda Backup Server in the left pane.
2. Go to the BACKUP > Sources page and add the SQL Server source using the availability group listener FQDN or IP address.
Select only databases that are in the availability group, do not choose system state or file system:
Configure Replicas
It is important to set up individual sources for each replica. The databases presented to the Barracuda Backup appliance post-failure will not be
the same as the ones presented pre-failover because the Availability Group Listener presents databases from the primary server only. Setting up
individual sources on each replica allows all non-availability group databases to be backed up regardless of the role of the replica. Additionally,
since availability groups only allow COPY_ONLY and transaction log backups on a secondary replica, attempting to run a backup with the Barrac
uda Backup appliance, which only supports non-COPY_ONLY full backups, will result in a backup error.
1. Log in to Barracuda Backup, and select the associated Barracuda Backup Server in the left pane.
2. Go to the BACKUP > Sources page and add an additional backup source for each replica in the group using the FQDN or IP address of
that replica.
Select only databases that are not in the availability group, including system databases. Use these sources to back up system
state and file system, if needed:


VMware Backup
In this Section

How to Configure a VMware Data Source


Barracuda Networks supports Barracuda Backup customers irrespective of whether they are protecting VMware environments. Barracuda
Networks supports operating systems, not specific hardware configurations. VMware operates as a hardware abstraction layer.
VMware supports a set of certified operating systems and hardware, and the customer and VMware are responsible for any interactions or issues
that arise at the hardware or operating system layer as a result of the customer’s use of VMware.
Barracuda Networks does not require customers to recreate and troubleshoot every issue in a non-VMware environment, however, Barracuda
Networks does reserve the right to request customers to diagnose certain issues in a native-certified operating system environment, operating
without the virtual environment. Barracuda Networks will only make this request when there is reason to believe that the virtual environment is a
contributing factor to the issue.
Any time spent on investigation of problems that may, in the sole opinion of Barracuda Networks, be related to VMware, will be handled in the
following fashion:
1. If a problem is encountered backing up a VMware environment, the customer may be required to recreate the problem on a non-VMware
server, at which time Barracuda Networks will provide regular support.
2. Regardless of the problem type or source, if the problem is determined to be a non-VMware related issue, time spent on investigation
and resolution will be covered as part of regular maintenance, and support will be provided as usual.
Please note that Barracuda Networks only provides technical support to customers who maintain the requisite subscription/s.

The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and VMware EXSi 5.0 and higher.
In order for the Barracuda Backup appliance to access VMware servers, you must open the following ports:
Table 1. Data Recovery.
Port Details
902 TCP Data Recovery Appliance ESX Host VDR to ESX

Communication
22024 TCP Data Recovery vSphere Client Plug-in Data Recovery Appliance
Data Recovery Management
Table 2. Ports Related to Non-Data Recovery Features.
Port Details
22 TCP User VDP ssh (for debugging)
53 UDP VDP DNS server DNS
80 TCP User VDP http
111 TCP, UDP VDP ESXi/ESX rpcbind
443 TCP User VDP https
700 TCP VDP, LDAP Active Directory Loginmgr tool
7778 TCP vCenter VDP VDP, RMI
7779 TCP vCenter VDP VDP, RMI
8509 TCP vCenter VDP Tomcat AJP Connector
8543 TCP User VDP Redirect for Tomcat
8580 TCP vCenter VDP VDP Downloader
9443 TCP vCenter VDP VDP Web Services
27000 TCP VDP vCenter Licensing communication


This article refers to Barracuda Backup Legacy Release firmware or newer and VMware 4.1 and higher with the VMware license
which includes access to vSphere Data Recovery API.
See also: How to Configure a VMware Data Source
ESXi600-201511001 (2137545).
Barracuda Backup utilizes the vSphere Data Recovery API to back up and restore the virtual machine's configuration and disks, providing a
comprehensive disaster recovery option. Virtual machines can be recovered to any VMware host accessible by the Barracuda Backup appliance.
Windows Dynamic Disk partitions are not supported by Barracuda LiveBrowse. If you need to restore individual files from a Windows
Dynamic Disk partition, Barracuda recommends using the Barracuda Backup Agent to protect that data.
Best Practices
To prevent errors and warnings, and to improve performance when setting up a VMware backup:
Ensure the datastore has sufficient space;

Enable changed block tracking; and
Uninstall any third-party backup agents.
Parallel VMware Backup
You can back up multiple guests on the same host concurrently. The following table lists the default number of guest machines that you can back
up simultaneously during a VMware backup by device:
Barracuda Backup Default Number of

Device Number Guest Machines
190 3
290 3
390 5
490 7
690 8
790 8
890 10
895 10
990 15
995 20
1090 20
Changed Block Tracking
You can enable Changed Block Tracking (CBT) to avoid warning messages when setting up a VMware backup. When enabled, CBT displays in
the data source list:

Configure the Data Source
Use the following steps to add a computer and configure the data source through Barracuda Backup:
1. Log in to Barracuda Backup as the administrator, and go to the Backups > Sources page.
2. Click Add Computer, and complete the details for the data source:
Enable Backups – Turn on to enable backups for the VMware host; this option is turned on by default
Computer Description – Enter a name to identify the host (for example, ESX, ESXi, vCenter) field
Computer Name – Enter the name or IP address of the VMware host on the network
Computer Type – Select VMware from the drop-down menu
Username/Password – Enter the credentials to access the VMware host
3. Click Test Credentials to verify the Barracuda Backup appliance can communicate with the VMware host.
4. Click Save to save the configuration for the new data source; the VMware host data source is detected and added automatically.
5. The Add Data Source page displays.
6. In the Add to Schedule section, select a schedule from the drop-down menu, or click Add New to create a new schedule.
7. Select whether to back up to Barracuda Cloud Storage.
8. Select whether to enable changed block tracking.
10. Click Save.
11. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the VMware data source to
back up all data recognized by the VMware host, or click and expand the data source to view the virtual machines available for backup
on the VMware host; turn on those virtual machines you want to back up.
12. Click Save to save the configuration for the data source.
The VMware data source displays in the Data Sources page.


This article refers to Barracuda Backup version 6.3 and higher, and VMware ESX/ESXi host machines, or vCenter Server version
4.0 or higher with vSphere (except where noted).
ESXi600-201511001 (2137545).
ESX/ESXi Host Machine Permissions
At a minimum, you must have the following permissions assigned to the user role on an ESX/ESXi virtual machine:
Table 1. ESX/ESXi User Role Permissions.
System Configuration Disk Change Tracking
Virtual Machine Provisioning Allow read-only disk access

Allow virtual machine download
Virtual Machine Snapshot Management Create snapshot

Remove snapshot
Global DisableMethods
EnableMethods
Licenses
If you are using SCSI hot-adding on an ESX/ESXi virtual machine, the user role must have the following
permissions:
All of the permissions listed in Table 1, and

The Barracuda Backup must have all of the permissions listed in Table 2
Table 2. Barracuda Backup Minimum Permissions.
System Configuration Permissions
Datastore Allocate space
Virtual Machine Configuration Add existing disk
Add new disk
Add or remove device
Change resource
Remove disk
Settings
vCenter Server Role for Backup and Recovery
If you wish to assign privileges to a vCenter Server user or a user in Active Directory (AD), you can create a new user with the VMware vCenter
roles.
The recovery operation requires privileges for operations on hosts, networks, and datastores. You must apply this new role to the
Datacenter object or higher in the VMware vCenter Server hierarchy for the user specified in the VMcuser option and Propagate to
Child Object must be turned on when adding the permission.
To create a vCenter Server role for backup and recovery operations, log in to the vCenter Server using the vSphere
Client, and add the permissions listed in Table 3:
Table 3. vCenter Server Role Permissions.

Location Configuration Permissions
Datastore Allocate space

Browse datastore
Low-level file operations
Global Licenses
Guest Operations(1,2) Guest Operation Modifications

Guest Operation Program Execution
Guest Operation Queries
Network Assign network
Resource Assign virtual machine to
vApp Add virtual machine

Assign resource pool
Create
Virtual Machine Configuration Add existing/new disk

Add/remove device
Advanced
Change CPU count
Change resource
Disk change tracking
Disk Lease
Host USB device
Memory
Modify device setting
Raw device
Reload from path(4)
Remove disk
Rename
Reset guest information
Settings
Swapfile placement
Upgrade virtual hardware
Virtual Machine Inventory Create new

Register
Remove
Unregister
Virtual Machine Provisioning Allow disk access

Allow read-only disk access
Virtual Machine(2) Snapshot Management(2) > State(2) Create snapshot

Remove snapshot
Revert to snapshot
Virtual Machine(3) State(3) Create snapshot

Remove snapshot
Revert to snapshot
Notes:
(1)Guest Operations permissions are necessary only if you are using Data Protection for VMware to protect Microsoft Exchange Server or
Microsoft SQL Server applications running inside a virtual machine guest.
(2) vSphere 5.0 only.
(4) vCenter Server 4.1 only.
vCenter Server Role for Scheduled Backup Operations Permissions
To add a vCenter Server role for backup operations only, add a role using the vSphere Client, and add the permissions listed in Table 4.
You must apply this new role to the target host (ESX/ESXi) object or higher in the VMware vCenter Server hierarchy for the user

specified in the VMcuser option, and Propagate to Child Object must be turned on when adding the permission.
Table 4. vCenter Server Role for Backup Operations Permissions.
Location Configuration Permissions
Global Licenses
Guest Operations(1)(2) Guest Operation Modifications

Guest Operation Program Execution
Guest Operation Queries
Virtual Machine Configuration Disk change tracking

Disk Lease
Virtual Machine Provisioning Allow read-only disk access

Virtual Machine(2) Snapshot Management(2) > State(2) Create snapshot

Remove snapshot
Virtual Machine(3) State(3) Create snapshot

Remove snapshot
Notes:
(1)
Guest Operations permissions are necessary only if you are using Data Protection for VMware to protect Microsoft Exchange Server or
Microsoft SQL Server applications running inside a virtual machine guest.
Barracuda Backup Set Up and Restore Permissions
To set up and restore a VMware virtual machine as a data source in the Barracuda Backup web interface, you must have administrator privileges
to the virtual machine. Once your credentials are verified and the data source is set up and backups are enabled, use the Restore page to
restore a virtual machine. For more information on this VMware requirement, refer to the VMware Data Recovery Administration Guide available
on the VMware website.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and VMware ESXi.
If you are clustering virtual and physical devices together for high availability (HA), you can use Raw Device Mapping (RDM) which allows for
both physical and virtual system compatibility. If you are clustering only virtual systems together for high availability, VMware recommends using
vStorage Virtual Machine File System (VMFS).
In RDM, a VMFS volume contains a special device mapping file that contains unique metadata that maps to a mapped device. Using this
one-to-one mapping, the VMFS file system can resolve each mapped device, managing and redirecting disk access to the physical device. The
RDM is linked from the VM configuration to the file and contains a reference to a logical disk volume. This allows the logical unit numbers (LUNs)
to appear as files in the VMFS volume because they are attached to a specific virtual machine (VM) rather than formatted for the entire cluster.
RDM Size
If the VMDK file size is larger than the maximum size of the VMDK datastore that contains the VM configuration file, the VM snapshot
will fail.
Protecting Physical RDM Devices

Because a physical RDM is not part of the virtual environment, VM snapshots are unavailable through VMware's VDAP tools. Instead, Barracuda
Backup recommends using the Barracuda Backup Agent to snapshot the VM and the corresponding physical device.
Protecting Virtual RDM Devices
Barracuda protects virtual RDM devices through the VMware's VDAP api, allowing virtual disk snapshots. VMware detects virtual RDMs as virtual
guest systems, hiding the real characteristics. Virtual RDM devices can be backed up in the following ways:
Leverage the Barracuda Agent to back up the system as a physical machine; or

Back up the system through Barracuda's VMware backup options.

Barracuda has encountered cases where VMware virtual machines using the default e1000e (Intel 82574L) network driver have
experienced intermittent agent backup errors as well as performance-related issues. Following VMware’s best practices, Barracuda
recommends changing the network driver to the VMXNET3 driver for better performance and reliability.
For additional information, refer to the following VMware articles:
Performance Best Practices for VMware vSphere 4.1

Choosing a network adapter for your virtual machine
Possible data corruption after a Windows 2012 virtual machine network transfer
Change Network Adapter
Use the following steps to change the network adapter:
Before adding the new network adapter you may want to uninstall the existing one within the Windows Device Manager to prevent an
IP address conflict. For more information, see the VMware knowledgebase solution Networking Error: IP address already assigned to
another adapter.
1. Connect to the host or vCenter Server using the vSphere Client.

2. Right-click the virtual machine, and then click Edit Settings.
3. Select the network adapter, click Remove, and then click OK.
4. Right-click the virtual machine, and then click Edit settings.
5. Click Add > Ethernet Adapter, and then click Next.
6. From the Adapter Type drop-down menu, select VMXNET3:
7. If applicable for your environment, select the appropriate Network Connection.

8. In Device Status, turn on Connect At Power On, and then click Next.
9. Review the settings, click Finish, and then click OK.

ESXi600-201511001 (2137545).
You can set retention policies for individual VMware virtual machines (VMs) as well as individual folders within File Share (CIFS and SSHFS)
backups using the following steps:
1. Log in to the Barracuda Backup web interface, and go to the Backup > Retention Policies page.
2. Click Add a retention policy to create a new policy.
3. Enter a Policy Name.
4. In the Items to Retain section, expand the source and select the specific VMs or folders to which to apply the policy:
5. Enter the Retention Timeline details, and then click Save.
Alternatively, you can edit an existing policy:
1. Log in to the Barracuda Backup web interface, and go to the BACKUP > Retention Policies page.
2. Click the Edit ( ) icon to modify an existing policy.
3. In the Items to Retain section, expand the source and select the specific VMs or folders to which to apply the policy:

4. Make any additional changes necessary, and then click Save.

How to Configure a VMware Data Source

This article refers to Barracuda Backup Legacy Release firmware or newer and VMware 4.0 and higher with the VMware license
which includes access to vSphere Data Recovery API.
Barracuda Backup utilizes the vSphere Data Recovery API to back up and restore the virtual machine's (VM) configuration and disks, providing a
comprehensive disaster recovery option. VMs can be recovered to any VMware host accessible by the Barracuda Backup Server.
Best Practices
To prevent errors and warnings, and to improve performance when setting up a VMware backup:
Ensure the datastore has sufficient space;

Enable changed block tracking; and
Uninstall any third-party backup agents.
Parallel VMware Backup
You can back up multiple guests on the same host concurrently. The following table lists the default number of guest machines that you can back
up simultaneously during a VMware backup by device:
Barracuda Backup Default Number of

Device Number Guest Machines
190 3
390 5
490 7
690 8
890 10
990 15
995 20
1090 20
Changed Block Tracking
You can enable Changed Block Tracking (CBT) to avoid warning messages when setting up a VMware backup. When enabled, CBT displays in
the data source list on the Backup > Schedules page:
Configure the Data Source
Use the following steps to add a computer and configure the data source through Barracuda Backup:
1. Log in to Barracuda Backup at login.barracuda.com.

2. Go to the Backup > Sources page.
3. Click Add a Computer. In the Computer Information section, enter the data source details:
Computer description – Enter a name to identify the host (for example, ESX, ESXi, vCenter) field

Computer name – Enter the name or IP address of the VMware host on the network
Computer type – Select VMware from the drop-down menu
4. In the VMware Computer Information section, enter the login credentials to access the VMware host, click Test Credentials to verify
the Barracuda Backup appliance can communicate with the VMware host, and then click Save:
5. In the Add Data Source page, click Test Credentials to once again verify the Barracuda Backup appliance can communicate with
the VMware host:
6. In the Add to Schedule section, you can apply multiple schedules to the same source. From the Schedule drop-down menu, select an e
xisting schedule to apply to the VMware source, or select Add New:
7.
8. If you select Add New, the Add New Schedule window displays. Enter the new Schedule Name, and then click OK:
9. New and selected schedules display in the Add to Schedule section:

10. Configure the remaining options:

Replicate to Barracuda Cloud Storage – When selected, data is replicated to Barracuda Cloud Storage.
Enable CBT – When selected, if CBT is not enabled on the VMware host, Barracuda Backup attempts to enable it. If CBT is
already enabled, this option has no effect.
Quiesce Only – When selected, Barracuda Backup does not attempt to retry failed quiesced snapshots as non-quiesced
snapshots.
Replicate to Other Barracuda Backup Appliances – When selected, you can replicate data to another Barracuda Backup
Appliance.
11. Once you have configured schedules and the backup and replication options, click Save.
12. Go to the selected schedule on the Backup > Schedules page.
13. In the Items to Back Up section, click the arrows to drill down into your VMware source. Select the VMs you want to back up under the
selected schedule:
If you want to break up the VMware backup into multiple schedules, select only the VMs you want to back up using the current
schedule, and then click Save. You can then create a new schedule and select the remaining VMs.
14. Once you select the VMs for backup, select the days that this schedule is to run in the Schedule Timeline section:

15. In the Daily Backup Timeline section, enter a Start Time:
16. If you want to have your backup schedule repeat throughout a 24-hour period, turn on Repeat:
Because this is a VMware data source, skip the SQL/Exchange Backup section.
17. Click Save.
Your newly created backup schedule displays in the Schedules page including the configured options:
Click Edit to modify the schedule, Remove to delete the schedule, and Run Backup Now to start the backup job immediately.
To view how much data was last backed up, go to the BACKUP > Sources page, and toggle the VMware source ON or OFF. A green
indicator signifies that the last backup was successful, while a red indicator means that the last backup encountered issues:
For details on issues encountered during backup, refer to the Reports page.


This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Active Directory (AD).
Barracuda Networks recommends enabling Active Directory Recycle Bin before backing up content. Refer to the Microsoft TechNet
article Enable Active Directory Recycle Bin for details.
Important
Before attempting to recover a domain controller, first review the Microsoft TechNet article Domain Controller Recovery for a complete
list of recommendations.
Backing up the AD is done on one or more Active Directory Domain Controllers, and is performed by backing up the System State on those
servers. Barracuda Backup utilizes the Barracuda Backup Agent (Windows) to back up and restore the Microsoft Windows System State. Back
up the System State to have a backup of critical system-related components.
The System State backup contains the following:
Local Registry
COM+ Class Registration Database
System Boot Files
Active Directory Database File (NTDS.DIT) for Domain Controllers
SYSVOL folder
A System State backup allows you to recover to a known "good" system state after a hardware or software crash.
Use the following steps to add a computer and configure the data source on Barracuda Backup:
2. Go to the Backup > Sources page, and click Add Computer, and complete the details for the data source:
a. Enable backups – Turn on to enable backups for the VMware host; this option is turned on by default
b. Computer description – Enter a name to identify the host (for example, ESX, ESXi, vCenter) field
c. Computer name – Enter the name or IP address of the VMware host on the network
d. Computer Type – Select Microsoft Windwos from the drop-down menu
3. Click Save.
8. Turn on Replicate to Other Barracuda Backup Servers, and click Save.
9. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the data source to back up, or
click and expand the data source to select individual items for backup.
System State must be selected to restore AD.
10. Click Save.

11. Once configured, define a policy for how long to retain the data on the Backup > Retention Policies page.
Tombstone Lifetime
To ensure a good backup you should be aware of the tombstone lifetime. The tombstone lifetime is the number of days before a
deleted object is removed from the directory services. A backup that is older than the tombstone lifetime (the default is 60 days) set in
Active Directory is not a good backup. At a minimum, perform at least two backups within the tombstone lifetime. Active Directory
incorporates the tombstone lifetime into the backup and restore process as a means of protecting itself from inconsistent data.


This article refers to Barracuda Backup version 6.3 and higher, Barracuda Backup Agent version 6.3 and higher, and MySQL™.
You can back up MySQL databases using a pre-execute script and the Barracuda Backup Agent.
Create a Batch File
Use the following steps to create a batch file to dump a MySQL database to a file prior to running a backup.
1. Verify the Barracuda Backup Agent is installed on all systems to be backed up.
2. Open a text editor, for example Notepad, and type the following lines:
cd\
cd "Program Files (x86)\MySQL\MySQL Server 5.6\bin"
mysql -u root -p -c -B mysqldump.exe sakila > c:\temp\test.sql
Replace root with the account with privileges to the database, replace sakila with the database name, and replace c:\tem
p\test.sql with the directory and file name of the location where you want to dump the database.
3. Save the text file as a batch (.bat) file:
Pre-Execute your Batch File
Use the following steps to modify the config.ini file to pre-execute your batch file prior to running a backup.
1. Navigate to and open the config.ini file in a text editor, located in the C:\Progarm Files\Barracuda\Barracuda Backup Agent\config di
rectory.
2. Enter the following lines below the configuration section:
#Batch file to backup mysql database

preExecuteScript=c:\mysqlbk.bat
Replace c:\mysqlbk.bat with the location and your batch file name.
3. Save the file.
Configure Your Backup Source
2. Go to the Backup > Sources page, and click Add a Computer to identify the system.
3. Enter the following details:
a. Computer Description – Enter a description to identify this system
b. Computer Name – Enter the fully qualified domain name (FQDN) or IP address
c. Computer Type – Select Microsoft Windows from the drop-down menu:
4. Click Save.
If you select specific items for backup, verify the location of your MySQL dump file is selected.
7. Select whether to back up to Barracuda Cloud Storage.
9. Click Save.
10.

data, or click and expand the data source to select individual items for backup.
11. Click Save.


The Barracuda Backup Agent does not support IBM® Domino® or IBM Notes®, however, the Barracuda Backup Agent (Windows)
protects IBM Domino databases on a Microsoft® Windows® 2008 platform using File System backup. Barracuda Backup does not
support IBM Domino transaction logging.
An IBM Domino server is a collection of databases using a flat file structure. A review of the database files in an IBM Domino environment reveals
that each user has a unique database for email, and that they may share application databases. This can result in hundreds or even thousands of
smaller, unique database files in the IBM Notes /data directory. In comparison, an Exchange deployment has relatively few databases supporting
an entire organization.
IBM Domino Server Databases
IBM Domino databases are accessed using IBM Notes clients. Within the database file there can be data, design elements, and programming
code, and each database file has its own security in the form of an Access Control List (ACL). A IBM Domino database has a file extension of .ns
f.
IBM Domino Server Backup
A complete backup of an IBM Domino Server includes:
1. IBM Domino Server data files

2. All databases
3. Template files
4. Notes.ini file
5. ID files
Before you begin a backup, verify the following files are open and running on the IBM Domino Server:
Logs.nsf
names.nsf
mail.box
Server ID file
Windows Volume Shadow Copy Service
Through the use of the Windows Volume Shadow Copy Service (VSS), the Barracuda Backup Service can consistently capture the open
database files. Using VSS, the Barracuda Backup Service can perform both full and incremental backups of the IBM Domino server. Because the
data may be made up of many small database files that can change daily, the incremental/differential backup can be very close to the master
database in size. Due to the manner in which IBM Domino writes the changes to the end of the files, a large amount of deduplication occurs on
these backups.
When using the VSS backup method, it is recommended that you execute the following two commands prior to the backup:
nserver -c "drop all"

nserver -c "dbcache flush"
This releases all open sessions and closes most open files. See How to Create a Pre- or Post-Agent Backup Command Batch File or Script if you
wish to create a pre-backup command batch file.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer. This articles applies to the Barracuda
Backup Agent (Windows) and Barracuda Backup Agent (Linux).
Barracuda Backup Agent Running on a Microsoft Windows System
You can run a pre- or post-Agent backup command batch file by editing the config.ini file. This enables you to stop and start certain
processes on the host computer where the Barracuda Backup Agent (Windows) is installed. This can allow you to stop conflicting processes
during the time that the Agent is backing up files.
Stop a Process
To automatically stop a specific process before starting the backup job, you can specify the batch file to stop the service.
1. Navigate to the config.ini file on the server in the following location:

C:\Program Files\Barracuda\Barracuda Backup Agent\config\
2. Open the config.ini file in a text editor, and in the [ configuration ] section, add the following lines:
# the batch file to stop the process
preExecuteScript=c:\stop.bat
Start a Process
To automatically start a specific process after completing the backup job, you can specify the batch file to start the service.
1. Navigate to the config.ini file on the server in the following location:

C:\Program Files\Barracuda\Barracuda Backup Agent\config\
2. Open the config.ini file in a text editor, and in the [ configuration ] section, add the following lines:
# the batch file to start the process
postExecuteScript=c:\start.bat
If the pre-backup batch commands fail, the backup may not run.
Barracuda Linux Backup Agent Running on a Linux/Unix-Based System
You can run a pre- and post-Agent backup command script by editing the Linux config.ini file to run pre- or post-commands to stop and start
certain processes on the Linux/Unix-based system where the Barracuda Backup Agent (Linux) is installed, For example, script.sh:
1. Navigate to the config.ini file located in "/usr/local/barracuda/bbs/config/" on the system where the Barracuda Linux
Backup Agent is installed.
2. Open the config.ini file in a text editor, and below the [ configuration ] section, enter the following lines:
preExecuteScript=/root/script.sh
postExecuteScript=/root/script.sh


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Novell NetWare Server and
GroupWise 8 and 2012.
Set up your Novell NetWare Server to complete GroupWise message-level backups with a Barracuda Backup Server.
Requirements
NetWare Server 6.5 or greater

GroupWise Server version 8 or greater
Configure the GroupWise Server
Use the following steps to configure the GroupWise Server:
1. On a Microsoft Windows workstation where the Novell Client is installed, log in with an account that has access to the GroupWise
primary domain database file wpdomain.db:
2. Create an account to be used by the Barracuda Backup Server to access the email in each mailbox; the service account must be a
member of either the Enterprise Administrators or Domain Administrators group.
Generate a GroupWise Trusted Key
A trusted application key allows a third-party program to authenticate to the post office agent (POA) or the Internet Agent and obtain GroupWise
information that would otherwise be available only by logging in to GroupWise mailboxes. Starting with GroupWise 8 Support Pack 1, you can
create a trusted application and its associated key in ConsoleOne for use with both Linux and Windows trusted applications.
Use the following steps to generate a trusted key:
1. Open ConsoleOne. From the Tools menu, point to GroupWise System Operations, and click Trusted Applications:

2. The Configure Trusted Applications dialog box displays. Click Create:
3. The Edit Trusted Application dialog box displays:

4. In the Name field, type Barracuda Backup, and enter a description for the trusted application in the Description field.
5. Leave the TCP/IP Address field blank to allow the trusted application from any server, or, to restrict the location from which the trusted
application can run, click the Edit icon to the right of the field, and in the Edit Network Address dialog box, specify the IP address or
DNS hostname of the trusted application server. Click OK to save your settings and close the dialog box.
6. To require a secure (SSL) connection between the trusted application, POAs, and Internet Agents, select the Requires SSL check box.
7. Click the Browse icon to the right of the Location for key file field, and browse to and select the directory where you want to create the
trusted application key file.
8. In the Name of Key File field, enter the trusted application key file name.
9. Click OK to save the trusted application configuration information.
Add the GroupWise Server as a Data Source
1. Log in to Barracuda Backup web interface, and select the associated Barracuda Backup Server in the left pane.
2. Go to the Backup > Sources page, and click Add a Computer.
3. In the Computer Information section, enter the Netware Server description and hostname or IP address.
4. From the Computer Type drop-down menu, select Novell Open Enterprise Server.
5. In the Open Enterprise Server Computer Information section, enter the login credentials for the server.
6. Click Save.
7. On the Add Data Source page, enter a description for the data source, and from the Data Type drop-down menu, select Message-Leve
l Backup (GroupWise).
9. In the Message-Level Backup (GroupWise) Information section, enter the GroupWise mailbox location in the Base Context field.
10. In the Trusted Application Key field, paste the Trusted Application Key created in the previous section.
11. You can optionally enter the e-Directory Server hostname or IP address.
12. Click the Test GroupWise Connectivity to verify the connection.
13. Click Save.
14. Go to the selected schedule on the Backup > Schedules page. In the Items to Back Up section, select the mailboxes you want to back
up.
15. Click Save.
Retain Emails
This step is optional. You can optionally set up GroupWise to have all emails backed up by Barracuda Networks. This feature instructs
GroupWise to not purge emails until Barracuda Backup has a backup copy of the email. For information on how to set up this feature, please view
the GroupWise Administration Guide - Environment Options: Retention section available on the Novell website.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer higher, and Novell NetWare Server and
GroupWise 8 and 2012.
The Barracuda GroupWise Trusted Application Key Generator is used when setting up GroupWise message-level backup on a Barracuda
Backup appliance. It generates a trusted key used to securely authenticate from the Barracuda Backup appliance to your GroupWise server.
Download the latest version from the System > Software Downloads page in the Barracuda Backup web interface.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Macintosh OS X.
By default, the root account on Macintosh OS X Servers is disabled. If a user uses the admin account to back up content to Barracuda Backup,
they may encounter a warning message stating that some files cannot be backed up. To resolve this issue, Barracuda Networks recommends
using the root account for backups as the root account has full permission on the disk and is able to back up the server with limited warnings.
Create a Root Account
Set up a root account based on your software release.

El Capitan OS X (10.11 and Higher)
1. From the Apple menu, click System Preferences > Sharing.

2. Select Remote Login. For allow access for, select All users.
OS X Yosemite/El Capitan OS X (10.10 and Higher)
1. From the Apple menu, click System Preferences.

2. From the View menu, click Users & Groups.
3. Select Remote Login. For allow access for, select All users.
Mac OS X v10.6.x

2. From the View menu, click Accounts.
3. Click the lock and authenticate as an administrator account.
4. Click Login Options, and click Edit at the bottom right of the screen.
5. Click Open Directory Utility, and in the Directory Utility, click the lock.
6. Enter the administrator account name and password, and click OK
7. From the Edit menu, click Enable Root User.
8. Enter the root password you wish to use in both the Password and Verify fields, and click OK.
Mac OS X v10.5.x
1. From the Finder's Go menu, choose Utilities, and open Directory Utility.
2. Click the lock in the Directory Utility window.
3. Enter an administrator account name and password, and click OK.
4. From the Edit menu, click Enable Root User.
5. Enter the root password you wish to use in both the Password and Verify fields, and click OK.
Mac OS X v10.3.x through v10.4.x
1. Click the Finder icon in the Dock.

2. From the Go menu, click Applications.
3. Open the Utilities folder.
4. Open the NetInfo Manager utility.
5. Click the lock in the NetInfo Manager window.
6. Enter the administrator account name and password, and click OK
Mac OS X 10.2
For Mac OS X 10.2 and later, choose Enable Root User from the Security menu.
Mac OS X 10.0 and 10.1
1. From the Domain menu, point to Security, and click Enable Root User.
2. If you have not previously set a root password, an alert box displays the message NetInfo Error, indicating that the password is blank.
Click OK.
3. Enter the root password you wish to use, and click Set.
4. Enter the password again, and click Verify.
5. Click the lock to prevent changes.
Log in as the Root User
1. Open the /etc/sshd_config file, and navigate to the line PermitRootLogin.

2. Uncomment the line, and set the value to yes:
PermitRootLogin yes
3. Run the following commands to stop and restart sshd:
launchctl stop com.openssh.sshd
launchctl start com.openssh.sshd
You can now log in using the root account based on your software release.
Mac OS X v10.2 and Later

1. If you are logged in, choose Log Out from the Apple menu.
2. If you are logging in from a list of usernames with pictures, click Other.
3. In the Name field, type: root
4. In the Password field, type the password you defined earlier.
Mac OS X v10.0 to v10.1.5
After enabling the root user, you must log out from Mac OS X and log back in as the root user. Logging in to Mac OS X from a list of
usernames is the default behavior for later versions of Mac OS X. Logging in by typing your username in a text entry field is the default
behavior in earlier versions of Mac OS X. You can choose either method in Login preferences. The root user does not appear in the
list, so you need the text entry option. If necessary, follow these steps to change the login method to text entry:

2. From the View menu, click Login.
3. Click the Login Window tab.
4. Select Name and password entry fields, and complete the steps in the next section to log in as root account.
1. If you are logged in, choose Log Out from the Apple menu.
2. In the Name field, type: root
3. In the Password field, type the password you defined earlier.
Set up SSH Key for Mac
For each local Barracuda Backup appliance, identify the data sources that are to be backed up. There may be more than one data source on
each server, and each can have unique backup characteristics.
2. Go to the Backup > Sources page, and click Add a Computer to identify the computer.
3. Enter the IP address of the Mac Server.
4. From the Computer Type drop-down menu, select Mac OS X.
5. In the Mac OS X Information section, enter root in the Username field.
6. Download the SSH Key installer, and run the setup.
7. Once the key is installed, save the settings. Click Save.
10. Select whether to replicate data to Barracuda Cloud Storage.
12. Click Save.
content, or click and expand the data source to select individual folders for backup.
14. Click Save.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer. Barracuda Backup uses the SSH
Filesystem (SSHFS) and public key authentication to connect and back up Linux data.
Backed Up Content
This article describes how to back up Linux/UNIX-based file systems, such as Red Hat, Ubuntu, or SUSE, using SSHFS. Before
backing up data, verify that you have adequate permissions to the folder you intend to back up.
Add the Linux Server
Use the following steps to add the Linux Server to Barracuda Backup.
Before adding the Linux Server to Barracuda Backup, notify users that their Secure Shell (ssh) session may be lost during set up.
2. Go to the Backup > Sources page, and click Add Computer.
3. Enter a computer description and enter the IP address or fully qualified domain name in the Computer Name field.
4. From the operating system drop-down menu, select Linux / Unix:
5. Turn on Enable File Share Backups; the Linux/Unix (SSHFS) Information section displays:

6. Enter the Username for the system account that is to have access to back up data.
7. In the To backup data on Linux or Unix based servers section, copy the commands to your clipboard.
8. On the Linux Server, determine the location of the ssh directory, including the authorized_keys file, in the user's home directory:
If a username different than root is used, place the ssh directory, including the authorized_keys fil
e, in the user's home directory.
If the root account is used, place the ssh directory, including the authorized_keys file, in the root
home directory
9. Log in to the Linux Server using an ssh client such as PuTTY, and paste and run the commands copied in step 7 into the appropriate
directory based on step 8 to set up the public key provided by Barracuda Networks:
10. On the Linux Server, navigate to /etc/ssh and open the file sshd_config:
If an error message stating that no sshd_config file could be found displays, the ssh daemon may not be installed.
In some Linux installations, the ssh client is installed without the ssh daemon.
For more information, refer to the documentation available online or included with your version of Linux for the proper
procedures to install the ssh daemon on your server. For your reference, the following link is provided to show an example of

sshd installation instructions, for example, see the Open SSHServer documentation.
11. In the file sshd_config, locate the line PubkeyAuthentication yes, and r emove the pound sign "#":
.
12. Run the following command to restart sshd:
/etc/init.d/sshd restart
Depending on the Linux Server distro, it may be necessary to disable SELinux enforcement using the command:
echo 0 > /selinux/enforce
13. In the Barracuda Backup web interface, click Save; the Add Data Source page displays. Continue with Add Linux Server Data Sources
below.
Add Linux Server Data Sources
Use the following steps to select the Linux Server folders you wish to back up.
1. In the Add Data Source page, enter a Data Description for the data source.
2. From the Data Type drop-down menu, select File Share - SSHFS.
3. In the File Share Information section, enter the full path of the directory to be backed up in the Share Name field, and click Test Share;
if the connection is successful, a message displays the connection status, for example, Status: Successfully connected to computer.
If the connection is not successful, return to the Add Computer page and verify the IP address is correct before continuing.
Click Save.
content, or click and expand the data source to select individual items for back up.
Important
If you are backing up root or /, you must clear the proc and sys directories.
6. Click Save.
Set Up Retention Policies
Once you have your Linux data source items set up for backup, you can set up retention policies.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and VMware® 4.1 and above with the
VMware license which includes access to vSphere® Data Recovery API.
ESXi600-201511001 (2137545).
Use Changed Block Tracking (CBT) to perform incremental backups on virtual machines running on VMware ESX/ESXi. CBT identifies and
tracks block changes since the last backup, and stores these changes in log form, greatly reducing the number of backup windows and improving
backup window times. Additionally, subsequent replication efficiency and speed are improved.
Barracuda Backup automatically leverages CBT when CBT is enabled for the virtual machine being backed up.
Setting Up Changed Block Tracking
For details on setting up and enabling CBT on virtual machines, refer to the VMware Knowledge Base articles available from the VMware website
:
Changed Block Tracking (CBT) on virtual machines

Enabling Changed Block Tracking (CBT) on virtual machines
Contact Barracuda Networks Technical Support for information on enabling CBT from the VMware API.
You can enable CBT directly on a VM data source. For a list of requirements and detailed steps, refer to How to Enable Changed Block Tracking
through the Barracuda Backup Web Interface.

The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and VMware 4.1 and above with the
VMware license which includes access to vSphere Data Recovery API.
Use Changed Block Tracking (CBT) to perform incremental backups on virtual machines (VMs) running on VMware ESX/ESXi. CBT identifies
and tracks block changes since the last backup, and stores these changes in log form, greatly reducing the number of backup windows and
improving backup window times. In Virtual Machine File system (VMFS) partitions, CBT can identify all disk sectors that are in use. Additionally,
subsequent replication efficiency and speed are improved. Barracuda Backup access CBT through the vSphere APIs for Data Protection (VADP)
by requesting the changed VMkernel return blocks of data on the virtual disk since the last backup snapshot.
VMware has reported an issue with ESXi version 6.0.x where incorrect changed sectors are returned. When a VM is running ESXi 6.0.x
and CBT is enabled, some change areas in data are not reported. When this occurs, that data is not recognized as changed and is not
backed up; current and past incremental backups are potentially compromised. For more information, see the VMware knowledgebase
solution Backing up a Changed Block Tracking enabled virtual machine in ESXi 6.0.x returns incorrect changed sectors (2136854).
ESXi600-201511001 (2137545).
Requirements
To enable CBT, verify the following is true for your environment:
The host must be ESX/ESXi 4.1 or later;

The VM owning the disks to be tracked must be hardware version 7 or later;
Snapshots do not exist on the VM; and
VM storage is not (persistent or non-persistent) independent disk, therefore it is unaffected by snapshots.
Enable Changed Block Tracking
Use the following steps to enable CBT on a data source:
2. Go to the Backup > Sources page, and click Edit for the VMware data source:
3. Scroll to the Enable Changed Block Tracking section, and select Enable CBT:
4. Click Save.
5. In the Item to Back Up section, clear Apply to all computers and data sources for this Backup Appliance. Expand the VMware
environment to locate your VMs.
6. When CBT is enabled, CBT displays to the left of the VM name on the Backup > Schedules page for the VMware data source:

Use CBT to perform incremental backups on VMs running on VMware ESX/ESXi. CBT identifies and tracks block changes since the last backup,
and stores these changes in log form, greatly reducing the number of backup windows and improving backup window times. Additionally,
subsequent replication efficiency and speed are improved.
Barracuda Backup automatically leverages CBT when it is enabled for the VM being backed up.
Set Up Changed Block Tracking
For details on setting up and enabling CBT on VMs, refer to the VMware Knowledge Base articles available from the VMware website:
Changed Block Tracking (CBT) on virtual machines

Enabling Changed Block Tracking (CBT) on virtual machines


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer. With CIFS backups, Barracuda Backup is
able to back up access control lists (ACLs).
Watch the Barracuda Backup - Backing up a Network Addressable Storage (NAS) video:
Configure Network Addressable Storage Data Sources
Use the following steps to identify the data shares on your server that are to be directly backed up:
1. Log into Barracuda Backup, and select the Barracuda Backup appliance in the left pane that is to back up the data shares.
2. Go to Backup > Source, and click Add a Computer.
3. In the Add a Computer page, complete the following:
a. Computer description – Enter a description of the data source
b. Computer name – Enter the data source IP address or fully qualified domain name (FQDN)
c. Computer Type – Select Microsoft Windows.
d. Turn on Enable File Share Backups, enter the file share credentials, and click Test Credentials.
4. Once you verify the connection, click Save at the top of the page; the Add Data Source page displays.
5. From the Data Type drop-down menu, select File Share - CIFS.
6. In the File Share Information section, click Toggle All Shares to view the available network shares on the server, and click Fetch Data
Sources to automatically populate the list of data sources.
7. Click on the share you want to back up. Alternatively, you can enter the exact name of the network share on the server, for example, C$,
needed to access the data source from devices on the local network.
8. Click Test Share to test share connectivity.
9. To replicate to the cloud, turn on Replicate to Barracuda Cloud Storage; note that if you have globally selected to replicate to the
cloud, you cannot change this setting.
Replication
If you wish to set up replication to another Barracuda Backup Server, turn on Replicate to Other Barracuda Backup Servers,
and click Add a new Backup Server. For detailed steps, refer to Configuring a Replication Destination.
10. From the Schedule drop-down menu, and click Add New Schedule.
11. In the Add New Schedule dialog box, enter a name to represent the schedule, and click OK. Click Save.
12. The Schedules page displays. In the Items to Back Up section, you can select to back up all folders in the network share, or select
specific folders you want to back up.
13. In the Schedule Timeline section, specify when you want the backup schedule to run.
To set retention policies,
2. In the Items to Retain section, select the NAS data source to which the retention policy applies; the Retention Timeline section
3. Click Save.
Configure Optional Features
You can optionally configure the following settings for the NAS data sources:
Back Up Rate Limit – Rate limits control the data replication rate to Barracuda Cloud Storage or other offsite storage locations. You can
limit Internet bandwidth consumption during peak usage times, and schedule backups for non-peak hours on the Backup > Rate Limit p
age.
Exclude Files from Backup – You can create exclusion rules that use pattern matching to identify directory or file names that you do
not wish to back up on the Backup > Exclusions page.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and the FirstClass Mail client running on
Windows or Linux/Unix.
Install the Agent
Use the following steps to install the Barracuda Backup Agent:
1. Log in to the Barracuda Backup web interface, and selected the associated Barracuda Backup Server in the left pane.
2. Go to the System > Software Downloads page, and select the appropriate Agent for the environment in which you are
running FirstClass Mail:
If you are running FirstClass in Windows, download and install the Barracuda Backup Agent (Windows).
If you are running FirstClass in a Linux/Unix environment, download and unzip the Barracuda Backup Agent (Linux) on your
local Linux system or server.
Replicate Data
If you are replicating data to another FirstClass Mail Server, you must disable mirroring when backups run.
You can run pre- and post commands to stop and start this process.
Permissions
To run these commands you must have permissions to the FCP utility fcputility.
To pause mirroring, use the command:
fcputil pause
To restart mirroring, use the command:
fcputil continue
If the installed Agent has access to fcputility, you can run these commands from the Agent. For more information, refer to How to
Create a Pre- or Post-Agent Backup Command Batch File or Script.
Add FirstClass Mail as a Data Source
Use the following steps to add FirstClass Mail as a data source:
1. Log in to the Barracuda Backup web interface, and selected the associated Barracuda Backup Server in the left pane.
2. Go to the Backup > Sources page, and click Add Computer.
3. Enter the FirstClass Network Store (FCNS) computer description, and enter the IP address or FQDN in the Computer Name field.
4. From the Computer Type drop-down menu, select either Microsoft Windows or Linux / Unix, and click Save.
5. In the Add Data Source page, select Barracuda Agent Software as the Data Type.
6. Click Test Software Connectivity to verify Barracuda Backup can communicate with the Agent.
7. In the Add to Schedule section, select an existing schedule from the Schedule drop-down menu, select Add New to create a new
schedule.
8. Click Save.
9. Go to the selected schedule on the Backup > Schedules page.
10. In the Items to Back Up section, select Apply to all computers and data sources for this Backup Appliance to back up the
entire FCNS folder including desktop folders, calendar, contacts, etc., or clear this option to select individual items for backup.
11. Click Save.
FirstClass Mail backups will run at the next scheduled time.

This article refers to Barracuda Backup version 6.3 and higher, and the Barracuda Backup Agent (Linux).
Back up NFS mounts using the Barracuda Linux Backup Agent.
Configure the Agent
Use the following steps to configure the Barracuda Backup Agent (Linux):
1. Log in to your Linux Server, and enter the following command to stop the Agent:
# /etc/init.d/bbagent stop
2. Navigate to the Barracuda Backup Agent installation directory. The default location is: /usr/local/barracuda/bbs/
3. Open the config directory, and open the config.ini file in a text editor.
4. Below the [configuration] section, enter:
IncludedMountpoints=/mount/mountpoint,/mount/mountpoint2
For example:

6. Enter the following command to restart the Agent:
# /etc/init.d/bbagent start

This article refers to Barracuda Backup version 6.3 and higher, the Barracuda Backup Agent (Linux), and the Novell Storage
Services (NSS) file system.
Back up NSS mounts using the Barracuda Backup Agent (Linux).
2. Navigate to the Barracuda Backup Agent installation directory. The default location is:
/usr/local/barracuda/bbs/
For example:


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Oracle running on Linux.
The script and command file in this article are only an example; there are many different configurations that can be modified using
Oracle Recovery Manager (RMAN). Refer to Oracle documentation when considering different environmental variables.
To automate the Oracle database backup process, you must create a script and command file which utilizes the Oracle RMAN.
Running an Oracle database in archivelog mode allows you to back up the database while it is open and in use. Verify your Oracle database is in
archivelog mode to complete your backup, as shown in Figure 1.
Figure 1. archivelog mode.
Example
Create a script named backup.sh containing the following:
#!/bin/bash
su – oracle -c "rman cmdfile='/u01/backup.rman'"
Create a command file named backup.rman containing the following:
connect target SYSTEM/<password>;

configure channel device type disk format '/u01/backup/%d_DB_%u_%s_%p';
configure retention policy to recovery window of 3 days;
backup database plus archivelog;
quit;
For more information on backing up an Oracle database with RMAN, refer to Backing Up the Oracle Database.
After creating the script and command file, edit the Barracuda Backup Agent config.ini file located in "/usr/local/barracuda/bbs/config/
", and add the following line under the entry [configuration]:
PreExecuteScript=/u01/backup.sh
For more information, refer to How to Create a Pre- and Post-Agent Backup Command Batch File or Script.
Save and run a backup from Barracuda Backup, as shown in Figure 2.
Figure 2. Barracuda Backup Report.


The articles in this section refer to Barracuda Backup Legacy Release firmware or newer, and Oracle running on Microsoft
Windows.
The script and command file in this article are only examples; there are many different configurations that can be modified using
Oracle Recovery Manager (RMAN). Refer to Oracle documentation when considering different environmental variables.
To automate the Oracle database backup process, you must create a script and command file which utilizes the Oracle RMAN.
Running an Oracle database in archivelog mode allows you to back up the database while it is open and in use. Verify your Oracle database is in
archivelog mode to complete your backup.
Example
Create a script named backup.bat containing the following:
C:
cd C:\ora10g\BIN
rman @C:\backup_rman\backup.rman
Create a command file named backup.rman containing the following:
connect target 'system/password'

run
{
allocate channel d1 type disk;
backup AS COMPRESSED BACKUPSET tag Full_database_open format 'C:\backup_rman\db_%t_%s_p%p.dbf' database;
backup AS COMPRESSED BACKUPSET archivelog all format 'C:\dbbackup_rman\al_%t_%s_p%p.dbf' delete all input;
backup AS COMPRESSED BACKUPSET current controlfile tag =cf1 format 'C:\dbbackup_rman\cf_%t_%s_p%p.dbf';
delete noprompt expired backup;
}
For more information on backing up an Oracle database with RMAN, refer to Backing Up the Oracle Database.
After creating the script and command file, edit the Barracuda Backup Agent config.ini file located in C:\Program Files\Barracuda\Barracuda
Backup Agent\Config\, and add the following line under the entry [configuration]:
PreExecuteScript=C:\backup.bat
For more information, refer to How to Create a Pre- and Post-Agent Backup Command Batch File or Script.
Save and run a backup from Barracuda Backup, and verify that the RMAN dump files are backed up with the barracuda Agent or CIFS method.


This article refers to Barracuda Backup Legacy Release firmware or newer and the Barracuda Backup Agent (Windows) and Barra
cuda Backup Agent (Linux).
Example uses the Barracuda Backup Agent (Windows). Note that the process for Barracuda Backup Agent (Linux) is the same.

2. Go to the Backup > Sources page.
3. Click Add Computer. In the Computer Information section, enter the data source details:
Computer description – Enter a name to identify the data source
Computer name – Enter the name or IP address of the data source
Computer type – Select Microsoft Windows (select Linux for Barracuda Backup Agent for Linux) from the drop-down menu
If you have not downloaded and installed the Barracuda Backup Agent, click Backup Agent software, and download
and install the agent on the client system:
4. In the Barracuda Backup Agent section, verify Enable File Share backups is turned off, and then click Save.
5. Click Test Software Connectivity to verify Barracuda Backup can communicate with your server.
If a message displays noting that the Barracuda Backup Agent software is presently upgrading, allow a minute, and then click
Test Software Connectivity again.
6. In the Add to Schedule section, you can apply multiple schedules to the same source. From the Schedule drop-down menu, select an e
xisting schedule to apply to the data source, or select Add New:
7. If you select Add New, the Add New Schedule window displays. Enter the new Schedule Name, and then click OK:

7.
8. New and selected schedules display in the Add to Schedule section:
9. Configure the remaining options:

Microsoft SQL Server Requires Authentication – If the local system account is not a member of the SysAdmin role in SQL,
turn on this option, and then enter a username and password with the appropriate access.
Replicate to Barracuda Cloud Storage – When selected, data is replicated to Barracuda Cloud Storage.
Replicate to Other Barracuda Backup Appliances – When selected, you can replicate data to another Barracuda Backup
Appliance.
10. Once you have configured schedules and the backup and replication options, click Save. The Schedules page displays.
11. In the Items to Back Up section, click the arrows to drill down into your data source. Select the items under the Agent you want to back
up under the selected schedule:
If you want to break up the Agent backup into multiple schedules, select only the data you want to back up using the current
schedule, and then click Save. You can then create a new schedule and select the remaining data/items. Note that System
State is required to perform a bare metal or physical to virtual restore.

12. Once you select the data for backup, select the days that this schedule is to run in the Schedule Timeline section:
13. In the Daily Backup Timeline section, enter a Start Time:
14. If you want to have your backup schedule repeat throughout a 24-hour period, turn on Repeat:
15. In the SQL/Exchange Backup section, specify the type of backup to run:
Smart – Automatically decides when full or log backups are appropriate.
After a full backup is performed, the backup server performs transaction log backups until the minimum threshold is met. After
the minimum threshold is met, the Barracuda Backup appliance performs a full backup unless there is more than 1 GB of data
in the Cloud Transfer Queue, or until the maximum threshold is met.
Smart mode with the default thresholds is recommended.
Full – Captures a complete database/information store each time.

Log – Captures transaction log changes since the last backup.
16. Click Save.
Your newly created backup schedule displays in the Schedules page including the configured options:
Click Edit to modify the schedule, Remove to delete the schedule, and Run Backup Now to start the backup job immediately.
To view how much data was last backed up, go to the Backup > Sources page, and toggle the source ON or OFF. A green indicator
signifies that the last backup was successful, while a red indicator means that the last backup encountered issues:

For details on issues encountered during backup, refer to the Reports page.

This article refers to Barracuda Backup version 6.3 and higher, and the Barracuda Backup Agent (Linux).
Back up Lustre mounts using the Barracuda Linux Backup Agent.

2. Navigate to the Barracuda Backup Agent installation directory. The default location is: /usr/local/barracuda/bbs/
For example:



This article refers to the Barracuda Message Archiver, and Barracuda Backup Legacy Release firmware or newer.
Back up archives using Barracuda Backup via SMB access to the Barracuda Message Archiver's data partition.
Step 1. Barracuda Message Archiver
The Barracuda Message Archiver provides authenticated read-only access to the internal data partition via CIFS.
1. Log in to the Barracuda Message Archiver as the administrator, and go to the Advanced > Backups page.
2. In the Backup of Archives section, set Back Up Archives via SMB to Yes to allow access to the message store as an SMB share.
3. Set a workgroup name and password to connect to the SMB share; note that the SMB share username is always smb:
4. Click Save to save your settings.
Step 2. Barracuda Backup
The Barracuda Message Archiver shares are published as: IP:/BMA-SMB-sharenumber
1. Log in to Barracuda Backup as the Administrator, and go to the Backup > Sources page.
2. Click Add a Computer. In the Add a Computer page, enter a Computer description and enter the IP address or fully qualified domain
name in the Computer Name field.
3. From the Computer Type drop-down menu, select Microsoft Windows:

4. Set Enable File Share Backups to On; enter smb as the Username.
5. Enter the password you set up on the Advanced > Backups page in the Barracuda Message Archiver web interface, and then click Test
Credentials to verify access to the file share.
7. In the Add Data Source page, from the Data Type drop-down menu, select File Share - CIFS, and verify Enable Backups is selected:
8. In the File Share Information section, enter BMA-SMB as the Share Name, and click Test Share.
9. In the Folder Selection section, specify which folders you want to back up.
10. To replicate to the cloud, turn on Replicate to Barracuda Cloud Storage:

11. Select the backup schedule for the SMB share.

12. Click Save at the top of the page to save your configuration and add the data source.
For more information, go to the go to the Advanced > Backups page in the Barracuda Message Archiver, and click Help.

Replication Page
Barracuda Backup appliances that are used to back up data from one or more Barracuda Backup appliances are known as replication destination
s. Data from one Barracuda Backup appliance can be replicated to one or more destinations.
Barracuda Backup 890 with an internal capacity of 16 TB, and you want to configure this system to receive data from multiple Barracud
a Backup 390 appliances which have an internal capacity of 2 TB, the total amount of Barracuda Backup 390 appliances sending to the
Barracuda Backup 890 should not be more than 8.
Before getting started, verify the following:
Make sure that your retention policies are configured before configuring replication. Otherwise you may waste bandwidth copying data
that does not need to be replicated.
Verify Internet connectivity between the local and remote Barracuda Backup appliance(s). Configuring a secure VPN connection
between multiple Barracuda Backup appliances ensures the highest level of security possible.
You must have the serial number and replication code of the destination Barracuda Backup appliance. Go to the destination Barracuda
Backup appliance, and go to the Backup > Replication page. The serial number and replication code display at the top right of the
page.
Configure Backup Data Replication
Configure backup data replication to one or more other Barracuda Backup appliances on the Backup > Replication page. Rate limits and total
number of replicated data sources for each target display in the Target List table:
Sending Data To
This section displays target system details. In this section, you can take the following actions:
Target List displays where data from the selected Barracuda Backup appliance is sent
Click Settings to edit the replication configuration.
Click Remove to remove the target and purge all data related to the source on the target device.
Toggle local backups On/Off in the Send all local backups field.
Receiving Data From
This section displays source system details. In this section, you can take the following actions:
Click Remove Replication Partner to delete the replication source.

Source List displays a list of devices sending data to the selected Barracuda Backup appliance.
Barracuda Backup compresses and encrypts data prior to replication; the value displayed in the Total Stored field represents

data before compression.
A Barracuda Backup appliance can act as a backup to one or more other Barracuda Backup appliances. Each Barracuda Backup appliance can
send data to one or more other Barracuda Backup appliances.
Important
Continue with Configure a Replication Destination.

Configuring a Replication Destination

Important
up on a second Barracuda Backup appliance cannot be backed up yet again onto another Barracuda Backup appliance or to
the Barracuda cloud.
When backing up to a second Barracuda Backup appliance, both appliances must be on the same firmware version.
Barracuda Backup 890 with an internal capacity of 16 TB, and you want to configure this system to receive data from multiple
Barracuda Backup 390 appliances which have an internal capacity of 2 TB, the total amount of Barracuda Backup 390 appliances
sending to the Barracuda Backup 890 should not be more than 8.
Replication page.
6. Click Save.
appliances.

Disable Replication


How to Temporarily Disable a Destination

You can temporarily disable the site-to-site replication feature for one or more destinations. When disabled, nothing is sent from the Barracuda
Backup Server to the destination for replication until the feature is enabled or until 24 hours have passed. This allows you to move the destination
system to a remote location, say, without getting replication errors. If the 24 hours pass without manually re-enabling this feature, the Barracuda
Backup Servers attempt to communicate with each other and, if successful, perform replication.
To temporarily disable site-to-site replication, go to the Backup > Replication page. In the Sending Data To table, click on the Settings link
beside the destination Barracuda Backup Server. On the Replication Target Settings page, clear Enable data replication to disable data
replication for up to 24 hours.

Managing the Data Queue

If there is a loss of communication between the Barracuda Backup Server and its backup destination for any reason, the data to be replicated is
queued and errors are generated; data is queued until the issue is resolved. The queue size in the table on the Backup > Replication page
indicates how much data is waiting to be replicated.
Note that not all of this data is actually copied to the destination. Some of it is deduplicated as the replication proceeds. Only those
parts that are not already stored in the remote location are sent over the Internet.
Bandwidth Recommendations
For every terabyte of data replicated, Barracuda Networks recommends a minimum of 1.5 Mbps or T-1 connection.
The following queue details display on the Backup > Replication page:
Settings – Click to change the replication target details, disable data replication, and modify rate limits
Status – Displays either the green indicator ( ) icon or the red indicator ( ) icon
Send All Local Backups – Toggle backup On/Off, and disable replication for up to 24 hours.
Total Stored – Total size of file parts transferred offsite from the Barracuda Backup Server
Queue Age – Amount of time that the queued data has been waiting to be transferred offsite from the Barracuda Backup Server for
replication
Queue Size – Total size of the file parts yet to be transferred offsite from the Barracuda Backup Server for replication

How to Set Rate Limits

day. By default, Barracuda Backup is configured to run at full speed around the clock, unless you set a rate limit allowing it to only run full speed
at night and an alternate, lower speed during the day.
Define rate limits on Barracuda Backup replication targets. Barracuda Backup uses Full Speed as the default rate limit. To customize the rate
limit on a target system:
1. Go to Backup > Replication, and click Add a Target.

2. In the Add Replication Target, enter the Replication Target Information.
3. In the Rate Limit section, the following options are available:
Option Settings Details
Default Rate Limit Full Speed – Uses 100% of available Specify the default rate limit.
bandwidth
Smart Mode – Drag the Percent of
Bandwidth bar to specify the rate
limit; click Test bandwidth to verify
your setting
Kb/s or Mb/s – Specify the
rate limit in Kilobits or
Megabits per second
Alternate Rate Limit Full Speed – Uses 100% of available You can optionally create an alternate rate
bandwidth limit which is maintained only during the
Smart Mode – Drag the Percent of specified time periods:
Bandwidth bar to specify the rate
From/To – Specify the start and end
limit; click Test bandwidth to verify
time (24 hour format)
your setting
On – Select the days on which the
Kb/s or Mb/s – Specify the alternate rate limit applies
rate limit in Kilobits or
Megabits per second

How to Set an Alternate Rate Limit

You can set rate limits to control the data replication rate from a Barracuda Backup appliance to another destination. Set rate limits to control
Internet bandwidth consumption during peak usage times, and schedule backups for non-peak hours.
Use the following steps to set rate limits:
1. Log in to Barracuda Backup, and go to the Backup > Replication page.

2. In the Sending Data To section, click Settings next to your replication target in the Target List.
3. The Edit Replication Target page displays. In the Rate Limit section, turn on Enabled for Alternate Rate Limit;
the alternate rate options display. Select the bandwidth limit, and then set the time and days that the limit is to be in effect:
4. Click Save. The alternate rate limit displays in the Target List:

Understanding the Data Replication Queue

Data is queued for replication as a backup job progresses. The replication queue reflects raw, uncompressed and undeduplicated data awaiting
replication. Note that not all of this data is actually copied to the destination, some of the data is deduplicated as the replication proceeds. Only
those parts that are not already stored in the remote location are sent over the Internet.
You can view the remaining data, in bytes, awaiting replication as well as bandwidth efficiency on the Backup > Replication page.
The Transfer Remaining graph on the Dashboard page displays the raw, undeduplicated and uncompressed data waiting to transfer in bytes. F
igure 1 shows transfer remaining for a device replicated to the cloud.
Figure 1. Transfer Remaining Graph.
Additionally, you can mouse-over graph to view more detailed information, or click on the graph for a larger view.
The Transfer Efficiency graph represents all content up to the current date that has been sent to Barracuda Backup based on the maximum data
transfer rate of your connection in bytes. To limit Internet bandwidth consumption during peak usage times, set rate limits and schedule backups f
or non-peak hours. To modify the rate limit, click Edit below the graph. Figure 2 shows transfer efficiency for a device replicated to the cloud.
Figure 2. Transfer Efficiency Graph.
Example 1. Estimating Data Transfer Time.
If there is 600 GB of raw data in the queue, and data is transferring at an effective average rate of 1GB/second, then it will take approximately
600 seconds (10 minutes) to clear the queue if it continues at this rate.

Schedules Page
This article refers to the Barracuda Backup Legacy Release firmware or newer, except where noted.
Once your Barracuda Backup Server is installed and data sources are set up, data is collected from each data source for the first time during an
initial backup period. Once the initial backup is complete, Barracuda Backup checks for changed and new data based on backup schedules you
define on the Backup > Schedules page. Any data sources that do not have a schedule defined are, by default, backed up nightly at 8:00PM
local time. When Barracuda Backup identifies new or changed information, each file is analyzed at the bit level, and only the new bit sequences in
the files themselves are copied and transferred, saving both bandwidth and storage space.
multiple schedules for each source, each with different sets of data selected.
In version 6.2 and higher schedules are part of data source item selection. For this reason, if you did not configure schedules in version
6.1 and earlier, a schedule is automatically created when you upgrade to version 6.2.
Create a Schedule
To create a backup schedule, configure computers and data sources, and then go to the Backup > Schedules page of the Barracuda
Backup web interface.
1. Click Add a Schedule (or click Edit to edit an existing schedule):
2. Once you are satisfied with your schedule, click Save. The new schedule displays on the BACKUP > Schedules page:
Schedule Fields
Schedule Name
Enter a label to identify the backup schedule:
Items to Back Up
In the Items to Back Up section, use the arrows to expand each server/source until you find the desired data or virtual machines to back up. You
can select an entire server or select specific directories, databases, or virtual machines. It is possible to select and create a schedule for as many
different items as you wish.
For example, in the image below we will create two schedules for an Exchange source; one for the Exchange database that we will repeat
throughout the day and another for the File System and System State that we will back up only once per day:

Schedule Timeline
Once you have selected data for backup, select the days on which this schedule will run:
Daily Backup Timeline
In the Daily Backup Timeline section, type in a Start time. Turn on Repeat if you want your backup schedule to repeat throughout a 24-hour
period:
SQL/Exchange Backup
If the backup schedule is for Microsoft SQL Server or Microsoft Exchange Server, you must specify the type of backup to run:
Smart – Automatically decides when full or log backups are appropriate.

After a full backup is performed, the backup server performs transaction log backups until the Minimum threshold is met. After the Mini
mum threshold is met, the Barracuda Backup appliance performs a full backup unless there is more than 1 GB of data in the Cloud
Transfer Queue, or until the Maximum threshold is met.
Smart mode with the default thresholds is recommended.
Complete – Captures a complete database/information store each time.

Log – Captures transaction log changes since the last backup.
Schedule Options
Once you create a backup schedule, you can edit, delete, or immediately run a backup:
Click the Edit link to modify the schedule, and then click Save at the top of the page to save your changes.
Click the Remove link to delete the selected schedule, and click Remove Schedule in the dialog box to verify you wish to remove the
selected schedule. For more information, see Granular Scheduling - Keep or Remove Data Options.
If you delete a schedule that a data source was schedule in, that data source does not have a schedule and therefore is not
backed up:

Click the Run Backup Now icon to run the scheduled backup process immediately, and click Run Backup Now in the dialog box that
follows to verify your the selected action. Once the backup starts, allow a few minutes for the report to generate on the REPORTS >
Backup page.
Additional Schedules on a Source
To create additional schedules for the same source, follow the process above selecting different data for the new schedule.

Granular Scheduling - Keep or Remove Data Options

This article applies to Barracuda Backup version 6.2 and higher.
In Barracuda Backup version 6.2 and higher, item selection has moved to the backup schedule. This allows you to granularly select specific sets
of data to back up and the ability to configure multiple schedules for each source, each with different sets of data selected. Additionally, you can
select whether to keep or remove data from Barracuda Backup when deselecting a previously backed up item from the Items to Back Up section
of a schedule or when choosing to delete an entire schedule.
Remove/Delete a Schedule
Use the following steps to remove an entire schedule:

2. Go to the Backup > Schedules page, and locate the schedule containing the data you want to delete; click Remove:
3. The Remove Schedule - Keep Data? dialog box displays:
4. Select Purge to permanently remove all revisions of the selected files from your Barracuda Backup Appliance:
5. Click Confirm. Purging may take up to 24 hours.
Edit a Schedule and Remove Previously Backed Up Data
Use the following steps to edit a schedule and deselect previously backed up data:
1. Log in to Barracuda Backup at https://login.barracudanetworks.com/.

2. Go to the Backup > Schedules page, and locate the schedule containing the data you want to deselect.
3. Click Edit:
4. Deselect the desired items under Items to Back Up, and then click Save; the Edit Schedule - Keep Data? dialog box displays:

4.
5. Select Keep.
6. Click Confirm. The data is retained in accordance with your retention policies.

Rate Limit Page
This article applies to Barracuda Backup version 5.0 through 5.4. Rate Limits in version 6.0 and higher you set on the replication
target from the Backup > Replication page.
day. By default, Barracuda Backup is configured to run at full speed around the clock, unless you set a rate limit allowing it to only run full speed
at night and an alternate, lower speed during the day.
If you do not set a rate limit, the Backup > Rate Limit page displays the following message:
Click Create one to set up a rate limit.
Once you create a rate limit, the Backup > Rate Limit page displays the customized rate limit settings:
If you have created a rate limit, you can take the following actions on the Backup > Rate Limit page:
Edit Rate Limit ( ) icon – Click to edit the rate limit. Select from the options listed in the following table:
Option Settings
Default Rate Limit Full Speed – Uses 100% of available bandwidth

Smart Mode – Drag the Percent of Bandwidth bar to specify
the rate limit;
click Test bandwidth to verify your setting
Kb/s or Mb/s – Specify the rate limit in Kilobits or Megabits per
second
Specify the default rate limit.

Alternate Rate Limit Full Speed – Uses 100% of available bandwidth

Smart Mode – Drag the Percent of Bandwidth bar to specify
the rate limit;
click Test bandwidth to verify your setting
Kb/s or Mb/s – Specify the rate limit in Kilobits or Megabits per
second
You can optionally create an alternate rate limit which is maintained

only during
the specified time periods:
From/To – Specify the start and end time

On – Select the days to which the alternate rate limit applies.
Reset to Default Rate Limit ( ) icon – Click to rest the selected Barracuda Backup Server to the default rate limit; click Reset To
Defaults in the dialog box that follows to complete your selection.

Exclusions Page
2. Go to the BACKUP > Exclusions page, and click Add an Exclusion.
Add Exclusions to Reports – Specify whether to include exclusions in reports.
Where to Exclude – Specify whether to apply the exclusion rule to all computers and data sources for the selected Barracud
a Backup Server.
4. In the What to Exclude section, specify the excluded file types:
From the Preset Expressions menu, select the content you want to exclude, for example, Audio files, then click Add.
Use Case
For example, a school organization does not want to back up music files located in user home directories. To exclude
these music files, they create an exclusion rule, select the directory, select the preset expression Audio files, and
enter the types of music files they want to exclude in the Expressions field.
To edit an existing exclusion rule, go to the BACKUP > Exclusions page in the Barracuda Backup web interface, and click Edit following the
exclusion rule you want to edit. Make the desired changes, then click Save.
To delete an exclusion rule, go to the BACKUP > Exclusions page in the Barracuda Backup web interface, and click Remove following the
exclusion rule you want to remove. Confirm that you want to remove the rule.

How to Create Directory-Level Exclusions
For Backup Agent data sources, you can create an Exclusion Rule inside of a specific directory, instead of the entire server or virtual machine
(VM).
Use the following steps to create a directory-level exclusion:
1. Log in to the Barracuda Backup web interface, and go to the Backup > Exclusions page.
2. Click Add an Exclusion; the Add Exclusion Rule page displays.
3. Enter a name to identify the exclusion rule, select whether to add the exclusion to reports, and whether to apply recursively to sub
directories.
4. In the Where to Exclude section, navigate to and select the directory to which to apply the Exclusion Rule. The Dash ( ) displays as
you expand directories, and the Check ( ) icon displays to the left of selected directories:
5. Scroll down to the What to Exclude section. Either select a preset expression from the Preset Expressions menu, or enter an
exclusion expression in the Expressions field, and then click Add:

6. Click Delete to the right of any expressions you want to exclude from the Exclusion Rule, and then click
Save to save your Exclusion Rule.

How to Exclude a Directory
You can create an Exclusion Rule to exclude a specific directory using the following steps:
1. Log in to the Barracuda Backup web interface, and go to the BACKUP > Exclusions page.
2. Click Add an Exclusion; the Add an Exclusion page displays.
3. Enter a name to identify the exclusion rule, select whether to add the exclusion to reports.
4. In the Where to Exclude section, navigate to and select the parent directory of the directory you want to exclude.
5. In the What to Exclude section, type the name of the directory you want to exclude; enter only the directory name, not the entire path,
and click Add.
6. For example to exclude the directory C:\Users\jane\Documents\temp and all sub directories:
a. Expand the agent source and file systems in the tree.
b. Expand C: in the tree.
c. Expand Users in the tree.
d. Expand jane in the tree.
e. Select Documents.
f. Type temp in the Expressions field, and click Add.
g. Click Save at the top of the page to save the exclusion rule.

Sample Exclusion Rules

Use Exclusion Rules to exclude files and file types from a backup. For best results, use exclusion rules rather than deselecting items on the
selections page.
If you do not want the exclusion to display in the Backup Report, clear Add Exclusions to Reports on the Exclusion Rule.
In this article, the following phrases are defined as:
Explicitly select – An item or folder is selected on the Selections page, and at least one item in the same directory is deliberately not
selected.
Click to view explicit selection...
Implicitly select – Any selected item on the Selections page where all other items in the same directory are also selected.
Click to view an implicit selection...

Sample 1. Set an Exclusion Rule on all Items in a Folder
1. Log in to the Barracuda Backup web interface, and go to the BACKUP > Schedules page.
2. Click Add a Schedule, and type Sample 1 Schedule as the Schedule Name.
3. In the Items to Back Up section, expand the Linux File Server data source, and select the etc folder:

4. In the Schedule Timeline section, select all days:
5. Click Save.
6. In Barracuda Backup, go to the BACKUP > Exclusions page, and click Add an Exclusion.
7. Complete the following details on the Add an Exclusion page:
a. Type Sample 1 Exclusion in the Exclusion Rule Name field.
b. Clear Add Exclusions to Reports.
c. Clear Apply recursively to subdirectories.
8. In the Where to Exclude section, select only the Linux File Server data source:

9. In the What to Exclude section, select Archived and compressed from the Preset Expressions menu, and click Add:
10. Click Save.
Results: All current and newly added data within the folder is backed up except for archived and compressed files.
Sample 2. Clear an item from a Schedule
1.

2. Click Edit to the right of Sample 1 Schedule.
3. Expand the Linux File Server data source, and clear the folder home:
4. Click Save.
Result: When the backup runs, all items in the folder are backed up based on the exclusions rule except for the content of the home folder. All
items in the same folder as the cleared item are now treated as explicit selections. New items are not backed up.
Sample 3. Explicitly Selected Item Deleted from the Data Source
2. Click Edit to the right of Sample 1 Schedule.
3. Clear and expand the Linux File Server data source, and explicitly select the intrd.img.old file:

4. On the Linux File Server data source, delete the intrd.img.old file from the server.
6. Click Run Backup Now to the right of Sample 1 Schedule.
Results: The deleted item displays as an error in the Backup Report and is not marked to age off as per the retention policy until the file is
deselected from the schedule, where the user is prompted to "keep or remove". An error also displays in the Backup Reports if a folder changes
to a file of the same name. If an explicitly selected folder becomes empty an error displays in the report.
Sample 4. Exclude a Folder and Back Up New Items
If you wish to exclude a folder and still back up new items, or exclude a folder that is causing errors during backup, add a new exclusion rule and
select the directory above the problem folder. Enter the name of the problem folder as the pattern. If you determine errors occur due only to the
agent accessing the folder, set the exclusion rule so it is not added to reports. In this example, exclude the folder cdrom.
1. Log in to the Barracuda Backup web interface, and go to the BACKUP > Exclusions page.
2. Click Add an Exclusion. Enter a name to represent the exclusion rule.
3. In the Where to Exclude section, expand and select Linux File Server > Backup Agent > File Systems:

4. In the What to Exclude section, type cdrom in the Expressions field, and click Add:
Results: The cdrom folder and all files and folders below it are not backed up.
Troubleshooting
Recursive Exclusions If an explicitly selected folder matches an exclusion rule, it is still

backed up. However, recursive exclusions applied to any folder abov
e an explicit selection (or to the entire source) still apply to the items
below the explicit selection. All exclusion rules that would normally
apply on the items below the explicit selection continue to apply.
Empty Folder If an explicitly selected folder is empty, or later becomes empty, it

shows up as an error in reports.

Symlinks and Mount Points If an explicitly selected folder changes to a mount point that the agent
is unable to follow, an error displays in the reports.
Windows:
Symlinks are not followed under File Systems.

Mount points are not followed under File Systems.
If a folder is explicitly selected and changes to a Symlink or
mount point that will not be followed, an error displays in the
report.
Linux:
Symlinks are not followed under File Systems.

Mount points for local filesystems are followed under
filesystems.
Mount points for special and network filesystems are not
followed under filesystems.
If a folder is explicitly selected and changes to a mount point or
Symlink that will not be followed, an error displays in the report.

Retention Policies Page

Configure retention policies for data stored on a Barracuda Backup appliance on the Backup > Retention Policies page. Be sure to configure
retention policies for your data. Not doing so means that some unwanted data will be moved across the Internet and stored, causing unnecessary
expense.
weekly, monthly, and yearly backups by creating data retention policies. Multiple retention policies can be created for files, data backed up by the
Barracuda Backup Agent (Exchange, SQL, System State), and email messages.
There are some template policies provided to assist you in creating your own retention policies. You can create one policy for all data sources on
a Barracuda Backup appliance or multiple policies that each include some subset of the data.
locations. Removed files that have been backed up using Network File Shares Protocol or SSHFS may be retained for a longer period of time,
according to the configuration. Otherwise, once your data has been purged, it is gone forever. Purging applies to historic file revisions only; your
current data is not impacted by a retention policy. If you wish to purge data immediately for a specific retention policy, go to the Backup >
Retention Policies page, and click Start Purge Process, and click Start Purge Process in the dialog that follows to confirm your selection.
Purging applies to historic file revisions only; your current data is never impacted by a retention policy.
Click Edit to the right of a retention policy to modify the retention timeline, and click Remove to delete a retention timeline.

Understanding Retention Policies

Use retention policies to define the length of time you retain historic data based on daily, weekly, monthly, or yearly time intervals. Barracuda
Backup retention policies can be created for different sets of data including virtual machines, data backed up by the Barracuda Backup Agent
(Exchange, SQL, Hyper-V, System State), and email messages.
Barracuda Backup Agent, VMware, and Network File Share Data
Data backed up using these methods retains revision data based on the date the file is removed. For example, if a file was backed up on January
1 and the retention policy is configured to hold onto data for 7 daily revisions, if the file is modified or removed at any point, the revision is held
onto for 7 additional days after this action.
To retain weekly, monthly, and yearly revisions, Barracuda Backup ages forward files that are not created specifically at the end of the week,
month, or year to be recoverable as part of these revisions.
Retention Policy
You can create one policy for all of the computers and data sources on Barracuda Backup or create multiple policies for each data source. Use
the Backup > Retention Policy page to define content retention rules:
Policy Name – Enter an identifying name for the policy

Items to Retain – Displays all data sources on the selected Barracuda Backup Server. Select all of the items you want to include in the
retention policy.
Items with no retention policy are retained forever on the local appliance.
Retention Timeline – Define how historic data is retained.
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 seven day periods beginning each month.
Timeline Templates – Select from the pre-defined templates which you can modify, or create your own custom timeline. The Re
visions Timeline and Retention Calendar display the timeline based on the selected template.
Revisions Timeline – Define how long to keep daily, weekly, monthly, and yearly backups.
Local and offsite means that revisions are stored both on the physical Barracuda Backup appliance and Barracuda
Cloud Storage or to another Barracuda Backup appliance. Set this value based on your business requirements.
Keeping revisions forever can affect your cloud storage requirements.
Keep all revisions for – Specify the number of day(s) to keep all content revisions, or select never or forever.
This features allows you to keep revisions when you have multiple backups per day. For example, you back
up your SQL Server hourly for 5 days giving you 120 revisions.
Keep daily revisions for – Specify how long to keep daily revisions. Specify a number of day(s), never, or forever.
Keep weekly revisions for – Specify how long to keep weekly revisions. Specify a number of week(s), never, or forever. Turn
on offsite only to use Barracuda Offsite Vaulting.
Keep monthly revisions for – Specify how long to keep monthly revisions. Specify a number of month(s), never, or forever.
Turn on offsite only to use Barracuda Offsite Vaulting.
Keep yearly revisions for – Specify how long to keep yearly revisions. Specify a number of years(s), never, or forever. Turn
on offsite only to use Barracuda Offsite Vaulting.

Offsite Vaulting
Offsite vaulting leverages Barracuda's replication technology to offload up to twelve monthly and seven yearly
revisions to an offsite location, freeing up disk space on your local Barracuda Backup Server. This feature maintains
your organization's compliance with long retention policies, allowing you to save more daily and weekly revisions. Note
that offsite vaulting is available for both Barracuda Cloud and box-to-box replication. For more information, see Unders
tanding Barracuda Offsite Vaulting.
Retention Calendar – Display the timeline based on the values in the Revisions Timeline. Click Show previous years to view
prior year retention timelines.
Email Messages Timeline (available for message-level backup only) – Specify the number of day(s), week(s), month(s), year
s(s), never, or forever to retain removed email messages.

How to Create 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
Create a Retention Policy
To set retention policies,
2. In the Items to Retain section, specify the data sources to which the retention policy applies; the Retention Timeline section displays.
Select a timeline template on which to base your retention policy, or specify your own revision timeline.
3. Click Save.
Set Removed Email Timeline
Specify 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.

Understanding Barracuda Offsite Vaulting

Offsite vaulting applies to file revisions only, not unique files. Offsite vaulting supports full SQL and Exchange backups, however,
unique log files are not supported.
Offsite vaulting leverages Barracuda's replication technology to offload up to twelve monthly and seven yearly
revisions to an offsite location, freeing up disk space on your local Barracuda Backup Server. This feature maintains
your organization's compliance with long retention policies, allowing you to save more daily and weekly revisions.
Note that offsite vaulting is available for both Barracuda Cloud and box-to-box replication. Offsite vaulting can be
used for 12 monthly and 7 yearly historical revisions; these revisions are retained at the end of each calendar month
and year.
Warning
Once offsite vaulting is enabled, it cannot be undone. If the feature is disabled, offsite vaulting will stop, however, the local Barracuda
Backup Server will not be repopulated with file revisions that have already been vaulted.
Initial Offsite Data Move
If you are already replicating data offsite and you enable offsite vaulting, the Barracuda Backup Server simply purges the relevant file revisions
from the local appliance; no data is transferred since it is already in the cloud. If you are not replicating data offsite and you enable offsite vaulting,
enable replication. Once the replication queue drains, the Barracuda Backup Server purges the local file revisions.
Set Up Offsite Vaulting
To specify offsite vaulting,
1. Log in to Barracuda Backup, and click on the Barracuda Backup appliance name in the left pane.
2. Go to the Backup > Retention Policies page.
3. Click the Edit Retention Policy ( ) icon to the right of the retention policy you want to configure monthly and/or yearly offsite
revisions.
4. Scroll down to the Retention Timeline section.
5. Select offsite only following weekly and/or monthly, and enter the associated time to keep the revisions:
Offsite Only
Monthly and/or yearly revisions sent offsite only are purged from the local Barracuda Backup Server, and all revisions outside
of this policy will be purged both locally and offsite.
6. Click Save to apply your changes.
Restore Offsite Vaulted Data
Use the Restore > Restore Browser to restore offsite vaulted data just as you would other data. Note that it may take an extended period of time
to recover the data as it must be downloaded as part of the restore process.

Creating Effective Retention Policies

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
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 Keep All Revisions Keep Daily Keep Weekly Keep Monthly Keep Yearly
Revisions Revisions Revisions Revisions
General Documents 5 days 1 week 1 month 1 year never
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 Never Never Never Never Never

Data
Exchange Data Never 2 weeks Never Never Never
Virtualization 1 day 2 weeks Never Never Never
SQL Server Never 1 month Never Never Never

Database
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.


Retention Policy Example

Use retention policies to define the length of time you retain historic data based on daily, weekly, monthly, or yearly time intervals. Think of
retention policies in terms of your ability to restore data backed up in the past. For example, you have a retention timeline that keeps daily
backups for five days, weekly backups for two weeks, monthly backups for six months, and yearly backups for one year:
A revision is created when the data being backed up is changed:
Daily revision is determined by the revision that is current at the end of each day;
Weekly revision is determined by the revision that is current on Sunday;
Monthly revision is determined by the revision on the last day of the month; and
Yearly is determined by the last day of the year.
For example, if a file changes every day Monday through Sunday, the revision that is current on Sunday becomes the weekly revision. If the last
time the document changes is on Friday, then that Friday revision becomes the weekly revision.
Change a Retention Policy
If you make changes to your retention policy, the updates take effect within 24 hours, at which time, any excess data based on your new policy
settings is removed from your device. Note that the removal process can take some time depending on the amount of data. View progress in the
Dashboard page.

Watched Files Page

This article applies to Barracuda Backup version 5.1 and earlier only.
The seldomly used Watched Files feature has been deprecated in versions 5.2, and will not be supported for new Barracuda
Backup Servers. Note that existing Watched File Rules will continue to function as expected.
Use this page to add files to watch on a particular Barracuda Backup Server. File watch rules are used to monitor and send email alerts when
specified files have not been changed often enough or appear smaller than expected. For example, an administrator could choose to receive an
alert if third-party backup software fails to process dump files or if the dump files appear to be of insufficient size. Use the BACKUP > Watched
Files page to add files to watch on a particular Barracuda Backup Server.
Click Add a File Watch, and enter the details described in the following table:
Field Description
Add File Watch Rule Name Enter a short description for the file watch rule.
Modified Time Threshold This section displays all data sources set up on the selected
Barracuda Backup Server. Select the items to which the watch rule is
to apply.
Modified Time Threshold Warning Turn on Warn if file is not modified at least once in, and specify
how frequently the file should change in hours, days, weeks, months,
or years.
Size Threshold Warning Turn on Warn if the size is not at least and enter the smallest
acceptable size for the file in bytes, kilobytes, megabytes, gigabytes,
or terabytes.
Click Save to save the watch rule, or click Cancel to close the page without saving changes.
Note that you can add file watch rules on network file share data sources only; you cannot add a file watch rule on agent data sources.
The ADMIN > Email Notifications page allows you to specify the email addresses that are to receive an email notification when files matching
the parameters in a file watch rule are detected. The emails are sent to those users who are configured to receive alerts.

Restore Page
Restore Browser Page
From the Restore > Restore Browser page you can restore data from the local Barracuda Backup appliance, from a remote Barracuda Backup
appliance that has been used to replicate that system, or from Barracuda Cloud Storage. Restores from the local Barracuda Backup appliance off
er the fastest restore times. Multiple methods are available to restore your backed up data. You can restore single files, individual email
messages, and entire systems.
All restores initiated from the Barracuda Backup web interface are restoring data that lives on the local Backup appliance. Only data
that does not exist on the local appliance, such as data that has been removed locally by the Offsite Vaulting feature, is restored
directly from the Barracuda Cloud.
See Also
VMware Server Recovery and Restoration

Microsoft SQL Server Database Recovery and Restoration
Microsoft Hyper-V Recovery and Restoration
Barracuda LiveBoot
Barracuda Cloud LiveBoot
Restore Browser
Restoring from Local and Offsite Backups
How to Recover Backed Up Data Using the Download Feature
How to Restore from a Replication Destination
Restoring Windows System State
How to Perform a Physical to Virtual Restore
On-Demand Purging
Recovering Data After a Ransomware Attack - Video
Related Article

LiveBoot Page
Use the Restore > LiveBoot page to instantly recover VMware virtual guest machines.
See Also
Understanding LiveBoot
Getting Started with LiveBoot
Understanding the LiveBoot Destination
How to Add a Virtual Machine to LiveBoot
How to Manage LiveBoot Virtual Machines
How to Restore a LiveBoot Virtual Machine to Production
Cloud LiveBoot Page
Use the Restore > Cloud LiveBoot page to boot VMware virtual guest systems and Microsoft Hyper-V virtual machines in the Barracuda Cloud.
Cloud LiveBoot is useful as a sandbox for testing purposes.
See Also
Understanding Cloud LiveBoot

Getting Started with Cloud LiveBoot

Understanding Cloud LiveBoot Interface Types
How to Add a Virtual Machine to Cloud LiveBoot
How to Manage Cloud LiveBoot Virtual Machines
How to Restore a Cloud LiveBoot Virtual Machine
How to Download or Destroy a Virtual Machine from Cloud LiveBoot
Troubleshooting Cloud LiveBoot

VMware Server Recovery and Restoration
In this Section

How to Restore a Virtual Machine to an Alternate VMware Host not available through the Barracuda Backup Service
Related Articles



This article refers to the Barracuda Backup Legacy Release firmware or newer, and supported versions of VMware and the
vSphere Data Recovery API.
Barracuda Backup utilizes the vSphere Data Recovery API to backup and restore the VMware Host configuration as well as VMware guests.
VMware host backup provides a comprehensive disaster recovery option for virtual machines and provides the ability to recover virtual machines
to any VMware host accessible by the Barracuda Backup appliance.
Use the Barracuda Backup Server web interface to restore VMware hosts, host configuration, or virtual machine images.
Use the following steps to restore a VMware data source:
1. Log in to the Barracuda Backup web interface, and go to the Restore > Restore Browser page.
2. Expand the VMware data source on the left, and click on the virtual machine you want to restore; all available revisions display.
3. Click Restore to the right of the revision to restore.
4. In the Restore dialog box, select the following options:
Restore to – Select Original Location
Overwrite – Turn On to overwrite existing data for this virtual machine at the source
5. Click Start Restoring.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and VMware and the vSphere Data Recovery API.
Barracuda Backup utilizes the vSphere Data Recovery API to protect the VMware guests at the host level. Barracuda Backup provides a
comprehensive disaster recovery option for virtual machines and provides the ability to recover virtual machines to any VMware host accessible
by the Barracuda Backup Server. Note that the VMware host being restored must have a VMware Disaster Recovery and Backup license
available from VMware.
Use the following steps to restore a virtual machine to a new location:
1. Log into the Barracuda Backup web interface, and go to the Restore > Restore Browser page.
2. Expand the VMware data source on the left, and click on the virtual machine you wish to restore; all available revisions display.
3. Click Restore to the right of the revision you wish to restore.
4. In the Restore dialog box, in the Restore to section, select the second radio button, and select the host from the drop-down menu.
5. If you are restoring to a vCenter, complete the following steps:
a. From the Datacenter drop-down menu, select the data center where you want to restore the virtual machine.
b. From the Host drop-down menu, select the desired restore host name.
c. From the Datastore drop-down menu, select the desired restore datastore.
6. To overwrite any existing data on the selected virtual machine at the source, turn on Overwrite.
7. Click Start Restoring.

How to Restore a Virtual Machine to an Alternate VMware Host not available through the Barracuda
Backup Service
This article refers to the Barracuda Backup Legacy Release firmware or newer, and VMware and the vSphere Data Recovery API.
Barracuda Backup utilizes the vSphere Data Recovery API to backup and restore the VMware Host configuration as well as VMware guests.
VMware host backup provides a comprehensive disaster recovery option for virtual machines and provides the ability to recover virtual machines
to any VMware host accessible by the Barracuda Backup Server. Note that the VMware host being restored must have a VMware Disaster
Recovery and Backup license available from VMware.
Use the following steps to restore a virtual machine to an alternate location:
1. Log into the Barracuda Backup web interface, and go to the Restore > Restore Browser page.
2. Expand the VMware data source on the left, and click on the virtual machine you want to restore; all available revisions display.
3. Click Restore to the right of the revision you want to restore.
4. In the Restore dialog box, in the Restore to section, select the third radio button, and enter the fully qualified domain name (FQDN) or
IP address of the VMware host where you want to restore the virtual machine:
5. Enter the VMware host username and password in the Authentication fields, and click Load Datacenters to view a list of datacenters
and datastores.
6. If you are restoring to a vCenter, complete the following:
a. From the Datacenter drop-down menu, select the data center where you want to restore the virtual machine.
b. From the Host drop-down menu, select the desired restore host name.
c. From the Datastore drop-down menu, select the desired restore datastore.
7. To overwrite any existing data on the selected virtual machine at the source, turn on Overwrite, and click Start Restoring.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and VMware® vSphere®, including VMware’s data
protection framework vStorage APIs for Data Protection (VADP) included with all licensed vSphere editions.
See also: VMware Data Recovery Backup and Restore Permissions.
Licenses Required for vStorage APIs for Data Protection
The vStorage APIs for Data Protection (VADP) are included with all licensed vSphere editions including Standard, Enterprise, and Enterprise
Plus. For additional information on licensing and VADP, refer to the VMware vSphere Storage API features on the VMware site.
Understanding vStorage APIs for Data Protection
Barracuda Backup can use VADP to back up vSphere virtual machines (VMs) without requiring the Backup Agent or
processing to be done inside each guest VM on the ESX host. This offloads the backup processing from ESX hosts
and reduces cost by allowing each ESX host to run more VMs.
VADP leverages the snapshot capabilities of vSphere, enabling backup across a storage area network (SAN)
without requiring VM downtime. This allows backups to be performed at any time without disrupting the VMs or
requiring extended backup windows and application downtime.


This article refers to the Barracuda Backup firmware version 6.3.04 and higher, and supported versions of VMWare ESX/ESXi with
the VMware license which includes access to vSphere Data Recovery API. Barracuda LiveBoot (local) currently does not support
Microsoft Hyper-V; to boot Microsoft Hyper-V virtual machines (VMs), use Barracuda Cloud LiveBoot.
See Also: How to vMotion a LiveBooted Virtual Machine from Barracuda Backup
Use Barracuda LiveBoot to instantly recover VMware virtual guest machines. In the event of a failure with your primary storage system,
Barracuda Backup acts as the datastore for your VMware ESXi server. You can recover any revision of a virtual guest machine within your
retention policy, and users can quickly access their files and applications directly from the deduplicated content stored within Barracuda Backup.
Additionally, you can use LiveBoot to granularly recover files and application-level items from applications such as Microsoft Exchange, Microsoft
SQL, and Microsoft SharePoint.
Barracuda Cloud LiveBoot supports a maximum of four virtual disks per guest VM.
Restore a Virtual Machine Using LiveBoot
Use the following steps to recover VMware VMs using LiveBoot:
1. Log in to the Barracuda Backup web interface, and go to Restore > LiveBoot.
2. In the Destination column, select the datacenter or hostname where you want to restore your VM.
3. In the Actions column, click Start.
Recover Virtual Machine to Production
Once you have recovered your VM using LiveBoot, there are two options available to you to move the VM image off of the Barracuda Backup
device and onto your production datastore. These options depend on your VMware vSphere licensing. If a vSphere vMotion license is present,
you can use vMotion to perform a live datastore migration of the VM from Barracuda Backup storage to your production storage. If a vSphere
vMotion license is not available, the VM must be shutdown first before a datastore migration can be performed.
1. Once the boot process is complete, the VM is powered on and ready to use.
2. Using your vSphere client, you can view your recovered VM:
Download a Virtual Machine
1. Log in to the VM and stop the virtual guest machine.

2. Log in to Barracuda Backup.
3. Go to Restore > LiveBoot, and click Download in the Actions column for the associated VM.
4. Save the file to your local system.

Destroy a Virtual Machine
You can permanently delete all changes made since the VM was started using the following steps:

2. Go to Restore > LiveBoot, and click Destroy in the Actions column for the associated VM.
3. In the confirmation dialog box, click Destroy.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and vmWare® vCenter vSphere vMotion.
This article assumes you have completed the steps to recover a virtual machine (VM) using Barracuda LiveBoot and the VM has booted
successfully. Otherwise, refer to the article How to Restore VMware Guest Systems Using LiveBoot to complete the LiveBoot process.
Use the following steps to LiveBoot and vMotion a VM from Barracuda Backup:
1. Log in to vCenter with your vSphere client.

2. Right-click on the LiveBooted virtual machine, and click Migrate:
3. In the Migrate Virtual Machine page, select Change datastore:

4. Click Next. In the Storage page, select the destination storage:
5. Click Next, and then click Finish in the Ready to Complete page.
6. In vCenter, the Relocate virtual machine task displays under Recent Tasks, and the status displays as Completed:

6.
7. Click on the host where the VM was running, and click the Configuration tab.
8. Right-click the LiveBooted NFS datastore, and click Unmount.

In this Section

This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange
Server 2013 and higher.
This article assumes the Microsoft Exchange Server is installed and configured. This article describes how to restore Microsoft
Exchange Server 2013 and higher using a Recovery Database.
Recovery Database
If you do not create a recovery mailbox database, Barracuda Backup creates one and places it in the default Exchange installation
location. If you want to create a recovery mailbox database in a different location, use the following Exchange PowerShell command,
replacing the bracketed variables with the actual database and server names, and the path with your desired location:
New-MailboxDatabase -Recovery -Name "[databasename] - Recovery" -Server [servername] -EdbFilePath

"R:\[databasename] - Recovery\[databasename] - Recovery.edb" -LogFolderPath "R:\[databasename] -
Recovery"
The recovery mailbox database must be named exactly as indicated above including the spaces, for example: Mailbox Database
1234 - Recovery, otherwise, Barracuda Backup ignores it and creates one in the default Exchange installation location.
Step 1. Barracuda Backup Setup
1. Log in to Barracuda Backup, and select the Barracuda Backup appliance that contains the Exchange Server backups you want to
restore.
2. Go to the Restore > Restore Browser page, and s elect the Microsoft Exchange data source; the backed up Exchange
databases display.
3. To restore the latest backed up database, click Restore. The Restore window displays. In the Restore to section, select Original
Location.
If restoring to a server with a different IP address, select the associated Exchange Server from the drop-down menu.
4. Next to the Method section, select Restore to an Exchange Recovery Storage Group / Database:
5. Click Start Restore. Once the restore is complete, go to the Reports > Restore page and verify the restore completed
successfully.
Step 2. Exchange Management Shell
1. Log in to the Exchange Server as the administrator, and open the Exchange Management Shell (EMS).
2. Mount the Recovery Database using the following command:
In the following commands, recoverydbname represents the name of the recovery database created by the restore job;
because the name includes spaces, it must be enclosed in quotes.

Mount-Database -Identity 'recoverydbname'

3. To verify the Recovery Database has the necessary mailbox(es), you can list the mailboxes within the database using the following
command:
Get-MailboxStatistics -Database 'recoverydbname'
4. You can now restore the data.
Each Exchange Server can have only one recovery database mounted at a time.
Step 3a. Restore Exchange Mailboxes
Once you mount the recovery database, you can select to restore a single mailbox.
Email and other items newer than the restored data are unaffected by the mailbox restore.
Use the steps in this section to restore all email to a single mailbox. Note that you must complete Step 1 and Step 2
above before you can restore a single Exchange mailbox.
You must have the name of the restored recovery database to complete these steps, for example, "[databasename] - Recovery"
.
1. Log in to the Exchange Server as the administrator, and select to run the Exchange Management Shell as
the administrator; the console opens.
2. Enter the following command at the prompt, and then press Enter:
New-MailboxRestoreRequest -SourceDatabase 'recoverydbname' -SourceStoreMailbox
'user' -TargetMailbox 'targetmailboxname' –AllowLegacyDNMismatch
Where user is the DisplayName of the user account you want to restore, recoverydbname is the name of the recovery
database created by the restore job, and targetmailboxname is the DisplayName of the mailbox where the mail is to be
restored; if a name includes spaces, enclose the name in quotes.
For additional examples and parameters, refer to the Microsoft TechNet article New-MailboxRestoreRequest.
3. Verify with the user that the mailbox has been restored.
4. Once you are done restoring mailboxes, enter the following command to remove the recovery database, and then press Enter:
Remove-MailboxDatabase -Identity 'recoverydbname'
A prompt displays indicating the recovery database has been removed. You can now manually remove the associated files.

Step 3b. Restore Exchange Mailbox Folders Including Contacts, Calendars, Notes
Once you mount the recovery database, you can select to restore specific folders from a mailbox such as the Inbox, Contacts, Calendar, or
Notes. Use the steps in this section to restore a specific Folder of items back to a single mailbox. Note that you must complete Step 1 and Step 2
above before you can perform this restore.
You must have the name of the restored recovery database to complete the steps in this section, for example, "[databasename] -
Recovery".
1. Log in to the Exchange Server as the administrator, and run the Exchange Management Shell as the administrator; the console opens.
2. At the prompt, type the following command, and then press Enter:
New-MailboxRestoreRequest -SourceDatabase 'recoverydbname' -SourceStoreMailbox 'user' -TargetMailbox
'targetmailboxname' –AllowLegacyDNMismatch –IncludeFolders Contacts –TargetRootFolder 'temprestorefol
der'
Where user is the DisplayName of the user account you want to restore, recoverydbname is the name of the recovery
database created by the restore job, and targetmailboxname is the DisplayName of the mailbox where the mail is to be
restored; if a name includes spaces, enclose the name in quotes.
In this example the user’s Contacts are restored back to the temporary folder temprestorefolder . From here you can
select specific contacts to recover from the temporary folder as opposed to having all contacts restored back to the primary
Contacts folder.
You can also restore other useful Folders including: Calendar, Notes, Tasks. This method can also restore individual
subdirectories such as a folder within the Inbox.
3. Verify with the user that the mailbox items have been restored. For example:

4. Once you are done restoring specific folders from a mailbox, type the following command to remove the recovery database, and then
press Enter:


This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010.
This article assumes the Microsoft Exchange Server is installed and configured. This article describes how to restore an Exchange
2010 Server by overwriting an existing database or to an original location. You can also restore to a Recovery Storage Group
(RSG).
Warning
This option overwrites all existing data. If you do not want to overwrite the database, see Restore to a Recovery Storage Group.
Take caution when overwriting an existing database; Barracuda Networks highly recommends restoring to a separate recovery
database except in cases of extreme data loss or when performing disaster recovery.
If you do not want to restore your Exchange Server by overwriting the existing database, you can select a different option:
Restore Exchange 2010 to Recovery Database

Restore Single Exchange 2010 Mailbox
Restore All Exchange 2010 Mailboxes
See Restore to a Recovery Storage Group for more information on these options.
Step 1. Allow Database Restore
1. Log in to your Exchange Server as the administrator, and open the Exchange Management Console (EMC) from Start > All Programs >
Microsoft Exchange Server > Exchange Management Console.
2. In the left pane, expand Microsoft Exchange > Microsoft Exchange On-Premises > Organization
Configuration, and click Mailbox:
3. In the center pane, right-click the mailbox database you want to overwrite with the restore, and click Properti
es.
4. In the Mailbox Database dialog box, click the Maintenance tab, and select This database can be
overwritten by a restore:

5. Click Apply, and then click OK to close the dialog box.

6. Right-click the database, and click Unmount.
Step 2. Specify Barracuda Backup Restore Settings
1. Log in to Barracuda Backup web interface, and select the associated Barracuda Backup Server in the left pane.
2. Go to Restore > Restore Browser. Locate the Exchange 2010 Server, and click Restore.
3. In the Restore dialog box, choose the Restore to location:
Original Location
Select an IP Address from the available servers
Enter an IP Address or FQDN
4. Choose the Restore method as Restore normally, and click Start Restore.

5. Go to the Reports > Restore page to monitor the restore progress.
Step 3. Mount the Database
Once the restore is complete, use the following steps to mount the database.
1. Log in to the target Exchange 2010 Server as the Administrator, and open the EMC.
Configuration, and click Mailbox.
3. In the center pane, click the Mailbox Database that was restored, and in the right pane, click Mount
Database.
4. The database should now be ready to use; ensure users can access their mailboxes.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010 and 2010
SP1 except where noted.
This article assumes the Microsoft Exchange Server is installed and configured. This article describes how to restore a Microsoft
Exchange 2010 Server to a Recovery Storage Group. You can also restore a Microsoft Exchange 2010 Server by overwriting an
existing database or restoring to an original location.
Recovery Storage Group

If you do not create a recovery mailbox database, Barracuda Backup creates one and places it in the default Exchange installation
location. If you want to create a recovery mailbox database in a different location, use the following Exchange PowerShell command,
replacing the bracketed variables with the actual database and server names and the path with your desired location:
New-MailboxDatabase -Recovery -Name "[databasename] - Recovery" -Server [servername] -EdbFilePath

"R:\[databasename] - Recovery\[databasename] - Recovery.edb" -LogFolderPath "R:\[databasename] -
Recovery"
The recovery mailbox database must be named exactly as indicated above including the spaces, for example: "Mailbox Database 1234
- Recovery". If it is named anything else Barracuda Backup will ignore it and create one in the default Exchange installation location.
Step 1. Barracuda Backup Setup
1. Log in to Barracuda Backup, and select the Barracuda Backup appliance that contains the Microsoft Exchange 2010 Server backups you
want to restore.
2. Go to the Restore > Restore Browser page, and select the Microsoft Exchange data source; the backed up Exchange 2010 databases
display.
3. To restore the latest backed up database, click Restore. The Restore window displays. In the Restore to section, select Original
Location.
If restoring to a server with a different IP address, from the drop down menu, select the associated Exchange Server from the
list.
4. Next to the Method section, select Restore to an Exchange Recovery Storage Group / Database:
Step 2. Microsoft Exchange 2010 Server
1. Log in to the Exchange 2010 Server as the administrator, and open the Exchange Management Console
(EMC) from Start > All Programs > Microsoft Exchange Server > Exchange Management Console .
2.

Configuration, and click Mailbox:
3. In the center pane, click the restored recovery database, and in the right pane, click Mount Database. You can now restore individual
mailboxes.
Each Exchange 2010 server can have only ONE recovery database mounted at a time.
Step 3. Restore Microsoft Exchange 2010 Mailboxes
Once you mount the restored database, you can select to restore a single mailbox or all mailboxes.
Email and appointments newer than the restored data are unaffected by the mailbox restore.
Exchange 2010 (Prior to Exchange 2010 SP1)Option 1. Restore a Single Mailbox
Use the steps in this option to restore all email to a single mailbox. Note that you must complete Step 1 and Step 2 above before you can restore
a single Exchange mailbox.
You must have the name of the restored recovery database to complete these steps. The recovery database usually has the same
name as the mailbox database appended with -Recovery.
1. Log in to the Exchange 2010 Server as the administrator, and select to run the Exchange Management Shell as the administrator; the
console opens.
Restore-Mailbox -Identity user -RecoveryDatabase recoverydbname
Where user is the name of the user account you want to restore, and recoverydbname is the name of the recovery
database created by the restore job; if a name includes spaces, enclose the name in double quotes (" ").
For additional examples and parameters, refer to the Microsoft TechNet article Restore-Mailbox.
3. Type Y and press Enter to confirm the restore operation. Once the operation is complete, the Exchange
Management Shell prompt displays.
4. Ask the user to verify the mailbox has been restored.
5. Once you are done restoring mailboxes, type the following command, and then press Enter:
A prompt displays indicating the recovery database has been removed. You can now manually
remove the associated files.

Option 2. Restore All Mailboxes
Use the steps in this option to restore all email to all mailboxes that exist in the specified database as well as the restored recovery database.
Note that you must complete Step 1 and Step 2 above before you can restore an Exchange mailbox.
You must have the name of the restored recovery database to complete this option. The recovery database usually has the same name
as the mailbox database appended with -Recovery.
console opens.
Warning
This option restores email to all user accounts that exist in the dbname database as well as the recovery database.
Get-Mailbox -Database dbname | Restore-Mailbox -RecoveryDatabase recoverydbname
Where dbname is the name of the mailbox database account to which to restore, and recoverydbname is the name of the
recovery database created by the restore job; if a name includes spaces, enclose the name in double quotes (" ").
3. Type A and press Enter to confirm the restore operation. Once the operation is complete, the Exchange Management Shell prompt
displays.
4. Ask users to verify mailboxes have been restored.
5. Once you are done, type the following command, and then press Enter:
Exchange 2010 (Exchange 2010 SP1 and Later)Option 1. Restore a Single Mailbox
Use the steps in this option to restore all email to a single mailbox. Note that you must complete Step 1 and Step 2 above before you can restore
a single Exchange mailbox.
You must have the name of the restored recovery database to complete these steps. The recovery database usually has the same
name as the mailbox database appended with -Recovery .
console opens.
New-MailboxRestoreRequest -SourceDatabase 'recoverydbname' -SourceStoreMailbox 'user' -TargetMailbox
'targetmailboxname' –AllowLegacyDNMismatch
Where user is the name of the user account you want to restore, recoverydbname is the name of the recovery database
created by the restore job, and targetmailboxname is the name of the mailbox where the mail is to be restored; if a name
includes spaces, enclose the name in double quotes (" ").
3. Ask the user to verify the mailbox has been restored.

4. Once you are done restoring mailboxes, type the following command, and then press Enter:
Option 2. Restore All Mailboxes
Use the steps in this option to restore all email to all mailboxes that exist in the restored recovery database. Note that you must complete Step 1
and Step 2 above before you can restore an Exchange mailbox.
You must have the name of the restored recovery database to complete this option. The recovery database usually has the same name
as the mailbox database appended with -Recovery.

console opens.
Warning
This option restores email to all user accounts that exist in the recovery database.
foreach($mailbox in Get-MailboxStatistics -Database recoverydbname) {New-MailboxRestoreRequest
-SourceDatabase recoverydbname -SourceStoreMailbox $mailbox.DisplayName -TargetMailbox $mailbox.Displ
ayName}
Where recoverydbname is the name of the recovery database created by the restore job; if the name includes spaces,
enclose the name in double quotes (" ").
You can enter the command Get-MailboxRestoreRequest to view restore status.
3. Ask users to verify mailboxes have been restored.

4. Once you are done, type the following command, and then press Enter:

Microsoft SQL Server Database Recovery and Restoration
In this Section

Related Articles


Restore a SQL User Database
When you request the restore of a Microsoft SQL Server user database, Barracuda Backup performs all of the restores required to get to the
desired date, as follows:
Restore a full backup of the SQL Server database

Restore the incremental backups in the order in which they were created
In other words, if you want to restore the database to a certain date, simply select the date and that database, and Barracuda Backup restores all
intermediate required database revisions.
ToUse the following steps to restore a Microsoft SQL user database,
1. On the Restore > Restore Browser page, select the day and time from which you want to restore.
2. Select the data source from which you want to restore.
3. Select the database(s) to restore, and click Restore.
Restore a SQL Master Database
If the master database becomes unusable, it must be restored from a previous SQL Dump or backup. All changes made to the master database
after the last backup or dump are lost when the dump is reloaded, and therefore must be reapplied.
A damaged master database is evident by the failure of the SQL Server to start, by segmentation faults, or by input/output errors. The
procedure used to recover a damaged master database is different from the procedure used to recover user databases. If the master
database becomes unusable, it must be restored from a previous SQL Dump or back up. All changes made to the master database
after the last backup or dump are lost when the dump is reloaded and therefore must be reapplied. It is strongly recommended that the
master database be backed up each time it is changed.
Use the following steps to recover a damaged master database,
1. Verify that the Barracuda Backup Agent is installed on the local machine.
2. Stop the SQL Server Services using the SQL Server Enterprise Manager.
3. Rebuild the master database; refer to Microsoft Developer Network (MSDN) for detailed procedures for your version of SQL.
4. Initiate Single User Restore Mode on the SQL database by entering the following from a command prompt; leave the window open after
executing the command:
CD \program files\microsoft sql server\<sql version>\mssql\binn
sqlservr -c -m (SQL 7)
sqlservr -c -m -s %<Named Instance>% (SQL 8)
5. After you complete the restore, remove the -m before you restart the server instance in the normal multi-user mode:
CD \program files\microsoft sql server\<sql version>\mssql\binn
sqlservr (SQL 7)
sqlservr -s %<Named Instance>% (SQL 8)
6. If login IDs or devices have been added to or dropped from the master database since the last backup, those changes must be
reapplied. Restart the server and reapply the changes manually or from saved batch files.
7. If any databases have been created, expanded, or shrunk since the last dump of the master, those databases must be dropped and then
restored. Refer to http://msdn.microsoft.com for detailed procedures for your version of SQL.
8. Close the command prompt.
9. Restart the SQL Service using SQL Enterprise Manager.
Restore a SQL SharePoint Database
Use the following steps to restore a SQL SharePoint database:
1. Start the Windows SharePoint Services VSS Writer service.

2. Start the Volume Shadow Copy service.
3. Shut down any web applications whose content is being restored.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server 2005 and 2008.
Step 1. Set Microsoft SQL Server to Single User Mode
1. Log in to the SQL server as the administrator.

2. Go to Administrative Tools > Services, right-click on the service SQL Server (MSSQLSERVER), and click Stop.
3. Double-click SQL Server (MSSQLSERVER) to open the Service Properties dialog box.
4. Click the General tab, and in the Start parameters field, type: -c -m
5. Click Start in the General tab to place the server in single user mode, and then click OK to close the dialog box.
Step 2. Stop Services
1. In the Services window, right-click on the service SQL Server Agent (MSSQLSERVER), and click Stop.
2. In the Services window, right-click on the service SQL Server Reporting (MSSQLSERVER) service, and click Stop:

Step 3. Restore the Database
1. Log in to Barracuda Backup, go to the Restore > Restore Browser page.

2. Click Restore next to the Microsoft SQL Server instance to restore.
3. In the Restore dialog box, select to restore to the original instance or a new instance, and click Start Restore.
Step 4. Set Microsoft SQL Server to Multi-User Mode
1. Log in to the SQL server as the administrator.

2. Go to Administrative Tools > Services, right-click on the following services, and click Start:
SQL Server (MSSQLSERVER)
SQL Server Agent (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)


This article refers to Barracuda Backup Legacy Release firmware and higher, and Microsoft SQL Server 2005 SP1 or higher
databases using Microsoft SQL Server Management Studio.
Flat File
This article describes how to restore a SQL database to a point-in-time, and then restore the database to working condition using SQL
Management Studio. Before completing this solution, you must first Restore the Microsoft Database to a Flat File.
Use the following steps to restore the database:
1. Open Microsoft SQL Server Management Studio, and navigate to Databases:
2. Right-click Databases, and click Restore Database. In the Source for restore section, select From Device,
and click the browse button:
3. Click Add in the Specify Backup window. Browse to the location of your recently restored flat files. Choose
the Full backup file which should be the first backup file in the list:

4. Click OK; the Specify Backup window displays:
5. Click OK. In the Destination for restore section, select the database to which you wish to restore, and in

5.
the Select the backup sets to restore section, select the backup file you selected above in step 3:
6. In the left pane, click Options, and select the following:

In the Restore options section, select Overwrite the existing database (WITH REPLACE), and leave the other options
unselected.
In the Recovery state section, select Leave the database non-operational, and do not roll back uncommited transactions.
Additional transaction logs can be restored. (RESTORE WITH NORECOVERY):
7. Click OK to perform the restore.

8. Complete these steps for each incremental backup file, including the .tm file, until you reach the incremental file containing the
point-in-time file to which you wish to restore.
9. A "Restoring" message displays; you can now proceed with the next section, Step 2. Restoring to a Point-in-Time.
Step 2. Restore to a Point-in-Time
Use the following steps to restore the last incremental file containing the point-in-time:
1. In Microsoft SQL Server Management Studio, right-click Databases, and click Restore Database.
2. In the Source for restore section, select From Device, and click the browse button.
3. Click Add in the Specify Backup window. Browse to the location of your recently restored flat files, select the

3.
incremental backup file containing the point-in-time to restore to, and click OK.
4. Click OK in the Specify Backup window. In the Select the backup sets to restore section, check the backup file you added in the
previous step.
5. In the Destination for restore section, select the database to which to restore:
6. In the Destination for restore section, click the browse button following To a point in time; the Point in
time restore window displays.
7. Select a specific date and time, and choose the date and time to which to restore:
8. Click OK. In the left pane, click Options, and make the following selections:
In the Restore options section, select Overwrite the existing database, and leave the other options unselected.
In the Recovery state section, select Leave the database ready to use by rolling back uncommitted transactions.
Additional transaction logs can be restored. (RESTORE WITH RECOVERY):

9. Click OK to perform the restore. the restored database should display with only the changes up to the specified point-in-time.


This article refers to Barracuda Backup version 6.2 and higher, and Microsoft SQL Server 2005 SP1 or higher databases using
Microsoft SQL Server Management Studio.
In Barracuda Backup version 6.2 and earlier, you can restore a SQL database—backed up using VDI—to a flat file by
editing the Barracuda Backup Agent's configuration. A flat file allows you to import the database manually using SQL
Management Studio.
In Barracuda Backup version 6.3 and higher, you can perform a flat file restore of a database backed up using VDI directly
from the Barracuda Backup Restore web interface.
For more information about Microsoft SQL Server VSS and VDI backups, see the following articles:

Barracuda Backup Version 6.3 and Higher
This section assumes that the Microsoft SQL Server database was backed up using VDI. Microsoft SQL Server 2005 and 2008 databases use
VDI by default. Microsoft SQL 2012 and higher databases use VSS by default; for information on switching to VDI, see How to Enable VDI
1. Log in to Barracuda Backup, and go to Restore > Restore Browser.

2. Drill down to and select the database revision to restore, and click Restore.
3. In the Restore dialog, select Original Location under Restore to if you plan to restore the database back to the original server, then
select Restore to file system as a flat file under Method:
4. Click Start Restore. You can view the status of your restore by clicking Reports > Restore.
5. Verify that your database was successfully restored to the target system:
6. The database is restored down to the server as a .bak file. If the restore is from an incremental backup, each backup has a separate .ba
k file that you can import back into SQL.
Step 2. Restore a Flat File Using SQL Management Studio
Once you restore the flat file, you can elect to Restore the Microsoft SQL Database to a Point-In-Time.
Use the following steps to restore the flat file using SQL Management Studio.
1. After connecting to the appropriate instance of the Microsoft SQL Server Database Engine, in Object Explorer, click the server name to
expand the server tree.
2. Expand Databases, and, depending on the database, either select a user database or expand System Databases and select a system
database.
3.

3. Right-click the database, point to Tasks, and click Restore.

4. Click the type of restore operation you want (Database, Files and Filegroups, or Transaction Log). The corresponding restore dialog
box displays.
5. On the General page, in the Restore source section, click From device.
6. Click browse for the From device text box; the Specify Backup dialog box displays.
7. From the Backup media menu, select Backup Device, and click Add; the Select Backup Device dialog displays.
8. In the Backup device menu, select the device you want to use for the restore operation.
Barracuda Backup Version 6.2

This section assumes that the Microsoft SQL Server database was backed up using VDI. Microsoft SQL Server 2005 and 2008 databases use
VDI by default. Microsoft SQL 2012 and higher databases use VSS by default; for information on switching to VDI, see How to Enable VDI
Step 1. Modify the Agent Configuration File
1. On the Microsoft SQL Server where you installed the Barracuda Backup Agent, open Services.
3. Open the config.ini file in a text editor such as Notepad; the file is located in the following directory:
/Program Files/Barracuda/Barracuda Backup Agent/config/config.ini
4. Add the following lines to the end of the file, where path to file represents the restore path:
[Microsoft SQL Server Agent]
restoreToFilePath=path to file
For example:

Use the following steps to restore the database normally through the Barracuda Restore Browser to the path specified in Step 1. Modify the Agent
Configuration File:
1. Log in to Barracuda Backup, and go to Restore > Restore Browser.

2. Drill down to and select the database revision to restore, and click Restore.
3. In the Restore dialog, select Original Location or select the third option and type the IP address of the destination server:

There is no need to select an Instance because this is a flat file restore.
4. Click Start Restore.

5. The database is restored down to the server as a .bak file. If the restore is from an incremental backup, each backup has a separate .ba
k file that can be imported back into SQL.
Step 3. Restore a Flat File into SQL Management Studio
Restoring to a Point-in-Time
Once you create the flat file, you can select to restore the Microsoft SQL Database to a Point-in-Time.
Use the following steps to restore the flat file into SQL Management Studio:
1. After connecting to the appropriate instance of the Microsoft SQL Server Database Engine, in Object Explorer, click the server name to
expand the server tree.
database.
3. Right-click the database, point to Tasks, and then click Restore.
4. Click the type of restore operation you want (Database, Files and Filegroups, or Transaction Log). The corresponding restore dialog
box opens.
5. On the General page, in the Restore source section, click From device.
6. Click the browse button for the From device text box; the Specify Backup dialog box displays.
7. From the Backup media menu, select Backup Device, and click Add; the Select Backup Device dialog opens.
8. In the Backup device menu, select the device you want to use for the restore operation.
You can now restore a SQL database to a point-in-time.


This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server 2012 and above databases.
Microsoft VSS is the default backup method for Microsoft SQL 2012 and above. This article applies to customers backing up Microsoft
SQL 2012 and above databases using Microsoft VSS. With Microsoft VSS, Barracuda Backup performs full and differential database
backups.
Use the following steps to restore a Microsoft SQL Server 2012 or higher database:
1. Log in to the Barracuda Backup web interface or local UI, go to the Restore > Restore Browser page. Select and expand the SQL
server data source in the left pane:
2. Click Microsoft SQL in the Contents list, and select the Instance:
3. Click the database to be restored to see the available revisions:
4. Click Restore to the right of the database to restore; the Restore dialog box displays:

Understanding the Restore Dialog Options
Restore to is the Destination Server for the restore location. Note that the restore location must be running the same version
of SQL Server and the Barracuda Backup Agent must be installed on the location. There are three options to restore to:
Original Location is the original server where the backup came from.
From the drop-down menu, select a different server currently added as a Barracuda Backup data source.
In the restore field, enter the fully qualified domain name (FQDN) or IP address of a server currently on the network
Database name displays, by default, the selected database name:
If you are restoring to Original Location, and you want to overwrite the current database, do not change this field.
If you are restoring to an Alternate Location and you do not want to override the original database, enter a new name
for the database in the Database name field.
Instance is the database instance:
Original Location is the name of the Instance under which the database resides.
Alternate Location is a different instance on the target server to which to restore the database.
Method is the restore method:
Select Restore normally to restore to the original location, and write the .mdf and .ldf files back to that location.
Select Restore to an alternate location to write the .mdf and .ldf files to a different file path that exists on the source
server. Enter the path in the associated field, for example, E:\restore. This option must be used if you select to chang
e the database name.
Select Restore to file system to restore a full database to a file (.mdf/.ldf). Enter the restore file path in the associated field,
or leave the default value, for example, C:\Microsoft_SQL_Restore_<date>.
5. Once you select the location, instance, and method, click Start Restore. Once the restore is complete, the Success dialo
g displays; click OK to close the dialog box.
6.

6. Restore details are available on the Reports > Restore page:


This article refers to version 6.3 and higher, and Microsoft SQL Server 2012 and above databases.
Use the following steps to restore a Microsoft SQL Server 2012 or higher database to a file system:
1. Log in to the Barracuda Backup web interface or local UI, go to the Restore > Restore Browser page. Select and expand the SQL
server data source in the left pane.
2. Click Microsoft SQL in the Contents list, and select the Instance:
3. Click the database to be restored to see the available revisions:
4. Click Restore to the right of the database to restore; the Restore dialog box displays. Set the following options:
a. Restore to – Select Original Location
b. Database name – Do not change this field
c. Instance – Select Original Instance
d. Method – Select Restore to file system to restore a full database to a file (.mdf/.ldf). Enter the restore file path in the
associated field, or leave the default value:

e.
If you specify a name that is the same as an existing database on the target server, the restore always overwrites the
database on that server, even when restoring to an alternate path.
Flat file restores can only be completed on individual databases. Use an alternate name if you do not want to
overwrite the existing database,
5. Click Start Restore. Once the restore is complete, the Success dialog displays; click OK to close the dialog box.
6. Open Microsoft SQL Server Management Studio, right-click Databases, and click Attach:
7. The Attach Databases dialog box displays. Click Add:

8. Browse to and select the restored .mdf file:

9. Click OK to attach the database:

10. Click OK to close the dialog box.

Microsoft Hyper-V Recovery and Restoration
In this Section

This article refers to the Barracuda Backup Legacy Release firmware or newer, and supported versions of Microsoft Hyper-V.
This article assumes Hyper-V is installed and configured on the restore destination server.
Microsoft does not support running Windows Server 2008/2008 R2 on Hyper-V Gen 2 virtual machines. Therefore, Windows Server
2008/2008 R2 physical machines with UEFI cannot be restored to Hyper-V.
Use the following steps to restore a Hyper-V virtual machine (VM):
The original VM must not exist on the host when restoring; therefore, you must remove or export the original VM from the host.
1. Log in to the Barracuda Backup web interface, select the associated Barracuda Backup Server in the left pane, and go to the Restore >
Restore Browser page.
2. Select the Hyper-V source that contains the VM you want to restore.
3. Drill down into the Hyper-V source and locate the VM you want to restore.
4. Click Restore to the right of the VM.
5. In the Restore dialog box, configure the restoration options:
a. Restore to:
i. Original Location – Restore the VM to the original host where it was backed up
ii. Drop-down list – Select a different source already added to the Barracuda Backup where you want to restore the VM
iii. Other hostname or IP – Enter a different source you want to add to the Barracuda Backup where you want to restore
the VM
b. Method:
i. Restore normally – Restores and registers the VM using the same file path it was backed up with
ii. Restore to an alternate location – Restores the VM to a different file path that you specify
iii. Restore to file system – Restores the VM to a flat file that you can later import into Hyper-V
Note that in firmware version 6.2.04 you can only restore to the original location.
6. Once you select the Restore to and Method options, click Start Restore.
7. Go to the Reports > Restore page to view the restore operation progress.
8. Once the restore is complete, log in to Hyper-V, locate and right-click the VM, and click Start to start the server:


In this Section
How to Restore a Microsoft Server 2008 R2 Active Directory Object from the Active Directory Recycle Bin

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft® Active Directory (AD) on Microsoft
Windows Server ® 2012. For information on backing up the AD, refer to How to Back Up Microsoft Active Directory.
Important
Use the following steps to restore an AD Object from the AD Recycle Bin:
1. Log in to the Windows Server 2012 as the administrator.

2. Go to Start, and type dsac.exe to open the ADAC, or in Server Manager, click Tools, and then click Active Directory Administrative
Center.
3. In the left pane, click on the target Server name; a Deleted Objects container displays in the center pane:
Deleted Objects Container

If the Deleted Objects container does not display, right-click on the Server name in the left pane to enable the container.
4. Double-click the Deleted Objects container to view a list of deleted items which can be restored.
5. Right-click on the user to restore, and click Restore:

6. Verify the user has been restored.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft® Windows Server® 2012. For
information on backing up the Active Directory (AD), refer to How to Back Up Microsoft Active Directory.
Important
Warning
Once you enable AD Recycle Bin in your environment, you cannot disable it.
Requirements
To manage the Recycle Bin feature through a user interface, you must install Active Directory Administrative Center in Windows Server 2012.
Step 1. Raise the Forest Functional Level
Before enabling AD Recycle Bin, you must first raise the forest functional level of your AD domain services (DS):
1. Log in to the Windows Server, and open Windows PowerShell.

2. At the PowerShell command prompt, enter the following cmdlet on a single line:
Set-ADForestMode -Identity contoso.com -ForestMode Windows2008R2Forest
-Confirm:$false
Where -Identity represents the fully qualified DNS name:
Step 2. Enable Active Directory Recycle Bin
Complete the following steps to enable AD Recycle Bin in Active Directory Administrative Center (ADAC) on the target domain:
1. Log in to the Windows Server, and open Windows PowerShell .

2. At the PowerShell command prompt, enter the following command; note that some wrapping may occur due
to formatting constraints:
Enable-ADOptionalFeature -Identity 'CN=Recycle Bin Feature,CN=Optional
Features,CN=Directory Service,CN=Windows
NT,CN=Services,CN=Configuration,DC=contoso,DC=com' -Scope
ForestOrConfigurationSet -Target 'contoso.com
3. Press Enter:

4. AD Recycle Bin is now enabled.

How to Restore a Microsoft Server 2008 R2 Active Directory Object from the Active Directory Recycle
Bin
This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft® Active Directory (AD) on Microsoft
Windows Server® 2008 R2. For information on backing up the Active Directory (AD), refer to How to Back Up Microsoft Active
Directory.
Important
Use the steps in this article to restore an AD Object from the AD Recycle Bin.
1. Log in to the Windows Server 2008 R2 as the administrator.

2. Go to Start > AdministrativeTools, right-click Active Directory Module for WIndows PowerShell, and click Run as administrator.
3. At the command prompt, enter the following command to verify that the object has been deleted:
Get-ADObject -Filter {displayName -eq "Shawn Lubahn"} -IncludeDeletedObjects
Where displayName is the name of the deleted user object:
4. Press Enter.
5. At the command prompt, enter the following command to restore the deleted object:
Get-ADObject -Filter {displayName -eq "Shawl Lubahn"} -IncludeDeletedObjects | Restore-ADObject
6. Verify the user has been restored.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft® Windows Server 2008 R2. If you
are running Windows Server 2012, refer to How to Enable Active Directory Recycle Bin on Windows Server 2012.
Important
Warning
Once you enable Active Directory (AD) Recycle Bin in your environment, you cannot disable it.
At a minimum, you must have membership in Enterprise Admins, or equivalent access privileges. For additional information, refer to the Microsoft
TechNet article Local and Domain Default Groups.
Enable Active Directory Recycle Bin
Important
You must use Active Directory Module for Windows PowerShell to run the commands described in this set of steps or an error will
occur. To run these commands using Windows PowerShell directly, run the command import-module activedirectory to import
the Active Directory cmdlet.
Use the following steps to enable AD Recycle Bin using the Enable-ADOptionalFeature cmdlet:
1. Log in to the Windows Server, and go to Start > Administrative Tools.

2. Right-click Active Directory Module for Windows PowerShell, and click Run as administrator:
3. At the PowerShell command prompt, enter the following command, replacing the bracketed variable as appropriate:
4.

4. Enable-ADOptionalFeature -Identity <ADOptionalFeature> -Scope

<ADOptionalFeatureScope> -Target <ADEntity>
5. Press Enter:
6. AD Recycle Bin is now enabled.

Barracuda LiveBoot
Barracuda LiveBoot

Use LiveBoot to instantly recover VMware virtual guest machines. In the event of a failure with your primary storage system, Barracuda Backup
acts as the datastore for your VMware ESXi server. You can recover any revision of a virtual guest machine within your retention policy, and
users can quickly access their files and applications directly from the deduplicated content stored within Barracuda Backup. Additionally, you can
use LiveBoot to granularly recover files and application-level items from applications such as Microsoft Exchange, Microsoft SQL, and Microsoft
SharePoint.
Virtual Machine States
A VM has two basic states: running or stopped. When a VM is stopped, applications are stopped and user sessions are inactive.
LiveBoot Destination
The destination is the Barracuda Backup data center and host IP address where you want to restore the VM. Install a Virtual Network Computing
(VNC) client on your local system to connect securely to your guest machine.
LiveBoot Status
Running – VM is successfully running

Not running – A VM is added but is not mounted or running (stopped or never started)
Configuring – VM started and Barracuda Backup is configuring the datastore with VMware
Running – The VM has booted with an IP address and is accessible via VNC
Stopped – The VM has been stopped and the disk is mounted but not running in VMware
Failed – The VM failed to boot after attempting to connect, configure, or start the VM within VMware
LiveBoot Recovery Features
Recover any revision of a VMware virtual guest server within your retention policy.
Granularly recover files and application-level items from applications such as Microsoft Exchange, Microsoft SQL, and Microsoft
SharePoint.
Serve up deduplicated content as needed by the virtual server.


Complete the steps in this article to use LiveBoot.
Step 1. Subscription Status
You must have a active Energize Update (EU) subscription to use LiveBoot. To subscribe:

2. Go to Restore > LiveBoot, and click Contact to Subscribe.
3. Enter your name, email address, message, and click Send.
4. Follow the instructions sent to the entered email address to add your subscriptions.
Once your VM is LiveBooted, you can connect to your VM securely using the VNC client while using a unique IP address and password provided
by Barracuda.
Step 2. Download and Install a Virtual Network Computing Client
Before you can connect and access your running VMs, download and install a Virtual Network Computing (VNC) client to your local system.
Continue with How to Add a Virtual Machine to LiveBoot.


The destination is the Barracuda Backup data center and host IP address where the VM is to be restored. Install a Virtual Network Computing
(VNC) client on your local system to connect securely to your guest machine.
Once the boot process is complete, the VM Preview link displays in the Destination column. Click to determine whether the VM booted
successfully. The link is available as long as the VM is running.

This article assumes you have completed the steps in Getting Started with LiveBoot.
To add a VM to LiveBoot:

2. Go to Restore > LiveBoot, and click Add LiveBoot.
3. In the Add VMs for LiveBoot dialog box, begin typing all or part of the VM name in the Search field to display matching items, or click F
ilter to further refine your search:
Click Clear if you want to clear all filters. If you click Filter again, the previous filter selections display.
4. Press Enter to return the search results. If there are no results, clear your filter and update your entry in the Search field.
5. The top five matching search results display in the dialog box. Click Show 5 more VMs or use the scroll bar to move through the results.
6. Select the VMs you want to add, and click Add; the selected VMs are added to the LiveBoot page.
7. Once you add the VM, click Start in the Actions column. In the Start VM dialog box, select where you want to boot the VM.
a. Original location – Boot your VM in the original datacenter and host where it was backed up; LiveBoot uses your stored
authentication credentials.
b. vCenter IP address – Boot your VM to a location already protected by Barracuda Backup; LiveBoot uses your stored
authentication credentials.
c. Other – Enter an alternate vCenter server and/or host name where you want to boot your VM; enter the authentication
credentials to authenticate to the VMware vCenter server or individual host, and click Authenticate. Once authentication is
successful, available data centers, datastores, and hosts display for selection.
8. If necessary, you can edit the name of the VM to avoid conflict with the original VM if it still exists in the environment.
9. Select the recovery options:
a. Boot VM with network connectivity
b. Customize VM hardware components – Click to select from available hardware components.
10. Click Boot. Allow the LiveBoot to create the VM.
11. If the VM fails to start, click Edit Boot Options and make any necessary changes.
Once the boot process is complete, the VM Preview link displays in the Destination column. Click to determine whether the VM booted
successfully. The link is available as long as the VM is running.
Continue with How to Manage LiveBooted Virtual Machines.


See also: How to Boot a VMware Guest System as a Clone Using LiveBoot
Moving the VM image off of the Barracuda Backup is dependent upon your VMware vSphere licensing. If a vSphere vMotion license is present,
you can use vMotion to perform a live datastore migration of the VM from Barracuda Backup storage to your production storage. If no vSphere
vMotion licenses is available, you must first shut down the VM before a datastore migration can be performed.
The Restore > Cloud LiveBoot page displays details about each added VM as described in Table 1:
Table 1. Cloud LiveBoot Table.
Column Description
VM Name VM name
Hard disk size used
Status Displays the VM status:
Running
Not Running
Stopped
Failed
Configuring
Revision Click to select the desired backup revision to restore
Destination Displays the data center location and host IP address
Recovery Options Displays the selected recovery options:
Boot with network connectivity

VM Hardware Components
Actions Displays the available actions based on the VM status:
Stop
Start
Restart
Edit
Destroy
Delete
LiveBoot a Virtual Machine
Use the following steps to LiveBoot a VM:
1. Log in to the Barracuda Backup web interface, and go to the RESTORE > Cloud LiveBoot page.
2. The Revision column displays the latest revision. Click the date picker to display the Revision History calendar selector. If there are
multiple revisions, you can pick a specific revision from which to boot.
3. Click Done. The Revision column displays the selected revision. When a user selects to boot the VM, the selected revision boots.
Manage Cloud LiveBooted Virtual Machines
Use the options in the Actions column of the Cloud LiveBoot table to manage your LiveBooted VMs:
Stop – Click to pause the VM

Restart – Click to restart the VM
Destroy – Once you shut down a VM, click Destroy to permanently delete all changes made since the VM was started
Start – Click to start a new Cloud LiveBoot instance
Delete – Click to delete the VM from Cloud LiveBoot


Select Revision

2. Go to Restore > LiveBoot. Select the desired VM.
You can select all revisions replicated to Barracuda Cloud Storage.
4. Once a revision is selected, the revision date picker in the Revision column displays the selected version. When a user attempts to boot
the VM, the selected revision boots.
vMotion Virtual Machine
Use the following steps to LiveBoot and vMotion a VM from Barracuda Backup:
1. Log in to vCenter with your vSphere client.
2. Right-click on the LiveBooted virtual machine, and click Migrate:
3. In the Migrate Virtual Machine page, select Change datastore:

4. Click Next. In the Storage page, select the destination storage:
5. Click Next, and then click Finish in the Ready to Complete page.
6. In vCenter, the Relocate virtual machine task displays under Recent Tasks, and the status displays as Completed:

6.
7. Click on the host where the VM was running, and click the Configuration tab.
8. Right-click the LiveBooted NFS datastore, and click Unmount.
Once the datastore is migrated, the Restore > LiveBoot page no longer displays the VM.

You can use LiveBoot to instantly recovery VMware VMs. A regular restore using LiveBoot, however, boots the VM with the exact hardware and
networking configuration with which it was backed up. In order to avoid conflicts with the original production VM, you can boot a clone using
LiveBoot so that the two systems can run side-by-side within your environment. This is useful to perform such tasks as granular file recovery and
application recovery.
Boot a Virtual Machine Using LiveBoot
Use the following steps to perform a side-by-side recovery of your VMware VM using LiveBoot:
1. Log in to the Barracuda Backup web interface, and go to the Restore > LiveBoot page.
4. The boot to location is based on your selection when the VM was added:
Original location – Boots the VM to the original datacenter and host where it was backed up
vCenter IP address – Boots the VM to a location already protected by Barracuda Backup
Other – Boots the VM to an alternate vCenter server and/or host name
5. The recovery options are based on your selection when the VM was added; boot VM with network connectivity and any selected
hardware components.
6. Click Start in the Actions column.
7. Use your vSphere client to view your recovered virtual machine:

There are no time limitations for how long a LiveBoot VM can run.
Use the following steps to shut down and delete a VM recovered using LiveBoot:
1. Log in to Barracuda Backup and go to Restore > LiveBoot.

2. Click Stop in the Actions column for the VM, and confirm you want to stop the VM.
3. In the Shut Down Virtual Machine dialog box, click Shut Down.
4. The VM powers off.
Once the VM is powered down, it retains the NFS mount to VMware ESXi and remains in the Stopped state until you choose to
destroy the VM. In the Stopped state, the VM image is stored on Barracuda Backup.
5. To destroy the VM and remove it from vSphere, click Destroy in the Actions column.
6. In the confirmation dialog box, click Destroy to unregister the VM from your VMware inventory, delete the disks, and unmount the
Barracuda Backup datastore.

Barracuda Cloud LiveBoot

Use Barracuda Cloud LiveBoot to boot VMware virtual guest systems and Microsoft Hyper-V virtual machines in the Barracuda Cloud. Cloud
LiveBoot is useful as a sandbox for testing purposes.
Cloud LiveBoot is available to all Barracuda Backup customers with Instant Replacement and a Cloud storage subscription, and is available to all
customers excluding those in Japan, Germany, and Austria.
In this Section




This article refers to the Barracuda Backup firmware version 6.3.04 and higher, and supported versions of VMWare and Microsoft
Hyper-V.
Cloud LiveBoot is available to all Barracuda Backup customers with Instant Replacement and a Cloud storage subscription, and is
available to all customers excluding those in Japan, Germany, and Austria.
Barracuda Cloud LiveBoot supports a maximum of four virtual disks per guest virtual machine.
Virtual Machine States

A virtual machine (VM) has two basic states: running or stopped. When a VM is stopped, applications are stopped and user sessions are inactive.
Recover and Test Virtual Servers
Cloud LiveBoot allows you to boot VMware and Hyper-V virtual guest systems in Barracuda's Cloud for recovery and testing, as described in
Table 1.
Table 1. Cloud LiveBoot Recovery and Testing Features.
Recovery Recover any revision of a VMware or Hyper-V virtual guest

server within your retention
policy.
Boot virtual servers in the cloud to recover and traverse the file
structure of virtual guest
system data.
Retrieve an individual Active Directory (AD) object.
For details on exporting an AD object, refer to the Microsoft
TechNet article
Import or Export Directory Objects Using Ldifde.
Serve up deduplicated content as needed by the virtual server.
Testing Once replicated to the cloud, boot the virtual guest system to
verify data integrity.
Use Cloud LiveBoot to set up a sandbox to test applications or
changes to applications
outside of your production environment.
When you back up a virtual guest server and replicate this data to Barracuda Cloud Storage, you can boot the server in Barracuda's Cloud
directly from the Barracuda Backup web interface; no additional configuration is necessary. Go to Restore > Cloud LiveBoot, select the guest
server, and click Start. Allow the operating system to complete the boot process. Once the system is available in the cloud, you are presented
your login credentials so that you can use a Virtual Network Computing (VNC) client to connect securely to your guest machine. Once your VM is
Cloud LiveBooted, you can connect to your VM securely using the VNC client while using a unique IP address and password provided by
Barracuda. For direct access, you can connect remotely over a public IP address by modifying the Network Settings to External. For more
information, see Getting Started with Cloud LiveBoot. Note that you must first shut down the server to enable a public IP address. The public
address is allocated by Barracuda.
When accessing a guest machine remotely, because it is assigned a public IP address, you are responsible for securing the VM in the
Cloud.
Once a virtual guest is running in the Cloud, it remains operational for seven days; if you require additional time, contact Barracuda Networks
Technical Support. The number of virtual images you can run is based on your Barracuda Backup model, as shown in Table 2.
Table 2. Virtual Images by Model.
Model Available Virtual Images
190/290/390 1
490/690 3
790 4
890/891/895/990/991/1090/1091 5
If there is a need for additional VMs, contact Barracuda Technical Support for assistance.

Interface Options
There are two interface options for VMs you want to Cloud LiveBoot:
Internal (default) – If you want your VM to be private, select Internal

External – If you want to assign a public IP address to your VM, select External; note that machines using a public IP address are not
protected behind a firewall.
Note that you can edit the interface option from the Restore > Cloud LiveBoot page.
Table 3. Frequently Asked Questions.
How long does it take to Cloud LiveBoot a VM? Quickly boot one or several guest machines. Typically, the guest
operating system begins the boot process less than a minute after
the request is made.
What are the options to access the LiveBooted VM in the Barracuda After a VM is LiveBooted in the cloud, credentials display in the VNC
Cloud? column of the Cloud LiveBoot page. Administrators can take the
credentials (IP, Port, and VNC password) and use any VNC client to
access the VM. Once the VM is booted in the Cloud, administrators
can power off the server and grant public IP addresses to the server.
This is accomplished by editing the server configuration in the Cloud
LiveBoot page. After the public IP address is assigned to the VM,
the administrator can start the VM again and assign the IP addresses
from the Barracuda interface to the network card(s).
Does Cloud LiveBoot require any configuration changes to the No, customers replicating to the Barracuda Cloud and that have
backup appliance before use? Instant Replacement are able to utilize the Cloud LiveBoot
functionality for VMware and Hyper-V backups.
Is there a fee to use Cloud LiveBoot? Cloud LiveBoot is available to all Barracuda Backup customers who
have Instant Replacement and a Cloud Storage subscription. Cloud
LiveBoot Instant Replacement provides the following benefits:
Overnight shipment to replace a down unit

Backup data pre-loaded from Barracuda Cloud locations in the
event of a disaster
Cloud LiveBoot recovery for VMware and Hyper-V:
24/7 support phone support
Hardware refresh for units that are four years old at no additional
cost, if continually under a contract subscription.
How can a VM that was booted in the cloud return to the production After testing or disaster, administrators can download the VM and
environment? save it to any location. The download file will save the VM as a .vmdk
/.vhd file that can be imported into any major hypervisor solution.
Does Barracuda change memory and CPU settings on the virtual Barracuda copies the configuration of the VM that has been booted in
machine booted in the cloud? the cloud. This means memory and CPU cores are identical to the
production environment.


Hyper-V.
Step 1. Subscription Status
You must have a subscription to both Barracuda Cloud storage and Instant Replacement to use Cloud LiveBoot as well as an active Energize
Update (EU) subscription. To subscribe:

2. Go to Restore > Cloud LiveBoot, and click Contact to Subscribe.
3. Enter your name, email address, message, and click Send.
4. Follow the instructions sent to the entered email address to add your subscriptions.
Step 2. Download and Install a Virtual Network Computing Client
Before you can connect and access your running virtual machines (VMs), download and install a Virtual Network Computing (VNC) client.
Continue with How to Add a Virtual Machine to Cloud LiveBoot.


Hyper-V.
There are two interface options for virtual machines (VMs) you plan to LiveBoot in the Cloud:
Internal (default option) – Select Internal if you want your VM to be private

External – Select External if you want to assign a public IP address to your VM; machines using a public IP address are not protected
behind a firewall
To change the interface type:
1. Start your VM, then stop it.

2. Once the VM is stopped, click Edit in the Interface Type column, select the new interface option, and click Done.
3. Restart your VM.


Hyper-V.
Hyper-V Guest System

Contact Barracuda Networks Technical Support to LiveBoot Hyper-V guest systems where the operating system is installed on a
non-primary disk.
This article assumes you have completed the steps in Getting Started with Cloud LiveBoot.
To add a virtual machine (VM) to Cloud LiveBoot:

2. Go to Restore > Cloud LiveBoot, and click Add LiveBoot.
3. In the Add VMs for Cloud LiveBoot dialog box, begin typing all or part of the VM name in the Search field to display matching items, or
click Filter to further refine your search.
Click Clear if you want to clear all filters. If you click Filter again, the previous filter selections display.
4. Click Enter to return the search results. If there are no results, clear your filter and update your entry in the Search field.
5. The top five matching search results display in the dialog box. Click Show 5 more VMs or use the scroll bar to move through the results.
6. Select the VMs you want to add, and click Add; the selected VMs are added to the Cloud LiveBoot page:
7. Once you add the VM, click VM Preview in the VNC column to view the details to connect and access the running VM via your VNC
client.
Continue with How to Manage Cloud LiveBooted Virtual Machines.


Hyper-V.
The Restore > Cloud LiveBoot page displays details about each added virtual machine as described in Table 1.
Table 1. Cloud LiveBoot Table.
Column Description
VM Name Hyper-V VMs:
VM name
Hard disk size used
Expiration date
VMware VMs:
VM name
Actual hard disk size
Expiration date
Status Displays the VM status:
Running
Not Running
Stopped
Failed
Configuring
Revision Click to select the desired backup revision to restore.
VNC Displays the VNC Information details necessary to connect to the

VM.
Interface Type Displays the selected interface option:
Internal (default) – Private VM

External – Displays the VM public IP address and password
Actions Displays the available actions based on the VM status:
Stop
Start
Restart
Download
Destroy
Delete
Cloud LiveBoot a Virtual Machine
Use the following steps to Cloud LiveBoot a VM:
1. Log in to the Barracuda Backup web interface, and go to the Restore > Cloud LiveBoot page.
Connect to your Cloud LiveBooted Virtual Machine
Use a Virtual Network Computing (VNC) client to connect directly to a Cloud LiveBooted VM:
1. Log in to Barracuda Backup, and go to Restore > Cloud LiveBoot.

2. In the VNC column for the VM, the VNC Information details display.
3. Open a VNC client, for example, TightVNC, and enter the VNC Information in the Remote Host field:

3.
4. Click Connect. You should now be connected to your Cloud LiveBooted VM:
Manage Cloud LiveBooted Virtual Machines
Use the options in the Actions column of the Cloud LiveBoot table to manage your Cloud LiveBooted VMs:
Stop – Click to pause the VM

Restart – Click to restart the VM
Destroy – Once you shut down a VM, click Destroy to permanently delete all changes made since the VM was started
Download – Click to download the VM as a VHD or VHDX file to your local system
Start – Click to start a new Cloud LiveBoot instance
Delete – Click to delete the VM from Cloud LiveBoot
Change the Virtual Machine Private IP Address to a Public IP Address
1.

1. Log in to Baracuda Backup, and go to Restore > Cloud LiveBoot.

2. In the Actions column, click Stop.
3. In the Interface Type field, click Edit, and then click External and make note of the Public IP Address and Default Gateway fields (you
will need these values in a later step).
4. In the Actions column, click Start.
5. Open the VNC client again, and connect to the virtual machine:
6. Log in to the virtual machine, and open TCP/IPv4 Properties:
7. Enter the Public IP address values from Step 3 in to the associated fields; You can use public DNS server values such as 8.8.8.8 and
4.4.4.2:
You may need a subnet calculator to calculate the subnet mask.

8. Click OK to apply your settings. Open a web browser and confirm that you can connect to the Internet.
Two Cloud LiveBooted VMs can communicate with each other provided they are both on the same account. Note that each account is
assigned a VLAN. The same is true if the VMs have a public IP address.


Hyper-V.
Barracuda Cloud LiveBoot supports a maximum of four virtual disks per guest virtual machine (VM).
Select the Revision

2. Go to Restore > Cloud LiveBoot. Select the desired VM.
4. Click Done. The Revision column displays the selected revision. When a user attempts to boot the VM, the selected revision boots.


Hyper-V.
Once you are done using your virtual machines (VMs) you can download the VM, and then delete (destroy) the VM from Cloud LiveBoot:
Hyper-V downloads as a fixed VHD disk

VMware downloads as a VMDK file
Download a Virtual Machine
1. Log in to the VM and stop the virtual guest machine.

3. Go to Restore > Cloud LiveBoot, and click Download in the Actions column for the associated VM.
4. Save the file to your local system.
Destroy a Virtual Machine
You can permanently delete all changes made since the VM was started using the following steps:

2. Go to Restore > Cloud LiveBoot, and click Destroy in the Actions column for the associated VM.
3. In the confirmation dialog box, click Destroy.

An error message displays when attempting to boot virtual machine The Add LiveBoot option is not grayed out when you use all of your
(VM) option. instances. You can add as many VMs as desired, however, an error
message displays if you boot a VM after you are out of allowed
instances.
The VMware column is not displaying the expected hard disk size. Hyper-V virtual machines (VMs) display the hard disk size used while
VMware VMs display the actual hard disk size.
I am backing up multiple Hyper-V VMs. Do I need to back up a You need only back up the VMs. With Cloud LiveBoot, Barracuda
Hyper-V host in order to live boot one of the VMs? provides the infrastructure/hosts to boot the VMs.

Restore Browser
In this Section
Understanding Restore Browser

How to Search for Items Using the Restore Browser
How to Restore Data Using the Restore Browser

Understanding Restore Browser

Use the Barracuda Backup web interface to restore data that was stored either using the Barracuda Backup Agent or file share data, or to
download a file, a file system directory, an email mailbox, or mailbox folders.
This is the recommended way to restore data backed up by the Barracuda Backup Agent. You should know:
Message-level data must be restored to the computer from which it originally came
Data can be restored back to its original location or to another computer on your network. If restoring to another location, the Barracuda
Backup Agent must be installed on that system
A functioning Barracuda Backup Server must be in place in order to restore SQL Server and Microsoft® Exchange databases
File Share Data
When restoring file share data through the web interface, you can restore one file at a time, a single directory, or an entire share. This works
well when you only need to restore a few documents. File share data can be restored to its original location through the web interface.

How to Search for Items Using the Restore Browser

Use the following steps to search for items using the restore browser:
1. Log in to the Barracuda Backup web interface using https://login.barracudanetworks.com/, and select the associated Barracuda Backup
appliance in the left pane.
2. Go to the Restore > Restore Browser page, and select the target data source.
3. Enter a word or phrase as the search string in the Search field, for example, enter the file extension .docx:
4. Click Search; the search results returns:
5. Identify the item you want to restore, and click Restore; the Restore dialog box displays:

6. In the Restore tab, select the Restore to location and Path, and then click Start Restore.
7. Once the restore is complete, the Success dialog displays:
8. Restore details are available on the Reports > Restore page.

How to Restore Data Using the Restore Browser
Use the Barracuda Backup web interface to restore data that was stored either using the Barracuda Backup Agent or file share data, or to
download a file, a file system directory, an email mailbox, or mailbox folders.
This is the recommended way to restore data backed up by the Barracuda Backup Agent. You should know:
Message-level data must be restored to the computer from which it originally came
Data can be restored back to its original location or to another computer on your network. If restoring to another location, the Barracuda
Backup Agent must be installed on that system
Requirements
When restoring data backed up by the Barracuda Backup Agent:
Message-level data must be restored to the computer from which it originally came.
Data can be restored back to its original location, or to another computer on your network. If restoring to another location, the Barracuda
Backup Agent must be installed on that system.
Message-level data must be restored to the computer from which it originally came.
File Share Data
When restoring file share data through the web interface, you can restore one file at a time, a single directory, or an entire share. This works
well when you only need to restore a few documents. File share data can be restored to its original location through the web interface, or for
Barracuda Backup firmware release 4.3 and earlier, you can use Barracuda Restore for Windows to restore file share data to its original location.
Backup Data by Date
By default, the Restore Browser page displays backups as of the current date. To select backups from an earlier date, click Change Date in the
left pane, and select the desired date:
Click Close to hide the date selection view.
Restore Data
1. Select the Barracuda Backup appliance from which to restore data, and go to the Restore > Restore Browser page.
2. In the left pane, select the computer and the associated data source that contains the files you want to restore.
3. In the right pane, navigate to and click on the content you want to restore, and click Restore.
4. In the Restore dialog, select a local location where you want to restore the data, or enter a resolvable hostname or IP address of a
restore location.
5. Select the Original Path, or enter a new path to which to restore the data, and click Start Restoring.
6. Go to the Reports > Restore page to view the restore status; click on a report to view individually restored items.
7. To stop the restoration process, go to the Reports > Restore page, and click Abort Restore.
Restore a Revision
For file systems and system state, you can select a revision to which to restore.
3. In the right pane, click View all revisions up to [date]; all available revisions display.
4.

4. Click Restore following the revision you want to restore.
Restore Latest Revision
3. In the right pane, click Restore Latest Revision of Data Source. The Restore Latest Revision of Data Source dialog box displays.
4. Select whether to restore to the original location, select an alternate location from the drop-down menu, or enter a resolvable hostname
or IP address of the restore location.
5. click Start Restore.
Download Files and Directories
You can select to download files and directories directly to your system. Click Download in the right pane to:
Download a single file

Download file system directories as ZIP files
Download email mailboxes and folders as ZIP files

Restoring from Local and Offsite Backups

Data can be restored from the local Barracuda Backup appliance, from a remote Barracuda Backup appliance that has been used to replicate
that system, or from the Barracuda Cloud Storage. Restores from the local Barracuda Backup appliance offer the fastest restore times.
Restore Methods
Multiple methods are available to restore your backed-up data including:
Restore Browser in the Barracuda Backup web interface

Restore from a Replication Destination
You can restore single files, individual email messages, and entire systems.
Restore Data Backed Up by the Barracuda Backup Agent
Data backed up by the Barracuda Backup Agent can be restored using the Restore Browser in the Barracuda Backup appliance web interface
Restore File Share Data
File share data can be restored using the Restore Browser in the Barracuda Backup web interface

How to Recover Backed Up Data Using the Download Feature

You can recover backed up content from either the local web interface or from the cloud.
Local Device Web Interface – To download from the local device at LAN speeds, use the Download feature in the Barracuda Backup
local web interface.
Cloud Web Interface – To verify and download data from the cloud, use the hosted Barracuda Backup web interface login credentials.
Download Using Local Device Web Interface
Use the Barracuda Backup Download feature through the local web interface to quickly download backed up data. The following steps
describe how to use this feature:
1. Open a web browser, enter the Barracuda Backup Server IP address, and log in to the Barracuda Backup web interface.
2. The System page displays; go to the Restore > Restore Browser page:
3. Navigate to a directory or file for download:
4. The Restore Browser section displays the latest backup date.
Older Revision
To restore an older revision of the file or directory, click Change Date to display all available revisions:

5. Click Download to the right of the file or folder you want to download:
6. The selected file is downloaded to a zip file. Once downloaded, you can extract the downloaded content from
the zip file:
Download Using Cloud Web Interface
Use the following steps to download and verify backed up data from the cloud:
1. Go to https://login.barracudanetworks.com/ and log in to the Barracuda Backup web interface.

2. Go to the Restore > Restore Browser page.
3. Navigate to a file or folder for download:
4. The Restore Browser section displays the latest backup date.
Older Revision
To restore an older revision of the file or directory, click Change Date to display all available revisions:
5. Click Download to the right of the file or folder you want to download, or click Download entire folder to download all content within the
folder selected in the Restore Browser section:
6. The content is downloaded as a .zip file. Once downloaded, you can extract the downloaded content from the zip file:

Example - Restore Data Using the Local Web Interface

Use the following steps to restore data using the Barracuda Backup local web interface. Note that the local web interface does not require an
Internet connection which may improve performance.
1. Open a web browser, and enter the Barracuda Backup appliance IP address.
2. Log into the Barracuda Backup web interface; the System page displays:
3. Click the Restore tab, and select the server from which to restore data. In the following example, a Microsoft Exchange Database is
selected:
4. Click the Restore link to the right of the data you want to restore; the Restore window displays. Select the Restore to and Method for
restoring the data, for example, select Original Location to select the original server, and select Restore to an Exchange Recovery
Storage Group/Database to restore to a recovery database:

5. Click Start Restore; the Restoration in progress window displays:
6. Click OK. In the web interface, go to Reports > Restore to view the restoration status:
7. Once the restore is complete, the left column displays a green indicator ( ) next to the restored data source.

How to Restore from a Replication Destination

This article refers to the Barracuda Backup Legacy Release firmware or newer, and assumes that replication has been successfully
set up on both devices and that backups are running successfully.
Only the Barracuda Backup Server 490 and higher can act as a backup to other Barracuda Backup Servers, although any
Barracuda Backup Server can send data.
To restore from a replication destination,
1. Log into the Barracuda Backup web interface, and select the receiving Barracuda Backup Server from which to restore.
2. Go to the Restore > Restore Browser page, and in the left pane select the sending Barracuda Backup appliance from which you are
receiving data:
3. Expand the sending Barracuda Backup appliance to review its backup sources, and click on the server or computer from which to
restore; the contents displays in the right pane:
4. In the Contents section, click Restore next to the file or directory you wish to restore; the Restore window displays.
5. In the Restore to field, enter the hostname or IP address of the restore to location. In the Path section, select the Original Path, or
designate a new location.


This article refers to Barracuda Backup Legacy Release firmware or newer, Microsoft SharePoint 2010, 2013 and 2016, and Kroll
Ontrack PowerControls version 6.0 and later, and assumes you have an active Kroll Ontrack license.
You can use Kroll Ontrack to granularly restore SharePoint Objects.
Restore SQL Flat File
To extract a SharePoint object from a restore, you must first restore the WSS_Content database to a flat file using the instructions in
the article How to Restore a Microsoft SQL Server Database to a Flat File.
Extracting and Converting Files
Once you restore the content database using the instructions in the article How to Restore a Microsoft SQL Server Database to a Flat File, use
the following steps to extract the .bak and .trn files, and then convert these files to .mdf and .ldf files.
1. Go to Start > Programs > Kroll Ontrack > Ontrack PowerControls > PowerControls ExtractWizard. On the introduction page of Ext
ractWizard, click Next.
2. In the Method of Extraction page, select Direct Method:
3. Click Next. On the Extraction Source page, navigate to and select the .bak file corresponding to the database you want to access:

4. Click Next. On the Catalog Performance Options page, select Catalog SharePoint backup datasets only:
5. Click Next. On the File Selection page, select Catalog, or browse to and select the database set you want to recover:

6. Click Next. On the Destination Folder page, browse to and select the destination folder where you want to copy the .mdf and .ldf files:
7. Click Next. Once the extraction is complete, click Finish to close ExtractWizard.
Restore the SharePoint Objects
Once you extract the .mdf and .ldf files from the restore, use the following steps to browse to and restore the SharePoint objects.
1. Go to Start > Programs > Kroll Ontrack > Ontrack PowerControls > PowerControls for SharePoint. The Data Wizard displays:

2. Click Next. In the Source Path Selection page, click Add, and navigate to and select the files created using the ExtractWizard in the
previous section:
3. Click Open to add the files. Verify the Temporary File Path is valid, and then click Next.
4. The database content displays in the Source list.
5. In the Target Server Selection page, from the SharePoint Server Site URL drop-down menu, select the target site URL:

6. Select an authentication option, and then click Next.

7. The source and target selections display. Expand the Source list, right click the item to restore, and then click Copy:
8. Expand the Target list, right-click the the site object location where you want to copy the source file, and click Paste:

9. Once the restore process is complete, the Copy Progress status log generates:
10. Click Print to print a copy of the report, Save to save a copy to your local system, or click Close.
11. Log in to SharePoint and verify the object has been restored to the desired location:


Restoring Windows System State
Restoring Windows System State should only be performed in a disaster recovery situation. Typically, this is if a server goes down and will not
boot or if the configuration is severely corrupted.
In this Section



This article refers to the Barracuda Backup Legacy Release firmware or newer, and Windows Server 2008, 2008 R2, 2012, and
2012 R2. This article assumes that a System State backup exists.
Important
Restoring Windows System State should only be performed in a disaster recovery situation. Typically, this is if a server goes down and
will not boot, or if the configuration is severely corrupted.
Requirements
Before proceeding, verify that all of the following are true:
The Barracuda Backup Agent is installed on the target server;

File System and System State from the source server exist;
Both the target and source server hardware and operating systems are configured the same;
The user performing the restore has administrator rights to all aspects of both the target and source systems;
The operating system media is available to load on target system; and
The target server is on the network and can communicate directly with the Barracuda Backup Server.
Prepare the Target
When setting up the target server, the configuration should be identical to that of the source server that you are restoring including:
Operating System Version and Edition

Target hardware is similar to source server
32- or 64-bit
For example, if the source server is 64-bit Windows 2008 R2, Enterprise Edition, the target server should also be 64-bit Windows 2008 R2,
Enterprise Edition.
To prepare the target server,
1. Install the source operating system on the target server.

2. Install the Barracuda Backup Agent on the target system.
3. Click Start > Run, enter services.msc, and click OK to open Services.
4. Navigate to Barracuda Backup Agent in the list of Services and verify the Status field displays as Started:
If the Barracuda Backup Agent Service is not listed in the Services window, you must first install the Agent before proceeding.
5. If the Status field displays as Stopped, right click the Agent, and click Start.
Restore System State
Mark Active Directory (AD) objects as authoritative. For more information, see Mark an Object or Objects as Authoritative.
To restore System State,
1. Log in to the Barracuda Backup web interface, and go to Restore > Restore Browser.
2. Expand the Windows Server that represents the source server, and select System State:
3. Click View all revisions up to: <date>; a list of revisions displays.
4.

4. Click Restore next to the revision you wish to restore:
5. The Restore window displays.
If the target server is set up with the same IP address as the source server you are restoring, select Original Location:
If the target server has a different IP address, select the third option and enter the IP address of the new location:

7. Go to Reports > Restore to view restore job details.
Restore Job
The restore job completion is dependent upon the size of the original server.
8. Once the restore is complete, a dialog displays. Click OK to close the dialog box.
Restore File Systems
Mark AD objects as authoritative. For more information, see Mark an Object or Objects as Authoritative.
To restore the file systems,
1. Log in to the Barracuda Backup web interface, and go to Restore > Restore Browser.
2. Expand the Windows Server that represents the source server, and select File System:


5. If the target server is set up with the same IP address as the source server you are restoring, select Original Location:

7. Go to Reports > Restore to view restore job details.
Restore Job
9. Once the restore job is complete, restart the server.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and Windows Server 2008 domain controller. This
article assumes that a System State backup exists, and that the user restoring to System State has access to the Directory
Services Restore Mode (DSRM) password. You cannot perform a system state restore from the Cloud.
Disaster Recovery
Restoring Windows System State should only be performed in a disaster recovery situation. Typically, this is if a server goes down and
will not boot, or if the configuration is severely corrupted.
Requirements
Before proceeding, verify that all of the following are true:
The Barracuda Backup Agent is installed on the target server;

File System and System State from the source server exist;
Both the target and source server hardware and operating systems are configured the same; and
The target server is on the network and can communicate directly with the Barracuda Backup Server.
Active Directory Domain Controllers
For Active Directory (AD) domain controllers, you must have access to the DSRM password. Additionally, it is highly
recommended that the IP address to which you are restoring is the same as the original server .
Prepare the Target
When setting up the target server, the configuration should be identical to that of the source server that you are restoring including:
Version
Edition
32- or 64-bit
For example, if the source server is 32-bit Windows 2008, Enterprise Edition, the target server should also be 32-bit Windows 2008, Enterprise
Edition.
Cancel Restore
If you decide you do not wish to restore the server, use the steps in the section Restoring Normal Boot Mode to return your server to
the normal boot mode.
1. Power on the target server, or if it is already running, reboot the target server.
2. Log on using an administrator account; if the target server is a domain controller, log in using a domain account with administrative
access to the server.
3. At a command prompt, enter the following command:
bcdedit /set safeboot dsrepair
4. Press Enter, and then enter the following command to restart the server:
shutdown -r -t 1
5. Press Enter to restart the server. The server restarts, and Windows boots into Directory Services Repair
Mode.
6. Press Ctrl-Alt-Delete and log into the system using the same credentials you entered above in Step 2.
7. Click Start > Run, enter services.msc, and click OK to open Services.
8. Navigate to Barracuda Backup Agent in the list of Services, and verify the Status field displays as Started:
If the Barracuda Backup Agent Service is not listed in the Services window, you must first install the Agent before proceeding.

9. If the Status field displays as Stopped, right click the Agent, and click Start.
Restore File System and System State
Use the following steps to restore an AD domain controller to the target server, or to restore a complete copy of the source server without AD.
This procedure restores the file system, overwriting existing files. Restoring System State from a source domain controller restores AD
to its original state on that server; check with your system administrator before restoring a domain controller from an old revision
backup.
1. Log in to the Barracuda Backup web interface, and go to RESTORE > Restore Browser.
2. Select the Windows Server that represents the source server you wish to restore:

If the target server is set up with the same IP address as the source server you are restoring, select Original Location:
7.

7. Go to REPORTS > Restore to view restore job details.
Restore Job
The restore job completion time is dependent upon the size of the original server.
9. Once the restore job is complete, use the steps in the section Restoring Normal Boot Mode to restore the server to normal mode.
Restore System State
Use the procedure described in this section only if you wish to restore System State to the target server without restoring the rest of the file
system as it was on the source server. This procedure restores System files including those in the C:\Windows folder. Perform the steps in this
section if you are not performing full disaster recovery and wish to keep the target server's file system intact. Since this procedure does not
restore file systems, following these steps will not restore replicated file systems or administration tools if the source server was a domain
controller. This means group policy objects and log on scripts will not be available on the target server unless they are already on that server or
on another server on the network. If you wish to restore file systems, use the steps described in the section Restoring File System and
System State, or restore file systems manually from another server on the network.
Restoring System State from a source domain controller restores AD to its original state on that server; check with your system
administrator before restoring a domain controller from an old revision backup.
To restore System State only,
1. Log in to the Barracuda Backup web interface, and go to RESTORE > Restore Browser.
2. Expand the Windows Server that represents the source server, and select System State:

If the target server is set up with the same IP address as the source server you are restoring, select Original
Location:


7. Go to REPORTS > Restore to view restore job details.
Restore Job
9. Once the restore job is complete, use the steps in the section Restoring Normal Boot Mode to restore the server to normal mode.
Restore Normal Boot Mode
Once the restore is complete, use the following steps to restore the server to normal boot mode:
1. Power on the target server, or if it is already running, reboot the target server.
2. Log on using an administrator account; if the target server is a domain controller, log in using a domain account with administrative
access to the server.
bcdedit /deletevalue safeboot
4. Press Enter, and then enter the following command to restore normal boot mode:
shutdown -t 0 -r
5. Press Enter to restart the server in normal boot mode.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange, Novell NetWare Server,
and GroupWise 8 and 2012.
Use the Barracuda Backup web interface to view, search, and restore Microsoft Exchange and Novell GroupWise messages. You can view all of
the messages within a single mailbox, or select multiple mailboxes in which to search for a text string.
Use the following steps to restore messages using the Restore Browser:
1. Log in to the Barracuda Backup web interface, and in the left pane, click on the Barracuda Backup Server from which to restore data.
2. Go to the Restore > Restore Browser page, and select the Exchange or GroupWise server that contains the messages you want to
restore.
3. Click Message-Level:
4. Select the mailbox from which to restore:
5. Once you select the mailbox, click the Inbox folder:
Message-level backup does not include items such as contacts, calendars, or tasks.
6. Browse through any additional folders. Click the Restore link to the right of the message you want to restore:

7. The Restore dialog box displays. Specify the restore settings:

a. Mailbox – Select to restore to the Original Mailbox, or select an alternate mailbox to which to restore the data.
b. Location – Select to restore to the Original Location, or select to restore the message(s) to an alternate folder:


Bare metal recovery allows you to restore a complete Microsoft Windows system, including data, settings, applications, and operating system,
onto a new computer on which nothing is installed.
Caution
The bare metal recovery process overwrites all existing data on the system to which you are restoring the data; therefore, bare metal
recovery is recommended only when no other recovery option is available. This process rebuilds the target computer or server to its
original system setup.
A bare metal restore is intended to be used for restoring to similar hardware.
All system volumes and system state must be backed up in order for bare metal recovery to be possible.
Requirements
You must have an existing backup of a system that uses one of the following Microsoft operating systems:
Microsoft Windows Server 2012 R2

Microsoft Windows Server 2012
Windows 2008 Server
Windows Small Business Server 2011
Windows Vista
Windows 10
Windows 8
Windows 7
Additionally, you must have all of the following:
Barracuda Backup Server firmware version 6.1 or higher;

Barracuda Backup Bare Metal Live CD 6.1 or higher (available from the System > Software Downloads page); and
Administrator rights to the Microsoft Exchange Server.
Bare Metal Live CD
Use the following steps to download the Bare Metal Live CD boot media; select the appropriate bit version for the OS you are planning to restore.
For example, if you are restoring a 64-bit operating system, you must use the 64-bit version.
1. Log in to Barracuda Backup and go to System > Software Downloads. Download the Bare Metal Live ISO file to your local system.

2. Burn the Bare Metal Live ISO file to a CD.

3. Boot the system you want to restore using the Bare Metal Live CD you created in step 2.
4. Read the onscreen warning:
5. To continue with the Bare Metal restore, click Next.

6. Set up the Network configuration:
If you have DHCP enabled on your network, an assigned IP address displays in the IP Address field.
If DHCP is not enabled, clear DHCP, and enter the IP Address, Subnet Mask, and Default Gateway:
7. Click Next. You are prompted to log in to Barracuda Backup:

7.
8. In the Barracuda Backup web interface, go to the Restore > Restore Browser page and select the system you want to recover.
9. Click View all revisions up to: <date> to view the selected system's revisions available for restore:
10. In the Revisions list, click Restore for the revision you want to recover.

11. In the Restore dialog box, click the Restore tab, and enter the IP address of the system you are recovering
in the Restore to section:

13. For the system booted using the Bare Metal Live CD, a list of volumes that are recoverable displays:
14. Select the volumes you want to recover.
You cannot deselect boot and system volumes as these are required for the Bare Metal restore.
If you choose to restore to a server that does not have identical volumes as the original machine the data was backed up from,
the Barracuda Backup appliance will still attempt to restore all drives even though you may have only selected one of these on
the Bare Metal Restore screen. The restore will throw errors for these missing drives, but will restore the drives that exist on
the target machine.
15. (Firmware version 6.3.02 and higher only) You are presented with the option to select which disks you want to include/exclude when
determining disk repartition. To exclude a destination disk, clear the checkbox next to the disk name:


a. Click Yes to confirm your selection:
b. An additional warning displays; click Yes if you want to proceed:
16. Click Next to begin the restore:

17. When the restore is complete, click OK in the Confirmation dialog box.
18. Remove the bare Metal Live CD, and reboot the system.
SQL, Exchange Server, and Hyper-V Host

If SQL, Exchange Server, and/or a Hyper-V Host are installed on the system, you must restore those items separately once the bare
metal restore is complete.

How to Create a Bootable USB Flash Drive from the Bare Metal Restore Live CD ISO
Step 1. Download the Bare Metal Live CD ISO
1. Log in to the Barracuda Backup web interface, and go to the System > Software Downloads page.
2. In the Bare Metal Live CD section, download the Bare Metal Live CD ISO 32- or 64-bit software to your local system.
Step 2. Prepare USB Flash Drive Using Diskpart
The diskpart utility deletes all information stored on the USB Flash Drive.
1. Insert the USB flash drive into the computer where you downloaded the Bare Metal ISO.
2. At a command prompt, type the following commands, pressing Enter after each line:
<X> is the drive number or drive letter of the USB flash drive.
diskpart
list disk
select disk <X>
clean
create part pri
select part 1
format fs=ntfs quick
active
exit
Step 3. Copy Bare Metal ISO Files to USB Flash Drive
You must extract the ISO files and place them on the root of the USB flash drive. You can either mount the ISO in Windows 8 and later operating
systems, or extract the ISO using a third-party tool in Windows 7 and prior operating systems. For the purpose of this article, 7zip will be used to
extract the ISO.
To Mount the ISO in Windows 8 and Later:
1. Right-click the ISO, and click Mount:
2. Once mounted, the ISO displays as a new drive in Windows. In Windows Explorer, browse to the new drive and select all files in the root
of the new drive and copy them.
3. Browse to the USB Flash Drive in Windows Explorer, and paste the files into the USB Flash Drive root.
The files are copied to the USB Flash Drive. Once the copy is complete, the USB Flash Drive is ready to boot.
To Extract the ISO in Windows 7 and Earlier:
1. Download and install 7-Zip.

2. Once installed, right-click the ISO file, and click Extract files:

3. Select the USB Flash Drive root as the Extract to location, and click OK.
The files are extracted to the USB Flash Drive. Once the extraction is complete, the USB Flash Drive is ready to boot.
Go to How to Restore a Windows System to Bare Metal for instructions on performing a Bare Metal restore.


This article refers to the Barracuda Backup Legacy Release firmware or newer, and the Barracuda Linux Backup Agent.
Use the steps in this article to restore Linux distributions (distros) that support Live CDs. Linux distros can o
nly be restored to bare metal; for example, Red Hat, Fedora, Ubuntu, Gentoo, and SUSE Linux.
Note that the mkfs commands in this example are based on GNU Grub version 2 which by default supports
256-bit index nodes. If y ou are using GNU Grub version 1 when creating the file system, you must specify 1
28-bit index nodes.
Use the following steps to restore an entire file system backed up using the Barracuda Linux Backup Agent.
Step 1. Install the Barracuda Linux Backup Agent
Example
The following steps are based on Ubuntu Desktop 12.04 x64, but apply to Linux distros that support Live CDs, for example, Red Hat,
Fedora, Ubuntu, Gentoo, and SUSE Linux.
1. Boot into a live CD environment that supports your hardware, for example, Ubuntu 12.04 x64.
2. Configure an IP address, and verify network connectivity to the Barracuda Backup appliance containing the data source files you want to
restore.
3. In the Barracuda Backup web interface, go to the System > Software Downloads page.
4. Download and unzip the Barracuda Linux Backup Agent to your live booted environment.
5. Unpack the tar file:
tar -xvf barracuda_backup_agent-x.x.x.tgz
For example:
6. On the live booted environment, and change the directory to the Barracuda Linux Backup Agent directory, for example:
/Desktop/agent-5.3-lin$
7. Install the agent:
./install
For example:
Step 2. Partition, Format, and Create the File System
The destination file system(s) must be empty. If you have multiple mount points, you must mount them such that the backup paths

match during restore. For example, if you have a separate root and home partition, mount the root partition at /mnt/system and the
home partition at /mnt/system/home. Configure the restore to target the path /mnt/system/.
1. Open a terminal window, and enter the following command to create the partition:
fdisk /dev/sda
2. Press Return. Enter N to create a new partition, and press Return.
3. Enter P the primary partition, and press Return.
4. Enter the partition number, for example, enter 1 for partition 1. Press Return.
5. Press Enter to select the default first sector, and then press Enter again to select the default last sector.
6. Enter W, and press Enter to write the changes:
7. Enter fdisk -l and press Return to view the partitions:
8. Enter mkfs.ext4 /dev/sda1 and press Return to create the file system:

9. Enter the mount point, and press Return. For example:
Step 3. Restore the File System Using the Barracuda Linux Backup Agent
1. Log in to the Barracuda Backup Server, and go to Restore > Restore Browser page.
2. Select and expand the Linux Server you want to restore; select File Systems.
3. In the right pane, click the top check box to select all contents.
4. Click Restore selected items at the top of the screen.
5. In the Restore dialog, enter the target IP address of the live booted machine, and enter the mount point to which to restore, for example,
type /mnt/data/:
6. Click Start Restore. To view the restore progress, go to the Reports > Restore page:
Step 4. Mount the Linux System Directories and Install a Bootloader

Complete the following steps when the restore is 100% complete and successful.
1. Open a terminal window, and enter the following commands to mount the Linux system directories and install a bootloader using your
mount points:
2. Enter update-grub2 and press Return to update the grub bootloader:
3. Reboot the system.


This article refers to the Barracuda Backup Legacy Release firmware or newer, VMware ESX/ESXi, and Microsoft Hyper-V.
LiveBrowse is supported for virtual machines stored on the local Barracuda Backup appliance and not revisions that are offsite
vaulted.
Barracuda Backup with VMware and Hyper-V is an agentless, image-based backup that provides simple disaster recovery methods including:
Restore an entire guest machine to any ESXi host on your network;

LiveBoot a virtual machine (VM) from the Barracuda appliance;
Browse inside the VM through the restore browser for granular file recovery.
Windows Dynamic Disk partitions are not supported by Barracuda LiveBrowse. If you need to restore individual files from a Windows
Dynamic Disk partition, Barracuda recommends using the Barracuda Backup Agent to protect that data.
Use the following steps to browse inside of VMware or Hyper-V VM using the restore browser:
1. Log in to your Barracuda Backup web interface, and go to the Restore > Restore Browser page.
2. Navigate to and expand the VM data source:
3. Click on the guest system you want to browse inside, and navigate through the appropriate .vmdk file and partition:
4. Navigate through the directory structure, locate the file you want to recover, and click Download to download a zip file containing the
selected file:
To recover a file from a different date:
1. Click Change Date in the upper left-hand corner of the Restore Browser:

1.
2. Select the desired date and time from the calendar:
3. Navigate through the VM directory structure to the file you want to recover, and click Download.


Use Barracuda Backup to back up Hyper-V guest machines. This type of host-based backup is an agentless, image-based backup that provides
fast and easy disaster recovery methods including:
Restore an entire guest machine to any host system on your network;

Browse inside the VM through the restore browser for granular file recovery.
To browse inside a Hyper-V VM using the restore browser, use the following steps:
1. Log in to your Barracuda Backup web interface, and go to the Restore > Restore Browser page.
2. Navigate to and expand the Hyper-V data source:
3. Click on the guest system you want to browse inside, and navigate through the appropriate . vhd/.vhdx f
ile and partition:
4. Navigate through the directory structure, locate the file you want to recover, and click Download to download a .zip file
containing the selected file:

To recover a file from a different date:

1. Click Change Date in the upper left-hand corner of the Restore Browser:
2. Select the desired date and time from the calendar:
3. Navigate through the VM directory structure to the file you want to recover, and click Download.

How to Perform a Physical to Virtual Restore

This article applies to:
Barracuda Backup Legacy Release firmware or newer

VMware ESX/ESXi host machines, or vCenter Server version 4.0 or higher with vSphere 4.0 or higher
Microsoft Hyper-V 2008 R2, 2012, and 2012 R2
See also:

You can restore a complete Microsoft Windows system, including data, settings, applications, and operating system, onto a new VMware virtual
machine (VM). Note that the VM must be built prior to performing a physical to virtual restore.
Requirements
P2V restores to VMware require the LSI Logic SAS vSCSI controller.
You must have an existing backup of a system that uses one of the following Microsoft operating systems:

Microsoft Windows Server 2012
Windows 2008 Server
Windows Vista
Windows 8
Windows 7
Additionally, you must have all of the following:
VMware or Hyper-V guest virtual machine;

Default Microsoft Windows drivers;
Barracuda Backup Server firmware version 6.1 or higher;
Barracuda Backup Bare Metal Live CD 6.1 or higher (available from the System > Software Downloads page in the web interface); and
Administrator rights to the Microsoft system.
Step 1. System Boot Options
Before proceeding, you must configure the system boot options on the virtual machine to match the original physical machine as one of the below
options:
BIOS
Extensible Firmware Interface (EFI)
If the operating system supports both BIOS and EFI, you can change the default from the Options tab in the Virtual Machine Properties editor
when setting up the VMware VM. For more information on system boot options, refer to the VMware vSphere article Select a Guest Operating
System.
Step 2. Download the Bare Metal ISO
Use the following steps to download the Bare Metal Live CD boot media; select the appropriate bit version for the OS you are planning to restore.
For example, if you are restoring a 64-bit operating system, download Bare Metal Live CD 6.1 (64 bit).
1. Log in to Barracuda Backup and go to System > Software Downloads. Download the Bare Metal Live ISO file to your local system.
2. Burn the Bare Metal Live ISO file to a CD.
Step 3. Build Your Virtual Machine
1. Build a VM using the same operating system architecture and configuration, e.g., CPU (x86 or x64), RAM, and Storage, as the physical
device.
2. Boot the new VM using the Bare Metal ISO.
3. Read the onscreen warning, and then click Next to continue.
4. Set up the Network configuration:

4.
If you have DHCP enabled on your network, an assigned IP address displays in the IP Address field.
If DHCP is not enabled, clear DHCP, and enter the IP Address, Subnet Mask, and Default Gateway.
5. Click Next. You are prompted to log in to Barracuda Backup.
Step 4. Start the Restore
1. Select the date you wish to restore.

2. In the Barracuda Backup web interface, go to the Restore > Restore Browser page, and select the system you want to restore.
3. Click Restore at the Agent level.
4. In the Restore dialog box, click Destination is a VMware or Hyper-V guest:
Step 5. Select Volumes to Restore
1. On the booted VM, select the volumes you want to recover.
Boot and System Volumes

You cannot deselect boot and system volumes as these are required for the Bare Metal restore.
2. Click Next to begin the restore.

3. When the restore is complete, click OK in the Confirmation dialog box, and reboot the system.
Microsoft Exchange, SQL, and SharePoint Application Databases

If SQL and/or Exchange are installed on the system, you are required to restore application databases separately once the bare metal
restore is complete. For more information, refer to the following sections:
Microsoft Exchange
P2V Restore

On-Demand Purging
You can manually purge items stored in Barracuda Backup. This is useful when Barracuda Backup appliances are low on available disk space or
if you have backed up an item that is no longer needed and you wish to remove it from Barracuda Backup.
Items that can be purged are:
Agent Backups (Windows & Linux)

Files
Folders
Microsoft SQL Server Databases
Microsoft Exchange Server Databases/Storage Groups
Exchange Message-Level Backups
Email Messages
Email Folders
User Mailboxes
File Share Backups (CIFS/SSHFS)
Files
Folders
VMware Backups
Virtual Machines
To manually purge an item:

3. In the Restore Browser, select the source from which you wish to manually purge a file:
4. Drill down into the source until you reach the location of the desired file, and then click Show Purge Links:
5. The Purge links display next to the files:
Warning
When you click Purge, an item and all of its historical revisions are purged from Barracuda Backup.
6. Click Purge next to the file you wish to remove from Barracuda Backup. Click Purge in the confirmation dialog to proceed:

6.
7. The item is set to be purged:
8. Click OK to close the confirmation window.
Note that purging data does not remove the data source from Barracuda Backup. If you no longer want to back up data for a particular
server, go to the Backup > Source page, and click the Delete icon for that particular server:
Once the data source is deleted you can purge the files from Barracuda Backup. If you do not delete the data source, items will display
in the Large Items report.


This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server 2008, 2008 R2, 2012, 2012
R2, 2014, and 2016.
Bare metal restores performed on systems running Microsoft SQL Server, require additional steps to restore the SQL instance to a running state.
The bare metal process restores the file system and system state only. Database files are excluded from file system backup in an effort to reduce
duplicate database file backup overhead. Instead, database files are backed up using either the VSS or VDI Microsoft SQL backup functions of
the backup agent and are not restored with the bare metal restore.
The steps in this article assume the following:
A bare metal restore was successfully completed, and

The System is online with a valid network connection to the Barracuda Backup appliance.
Restore SQL VSS Backup
1. Log in to Barracuda Backup, and go to Restore > Restore Browser page.

2. Select and expand the source containing the SQL Server.
3. Drill down to the Backup Agent\Microsoft SQL instance to be restored, and click Download for the master da
tabase:
4. Extract the files and copy only the MDF and LDF files to the system database directory, typically located: C:\
Program Files\Microsoft SQL Server\MSSQL12.<instance name>\MSSQL\DATA\
5. Click Download for the model database:
6. Extract the files and copy only the MDF and LDF files to the system database directory, usually located:
C:\Program Files\Microsoft SQL Server\MSSQL12.<instance name>\MSSQL\DATA\
7. Click Download for the msdb database:
8. Extract the files and copy only the MDF and LDF files to the system database directory, usually located: C:\P
rogram Files\Microsoft SQL Server\MSSQL12.<instance name>\MSSQL\DATA\
9. The SQL instance should now start and can accept restores from the Barracuda Backup appliance.
10. To restore additional databases, click Restore to the right of the database name in the Restore Browser, and select from the available

10.
restore options.
Restore SQL VDI Backup

Step 1. Initiate Single User Restore Mode
1. Log in to the Server as the administrator and open a command prompt.

2. Copy the template database files from the Template Data folder, typically located: C:\Program Files\Microsoft SQL Server\MSSQL12.
<instance name>\MSSQL
3. Use the instructions in the Microsoft article Rebuild System Databases to rebuild the system databases from the command prompt.
4. Open the SQL Configuration Manager, and click SQL Server Services in the left pane.
5. Double-click the SQL Server (<instance name>), and click the Startup Parameters tab.
6. Type -m in the Specify a startup parameter field, and click Add:
7. Click OK.
8. Right-click the SQL Instance, and click Start. The instance should now be started in single user mode and ready for the master database
restore.
Step 2. Start the SQL Instance
1. Browse to the source SQL Server instance, drill into the instance, and click Restore to the right of master database:
2. Restore to the original instance.

Step 3. Return to Multi-User Mode
1. Open the SQL Configuration Manager, and click SQL Server Services in the left pane.
2. Double-click the SQL Server (<instance name>), and click the Startup Parameters tab.
3. Click on the parameter in the Specify a startup parameter field, and click Remove.
4. Click OK to apply the change. If prompted to restart, click OK.
Step 4. Restore Additional Databases
1. Click Restore for the model database, and restore to the original instance.
2. Click Restore for the msdb database, and restore to the original instance.
3. Repeat the restore steps for any additional user databases.

Recovering Data After a Ransomware Attack - Video

Reports Page
Backup Reports
Barracuda Backup provides a detailed report for each backup that is run. Backup reports can be accessed from the Reports > Backup page of
the Barracuda Backup web interface. In addition, any backup process that is currently running is also displayed from this page. Backup reports
include details about the backup such as when the backup started, duration, size, if there were any errors or warnings, and any new, changed, or
removed items. Reports also include links to each backed up file to view or download the item from the report.
Click Details to view recent activity in chart form. You can also view a list of backed up files including the number of new, changed, and removed
files, as well as a list of any errors encountered during backup.
If a backup is currently in progress, the Reports > Backup page displays this information and allows you to cancel the backup.
To send a summary of backup reports based on selected schedules, click Send Summary Report and enter an email address to which to send
the report:
To download a report as a .csv file to your local system, click Download in the Actions column, or in the report view, click Download Report
(CSV).
Click on the report to view report details. Expand the report details, and click on a file name to restore the file through the Restore > Restore
Browser page:

Restore Report
You can view restoration details in the Reports > Restore page. To specify how you wish to sort the table, click on a heading, and then click on
the up/down arrows to the right of each heading to specify either an ascending or descending sort.
Click Details to view all details for the selected restoration including any encountered errors. Expand the detail tabs to view specific file errors
and a list of restored content.
Large Items Report
The Reports > Large Items page displays a detailed list of large items including the data source and path, original file size, and deduplicated
backup size. From the Sources drop-down menu, you can select to view large items by individual source, by Agent, or for all sources. To further
refine the report, enter a string in the Filename contains field, and click Filter. The report displays only those items matching the Filename
contains value for the selected source.

Audit Log Report
The Reports > Audit Log page displays a report of all activities in the Barracuda Backup web interface by time and date, by user, and by action.
Logged activities include log on authentication, firmware update, changes to settings, changes to account information, and more. Click the Detail
s icon for additional information for a specific activity.
For more information about audit logging, refer to the article Understanding Audit Logging in the Cloud UI.
In the top pane, you can specify the following:

Select a specific user or display logs for all users
Specify whether to include log on authentication activities
Date range of logs to display

How to Configure Daily Summary Reports

You can configure users to receive a once daily summary report that includes information about the Barracuda Backup appliance and the last run
of each backup schedule from the previous day.
Figure 1. Sample Daily Summary Report.
To configure Summary Reports for users on the account:
1. Go to the Admin > Users page, and click Edit in the Actions column for that user.
2. In the Email notifications section, select Backup Summary Reports:

3. Click Save.
To configure Summary Reports for users not associated with your account (non-users such as your reseller):
1. Go to the Admin > Email Notifications page, and enter the recipient's email address in the Email Address field.
2. In the Send section, select Backup Summary Reports:
3. Click Add. The email address is added to the Recipients table.

How to Download a Detailed Backup Report

You can download a detailed backup report in CSV format. The backup report includes information about every item that was added, modified,
removed, or excluded from the selected backup schedule.
Figure 1. Sample Backup Report.
To download a detailed backup report:

2. Go to the Reports > Backup page.
3. Click Download to the right of the desired backup schedule, or click Details and then click Download Report (CSV):

How to Generate a Large Items Report

From the Reports > Large Items page you can view a detailed list of large items including the data source and path, original file size, and
deduplicated backup size. You can select to filter the results by all sources, an individual source, or by Agent, and further refine the report by
entering all or part of a filename.
Barracuda recommends generating a new report only when backups are not currently running as the process can be
resource-intensive depending on the number of items and amount of data on the Barracuda Backup Server. This also affects the
amount of time it takes for a new report to generate.
To generate a large items report,
1. Log in to Barracuda Backup, and go to the Reports > Large Items page.
2. Click Generate list of Large Items to view a detailed list of all large items.
3. Once the list generates, enter the following details to refine your search:
a. From the Sources drop-down menu, select the desired source.
b. To search by filename, enter all or part of a filename in the Filename contains field.
4. Click Filter; the updated report displays only those items matching the entered criteria:

How to Manually Send a Summary Report

You can send customized Backup Summary Reports to any email recipient. Backup Summary Reports include information about the Barracuda
Backup appliance and information about the backup schedules that ran on the selected day(s).
Figure 1. Sample Backup Summary Report.
To send a Backup Summary Report:

2. Go to the Reports > Backup page.
3. Click Send Summary Report:
4. Enter the recipient's email address in the Send to field, select the data range from which you want to include your schedules, then click
Send Report:
5. Click OK in the confirmation screen:

5.

Understanding Audit Logging in the Cloud UI
The following table lists the primary audit logging details available in the Reports > Audit Log page:
Log Type Details
Event Logging User login(1)

Start restore
Abort restore(2)
Start backup
Abort backup(2)
Restore browser download
Started purge process
Barracuda LiveBoot in the cloud
Change Logging Backup > Sources page:
Add/remove/edit data source

Server settings (for example, server name, type, hostname,
username, password, etc.)
Add/remove/edit share
Share settings (name, type, etc.)
Object tree (files, folders, mailboxes)
Backup > Replication page:
Add/remove destinations
Add/remove replication target
Multiple share disablement of replication ('disable all replication
to [server name]')(3)
Enable/disable sending to Barracuda Control Server(3)
Details of Add replication target(4)
Backup > Schedules page:
Add/remove schedule
General schedule settings (name, date/time, repeat interval,
etc.)
Server/share/object tree
Backup > Rate Limit page:
General settings (mode, percentage, alternate rate, alternate

rate schedule, etc.)
Backup > Exclusions page:
Add/remove exclusion rules

General exclusion rule settings (name, add to reports, apply
recursively, etc.)
Expressions
Backup > Retention Policies page:
Add/remove retention policy

General retention policy settings (name, retention timeline, etc.)
System > Firmware page:
Firmware upgrade
System > BBS Settings page:
General settings (group name, time zone, etc.)

Admin > Users page:(1)

IP restrictions
Account permissions (Barracuda Backup Server permissions)
Admin > Email Notifications page:
Add/remove alerts to email addresses
Admin > Display Groups page:
Add/remove display group
Notes:
(1) Entries display in audit log only when Include log in and admin actions is turned on in the Reports > Audit Log page.
(2) Because the audit log entry is incomplete, the job name does not display for this entry.
(3) Event is not logged.
(4) Only the name of the replication target is included in audit log.

System Page
Use the System page to manage the Barracuda Backup firmware version and settings, and access software downloads.
Firmware Settings Page
Barracuda Backup Appliance Firmware – Use this section displays the current version of the installed firmware, and allows you to set
your Firmware Upgrade Policy and install a new firmware release based on the selected policy:
Legacy Release – Access a previously installed version of the firmware; do not select this option unless directed to do so by Ba
rracuda Networks Technical Support.
General Release – The latest generally available version of the firmware available for use on Barracuda Backup.
Early Release – The newest firmware versions available for early access to Barracuda Backup.
Firmware Available – Click Check for new firmware to determine if a new firmware version is available. If a newer version is
available, you are prompted to download and apply the new firmware.
Manual Firmware Update Availability – Use this section to manually update device firmware; you must first download the firmware and
upload it to the device through the local user interface.
Release Notes – View Barracuda Backup release notes including new features and resolved issues.
See Also
Firmware Upgrade Policy

How to Upgrade Firmware
How to Upgrade Firmware on a Local Control Appliance
Barracuda Backup Appliance Settings Page
Specify the Barracuda Backup appliance settings including:
Backup Appliance Name – Enter a name to identify the Barracuda Backup appliance in the web interface.
Backup Appliance Time Zone – From the drop-down menu, select the time zone where the Barracuda Backup appliance is located.
Backup Appliance Location – Enter the Barracuda Backup appliance physical location details.
Backup Appliance Display Group – If you have created display groups, select the group in which to display the Barracuda Backup
appliance from the drop-down menu. Click Manage your display groups to go to the Admin > Display Groups page where you can
create and update display groups.
Backup Export Tool Settings – If you are using the Backup Export Tool, enter the IP address of the Backup Export Tool host.

See Also
How to Update Appliance Settings

How to Configure Barracuda Backup
Display Groups page
Backup Export Tool
How to Install and Configure the Backup Export Tool
Software Downloads
Download tools for use with Barracuda Backup.
See Also


Bare Metal Restore
GroupWise Message-Level Backups
Restoring SharePoint Objects Using Kroll Ontrack
Backup Export Tool
Advanced Graphs Page
View detailed system performance information on the Advanced Graphs page.
See Also
Advanced Graphs


See also: Firmware Upgrade Policy
Firmware Update
Use the System > Firmware Settings page to select the firmware upgrade policy:
Current Installed Version – Displays the currently installed firmware version

Firmware Upgrade Policy – Select the release stage you want to update to the latest firmware:
Legacy Release – Access a previously installed version of the firmware; do not select this option unless directed to do so by Bar
racuda Networks Technical Support.
General Release – The latest generally available version of the firmware available for use on Barracuda Backup.
Early Release – The newest firmware versions available for early access to Barracuda Backup.
Firmware Available – Specifies the latest firmware version available based on the selected Upgrade Policy
Upgrade Now – If a newer version of firmware is available, click Upgrade Now to upgrade the firmware
View release notes – Click to view the Barracuda Backup release notes
Firmware Notification
If a newer version of firmware is available, once you log in to Barracuda Backup, the Dashboard page displays a notification banner across the
top of the page. Click Upgrade Now to immediately begin the firmware upgrade, or click Dismiss to hide the banner until the next time you log in
to the web interface.
If a backup job is running and you select to upgrade the firmware, the firmware upgrade is queued until the existing job is completed.
Firmware Update, Local Control Appliance
When managing your Barracuda Backup appliance independently of Barracuda Networks Cloud through Local Control, update firmware on the S
ystem > Firmware Settings page. For step-by-step instructions, see How to Upgrade Firmware on a Local Control Appliance.

Firmware Upgrade Policy
Verify you are running at least the Legacy Release firmware to ensure compatibility with the Barracuda Backup cloud UI and services
such as replication. Firmware versions older than the latest Legacy Release are not supported.
Energize Updates
Barracuda Backup requires an Energize Updates subscription for firmware upgrades and Technical Support. Energize Updates are also required
to maintain compatibility with the Barracuda Backup Cloud (accessed through login.barracuda.com). Barracuda Backup performs updates to the
cloud to maintain compatibility with the latest legacy, general, or early release firmware versions. Barracuda Backup devices with expired
Energize Updates running unsupported firmware versions may experience difficulties using the Barracuda Backup Cloud for management as well
as services such as data replication.
This does not apply to the local web-based management interface which is accessible for restores or the Local Control management option.
If your Energize Updates Subscription expires, contact Barracuda Sales to renew your subscriptions.
Note that Barracuda Backup devices managed using Local Control (independent of Barracuda Cloud Control) has access to firmware
releases on a delayed schedule.
Automatic Firmware Upgrades
Barracuda Backup enables administrators to perform manual upgrades at a time that is convenient, however, Barracuda performs automatic
upgrades for Barracuda Backup devices with an active Energize Update subscription if they are running unsupported firmware versions.
After a major firmware version has completed the rollout phase, Barracuda sends an upgrade notification, providing 30-day's notice before the
upgrade takes place. This notification includes information on new features, bug fixes, and end-of-life announcements. You must subscribe to em
ail notices to receive the upgrade notifications.
Devices connected via site-to-site replication must be running matching firmware versions to ensure compatibility.
Firmware Release Example
Note that the information listed in the table below may not be current. Go to the System > Firmware Settings page in the web interface for the
latest firmware availability.
To view all historical firmware releases, refer to Minimum Supported Versions and Historic Releases.
Major Firmware Latest Maintenance Release Firmware Upgrade
Version 6.4 6.4.03 Early Release
Version 6.3 6.3.04 General Release
Version 6.2 6.2.04 Legacy Release
Warning
Early Release firmware is subject to partial testing. Be aware of the risks before upgrading as firmware versions cannot be reverted.

Minimum Supported Versions and Historic Releases
To ensure interoperability with Barracuda Cloud Control, cloud connected Barracuda Backup systems must run the latest firmware
version. Download and install the latest available firmware from the System > Firmware Settings in the web interface. Additionally:
You must have an active Energize Update (EU) subscription and be running the latest minimum supported firmware for
Barracuda Cloud Control support
Firmware version must be upgraded to the latest version (legacy, general, or early)
If firmware version is not maintained, you will lose interoperability with Barracuda Cloud Control; the local restore browser
remains accessible for data recovery
If your Barracuda Backup product no longer has EU, and there is no intention to renew EU, you can restore from the local UI or
convert the system to local control to manage the system independent of Barracuda Cloud Control
Table 1. Minimum Supported Versions
Current Release Release Date Minimum Legacy Release General Release Early Release
Supported
Versions
6.4 June 6, 2017 Firmware 6.2.04 6.3.04 6.4

version 6.3
Barracuda
Backup Agent
6.3.04
(Windows)
Barracuda
Backup Agent
6.3.04 (Linux)
Bare Metal Live
CD 6.3.04
(64-bit)
Bare Metal Live
CD 6.3.04 (32-b
it)
GroupWise
Trusted
Application Key
Generator
Backup Export
Tool (BET)
Local Control
Offsite Vaulting
Cloud LiveBoot
Microsoft
Windows,
Exchange,
SQL, and
Hyper-V
support
VMware
support
SIte-to-site
replication
Supported
servers and
data types
Table 2. Historic Releases
Version Release Date Main Feature(s) Description

6.4 June 6, 2017 New Dashboard The Dashboard has been

redesigned for an improved
Configure Barracuda Backup Vx the user experience. When
to replicate to a physical looking at their backup
appliance account, customers and
resellers will get an
aggregate view of all their
units. This view changes
during Barracuda Backup
appliance selection to view
specific detail about a
selected unit.
You can configure the
Barracuda Backup Vx
appliance to replicate
bi-directionally to another
Barracuda Backup Vx or to
a Barracuda Backup
appliance.
With a Receiver Vx
subscription, you can pair a
physical appliance and a
Barracuda Receiver Vx,
one-to-one. Replication from
physical appliances to a
Receiver Vx is limited to
Barracuda Backup models
190 through 690.
6.3 July 25, 2016 Backup Agent Update and Boosts initial backup speed and
exporting to AWS Storage recovery performance by up to
Gateway-VTL 1.5-2x on large files and up to 3x
for file server backups with
millions of small files with the
Barracuda Backup Agent for
Windows and Linux.
6.2 August 2015 Backup Summary Report New Barracuda Backup

Summary Report, reporting
downloads and improved
granularity for scheduling.
6.1 June 2015 Export to tape or disk Export historical data from
Barracuda Backup using the
Backup Export Tool.
6.0 September 2014 Local Control Administer your Barracuda

Backup appliance independently
of Barracuda Networks' Cloud in
a "connectionless" state.
5.4 January 2014 Offsite Vaulting Extend offsite retention policies

for up to twelve monthly and
seven yearly revisions.
5.3 September 2013 Microsoft Windows 8/2012 Support for Microsoft's latest
Microsoft Exchange 2013 version of Windows, Exchange,
Microsoft SQL 2012 SQL, and Hyper-V.
Microsoft Hyper-V 2012 CSV
5.2 May 2013 Cloud LiveBoot Instantly boot a virtual machine

from Barracuda's Cloud.
5.1 February 2013 Restore to Copy Restore data to a Copy account

Large Items Reporting for synchronization and sharing.
5.0 December 2012 LiveBoot Boot a virtual server instantly

from Barracuda's local storage.

4.3 July 2012 Barracuda Backup 1090 New high capacity backup
64-bit hardware appliance and update all
systems to the 64-bit
architecture.
4.2 April 2012 VMware Support Agentless VMware backups

using the vStorage APIs.
4.1 November 2011 Bare Metal Recovery Perform a full system restore
without installing the operating
system.
Deprecated support for Windows
2000.
4.0 June 2011 Box-to-box replication Offsite replication between

Barracuda Backup appliances

How to Manually Upgrade Firmware
Important
When the Barracuda Backup firmware is updated, all associated Agents are automatically updated to the latest build when the
scheduled backup runs.
Upon upgrading to a major firmware version, the Backup Agent performs a one-off consistency check which may result in a longer
running backup schedule.
To manually upgrade Barracuda Backup firmware:

1. Log in to Barracuda Backup, and go to the SYSTEM > Firmware page.
2. From the Firmware Upgrade Policy drop-down menu, select Manual.
3. In the Manual Firmware Update Availability section, click on the firmware release you wish to download to your local system.
4. Upload the firmware using the tools in the Barracuda Backup Appliance Firmware section.
5. Click Save at the top of the page once the firmware upgrade is complete.
Release Notes
Review the Release Notes after upgrading your firmware for important updates.

How to Upgrade Firmware

When you log in to the Barracuda Backup web interface, if there is a newer version of firmware available (based on the currently selected Firmw
are Upgrade Policy), the Dashboard page displays a notification banner across the top of the page. Click Upgrade Now to proceed to the Syst
em > Firmware Settings page to upgrade your firmware, or click Dismiss to hide the banner until the next time you log in to the web interface.
Important
When the Barracuda Backup firmware is updated, all associated Agents are automatically updated to the latest build when the
scheduled backup runs.
Upon upgrading to a major firmware version, the Backup Agent performs a one-off consistency check which may result in a longer
running backup schedule.
To upgrade Barracuda Backup firmware:
1. Log in to Barracuda Backup, and go to the System > Firmware Settings page.
2. From the Firmware Upgrade Policy drop-down menu, select the upgrade policy from the following options:
Legacy Release – Access a previously installed version of the firmware; do not select this option unless directed to do so by Ba
rracuda Networks Technical Support.
General Release – The latest generally available version of the firmware available for use on Barracuda Backup;
recommended.
Early Release – The newest firmware versions available for early access to Barracuda Backup; do not select this option until
thoroughly reading the release notes.
3. Click Check for new firmware, and allow the system to check for a newer version of firmware.
4. If a new firmware release is available, click Upgrade Now and allow the system to update.
5. Click Save at the top of the page once the firmware upgrade is complete.
Review the Release Notes after upgrading your firmware for important updates.

How to Upgrade Firmware on a Local Control Appliance
This article refers to the Barracuda Backup Legacy Release firmware or newer in Local Control.
Before enabling Local Control, to receive firmware update notifications, you must configure an email contact within Barracuda Cloud
Control. This is usually the email account you use when setting up your Barracuda Cloud Control account.
Complete the following steps to upgrade the firmware on a Local Control appliance:
1. Log in to the Barracuda Backup Local Control web interface, and go to the System > Firmware page.
2. Click download the newest Firmware Package:
3. Save the firmware package to your local system:
4. In the web interface, to the right of Firmware Package file, click Browse, and select the firmware package you downloaded to your local
system:

5. Once the file is selected, click Upload Firmware Package:
6. The firmware package is now loaded. Click Upgrade Now to begin the firmware upgrade:
7. Allow the upgrade to complete; this may take up to 10 minutes. A notification displays when the upgrade process is complete:

7.
8. Click OK to close the notification. Allow approximately 10 minutes for services to update and restart. Refresh your browser to see the
changes in the web interface.



How to Update Appliance Settings

Use the following steps to add or update Barracuda Backup settings in the System > Barracuda Backup Appliance Settings page:
1. Log in to Barracuda Backup, and go to the System > Barracuda Backup Appliance Settings page.
2. In the Barracuda Backup Appliance Name (Serial Number) section, enter a name used to identify the currently selected Barracuda
Backup Server in the web interface.
3. In the Barracuda Backup Appliance Time Zone field, select the time zone where the currently selected Barracuda Backup appliance is
located.
4. In the Barracuda Backup Appliance Location section, enter the physical location of the Barracuda Backup appliance including city,
state, and country.
5. In the Barracuda Backup Appliance Display Group section, if you have created display groups, from the drop-down menu, select the
group in which to display the Barracuda Backup appliance.
6. To add or remove a display group, click Manage your display groups, or go to the Admin> Display Groups page.
7. If you want to set up the Backup Export Tool, enter the IP address of the Backup Export Tool host in the Host IP Address field.

Software Downloads Page

Go to the System > Software Downloads page to download tools for use with Barracuda Backup including:
Barracuda Bare Metal Live CD


Advanced Graphs Page

To view Advanced Backup Graphs, log in to the web interface, select the Barracuda Backup appliance in the left pane, and go to the System >
Advanced Graphs tab. Click on a section heading to view historical data.
Local Ethernet Traffic
The Local Ethernet Traffic graph presents inbound and outbound network traffic for the selected Barracuda Backup appliance:
Barracuda Central Bandwidth
The Barracuda Central Bandwidth graph represents the bandwidth utilization from the Barracuda Backup appliance to the Barracuda Networks
Cloud Servers:
Node Latency
The Node Latency graph represents the latency between the Barracuda Backup appliance and the cloud node:
Disk Space
The Disk Space graph provides a detailed account of the amount of disk space that has been used on the Barracuda Backup appliance, as well
as the remaining available disk space:

Queue Size
The Queue Size - Barracuda Cloud graph presents a graphical history of the amount of data replicated over time from the Barracuda Backup
appliance to the Barracuda Cloud:
Queue Count
The Queue Count - Barracuda Cloud graph represents the number of parts replicated over time:
Transfer Efficiency
The Transfer Efficiency graph provides a detailed look at data replication from the Barracuda Backup appliance to the replication target
(Barracuda Cloud or another Barracuda Backup appliance). In the graph below, the green shaded area represents the Skipped or deduplicated
data. The blue, TX (Uncompressed), represents the actual data being transferred and the amount of bandwidth that would be used if

compression was not utilized. The orange, TX (Compressed), represents the actual bandwidth utilized, after compression, to send data offsite.
The red Purged amount refers to data removed from the offsite transfer queue that has already been purged locally:
Processor Utilization
The processor utilization graph represents the following:
System – Percentage of CPU utilization that occurred while executing at the system level (kernel).
User – Percentage of CPU utilization that occurred while executing at the user level (application).
Nice – Percentage of CPU utilization that occurred while executing at the user level with nice priority.
IO Wait – Percentage of time that the CPU or CPUs were idle during which the system had an outstanding
disk I/O request.
Idle – Percentage of time that the CPU or CPUs were idle and the system did not have an outstanding disk I/O request.
Metadata Queue Length
The Metadata Queue Length graph provides a graphical representation of the reporting and statistics data transfer over time:
Load Average

The Load Average graph details the history of running processes over time:

Admin Page
This article refers to the Barracuda Backup Legacy Release firmware or newer
Use the Admin page to configure users, set up email notifications, manage display groups, and link a Barracuda Backup appliance.
Users Page
Administer users that have access to the Barracuda Backup web interface. Click the Edit icon to modify email notifications, authentication, and
permissions for the selected user, or click Add & Remove Users to add a new user, edit details for an existing user, or delete a user.
If you are an administrator, you can modify your profile in the following manner:
1. Go to Admin > Users, and click Add & Remove Users, or click the Home link in the left pane.
2. Click My Profile to select your preferred language, set up multi-factor authentication, and set the time zone for your user account.
3. Click Save to apply your settings.
See Also
Managing Users
Managing Your Account
Email Notifications
You can specify whether a user on the account receives email notifications whenever a report generates on the Admin > Users page, or add
additional email notification recipients on the Admin > Email Notifications page. Add an email notification recipient and specify the type of email
notifications:
Backup Summary Reports – When selected, an email notification is sent about the last run of each scheduled backup from the
previous day.
Backup Detailed Reports – When selected, a report is sent each time a backup job completes including a list of backed up items.
Alerts – When selected, an email notification is sent if a backup job has errors or if your Barracuda Backup appliance is offline.
Notices – When selected, an email notification is sent when your Barracuda Backup appliance software is updated.

See Also
Managing Email Notifications
Display Groups Page
Add and remove display groups to manage multiple Barracuda Backup appliances.
See Also
Display Groups
Activate Backup Product
Link your Barracuda Backup appliance to your Barracuda Cloud Control Account.

See Also
Link a Backup Appliance to an Account

Unlink a Barracuda Backup Appliance
AWS Credentials Page
Access the AWS Account wizard to add your Amazon Web Services (AWS) Account to Barracuda Backup, and configure AWS replication and
restore.
See Also

Online Service Terms Page
Click to view the Barracuda Terms of Service.

Users Page
Use this page to administer users that have access to the Barracuda Backup web interface.
From the Admin > Users page, you can complete the following actions:
Click Add & Remove Users to add or remove users

Click the Edit icon to the right of a user name to modify email notifications, set IP login restrictions, and set the user's role:
Account Administrators have full access to all Barracuda Backup Appliances within the account.
Barracuda Backup Appliance Administrators have full access to backup appliances selected below, minus the ability to
edit/view user accounts.
Operators are limited to viewing statistics and modifying backup configuration for selected Barracuda Backup Appliances.
Operators cannot restore data or edit user accounts.
Helpdesk users are limited to viewing the Dashboard page, the restore browser and restore reports on Barracuda Backup
Appliances. Helpdesk users can restore data and stop running restores.
Status users are limited to viewing the Dashboard page on Barracuda Backup Appliances.
See also:
Manage Your Account

Manage User Access
Manage Product Entitlements

Managing Your Account

Your Barracuda Cloud Control account gives you access to Barracuda Backup, Barracuda Networks services to which you have a subscription,
and any devices added through Barracuda Appliance Control. As long as you are logged in as an administrator, you can add users and assign
roles. Each user uses their own user name to log in.
Select Account Options
Click the Home link in the left pane to perform these account-related tasks:
Add, edit and remove users, including setting their privileges and start page. When you add a user you can select the services that
the user is able to access.
View audit logs.
Update contact and billing information for your Barracuda Cloud Control account.
View invoices.
Manage services associated with your account.
Configure account security and authentication.
Click Backup in the left pane to go to the Barracuda Backup web interface.
Community
Click Community at the top right of the web interface to access product forums and add your own feedback. Use forums to discuss and view
feature requests. For additional information, refer to Barracuda User Community.
Your Account
Click My Profile to perform the following tasks:
Set preferred language

Set up multi-factor authentication
Set the time zone for your user account
Support
Click Support at the top right of the web interface to perform the following tasks:
Search Barracuda Networks Knowledgebase solutions

Access the Barracuda Networks Campus
Contact Barracuda Networks Technical Support
Access existing support cases, or open a new case
Manage your Barracuda Backup Server serial numbers

Managing User Access

Use the Admin > Users page to administer users that have access to the Barracuda Backup web interface. This page has a link that takes you
to Account/Support to add or remove users.
Edit user details from this page by selecting a user and clicking Edit to the right of the user. You can edit the following user options, all of which
are specific to this service:
Receive emails with backup reports, error condition alerts, or Barracuda Backup Server software update notices.
Restrict access to the Barracuda Backup web interface to one or more IP addresses.
Designate the user as an Account Administrator, Barracuda Backup Appliance Administrator, Operator, Helpdesk, or Status user.
Account Administrator has full access to all Barracuda Backup Appliances within the account.
Barracuda Backup Appliance Administrator has full access to backup appliances selected below, minus the ability to edit/view
user accounts.
Operator is limited to viewing statistics and modifying backup configuration for selected Barracuda Backup Appliances.
Operators cannot restore data or edit user accounts.
Helpdesk is limited to viewing the Dashboard page, the restore browser, and Barracuda Backup Appliance reports. Helpdesk
users can restore data and stop running restores.
Status is limited to viewing the Barracuda Backup Dashboard page.

How to Set User IP Restrictions

A restricted IP address must be a public address.
Use the following steps to restrict the IP address from which a user can log in to the Barracuda Backup web interface.
1. Log in to Barracuda Backup, and go to the Admin > Users page.

2. Click the Edit icon to the right of the user whose restrictions you want to modify.
3. In the IP login restrictions field, enter an IP block in single 192.168.1.100 notation, CIDR net block 192.168.1.0/24 notation, or a range
in 192.168.0.0-192.168.0.128 notation to restrict the IP address for the selected user. Use a comma to separate multiple IP blocks.

How to Set Product Entitlements
Set Product Entitlements
Use the following steps to add Barracuda Backup entitlements when you add a user to your Barracuda Cloud Control account.
Alternatively, if you are already logged in to Barracuda Backup, click Admin > Users and complete these steps.
1. Log in to Barracuda Cloud Control as the administrator, click Home in the left pane, and go to the Admin > Users page.
2. Click Add User; the new User Details displays.
3. Enter the new user's first and last name in the Name field, and enter their Email address; the user email address will serve as their
username.
4. Select the Starting Page for this user upon log in from the following options:
Default
Community/Forum
Account
Support
5. If you are using Multi-Factor Authentication, complete this section.
6. In the Privileges section, select from the following options:
a. User Management – Specify whether the user can add, remove, and edit users.
b. Billing Administration – Specify whether the user can update billing information for this account.
7. In the Product Entitlements section, click Backup (Admin).
For details on adding additional subscribed to Barracuda Networks products and services, refer to Connecting Barracuda
Networks Products to Barracuda Cloud Control.
8. Click Save User at the top of the page to add the user to Barracuda Backup; an email is then sent to the user prompting them to set their
password.
9. Click on the username in the Users list; the User Details section displays in the right pane. In the Product Entitlements section under
Backup (Admin), click Configure Permissions.
10. In the configuration page, configure Email Notifications:
Backup Summary Reports – When selected, a summary report is sent to this user for each appliance daily.
Backup Detailed Reports – When selected, a detailed report each time a backup job completes, including a list of all backed
up items.
Alerts – When selected, an alert is sent to this user if an error occurs during a backup job or if a Barracuda Backup appliance
goes offline.
Notices – When selected, a notice is sent to this user when the Barracuda Backup appliance software is updated.
11. If you have multiple appliances on an account, you can selectively limit visibility. To restrict the IP address that this user is allowed to log
in from:
a. In the IP login restrictions field, enter an IP block in single 192.168.1.100 notation, CIDR net block 192.168.1.0/24 notation or a
range in 192.168.0.0-192.168.0.128 notation to specify the IP addresses from which this user is allowed to log into Barracuda
Backup.
b. Separate multiple IP blocks or ranges with a comma.
12. From the User role drop-down menu, select permissions for this user:
a. Account Administrator – User has full access to all Barracuda Backup appliances within the account.
b. Barracuda Backup Appliance Administrator – User has full access to all selected Barracuda Backup appliances; user does
not have edit or view user accounts access. When selected, the Grant access to section displays:
Select All Backup Appliances –When selected, user has full access to all Barracuda Backup appliances within the
account. When cleared, a list of all connected Barracuda Backup appliances displays. Turn on the Barracuda Backup
appliances to which this user is to have access.
c. Operators – User access is limited to viewing statistics and modifying backup configuration for selected Barracuda Backup
appliances. Operators cannot restore data or edit user accounts.
Select All Backup Appliances – When selected, user has Operator access privileges to all Barracuda Backup
appliances within the account. When cleared, a list of all connected Barracuda Backup appliances displays. Turn on the
Barracuda Backup appliances to which this user is to have Operator access.
d. Helpdesk – User access is limited to the Dashboard page, the restore browser and restore reports on Barracuda Backup
Appliances. Helpdesk users can restore data and stop running restores.
Select All Backup Appliances – When selected, user has Help Desk access privileges to all Barracuda Backup
appliances within the account. When cleared, a list of all connected Barracuda Backup appliances displays. Turn on the
Barracuda Backup appliances to which this user is to have Helpdesk access.
e. Status – User access is limited to viewing the Dashboard page for Barracuda Backup appliances to which they have access.
Select All Backup Appliances – When selected, user has Status access privileges to all Barracuda Backup appliances
within the account. When cleared, a list of all connected Barracuda Backup appliances displays. Turn on the Barracuda

e.
Backup appliances to which this user is to have Status access.
Note that in firmware version 6.4, the Status page has been renamed to Dashboard in the appliance web
interface. For more information, see Dashboard Page.
The multi-appliance dashboard displays irrespective of the firmware version running on the
appliances.
The single appliance dashboard displays on appliances upgraded to firmware version 6.4; older
firmware versions continue to display the existing Status page.
13. Click Save at the top of the page to save the Backup configuration settings for the selected user.

Email Notifications Page

Email Notification Options
Specify the type of email notification for each user on the account, or users not associated with your account (non-users):
Backup Summary Reports – Sends a daily report for each appliance, including information about the last run of each schedule the
previous day, is sent
Backup Detailed Reports – Sends a detailed report each time a backup job completes, including a list of all items backed up
Alerts – Sends a notification for conditions such as:
A Barracuda Backup appliance is offline or has come online
A Barracuda Backup appliance has not been able to communicate with a Barracuda replication target, that is, another Barracuda
Backup appliance or Barracuda Cloud Storage (check for Internet problems)
A Barracuda Backup appliance, such as a RAID volume or HD hardware, fails
An error has occurred in a backup
An error situation returned to normal and no (further) action is required
You have reached the limit on your Barracuda Cloud Storage subscription plan size
Notices – Sends a notification when the your Barracuda Backup appliance software is updated
Managing Email Notifications
To specify email notifications for a user on the account:
1. Go to the Admin > Users page, and click Edit to the right of the user name.
2. Select the desired notifications in the Email notifications section, and click Save.
To specify email notifications for users not associated with your account (non-users such as your reseller):
1. Go to the Admin > Email Notifications page, and enter an address in the Email Address field.
2. Select the notifications you want the user to receive, and click Add. The email address is added to the Recipients table.

Display Groups Page

See also: Dashboard Page
Display Groups
3. To add a new display group, enter a name for the group of devices in the Display Group field, and then click Add. For example, if you
want to group all Barracuda Backup by location, you might create groups by geographic location: Engineering - Asia, Engineering - US,
Engineering - Europe.
5. To remove a display group, click Remove following the name of the group you want to remove; click OK to confirm you want to remove
the group.
1. In the left pane, select the appropriate Barracuda Backup, and go to the System > Barracuda Backup Appliance Settings page.
2. In the Backup Appliance Display Group section, choose from the Current Display Group drop-down list, select the display group
name.
3. To add or remove display groups, click Manage your display groups to go to the Admin > Display Groups page.
4. Click Save.
Important - Resellers
A group that includes multiple customers displays only those devices for the customer selected from the Current Account drop-down
list. To view all devices for all customers in a group, select Manage all accounts:

Link a Backup Appliance Page

Use this page to set up your Barracuda Backup appliance. The Barracuda Backup appliance must be linked online before backups can be
initiated. See the following articles for details on linking and unlinking a Barracuda Backup appliance:
Link a Barracuda Backup Appliance as a User or Reseller

Unlink a Barracuda Backup Appliance

How to Link a Barracuda Backup Product as a User or Reseller

Important
If you are an Intronis customer, contact Intronis before proceeding.
If you are linking a Barracuda Backup Virtual Appliance (Vx), it is crucial that the Barracuda Backup Vx that will be performing backups
be linked to your Barracuda Cloud Control account before you link the receiving unit. Attempting to link the receiving unit first can cause
linking issues for your entire Vx deployment.
The Barracuda Backup appliance must be linked online before backups can be initiated. You must have billing information (credit card
recommended) to complete the linking process.
Link a Barracuda Backup Appliance as a User
1. Go to http://login.barracuda.com, and log in. If you do not have an account, click Create a User, follow the account creation instructions,
and log in.
2. Click Backup in the left pane. If this is your first time linking a Barracuda Backup appliance, click Start Backup setup, otherwise, click
the Backup tab, and go to Admin > Activate Backup Product.

3. Enter the Serial number and Linking code from the sticker on the back of your Quick Start Guide included with the appliance, and
select This Barracuda Backup is for me or my company in the Identity section. Click Continue.
4. Enter the geographical location of the appliance, and select the timezone of the appliance location.
To manage the appliance independently of Barracuda Cloud Control (conectionless), turn on Locally control device under De
vice Management, and proceed to Step 6 below.
5. To replicate data to Barracuda Cloud Storage, in the Services section, select Replicate data to Barracuda Cloud Storage, and select
the Storage Amount and Subscription Period; no Cloud Storage subscription is required for site-to-site replication:
6. Enter your Billing Information. Read and accept Terms of Service.

7. Click Activate Barracuda Backup:

7.
8. Once the appliance is linked, the firmware is updated and the appliance reboots. When the unit comes back online you must log out and
then log back in to the user interface to clear any cached pages.
9. You can now set up data sources on the Barracuda Backup appliance.
Link a Barracuda Backup Appliance as a Reseller
Use these steps to link the client appliance as a reseller:
1. Go to http://login.barracuda.com, and log in. If you do not have an account, click Create a User, follow the account creation instructions,
and log in.
2. Click Backup in the left pane. If this is your first time linking a Barracuda Backup appliance, click Start Backup setup, otherwise, click
the Backup tab, and go to Admin > Activate Backup Product.

3. Enter the Serial number and Linking code, select I am a reseller and this Barracuda Backup is for a client, and click Continue.
4. When selected, an additional set of dialog boxes display where you add the end-user information. Click Continue.
The details added in this set of dialog boxes are used to create an account to which the unit is linked, and to which the reseller
is then granted access. This allows a reseller to manage multiple Barracuda Backup appliances from one central location in
the UI, while giving the end-customer access to their individual appliances. Note that a reseller can determine whether to have
access to the appliance once it is linked.
5. In the next page, enter the physical location and time zone details, and choose a Cloud Storage subscription plan if your client intends to
6. In the Billing Information section, enter the client's billing information.
7. In the Client Information section, select Grant me (the reseller) administrative access to this Barracuda Backup Appliance if you,
the reseller, want access to the unit after it has been linked.
If you clear the Grant me (the reseller) administrative access to this Barracuda Backup Appliance option, the only way to
manage the linked unit is through the end-user (client) credentials.
8. Enter the client's Company name, the client contact's Name and Email address.
9. Select whether the Client should receive email based alerts:
10. Enter the client Phone number and Address.
11.

11. Read and accept Terms of Service.

13. Once the unit is linked, the firmware is updated and the appliance reboots. When the unit comes back online you must log out and then
log back in to the user interface to clear any cached pages.
14. You can now set up data sources on the Barracuda Backup appliance.

How to Manage Accounts and Barracuda Backup Appliances as a Reseller

When you log in to Barracuda Cloud Control, and click the Barracuda Backup tab, the reseller account and its associated Barracuda Backup
appliances display. From this view, you can select to load all devices across all accounts to view the overview statistics.
The Barracuda Backup appliance must be linked online before backups can be initiated. You must have billing information (credit card
recommended) to complete the linking process.
1. Go to http://login.barracuda.com, and log in using your credentials.
Click Backup in the left pane. Your customer accounts display in the left pane including linked Barracuda Backup appliance status:
Health Indicators
– Health is good
– Health is at risk (warning)
– Health is critical
2. Once you are logged in, the status of all of the Barracuda Backup appliances linked to your account display:
3. Click on a Barracuda Backup appliance in the left pane, or click on an appliance in the Barracuda Backup Appliances list to select and
manage a specific appliance.
4. To switch to an account for a specific client, click Home in the left pane:
5. The Admin page displays. From the Current Account drop-down list, select the client account you want to
manage:
Switching to a client account allows you to manage account-specific information such as creating, editing, and removing users,
viewing Barracuda Backup appliance and service status, viewing an audit log, managing billing, and configuring account
security and authentication.
6. Once you select the account, click Backup in the left pane to return to the Barracuda Backup Dashboard to select specific appliances to
manage.

AWS Credentials Page

Access the AWS Account wizard to add your Amazon Web Services (AWS) Account to Barracuda Backup, and configure AWS replication and
restore on the Admin > AWS Credentials page.

Cloud Backup Web Interface

This section describes each page in the Barracuda Cloud-to-Cloud Backup web interface. For Barracuda Backup appliance web interface, see Ap
pliance Web Interface.
After activating Barracuda Cloud-to-Cloud Backup, get familiar with the product user interface.
In this Section
Status Page - Cloud Backup

Backup Page - Cloud Backup
Restore Page - Cloud Backup
Reports Page - Cloud Backup
System Page - Cloud Backup
Admin Page - Cloud Backup

Status Page - Cloud Backup
The Status page provides an overview of your backup activity and storage details. Click on a graph to view a larger display of the data.
Mobile Access
You can also view Barracuda Backup appliance status using Barracuda Networks Mobile Applications.
Backup Activity Section
The two graphs in this section display cloud storage backup activity indicating the size and the number of backup items and data added by date.
Storage Efficiency Statistics
This section displays storage efficiency statistics including raw data and actual storage in the cloud.
Table 1. Storage Efficiency Statistics.
Raw Data Total amount of data sent to Barracuda Cloud Backup including
revisions.
Items Total items sent to Barracuda Cloud Backup.
Actual Storage The amount of actual storage space being used.
Snapshot The amount of space that would be required to back up your data
Equivalent based on your retention policies projected over the next three years,
without deduplication and compression.
Deduplication The overall amount of space savings calculated by dividing raw data
Ratio by actual storage space.
Storage History
This table displays the Barracuda Cloud Backup Storage History. View current, historic, and actual data storage size (in GB) in the cloud by date.
Table 2. Storage History.
the cloud.
Raw Current Represents current content sent to the cloud before deduplication
processing.
Actual Storage Represents the total content currently stored in the cloud.

Backup Page - Cloud Backup
Use the Backup page to manage how data is backed up.
Location Description
Backup > Sources Use this page to configure Office 365 data sources:
Identify systems to be backed up

Select the type of data to be backed up
Related Articles

Backup > Schedules Once you configure data sources, use this page to create backup
schedules.
Related Article
Schedules Page
Backup > Retention Specify how long to keep daily, weekly, monthly, and yearly backups
Policies by creating data retention policies. Different retention policies can be
created for different sets of data.
You can create one policy for all data sources or multiple policies that
each include a subset of the data.
Related Article
Retention Policies Page

Retention Policies Page - Cloud Backup
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, forever, or never.
Important
Configure retention policies for data stored in Barracuda Cloud Backup on the Backup > Retention Policies page. Be sure to configure retention
policies for your data. Not doing so means that some unwanted data will be moved across the Internet and stored.
How it Works
Historic data is retained according to the retention policy timeline. Data backed up using Barracuda's cloud treats Sunday as the end of week in
accordance with the ISO date standard.
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 data sources on a Barracuda Backup
Server, or create different policies that include subsets of the data.

Schedules Page - Cloud Backup

See also:


deselect all days:
days:


Restore Page - Cloud Backup
Use the Restore page to restore data from Barracuda Cloud Storage. You can restore single files or entire systems.
Restore > Restore Use this page to restore backed up Office 365 data sources.
Browser
Related Article


How to Restrict Search to Current Folder in Restore Browser

Use the following steps to limit your search for items to the current directory in the Restore Browser:
1. Log in to Barracuda Backup using https://login.barracudanetworks.com/, and select the Cloud Source in the left pane.
2. Go to the Restore > Restore Browser page, and select the target data source.
3. Navigate to the desired directory, and enter a word or phrase as the search string in the Search field.
4. Click Search this Folder:
5. The search results display.
You can now restore or download the desired item.

Reports Page - Cloud Backup
Use the Reports page to view backup and restore details as well as an audit log of all activities in the Barracuda Cloud Backup web interface.
Reports > Backup Barracuda Backup provides a detailed report for each backup that is
run. In addition, any backup process currently running displays.
Backup reports include details about the backup such as when the
backup started, duration, size, if there were any errors or warnings,
and any new, changed, or removed items. Reports also include links
to each backed up file to view or download the item from the report.
Click Details to view recent activity in chart form. You can also view
a list of backed up files including the number of new, changed, and
removed files, as well as a list of any errors encountered during
backup.
Click Download the report as a .csv file to your local system.
Reports > Restore You can view restoration details in the Reports > Restore page. To
specify how you want to sort the table, click on a heading, and then
click on the up/down arrows to the right of each heading to specify
either an ascending or descending sort.
Click Details to view all details for the selected restoration including
any encountered errors.
Reports > Audit The Reports > Audit Log page displays a report of all activities in
Log the Barracuda Cloud Backup web interface by time and date, by
user, and by action. Logged activity includes log on authentication,
changes to settings, changes to account information, and more.
Click Details for additional information for a specific activity.

System Page - Cloud Backup
Use the System page to specify a name to identify Barracuda Cloud Backup in the web interface and set the time zone for the cloud provider.
System > Settings Enter a name to identify Barracuda Cloud Backup in the web
interface, and select the time zone for the cloud provider.
System > Tech Access the Barracuda documentation and help content.
Documentation

Admin Page - Cloud Backup
Use the Admin page to configure users, set up email notifications, manage display groups, activate a Backup product, and access
documentation.
Admin > Users Use this page to administer users that have access to the Barracuda
Cloud Backup web interface. Click the Edit icon to modify email
notifications, IP login restrictions, and the user role for the selected
user, or click Add & Remove Users to add a new user, edit details
for an existing user, or delete a user.
Admin > Email Specify the type of email notification for each user:
Notifications
Backup Summary Reports – When selected, an email
notification containing a summary of each backup job is sent.
Backup Detailed Reports – When selected, an email
notification containing a list of all items backed up is sent.
Alerts – When selected, an email notification is sent if a backup
job has errors.
Notices – When selected, if the account includes physical
appliances, a notice is sent when the Barracuda Backup
software is updated.
Admin > Display Groups Add and remove display groups to manage multiple Barracuda
Backup appliances.
Admin > Activate Backup Product Link a Barracuda Backup appliance to your Barracuda Cloud Control
Account.
Admin > Online Service Terms Click to view the Terms of Service.

Users Page - Cloud Backup

Use the Admin > Users page to administer users that have access to the Barracuda Cloud Backup web interface.
Edit user details from this page by selecting a user and clicking Edit to the right of the user. You can edit the following user options, all of which
are specific to this service:
Receive emails with backup reports and error condition alerts.

Restrict access to the Barracuda Cloud Backup web interface to one or more IP addresses. Enter an IP block in single 192.168.1.100
notation, CIDR net block 192.168.1.0/24 notation, or a range in 192.168.0.0-192.168.0.128 notation to restrict the IP address for the
selected user. Use a comma to separate multiple IP blocks.
Designate the user's role:
An Account Administrator can create new users and manage billing information, and has full access to Barracuda Cloud Backup
and all appliances associated with the account.
A Barracuda Backup Server Administrator has full access to specific Barracuda Cloud Backup and all appliances associated
with the account including data restore. A Barracuda Backup Server Administrator cannot edit or view other user accounts.
An Operator cannot restore data or edit user accounts; operators are limited to viewing statistics and modifying backup
configuration.
Help Desk user access is limited to viewing role status, statistics, and the restore browser and restore reports. User can restore
data and stop running restores.
Status user access is limited to viewing the Status page for Barracuda Backup appliances to which they have access.
Click Add & Remove Users to add a new user, edit details for an existing user, or delete a user.

Email Notifications Page - Cloud Backup

Add email notification recipients on the Admin > Email Notifications page:
Backup Summary Reports

Backup Detailed Reports
Alerts
Notices
Enter the email address, select the report type(s), and click Add.

Security
In this Section
Backup Security and Site-to-Site Replication

Barracuda Cloud Storage Standards and Protection
Policy-Based Security
How to Secure Your Barracuda Backup Appliance
Barracuda Backup Login Authentication Using Multi-Factor Authentication

Backup Security and Site-to-Site Replication
When deploying Backup appliances for site-to-site replication, you need to ensure the physical security of these systems. The Barracuda Backup
servers should be configured behind corporate firewalls with appropriate restrictions in place. All data transmitted between Barracuda Backup app
liances is sent encrypted using 256-bit AES.
For additional security measures, customers may choose to set up a private VPN tunnel between sites, however this is not a requirement.

Barracuda Cloud Storage Standards and Protection
Facility Standards
Barracuda Networks leases space in a number of Tier 3 and 4 facilities across the world. Each of these storage locations is equipped with:
Controlled access systems requiring key-card authentication and physical check-in

Video-monitored access points
Intrusion alarms
Locking cabinets
Climate control systems
Waterless fire suppressant systems
Redundant power (generator backup, UPS, no single point of failure)
Redundant Internet connectivity
The Barracuda Cloud Storage infrastructure boasts high-quality RAID hardware with hot-spare drives in every file server, and near instant data
mirroring over high-speed fiber connections between the storage locations.
Storage
In the United States, data is transmitted from Barracuda Backup Servers to one data center, and then replicated to another. The process of
replicating data begins immediately after it is copied from a Barracuda Backup Server, and runs continuously. Data in Barracuda Cloud Storage is
stored in parts, and no single computer in the storage system has all the parts required to reconstruct data. Each of these computer systems
communicates in unison to deliver restored data securely. This diverse storage system serves to further strengthen the physical security of your
data.
With this architecture, Barracuda Networks equipment can maintain up to three distinct copies of your data which can be stored in three
geographically separate locations.
Oversight
Access to Barracuda Backup Servers is limited to approved Barracuda Networks employees on an 'as needed' basis. Employee activity is logged,
and all logs are archived to an independent storage device.
Verify Service Plan Size
After you have successfully linked your Barracuda Backup Server, your Barracuda Cloud Storage service plan is activated. To ensure that you
have a sufficient amount of offsite storage space at Barracuda Networks, it is important for you to verify that the plan size is the one you selected.
View your Barracuda Cloud Storage service plan size on the Dashboard tab of the Barracuda Backup web interface.

Policy-Based Security
Data retention policies allow you to specify the retention of selected files or broader data based on daily, weekly, monthly or annual time intervals.
You can create multiple retention policies for different types of data:
Files
Data backed up by the Barracuda Backup Agent (Exchange, SQL, system state)
Email messages
Retention policies are the only way to purge data; data cannot be deleted directly by a user.

How to Secure Your Barracuda Backup Appliance
The Barracuda Backup appliance is deployed behind your corporate firewall, and is protected by the same security as your primary data sources.
256-bit encrypted VPN tunnel. The Barracuda Backup appliance uses HTTPS port 1194 to send status updates to Barracuda Backup. Data
transfers are initiated by the Barracuda Backup appliance rather than by Barracuda Cloud Storage or a remote Barracuda Backup appliance.
Data transferred between your network and Barracuda Cloud Storage, or between your network and a remote Barracuda Backup appliance, is
always encrypted. File parts are AES 256-bit symmetrically encrypted before they are stored, and they remain encrypted until a restore is
requested.
Management Access
account information. Go to the Admin > User page to see all activity for an account, including logins and when a user has enabled or
disabled replication.
ge, click Edit to edit a user account; enter an IP address or a range.
Secure Network Access – HTTPS is used for secure web browser communication with Barracuda Backup unless logging in to the local
web interface.
Encryption
Data transfers from the local Barracuda Backup appliance to a receiving Barracuda Backup appliance are always encrypted. Data is stored
compressed and encrypted at rest on the receiving Barracuda Backup appliance; the local Barracuda Backup appliance does not store in an
encrypted or compressed state. Barracuda Backup utilizes an aggressive combination of symmetrical and asymmetrical encryption. The United
States government recently approved 192-bit AES encryption as the preferred method for protecting top-secret information. The Barracuda
Backup solution starts with even higher 256-bit AES encryption. In addition, Barracuda Networks has developed a proprietary advanced digital
cataloging system that breaks down your data into small pieces and tracks the changes of these parts over time, and strips the original meta
identifiers from your files.

Barracuda Backup Login Authentication Using Multi-Factor Authentication
Multi-factor authentication (MFA), also known as two-factor authentication, is a security feature that requires two forms of authentication to access
Barracuda Backup. When enabled, MFA provides an extra layer of security to your account:
Even if a user's login credentials are stolen, without the trusted device, an attacker cannot access the account, and if a user's device is taken, the
attacker cannot access the account without the login credentials.
MFA is optional by default, allowing the account administrator to determine whether to enable MFA. When enabled, users must download and
install the BCC Mobile App for iOS, Google Authenticator, or Duo Mobile authentication tool to their mobile device to log in to Barracuda Backup
using MFA. These free authentication tools are available for download from iTunes and the Google Play Store.
For details, see Multi-Factor Authentication in Barracuda Cloud Control.

BitLocker
BitLocker Drive Encryption is a Windows data protection operating system feature starting with Windows Vista. Subsequent operating system
releases continue to improve security, providing BitLocker protection to more drives and devices. BitLocker and operating system integration addr
esses the threats of data theft or exposure from lost, stolen, or inappropriately decommissioned computers.
Backup
The Barracuda Backup Agent for Microsoft Windows supports BitLocker Drive Encryption for both operating system drives and data drives. By
default, after booting a system, the operating system drive is "unlocked" and the Barracuda Backup Agent is able to read and access the files. For
data drives, the Auto-Unlock setting must be turned on so that the Barracuda Backup Agent is able to access the encrypted drive. Once all drives
are "unlocked" the files are backed up in an unencrypted state even though the drives are still being encrypted.
To enable the Auto-Unlock setting on Windows Server 2012 R2:
1. Open the BitLocker Drive Encryption Manager from the Control Panel.
2. Select the data drive, and then click Turn on auto-unlock:
3. The encrypted drive is now accessible without password or recovery key prompts.
Recovery
Since the files on the encrypted drives are backed up in an unencrypted state, they are also restored unencrypted. Bare Metal Restoration is
possible for systems using BitLocker Drive Encryption. After performing Bare Metal Recovery, the BitLocker service continues running, but
BitLocker Drive Encryption is disabled for each drive and must be re-enabled from the BitLocker Drive Encryption Manager in the Control Panel.

System Management
In this Section

Barracuda Backup Replacement and Data Migration FAQ
Replacing a Failed Barracuda Backup Appliance
How to Shut Down a Barracuda Backup Appliance
How to Wipe a Barracuda Backup System
Barracuda Backup Panel Indicators, Ports, and Connectors
Barracuda Backup Hardware Specifications
How to Physically Install the Barracuda Backup Appliance
Barracuda Backup Network Interface Bonding
Barracuda Backup Data Transfer IP Ranges
Understanding the Barracuda Backup Service Data Plan
How to Open a Support Tunnel
Related Articles
How to Link a Barracuda Backup Server

How to Unlink a Barracuda Backup Appliance
Software Downloads Page
How to Open a Support Case in Barracuda Cloud Control

If you have any questions or concerns regarding your Barracuda Backup Replacement, contact Barracuda Networks Technical
Support.
Barracuda will migrate configuration data and data residing on the Barracuda Backup appliance and Barracuda Cloud Storage for
customers receiving replacements through:
Instant Replacement
Hardware Refresh
Upgrade/Trade-in Program
See also: Barracuda Backup Replacement and Data Migration FAQ
Pre-Migration Steps
Before you can replace a device and migrate the data, you must first install and configure the new Barracuda Backup device with an IP address,
ensuring that it is online. Use the Barracuda Quick Start Guide included with your appliance (also available as a PDF download from the Overvie
w page). For step-by-step instructions, see the Getting Started section of this library.
You can take these additional steps to ensure a smooth migration and reduce the initial setup time:
Have the replacement device installed and online with a valid IP address (see Barracuda Console)
Verify a support tunnel is open on the old/existing device, preferably before linking the new device (see How to Open a Support Tunnel):
If possible, have both the old/existing device and the replacement/new device on the same networking switch and subnet for the best
data transfer/migration performance
Have the replacement device linked to your Barracuda Cloud Control account (see How to Link a Barracuda Backup Product as a User
or Reseller):

Ensure that any firewall or web filtering rules configured for the old/existing device are configured for the replacement device (see Barrac
uda Console)
Replacement and Data Migration Process
The replacement and data migration process consists of the following steps:
1. An RMA, upgrade, or hardware refresh is processed (see Replacing a Failed Barracuda Backup Appliance).
2. The subscriptions (Energize Updates, Instant Replacement, Cloud) on the old/existing device are moved to the new/replacement device
(see Firmware Upgrade Policy and How to Upgrade Firmware).
3. A replacement/data migration ticket is created and sent to the Barracuda migrations team.
4. An email is sent to the customer with a list of available options for the replacement/data migration process, as described in the Data
Migration Options section below.
5. The customer replies to the email in Step 4 with their selected data migration option.
6. A technical support case/ticket is created to track the replacement/data migration progress.
7. The case/ticket is sent to the migrations team queue.
8. The ticket is picked up based on priority by a Barracuda migrations team member and an email is sent to the customer notifying them
that the replacement/data migration has begun.
9. The configuration (metadata) is pulled from the old/existing device or cloud (based on the option selected by the customer) and copied to
the new/replacement device.
10. After the metadata pull is complete, backups are functional and run as normal. The entire backup configuration is now present on the
new/replacement device and can be accessed and/or modified as normal.
11.

11. The backed up data (binary data) is pulled from the old/existing device or cloud (based on the option selected by the customer) and
copied to the new/replacement device.
12. Once the binary pull is complete, an email is sent to the customer notifying them that the replacement/data migration is complete.
Data Migration Options
Select the data migration option that best suits your deployment.
Option 1. Pull Data from the Cloud
If you elect to pull the data from the cloud, Barracuda Networks uses the following procedure to complete your request:
1. Once the new unit is linked, Barracuda Networks connects to the new device and begins wiping the metadata in the database
ensuring the unit is completely clean of any data.
2. Barracuda Networks then pulls the metadata associated with all binary data (your backed-up data).
The metadata is a description of the data, whereas the binary data is comprised of your actual files.
3. As the metadata is downloaded, it is inserted into the database tables on the new device. Depending on the amount of metadata to
be pulled, this process may take 24 or more hours to complete.
4. Once the metadata download is complete, backups are enabled on the new device, and the binary data is then pulled from the
cloud. The process of pulling the binary data from the cloud can take 24 hours or more depending on the amount of data to be
retrieved.
5. You will receive a notification at the time backups start and the binary data begins to be pulled.
At this point you can make any changes to the configuration via the web interface; the device is now at full capability.
6. Once the initial binary data pull is complete, a final check is run with the cloud to ensure data integrity and to verify that all data is
present and accounted for. Once verification is complete, the data migration as a whole is finished.
7. You will receive a notification indicating the process is complete.
Option 2. Pull Data from an Existing Barracuda Backup Appliance
If you have elected to pull the data from your existing Barracuda Backup appliance, confirm the following:
Both appliances are on the same LAN/subnet, and
Both appliances are linked to a Barracuda Networks Account
1. Once the new device is linked to the existing Barracuda Backup appliance, Barracuda Networks begins prepping the old device for
the migration including:
Shutting down all dependent functions of the old device
Dumping the metadata tables from the databases on the old device in order to pull them across and import them into the
new appliance
2. Once prepping is complete, Barracuda Networks begins the actual data migration by importing the metadata tables from the old
device to the new appliance.
3. Once the metadata import is complete, backups are enabled on the new appliance and backups can run on all data sources. The
binary data is migrated across to the new appliance in the background. The process of pulling the binary data from the old device
can take 24 hours or more depending on the amount of data being migrated.
Running a backup on all data sources assists in populating the new device with the synchronized data. By backing up the
data sources, those data parts that already exist are skipped over, thus reducing the time it takes to complete the process.
4. You will receive a notification alerting you that the backup process has begun on the new device and that data is syncing.
See Also
5. Once the initial binary data pull is complete, a final check is run with the cloud to ensure data integrity and to verify that all data is
present and accounted for. Once verification is complete, the data migration as a whole is finished.
Option 3. Use an Existing Configuration
You can set up and configure a new Barracuda Backup appliance with an existing configuration, data sources, retention policies, and all other
aspects of backup.barracuda.com. This is the fastest type of migration because you are not migrating large amounts of data. To use an existing
configuration:


1. Once the new device is linked, Barracuda Networks pulls the configuration from the cloud.
Option 4. Set Up a New Appliance from Scratch
You can set up and configure a new Barracuda Backup appliance without utilizing an existing configuration. With this option, you must configure
the new device from scratch as it is treated as a brand new unit. For step-by-step instructions on setting up backups, refer to Data Backup Tasks i
n the Getting Started section.

Barracuda Backup Replacement and Data Migration FAQ
Question Answer
What do I do if I need my migration to start immediately? If you are in a disaster or data recovery scenario and require the data
migration process to be prioritized and begin immediately, notify the
Barracuda migrations team member when you reply to the data
migrations email. You can also contact the migrations team at BBSMi
grations_team@barracuda.com.
How long should I expect the data migration to take? The metadata transfer is the most important part of the data
migration process. Once the metadata pull s complete, backups run
on schedule and the backup device has full functionality. The
metadata pull can take up to 48 hours, but in most cases can be
accomplished in just a few hours. The time it takes for the metadata
pull to complete is dependent upon the size of the dataset, the
Barracuda Backup model, and customer bandwidth and/or network
performance.
The binary data transfer usually takes a bit longer than the metadata
transfer and is done in the background while the replacement device
is running normally. Binary data transfers can range from several
hours to days or even weeks, depending on the size of the dataset,
the Barracuda Backup model, and customer bandwidth and/or
network performance. Another factor affecting the binary data
transfer is the available processing resources on the Barracuda
Backup device. Devices that are performing backups around the
clock, heavy offsite replication, and data purging will negatively
impact the binary data transfer.
When will my backups run? Backup jobs are kicked off as soon as the metadata pull is complete.
After that, all scheduled backup jobs run per the configured schedule
time.
Will Barracuda contact me with an update once the binary data No. If you would like an update on the progress of the binary data
transfer has begun? transfer, contact the migrations team at BBSMigrations_team@barra
cuda.com. Make sure to include your device serial number and/or the
case number in the email.
Will my data be secure during the migration process? Yes. Data being transferred from the old/existing device to the
new/replacement device is on the customer LAN and presumably
behind the customer firewall. Data pulled down from the cloud to the
new/replacement device is transferred in its encrypted state until it
reaches the new/replacement device where it is then unencrypted.
Can I restore data during the migration? Yes. If transferring data from an old/existing Barracuda Backup
device, the migration process can be paused while recovery is
performed. If the data is being transferred from the cloud, once the
metadata pull is complete, a restore job can be initiated and the data
is recovered directly from the cloud.
Can I select the servers or backup sets that are migrated? No. The replacement/data migration process is all or nothing.

Contact Barracuda Networks Technical Support to complete your Barracuda Backup Replacement.
Set Up the New Appliance
Before you can replace a device and migrate the data, you must first install and link the new Barracuda Backup appliance. Refer to the Barracuda
Backup Quick Start Guide included with your appliance (also available as a PDF download from the Overview page), or use Step 1 and Step 2 in
the Getting Started section of this library. Once the device is linked, contact Barracuda Networks Technical Support or your sales engineer to
start the migration.
Understand the Migration Process
There are two steps to migrate data from an existing Barracuda Backup appliance to a new unit as detailed in Option 2 in the article Barracuda
Backup Replacement and Data Migration:
First, the Barracuda Networks migration engineer must copy the metadata and configuration from the original appliance to the new applia
nce, which typically takes less than 24 hours. Once this is complete, the new device functionally takes the place of the original device,
including backup jobs.
Second, the Barracuda Networks migration engineer must copy the actual data from the original appliance to the new appliance. This
takes place in the background and does not impact backup jobs. This process can take multiple days depending on the amount of data
being transferred as well as network speeds.
You can view migration progress on the System > Advanced Graphs page in the web interface.
Determine Migration Progress
Use the Disk Space graph to determine the amount of data awaiting migration. Log in to the new appliance web interface, go to the System >
Advanced Graphs page, and expand the Disk Space graph. Typically the remaining amount of data to be migrated can be determined using the
first two graphs.
For example, in Figure 1 there was roughly 6 TB of data on the original unit before the migration began on Monday afternoon, and at this point
the migration has transferred approximately 4.8 TB of data. Because backups have been running since the metadata and configuration were
copied to the new appliance, and data has been purged according to retention policies, the migration may finish with slightly more or less data,
but this graph provides a good estimate of the current migration progress.
Figure 1. Disk Space.

Use the Local Ethernet Traffic graph to determine the speed at which data is being transferred to the new appliance. Log in to the new
appliance web interface, go to the System > Advanced Graphs page, and expand the Local Ethernet Traffic graph. This provides a good
indication of the speed at which data is being transferred.
For example, in Figure 2, the Inbound traffic in green shows that the migration is running at around 20MB per second or 160Mb per second. The I
nbound traffic spikes represent backup jobs that are running at night, in this case starting around 10:30pm, but the constant 20MB per second
bandwidth usage is the box-to-box data transfer. At 20MB per second one can expect around 1.5 TB of data transfer per day. This is in line with
the increase shown in Figure 1, Disk Space.
Figure 2. Local Ethernet Traffic.
Note that these graphs show rough numbers but provide a good indication of migration progress and the amount of time remaining.
Once data transfer is complete, the Barracuda Networks migration engineer performs the final steps to complete the process. Once verification is
complete, you will receive a notification indicating the process is complete. At this point the Inbound Local Ethernet Traffic drops back to around 0
when backups are not running. If you have questions about your migration, contact Barracuda Networks Technical Support.

Barracuda Networks Technical Support

Before you replace your Barracuda Backup appliance, contact Barracuda Networks Technical Support to try to resolve the problem. For
additional information, refer to How Barracuda Networks Manages Returned Device Drives.
Troubleshooting
Use the articles in Troubleshooting and Error Messages to help resolve issues encountered on your system.
Instant Replacement Service
In the event that a Barracuda Backup appliance fails and you cannot resolve the issue, customers that have purchased the Instant Replacement
service can contact Barracuda Networks Technical Support to arrange for a new unit to be shipped out within 24 hours.
After receiving the new system, ship the old Barracuda Backup appliance back to Barracuda Networks at the address below with the Return
Material Authorization (RMA) number clearly marked on the package; Barracuda Customer Services can provide details on the best way to return
the unit:
Barracuda Networks
Attn Shipping/Receiving
5710 Fontanoso Way
San Jose, CA 95138
US
attn: RMA # <your RMA number>

How to Shut Down a Barracuda Backup Appliance
You can remotely reboot or shut down a Barracuda Backup appliance by logging in to its local web interface. Type the Barracuda Backup IP
address in a web browser, log in using your Barracuda Networks account, and go to the System > Device Information page:
You can also perform a safe shutdown of a Barracuda Backup appliance by pressing the POWER button on the front of the device. This issues a
shutdown command to all system and service processes before the device powers down.
Caution
Do not push the POWER button for more than a couple of seconds. Holding it for five seconds or longer causes an immediate hard
shutdown. This interrupts running processes and the Barracuda Backup appliance powers off before unmounting the file system.

How to Wipe a Barracuda Backup System
Wiping a Barracuda Backup Server unlinks it from your account and puts all data and configuration information into a queue to be purged from
Barracuda Cloud Storage. The wipe feature also deletes the contents of the local databases on the Barracuda Backup appliance, moves the
binary data on the Barracuda Backup appliance into a temporary storage location on the system, and then shuts it down. The next time the
Barracuda Backup appliance is booted, the binary data that has been moved is deleted.
Internet Access
In order for the wipe process to succeed, the Barracuda Backup appliance must first be connected to the Internet; verify the appliance
has internet connectivity before proceeding.
Use the following steps to wipe a Barracuda Backup Server to unlilnk it from your account:
1. Enter the Barracuda Backup IP address to log in to the local web interface.
2. Go to the System > Device Information page, and in the Server Actions section, click Wipe Barracuda Backup Appliance:
3. The message Wipe Started Successfully displays in the web interface; a warning message displays:
4. Click OK to complete the unlinking process. Once the Barracuda Backup appliance is unlinked from the account, the Backup Server
Wipe Successful page displays, including the Serial Number and Linking Code.
5. Make note of the serial number and linking code. You can now link the Barracuda Backup appliance to a new account. For details, see H
ow to Link a Barracuda Backup Product as a User or Reseller.

Barracuda Backup Panel Indicators, Ports, and Connectors
The illustrations in this article are based on current hardware models, however, models differ based on release date and may change in
the future. If your appliance connections differ from those shown in this article, refer to the Barracuda Backup Datasheet on the
Barracuda website, or contact Barracuda Technical Support for additional information.
Barracuda Backup Model 190, 290, 390, 490, and 690
The following figure illustrates the Barracuda Backup power and disk activity indicator lights for models 190, 290, 390, 490, and 690.
The following table describes the Barracuda Backup front panel power and disk activity indicator lights for models 190, 290, 390, 490, and 690.
Model 190, 290, 390, 490, and 690 Front Panel Component Description
Component Name Description
Power Button Push to power on the Barracuda Backup appliance, and tap to safely
reboot the appliance.
Reset Button Push for 5 seconds to reset the Barracuda Backup appliance.
Power Light Displays a solid blue light when the system is powered on.
Disk Light Displays a solid green light and blinks during disk activity.
The following figure illustrates the Barracuda Backup rear panel ports and connectors for model 190.
Model 190 Rear Panel
The following table describes the Barracuda Backup rear panel ports and connectors for model 190.
Model 190 Rear Panel Port and Connector Description
Port/Connector Name Details
Mouse Port Optional. Mouse port.
Keyboard Port Optional. PS2 keyboard connection.
VGA Port Recommended. Video graphics array (VGA) monitor connection.

USB Ports (2) Optional. USB device connection.
HDMI Port Optional. HDMI video connection.
Network Port Network connection.
Serial Port Optional. Serial device connection.
Power Supply Power supply input.
Power Supply Power supply input.
Network Port Network connection.
Power Supply(1) Power supply input.

Dual Link DVI-D Port Optional. Digital monitor connection.
Network Port Network port.
Note: (1)The C13 to C14 cable is standard for most rack setups as a power strip allows for the C14 connection. C13 to NEMA 5-15P is the
standard for direct connections to a UPS.
Power Supply Power supply input.(1)
Power Switch Power switch.
Dual Link DVI-D Port Optional. Digital monitor connection.
Network Port Network port.

Power Supply Power supply input.(1)
Power Switch Power switch.
IPMI Port Intelligent Platform Management Interface (IPMI) port for device
management over the network.
Network Ports (2) Network connection.
10 Gigabit Ethernet Card If your organization's environment does not support 10 Gigabit
throughput, the card reduces its speed to 1 Gigabit:
1 Gigabit Connection – Plug in a CAT5e cable for 1 Gigabit

throughput.
10 Gigabit Connection – Plug in a CAT6e cable and a 10 Gigabit
switch for 10 Gigabit throughput.
Barracuda Backup Models 790 through 995
The following figure illustrates the Barracuda Backup power and disk activity indicator lights for models 790 through 995.
The following table describes the Barracuda Backup front panel indicator lights for models 790 through 995.
Power Supply/Internal Fan Power supply and internal fan issue indicators:
Continuously on and red – An overheat condition has occurred;

this may be caused by cable congestion.
Blinking red (1Hz) – Fan failure, check for an inoperative fan.
Blinking red (0.25Hz) – Power failure; check for non-operational
power supply.
Solid blue – Local UID has been activated; use this function to
locate the server in a rack-mount environment.
Blining blue (300 mSEC) – Remote UID is on; initiate this
function from a remote location to identify the appliance.
Network Activity (2) Blinks green to indicate network activity.
Disk Light Displays a solid orange light and blinks during disk activity.
Power Light Displays a solid green light when the system is powered on.
The following figure illustrates the Barracuda Backup rear panel ports and connectors for models 790 and 890.

Models 790 and 890 Rear Panel
The following table describes the Barracuda Backup rear panel indicator lights for models 790 and 890.
Models 790 and 890 Rear Panel Port and Connector Description
Port/Connector Name Description
Power Supply (2) Redundant power supply input.(1)
Power Indicator Displays based on power supply health:

Lights
Solid green light – System is powered on and the power supply
is healthy
Solid orange/amber light – Power supply is degraded(2)
No light – System is not powered on or a power supply unit
(PSU) has failed
IPMI Port IPMI port for device management over the network.

throughput.
Notes:
(1)The C13 to C14 cable is standard for most rack setups as a power strip allows for the C14 connection. C13 to NEMA 5-15P is the standard
for direct connections to a UPS.
(2)Thepower supply may be degraded when, for example, one of the PSUs is not functioning. Push Reset; if this does not resolve the issue
you may need to replace a PSU.
Contact Barracuda Networks Technical Support for additional troubleshooting.
The following figure illustrates the Barracuda Backup rear panel ports and connectors for models 791 and 891.
Models 791 and 891 Rear Panel
The following table describes the Barracuda Backup rear panel indicator lights for models 791 and 891.

Model 791 and 891 Rear Panel Port and Connector Description
Power Indicator Lights Displays based on power supply health:

is healthy
(PSU) has failed

throughput.
10 Gigabit Fiber Card Optional. Use a small form-factor pluggable (SFP) transceiver
module:
SFP – Use SFP for 1/4 Gigabit/second throughput; you will need
a multi-mode cable with LC connections or a direct attach cable.
SFP+ – Use SFP+ for 10 Gigabit/second throughput (included);
you will need a multi-mode cable with LC connections or a direct
attach cable.
Vendor-Specific SFP – If you are using a vendor-specific module
in your environment, simply remove the Barracuda provided SFP
and replace with other vendor.
By default the top port is active.
If you want to bond the two ports for 20 gigabit throughput with
failover capabilities, Contact Barracuda Networks Technical Support.
Notes:
Barracuda Backup Models 895, 990, and 995
The following figure illustrates the Barracuda Backup rear panel ports and connectors for models 895A, 990, and 995A.
Models 895A, 990, and 995A Rear Panel

The following table describes the Barracuda Backup rear panel indicator lights for models 895A, 990, and 995A.
Model 895A, 990, and 995A Rear Panel Port and Connector Description

is healthy
(PSU) has failed

throughput.
Notes:
The following figure illustrates the Barracuda Backup rear panel ports and connectors for models 895B, 991, and 995B.
Models 895B, 991, and 995B Rear Panel

The following table describes the Barracuda Backup rear panel ports and connectors for models 895B, 991, and 995B.
Model 895B, 991, and 995B Rear Panel Port and Connector Description

is healthy
(PSU) has failed

throughput.
10 Gigabit Fiber Card Optional. Use a small form-factor pluggable (SFP) transceiver
module:
attach cable.

Notes:
The following figures illustrate the Barracuda Backup rear panel ports and connectors for models 990 and 991.
Barracuda Backup Models 1090 and 1091
The following figure illustrates the Barracuda Backup power and disk activity indicator lights for models 1090 and 1091.
The following table describes the front panel indicator lights for models 1090 and 1091.
Power Light Displays a solid green light when the system is powered on.
Disk Light Displays a solid orange light and blinks during disk activity.
Network Activity (2) Blinks green to indicate network activity.
Power Supply/Internal Fan Indicators Power supply and internal fan issue indicators:
Continuously on and red – An overheat condition has occurred;

this may be caused by cable congestion.
Blinking red (1Hz) – Fan failure, check for an inoperative fan.
Blinking red (0.25Hz) – Power failure; check for non-operational
power supply.
Solid blue – Local UID has been activated; use this function to
locate the server in a rack-mount environment.
Blining blue (300 mSEC) – Remote UID is on; initiate this
function from a remote location to identify the appliance.

The following table describes the Barracuda Backup rear panel indicator lights for model 1090.

is healthy
(PSU) has failed

throughput.
Notes:

The following table describes the Barracuda Backup rear panel indicator lights for model 1091.

is healthy
(PSU) has failed

throughput.
10 Gigabit Fiber Card Use a small form-factor pluggable (SFP) transceiver module:
attach cable.

Notes:

Barracuda Backup Hardware Specifications
The articles in this section refer to Barracuda Backup Legacy Release firmware or newer. Specifications subject to change without
notice.
MODEL 190 290 390 490 690 790 890 895 990 995 1090
COMPA
RISON
CAPACITY
Usable 1 TB 2 TB 4 TB 6 TB 12 TB 18 TB 24 TB 36 TB 48 TB 80 TB 112 TB
Storage
Capacit
y
Recom 500 GB 1 TB 2 TB 3 TB 6 TB 9 TB 12 TB 18 TB 24 TB 40 TB 56 TB
mended
Environ
ment
HARDWARE
Form Desktop 1U 1U Mini 1U 2U 3U 4U

Factor Micro
Weight 5 9 12 26 45 52 70 76 114 121

(lbs)
Network 1GB RJ45 2 x 10GB RJ45

Interfac
e
Optiona N/A 2-port SFP+

l 10Gb
Fiber
IPMI N/A YES
Disk 1 x 1 TB 1 x 2 TB 2 x 4 TB 4 x 4 TB 4 x 6 TB 6 x 6 TB 8 x 6 TB 10 x 6 16 x 4 14 x 8 32 x 4
Arrange TB TB TB TB
ment
Redund N/A SW SW HW RAID 10 HW RAID 60

ant Disk RAID 1 RAID 10
Array
(RAID)
Dedicat N/A 2 x 2 TB 4 x 2 TB
ed
Databas
e and
OS
Disks
Redund N/A HW HW
ant Disk RAID 1 RAID 10
Array
(OS)
Swappa N/A Hot Swappable

ble
Disks
Redund N/A Hot Swappable

ant
Power
Supplie
s

AC 0.25 0.40 0.65 1.3 1.7 2.5 2.6 6.9 7.8 8.4
Input
Current
(amps
@ 120V)
FEATURES
Manage Barracuda Cloud Control centralized management

ment
Interfac
e
Barracu Windows File System & System State, Microsoft Applications (Exchange, SQL, and SharePoint), Linux
da
Backup
Agent
Network NAS, Unix, Linux, Mac OS X

Backup
s
Include
d
Virtual Host level: VMware vSphere, Microsoft Hyper-V Guest level: Citrix XenServer, Oracle VM, Red Hat Enterprise Virtualization,
Environ KVM
ments
SaaS Microsoft Office 365 including Exchange Online, OneDrive for Business, and SharePoint Online
Environ
ments
Dedupli Global, Inline, Block-Level, Source- and Target-Based

cation
Physica • • • • • • • • • • •
l-to-Virt
ual
(P2V)
Recove
ry
Export • • • • • • • • • • •
to
External
Media
Offsite • • • • • • • • • • •
Vaulting
Local • • • • • • • • • • •
and
Cloud
LiveBo
ot
Cloud • • • • • • • • • • •
Replicat
ion
Site-to- Sender Sender and Receiver

Site
Replicat
ion
SFP+ Fiber 10GbE: 791, 891, 895b, 991, 995b, 1091
10 Gigabit Ethernet Card Standard
Models 690/790/890/895/990/995a/1090 include a 10 Gigabit Ethernet card. If your organization's environment does not support 10 Gigabit

1 Gigabit Connection – Plug in a CAT5e cable for 1 Gigabit throughput.

10 Gigabit Connection – Plug in a CAT6e cable and a 10 Gigabit switch for 10 Gigabit throughput.
10 Gigabit Fiber Card Option
Use a small form-factor pluggable (SFP) transceiver module:
SFP – Use SFP for 1/4 Gigabit/second throughput; you will need a multi-mode cable with LC connections or a direct attach cable.
SFP+ – Use SFP+ for 10 gigabit/second throughput (included); you will need a multi-mode cable with LC connections or a direct attach
cable.
Vendor-Specific SFP – If you are using a vendor-specific module in your environment, simply remove the Barracuda provided SFP and
replace with other vendor.
By default the top port is active. Contact Barracuda Networks Technical Support if you want to bond the two ports for 20 Gigabit throughput with
failover capabilities.
Model 790 Drive Layout
Models 995 and 1090 Drive Layout


How to Physically Install the Barracuda Backup Appliance
For rack mounting installation instructions by model, see Rack Installation of Barracuda Appliances.

Barracuda Backup Network Interface Bonding
This article refers to the Barracuda Backup Legacy Release firmware or newer running on Barracuda Backup Server models 690
and above.
Bonding is the creation of a single bonded interface by combining two or more Ethernet interfaces. This helps in network interface high availability
(ha) and offers performance improvement. Bonding is the same as port trunking or teaming.
By default, the second onboard 1 x Gb network interface on the 690 and 890 models, and the 1 x 10Gb network interface on the 990 and 1090
models, is disabled and denoted by a plastic RJ45 connector plugged into the interface. However, the two network interfaces can be bonded for
20 Gigabit throughput with failover capabilities. A typical use is to add a separate VLAN to be backed up or a designated replication interface. Co
ntact Barracuda Networks Technical Support if you want to bond the two network interfaces; Barracuda Networks Technical Support can also
bond the optional 10GbE fiber cards included on Barracuda Backup Server models 891, 991, and 1091.
Link Aggregation (LAG) allows you to bond two or more ports in parallel to achieve greater throughput. LAG has the following
properties:
LAG provides automatic recovery when individual physical links fail. As long as at least one physical link exists, the LAG connection
continues to exist.
Data transmission is distributed as frames over the physical links.
All frames forming part of a specific data communication packet are transmitted over the same physical connection, ensuring delivery of
the individual frames of a data communication packet in the correct order, preventing disordering.
Barracuda Networks uses Mode 4 (802.3ad) bonding, known as Dynamic Link Aggregation mode. This
mode creates aggregation
groups that share the same speed and duplex settings, and requires a switch that supports IEEE 802.3ad
Dynamic link.

Barracuda Backup Data Transfer IP Ranges
While it is not recommended practice, some networks may require that you lock down IP addresses/ranges per service. The following sections list
the IP addresses used by the Barracuda Backup appliance. Firewall modifications must be made for outbound traffic only. The Barracuda Backup
appliance does not require that you open any inbound ports since the appliance initiates the connection to our cloud.
The IP address ranges in the following table are subject to change without notice. If this occurs, the Barracuda Backup appliance stops
seeding data to the cloud.
Open Outbound Ports: 80, 443 (TCP)
216.129.105.129/32
205.158.110.60/32
204.156.124.128/32
212.118.243.148/32
204.14.15.41/32
206.180.126.10/32
209.18.50.242/32
69.7.235.214/32
216.162.80.57/32
Open Outbound Ports: 1194 (TCP/UDP), 5120-5129 (TCP/UDP), 80, 443
USA
64.235.144.0/20
209.124.61.96/27
209.222.80.0/21
Canada
64.235.144.0/20
204.156.124.0/22
EMEA United Kingdom
64.235.144.0/20
64.235.158.0/24
EMEA Germany
64.235.144.0/20
95.172.71.0/28
95.172.75.0/24
APAC Australia
64.235.144.0/20
175.45.106.0/24
Japan
64.235.144.0/20
203.191.241.128/27
203.191.241.143/32

Understanding the Barracuda Backup Service Data Plan
If you have any questions or concerns regarding your Barracuda Backup Service plan, contact Barracuda Networks Technical
Support.
Barracuda Backup Service data plans are billed based on the total amount of data currently backed up offsite at the compressed and
deduplicated rate. When the storage limit is reached, the plan is automatically increased to meet the data requirements and billed at the new
level. A notification is sent to all users designated to receive Offsite Backup Over-Usage notifications once the storage limit is reached.
To designate a user to receive these notifications, log in to the Barracuda Backup web interface, click Account > Manage Users, and then click
on the user name. In the right panel, in the Privileges section, turn on Billing Administration:
You have several options to address data plan overage, including:
Select less data to be backed up.

Modify your retention policies; modifying a retention policy timeline purges historic file revisions, freeing up storage space. For more
information, refer to Understanding Retention Policies and Creating Effective Retention Policies.
Upgrade to a larger data plan. The larger plan is less expensive than paying for the current plan plus overage charges. Refer to the
Barracuda Knowledgebase Solution #00003985 for details on sizing your data plan, or contact your Barracuda Networks Sales Associate
for details.
Select data to be backed up locally only. This removes the data from the off site location, reducing offsite data plan usage.

See also: Supported Data Sources by Version
Important
Barracuda makes every effort to test and qualify all hardware platforms and software including operating systems, service packs, and
other applications, however, not every combination can be fully tested. However, due to the infinite number of combinations, it is not
possible to test every configuration for compatibility. If a specific hardware platform, operating system, browser, service pack, or other
application version is not listed as supported, then it has not been explicitly tested and may not be supported even though it may work.
Browser Support
The Barracuda Backup web interface is compatible with the following browsers:
Internet Explorer 11.0 and higher

Mozilla Firefox 24 extended browser support (ESR) and higher
Google Chrome 30 and higher
Opera Browser 11.0 and higher
Agent Software Requirements
Microsoft .Net Framework 3.5 is required for Barracuda Backup Agent installation.
Barracuda Backup Agent (Windows) 6.0 and higher supports the following Microsoft Windows systems:
Windows Server 2016

Windows Server 2014
Windows Server 2012 and 2012 R2
Windows Server 2008 and 2008 R2
Windows 10
Windows 8
Windows 7
Windows Vista SP1 or higher
Barracuda Backup Agent (Linux) 6.0 and higher supports:
If your Linux system is running a version prior to Kernel 2.6.16, Barracuda recommends using SSHFS for backup.

Supported Agent Applications
Barracuda Backup supports all of the latest service packs for Agent applications.
Microsoft Hyper-V
Hyper-V 2016
Hyper-V 2012 R2
Hyper-V 2012
Hyper-V 2008 R2
Hyper-V 2008
Microsoft Exchange
Exchange 2016
Exchange 2013
Exchange 2010

SQL Server 2016

SQL Server 2014
SQL Server 2012
SQL Server 2008
SQL Server 2005
VMware Support
vSphere ESXi 6.5

vSphere ESXi 6.0
vSphere ESXi 5.5
vSphere ESXi 5.1
vSphere ESXi 4.1
vSphere ESXi 4.0
Cloud LiveBoot for VMware Operating System Compatibility (Windows)
Install virtio drivers whenever possible. There is a maximum of four disks per LiveBoot instance.
If an independent disk is associated with a virtual machine, the virtual machine is backed up but the disk is excluded. Install the
Barracuda Agent to capture the disk data.
Windows Server 2012 R2 64-bit

Windows Server 2012 64-bit
Windows Server 2008 R2 64-bit
Windows Server 2008 32- and 64-bit
Windows 10 32- and 64-bit
Windows 8.1 64-bit
Windows 8 64-bit
Windows 7 32- and 64-bit
Windows Vista 32- and 64-bit
Cloud LiveBoot for VMware Operating System Compatibility (Linux/Unix)
Install virtio drivers whenever possible. There is a maximum of four disks per LiveBoot instance.
If an independent disk is associated with a virtual machine, the virtual machine is backed up but the disk is excluded. Install the
Barracuda Agent to capture the disk data.
CentOS 5.5 32- and 64-bit

Fedora 5 and higher 32- and 64-bit
Red Hat Enterprise Linux 3 and higher 32- and 64-bit
Debian 5 and higher 32-bit
Ubuntu 8.04 and higher 32- and 64-bit
Knoppix 5.1.1 and higher 32-bit
SUSE Linux Enterprise Server 10 and higher 32- and 64-bit
openSUSE 11.0 and higher 32- and 64-bit
OpenBSD 4.0 and higher 32- and 64-bit (with e1000 network driver)
FreeBSD 7.2 and higher 64-bit (with e1000 network driver)
FreeBSD 7.4 and higher 32-bit (e1000 network driver)
Local LiveBoot Operating System Compatibility
See VMware Guest Operating System Installation Guide for a complete list of supported LiveBoot guest operating systems
LiveBrowse Virtual Disk Formats (VMware & Hyper-V)
VHD/VHDX Fixed
VHD/VHDX Dynamic
VMDK Thin
VMDK zeroedthick
VMDK eagerzeroedthick

LiveBrowse Partition/Volume Structure Support (VMware & Hyper-V)
Master Boot Record (MBR) Disks

Linux Logical Volume Manager (LVM), single disk/volume only
GUID Partition Table (GPT)
LiveBrowse Supported File Systems (VMware & Hyper-V)
NT File System (NTFS)

FAT File System
FAT32 File System
Second Extended Filesystem (ext2)
Third Extended Filesystem (ext3)
Fourth Extended Filesystem (ext4)
XFS File System
Btrfs File System
ReiserFS File System
LiveBrowse Supported Windows Volumes (VMware & Hyper-V)
Supported:
Simple
Unsupported:
Spanned
Striped
Mirrored
RAID 5 volumes
Linux Supported Backup Methods

SSHFS
NFS Mounts
Oracle Database on Linux Using RMAN and Barracuda Backup
Mac OS X Supported Backup Methods
SSHFS
Hardware and Connectivity Requirements
Verify you have the following before setting up your Barracuda Backup appliance:
Barracuda Backup Appliance and AC power cable (shipped with the appliance)
Barracuda Backup serial number and linking code (included on the Barracuda Backup Quick Start guide shipped with the appliance)
Connectivity and access information for servers to back up
VGA Monitor and USB or PST/2 keyboard (recommended/customer supplied)
19-inch rack or stable location in which to place the appliance
*Cabling differs based on the appliance model. For more information, refer to the Barracuda Backup Hardware Specifications.
Source Configuration


How to Open a Support Tunnel
This article refers to Barracuda Backup version 6.2 or higher.
See also: How to Open a Support Case in Barracuda Cloud Control
When Barracuda Technical Support needs to troubleshoot a Barracuda Backup appliance linked through Cloud Control, the technician uses the
VPN tunnel between the appliance and the Barracuda Cloud Servers. However, there are some conditions where the VPN tunnel is prevented
from connecting. For example, if a Barracuda Backup appliance is linked through Local Control, a support tunnel must be manually opened for
remote diagnostics and technical support services over TCP port 22 outbound in contrast with the default VPN connection over port 1194.
Open a Support Tunnel Using the Console
You can use the Console screen to open a support tunnel.
To access and interact with the Console screen, you need a VGA Monitor and USB or PS/2 keyboard.
Use the following steps to open a Support Tunnel using the Console:
1. Connect the VGA monitor and keyboard to the Barracuda Backup appliance.
2. Use the keyboard arrows to highlight Troubleshooting, and press either Enter or the right arrow key on your keyboard to move the
cursor to the Troubleshooting menu:
3. Use the arrow keys on your keyboard to move the cursor to Enable Tunnel in the Remote Support section:

4. Press Enter to open a support tunnel. Verify the support tunnel is open:
5. Once troubleshooting is complete, repeat steps 1-4 to Disable the support tunnel.
Open a Support Tunnel from Local Control
The steps in this section apply to both Cloud and Local Control Barracuda Backup appliances; a version of the Local Control interface
is available on both.
Use the following steps to log in to the local interface and open a support tunnel for remote diagnostics and technical support services over TCP
port 22 outbound:
1. In a browser window, enter the Barracuda Backup appliance IP address.

2. Log in using your Barracuda Cloud Control credentials.
3. Go to the System > Device Information page, and in the Server Actions section, click Open Support Tunnel:

3.
4. The button changes to Close Support Tunnel, and a message displays indicating that the tunnel is open.
5. Once troubleshooting is complete, click Close Support Tunnel.

Troubleshooting and Error Messages
In this Section
Understanding Why the Barracuda Backup Agent Moves to a New Volume

Understanding Why Data is not Replicating to an Offsite Barracuda Backup Location
How to Resolve Low Disk Space
How to Change the Barracuda Backup Agent Port Number
How to Resolve "Agent database moved to different location" Warning
How to Resolve "Error Creating Snapshot" Error During ESX/ESXi Virtual Machine Backup
How to Resolve "Error Reading Object" Error During ESX or ESXi Virtual Machine Backup
How to Resolve "Error Removing Snapshot" Error During ESX/ESXi Virtual Machine Backup
How to Resolve "Failed to connect to backup agent software" Error
How to Resolve "Incremental backups cannot be performed while circular logging is enabled" Error
How to Resolve "An error occurred during agent backup initialization" Error
How to Resolve "Unable to back up virtual machines with independent disks" Error
How to Resolve "VMDK is larger than the maximum size supported by datastore" Error
How to Resolve "Error backing up selected object" Error
How to Increase Backup Performance
How to Move the VSS Snapshot Location
Understanding "Unable to Quiesce Disk" Warning During ESX/ESXi Virtual Machine Backup
How to Resolve "A Volume (drive) that was previously backed up is no longer there and being backed up" Warning
How to Resolve "An error occurred during agent backup initialization" Error - Event ID 8193 - Diff Area
How to Resolve "File System Snapshot released, this backup is invalid" Error
How to Resolve "Error opening object"
Resolve the "Failure while using USN journal" Error
Resolve the "EWS connection error" for Specific Users in Message-Level Backup
Understanding Why VMware Virtual Machine Returns Incorrect Changed Sectors
Related Articles


The Barracuda Backup Agent requires at least 1GB of free disk space on a data source for its database. If less than the required amount of disk
space is available, the Barracuda Agent database is automatically moved to another storage volume. While backups will continue to run, a
warning message displays in the Barracuda Backup web interface notifying you that the database has been moved:
To resolve this issue, install the Barracuda Backup Agent to an alternate storage volume with adequate free disk space.
Updating the Backup Agent Location
Use the following steps to move the Barracuda Backup Agent to an alternate storage volume and eliminate the warning message:
1. Completely uninstall the Barracuda Backup Agent using the Add/Remove Programs or Programs and Features option on your
system.
2. Once the Agent is uninstalled, log in to the Barracuda Backup web interface, and go to the System > Software Downloads page.
3. Download and install the latest version of the Barracuda Backup Agent.
4. During installation, select the installation path on a storage volume with at least 1GB of free disk space.
5. Once the next successful backup occurs, the warning message no longer displays.

Understanding Why Data is not Replicating to an Offsite Barracuda Backup

Location
The Barracuda Backup default rate limit controls the rate of data replicated to offsite storage locations throughout the day; preserving Internet
bandwidth during peak usage and optimizing offsite backup transfers during daily non-peak hours. You can further refine the rate limit by enabling
an alternate rate limit and specifying a specific time period to which it applies.
However, if a large backup is scheduled during the alternate rate limit time interval, replication to the offsite location may not complete within the
specified time period. In this case, the yellow status indicator ( ) icon displays in the Replication Health field on the Dashboard page
indicating there is a problem with the offsite syncing queue.
Resolve Data Replication Issue
To resolve this issue, you can:
Increase the speed limit

Reduce the amount of replicated data
Decrease the backup schedule frequency
Increase Speed Limit
Use the following steps to increase the speed limit to ensure data replication finishes within the specified timeframe:
1. Log in to Barracuda Backup, and go to Backup > Rate Limit page.

2. Turn on Alternate Rate Limit, and update the bandwidth based on the selected option:
Full Speed – Uses 100% of available bandwidth
Smart Mode – Increase the Percent of Bandwidth value
Kb/s or Mb/s – Specify a higher value
3. Click Save at the top of the page to save your changes.
Reduce Amount of Data for Replication
Use the following steps to select less data for replication:
1. Log in to Barracuda Backup, and go to Backup > Sources.

2. On the Data Sources page, locate the data source on the system you wish to modify, and click Edit to the right of the data source.
3. In the Edit page, in the Item Selection section, review the selected items. Determine if there are items that do not need backup, and
deselect those items.
Decrease Backup Schedule Frequency
1. Log in to Barracuda Backup, and go to Backup > Schedule.

2. Click the Edit ( ) icon to the right of the schedule associated with the backup.
3. In the Edit Backup Schedule page, if Repeat is turned on in the Daily Backup Timeline section, reduce the minute or hour frequency.
View Offsite Transfer Statistics
To view transfer statistics, log in to Barracuda Backup, and go to Backup > Replication The following queue details display:
Status – Displays either the green indicator ( ) icon or the red indicator ( ) icon
Total Stored – Total size of file parts transferred offsite from the Barracuda Backup appliance
Queue Age – Amount of time that the queued data has been waiting to be transferred offsite from the Barracuda Backup appliance
Queue Size – Total size of the file parts yet to be transferred offsite from the Barracuda Backup appliance

This article refers to the Barracuda Backup Legacy Release firmware or newer, and the Barracuda Backup Agent (Windows).
Use the Backup Agent bbtrace.txt log files to understand and resolve any errors that may occur with the Backup Agent such as an initialization
error. Each time the Backup Agent Service is restarted, a number is appended to the current bbtrace.txt file, and a new file is generated.
To review the log file:

1. Log in to the data source that is failing to back up data, and go to the Backup Agent log files. By default, the log files are located in:
C:\Program Files\Barracuda\Barracuda Backup Agent\log
2. Locate the file bbtrace.txt; this is the most recent log file.
If the server was rebooted, or the agent was restarted, you may need to review older bbtrace.txt files to find the time listed in
the Report details page in the previous step.
3. Open bbtrace.txt in Notepad. This file contains data that is helpful in determining the specific error. Each log entry is time stamped, so
you will first want to identify when the failed backup occurred based on the Report details page; note that there may be multiple days of
log details so it is recommended that you use the search function to find the error.
4. Search the log file for terms such as Failed or Critical. Once you locate the term, review the associated content to determine the specific
error message:
In this example, a VSS snapshot failed due to an unexpected operating system error on the targeted server.
Note that an Agent error message is typically followed by associated CRITICAL Sup: Resource not put details which is
not needed for troubleshooting.
5. With most errors located in bbtrace.txt there are generally errors or warnings located within Application/System Event logs. Barracuda
recommends taking the timestamp within bbtrace.txt, for example, 05/22/13 02:09:55, and looking at the event logs based on that
timestamp.

How to Resolve Low Disk Space
If the Barracuda Backup appliance drives run out of space, backups cannot complete and will fail. A low disk space notification is sent when
the Barracuda Backup appliance reaches 80% capacity and above. Following are several options to combat this issue:
Review Retention Policies
Verify a retention policy is applied to all data sources. If a source does not have a retention policy applied to it, all data from that source is
retained forever.
For example, if you initially back up 100GB of data and 5GB of changed data daily, after 30 days with no retention policy you will have a
total of 250GB for the source.
Go to the Backup > Retention Policies page in the web interface and verify that each source has a retention policy applied to it.
Additionally, you can contact Barracuda Networks Technical Support and request verification that each data source on the Barracuda
Backup appliance has a policy applied.
Remove Large Files
Determine which data sources are backing up the largest files – see How to Generate a Large Items Report for more information.
Go to Reports > Large Items to review which sources are backing up the largest files. You can then determine if these files need to be
backed up and exclude them, or lower the retention policy applied to the source.
Review Large Servers
Determine which servers are using the most space.
Contact Barracuda Networks Technical Support and request to have a usage report generated for your Barracuda Backup appliance.
This report displays the amount of space used by each backup data source. Additionally, this report shows which server is retaining the
most historic data kept per the retention policy.
Modify your retention policies by source basis to manage disk usage.
Enable Offsite Vaulting
Determine if replicating data offsite would be of beneficial to your organization – see Understanding Barracuda Offsite Vaulting for more
information.
Offsite vaulting leverages Barracuda's replication technology to offload up to twelve monthly and seven yearly revisions to an offsite
location, freeing up disk space on your local Barracuda Backup appliance. This feature maintains your organization's compliance with
long retention policies, allowing you to save more daily and weekly revisions. Note that offsite vaulting is available for both Barracuda
Cloud and site-to-site replication. Offsite vaulting can be used for 12 monthly and 7 yearly historical revisions; these revisions are
retained at the end of each calendar month and year.
If you determine that all of the above suggestions are in place and all settings are correct, and you are continuing to run low on space, it may be
time to look at upgrading to the next model with increased disk capacity.
If you are unable to determine what is causing your server to run low on space, contact Barracuda Networks Technical Support and a
technician can assist with troubleshooting.

This article describes how to resolve the service start error 112.
Issue
You encounter the following error when installing the Barracuda Backup Agent on a server or workstation in your environment:
Barracuda Backup Agent setup received error "112 Service Error" while attempting to start service.
Cause
You may be running software that uses port 5120 on the selected system which is causing a conflict and generating the error.
Solution
If port 5120 is in use by another piece of software on your data source, Barracuda Networks recommends configuring the Barracuda Backup
Agent to use port 5121.
Step 1. Determine the Ports Used by the System
Use the following steps to configure the port:
1. Log in to the system where you received the error, and launch a web browser.
2. Go to the downloads page on the Microsoft TechNet site, and download and install TCPView.
3. Launch TCPView; the ports that the system is currently using display in the web interface.
4. Review the list. If you see that port 5120 is in use, change the port number in the config.ini file as described in step 2.
Step 2. Add the Alternate Port Number config.ini
Use the following steps to change the port number through the config.ini file:
1. On the system where you received the error, locate the config.ini file, usually found in the C:\Program Files\Barracuda\Barracuda
Backup Agent\config folder.
2. Open config.ini in a text editor such as Notepad, and add the line port='port number' beneath the [configuration] options.
For example:
[configuration]
nodeGuide={XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX}
port=5121
Step 3. Restart Services
1. Log in to the system again.

2. Restart the Barracuda Backup Agent service.
Step 4. Update Data source
1. Log in to Barracuda Backup, select the associated Barracuda Backup Server in the left pane, and go to the Backup > Sources page.
2. In the right pane, click Edit to the right of the system where the error occurred.
3. In the Computer Name field, append the IP address with the port number added in Step 2 above.
For example, if your IP address is '192.168.0.1', and you added the line 'port=5121' to the config.ini file, update the Computer Name fiel

d as follows:

This article refers to the Barracuda Backup Legacy Release firmware or newer, and the Barracuda Backup Agent (Linux).
By default the Barracuda Backup Agent (Linux) utilizes port 5120 to communicate with the Barracuda Backup Server. If there is a port conflict
with another service, assign the Linux Agent a different port.
Assign a New Port
1. Locate the config.ini file in the default file location: /usr/local/barracuda/bbs/config/config.ini

2. To view the file, type the following command: cat /usr/local/barracuda/bbs/config/config.ini
3. The file content displays:
[installControl]
installedVersion=6.3.04-rel
buildNumber=200513
[configuration]
nodeGuid={00001001-5476F68E-5476F68E-5476F68F}
4. Open the file with a text editor such as vi or vim, for example: vim /usr/local/barracuda/bbs/config/config.ini
5. Add the following line to the end of the config.ini file: Port=5555
Where 5555 represents the port number you want to assign the Agent.
6. View the file, it should look similar to:
[installControl]
buildNumber=200513
[configuration]
Port=5555
Restart the Agent
Enter the following command to restart the Linux Agent:
/etc/init.d/bbagent start
Edit the Data Source
1. Log in to the Barracuda Backup web interface, and go to the Backup > Sources page.
2. Click Edit next to the data source, and configure the new port that the Linux Agent is to use, for example:

This article refers to Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server 2005, 2008, 2008 R2, and
2012.
The Barracuda Backup appliance is designed to initially complete a full backup of the SQL Server database(s). Once the initial full backup is
complete, the Barracuda Backup Server can attempt to complete an incremental backup of the SQL Server database. In order for the Barracuda
Backup Server to successfully complete an incremental backup, the SQL Server database(s) must be set to Full Recovery Model. Typically, SQL
Server databases are set to Simple Recovery Model by default.
Warning Message
If an incremental backup cannot be completed, the Barracuda Backup Server reverts to a full backup and a warning message displays:
Simple Recovery Model

If you want to leave the SQL Recovery Model set to Simple Recovery Model, log into the Barracuda Backup web interface, and go to
the Backup > Schedules page. On the Schedules page, Click the Edit icon for the associated backup schedule. On the Schedules p
age, in the SQL/Exchange Backup section, select Complete from the Backup type drop-down menu. Click Save at the top of the
page to save your changes.
The recovery model controls how transaction logs are managed. Before changing the Recovery Model, consult your database administrator to
determine the setting that is appropriate for your environment.
Set the SQL Recovery Model
All SQL databases need to be set to Full Recovery Model in order to produce Incremental backups. Otherwise, Full backups are performed on
every run.
Use the following steps to set the Recovery Model on your SQL databases to Full:
1. Connect to the appropriate instance of the Microsoft SQL Server Database Engine.
2. In Object Explorer, click the server name to expand the server tree.
database.
4. Right-click the database, and then click Properties; the Database Properties dialog box displays.
5. In the Select a Page pane, click Options.
6. The current recovery model displays in the Recovery Model list. Select Full from the list, and click OK to save your changes.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft SQL Server.
Typically, this warning occurs when a user chooses to enter credentials for the Microsoft SQL Server connection and those credentials
are for a Windows account, and not a Microsoft SQL Server account. When the Agent is configured to perform a VDI backup of the
Microsoft SQL Server databases, the entered credentials must be those of a SQL account, not a Windows account. To verify this error,
open the Application Event Logs on the Microsoft SQL Server, and look for Event ID 18456 at the time of the backup. This event
indicates there was a failed login using a Windows account.
By default, the Barracuda Backup Agent uses the Local System (NT Authority\System) account to connect to Microsoft SQL Server. If you enter
Microsoft SQL Server credentials when setting up the data source, the Agent attempts to use those first:
If the credentials entered during setup fail, the Barracuda Agent defaults to the Local System account credentials to allow for successful database
backup, and displays the warning message “Error with SQL authentication”:
To clear this warning, remove the credentials entered during data source setup:
1. Log in to Barracuda Backup, and go to the Backup > Sources page.

2. Click Edit to the right of the Microsoft SQL Server data source to edit the share settings, and scroll down to the authentication section:
3. Clear the Microsoft SQL Server Requires Authentication option:
The Barracuda Agent uses the Local System account credentials for all future database backups.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010 successfully
running message-level backups.
Error Message
If you attempt to restore large messages from Microsoft Exchange 2010, you may encounter a Max EWS Request error:
Modify web.config
Use the following steps to resolve a failed restore:
1. Log into your Microsoft Exchange 2010 Server as the administrator, and navigate to the Program Files > Microsoft > Exchange
Server > V14 > Client Access > exchweb > ews folder, and create a copy of the file web.config:
Creating a copy of the web.config file allows you to revert to your original settings in case you encounter issues during
resolution of the restore error.
2. Open the original web.config file using Notepad running as the administrator.
3. In Notepad, go to Edit > Find, and enter max in the find what field:

3.
4. Click Find Next until you locate the following line of code:
<httpsTransport maxReceivedMessageSize="13600000" authenticationScheme="Anonymous"
maxBufferSize="81920" transferMode="Streamed" />
5. The value maxReceivedMessageSize="13600000" represents a maximum attachment size of 13MB. Therefore, any attachments
over 13MB cannot be restored. Change this value to a larger value to handle the largest attachment failing to restore, for
example, replace 13600000 with 53600000 which allows for attachments just over 50MB:
6. Click Find Next until you locate the following line of code:
<httpsTransport maxReceivedMessageSize="13600000" authenticationScheme="Anonymous"
maxBufferSize="81920" transferMode="Streamed" />
7. Replace 13600000 with the same value you entered in step 5 above, for example, 53600000 .
8. Click Find Next once again until you locate the following line of code:
<requestLimits maxAllowedContentLength="13600000" />
9. Replace 13600000 with the same value you entered in step 5 above, for example, 53600000 .
Click File > Save, and close Notepad.
Run appcmd
1. Log into your Microsoft Exchange 2010 Server, and at a command prompt, change the directory to the inetsrv folder:
cd c:\windows\system32\inetsrv
2. At a command prompt, run the appcmd command using the new size limit value you entered in the previous section:
appcmd set config "Default Web Site/ews" -section:requestFiltering
-requestLimits.maxAllowedContentLength:53600000

3. Close the command prompt.

4. Open Services and restart the following services:
Restart IIS Admin Service:
Restart Microsoft Exchange Transport:

Barracuda Backup Restore
1. Log in to your Barracuda Backup web interface, and restore the messages that originally failed.
2. Messages should now restore without any errors. However, if you continue to encounter errors when restoring large messages, continue
to the next section, Configuration Settings.
Configuration Settings
Microsoft Exchange 2010 Configuration Settings

Use the steps in the following sections only if you continue to encounter errors when restoring large messages.
Verify Exchange Management Console Settings
1. Log in to your Microsoft Exchange 2010 Server, and open the Exchange Management Console (EMC).
2. Expand Organization Configuration, click Hub Transport, and click the Global Settings tab:

3. Right-click Transport Settings, and click Properties:
4. Verify the Transport Limits settings are large enough and listed correctly, then click OK.
5. In the EMC, expand Server Configuration, click Hub Transport:

5.
6. Right-click on the Client Receive Connector, and click Properties:
7. Verify the value in the Maximum message size (KB) is large enough to accommodate message restore.
8. Right-click the Default Receive Connector, click Properties, and verify the Maximum message size (KB) is large enough to
accommodate message restore.
9. If you modified any settings in the preceding steps, go to Services and restart both IIS Admin Service and Microsoft Exchange
Transport services.

Exchange Management Shell
1. Open the Exchange Management Shell, and enter the following command:
get-tranportconfig:
2. Verify that the following settings are large enough and listed correctly:
ExternalDsnMaxMessageAttachSize
InternalDsnMaxMessageAttachSize
MaxReceiveSize
MaxRecipientEnvelopeLimit (shown in KB)
MaxSendSize
3. If any of the values need modification, run the following command:
Set-transportconfig -<setting to be changed> <size>
For example:
set-transportconfig -MaxSendSize 50MB
4. If you modified any values through the Exchange Management Shell, go to Services and restart both IIS Admin Service and Microsoft
Exchange Transport services.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Windows Vista, Windows 7, and
Windows 2008.
If you receive a File System Snapshot was Released reporting error, a partition may be heavily used or fragmented. Use the steps in this article
to determine the issue and to resolve the error.
Move the Snapshot Location
First determine if the server has multiple partitions with available disk space, and then move the snapshot location to a less used disk using
the following steps:
1. Log in to the server as the administrator, go to My Computer, and right-click on the troubled partition.
2. Select Properties, and click the Shadow Copies tab:
3. In the Select a volume list, click on the troubled partition, and click Settings:

4. In the Settings dialog box, from the Located on this volume drop-down menu select a partition with available space, and then click OK.
Verify the maximum size is adequate to back up the partition.
Defragmentation
Analyze the partition in question for a Defrag. The disk will show up heavily fragmented:
It is recommended that you defragment the hard drive during off hours in order to reduce server load during normal business hours.

The Barracuda Backup Agent requires at least 1GB of free disk space on a data source for its database. If less than the required amount of disk
space is available, the Barracuda Agent database is automatically moved to another storage volume.
While backups will continue to run, a warning message displays in the Barracuda Backup web interface stating that the database has been
moved:
To resolve this issue, install the Barracuda Backup Agent to an alternate storage volume with adequate free disk space.
Update the Backup Agent Location
Use the following steps to move the Barracuda Backup Agent to an alternate storage volume and eliminate the warning message:
1. Completely uninstall the Barracuda Backup Agent using the Add/Remove Programs or Programs and Features option on your
system.
2. Once the Agent is uninstalled, log in to the Barracuda Backup web interface, and go to the System > Software Downloads page.
3. Download and install the latest version of the Barracuda Backup Agent.
4. During installation, select the installation path on a storage volume with at least 1GB of free disk space.
5. Once the next successful backup occurs, the warning message no longer displays.

How to Resolve "Error Creating Snapshot" Error During ESX/ESXi Virtual

Machine Backup
This article refers to the Barracuda Backup Legacy Release firmware or newer, and VMware with the VMware license which
includes access to vSphere Data Recovery API.
This article describes how to resolve the error "Error creating snapshot" encountered while backing up an ESX/ESXi virtual machine, as shown in
the following image:
The most common causes for this error are the size of the snapshot being created is larger than the available free space on the datastore, or a
vss writer error.
For more information, refer to the following VMware knowledgebase articles:
VMware Data Recovery backup fails with the error: Failed to create snapshot. Error -3941 (1028924)
Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for
holding off I/O in the frozen virtual machine (1018194)

How to Resolve "Error Reading Object" Error During ESX or ESXi Virtual
Machine Backup
This article refers to the Barracuda Backup Legacy Release firmware or newer, and VMware® 4.1 and above with the VMware licen
se which includes access to vSphere® Data Recovery API.
This article describes how to resolve the error "Error reading object" encountered while backing up an ESX/ESXi virtual machine. The most
common causes for this error are a crashed virtual machine or missing blocks on the virtual machine.
When an error is encountered when backup up the disk, the following displays in the vSphere logs:
Error QueryChangedDiskAreas
If you receive this error:
Use the following steps to resolve this error:
1. Remove all virtual machine snapshots.

2. Disable changed block tracking.
3. Enable changed block tracking.

How to Resolve "Error Removing Snapshot" Error During ESX/ESXi Virtual

Machine Backup
This article refers to the Barracuda Backup Legacy Release firmware or newer, VMware, VMware vCenter, vSphere, and ESX, and
Agent for VMware Virtual Infrastructure (AVVI).
When AVVI is enabled, you cannot manually delete a vCenter snapshot because when a snapshot is removed from a virtual machine, ESX
automatically creates a Consolidated Helper-0 snapshot which holds the snapshot data until the actual snapshot is deleted. Once the process is
complete, the Consolidated Helper-0 is rolled into the resulting .vmdk file only when the following conditions are met:
Consolidated Helper-0 snapshot file size must meet the minimal snapshot size in VMware which is less than 16MB
None or minimal I/O write on the virtual machine
To automatically delete a vCenter snapshots, log into the Barracuda Backup web interface, and go to the Backup > Schedules page.
If you attempt to manually delete a vCenter snapshot from Barracuda Backup before the Consolidated Helper-0 snapshot is rolled into the VMDK,
an error displays in the Reports > Backup report page in the Barracuda Backup web interface, as shown in the following image:
Verify VMware Disk I/O Issues
If you continue to encounter an error, you may wish to confirm whether there are I/O issues on the virtual machine causing high CPU usage.
1. Log into and restart the virtual machine to commit the Consolidated Helper-0 snapshot.
2. Log into the vCenter/vSphere Snapshot Manager and create a quiesce snapshot file.
3. Once the quiesce snapshot is created, click on the quiesce snapshot file name, and click Delete.
4. When you delete the snapshot, if a Consolidate Helper-0 snapshot continues to display, and the Status field displays an error message
similar to the following:
You may need to adjust your virtual environment to resolve the high CPU usage.
Unlock the quiesce Snapshot
Use the following steps to unlock the Consolidated Helper-0 file:

1. Log into and restart the virtual machine.
2. Allow the quiesce snapshot to commit the snapshot; the Consolidated Helper-0 file should be automatically removed once this process
is complete.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and VMware ESX/ESXi host machines, or vCenter
Server with vSphere except where noted.
When an ESX/ESXi host is added to a vCenter Server using the hostname as opposed to the Fully Qualified Domain Name (FQDN) or IP
address, Barracuda Backup may have issues backing up the guest machines under that host:
To perform a backup of a virtual machine (VM), multiple steps are initiated by Barracuda Backup. The first is to force a Snapshot on each guest
machine scheduled for backup. Once the Snapshot is complete, Barracuda Backup attempts to connect directly to the host to initiate the actual
backup. At this point, if Barracuda Backup cannot resolve the hostname of the host, it cannot continue and fails with the error message Error
reading object:
Why Error Occurs
Barracuda Backup is not a true member of a domain and the only opportunity for it to know what domain to append to a hostname is if it is using
DHCP and the DHCP Server provides the domain search list. If a customer is using a static IP or DHCP does not provide this information, Barrac
uda Backup does not have the necessary information to provide the FQDN to the DNS server for resolution.
Resolve Error
To resolve this error, log in to vCenter, remove the host in question, and then re-add the host using the FQDN or IP address. Be aware that this
process results in the disassociation of all metadata previously associated with that hostname within vCenter, for example, the host's task, event,
and performance history. Note that you must also re-select the VMs for backup within the Barracuda Cloud interface.

Use the following steps to resolve this issue:
1. Within vCenter, right-click the host in question, and click Remove.

2. Right-click on the Datacenter where the host is to be re-added, and click Add Host.
3. In the Host field, enter the FQDN or IP address.
4. Enter the administrative account information for the host, and then click Next.
5. Complete the remaining pages in the Add Host Wizard.
6. Log in to the Barracuda Backup web interface, and edit the VMware data source. The old host displays with a warning ( ) icon
indicating it is no longer available, and the new host displays. Note that you must re-select the VMs you want to back up:
7. After the next backup runs, go to the Reports > Backup page. The old VMs display as Removed, and
the new VMs display as Modified. This indicates that the previous revisions are now associated with the
current host.
8. Go to the data source, and uncheck the old host from the Items list, and save your changes.

If you encounter slow incremental backups when using Changed Block Tracking (CBT), you may need to reset CBT.
Issue
You run a full backup of your virtual machines (VM) running on VMware ESX/ESXi, and then run the backup a second time with only a nominal
difference in completion time, and the data size during incremental backup is small and corresponds to the normal size of an incremental backup.
For example, 2TB of data takes ten hours to back up, an incremental backup takes a similar amount of time to complete, and the increase in data
size is minimal and corresponds to the actual data change rate.
Cause
CBT is improperly detecting changed disk sectors on the backed up VMs, and returns the range equal to the original data backup size. Barracuda
Backup must then read through and analyze all reported sector ranges. This results in the long incremental backup time.
Solution
To resolve this issue, you must manually disable and then re-enable CBT. For more information, refer to the VMware Knowledgebase solution En
abling Changed Block Tracking (CBT) on virtual machines.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and the Barracuda Backup Agent (Windows and
Linux).
The Barracuda Agent is a light weight agent that performs source side-based deduplication, and securely transfers changes over port 5120. Use
the following steps to resolve the "Failed to connect to backup agent software" error:
Step 1. Verify Barracuda Backup Agent is Started
1. Log in to the Barracuda Backup web interface, and go to the Backup > Data Sources page.
2. Determine which appliance is unable to connect to the Backup Agent.
3. Log in to that appliance, open Services, and verify that the Barracuda Backup Agent Service is started.
4. If the Service is not started, restart it.
If you are still unable to connect to the Agent, move on to the next step.
Step 2. Verify Firewall Rules
If you have a Firewall enabled, make sure you have both an inbound and an outbound rule created and enabled for Barracuda Backup.
Step 3. Ping Barracuda Backup from the Server
You can use the ping command to check whether the Barracuda Backup IP address is accessible from the Server.
1. Log in to the appliance that is unable to connect to the Backup Agent.

2. Ping the IP address of the Barracuda Backup appliance.
For additional information and ping command options, refer to the Microsoft TechNet article Using the ping command.
Step 4. Test and Reinstall Barracuda Backup Agent
1. Log in to Barracuda Backup and download and install the latest Barracuda Agent from the System > Software Downloads page.
2. Once the Agent is installed, go to the Backup > Data Sources page.
3. To the right of the appliance unable to connect, click Verify connectivity with the Barracuda Backup Agent software.
4. In the Edit Server page, click Test Software Connectivity.

How to Resolve "Incremental backups cannot be performed while circular

logging is enabled" Error
This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010 and 2013; not
e that circular logging is disabled by default in Microsoft Exchange 2010 and 2013.
Logging Cycle
circular logging is designed to save storage on your Microsoft Exchange Server by preventing transaction logs from building up on the Server.
This is achieved by creating and writing to a total of four transaction log files. Once the fourth log is full, it cycles back to the first log and
overwrites it, creating a logging cycle referred to as circular logging. Once the first log is full, it then moves on to overwrite the second, third, and
fourth, and then cycles back to the first log. The assumption is that by the time the fourth log is filled, the first log is committed.
These transaction logs are saved for use when restoring data. If circular logging is enabled, this is not possible as you are able to restore only to
the last full backup as the transaction log sequence is not consistent making it unreliable.
If you are unable to complete a Smart Backup or Log Backup of your Microsoft Exchange Server, you can enable circular logging. In this case, an
error similar to the following displays either in the Barracuda Backup web interface or in a Barracuda Backup report:
Incremental backups cannot be performed while circular logging is enabled for

<Exchange Storage Group>. Disable circular logging to perform incremental backups.
Disable circular logging in Exchange 2010
circular logging is disabled by default in Microsoft Exchange 2010.
Use the following steps to disable circular logging for the Exchange Storage Groups on the Exchange Server 2010:
1. Log into the Exchange Server as the administrator, and open the Exchange Management Console (EMC).
2. In the console tree, expand Organization Configuration, and click Mailbox.
3. In the result pane, click the Database Management tab and click Properties below the storage group database.
4. Click the Maintenance tab, and turn Off Enable circular logging. Click OK to close the Properties dialog box.
5. Restart the Microsoft Exchange Information Store service or dismount and then mount all of the databases in the storage group.
Disable circular logging in Exchange 2013
circular logging is disabled by default in Microsoft Exchange 2013.
Use the following steps to disable circular logging for the Exchange Storage Groups on the Exchange Server 2013:
1. Log into the Exchange Server as the administrator.

2. In the left pane, click servers, and then click databases at the top of the page.
3. Click on the Mailbox Database, and click the edit ( ) icon.
4. In the Properties window, click maintenance, and turn Off Enable circular logging.
5. Click save to close the Properties window.
6. Click on the Mailbox Database once again, and click the more ( ) icon.
7. Click Dismount database. Once the view refreshes, click the more ( ) icon once again, and click Mount database.
Before you can complete an Exchange Server Smart Backup or Log Backup, you must first perform a full backup to ensure that
transaction logs are reset.

How to Resolve "An error occurred during agent backup initialization" Error
If a backup fails, and the error "An error occurred during backup initialization" displays, there can be a number of causes. Use the information in
this article to resolve this error.
You may need the Barracuda Backup Agent log files and Server Application and System log files to assist in troubleshooting this error.
Use the following troubleshooting options to resolve this error:

Review error message details on the data source
Review the Barracuda Backup Reports
Review the Backup Agent bbtrace.txt log file
Review the Server Application and System event logs
Additional resources
If you receive an email report stating that a source has failed to back up data, or if you notice a red status indicator ( ) on the Dashb
oard page, use these steps to determine the cause of the error.
View Data Source Errors
1. Log in to Barracuda Backup, and go to the Backup > Sources page.

2. To the right of the source, a red status indicator ( ) displays if an error is generated during backup. Mouse-over the status indicator to
view a pop-up message describing the cause of the error:
3. If the error "An error occurred during agent backup initialization" displays, then something during the beginning of the Agent backup
failed.
Review Reports
Use the following steps to review the Barracuda Backup Agent log file and determine if something failed to initialize.
1. Go to the Reports > Backup page, and select the following options in the filter section above the table:
a. Schedules – Select All
b. Sources – Select Agent directly below the Source in question
c. From – Specify a date
2. View the list of reports. A red status indicator displays to the left of a failed backup. Click Details to the right of the most recent backup
report.
3. At the bottom of the Report details page, a list of errors display. Determine the date and time the error occurred:
Review Backup Agent Log Files
Use these steps to review the Backup Agent log files for the specific error reported by the Backup Agent.
1. Log in to the data source that is failing to back up data, and go to the Backup Agent log files. By default, the log files are located
in:
C:\Program Files\Barracuda\Barracuda Backup Agent\log

2.
first identify when the failed backup occurred based on the Report details page; note that there may be multiple days of log details so it
is recommended that you use the search function to find the error.
error message:
In this example, a VSS snapshot failed due to an unexpected operating system error on the targeted server.
Note that an Agent error message is typically followed by associated CRITICAL Sup: Resource not put details which is
not needed for troubleshooting.
Review Source Logs
If the Backup Agent log files indicate an error on the source, use the following steps to review the Application and System log files:
1. Log in to the source server, and locate the Application and System log files for further troubleshooting.
2. In the Application and System log files, locate the time the errors occurred on the Backup Agent based on the Report details page.
3. Critical errors should display for the time in the log files.
4. Review the error messages and determine if additional troubleshooting is needed on the source.
Review the error messages and determine if additional troubleshooting is needed on the source. Use the event ID found in the
Application and System event log files, and use an Internet search engine for troubleshooting.
Restart the Barracuda Backup Agent
If you determine that restarting Services is appropriate for your environment, complete the following steps:
1. Log in to the system, and click Start.

2. Enter services.msc in the Start Search box, and press Enter.
3. In the Services window, right-click Barracuda Backup Agent, and click Restart.
4. Close the Services window.
Additional Troubleshooting
See How to Check Volume Shadow Copy Services Driver State for details on troubleshooting Volume Shadow Copy Services (VSS) drivers.

How to Resolve "Unable to back up virtual machines with independent disks"

Error
Use the steps in this article to resolve the "Unable to back up virtual machines with independent disks" error while backing up an ESX/ESXi virtual
machine.
If you encounter the following error while backing up an ESX/ESXi virtual machine:
When you revert a virtual machine snapshot, it returns to the state the system was in when the snapshot was taken by reloading the memory and
eliminating the matching disk snapshot.
VMware does not support independent disk snapshotting. To back up an independent disk, you must install the Barracuda Backup
Agent on the guest machine and configure a new data source to protect the data on that disk.
If you have Independent turned on in your virtual machines, the persistent attribute of the independent disk prevents a snapshot from being
taken. To resolve this, power off the virtual machine, and disable the following options:
1. Go to Inventory > Virtual Machine > Edit Settings, and click the Hardware tab.
2. Under Mode, clear Independent.

How to Resolve "VMDK is larger than the maximum size supported by

datastore" Error
This article refers to the Barracuda Backup Legacy Release firmware or newer, and VMware ESX/ESXi 4.0 and higher with the
VMware license which includes access to vSphere Data Recovery API.
Use the steps in this article to resolve the error "VMDK is larger than the maximum size supported by datastore" encountered when creating an
ESX/ESXi virtual machine snapshot.
In the vSphere Client, you may see the error:
File is larger than the maximum size supported by datastore.
In the hosted log file, you may see the error:
Snapshot guest failed: The file is too big for the filesystem.
In the vmware.log file of the virtual machine, you may see an error similar to:
vmx| FILE: File_VMFSSupportsFileSize: Requested file size ( 554051831808) larger than maximum supported
filesystem file size (274877906944)
vmx| DiskLibCreateCustom: if your disk is on VMFS, you may consider increasing the block size.
vmx| DISKLIB-LIB : Failed to create link: The destination file system does not support large files (12)
vmx| SNAPSHOT: BranchDisk: Failed to create child disk ' /vmfs/volumes/uuid/vmname/vmname-000001.vmdk' :
The destination file system does not support large files (12)
vmx| SNAPSHOT: SnapshotBranch failed: The destination file system does not support large files (5).
vmx| [msg.checkpoint.save.fail2.std3] Error encountered while saving snapshot.
vmx| The destination file system does not support large files.
These errors occur when the snapshot file has exceeded the maximum size to fit in a datastore. Beginning with version 4.0, ESX/ESXi compares
the maximum size of a snapshot redolog file to the maximum size of files on the datastore. The redolog file may not work correctly once it
reaches the maximum size of the datastore. If the file can grow beyond the maximum size, ESX cancels the Create Snapshot operation and
displays the error message: File is larger than the maximum size supported by datastore
ESX/ESXi 3.5 and Earlier

This does not apply to ESX/ESXi versions prior to 4.0; in prior versions, a snapshot is created even if there is insufficient space to store
the full size redolog.
Use the following steps to resolve this error.
Step 1. Determine Maximum File Size
1. Compare the base disk size of the virtual machine against the block size of the datastore which contains the working directory of the
virtual machine. By default, the working directory contains the virtual machine's .vmx configuration file. Note that the maximum file size
differs among versions of ESX/ESXi and among versions of VMFS.
2. If you experience this error even after confirming that the snapshot files can fit on the datastore, proceed to STEP 3.
A virtual machine on NFS or VMFS has a maximum virtual disk size of 2TB - 512Bytes, the same as the maximum in each of these
tables.
ESXi 5.0 and 5.1 with VMFS5
On ESXi 5.0 and 5.1 and newly formatted VMFS5, a standard 1MB block size is available. The maximum file size is 2TB - 512Bytes.
Block Size 1MB / Maximum File Size 2TB - 512 Bytes
On ESXi 5 hosts using VMFS5 upgraded from VMFS3, upgraded volumes inherit the VMFS3 block size. The default block size
for new volumes is 1MB. The maximum file size, regardless of block size, is 2TB - 512Bytes. For more information, see the Sto
rage Maximums table in Configuration Maximums for VMware vSphere 5.0.
ESX/ESXi 4.1 and ESXi 5.1 with VMFS3
On ESX/ESXi 4.1 and ESXi 5.1 using a VMFS3 datastore, the maximum file size corresponds to the block size of the VMFS datastore:
Block Size 1MB / Maximum File Size 256GB

Block Size 2MB / Maximum File Size 512GB

Block Size 4MB / Maximum File Size 1TB
ESX/ESXi 4.0 with VMFS3
On ESX/ESXi 4.0, the maximum file size corresponds to the block size of the VMFS3 datastore:
Block Size 1MB / Maximum File Size 256GB - 512Bytes

Block Size 2MB / Maximum File Size 512GB - 512Bytes
Block Size 4MB / Maximum File Size 1TB - 512Bytes
Step 2. Move Files to Accommodate Space Requirements
This step describes how to resolve this error by changing either the location of the virtual machine configuration files or the workingDir to a
datastore with enough block size.
The workingDir is the location where the snapshots are created, By default, the workingDir contains the virtual machine's .vmx configuration file.
To change the workingDir directory to a datastore with enough block size, see the VMware solution Creating snapshots in a different location than
default virtual machine directory (1002929).
To move the virtual machine's disks and/or configuration files, use Storage vMotion or cold migration with relocation of files. For more information,
see the following VMware documentation:
vSphere 5: Migrating Virtual Machines section of the vCenter Server and Host Management Guide.
vSphere 4.1: Migrating Virtual Machines section of the vSphere Datacenter Administration Guide.
vSphere 4.0: Migrating Virtual Machines section of the vSphere Basic System Administration Guide.
If the virtual machine already has snapshots, some procedures may not work, or they may attempt to create a snapshot. Table 1 table lists the
requirements for the various procedures.
Table 1. Procedure Requirements.
Procedure Requirements
Storage vMotion The virtual machine must not have snapshots on ESX/ESXi 4.1 hosts
or earlier. It may have snapshots on ESXi 5.0 or later.
Cold migration with file relocation The virtual machine may have snapshots. The source and
destination hosts must be running ESX/ESXi 3.5 or later.
Change workingDir The virtual machine may have snapshots. When new snapshots are
created, new redologs are placed in the workingDir directory.
Hot clone The virtual machine may have snapshots, but the snapshot hierarchy
must be less than 31 snapshots deep. Hot cloning a virtual machine
creates a snapshot on the source at the beginning of the process,
and then deletes the snapshot at the end of the process.
Cold clone The virtual machine may have snapshots. Cloning the virtual
machine creates a new virtual machine with the same content as the
original virtual machine, but without snapshots.
vMotion to ESX/ESXi 3.5 The virtual machine may have snapshots. The virtual machine must
use hardware version 4. ESX/ESXi 3.5 does not perform the check
described here and allows snapshots to be created.
Step 3. Calculate Required Overhead
The failure depends on the size of the virtual disk. All virtual machines that have disks greater than the maximum supported size by VMFS may
experience this error. Overhead for the snapshot is approximately 2GB for a disk size of 256GB. If snapshots are to be used, consider the
overhead while deciding the size of the disks:
Maximum VMDK Size Maximum Overhead Maximum Size Less Overhead
256GB - 512B ~ 2GB 254GB
512GB - 512B ~ 4GB 508GB
1TB - 512B ~ 8GB 1TB

2TB - 512B ~ 16GB 2TB
VMware recommends that you create virtual disks that are smaller than the maximum size minus the overhead to enable the use of features such
as snapshotting, cloning, and independent non-persistent disks.

How to Resolve "Error backing up selected object" Error
Through the Barracuda Backup web interface you can select specific folders for back up within a parent directory. However, if a folder that has
been selected for backup is moved or removed from the parent directory, the Barracuda Backup appliance generates an error because the
item selected for back up is no longer present:
To resolve this error, log in to the web interface and deselect the folder which has been removed from the directory for the source. To do so,
1. Log in to Barracuda Backup, and go to the BACKUP > Sources page.

2. Click Edit to the right of the source to edit share settings.
3. Expand the item selection. The folder displays with a warning triangle:
4. Uncheck the removed folder, and click Save to save your settings.
Important
Deselecting folders and/or files purges the associated data from the Barracuda Backup appliance.

If you encounter errors during backup initialization of Microsoft Server 2008 or 2008 R2, or Small Business Server (SBS) 2011, you may have
misconfigured or disabled Volume Shadow Copy Services (VSS) drivers. Microsoft provides a command-line tool to verify the state of the VSS
writers. To utilize this tool, open a command prompt on the Windows Server, and enter: vssadmin list writers
Following is an example using this tool to check driver status:

C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001
Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {449e12cf-6b8f-4d75-a821-bc869d6612c4}
State: [1] Failed
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {de3b2861-77f6-43f8-8619-64dc9ea2fbcf}
State: [1] Stable
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {9036fdfa-05ef-4f7d-9c2f-84fa2f06560a}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {f9f92826-a3d4-486c-ade3-a4201deb8ad2}
State: [7] Failed
If the output of this command contains writers with a state that is not 'Stable', you must restart the VSS service Volume Shadow Copy Services. If
you continue to see this error in reports and agent logs even after restarting the services, register your VSS drivers use the following instructions:
Windows Server 2008 and Windows Server 2008 R2 – VSS drivers on Windows Server 2008 and 2008 R2 can normally be reset by
restarting the Services from the Management Console based on the Microsoft Knowledgebase solution No VSS writers are listed when
you run vssadmin list writers on Windows Server 2008.
Small Business Server (SBS) 2011 – Refer to the Microsoft Knowledgebase solution You May Get VSS Warnings in the Application
Event Log of SBS 2011 Standard.

Important
Restarting VSS on Windows 2008 can cause unexpected behavior. Verify that all necessary writers (e.g., Hyper-V or
Exchange) have restarted or data objects may not be detected or backed up. It is recommended that you reboot the Server in
lieu of restarting the VSS writer components listed below, and verify that all appropriate Microsoft updates are installed.
Restarting VSS on SBS 2011 may cause post installation errors to display. See the Microsoft Knowledgebase solution Window
s SBS 2011 Standard Known Post Installation Event Log Errors and Warnings for additional information.
If you determine that restarting Services is appropriate for your environment, complete the following steps:
1. Log in to the system, and click Start.

2. Enter services.msc in the Start Search box, and press Enter.
3. In the Services window, right-click each of the following services individually, and then click Restart:
COM+ Event System
Volume Shadow Copy
4. Close the Services window.
5. Open an elevated command prompt, enter:
vssadmin list writers
6. Press Enter.
7. Verify that the VSS writers are listed.
Barracuda Networks Technical Support

If you continue to experience problems with your VSS drivers in relation to your Barracuda Backup Server, contact Barracuda Networks
Technical Support.
Error occurred during backup initialization

This article refers to Barracuda Backup firmware version 6.2 and higher, and Microsoft Windows 7, Windows 8, Windows 10,
Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Vista, except where noted.
During backup, your organization may encounter performance or resource contention. To reduce this possibility, first evaluate the systems in your
environment for hardware-specific performance limitations. Once this is determined, configure data sources for backup, and then monitor system
performance using a system performance monitoring tool.
Monitor Windows System Components
This utility is available for Windows 7, Windows 8, Windows 10, Windows Server 2008 R2, Windows Server 2012, and Windows Vista.
Evaluate Windows system components using a tool such as Windows Performance Monitor to evaluate performance in real time during backup
or by reviewing historical data. You can view the results in graph, histogram, or report form. This utility organizes the results by object, counter,
and instance which you can customize as data collector sets:
Performance counters
Event trace data
System configuration information (registry key values)
An object is a system resource category, and counters are the properties of that object. For example, % Processor Time and Interrupts/sec are
counters for the Processor object.
For additional information, refer to the following Microsoft TechNet articles:
Windows Performance Monitor

Using Performance Monitor
Creating Data Collector Sets
CPU Usage
If backups consume too much CPU processing, system performance is affected. To determine whether a system is consuming too much CPU
processing during backup, monitor the % Processor Time counter for the Processor object. This counter measures the time the processor
spends working on productive threads against time spent servicing requests. The normal range for the counter is 0-80%, with occasional spikes
up to 100%. Consistent values over 80% indicate a potential performance hit on the CPU load.
To determine the number of processes waiting, monitor the Process Queue Length for the System object. A continuous value of two or more
indicates too many threads are queued up for processing. If you encounter a sustained value of 0, verify that a non-zero value can display.
Determine the default scale for the Process Queue Length counter to determine the actual value. For example, if the scale is 10x,
then a reading of 20 indicates 2 waiting processes.
Memory Usage
If memory usage is too high, backup operations are negatively affected. To determine the amount of committed virtual memory in bytes, use the
Committed Bytes counter for the Memory object. Verify that the Committed Bytes value is not approaching the amount of physical memory.
Additionally, determine hard page faults on the system. Hard page faults occur when requested information is not where the application expects it
to be, and must be must be retrieved either from another location or from the page file. Review for both a sustained value, which may indicate
memory usage is too high, as well as the number of hard page faults that represent the actual read/write requests. A high Page Fault/sec rate
may negatively affect performance and indicate insufficient memory. To resolve hard page faults, use the Page Faults/sec counter on the Memo
ry object.
Disk Load
Use the disk performance counters to evaluate disk subsystem performance including disk controller card, High disk load during backup
negatively affects performance. I/O bus, and the disk. Use the %Disk Time counter on the PhysicalDisk object to determine the elapsed time
that the disk processes read/write requests. Additionally, use the Avg. Disk Queue Length counter on the PhysicalDisk object to determine the
number of processes waiting for the hard disk. A value greater than one that lasts for more than one second indicate multiple processes are
waiting and indicate heavy disk load.
Enable Disk Performance Counters

If the disk performance counters are disabled, use the following steps to enable all disk performance counters:
1.


diskperf -y
2. Restart the Windows system. Once the system restarts, all disk performance counters are enabled.
For additional information on using Diskperf, refer to the Microsoft TechNet article Diskperf.

How to Increase Backup Performance
It can take longer to back up multiple small files in comparison to one large file. To improve performance during backup:
Turn off virus scanning on Windows systems, this can double performance
Upgrade network interface card (NIC) drivers to the latest release
Barracuda has encountered issues with several server network cards which were resolved by upgrading the network driver.
Increase system background performance over foreground performance

Uninstall unused/unnecessary programs
Remove unnecessary files using a program such as Disk Cleanup to remove temporary files, empty the Recycle Bin, and to
remove other unnecessary items
Run fewer programs when the Backup is scheduled to run
Apply the latest service packs and system patches
Review data fragmentation levels; you can set Disk Defragmenter to run on a schedule or run it manually
If appropriate, add secondary physical disks to the system to increase performance
Add additional memory to the system
Use RAID devices for greater throughput
Review the system controller
Install the Barracuda Agent on a less used partition rather than a heavily used partition
For details on moving the Barracuda Backup Agent database to an alternate location, refer to the following articles:
How to Manually Move the Barracuda Backup Agent (Windows) Database to an Alternate Location
How to Manually Move the Barracuda Backup Agent (Linux) Database to an Alternate Location

How to Move the VSS Snapshot Location
This article refers to the Barracuda Backup Legacy Release firmware or newer, Microsoft® Windows® 2008 Server, and Microsoft Volume
Shadow Copy Services (VSS).
By default, VSS is configured to write shadow copies to a storage location on the local volume which can result in VSS errors during backup if the
Windows 2008 Server is low on disk space or the IO is too high to maintain the shadow copies. To resolve this issue, you can configure VSS to
write shadow copies to a different drive or NTFS volume on the Server. Dedicate a separate drive that is not being backed up to the shadow
copies, or if a separate drive is not available, configure a separate NTFS volume on the server that contains the paging file and is not being
backed up.
Use the following steps to configure VSS to write the shadow copies to a different location:
1. On the Windows 2008 Server, navigate to C:\Windows\System32\, right-click cmd.exe, and click Run as administrator
.
2. At the command prompt, run the following command:
vssadmin add shadowstorage /for=<backed up drive> /on=<new shadow copy drive> /maxsize=<allowed disk
space percent usage>
3. if the VSS shadow copies of drive D: are to be stored on drive C: and can use up to 90% of free disk space on drive C, you would enter
the command:
vssadmin add shadowstorage /for=d: /on=c: /maxsize=90%
4. Once the command is run, the following message display:
Successfully added the shadow copy storage association
5. To view the shadow copy storage locations, run the following command:
vssadmin list shadowstorage

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010 DAG.
If you encounter warnings such as log truncation failed to complete or the database is unavailable for recovery upon completion of a backup
performed on an Exchange 2010 database that is a member of a Database Availability Group (DAG), use the steps in this article to disable the
Exchange Replica Writer, and then execute a new backup.
Determine Active and Passive Mailboxes
To determine if there are a combination of active and passive mailboxes,
1. Log in to the Exchange Server as the administrator, and open the event log.
2. In the log file, search for and view Event ID 2137, for example:
Log Name: Application
Source: MSExchangeRepl
Date: 24/01/2014 11:25:00 AM
Event ID: 2137
Task Category: Service
Level: Warning
Keywords: Classic
User: N/A
Computer: EX01.exchangebbs.local
Description:
RPC request to the Microsoft Exchange Information Store service for log truncation failed for database Mailbox Database 02\EX01.
Error: 3523092309
3. To determine where Mailbox Database 02 is mounted, at a command prompt, enter the following command:
C:\>Get-MailboxDatabaseCopyStatus
4. Press Enter. The results displays the name, location, and status of the Mailbox Databases, for example:
Name Status
---- ------
Mailbox Database 01\EX01 Mounted
Mailbox Database 02\EX01 Failed
Archive Mailboxes\EX01 Mounted
5. In the above example, log truncation on Mailbox Database 02 failed because it is a passive database copy on server EX1 and is
mounted on a different DAG member.
Disable Exchange Replica Writer
Use the following steps to disable Exchange Replica Writer,
1. On the Exchange Server, type regedit in the Start menu to open the Registry Editor.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V14\Replay\Parameters
3. Add a DWORD entry EnableVSSWriter and set the value data to 0 (zero).
C:\>Restart-Service MSExchangeRepl
5. Press Enter. The Microsoft Exchange Replication Service restarts.
6. The VSS Writer for Exchange 2010 Mailbox Database backups is now disabled.
Run the Backup Job
You can now log back in to the Barracuda Backup web interface and rerun the Exchange Server 2010 DAG backup from the Backup >
Schedules page.

Understanding "Unable to Quiesce Disk" Warning During ESX/ESXi Virtual

Machine Backup
This article describes the possible causes of the warning "Unable to quiesce disk" encountered while backing up an ESX/ESXi virtual machine, as
shown in the following image:
There are numerous issues that can generate this warning such as corrupt or out-of-date VMware Tools, or a VSS writer error on the guest
machine.
Understand Quiescing
According to VMware, quiescing a file system is a process of bringing the on-disk data of a physical or virtual computer into a state suitable for
backups. This process might include such operations as flushing dirty buffers from the operating system's in-memory cache to disk, or other
higher-level application-specific tasks; see the VMware knowledgebase solution Understanding virtual machine snapshots in VMware ESXi and
ESX (1015180) for additional detail.
The process of quiescing a file system prior to backup provides for an application-consistent backup. Using VMware Tools, VMware instructs the
guest operating system to prepare for the backup. As of firmware version 6.0.07, if it is unable to quiesce the disk, the Unable to quiesce disk w
arning is generated and the snapshot and backup are crash consistent. Though the backup is still valid in this case, it is highly recommended that
you resolve the underlying issue preventing the file system from being quiesced. In firmware versions prior to 6.0.07 the backup fails with an
error.
Determine the Cause
To determine the cause, you can manually snapshot the virtual machine (VM), and select the Quiesce guest file system option:
If the Snapshot is successful – The backup issue may be related to the time of day the backup is run and the load on the VM at the
time of backup, or there may be a conflict with another backup solution at that time.
If the snapshot fails – Review the VMware logs as well as the additional information in this article to troubleshoot the issue.
In either case, if you need further assistance, contact Barracuda Technical Support.
For more information, refer to the following VMware knowledgebase articles and documentation:
Troubleshooting Volume Shadow Copy (VSS) quiesce related issues (1007696)

Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off I/O in the frozen virtual
machine (1018194)
A virtual machine can freeze under load when you take quiesced snapshots or use custom quiescing scripts (5962168)

Volume Shadow Copy Services Quiescing

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010.
If you encounter the error message "Error listing messages in a folder" or the message "Error opening message" when running message-level
backups:
This error is due to backup threads established to your Exchange Server that are timing out. To resolve this issue, apply Service Pack 3 (SP3) to
Exchange Server 2010, available from the Microsoft download center: http://www.microsoft.com/en-us/download/details.aspx?id=36768
If you continue to encounter these errors after applying SP3, contact Barracuda Networks Technical Support.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange Server 2010.
To verify the Microsoft Exchange backup completed successfully and backed up the log files:
Check Services
Check the Volume Shadow Copy (VSS) Writers
Check Application Events
Check Services
Open services.msc, and verify that both Microsoft Exchange Information Store and Microsoft Exchange Replication are running:
Check VSS Writers
Microsoft provides a command-line tool to verify the state of the VSS writers. To utilize this tool, open a command prompt on the Windows
Server, and enter: vssadmin list writers
Verify the state for each writer is Stable:

Check Application Events
Use the following steps to open the Event Viewer:
1. Click Start, point to All Programs, point to Administrative Tools, and then click Event Viewer.
2. In Event Viewer, in the console tree, click Application.
3. In the details pane, look for ESE Event ID: 224
4. If you find this event, double-click the event to open the Event Properties, and then read the description of the event:

How to Resolve "A Volume (drive) that was previously backed up is no longer
there and being backed up" Warning
This article describes how to resolve the error "A Volume (drive) that was previously backed up is no longer there and being backed up", as
shown in the following image:
The most common cause of this error is a selected drive missing when a backup runs. To resolve this issue, bring the missing drive back online.
Once the drive is online, the error clears upon the next backup.
If you remove a drive from the backup selection list, all historic data for that drive is removed within 48 hours.
Example Scenario
For example, you add a data source and select to back up drives C and J on the Backup > Sources page:
After a few successful backups, the J drive goes offline and the next backup report displays the warning message:
Go to the Backup > Sources page and view the data source; the drive J is missing:
Bring the missing drive back online to resolve the error once the next backup is run.

How to Resolve "An error occurred during agent backup initialization" Error -
Event ID 8193 - Diff Area
If after following the steps outlined in the article How to Resolve "An error occurred during agent backup initialization" Error you find an error in
the application event logs for VSS Event ID 8193 "Cannot find anymore diff area candidates", there is insufficient storage allocated for the volume
shadow copy snapshot to grow.
Figure 1. Application Event Logs Show Event ID 8193.
For reference, here are the relevant Barracuda Backup Agent logs; the combination of these logs and the above Event ID indicate the issue is
VSS-related, and specifically that there is insufficient storage allocated for the VSS snapshot to grow:
06/30/15 23:58:36 0x0001344 YVssManager: Failed to perform snapshot Exception - Original: 2147754767 - 0x8004230f Mapped:5094
Location:YVssManager::WaitAndCheckForAsyncOperation:C:\Users\Administrator\Documents\repos\agent-source\ods++\server\vam\vss\
YVssManager.cpp:1417 Description:'The shadow copy provider had an unexpected error while trying to process the specified operation.'
06/30/15 23:58:36 0x0001344 YVssManager: Failed to create backup snapset Exception - Original: 2147754767 - 0x8004230f
Mapped:5094
Location:YVssManager::WaitAndCheckForAsyncOperation:C:\Users\Administrator\Documents\repos\agent-source\ods++\server\vam\vss\
YVssManager.cpp:1417 Description:'The shadow copy provider had an unexpected error while trying to process the specified operation.'
Use the steps outlined in this article to help resolve this error.
Step 1. Determine the Volume to which the Error is Referring
The VSS Error references the volume by the GUID. For example, in Figure 1 above:
\\?\Volume{6f0b6b4b-ab80-11e2-a9cd-0010183feca2}\
There are numerous ways to determine which volume this refers to, one of which is to use Powershell.
1. From the Powershell command-line, run:

Get-WmiObject -Class win32_volume | Format-List caption,label,deviceid

2. In the example above, the error is referring to the E:\ drive.
Step 2. Change the Maximum Size Available for the Shadow Copy Storage
1. Open Windows Explorer to your drive.

2. Right-click on the volume in question, and click Configure Shadow Copies:
.
3. The Shadow Copies dialog box displays. Select the volume in question, and then click Settings:

4. The Settings dialog box displays. In the Maximum size section, select either No limit, or select Use limit and select a larger value:
5. Click OK to save your settings changes, and then click OK to close the Shadow Copies dialog box.
Step 3. Perform a New Backup
Perform another backup and verify that the error no longer displays.


If you encounter an error during backup selection, you may have misconfigured or disabled Volume Shadow Copy Services (VSS) drivers. Use
the following steps to help resolve the error.
Step 1. Review bbtrace.txt File
1. Log in to the data source that is encountering the error, and go to the Backup Agent log files. By default, the log files are located in C:\Pr
ogram Files\Barracuda\Barracuda Backup Agent\log
you will first want to identify when the failed backup occurred based on the Report details page; note that there may be multiple days of
log details so it is recommended that you use the search function to find the error.
You may also see a failed to perform/create/open snapshot message following this error.
error message:
07/23/15 23:07:07 0x0000b7c YVssManager: Bad writer status [Microsoft Hyper-V VSS Writer]:
VSS_WS_FAILED_AT_PREPARE_SNAPSHOT
5. In this example, a VSS snapshot failed during backup selection.
6. Note the timestamp in the error, in this example:
07/23/15 23:07:07
7. Review your application and System event logs based on the error timestamp, for example 07/23/15 23:07:07, for any additional
information about these errors to help resolve the problem.
Step 2. Check VSS Writers
1. Open PowerShell.
2. At the PowerShell command prompt, enter the following command:
vssadmin list writers
3. Determine if the Hyper-V VSS writer is in Stable condition. For example:
C:\>vssadmin list writers
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {42422b7b-17aa-4cba-9241-0e34f8982f2f}
State: [8] Failed last error: Retryable error
Step 3. Restart or Reboot
You can either restart the Hyper-V process or reboot the server and run a test backup or wait until the next scheduled backup runs.
If the problem persists, contact Barracuda Networks Technical Support.

How to Resolve "File System Snapshot released, this backup is invalid" Error
If the Backup Exec provider, BeVssProvider, is active or running on the target server, the backup may fail due to a VSS conflict:
If this occurs, note the time of the backup failure and check the associated time in the server's application and system event logs for possible
system errors or notifications.
For example:
In this example, an alternate VSS provider, BeVssProvider, attempted to start, causing a conflict with the Barracuda Backup Agent.
To resolve this issue, disable or uninstall the third-party VSS provider, in the above example, BeVssProvider, or service that installed the
provider. For more information, refer to the VMware knowledge base article, Cannot create quiesced snapshots if backup or system recovery
applications are installed (1009558).

How to Resolve "Error opening object"
If the Barracuda Backup Report displays the message "Error opening object", use the following steps to clear the warning:
1. Verify that your antivirus software has not quarantined your files; quarantined files are locked and cannot be backed up. Remove the files
from the antivirus software quarantine.
2. If you do not find quarantined files, verify the file exists. If the file does exist, verify no other backup agent is running at the same time as
the Barracuda Backup appliance backup process.
3. Review the Backup Agent logs. Open the bbtrace.txt file, usually found here: C:\Program Files\Barracuda\Barracuda Backup
Agent\log. Review the file for errors and cross reference the timestamp with both Application and System window event logs.
If you continue to encounter the warning, contact Barracuda Technical Support.

Resolve the "Failure while using USN journal" Error
This article applies to Barracuda Backup Legacy Release firmware or newer, and Microsoft Windows Server 2008 and higher.
An Update Sequence Number (USN) Journal is a change journal of file and directory changes on the NTFS volume including a description of the
change, and the name of the file or directory. Each log file is incremented for each entry in the journal. Log files are stored until they are deleted
or storage runs out. If storage is exhausted, older log files are deleted and cannot be restored.
If too many file or directory changes are encountered on your Windows Server, you may encounter a max journal wrapping error causing slower
Barracuda Backup Agent backups. While full backups should not be affected, you may encounter differential and incremental backup failure:
08/13/13 18:32:55 0x0001208 YUsnJournalManager: Info: USN journal backups have been disabled for volume:
C:\
08/13/13 18:43:09 0x0001208 YUsnJournalManager: Exception occurred while backing up volume changes:
Exception - Original: 12011 - 0x00002eeb Mapped:12011
Location:YUsnJournalManager::BackupVolumeChanges:D:\compile\source\ods++\server\vam\core\win\YUsnJournalMan
ager.cpp:214 Description:'Failure while using USN journal'
This article describes how to expand the maximum Update Sequence Number (USN) Journal size in Windows.
The following instructions apply only if the USN change Journal is available and readable.
Delete an Active USN Change Journal
Use the following steps to remove the active USN change Journal using fsutil usn deletejournal.
fsutil usn Parameters
deletejournal – Deletes the active USN change journal. Deleting the change journal impacts the File Replication Service
(FRS) and the Indexing Service. Additionally, this negatively impacts FRS SYSVOL replication and replication between DFS
link alternates during rescanning of the volume.
/D – Disables the active USN change journal and returns I/O control while the change journal is being disabled.
1. Log in to your Windows Server, launch cmd, and run as admin.

2. Enter the following command:
fsutil usn queryjournal C:
Where "C" represents the backup or partition drive.
3. The USN change Journal settings display including its size in hex bytes. If the value is approximately 30MB, the backup can fail due to
snapshot creation failure from lack of space.
fsutil usn deletejournal /D C:
5. The USN Journal is deleted and the size reset.
6. You can proceed with your backup.
Add a USN Change Journal
Use the following steps to add a USN change Journal using fsutil usn createjournal.
1. Log in to your Windows Server, launch cmd, and run as admin.

fsutil usn createjournal m=2147483648 a=1 C:
Where "C" represents the backup or partition drive.
3. The USN Journal is added.
Once the USN change Journal is recreated, Barracuda Backup goes through the entire file system which may result in a longer backup.

Resolve the "EWS connection error" for Specific Users in Message-Level

Backup
This article applies to Barracuda Backup Legacy Release firmware or newer, and Microsoft Exchange 2010 Message-Level
backup.
When the NT AUTHORITY/SELF permission is removed from a user, 'EWS connection error' is generated in an Exchange 2010 Message-Level
backup:
To resolve this error:
1. Log in to the Exchange server, and open the Exchange Management Console (EMC).
2. Expand Recipient Configuration, and click Mailbox.
3. Navigate to and right-click the user, and click Manage Full access Permission.
4. Verify that the NT AUTHORITY/SELF permission is missing from the list, and then click Add.
5. Type self in the search field, and click Find Now:
6. Click OK. The permission is added to the list:

7. Click Manage, and then click Finish to update the user permissions.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and Windows 10 and higher.
If you installed the Barracuda Backup Agent on Windows 10 or newer and attempt to restore the C:\Program Files\WindowsApps folder or files,
the restore will fail because Microsoft does not support third-party software running in a normal Windows environment:
Resolve WindowsApps Folder Restore Failed
To resolve this issue, you can restore the entire system using Bare Metal Restore. For more information, see How to Restore a Windows System
to Bare Metal.

Understanding Why VMware Virtual Machine Returns Incorrect Changed

Sectors
Issue
VMware has reported an issue with ESXi version 6.0.x where incorrect changed sectors are returned. When a virtual machine (VM) is running
ESXi 6.0.x and Changed Block Tracking (CBT) is enabled, some change areas in data are not reported. When this occurs, that data is not
recognized as changed and is not backed up; current and past incremental backups are potentially compromised. For more information, see the
VMware knowledgebase solution Backing up a Changed Block Tracking enabled virtual machine in ESXi 6.0.x returns incorrect changed sectors
(2136854).
ESXi600-201511001 (2137545).
Symptoms
VMware version 6.0.x

CBT is enabled
Incremental backups using CBT from ESXi 6.0.X servers may be corrupted or incomplete.
How to Resolve
Upgrade all ESXi 6.0.x servers to the latest available patch and replace all previously generated incremental backups:
1. Upgrade using the VMware solution VMware ESXi 6.0, Patch Release ESXi600-201511001 (2137545).
2. Force an initial new full backup by resetting Changed Block Tracking (CBT) of all the VMs to backup:
a. Open the vSphere Web Client.
b. Right-click the VM and click Power Off.
c. Right-click the VM, click the Snapshot and navigate to Snapshot Manager. Ensure there are no active snapshots. If there are
snapshots present, consolidate them to commit the changes. For more information, see Consolidating snapshots in vSphere
5.x/6.0 (2003638).
d. Right-click the VM, and click Edit Settings.
e. Click the Options tab, select the General section, and click Configuration Parameters.
f. Disable CBT for the VM by setting the ctkEnabled value to false.
g. Disable CBT for the individual virtual disks attached to the VM by setting the scsix:x.ctkEnabled value for each attached virtual
disk to false.
3. Once the host upgrade is complete, run a full backup to ensure incremental backup integrity.
For more information, refer to the following VMware knowledgebase solutions:
Consolidating snapshots in vSphere 5.x/6.0 (2003638)

Resetting Changed Block Tracking for VMware vSphere virtual machines (2139574)
Determining if there are leftover delta files or snapshots that VMware vSphere or Infrastructure Client cannot detect (1005049)
Locating virtual machine log files on an ESXi/ESX host (1007805)
Enabling or disabling Changed Block Tracking (CBT) on virtual machines (1031873)

Agents and Tools
Go to the System > Software Downloads page in Barracuda Backup to download Tools and Backup Agents.
In this Section

How to Silently Install, Upgrade, or Remove the Barracuda Backup Agent (Windows)
Understanding the Barracuda Backup Agent (Windows) File Structure
How to Install and Use the Barracuda Backup Agent (Linux)

Backup Export Tool
Understanding the Backup Export Tool

How to Manually Export Data Using the Backup Export Tool
How to Schedule Automatic Data Export Using the Backup Export Tool
How to Restore Exported Data Using the Backup Export Tool
Backup Export Tool Advanced Options
Backup Export Tool Supported Devices
Configuring Encryption and Compression in the Backup Export Tool
Configuring Backup Schedule Settings
Managing Devices
How to Schedule Restore and Verify Jobs
Advanced Restore and Verify Options
How to Test Your Setup with the Barracuda Backup Export Tool
How to Export Data to AWS Storage Gateway-VTL Using the Backup Export Tool
How to Restore Archived Data from an AWS Storage Gateway Using the Backup Export Tool
Understanding AWS Storage Gateway-VTL
Additional Tools
How to Edit Network Settings through the Barracuda Console

Bare Metal Restore
GroupWise Trusted Key Generation
Related Troubleshooting and Error Message Articles
Resolving "An error occurred during agent backup initialization" Error
Resolving "An error occurred during agent backup initialization" Error - Event ID 8193 - Diff Area

In this Section



This article refers to the Barracuda Backup Legacy Release firmware or newer, and Barracuda Backup Agent (Windows) on the
same major release.

Use the Barracuda Backup Agent (Windows) to back up your Microsoft File System, Microsoft Exchange Server, Microsoft SQL Server,
and system state. For a list of supported Microsoft Windows systems, see System, Platform, and Software Compatibility.
The Barracuda Agent is enabled by default for Windows Servers.
Install Barracuda Backup Agent
1. Log in to the Barracuda Backup web interface, select the desired appliance in the left pane, and go to the System > Software
Downloads page.
2. Download the Barracuda Backup Agent 6.x (Windows) to your local system or server.
3. Navigate to the download location, and run the executable; the installer self-extracts.
4. Follow the instructions in the wizard to complete the installation.
Add Data Sources
Use the following steps to add the Data Source to Barracuda Backup:
1. Log in to the Barracuda Backup web interface, select the desired appliance in the left pane, and go to the Backup > Sources page.
2. Click Add Computer.
3. Enter the following backup source information:
c. Computer name – Enter the FQDN or IP address; must be resolvable on your local network.
d. Computer type – Data source device type. Select Microsoft Windows
e. For network file shares, select Enable File Share Backups, and enter your credentials.
7. Choose Select all items to back up the entire computer, or choose Select specific items to granularly select specific sets of data to
back up; note that you can configure multiple schedules for each source, each with different sets of data.
Set Up Retention
Once you have your data source items set up for backup, you can set up retention policies.

This article refers to the Barracuda Backup Legacy Release firmware or newer, and the Barracuda Backup Agent (Windows) on the
same major release.
Use the steps in this article to "silently" install, upgrade, or remove the Barracuda Backup Agent. These steps apply to either a new installation or
an upgrade to a previously installed version of the Agent.
Install the Agent
2. Under Barracuda Backup Agent, click Download the latest version, and download the .exe installer file to the system you intend to back
up.
3. At a command prompt, change the directory to the location where you saved the Agent .exe installer file, and enter the following
command:
barracuda_backup_agent-version.exe -sp"-silent=yes -install=Yes"
Where version represents the version of the downloaded .exe installer file. For example:
barracuda_backup_agent-6.3.03.exe -sp"-silent=yes -install=Yes"
Upgrade the Agent
Use the following steps to upgrade the Barracuda Backup Agent:
2. Under Barracuda Backup Agent, click Download the latest version, and download the .exe installer file to the system you intend to back
up.
3. At a command prompt, change the directory to the location where you saved the Agent .exe installer file, and enter the following
command:
barracuda_backup_agent-version.exe -sp"-silent=yes -upgrade=Yes"
Where version represents the version of the downloaded .exe installer file. For example:
barracuda_backup_agent-6.3.04.exe -sp"-silent=yes -upgrade=Yes"
Remove the Agent
Use the following steps to remove the Barracuda Backup Agent:
At a command prompt, change the directory to the location of the Agent .exe installer file, and enter the following command:
barracuda_backup_agent-version.exe -sp"-silent=yes -remove=Yes"
Where version represents the version of the Agent .exe installer file. For example:
barracuda_backup_agent-6.3.04.exe -sp"-silent=yes -remove=Yes"


same major release.
This article describes the overall file structure of the Barracuda Backup Agent (Windows) installation.
Important
If the volume on which the Backup Agent is installed has less than 2GB available free space, the Backup Agent attempts to move its
database to another volume. For details and resolution, see Understanding Why the Barracuda Backup Agent Moves to a New Volume.
The Barracuda Backup Agent default installation directory is: C:\Program Files\Barracuda\Barracuda Backup Agent
The following application is contained in this directory:
File Details
setup.exe Setup installation file.
Within this directory, the following folders contain:
Folder Details
config This folder contains the Barracuda Backup Agent configuration files
including:
config.ini - Contains the Barracuda Backup Agent build number

and installation version. Additionally, you can modify the file to
take advantage of additional features, for example, change the
Backup Agent port number.
bbfilter.ini - Initializes Backup Agent filters.
install.ini - Contains installation configuration settings.
database Contains the local database used for source-based deduplication,

and maintains the organization of the managed files for backup. This
folder contains multiple .dat files.
log Contains the Backup Agent log files; bbtrtace.txt is always the most
recent log file. Each time the Backup Agent Service is restarted, a
number is appended to the current bbtrace.txt file, and a new file is
generated. Use these files to understand and resolve any errors that
may occur with the Backup Agent such as an Agent backup
initialization error.
resource Contains the Backup Agent resource files.

temp Remains empty unless an update is downloaded, at which time the

update installer is temporarily added to this folder during installation.
win Contains the .dll files and applications used by the Backup Agent
Service.
Barracuda Backup Agent Service

The Backup Agent runs as a Service called Barracuda Backup Agent:
Process Name
In the Task Manager, the process displays as bbwinsdr.

How to Manually Move the Barracuda Backup Agent (Windows) Database to an Alternate
Location
same major release.
In cases where the partition has limited space, use the following steps to move the Windows Backup Agent database:
1. Log in to the system where the Agent is installed.

2. Open the Agent database folder: C:\Program Files\Barracuda\Barracuda Backup Agent\database\
3. Copy the database named bbs400000 - File Systems.db where 400000 represents the Barracuda Backup appliance serial number:
4. Paste the copied file into an alternate location.

5. Locate the Windows Agent configuration file config.ini in the default file location: C:\Program Files\Barracuda\Barracuda Backup
Agent\config\config.ini
6. Open config.ini using a text editor such as Notepad, and add the following lines to the end of the file:
[fileStores]
bbs400000 - File Systems=C:\Program Files\Barracuda\Barracuda Backup Agent\ database\bbs400000 - File
Systems.db
Where 400000 represents the serial number of your Barracuda Backup Server.
For example:
[installControl]
buildNumber=200513
[configuration]
nodeGuid={00001001-AC5CBCB7-AC4CBCB6-AC5CDCB8}
[fileStores]
bbs400000 - File Systems=C:\Program Files\Barracuda\Barracuda Backup Agent\database\bbs400000 - File
Systems.db
8. Type services.msc in the Start Search box, and press Enter.
9. In the Services window, right-click Barracuda Backup Agent, and click Restart:

9.

In this Section




Barracuda Linux Backup Agent supports:

Backed Up Content
Use the Barracuda Backup Agent (Linux) to back up Linux file systems such as Red Hat, Ubuntu, or SUSE.
The Linux Agent can back up open files, permissions, soft and hard links, and supports multiple data
streams .
Install the Linux Backup Agent
Use the following steps to install the Backup Agent:
1. Log in to Barracuda Backup, and go to the System > Software Downloads page.
2. Download and unzip the Barracuda Backup Agent (Linux) on your local Linux system or server.
3. Unpack the tar file:
tar -zxvf barracuda_backup_agent-x.x.x.tgz
4. On your Linux system, open a terminal window, and change the directory to the Barracuda Linux Backup Agent directory, for example:
5. In the terminal window, run the command sudo ./install:
Press Enter to install the Backup Agent in the default location:
[usr/local/barracuda/bbs]
6. Once the Barracuda Linux Backup Agent installs, the Service automatically starts.
7. In the terminal window, run the command ps-Al to view the Barracuda Linux Backup Agent Service:
8. The Linux Backup Agent is now installed; close the terminal window.
Add the Linux Data Source
Use the following steps to add the Linux Data Source to Barracuda Backup:
1. Log into Barracuda Backup, and go to the Backup > Sources page.
2. Click Add a Computer. Enter a computer description and enter the IP address or fully qualified domain name (FQDN) in the Computer
Name field.
3. From the operating system drop-down menu, select Linux/Unix:

4. Click Save at the top of the page. Specify the data source details in the Add Data Source page.
7. Choose Select all items to back up the entire system, or choose Select specific items to select individual items for backup.
Set Up Retention
Once you have your Linux data source items set up for backup, you can set up retention policies.
Uninstall the Linux Backup Agent
Use the following steps to uninstall the Backup Agent:
1. On your Linux system, open a terminal window, and change the directory to the Barracuda Linux Backup Agent directory, for example:
2. In the terminal window, run the command sudo ./install:
3. Press Enter. A message similar to the following displays:
Found product installed at /usr/barracuda/bbs
Would you like to [r]einstall or [u]ninstall?
4. Enter u to uninstall the Agent.

How to Manually Move the Barracuda Backup Agent (Linux) Database to an Alternate
Location
In cases where the partition has limited space, use the following steps to move the Backup Agent database.
1. At a command prompt, issue the following command where 40000 represents the serial number of your Barracuda Backup Server, and
/opt/ represents the file path to which you want to move the database:
Mv /var/lib/bbs/database/bbs400000 - File Systems.db /opt/database/bbs400000 - File Systems.db
2. Locate the Linux Agent configuration file config.ini in the default file location /usr/local/barracuda/bbs/config/
3. Open config.ini using a text editor, and add the following lines to the end of the file:
[fileStores]
bbs400000 - File Systems=/opt/database/bbs400000 - File Systems.db
Where 400000 represents the serial number of your Barracuda Backup Server and /opt/ represents the database file path.
4. Save the file.
5. Enter the following command to restart the Backup Agent:
/etc/init.d/bbagent restart
6. View the config.ini file; it should look similar to:
[installControl]
buildNumber=200513
[configuration]
nodeGuid={00001001-AC5CBCB7-AC4CBCB6-AC5CDCB8}
[fileStores]
bbs400000 - File Systems=/opt/database/bbs400000 - File Systems.db
7. Close the config.ini file.

Backup Export Tool
Data copies from a Barracuda Backup appliance to external media (tape or disk) using the Backup Export Tool. Supported on
Barracuda Backup 64-bit architecture firmware version 6.1 purchased after July 2012.
The Backup Export Tool, free for Barracuda Backup customers, allows Barracuda Backup users to export historical revisions of data backed up
and stored on a Barracuda Backup appliance or appliances.
General Overview

Supported Devices
Managing Devices
Export

How to Schedule Automatic Data Export
Configuring Encryption and Compression
Advanced Options
Restore

AWS Storage Gateway-VTL

What is AWS Storage Gateway
Getting Started with AWS Storage Gateway
Setting Up Your Gateway-VTL
How to Restore Archived Data from an AWS Storage Gateway Using the Backup Export Tool
Managing Your Activated Gateway
BET


Data copies from a Barracuda Backup appliance to external media (tape or disk) using the Backup Export Tool. The Backup Export
Tool is supported on Barracuda Backup 64-bit architecture firmware version 6.1 purchased after July 2012 and is available from the
System > Software Downloads page in the web interface.
The Backup Export Tool, free for Barracuda Backup customers, allows Barracuda Backup users to export the historical revisions of data backed
up and stored on a Barracuda Backup appliance or appliances. The Backup Export Tool is installed on a media server in the same network as the
Barracuda Backup appliance. Once installed, users can browse connected Barracuda Backup appliances through the Backup Export Tool, locate
data required for export, and export it to external media such as tape drives, tape libraries, virtual tape libraries (VTL), USB drives, and network
attached storage (NAS). Data can be manually exported, or automatically exported on a schedule for weekly, monthly, and yearly revisions.
The Backup Export Tool was designed to allow users to export backup data to external media for long-term archival or for compliance reasons
which may require data to be stored on tape or other form of external media. The Backup Export Tool is not intended to provide disaster recovery
capability and exporting data from a Barracuda Backup appliance does not remove it from the appliance.
Export Data
Data stored "in-retention" on a Barracuda Backup appliance can be copied to external media for long-term archiving. This data includes file
system data, application databases (Microsoft SQL and Exchange), and Hyper-V virtual disks, all backed up using the Barracuda Backup Agent
for Windows. The Backup Export Tool can read "received" data from a Barracuda Backup appliance that is receiving data from another
Barracuda Backup appliance in a site-to-site replication model.
Which data types can be copied using the Barracuda Export Data stored "in-retention" on a Barracuda Backup appliance can be
Tool? copied to external media for long-term archiving including file system
data, application databases (SQL and Exchange), and Hyper-V
virtual disks.
Support for VMware images available in version 6.3.01 and higher.
System-state and message-level data are not supported.
Which types of external media are supported? Tape drives, tape libraries, virtual tape libraries (VTL), USB drive, AW
S Storage Gateway-VTL, and network attached storage (NAS).
Can data from Barracuda Backup be copied to tape or disk for When copying data from your Barracuda Backup appliance to
disaster recovery? external media, such as tape or disk, the data is first rehydrated
(undeduplicated), then stored in the Barracuda Export Tool
proprietary format. Data copies are for specific data types only and
cannot be recovered back to a Barracuda Backup appliance if a
disaster occurs.
Configure Barracuda Backup to replicate to Barracuda Cloud Storage

or another Barracuda Backup appliance to mirror the Barracuda
Backup appliance data set for disaster recovery. In other words, if a
disaster occurs, your data can be repopulated from the replicated
copy.
How do I use the Barracuda Export Tool to copy data from a The Backup Export Tool software is installed on a media server in the
Barracuda Backup appliance? same network as the Barracuda Backup appliance. The media server
must have access to the external media, for example, iSCSI adapter
or via network shares.
Data can then be manually or automatically copied to external media

from a Barracuda Backup appliance. A report is sent once the job is
complete by the Backup Export Tool software.
Can I encrypt data copies? Yes, encryption is optional.
Which data revisions can be copied on a schedule? Any revision can be exported manually. Only weekly, monthly, and
yearly revisions are available for scheduled exports.
Is a separate subscription or hardware needed to use the No, there is no charge for using the Backup Export Tool.
Barracuda Export Tool?
Do I need to back up data using the Barracuda Export Tool and All data should be backed up using Barracuda Backup as your
Barracuda Backup? primary device for data recovery.

Can I use the Barracuda Export Tool with a Barracuda Backup Yes, the Backup Export Tool can connect to a Backup "sender" or a
"receiver"? Backup "receiver" for systems setup for site-to-site replication.
Will this interrupt my backup schedules? No. Backups continue to run as scheduled. However, to improve
performance, these can be configured to run at different times.
Is data purged off my Barracuda Backup appliance after it is No, data is not automatically removed from your Barracuda Backup
exported? appliance. All data on your local Barracuda Backup appliance is
retained to match your configured retention policy.
Can I use the Barracuda Export Tool data copies with Offsite For data retention up to 12 monthly copies and 7 years, Barracuda
Vaulting? Backup can be configured to use Offsite Vaulting to another Backup
appliance or Barracuda’s Cloud Storage. If using the Backup Export
Tool to external media in conjunction with Offsite Vaulting, data
revisions that are copied must exist on the local Barracuda Backup
appliance storage. As Offsite Vaulting automatically removes
revisions older than the first 30 days, the oldest revision is the end of
the month. Offsite Vaulting removes monthly and yearly revisions
from the local appliance for long-term archival in the Barracuda
Cloud.
How do I restore data from external media? Once data is exported to external media, it can be restored back to
the network using the Backup Export Tool. As the data is stored in a
raw undeduplicated format, it can be recovered independently from
Barracuda Backup.


The master server hosts a special-purpose database, represented by the catalog object in the user interface. The database contains all
information regarding the backup domain. The master server is hardware agnostic, meaning it can be either physical or virtual.
System Requirements
Depending on your organization's backup needs, your system should meet the following requirements:
The Backup Export Tool Catalog requires additional space. When you install the Backup Export Tool on the machine that will serve as
the Domain Server, Barracuda recommends selecting a hard drive other than the default drive. A disk drive with at least an additional 20
GB is recommended
VGA display with 1024x768 resolution, for use with Windows or an X Window System
CD or DVD writer for use with the Backup Export Tool Bare Metal Disaster Recovery (recommended)
The Backup Export Tool supports all major storage hardware technologies and requires at least one storage media drive and/or library and the
appropriate controller card.
512 MB RAM required (1024 MB RAM recommended) above operating system and application requirements
400 MB hard disk space required (typical installation)
Internet Explorer 6 or higher required for all Windows installations
At least 20GB hard disk space recommended on the machine that will serve as the Backup Export Tool master server for the Backup
Export Tool Catalog.
Supported Platforms
Barracuda Export Tool is supported by and has been tested with many different versions of Windows and Linux operating systems. For the most
current list of supported platforms, visit http://www.barracudaware.com
Barracuda recommends that you install the latest service packs and updates for your operating system.
Most operating systems list both minimum and recommended system requirements. As a general rule, if your system meets the minimum
requirements for the operating system, it will also meet the minimum system requirements of the Backup Export Tool.
Barracuda has certified the operating systems and applications listed below to be compatible with the Backup Export Tool. The Backup Export
Tool is designed using standard operating system facilities and has been observed to be compatible with more operating systems than have been
officially certified. If your operating system distribution or version is not listed here, use the 60-day evaluation period to test Backup Export Tool in
your environment.
Table 1. Windows Requirements.
Version Edition Proc Service Pack
Server 2016 Standard x86_64
Server 2016 Datacenter x86_64
Server 2016 Essentials x86_64
Server 2012 Standard x86_64 R2
Server 2012 Datacenter x86_64 R2
Server 2012 Essentials x86_64 R2
Windows 10 Enterprise x86, x86_64
Windows 10 Pro x86, x86_64
Windows 8.1 Enterprise x86, x86_64 1
Windows 8.1 Pro x86, x86_64 1
Windows 8 Enterprise x86, x86_64 1
Windows 8 Pro x86, x86_64 1

SBS 2011 Small Business Server x86_64
Windows 7 Home Premium x86, x86_64 1
Windows 7 Professional x86, x86_64 1
Windows 7 Ultimate x86, x86_64 1
Server 2008 Foundation x86, x86_64 2, R2 SP1
Server 2008 Standard x86, x86_64 2, R2 SP1
Server 2008 Enterprise x86, x86_64 2, R2 SP1
Server 2008 Datacenter x86, x86_64 2, R2 SP1
Server 2008 Web x86, x86_64 2, R2 SP1
Server 2008 Storage Server x86, x86_64 2, R2 SP1
Server 2008 SBS x86_64 2, R2 SP1
Server 2008 EBS x86_64 2, R2 SP1
Vista (1) Basic x86, x86_64 1, 2
Vista (1) Home Premium x86, x86_64 1, 2
Vista (1) Business x86, x86_64 1, 2
Vista (1) Ultimate x86, x86_64 1, 2
Vista (1) Enterprise x86, x86_64 1, 2
Server 2003 Standard x86, x86_64 1, R2 SP2
Server 2003 Enterprise x86, x86_64 1, R2 SP2
Server 2003 SBS x86 1, R2 SP2
Server 2003 Storage Server x86, x86_64 1, R2 SP2
XP Professional x86, x86_64 2, 3
Note: (1) Service Pack 0 - No Disaster Recovery
Table 2. Linux Requirements.
The values in Table 2 apply to the listed versions—except Media Servers for tape, optical devices, and loaders—only in case of release kernel.
Version Edition Proc Service Pack
RHEL 6 x86, x86_64 1, 2, 3, 4
RHEL 5 x86, x86_64 1, 2, 3, 4, 5, 6, 7, 8, 9
SLES 11 x86, x86_64 1, 2, 3
Ubuntu 13 Desktop and Server Edition x86, x86_64 04
Ubuntu 12 Desktop and Server Edition x86, x86_64 04(1), 10(1)
Ubuntu 11 Desktop and Server Edition x86, x86_64 04, 10
Note: (1) Bare Metal Disaster Recovery (BMDR) is not supported with 3.5.x kernels.
Barracuda Export Tool

BET

This article refers to Barracuda Backup firmware 6.3 or higher.
Tool is supported on Barracuda Backup 64-bit architecture firmware version 6.1 purchased after July 2012 and is available from the Sy
stem > Software Downloads page in the web interface.
You must open outbound port 3817 to access Barracuda Backup from the Backup Export Tool.
To install the Backup Export Tool:
1. Log in to Barracuda Backup, and go to the System > Software Downloads page.
2. In the Backup Export Tool section, click Download the latest version to download and save the Backup Export Tool installer to the
target master/media server.
3. Right-click the installer, and then click Run as administrator.
4. In the installer window, select a Destination folder where you want to extract the installer, and then click Extract the installer.
5. Once the installer is extracted, locate and open the folder from the specified destination folder:
6. Once the installer is extracted, locate and open the folder from the specified destination folder:

7. Right-click setup.exe, and then click Run as administrator to launch the Backup Export Tool installer:
8. Select your language from the drop-down menu, and click OK.
9. Accept the Software License Agreement terms, and click Next.
10. Select Make this machine the Master Server and choose an Installation folder:
11. Click Next. Allow the installation to complete:

11.
12. Click Finish. The Backup Export Tool is now installed.
To configure the Backup Export Tool:
1. Log in to Barracuda Backup according to your setup:

For appliances controlled remotely: log in to login.barracuda.com
For appliances controlled locally: log in to the appliance IP address
2. Go to the System > Barracuda Backup Appliance Settings page, and enter the IP address of the host server where you installed the
Backup Export Tool:
3. Click Save.
4. The Backup Export Tool is now configured for use.
Next Steps:

How to Schedule Automatically Data Export Using the Backup Export Tool


This article refers to Barracuda Backup firmware version 6.3 or newer.
When manually performing a data export or configuring a schedule to automatically export weekly and monthly revisions, it is
recommended that you do this during a time when the Barracuda Backup appliance is not scheduled to run backup jobs. Performing
backups and data export simultaneously can adversely affect Barracuda Backup appliance performance.
After installing and configuring the Backup Export Tool on your master server, enabling it in the Barracuda Backup user interface, and configuring
a media device to which to export data, perform the following steps to manually export data from a Barracuda Backup appliance:
1. On your master server, open the Backup Export Tool.

2. From the Tasks page, double-click Backup:
3. In the New Backup Job window, enter a name to identify the backup/export job:
4. Click OK. The Backup Job Properties window displays. All Barracuda Backup appliances connected to the Backup Export Tool client
display below Network:
5. Expand your Barracuda Backup appliance tree until you reach the backup sources currently being protected by the Barracuda Backup
device:

6. Expand the data source containing the data you want to export. The revisions available for export are listed under Backup Agent in the
tree. Note that only weekly, monthly, and yearly revisions are available for export:
Contact Barracuda Networks Technical Support if you need daily revisions.
7. Select the desired backup revision, and expand the revision to drill down into the folder structure. You can navigate the folder structure
and any supported applications that are present, for example, Microsoft SQL, Exchange, Hyper-V:

8. Navigate to and select the folder(s) containing the data you want to export from the Barracuda Backup appliance. The contents of the
selected folder(s) displays in the right pane:
9. Click Device in the left pane, and then select a device to which to export the selected data:

9.
If you select multiple devices, data is exported to each device simultaneously.
For a list of supported devices, refer to Backup Export Tool Supported Devices.
10. Once you select a device, click Encryption in the left pane:
You can optionally enable encryption and compression on the exported data. For more information, refer to Configuring
Encryption and Compression in the Backup Export Tool.
11. Once you select your optional encryption and compression options, click Configuration in the left pane. Use the Configuration page to
specify how data is written to the selected storage device.
See Configuring Backup Schedule Settings.

12. Once your backup options are configured, click Advanced in the left pane to access advanced options related to email alerts, log files,
barcode filters, and copy policies.
For more information on advanced options, refer to Backup Export Tool Advanced Options.
13. When you are done configuring options, click OK in the lower right corer to create the new backup job.
14. Click Jobs and Media in the left pane. The newly created backup job should now display in the right pane:
15. Click on the backup job, and select Run in the toolbar or right-click the backup job and click Run to execute the data export:

16. In the confirmation dialog, click Yes to run the back job:
17. Click Status and Logs in the left pane to view the backup/export job status:
18. Allow the backup job to complete:

BET

How to Schedule Automatic Data Export Using the Backup Export Tool
When performing a data export manually or configuring a schedule to automatically export weekly and monthly revisions, it is
After installing and configuring the Backup Export Tool on your master server, enabling it in the Barracuda Backup user interface, and configuring
a media device to which to export data, perform the following steps to automatically export data from a Barracuda Backup appliance:

5. Expand the Barracuda Backup appliance tree until you reach the backup sources currently being protected by the Barracuda Backup
device. Select Recurring:

6. From the Archive the most recent drop-down menu, select weekly, monthly, or yearly:
tree.
8. Select the desired backup revision, and expand the tree to drill down into the folder structure. You can navigate the folder structure and
any supported applications that are present, e.g., Microsoft SQL, Exchange, Hyper-V.

10. Click Device in the left pane, and then select a device to which to export the selected data:
Warning
If you select more than one device, data is exported to each device simultaneously.

12. Once you select the optional encryption and compression settings, click Configuration in the left pane. Use the Configuration page to
specify how data is written to the selected storage device.
13. In the Schedule Settings section, select Run repeatedly as the Schedule type, and then select a Start time:
a. In the Interval settings section, click Day, and clear Enable scheduling by day:
b. Click OK. Click Week, select Enable scheduling by week, and select the Day of week from the drop-down menu:

If you want to automatically export historical data monthly or yearly only, then choose those options under Interval set
tings.
If you are running backups every day of the week with your Barracuda Backup appliance, then the weekly revision is
Sunday’s backup. If you only run backups Monday through Friday, then the weekly backup falls on Friday’s backup.
The Backup Export Tool should be run on the day after the weekly backup for the Barracuda Backup appliance has
taken place. For example, the Barracuda Backup appliance is running backups every single day, making Sunday’s
backup the weekly revision. We schedule our weekly export to run every Monday:
Monthly revisions for the Barracuda Backup appliance are created on the last day of the month, so configure data
export to run on the first day of the new month. Yearly revisions for the Barracuda Backup appliance are created on
the last day of the year, so configure data export to run on the first day of the new year.
c. Click OK to save the selected scheduling.
If you want to run an export on the current day's date instead of the next automatically scheduled day, then skip Step
13d below.
d. Click Calendar in the left pane. Right-click the current day's date (highlighted), click Deselect day:
Tip: Before you click OK, click the arrows at the top right of the calendar to view the next month, and verify that the
highlighted day is when you want your weekly, monthly, or yearly scheduled data export to occur:

For more information, see Configuring Backup Schedule Settings.
e. Click OK.
14. Once you have configured your backup and scheduling options, click Advanced in the left pane to access advanced options related to
email alerts, log files, barcode filters, and copy policies.
15. When you have configured all options in your backup job, click OK in the lower right corner to create the new backup job.
16. Click Jobs and Media in the left pane. The newly created backup/export job should now display in the right pane:
17. Click the backup job, and click Run in the toolbar, or right-click the backup job and click Run to execute the data export:

18. Click Yes in the confirmation dialog box to run the backup/export job:
19. To view the backup/export job status, click Status and Logs in the left pane:
20. Allow the backup/export job to complete:

BET


Data exported using the Backup Export Tool cannot be restored back to a Barracuda Backup appliance. This data can be restored
back to the original client system, a different system, or media connected to the master server.
Select files and folders to restore the same way that you select files and folders for backup/export. For a restore, you must specify which version
of the file or folder you want to restore.

2. From the Tasks page, double-click Restore:
3. In the New Restore Job window, enter a name to identify the restore job:
4. Click OK. The Restore Job Properties window displays. All previous backup/export jobs form Barracuda Backup appliances display in
the tree below Network:
5. Expand the tree until you reach the previously exported data you want to recover:

6. Select either the entire folder from the tree, or select individual files in the right pane.
7. Once you select the data you want to restore, the Select Destination window displays. Expand the tree under Network and locate
recovery destination for your selected data. the Backup Export Tool recognizes any computers in the network where the Backup Export
Tool is installed. For example, in the following image, the recovery folder RESTORE_DATA is created on the Backup Export Tool client
system:
8. Once you select a restore destination, click OK.

9. Click Device in the left pane, and choose a device from the list; this is the device you are restoring data from:
Once you select a device to restore from, you can optionally click Configuration and Advanced in the left pane to configure
additional options. For more information, see How to Schedule Restore and Verify Jobs and Advanced Restore and Verify
Options.
10. Once all configuration options are configured, click OK.

11. Click Jobs and Media in the left pane; the newly created restore job should now display in the right pane:

12. Right-click the restore job, and click Run, or click on the restore job and click Run in the toolbar to execute the restore job.
13. In the confirmation dialog, click Yes to run the backup/export job:
14. Click Status and Logs in the left pane to view the restore job status:
15. Allow the restore job to complete. Verify the data is successfully restored.
BET

Backup Export Tool Advanced Options

The options in the following tables are provided for advanced users who need to customize their backup jobs for unique circumstances.
Unless you have specific needs that require changes to the advanced options, leave the default values unchanged.
Settings for All Platforms
Option Description
Eject media after use When selected, the Backup Export Tool automatically ejects the
media at the end of the backup job. This feature only works on
devices that support software eject.
Auto Retention When checked, the Backup Export Tool automatically re-tensions the
media at the beginning of the backup job. This feature winds the tape
cartridge end-to-end, applying equal tension to the entire media for
maximum media life and data integrity. Your device must support
auto re-tension to use this feature.
Create DR bootable media Select this option to write disaster recovery (DR) system information
to the backup media. This option is only useful when the backup
media is bootable as in the case of OBDR tapes or optical media.
However, leaving this option checked does not hurt the backup.
Update DR information on selected machine Check this option to generate DR system information for the selected
machines. The generated system information is saved on the Domain
Server and can be used later to create DR media even after a failure
of the original machine.
Native data streams format Different operating systems transmit data across the network to the
Backup Export Tool in different formats. If you plan to restore files to
a different operating system than the one in which they were created,
the data should be stored on media in a common data format, not in
the native data streams format.
Settings for Windows
Option Description
Enable snapshots By default, the backup job creates a temporary snapshot before
backing up the selected file. Deselect this checkbox to disable
snapshots. A snapshot freezes the volume data at a point in time.
Any subsequent changes are not backed up until the next backup
job. The temporary snapshots are deleted after the job has finished.
If this option is off, files open during backup may not be backed up.
Failure to back up open files are noted in the job logs.
Snapshots are currently implemented only on Windows

platforms. Snapshots are created using Microsoft Volume
Shadow Copy Services (VSS) for those Windows editions
that support VSS.
Reparse points Check this option to back up the reparse point data. When this option
is deselected, the Backup Export Tool backs up the object as if it
were a normal file or directory.
Mount Points When selected, the Backup Export Tool includes the mount point
information in the backup. If this option is not selected, the Backup
Export Tool treats the object as a directory.

Optimize backup order by size If selected, the Backup Export Tool mixes backups of large and small
files in an attempt to maintain consistent throughput to the backup
devices.
Volume restrictions When enabled, volume quota information is backed up.

Backup Export Tool Supported Devices

Data copies from a Barracuda Backup appliance to external media (tape or disk) using the Backup Export Tool. The Backup
Export Tool is supported on Barracuda Backup 64-bit architecture firmware version 6.1 purchased after July 2012 and is available
from the System > Software Downloads page in the web interface.
The Backup Export Tools is designed to support families of devices regardless of the specific device model deployed.
The system supports removable USB disks up to 128 TB.

8mm
Manufacturer Device Name Minimum Version Drives Slots Notes
Certance Sidewinder 50 6.1 N/A N/A AIT-1
Certance Sidewinder 70 6.1 N/A N/A AIT-1
Compaq AIT 50 6.3 sp3c N/A N/A AIT-2
Compaq AIT 35 IDE 6.3 sp3c N/A N/A AIT-1 IDE
Ecrix VXA-1 6.2 sp2a N/A N/A
Exabyte EXB-8500 6 N/A N/A -
Exabyte VXA-320 8.1 sp1a N/A N/A Windows, Linux

only
Exabyte Mammoth 6 N/A N/A EXB-8900
Exabyte EXB-8205 6 N/A N/A 1/2 high version of

8500C
Exabyte VXA-172 8.1 sp2a N/A N/A Windows, Linux

only
Exabyte Mammoth2 6.2 sp1b N/A N/A -
Exabyte EXB-8700 6 N/A N/A Identifies self as

8505
Exabyte VXA-2 6.3 sp3b N/A N/A SCSI, IDE
Exabyte EXB-8505 6 N/A N/A 1/2 high version of

8500C
Exabyte EXB-8500C 6 N/A N/A 8500

w/compression
Exabyte EXB-8200C 6 N/A N/A 8200

w/compression
Exabyte EXB-8200 6 N/A N/A -
Exabyte VXA-1 7.0 sp5b N/A N/A
NEC ND-6500A 8.1 sp1d N/A N/A Windows/Linux

only. Disaster
Recovery NOT
supported.
Sony SDX-400C 6.2 sp3f N/A N/A AIT-1
Sony SDX-700C 6.3 sp2b N/A N/A AIT-3
Sony SDX-450V 7.0 sp7b N/A N/A AIT-1 Turbo
Sony SDX-250V 7.0 sp7b N/A N/A AIT-E Turbo

Sony SDX-560V 7.0 sp7b N/A N/A AIT-2 Turbo, IDE
Sony SDX-520V 7.0 sp5b N/A N/A AIT-2, IDE
Sony SDX-900V 7.0 sp7c N/A N/A AIT-4
Sony SDX-460V 8.1 sp2a N/A N/A AIT-1, USB,

AITe100T-UL,
Windows only
Sony SDX-700V 7.0 sp5b N/A N/A AIT-3
Sony SDX-260V 7.0 sp7b N/A N/A AIT-E Turbo, IDE
Sony SDX-800V 8.1 sp1c N/A N/A
Sony SDX-870V 8.5 sp0 N/A N/A AIT-3Ex, SATA
Sony LIB-81/A4 7.0 sp7c 1 8 AIT-4
Sony SDX-570V 8.1 N/A N/A
Sony SDX-470V 8.1 N/A N/A
Sony SDX-460V, IDE 7.0 sp7b N/A N/A AIT-1 Turbo
Sony SDX-560V 8.1 sp2a N/A N/A AIT-2, USB,

AITe200T-UL,
Windows only
Sony SDX-520C 6.3 sp3c N/A N/A AIT-2, IDE
Sony SDX-300C 6.1 N/A N/A AIT-1
Sony SDX-420V 7.0 sp5b N/A N/A AIT-1, IDE
Sony SDX-500C 6.2 sp1a N/A N/A AIT-2
Sony SDX-1100 8.1 sp3a N/A N/A AIT-5 SCSI
Sony SDX-420C 6.3 sp3c N/A N/A AIT-1, IDE
Sony SDX-550V 7.0 sp7b N/A N/A AIT-2 Turbo
Tandberg VXA-320 8.1 sp1 N/A N/A Windows and Linux

only
ADR
OnStream ADR50 6.2 N/A N/A 50, 50e
OnStream ADR2.120 6.3 sp2a N/A N/A Si,Se
OnStream ADR2.120 6.3 sp3b N/A N/A ide
OnStream ADR2.60 6.3 sp2a N/A N/A usb
OnStream ADR30 6.2 N/A N/A Not Di30
OnStream ADR2.60 6.3 sp1a N/A N/A Si,Se,ide
Autoloader
IBM TS2900 LTO4 HH 9.0 1 9

SAS

IBM TS2900 LTO5 HH 9.0 1 9

SAS
IBM TS2900 LTO6 HH 10.0.01 1 9

SAS
CD/DVD
HL-DT-ST GCE-8487B 8.1 sp3a N/A N/A CD-RW
HL-DT-ST GCC-4482B 8.1 sp1d N/A N/A CD-RW/DVD-ROM
HL-DT-ST GSA-4163B 8.1 sp1d N/A N/A DVD+/-RW
HL-DT-ST GWA-4166B 8.1 sp1d N/A N/A DVD+/-RW
Lacie ND-2500A 8.1 sp1d N/A N/A Windows/Linux

only. Disaster
Recovery NOT
supported.
LG GCE-8483B 8.1 sp1d N/A N/A Windows/Linux

only. Disaster
Recovery NOT
supported.
Lite-On SOHC-4836V 8.1 sp1d N/A N/A CD-RW/DVD-ROM
Lite-On SOHC-4836K 8.1 sp1d N/A N/A CD-RW/DVD-ROM
Lite-On SOHC-4836B 8.1 sp1d N/A N/A CD-RW/DVD-ROM
Lite-On SOHW-1673S 8.1 sp1d N/A N/A DVD+/-RW
Lite-On SOHR-4839S 8.1 sp1d N/A N/A CD-RW
NEC ND-3540A 8.1 sp1d N/A N/A DVD+/-RW
Plextor 504UF 8.1 sp1d N/A N/A
Plextor 712UF 8.1 sp1d N/A N/A Windows/Linux

only. Disaster
Recovery NOT
supported.
Plextor PX-712A 8.1 sp1d N/A N/A DVD+/-RW
Plextor PX-W5224A 8.1 sp1d N/A N/A CD-RW/DVD-ROM
Samsung SW-252S 8.1 sp1d N/A N/A IDE, USB.
Sony CRX216E 8.1 sp1d N/A N/A CD-RW/DVD-ROM
Sony PCGA-DDRW2 8.1 sp1d N/A N/A DVD+/-RW
Teac DW-224E 8.1 sp3a N/A N/A CD-RW/DVD-ROM
Toshiba TS-H492C 8.1 sp1d N/A N/A CD-RW/DVD-ROM
D2D/VTL
Hewlett Packard D2D2500 Backup 8.7 N/A N/A

Enterprise System (iSCSI)
Hewlett Packard D2D4000 Backup 8.7 N/A N/A

Enterprise System (iSCSI)

Hewlett Packard D2D4112 Backup 8.7 N/A N/A FC, iSCSI

Enterprise System
DAT
AIWA GD-24000 6.2 sp1b N/A N/A DDS-3
AIWA HP NCE 6.1 N/A N/A DDS-2, GD-8000
AIWA GD-8000 6 N/A N/A DDS-2
Archive 4586XX 6 N/A N/A -
Archive 4320XX (Python) 6 N/A N/A -
Archive Python 6 N/A N/A -
Certance STD 2400N 6.1 N/A N/A DDS-1

w/compression
Certance STD 240LW 6.1 sp2d N/A N/A DDS-4 Scorpion 40
Certance DAT 72 7.0 N/A N/A -
Compaq TSL-9000 6.2 sp1a N/A N/A 8 slot DDS-3

integrated loader
Compaq TSL-10000 6.2 sp4b N/A N/A 8 slot DDS-4

integrated loader
Compaq SDT-7000 6.2 N/A N/A DDS-2
DEC TLZ07 6.1 sp2d N/A N/A -
Dell PV-100T DDS4 6.3 sp2b N/A N/A -
Dell PV-114T DAT72 7.0 sp7d N/A N/A
Dell PV-100T Dat72 7.0 sp7c N/A N/A
Exabyte 4200C 6 N/A N/A DDS-1

w/compression
Exabyte 4200 6 N/A N/A DDS-1
Hewlett Packard DAT160 SAS 8.5 sp.1 N/A N/A DDS4,DAT72,DAT1

Enterprise 60
Hewlett Packard DAT160 SCSI 8.5 sp.1 N/A N/A DDS-4, DAT72,
Enterprise DAT160
Hewlett Packard DAT 320 8.7 1 N/A USB, SAS

Enterprise
Hewlett Packard DAT160 USB 8.5 sp.1 N/A N/A DDS4, DAT72,
Enterprise DAT160

Indigita iDT-2500 6 N/A N/A 4mm (Not DAT

format though)
Indigita iDT-2700 6 N/A N/A 4mm (Not DAT

format though)
Quantum DAT160 SAS 8.5 sp.1 N/A N/A DDS4,DAT72,DAT1

60
Quantum DAT 72 8.1 sp1c N/A N/A SATA, SCSI
Quantum DAT160 USB 8.5 sp.1 N/A N/A DDS4, DAT 72,
DAT 160
Quantum DAT160 SCSI 8.5 sp.1 N/A N/A DDS4, DAT 72,
DAT 160
Sony SDT-7000 6 N/A N/A DDS-2 SE i/f
Sony SDT-2000 6 N/A N/A DDS-1,

discontinued
Sony TSL-11000 6.2 sp3a N/A N/A DDS-4 in integrated

loader with SE/LVD
i/f
Sony SDT-11000 6.2 N/A N/A DDS-4 with SE/LVD

SCSI i/f
Sony TSL-10000 6.2 sp3a N/A N/A DDS-4 in integrated

loader with SE i/f

discontinued
Sony SDT-10000 6.1 sp2d N/A N/A DDS-4 SE i/f

discontinued
Sony TSL-9000 6.1 N/A N/A DDS-3 in integrated

loader

discontinued
Sony TSL-7000 6.1 N/A N/A DDS-2 in integrated

loader
Sony SDT-9000 6 N/A N/A DDS-2 SE i/f
Tandberg DAT 72 8.1 N/A N/A SCSI and USB
Tandberg DAT 160 8.5 sp1 N/A N/A SCSI and USB
Tandberg DAT 320 8.7 N/A N/A SAS and USB
WangDAT 2600 6 N/A N/A DDS/DC (obsolete)
WangDAT 1300 6 N/A N/A DDS (obsolete)
WangDAT 3100 6 N/A N/A DDS-1
WangDAT 3300DX 6 N/A N/A DDS-2
WangDAT 3800DX 6 N/A N/A id as 3400 but

added in case
WangDAT 3900DX 6 N/A N/A Never happened
WangDAT 3200 6 N/A N/A DDS-1

w/compression

WangDAT 3400DX 6 N/A N/A DDS-2

w/compression
DLT
Cipher L860s 6 N/A N/A 7 slot integrated

loader w/6 GB DLT
Cipher T860s 6 N/A N/A 6 GB DLT
Cipher L826s 6 N/A N/A 7 slot integrated

loader w/2.6 GB
DLT
Cipher T826s 6 N/A N/A 2.6 GB DLT
Compaq DLT 4000 6.2 sp1a N/A N/A -
Compaq VS80 6.3 sp3c N/A N/A -
Compaq 100GB SDLT 6.3 sp3c N/A N/A SuperDLT1
Compaq DLT 8000 6.3 sp3c N/A N/A -
Compaq 160GB SDLT 6.3 sp3c N/A N/A SDLT320
DEC DLT 4500 6 N/A N/A 5 slot loader w/DLT

4000
DEC DLT 2000 6 N/A N/A -

2000
DEC TZ87 6.2 N/A N/A DLT 7000
DEC TZ89 7.0 sp2a N/A N/A DLT 7000
DEC DLT 7000 6.1 N/A N/A indentifies as TZ87

4000

2000
DEC DLT 4000 6 N/A N/A -
Dell PV-114T SDLT320 7.0 sp7d N/A N/A
Dell PV-114T DLT 7.0 sp7d N/A N/A

VS160
Dell PV-110T SDLT320 6.3 sp2b N/A N/A -
Dell PV-110T DLT 6.3 sp3b N/A N/A -

VS160
Dell PV-110T DLT VS80 6.3 sp2b N/A N/A -
Quantum DLT 4500 6 N/A N/A DLT 4000, 5 slot

integrated loader
Quantum Super DLT 220 6.2 sp3c N/A N/A -
Quantum DLT 2500 6 N/A N/A 5 slot integrated

loader

Quantum DLT-S4 8.1 sp2a N/A N/A
Quantum DLT 7000 6.1 N/A N/A -
Quantum SDLT600 7.0 sp5b N/A N/A

loader
Quantum DLT 4000 6 N/A N/A -
Quantum DLT-V4 7.0 sp7c N/A N/A SCSI (TapeWare 7

requires this patch,
SATA (8.1 sp1c))
Quantum DLT 2000 6 N/A N/A -
Quantum VS160 6.3 sp3d N/A N/A -
Quantum DLT 8000 6.1 sp2d N/A N/A -

loader
Quantum Super DLT 320 6.3 sp3a N/A N/A -
Quantum/Benchmar VS80 6.2 sp4b N/A N/A -

k
Quantum/Benchmar Blade 640 6.3 sp3a N/A N/A VS80 Autoloader

k
Quantum/Benchmar VS160 6.3 sp3b N/A N/A Benchmark Version

k
Quantum/Benchmar DLT1 6.2 sp3e N/A N/A BTS100,

k BNCHMRK DLT1,
or BNCHMARK
DLT1
StorageTek 9840 6.2 sp4b N/A N/A -
Tandberg SDLT220 7.0 sp2c N/A N/A
Tandberg DLT-V4 8.1 N/A N/A SCSI, SATA (8.1

sp1c)
Tandberg SDLT600 7.0 sp5b N/A N/A -
Tandberg VS160 6.3 sp3d N/A N/A -
Tandberg DLT 4000 6.2 sp1b N/A N/A -
Tandberg SDLT320 7.0 sp2c N/A N/A
Library/Loader
Acer Altos LTO-2 8.1 sp1c 1 8

Autoloader
Archive Python DAT 6.0 1 4-12 -
BDT ThinStor 6.3 sp3a 1 8 DLT VS, DLT,

SDLT, LTO
BDT ThinStorPlus 8.1 sp1c 1 8

Certance DAT432 Autoloader 7.0 sp3a 1 6 Seagate branded
Certance SuperLoader 3 8.1 sp2b 1 8 -
Certance DAT 240 6.2 sp2a 1 6 240 GB
Certance LDR 6.1 sp2c 1 4 AIT-1
Certance LTO3 Autoloader 7.0 sp5c 1 8 CLL6400
Certance LTO2 Autoloader 7.0 sp5b 1 8 CLL3200
Certance DAT 96 6.2 sp3e 1 6 96 GB
Certance LTO Autoloader 7.0 sp2a 1 8 CLL1600
Cipher TZ Media Changer 6.0 1 7 DLT
Compaq TSL-A300C 6.3 sp3c 1 4 AIT-1
Compaq TSL-7000 6.3 sp3c 1 8 DDS-2
Compaq LIB-81 6.3 sp3c 1 8 AIT-1, AIT-2, AIT-3
Compaq TSL-11000 6.3 sp3c 1 8 DDS-4
Compaq TSL-10000 6.1 sp4b 1 8 DDS-4
Compaq TSL-9000 6.1 sp1a 1 8 DDS-3
DEC DLT 2700 6.0 1 7 -
DEC TZ Media Changer 6.1 1 7 DLT
DEC TL800 7.0 sp2a 1-2 10 DLT
DEC DLT 4500 6.0 1 5 -
DEC DLT 2500 6.0 1 5 -
DEC DLT 4700 6.0 1 7 -
Dell PV-124T 7.0 sp5c 1 16 VS160, LTO-2,

Must apply this
patch (TW7 only): zi
p, LTO3
Dell TL2000 8.1 sp3a 2 24 8.5 sp2 needed for

LTO4, 8.8.03
needed for LTO5
Dell PV-122T 6.3 sp2b 1 8 VS80, SDLT, LTO ,

LTO-2
Dell PV-120T 6.3 sp2b 1 8 DDS4
Dell PV-136T 7.0 sp2a 1-6 60-72 SDLT, LTO, LTO-2 ,

LTO-3
Dell PV-132T 7.0 sp2a 1-2 21-24 SDLT, LTO, LTO-2 ,

LTO-3
Dell PowerVault ML6000 8.1 sp1b 1-18 41-409 8.5 sp2 needed for
LTO4, 8.8.03
needed for LTO5
Dell TL4000 8.1 sp3a 4 48 8.5 sp2 needed for

LTO4, 8.8.03
needed for LTO5

Exabyte 18D 6.1 sp2c 1 18 DLT
Exabyte 110L 6.1 sp4b 1 10 LTO
Exabyte Magnum 1x7 7.0 sp7d 1 7 LTO-2, LTO-3
Exabyte 210 6.0 1 10+1 8mm
Exabyte X200 - 2-10 40-200 Mammoth
Exabyte 215M 6.1 sp4b 1-2 15 Mammoth
Exabyte EXB-10e 6.0 1 10 8mm
Exabyte 220 6.1 sp2c 2 20 8mm
Exabyte 690D 6.2 sp4b 2-6 30-90 DLT
Exabyte PacketLoader 1x10 7.0 sp4c 1 10

1U (VXA-2)
Exabyte PacketLoader 1x10 8.1 sp1a 1 10

1U (VXA-320)
Exabyte X80 - 2-8 40-80 Mammoth
Exabyte EXB-10i 6.0 1 10 8mm
Exabyte 230D 6.2 1-2 30 DLT
Exabyte 440/480 6.1 sp2c 4 40/80 8mm
Exabyte PacketLoader 1x7 6.3 sp3b 1 7 VXA-2, identifies as

EZ17
Exabyte EXB-10h 6.0 1 10 8mm
Exabyte StorageLoader 8.1 sp0 1 8 LTO-2
Exabyte 430 6.1 sp4b 1-4 30 Mammoth2, VXA-2,

430M
Exabyte EXB-218 6.1 sp2c 1-2 18 DDS-2
Exabyte 221L 6.1 sp4b 1-2 21 LTO
Exabyte EZ17 6.1 sp2c 1 7 8mm, VXA-1,

VXA-2
Exabyte PacketLoader 1x10 7.0 sp7c 1 10 VXA-2

2U
Gateway Gateway E-826R 8.1 sp2b 1 8 -

SuperLoader3
Gateway 823 N/A 8
Hewlett Packard 1/8 G2 Tape 8.1 sp3a 1 8 8.5 sp2 needed for
Enterprise Autoloader LTO4, 8.8.03
needed for LTO5,
10.0.00 needed for
LTO6, 10.5.00 for
LTO7
Hewlett Packard MSL2024 Tape 8.1 sp2a 2 24 8.5 sp2 needed for
Enterprise Library LTO4, 8.8.03
needed for LTO5,
10.0.00 needed for
LTO6, 10.5.00 for
LTO7

Hewlett Packard MSL4048 Tape 8.1 sp2a 4 48 8.5 sp2 needed for
needed for LTO5,
10.0.00 needed for
LTO6, 10.5.00 for
LTO7
Hewlett Packard MSL8048 Tape 8.7 4 48 8.8.03 needed for

needed for LTO6,
10.5.00 for LTO7
Hewlett Packard MSL8096 Tape 8.7 4 96 8.8.03 needed for

needed for LTO6,
10.5.00 for LTO7
Hewlett Packard MSL G3 Library 8.7 N/A N/A -

Enterprise Extender Kit
Hewlett Packard MSL6840 Tape 10.5 42 560 10.5.00 for LTO5,

Enterprise Library LTO6, LTO7
Hewlett Packard ESL G3 Tape 10.5 192 12006 10.5.00 for LTO5,
Enterprise Library LTO6, LTO7
IBM TS3310 Tape 8.7 2 35 If encryption is to be

Library used, the library
needs to be set to
use the “application”
controlled
hardware
encryption mode
IBM TS2900 LTO-3 8.7 1 9 SAS
IBM TS2900 LTO-4 8.7 1 9 SAS
IBM Magstar MP 3570 6.2 sp4c 1-2 10 -
IBM ULT 3581-TA 6.1 sp4b 1 7 LTO
IBM ULT 3583-TL 6.1 sp4b 1-6 18-72 LTO
IBM TS3100 8.5 2 24 LTO3, LTO4
IBM Magstar 3590 6.2 sp4c 1 10 -
IBM TS3200 8.5 sp2 4 48 8.8.03 needed for

LTO5
Iomega REV 280 8.5 1 8 Windows

Linux: (2.6 kernel
distos only)
Iomega REV Autoloader 7.0 sp7b 1 10 Windows only.

1000
MediaLogic ADL SLA8 6.2 1-6 26-49 8mm
Overland LoaderXpress (LXL) 6.3 sp3c 1 10 DLT, SuperDLT,

LTO
Overland PowerLoader (LXM) 6.3 sp3c 1-2 15-17 DLT, SuperDLT,

LTO
Overland LibraryXpress (LXB) 6.2 1-16 10-138 DLT
Overland Library Pro 6.2 sp3f 1-18 19-171 AIT only support up
to 16

Overland Neo Series 6.3 sp3c 1-16 24-240 2000 only, DLT,
SDLT, LTO
Qualstar (TLS TLS-6110 6.2sp4c 1 10 DLT

Series)
Qualstar (TLS TLS-2472 6.1sp2c 4 72 4mm

Series)

Series)

Series)

Series)

Series)
Qualstar (TLS TLS-4660 6.3sp1b 4 60 8mm, DLT

Series)

Series)

Series)

Series)

Series)

Series)

Series)
Qualstar (TLS TLS-4210A 6.1sp2c 2 10 8mm

Series)

Series)

Series)

Series)

Series)
Qualstar (TLS TLS-2218A 6.1sp2c 2 36 4mm

Series)
Quantum DLT 4700 6.0 1 7 -
Quantum DLT 4500 6.0 1 5 -
Quantum DLT stor314 6.2 sp5b 1 7 -
Quantum ATL P2000 6.3 sp3c 10 100-198 DLT, LTO
Quantum SuperLoader 3 8.8.03 1 16 LTO-5
Quantum ATL P3000 6.3 sp3c 16 170-326 DLT, LTO

Quantum SuperLoader 3 8.1 sp2b 1 16 DLT VS160,

DLT-V4, SDLT 600,
DLT-S4, LTO-2 HH,
LTO-3, LTO-3 HH,
LTO-4
Quantum SuperLoader 7.0 sp2c 1 16 DLT1, SDLT, LTO
Quantum Scalar i40 8.9 2 25-40 LTO-5
Quantum Scalar i500 8.1 sp1b 1-18 41-409 8.5 sp2 needed for
LTO4, 8.8.03
needed for LTO5
Quantum ATL L500 6.1 sp2c 1-3 14 DLT
Quantum PX500 Series 8.1 sp2a 1-24 32-440 SDLT600, Disaster

Recovery is
untested
Quantum DLT 2500 6.0 1 5 -
Quantum DLT 2700 6.0 1 7 -
Quantum Powerstor L200 6.2 sp5b 1 7 -
Quantum Scalar i80 8.9 5 25-40 LTO-5
Quantum Scalar 24 8.5 sp2 N/A N/A LTO-4 SCSI
Quantum ATL P1000 6.1 sp2c 1-4 30 DLT
Quantum / ADIC Scalar AIT 220 6.1 sp1b 2 20 -
Quantum / ADIC VLS 4mm 6 2 15 DDS-1, DDS-2
Quantum / ADIC FastStor 22 6.2 2 22 DLT
Quantum / ADIC Scalar 218 6.1 2 18 DLT
Quantum / ADIC DAT AutoChanger 6 1 12 -
Quantum / ADIC Scalar 1000 6.3 sp3c 1-12 118-237 AIT, DLT, SDLT,
LTO
Quantum / ADIC FastStor 6.1 1 7 DLT, LTO
Quantum/Benchmar Blade 640 6.3 sp3a 1 8 VS80

k
Sony LIB-D81/AIT-2 7.0 sp7b 1 8 SDX-550V

Turbo
Sony TSL-A300C 6.2 sp2a 1 4 AIT-1
Sony TSL-A500C 6.2 sp2a 1 4 AIT-2
Sony LIB-D81/A5 8.1 sp3a 1 8 AIT-5
Sony TSL-7000 6.0 1 8 DDS-2
Sony LIB-81 6.3 sp3a 1 8 AIT-1, AIT-2, AIT-3
Sony LIB-81/A5 8.1 sp3a 1 8 AIT-5
Sony LIB-162 7.0 sp2a 2 16 AIT-1, AIT-2, AIT-3
Sony LIB-81/A3Ex 8.1 sp1c 1 8 SDX-800V
Sony LIB-162/A4 7.0 sp7c 2 16 AIT-4
Sony LIB-162/A3Ex 8.1 sp1c 2 8 SDX-800V
Sony LIB-D81/A3Ex 8.1 sp1c 1 8 SDX-800V

Sony TSL-10000 6.2 sp3a 1 8 DDS-4
Sony LIB-D81 7.0 sp2a 1 8 AIT-1, AIT-2, AIT-3
Sony TSL-A400C 6.2 sp4b 1 4 AIT-1
Sony LIB-162/A5 8.1 sp3a 2 16 AIT-5
Sony LIB-D81/A4 7.0 sp7c 1 8 AIT-4
Sony TSL-11000 6.2 sp3a 1 8 DDS-4
Sony TSL-9000 6.1 1 8 DDS-3
Spectra Logic Gator 6.3 sp3a 1-32 30-645 20k or 64k, AIT-1,
AIT-2, AIT-3
Spectra Logic Bullfrog 6.3 sp3a 1-4 20-40 10k, AIT-2, AIT-3
Spectra Logic 215 6.1 1 15 Travan
StorageTek L180 6.2 sp4c 1-10 84-174 DLT, SDLT, LTO
StorageTek L20 6.2 sp4a 2 20 DLT, SDLT, LTO
StorageTek 9730 6.2 sp2a 1-4 30 DLT
StorageTek 9714 6.2 1-6 40-100 DLT
StorageTek L40 6.2 sp4a 4 40 DLT, SDLT, LTO
Sun StorageTek SL24 8.1 sp2a 2 24 8.5 sp2 needed for

LTO4, 8.8.03
needed for LTO5
Sun StorageTek SL48 8.1 sp2a 4 48 8.5 sp2 needed for

LTO4, 8.8.03
needed for LTO5
Tandberg StorageLoader 7.0 sp7c 1 8 LTO2 only
Tandberg StorageLibrary T24 8.8.03 2 24 LTO-3, LTO-4,

LTO-5
Tandberg Storageloader 1x8 8.5 sp2 1 8 8.5 sp2 needed for

LTO4, 8.8.03
needed for LTO5
Tandberg StorageLibrary T48 8.8.03 4 48 LTO-3, LTO-4,

LTO-5
Tandberg SDLT Autoloader 7.0 sp5c 1 10 NEC inquiry string
Tandberg TDS-1210 6.2 1-2 10 QIC
Tandberg StorageLoader 8.1 sp3a 1 10

LTO3
Tandberg LTO Autoloader 7.0 sp5c 1 10 NEC inquiry string
Tandberg SuperLoader 7.0 sp2c 1 16 DLT1, SDLT
Tandberg StorageLoader VXA 8.1 sp1a 1 10 VXA-172, VXA-320

(VXA-172/320)
Tandberg StorageLoader 8.1 sp0 1 8 LTO1, LTO2
Tandberg StorageLoader VXA 7.0 sp4c 1 10 VXA-2

(VXA-2)

Tandberg SLR Autoloader 6.2 sp4a 1 8 QIC
WangDAT LD8 6.2 1 8 DDS-3
LTO
Certance Ultrium 3 7.0 sp5c N/A N/A
Certance Ultrium 2 7.0 sp5b N/A N/A
Certance Ultrium 2 HH 7.0 sp5c N/A N/A
Certance Ultrium 6.3 sp1b N/A N/A Ultrium 1
Dell PV-110T LTO-3 7.0 sp7c N/A N/A LTO3
Dell PV-114T LTO-3 7.0 sp7d N/A N/A
Dell PV-110T LTO-3-L 8.1 sp3a N/A N/A LTO3 half-height
Dell PV-114T LTO-2-L 7.0 sp7d N/A N/A
Dell PV-114T LTO-2 7.0 sp7d N/A N/A
Dell PV-110T LTO-2-L 8.1 sp0 N/A N/A
Dell PV-110T LTO-2 6.3 sp3b N/A N/A -
Dell PowerVault 8.1 sp3a N/A N/A SAS (HW

LTO4-120 encryption in 8.5
sp0 only)
Dell PowerVault 8.1 sp3a N/A N/A

LTO3-060
Dell PV-110T LTO 6.3 sp2b N/A N/A LTO1
Exabyte Magnum LTO-2 7.0 sp7c N/A N/A -
Hewlett Packard Ultrium 3280 Tape 8.8.03 N/A N/A LTO5

Enterprise Drive
Hewlett-Packard Ultrium 960 7.0 sp7a N/A N/A Ultrium 3
Hewlett-Packard Ultrium 920 8.1 sp2a N/A N/A SCSI, SAS (8.1
sp3a)
Hewlett Packard Ultrium 1840 Tape 8.5 sp2 1 N/A LTO4

Enterprise Drive
Hewlett Packard Ultrium 1760 Tape 8.5 sp2 1 N/A LTO4

Enterprise Drive
Hewlett Packard Ultrium 3000 Tape 8.8.03 N/A N/A LTO5

Enterprise Drive
Hewlett Packard Ultrium 6250 SAS 10.0.00 N/A N/A LTO-6 HH, SAS
Enterprise
Hewlett Packard HPE StoreEver 10.5.00 N/A N/A LTO-7 HH, SAS
Enterprise Ultrium 15000 SAS
Hewlett Packard HPE StoreEver 10.5.00 N/A N/A LTO-7 HH, FC

Enterprise Ultrium 15000 FC
IBM 00D8924 HH 10.0.01 N/A LTO-6, SAS
IBM ULT 3580-TD6 10.0.01 N/A LTO-6, SAS
IBM ULT 3580-HH6 10.0.01 N/A LTO-6, SAS

IBM IBM 3628N5X HH 9.0.01 N/A N/A LTO 5, SAS

External
IBM ULT 3580-TD2 6.3 sp3b N/A N/A LTO2
IBM IBM 3628L5X HH 9.0.01 N/A N/A LTO 5, SAS

External
IBM ULTRIUM-TD4 8.5 sp1 N/A N/A LTO4
IBM IBM 49Y9898 HH 9.0.01 N/A N/A LTO 5, SAS

Internal
IBM TS2250 8.8.03 N/A N/A LTO-5
IBM ULTRIUM-TD3 7.0 sp7c N/A N/A LTO3
IBM ULT 3580-TD4 8.5 sp1 N/A N/A LTO4
IBM ULT 3580-TD3 7.0 sp7c N/A N/A LTO3
IBM TS2240 LTO4 HH 8.5 sp1 N/A N/A LTO4
IBM ULT 3580 6.2 sp4b N/A N/A LTO1
IBM ULTRIUM-TD2 6.3 sp3b N/A N/A LTO2
IBM ULTRIUM-TD1 6.2 sp4b N/A N/A LTO1
IBM TS2350 8.8.03 N/A N/A LTO-5
IBM TS2230 LTO3 HH 8.5 sp1 N/A N/A LTO3
Quantum LTO-4 8.5 sp.1 N/A N/A SAS
Quantum LTO-2 HH 8.1 sp0 N/A N/A half-height
Quantum LTO-5 8.8.03 N/A N/A LTO5 HH SAS

Standalone
Quantum LTO-3 WORM 8.1 sp2a N/A N/A
Quantum LTO-3 8.1 sp0 N/A N/A
Quantum LTO-2 8.1 sp0 N/A N/A
Quantum LTO-5 8.8.03 N/A N/A LTO5 FH SAS

Standalone
Quantum LTO-3 HH 8.1 sp2a N/A N/A SCSI, SAS, FC
Tandberg LTO-4 FH 8.5 sp1 N/A N/A aka 1640LTO
Tandberg HH LTO-4 8.5 sp2 N/A N/A SCSI, SAS
Tandberg LTO-5 HH 8.8.03 N/A N/A SAS
Tandberg 440LTO 6.3 sp3b N/A N/A IBM ULT3580-TD2
Tandberg Tandberg LTO SAS 10.0.00 N/A N/A LTO-6 HH, SAS
Tandberg TS800 8.5sp2 1 N/A LTO3
Tandberg 820LTO 8.1 sp3a N/A N/A LTO3 HH
Tandberg HH LTO-4 8.5 sp2 N/A N/A SCSI,SAS
Tandberg HH LTO 4 8.5 sp2 N/A N/A SCSI,SAS
Tandberg 840LTO 7.0 sp7c N/A N/A IBM ULT3580-TD3

Tandberg 240LTO 6.2 sp4b N/A N/A IBM ULT3580-TD1
Tandberg 220LTO 8.1 sp1d N/A N/A
Tandberg TS1600 8.5 sp.2 N/A N/A LTO4 HH
Tandberg 420LTO 7.0 sp7c N/A N/A aka TS400
QIC
Archive Anaconda 2750 6.2 sp1b N/A N/A -
Archive Viper 60 6 N/A N/A -
Conner CTMS 3200 6.1 N/A N/A Mini QIC
Emerald 3800 6 N/A N/A -
Emerald 4100 6 N/A N/A -
Exabyte 2501 6 N/A N/A Mini QIC
PeriDAT APD-1326 6.1 N/A N/A Alias for MLR1, now

SLR32
Tandberg TDC 3600 6 N/A N/A -
Tandberg SLR40 6.2 sp3f N/A N/A 20/40 GB
Tandberg SLR140 7.0 sp5b N/A N/A 70/140 GB
Tandberg SLR6/SLR24 6 N/A N/A 12/24 GB
Tandberg TDC 4222 6 N/A N/A 2 GB

w/compression
Tandberg SLR75 6.2 sp3f N/A N/A 38/75 GB, identifies

as SLR60
Tandberg SLR60 6.2 sp3f N/A N/A 30/60 GB
Tandberg SLR7 6.2 N/A N/A -
Tandberg SLR32/MLR1/TDC 6 N/A N/A 16/32 GB

6100
Tandberg SLR100 6.2 sp3c N/A N/A 50/100 GB
Tandberg SLR5 6 N/A N/A 4/8 GB
Tandberg SLR50/MLR3 6.1 N/A N/A 25/50 GB
Wangtek 5150 6 N/A N/A -
Wangtek 9500 DC 6 N/A N/A 5 GB

w/compression

Wangtek 9500es 6 N/A N/A 5 GB
Removable Disk
Dell RD1000 8.1 sp3a N/A N/A Windows, Linux;

USB, SATA
Hewlett Packard RDX 10.5 N/A N/A USB 3.0

Enterprise
IBM RDX 8.1 sp3a N/A N/A -
Imation RDX 9.0.01 N/A N/A SATA, USB 2.0,

USB 3.0
Iomega REV 70 8.1 sp3a N/A N/A Windows:

IDE,SATA,USB
Linux:
IDE,SATA,USB (2.6
kernel distos only)
NetWare: IDE
Iomega REV 35 7.0 sp6a N/A N/A Windows only. IDE,

SCSI, USB
Iomega REV 35 8.1 N/A N/A Windows:

IDE,SCSI,USB
Linux: IDE,SCSI
NetWare: IDE,SCSI
Lenovo Lenovo RDX 8.1 sp3a N/A N/A Internal USB 2.0
Prostor RDX 8.1 sp1c N/A N/A -
Quantum GoVault 8.1 sp1b N/A N/A Windows, Linux (8.1

sp3a); SATA, USB
(Internal, External)
Tandberg RDX Quickstor 8.1 sp3a N/A N/A Windows, Linux;

USB, SATA
SDLT
DumCo XYZ-3000 7.0 sp7b 1 6 None
Travan
AIWA TD-8001 6.2 N/A N/A Travan 4, SCSI
Certance STT20000/NS20 6.2 sp3e N/A N/A IDE, SCSI
Certance Travan 40 6.3 sp1b N/A N/A IDE, STT2401,

STT3401
Certance STT8000/NS8 6.1 N/A N/A IDE, SCSI

Certance Travan 20 USB 6.3 sp3b N/A N/A STT6201
Certance Travan 40 USB 6.3 sp3b N/A N/A STT6401
Compaq TR4 6.3 sp1b N/A N/A IDE
Conner CTT8000 6.1 N/A N/A Travan 4, SCSI
Dell PV-100T Travan40 6.3 sp2b N/A N/A IDE
Exabyte Eagle TR-4 6.1 N/A N/A -
Tandberg NS20 - N/A N/A Travan 5

w/compression,
SCSI
Tandberg TR4 - N/A N/A 4 GB, SCSI
Tandberg NS8 - N/A N/A Travan 4

w/compression,
SCSI
Tecmar NS8 6.1 N/A N/A SCSI
Tecmar NS20 6.2 N/A N/A SCSI
Wangtek TS420 6.1 N/A N/A SCSI
USB
OnStream ADR2.60 6.3 N/A N/A
Other
Enhance Ultrastor RS16 IP-4 8.5 sp1 N/A N/A Disk to Disk Backup
Technology Inc. via VLD
Sony SDZ-100 7.0 sp5b N/A N/A SAIT-

Configuring Encryption and Compression in the Backup Export Tool

Encryption is the process of changing data into a form that cannot be read until it is deciphered, protecting the data from unauthorized access and
use. Company policy normally determines when encryption is required. For example, it may be mandatory for company confidential and financial
data, but not for personal data. Company policy will also define how encryption keys should be generated and managed.
The current version of the Backup Export Tool provides the user with the ability to encrypt the data that is written to the media and fully
implements the Advanced Encryption Standard (AES) for both hardware and software encryption.
Hardware encryption is supported on some backup devices, such as HP LTO-4 tape drives. It is faster than software encryption and
requires no processing on the backup server. The encryption strength is determined by the backup device. HP LTO-4 tape drives always
provide strong AES-256 encryption. This feature can be managed by a backup application that supports hardware encryption, such as
the Backup Export Tool.
Software encryption uses the encryption algorithms available within the Backup Export Tool. The user selects an encryption strength:
Low 56 bit, Medium 128-bit or High 256-bit. Each encryption key size causes the algorithm to behave slightly differently. Increasing
software encryption strength makes the data more secure, but requires more processing power.
If your business requires you to use encryption, the Backup Export Tool allows you to set the required encryption types and levels.
Cryptographic Algorithms
Cryptographic algorithms are the basic components of cryptographic applications. It is important to understand that as you increase the
complexity of the encryption the information gets closer to impossible to read and the load on your machine, for software-based encryption, will
increase.
Software
Three cryptographic algorithms are provided. These three settings provide three levels of resistance which require progressively more CPU time
to convert the same amount of data. The three options are for the software encryption mode only.
Low – DES 56-bit
Medium – AES 128-bit
High – AES 256-bit
Hardware
The cryptographic algorithm provided by hardware devices that provide this feature is not under the Backup Export Tool control. The hardware
provides configuration and operating parameters via a special encryption command. The device driver adjusts its crypto session settings from this
input. Hardware encryption is an on/off feature, you do not have the ability to adjust the encryption level through the Backup Export Tool interface
. By default the Backup Export Tool attempts to use the highest encryption algorithm supported on the device, if the device supports multiple
algorithms. If the device does not support encryption, the user will be prompted with an alert telling them that the device cannot be used since it
does not support hardware encryption.
Passphrase
The passphrase is a series of characters that must be provided by the user for input to the cryptographic key generation process.
Passphrases must be no less than eight logical characters. They may be created by the user or randomly generated by a separate
application.
If created by the user, the passphrase should be difficult to guess and should contain a mix of lowercase/uppercase letters, digits and
special characters.
The passphrase is one of the components the Backup Export Tool uses to generate the encryption key. A longer or random passphrase
will increase the strength of the encryption key even more.
To aid the user in remembering the passphrase, the user may enter a hint message. The use of this field is optional and provided to the
user as prompt for remembering the passphrase.
If a backup job spans multiple media, the same passphrase will be used for all media in the set.
Passphrases for the media are stored in the the Backup Export Tool catalog. This means the user is able to read and append to the encrypted
media without being prompted for a passphrase as long as it is being accessed by the instance of the Backup Export Tool that first encrypted it.
Once a media is deleted or exported from the Backup Export Tool catalog the passphrase is also deleted. There are two instances when the user
needs to know the passphrase:
When importing the media to another machine or another instance of the Backup Export Tool
During disaster recovery
Important

Managing the passphrase is a critical component of any encryption system. Data may be stored for months or years, so passphrases
must be archived securely. The user should keep a record or backup of encryption passphrases and store them in a secure place
separate from the computer running the Backup Export Tool. If the user is unable to supply the passphrase when requested to do so,
neither the user nor the Backup Export Tool Support can access the encrypted data.
Encryption Options
Encryption is enabled on the job’s Encryption page.
Option Description
Off Both hardware and software encryption are disabled.
Automatic This selection uses hardware encryption if it is available from the

device; otherwise, software encryption is used.
Software Software encryption is used. When Software is selected, the user

can choose the strength of software encryption.
Hardware Hardware encryption is used if the device supports it. If it does not
support encryption and this option is selected, the user is prompted
with an alert stating that the device cannot be used since it does not
support hardware encryption.
Software Strength Options for the software encryption strength are listed below as three
selections, low, medium and high. Low is the easiest method to
decipher by outside methods, High is the hardest method to decipher
by outside methods. As you progress from low to high, the encryption
algorithm requires more CPU computations for each block of data to
be encrypted, which may slow down the data stream to the device
and increase CPU loading on the Media Server.
Encryption passphrase / Verify Passphrase The user-supplied portion of the encryption key. The Backup Export
Tool uses this value, along with other information it generates, to
calculate an encryption key for the media. The passphrase must be
entered twice to minimize the change of making a mistake while
typing.
Hint The text entered here is added to the log file of an import job if the
media later needs to be imported and the incorrect passphrase is
supplied. Use this field to create a reminder of the passphrase as the
Backup Export Tool cannot recover a lost passphrase.
Key Management
The Backup Export Tool has adopted a very simple key management strategy. A media is encrypted originally by configuring the job that creates
it according to the parameters described above. From that point on, the media is known to the catalog. As long as the media is known, restore
jobs may use the media without entering the passphrase again. If a media is unknown—because it was deleted from the catalog or because it
came from a different catalog—you must import the media to make it known to the catalog again. The import process required you to supply the
passphrase to complete the import. If the passphrase supplied does not match that used to encrypt the media, then the hint supplied at
encryption time is shown in the job log so you can try the import again.
When media is encrypted the media is depicted on the Jobs and Media view with a lock on it. The Platinum colored lock indicates hardware, and
the gold lock indicates software encryption. The Media details window shows the type of encryption used.
Compression
Software encryption disables hardware compression, although you will still be able to select Software compression.
If the backup device has hardware compression then performance is better if only hardware compression is used, and that there is little to no
benefit of having both enabled. Enabling software compression in this circumstance reduces performance.
If you select Hardware encryption, Barracuda recommends that Enable hardware compression is also selected. Hardware encryption and
hardware compression can be used on devices, such as the HP LTO-4 tape drive, without any loss of backup speed.


You can define retention policies which allow you to balance your data protection and historical retention needs with the economic realities of
media and management costs. To determine the type of backup job to create, answer the following questions:
How many days of data can you afford to lose?

How large will a full backup job be?
How much does your data change on a day-to-day basis?
How many media does your budget allow?
How much data can the backup media hold?
If you have a library, how many tapes does it hold?
Are there times when your tape drive will be unavailable?
Will the amount of traffic on your network require backup jobs to be scheduled to run during non-peak periods?
Are there certain days of the week when running lengthy jobs will interfere with other uses of your network?
In this Section
Scheduling Concepts
Media Rotation Types
Schedule Settings
Mode Settings
Media Settings
Running Jobs in Rotation

Scheduling Concepts
Typically it is not practical from either a time or a media perspective to create a full backup every day. The solution involves running different
types of jobs (full, incremental, differential, or copy) on predefined schedule intervals using predefined numbers of media sets that are reused
over time. The process of reusing media is referred to as media rotation. The media rotation type determines how and when each media set is
used, how long it is retained once it contains data, and the granularity of your backup history.
Media Sets
The Backup Export Tool organizes media into sets based on the rotation type and schedule interval. Whether the job requires several or only one
physical media to complete, they are identified in the Backup Export Tool catalog as a set. When more than one physical media is required for a
job, the Backup Export Tool creates a unique name for each media in the set.
When planning scheduled backup jobs, it is important to know whether one or several physical media are required to complete a backup job. This
can usually be estimated by comparing the size of the backup selection to the capacity of the selected media. If you do not want the Backup
Export Tool to use more than one media for a backup job, then you must select fewer files to back up.
The term media can be used to refer to both physical media, like an LTO tape, or to the catalog object the Backup Export Tool uses to
keep track of file versions.
Intervals
Job schedules are defined using the Intervals Daily, Weekly, Monthly, and Yearly. Intervals are used to define which days a job runs, the type
of backup (full, incremental, differential, or copy), and how many sets of media are dedicated to the interval. The size of an interval refers to the
amount of time between interval runs.
When the Run repeatedly schedule type is selected, the job Configuration page displays an additional section, Interval settings, that controls
the schedule parameters. Each interval type is listed along with a textual description of its current setting. To customize interval settings, click on
the interval button. Most schedules are defined in terms of the following intervals:
Daily – Run on sequential weekdays.

Weekly – Run once per week on the day specified by the user, for example, Friday.
Monthly – Run once per month on a day specified by the user such as the first day, the last day, the first Monday, and others. You can
also specify how many months should elapse between monthlies. Setting the monthly interval to every 3 months creates a backup every
quarter.
Yearly – Tun once per year on a specified day of the year. By increasing the interval you can also schedule a job to run once every so
many years.
There are also Hourly and Minute intervals that are less commonly used. The concepts behind using these are similar to
those of the intervals discussed above.
For all intervals there is a setting that controls the number of sets. This setting determines how many sets of that backup
interval are created before the Backup Export Tool goes back and overwrites the first. For example, if your schedule starts in
January and calls for three monthly sets, you will have a set for January, a set for February, and a set for March. In April, the
job will overwrite the set from January.
When configuring a rotation the Calendar view displays the schedule graphically. The interval type for each day is displayed in
the calendar. Click on a day in the calendar to display the type of backup, the write mode, and the name of the media that is to
used on that day.
Right-click on a day in the calendar to change the schedule interval for that day. This is useful to prevent a job from running on a given
day. This is helpful for times when you know the job will not complete because you are unable to supply the right media for the job, as
in the case of holidays.
Click the name of a day in the calendar view heading to enable or disable jobs from running on specified days of the week. For
example, if you want daily backups on Saturdays.
Implications of Intervals for Restoring Data
Intervals also define the granularity of the data you can restore. Rotations are set up to capture more granularity in the recent past and less
granularity as data gets older. Larger intervals, like Yearly and Monthly, produce lower granularity data history. Smaller intervals, like Daily,

produce higher granularity history. Take, for example, a rotation with three full monthly backup sets on the last day of each month, four full weekly
backup sets created on each Friday, and four incremental daily backup sets created Monday through Thursday. Now suppose you have a critical
file that changes daily. On Wednesday, you are asked to retrieve the file as of a specific date. With this rotation you can roll back to the Monday
and Tuesday versions of the file in the current week and the Wednesday, Thursday, and Friday versions of the file in the previous week. Beyond
that, you will only have the versions of the file as they existed on Friday for the previous four weeks previous to the current week. And beyond
that you will only have the versions of the file that existed on the last day of the month for the previous three months.
The catalog keeps track of the files and versions that have been backed up so you do not have to remember what media they are on. This
knowledge makes the restoration process very simple. You only need to specify the files you want restored and the Backup Export Tool prompts
you for the media it needs to restore the files. Full reconstruction of data may require multiple media sets. For example, to reconstruct the data for
a Wednesday from a GFS 20 set rotation type, you will require the full backup media set from the previous end of week and all of the incremental
media sets from that week (that is, Mondays, Tuesdays and Wednesdays). In some circumstances, the preceding full backup media set will be a
monthly or yearly job and not a weekly job. As long as none of these media sets are overwritten, full data recovery is possible.
When a full backup media set is reused, any incremental or differential backups relative to that full backup are no longer usable for full
system restores. However, files on those media are still recoverable.
Yearly backups only provide you with access to files present on your computer or network on that one day each year. No copy exists
for files that were created after the oldest yearly backup and then deleted before the most recent yearly backup. It is the responsibility
of the user to manage the retention of media containing critical business data.

Media Rotation Types

The Backup Export Tool provides several default media rotation types. These type can be used as is or as examples for creating custom
rotations.
Each media set may contain more than one tape or media. Several factors determine how much media you will need: the type of
backup being performed (for example full, differential, incremental), the amount of data to be backed up during a full backup, and the
media's storage capacity. If the total size of a full backup is larger than the capacity of the tape, additional tapes are required. Your
historical usage is the best guide to determining how many tapes these jobs will require.
No Rotation Type
When no rotation type is selected. the user may schedule the days to run on but the Backup Export Tool does not manage the media. The user
must supply the desired tapes each time the job runs and manage the reuse of older media.
Fixed Rotation Types
Media sets are named for the interval that has been run, and follow the form [Interval ] Set [ number ]
Fixed by day of week – For example, a daily media set is 1st Monday
Fixed by week of month – For example, a weekly media set is 1st Week of the Month
Fixed by day of month – For example, a monthly media set is 1st Month
An example of yearly media set is Yearly 1
Fixed by day of year – For example, a yearly media set is First Day of Year 1
Daily Append
This is a special rotation designed for users with a single backup device. It is the only rotation that appends data to media. It performs a full
backup on the specified day followed by daily incrementals on the remaining weekdays. At the end of the rotation, the user must insert new
media for the job to use. This rotation assumes that an entire week of backups will fit on a single media.
Simple and GFS Rotation Types
These rotation types specify combinations of full and incremental backups that efficiently use a specific number of media sets. The main
difference between the Simple and the GFS rotations are that only the GFS rotations specify Yearly backups.
Custom
Select this option to create your own rotation.
You can select a rotation similar to the desired rotation prior to selecting the custom rotation type and the values from the previously
selected rotation will remain as a starting place. The Calendar view is very helpful when creating custom rotations.
Rotation Types Compared
The Backup Export Tool provides a variety of media rotation types to select from, or you can define your own media rotation.
The following table compares the historical backups and full data recovery capabilities of each of the rotation types provided in the Backup Export
Tool.
Rotation Type # of Sets Yearly Sets Monthly Sets Weekly Sets Daily Sets
Simple 4 1 full 1 full 2 full
Simple 6 2 full 1 full 3 full
Simple 10 3 full 3 full 4 incremental

Daily Append N (def. 4) N full 4 incremental

appends
GFS 20 2 full 6 full 6 full 6 incremental
GFS 25 2 full 7 full 8 full 8 incremental
GFS 30 2 full 8 full 8 fill 12 incremental

Schedule Settings
The Schedule Settings box contains several settings that control when jobs are run and how the jobs use media.
Schedule Type
This setting is the first step in choosing when the job is to run. Once scheduled, the Backup Export Tool service ensures the job is started. If one
or more job runs are missed because the service is not running at the scheduled time, the service determines the backup mode with the largest
interval setting (Daily, Weekly, Monthly, Yearly) that was missed, and runs it.
Type Description
Not scheduled The job is run manually by the user when desired.
Run on selected days The job runs only on a selected day (or days) at a specified time.
When this option is selected an additional setting, Scheduled Dates,
appears.
Run repeatedly The job runs on a regular interval. Use this setting to set up a job with
media rotation. When this option is selected an additional set of
options, Interval Settings, appear.
Start Time
This setting is only visible for jobs that are to run on a schedule. It specifies the time of day that the job should start. For jobs that are scheduled
to run more than once, all runs happen at the same time of day.
Rotation Type and Sets
This setting is only available when the job is scheduled to run repeatedly. The Rotation type and Sets controls allow you to specify a set of
preconfigured rotations. The Custom Rotation type is a special case. It unlocks the user interface to allow the user to configure his own rotation.
Type of Fixed Rotation
This setting is only available when creating a custom rotation.
Scheduled Dates
This setting is only visible when the schedule type is set to run on selected days. It consists of a list of selected days to run the job. To add days
to or remove days from the schedule, click Calendar to open the schedule calendar. To schedule the job to run on a day, right-click on the day in
the calendar, and then click Daily. To unschedule a day, right-click on it, and then click None.
Interval Settings
This setting is only visible when the job is scheduled to be run repeatedly. It contains controls for specifying which types of jobs (full, incremental,
or differential) are to be run on which intervals and the number of media sets that are to be used. Click Calendar to view of the schedule. The
calendar displays when daily, weekly, monthly and yearly backups are to run. Clicking a day displays a message along the bottom of the dialog
explaining the type of job that is to be run, the name of the media that is to be created, and whether the media is to be appended to or
overwritten. To override the schedule on an individual day, right-click on the day, and then select the new backup type or deselect the day to stop
the backup on that day.
It is a good idea to deselect holidays from you schedule if you do not have a tape library or if no one will be available to put the correct
media into the device.

Mode Settings
The Mode box contains several settings that control:
Type of backup
How automatic verify is performed
How to treat used media
What to do when a file does not fit on the current media.
Many of these settings are set automatically when a schedule rotation is in effect. When a rotation controls these settings, they are disabled in the
Administrator.
Backup Mode
The Backup Export Tool supports the backup modes listed below. For scheduled automatic rotation jobs, the Backup Export Tool uses the
backup mode for each backup set as indicated on the Schedule page; for unscheduled or manual jobs, the Backup Export Tool uses the settings
set by the user.
Setting Description
Full This setting instructs the Backup Export Tool to back up all selected
files.
Differential This setting instructs the Backup Export Tool to back up all selected
files that have changed since the last full backup.
Incremental This setting instructs the Backup Export Tool to back up all selected
files that have changed since the last full, differential, or incremental
backup.
Copy This setting instructs the Backup Export Tool to back up all selected
files, but it has no effect on any future scheduled job. Use this option
when you wish to make a record of files or systems at a particular
time, but do not wish to disrupt the normal backup schedule.
Incremental jobs are the shortest and smallest jobs to run, but they present some issues related to full data recovery. The difference
between an incremental and a differential backup is important: incremental backup jobs back up only files that have changed since the
last full, differential, or incremental backup, while differential backup jobs back up all files changed since the last full backup. If
incremental backup media sets are overwritten or recycled before another full backup is performed, this can create a gap in available
data if you need to recover files from the overwritten media.
Exclusive use of incremental backup jobs to ensure full data recovery after a disaster is not recommended, unless you are using a
schedule that retains one full backup and all subsequent incremental backups before overwriting any media. However, to ensure
successful data recovery with incremental jobs, follow these guidelines:
Have at least as many incremental media as there are days between full or differential backup jobs. For example, if you run full
backup jobs every five days, have at least four incremental media; if you run full backup jobs every seven days, have at least
six incremental media.
Never recycle incremental media between differential or full backup jobs. If you run more than one incremental job in a row, be
certain to not recycle any of the media used during this string of incremental jobs.
Auto Verify Mode
After the Backup Export Tool backs up a set of data, it can verify that the data was backed up correctly. The Backup Export Tool reads the files
from the media and performs the selected verification type. If any discrepancies between the two files are found, the file is reported in the job log.
Verification Type Description

Full Verify This setting instructs the Backup Export Tool to compare every
selected file stored on the media with the original file from the PC
desktop or file or application server. If the file has changed since it
was backed up, the full verify process reports that the file on the
media does not match the file on disk. This does not mean that the
backup was unsuccessful.
Quick Verify This setting instructs the Backup Export Tool to be certain that every
file backed up onto the media is in readable condition. It does not
verify that the data matches the file, only that the data stored on the
media can be read.
No Verify This setting instructs the Backup Export Tool to skip the verification
step. It is not recommended.
Verifying that data has been correctly written to the media is an essential part of a comprehensive backup program. Also, verifying the
files ensures that the media and the media drive are working correctly.
Write Mode
For automatic rotation jobs, the Backup Export Tool overwrites all media. For other jobs, the Backup Export Tool uses the write mode settings set
by the user. This mode determines whether the old data on the media is overwritten with new data or whether the new data is appended to the
end of the old data. When media is overwritten, all of the data previously stored on it is lost. Appending data preserves the old data.
Setting Description
Append to all media This setting instructs the Backup Export Tool to append all data to
the end of the media. No data is overwritten. Select this setting for
permanent storage.
Append to first media, overwrite others Append to first media, overwrite others.
Overwrite all media This setting instructs the Backup Export Tool to overwrite all media.
All data on media that is overwritten is lost. Use this option for media
that are going to be recycled.
Split File
The Split File mode determines how the Backup Export Tool handles a file if the file is too large to fit on the current media. Select this option to
instruct the Backup Export Tool to split a file across two media if it will not fit on the current backup media. If this option is not selected then files
that do not fit on the media are restarted on the next media.
If you use the split file option, files that span two media require both media for restore. If one is lost then the file cannot be recovered. Fi
les protected with split file mode cannot be restored during Disaster Recovery. They must be restored after the DR process has
completed.

Media Settings
Media to Use
Select the folder where a job can look for existing media to reuse. Note that the default folder is the current Job folder. To use media from another
folder, click Add to open a catalog browser and navigate to the desired folder.
Auto Format Mode
Before data can be written to media, the media must be formatted. When media is formatted, any data on it is lost and all record of the media is
removed from the catalog.
Mode Description
No auto format Instructs the Backup Export Tool to send an alert to the alert window
if it encounters media that needs to be formatted (either blank or
unrecognized media). While waiting for a user reply, the Backup
Export Tool scans the network for devices with the media it was
expecting.
Auto format blank media only Instructs the Backup Export Tool to automatically format all new or
blank media. However, if the Backup Export Tool encounters
unrecognized media, it sends an alert to the alert window and then
scans the network for the media it was expecting. This setting can
help prevent data from being accidentally destroyed by formatting,
while not needlessly querying the user before formatting a blank
media.
Auto format all media Instructs the Backup Export Tool to automatically format all of the
media inserted into the tape drive which require formatting. With this
setting selected, the Backup Export Tool automatically formats all
new or blank media and all unrecognized media.
New Media Location
Specifies the folder in which the Backup Export Tool stores any new media created while the job is run. By default, the Backup Export Tool stores
media under the backup job to ensure the media is not used by another backup job. To change the default, click Browse and select the folder
from the Browse dialog box.
When the Backup Export Tool runs any scheduled automatic rotation job, it automatically creates media folders for the job. The folders are
organized by the name of the job and the various rotation sets in that job.
Move Media to New Media Location on Overwrite
Setting this check box moves media from the Media to be used folder to the New media location folder when it is used.
If this option is turned off, it is possible for a job to exhaust its set of available media and stop running.
Rename Media to New Media
Selecting this check box renames any existing media that is overwritten to the name that would have been used had the media been freshly
formatted. When this check box is cleared, already formatted media retains the name that it was given when it was previously used by this job.
New Media Name
Enter the name that the Backup Export Tool gives to any new media it creates while running a job. For scheduled automatic rotation jobs, the
Backup Export Tool automatically updates this setting to match the media’s place in the rotation schedule and this setting has no effect.
For manual rotation and unscheduled jobs, the Backup Export Tool assigns the name in this field to any new media that it creates. It also assigns
this name for automatic rotation jobs that are "forced" to run. If the job creates more than one media, the job uses this setting as a template to
create a unique media name from this setting.

Running Jobs in Rotation

The info bar displays the Current rotation set and the Next rotation set in the Rotation Details section of the info bar. Before the job is run the
first time, both fields have the same value. Once the job runs successfully, the Current rotation set field displays the media that has just been
used and the Next rotation set field displays the media that is to be used next.
Initial Run
The initial run of a rotation job uses the largest schedule interval in the rotation. For example, suppose a job is configured to begin a GFS 20
rotation on Thursday, October 28th, 2010. Even though a Thursday in the middle of a month would normally be classified as a Daily backup, the
first time the job is run, the Backup Export Tool performs a Yearly backup.
Missed Jobs
If, for some reason, a run of the job is missed, for example, because the domain server was offline at the scheduled run time, the scheduler
determines the largest interval missed and runs it automatically a few minutes after the Backup Export Tool starts up again.
Failed Jobs
If a job fails, the Backup Export Tool does not automatically run it again. However, you can manually rerun the job by clicking Run in the
command bar.
Pausing and Continuing a Schedule
You can stop a scheduled job from running for a period of time by clicking Pause Schedule in the command bar. To turn the scheduled job back
on, click Continue Schedule in the command bar. As with initial and missed jobs, the scheduler starts again with the largest schedule interval
that was skipped.
Forcing a Run
At times it may be desirable to start a job before its regularly scheduled time. To run the next scheduled interval immediately, click Run next
schedule in the command bar. When its originally scheduled time arrives, the job is not run again. Forcing a job to run ahead of its next
scheduled time does not affect the schedule of subsequent runs, which resume their normal schedule.

Managing Devices
The Backup Export Tool recognizes any installed device that is part of the Backup Export Tool management domain and displays them on the De
vices view. You can use the Devices view to perform operations on any physical or virtual device.
In this Section
Device Commands
Device Properties
Sharing Storage Devices on a SAN
Working with Tape Libraries

Device Commands
There are several physical operations that can be performed on a selected device. Some of these operations affect the device itself, while others
affect the current media in the device.
Not all operations are available on all devices. For example, an optical device does not support the Rewind command. Check your
hardware documentation to determine which of the following commands are supported by your device. Only supported commands
appear on the context menu and the command bar.
Identify
Use this command to get the name of the media currently loaded in the device. The Backup Export Tool attempts to identify the tape or other
media that is currently loaded in the device. If the Backup Export Tool cannot identify the media, it reads the media header, a process that may
take up to several minutes. The name of the media appears on the log file for the media job and in the Media column of the device list.
Import
This command allows you to use data on media that was created in another Backup Export Tool management domain. To use media that was
not created in the current catalog, you must import that media into the current catalog.
You might import media in one the following situations:
To use media created by an earlier version of the Backup Export Tool.

To use media created in a different the Backup Export Tool management domain.
To use media accidentally deleted from the catalog.
When you select the Import command a property page opens and prompts you for the media password and the encryption passphrase. The
media password is only applicable to media created with older version of the Backup Export Tool and can usually be left empty.
An encryption passphrase is only required for encrypted media. If the supplied passphrase is not correct, the job log presents you with the hint
supplied at the time of the media's creation.
Format
Use this command to format media currently loaded in the selected device.
When you format new media, the Backup Export Tool opens the Format Media dialog box. Use this dialog box to name the media and select a
media folder in which to store the media. The Backup Export Tool formats the media currently loaded in the device you select. If you select a
library, select the storage slot that holds the media you want to use. When you format media, you can also set your choice of encryption levels.
Any backup job that uses media pre formatted with encryption must specify the same encryption parameters.
The Backup Export Tool is designed to manage your media for you. This command should only be used by knowledgeable users and
only after determining that the built-in media management does not produce the desired results.
Erase
This command erases the media currently loaded in the selected device. It has the following options:
Command Description
Quick Erase Erases the first block and then writes an end of data marker to that
first block. The other blocks of the tape are not erased, but when that
tape is read, the Backup Export Tool treats it as if it were blank
because it encounters the end of data marker in the first block.
Secure Erase Erases every block on the tape. This operation can be very time
consuming, lasting several hours. However, it will physically erase
every block on the tape. If you want to destroy sensitive data, use
this command.
Some devices support both options; some support only one of the two erase options. Only options supported by the selected device will be
available.
Retension Media

Occasionally when a tape is repeatedly fast-forwarded and rewound for only short distances, tension differences develop in the tape that cause
the tape drive to falsely believe it has reached the end or beginning of the tape. You can use this command fast-forwards the tape to the end of
the tape and then rewinds it to the beginning. This command can be useful in some circumstances. By retensioning the tape, you can sometimes
make an otherwise unusable tape operational again.
If you need to retension tapes regularly to use them, consider servicing your tape drive or replacing your tapes.
Eject
You can use this command to eject media from the selected device or eject the media magazines from the selected library. Some libraries do not
support ejecting media magazines using this command.
Restore Catalog
The Restore Catalog command provides a quick method of restoring your current catalog–for example in case it has been corrupted. For
example, you might use this command if the Backup Export Tool Domain Server has crashed. Use this command only when your current set of
media is intact.
The Restore Catalog command differs significantly from the Import Media command in that it replaces the current catalog with the last known
good catalog on that media. The Import Media command, on the other hand, does not replace the current catalog; it only adds additional data to
it.
The advantage of the Restore Catalog command is that it provides a quick and easy way to replace a lost or corrupted the Backup Export Tool c
atalog. You could use the Import Media command to restore a corrupted catalog, but this process requires importing all of your media rather than
simply reading the media containing the catalog.
It's a good idea to make a regular backup of the Backup Export Tool catalog. It is automatically included in any full backup of the
Backup Domain.
All information in the current Backup Export Tool catalog will be lost when you use the Restore Catalog command. This command
does not append data to the current catalog; it replaces the current catalog with the last known good catalog on that media.
You will be prompted stop and restart the service. Use the Backup Export Tool Service Control Manager to start and stop the Backup
Export Tool service.
Clean Device
The Clean Device command will run the backup device through a cleaning cycle.
This command is supported only by libraries. If a device in a library provides notification that it needs cleaning and the library has a cleaning
cartridge available, a cleaning cycle will be performed automatically at the start of a backup job. If you are using a device that is not a library, you
must manually clean the device at the manufacturer’s suggested intervals.
To clean a device in a library, highlight the device and select Clean Device from the Command bar. The Backup Export Tool checks to see if
one of the slots holds a cleaning cartridge. If it does, the cleaning cycle will be performed in the background; if not, an error message is shown.
If the Clean Device command is missing, it is not available for your backup device. In this case, a cleaning cycle can often be performed by
manually inserting a cleaning cartridge into the backup device.
Start, Stop, and Rescan
Sometimes you will need to restart a device that has, for some reason, failed to initialize properly. A device may have stopped for any number of
reasons, such as a power failure or a connecting cable malfunction. Virtual devices on a network appear disabled if the network connection has
failed.
When a device is not initialized, it appears with a yellow warning icon. Some devices may take some time to initialize, during which the warning
icon continues to display. If a device shows the warning icon after it is initialized, press F5 to refresh the device display.
If you do not see a device that you expect to see connected to a machine, select the Device folder under the machine and click the Rescan for
New Devices command.
If there is some other problem with the device or the controller, the warning icon continues to display. You must identify and correct the problem
yourself. Then you must restart both the Backup Export Tool and the Backup Export Tool service. When the Backup Export Tool restarts, it
initializes the device driver again. Check the Devices view to see that the devices are now properly working and that they no longer display the
warning icon. Any duplicate or old devices that are offline can be deleted from the Catalog view.

Device Properties
System > Software Downloads page in the Barracuda Backup web interface.
When you select a specific device in the Devices view and click Properties, you can view the device status, configure settings, and review
diagnostic information.
Status
The Status page displays the current status information for the selected device. For example, it shows the current operation, if any, being
performed on the device. It also shows the last time a write and read was done on the device.
The Backup Export Tool tracks the contents of devices and libraries while it is running. However, there may be times when someone
changes media in a device or a library when the Backup Export Tool is not running. The "Probably" qualification on element status
indicates that the Backup Export Tool has restarted and is operating under its previous understanding of the current element status but
that the understanding may be incorrect. When "Probably" appears before an element status, the element's actual status is determined
the next time the element is used.
Status Description
Valid The slot is known to hold media that is in the current catalog.
Probably Valid The slot held valid media previously. The Backup Export Tool verifies
that the media is valid before using it. When you exit and restart the
Backup Export Tool, media marked Valid is reset to Probably Valid.
Invalid The slot holds media that is definitely not in the current catalog.
Probably Invalid The slot holds media that may not be in the current catalog. When
you exit and restart the Backup Export Tool, media marked Invalid is
reset to Probably Invalid.
Empty The slot is either known to be empty or a user changed its status to
Empty.
Probably Empty The slot was empty previously. When you exit and restart the Backup
Export Tool, slots marked Empty are reset to Probably Empty.
Unknown The status of the slot is not known, usually because it has not been
used yet.
Cleaning Tape A user marked the slot as holding a cleaning cartridge. The number
of remaining cleaning cycles also appears. The Backup Export Tool d
oes not verify that a cleaning cartridge was, in fact, inserted into this
slot.
Probably Cleaning Tape The slot previously contained a cleaning tape. When you exit and
restart the Backup Export Tool, slots marked Cleaning Tape are reset
to Probably Cleaning Tape.
Reserved The slot was disabled by a user. The Backup Export Tool ignores it
during any job. You can only change the status of a reserved slot.
The Backup Export Tool changes the status of all other slots during
normal operations.
Configuration
You can set the size of the I/O buffer to be used for this device. Usually, you do not need to change the default. However, for some devices, you
may be able to increase performance by adjusting the size of the I/O buffer.
Diagnostics
The Diagnostics page displays device diagnostic information including information about the driver, the inquiry information, device statistics, and
buffer statistics. Often this information can assist in troubleshooting problems. The diagnostics can be saved to a file or emailed directly from the
diagnostic screen.

Sharing Storage Devices on a SAN
Backup jobs automatically select devices to use based on their availability (whether or not they are in use). In a SAN environment, the Backup
Export Tool automatically recognizes that a single backup device attached to a SAN may be accessible from two or more servers, and treats the
device as a single device.
All machines that need access to a SAN server must be included in the same Backup Export Tool management domain.

Working with Tape Libraries
Tape libraries automate tape media handling which, in conjunction with the Backup Export Tool backup schedules, allows hands-off backup
operations. A tape library contains one or more tape drives, some number of storage slots for tape media, and, in some cases, import/export slots
to add or remove media from the library.
The Backup Export Tool The Backup Export Tool Server Backup tape library support includes managing media using barcodes, using the
on-board memory in some tape cartridges, such as Ultrium Memory in Cartridge (MIC), and user-configurable tape media load ports (mail slots).
Always manage your tape media from the Backup Export Tool interface. Your tape library may provide a front panel that allows you to
carry out various media management tasks but if you use this for media operations the Backup Export Tool catalog does not have the
up-to-date media location information. For this reason, front panel media operations require time-consuming inventory processes to
update the catalog.
If your library supports multiple tape devices and you want to use a specific device, you must select that device to use it. If you select
the library, the Backup Export Tool uses the first available device in the library.
Installation and Configuration
If the tape library is installed correctly, the Backup Export Tool automatically detects the tape library. When detected, the tape library is added as
an available device to the Backup Export Tool catalog.
Once you have installed the Backup Export Tool, expand the Devices view to locate the tape library. Note how the components of the tape library
are displayed so that you can see how many devices (tape drives), import-export Slots (mail slots), and storage slots are associated with the
library.
Devices – The tape drives in a tape library are viewed and managed in the same way as stand-alone tape drives.
Storage Slots – The Storage Slots folder displays the number of available slots. Each slot may contain blank (new) media, media
containing the Backup Export Tool data, or media containing unknown (non-Backup Export Tool) data. The Backup Export Tool inventori
es the media in the slots and displays the information about the media and its status in the view. This allows you to view all kinds of
media, not just the media used by the Backup Export Tool, but you cannot select non-Backup Export Tool media for a backup or restore
job.
It can take a long time to inventory the tape media in a tape library, which is why the Backup Export Tool usually performs a "light
inventory" rather than running an identify job on all the slots in a loader. See the Inventory Process section below for more information.
Additional media slot configuration is accessed via the Element Status dialog for that slot, which is accessed by a right click on the desired
slot. For example, you can use this to disable slots (using the 'Reserve' option) and identify a cleaning cartridge.
Import/Export Slots – Some library devices provide special import/export mail slots an operator uses to enter or eject media to or from
the device without removing the whole media repository or magazine. Depending on the device, more than one import/export slot can be
provided. In case of a single mail slot, media are inserted one by one, while in case of multiple mail slots, a particular number of slots can
be used in one enter/eject operation.
Barcodes and Memory in Cartridge
If the tape library supports barcode and/or MIC, the details are added to the Backup Export Tool catalog. The barcode information is hidden by
default; to display this detail, right-click anywhere in the column title row to see available column headings and click on Media barcode to make
the barcode information visible in the slots view.
Barcode and MIC technologies are used to reduce the time spent organizing and managing media in a library or an autoloader. In these devices,
each medium is identified with a unique barcode or, where MIC is used, a chip is embedded in the tape cartridge which holds a unique identifier
as well as other information.
Barcodes and MIC enable the Backup Export Tool to significantly reduce media recognition, labeling and cleaning tape detection times.
Scanning the barcode or MIC of the media is faster than reading the medium header, because the Backup Export Tool does not need to
actually load the media into a drive.
A barcode or MIC is a unique identifier for media in the Backup Export Tool catalog. You should not have duplicate barcodes in your
environment.

Barcode Filters
The barcode filter allows users to control access to media by barcode. The user can specify ranges, wildcards, or explicit barcodes that either
include or exclude media for use by the product. This property only applies to libraries. Stand alone devices are not restricted in any way by it.
The filter rules may be set for the whole domain and will be applied automatically to all tasks. Or, they may be set and applied at job level. Any
filter rules applied at job level overwrite the default domain settings.
For more information on setting barcode filters, see Barcode Job Filters.
Initialization Process
The traditional loader inventory mechanism is accomplished by running an identify job on all the slots in a library. This complete inventory can
take a very long time, so the Backup Export Tool uses a "light inventory" process, which is known as an initialization process. This initialization
process consists of:
Checking that the loader is ready for use. If the magazine door is open, this step will fail, and initialization will fail as a result.
Querying the number of physical storage, import/export and device elements that the library contains. (These elements display in the
Tape Library view.)
Binding the loader to its physical devices. This ensures that the devices are associated with the library in the Backup Export Tool catalog.
Updating the status for each element in the loader. Barcodes are read at this time, and are associated with each element regardless of
status (i.e., both Invalid and Valid elements get a barcode shown in the loader status pane).
Initialization occurs when the library driver starts (at service startup or when the driver is manually started), when the user selects the Initialize
command on the loader object or when the Backup Export Tool detects that a user has changed the state of the loader (either by opening the
front door or by using the front panel).
During initialization, the library attempts to perform barcode based identification of media. If a match is found, the loader sets that element’s
status to Probably Valid. This means that if a user is using barcodes with their tape library, they rarely need to run an identification job.
When the job loads the tape it makes sure that the tape is really what the catalog says it is and, if necessary, updates the catalog to indicate what
is really there. If the tape is, in fact, not usable because of the supplied media rules, the tape is re-stowed and another media is tried.
An Identify job will always physically mount media, and reassociate media to barcodes. This provides a mechanism for users to update
barcodes on their media, should they ever need to. It also handles the case where barcodes are added to media after they have been
used without barcodes.
Tape Media Management
One benefit of using the Backup Export Tool with tape libraries is the ease with which you can schedule different backups for different days of the
week/month/year. There are no specific media tasks that must be carried out before you run a backup job. As long as the library has valid media
loaded in it, the Backup Export Tool automatically uses it.
Media is invalid if it has been used by another backup product, is dirty or has been corrupted, or simply has not been identified.
Similarly, if you are restoring data from media that is already within the Backup Export Tool catalog, there are no media management tasks.
However, if you are restoring media from a different domain, you must first import it so that the Backup Export Tool can add the media to the
database and associate all data objects on the tape with that media.
For a detailed description of all media management jobs, see Device Commands.

Barcode Job Filters

Many tape libraries support the use of barcodes to identify media. Each piece of physical media has a unique barcode that the tape library can
read.
The Barcode Filter page allows you to define barcode filters for a job. The filter rules may be set for the whole domain and will be applied
automatically to all jobs. Or, they may be set and applied at job level, using this page. Any filter rules applied at job level overwrite the default
domain settings. All options will be grayed out initially. Deselecting Inherit settings from domain enables the editing buttons and allows you to
create job-specific filters.
There are three ways to assign barcode filters:
Add an individual barcode – This option allows you to specify an individual barcode for inclusion or exclusion. Up to eight characters
may be specified in this filter; the first six relate to the volume identifier and the last two relate to the media identifier. Wildcards may be
used to increase the number of barcodes selected by the filter.
Add a range of barcodes – This filter allows you to specify a range of volume identifiers and media identifiers to include. Any media
without a barcode or outside of the specified range is excluded.
Add barcodes from media present in the library – This filter displays a list of all libraries and their elements. Select the required
barcodes from the list and click either Exclude or Include, as appropriate.


Restore Job Settings
To schedule a restore job to happen at a particular time, change the Schedule Type to Run on specific day and then set the start time and
date. The service ensures that the restore happens at that time.
Verify Job Settings
Like the restore job, you can schedule a verify to happen at a particular time as well. Additionally, you can specify whether the job is a Full or a
Quick verify. A full verify compares the contents of the backup media with the source files on disk. A quick verify only validates that the media can
be read from end-to-end.


Advanced Restore Options
These options apply to all restore jobs regardless of the operating system.
Option Restore
General options
Eject media after use If selected, the Backup Export Tool automatically ejects the media at
the end of the job. This feature only works on devices that support
software eject.
Auto Retension If selected, the Backup Export Tool automatically re-tensions the
media at the beginning of the job. This feature winds the tape
Restore files that are in use If selected, the Backup Export Tool restores the backup copy of the
open file. (On Windows platforms, you can access the restored file
after you restart the computer.) If you select this option, the restored
file will replace your open file. As a result, your current changes may
be lost.
Deselect this option to skip over all selected files that are in use. This
is useful if the open files are more current than the backed up files.
Omit security information If selected, any security information associated with the files and
folders which were part of the backup is removed. The files and
folders are restored, as if they were freshly created, inheriting
permissions.
Windows options
Reparse points Select this option to restore the reparse point data. When this option
is deselected, the Backup Export Tool restores the object as a file or
folder rather than as a reparse point.
information in the restore. If this option is not selected, the Backup
Export Tool restores the object as a directory.
Volume restrictions When enabled, volume quota information will be restored.
Finalize recovery of Microsoft SQL and Exchange Server Select this option to process database transactions when the last
databases incremental restore is complete.
Restore all registry keys / Restore hardware registry keys Controls whether/how the Backup Export Tool restores the described
objects. This setting only applies if you restore the Registry System
State object.
Restore DFS/FRS shares as primary replica (authoritative Use this option to control how a DFS or FRS share is being restored.
restore) Only select it if you want an authoritative restore. See the Microsoft
documentation for more information on authoritative restores.
Data filters, such as security information and directory attributes, cannot restore data that was not originally backed up to the media.
For example, if you did not select Volume restrictions for the backup job, the Backup Export Tool cannot restore this information
because it was never stored on the media.
Advanced Verify Options

The following advanced options are available for Verify jobs.
Option Description
General options
Eject media after use When selected, the Backup Export Tool automatically ejects the
media at the end of the job. This feature only works on devices that
support software eject.
Auto Retention When selected, the Backup Export Tool automatically re-tensions the
media at the beginning of the job. This feature winds the tape
Native data streams format When selected, the Backup Export Tool compares the data in native
format. When unselected, only the data portion of the file is verified.
This must match the mode used during backup.
Windows options
Enable snapshots By default, the verify job creates a temporary snapshot before
verifying the selected file. Deselect this to disable snapshots.
Reparse points Select to verify the reparse point data. When deselected, the Backup
Export Tool verifies the object as a file or folder rather than as a
reparse point.
information in the restore. If this option is not selected, the Backup
Export Tool verifies the object as a directory.
Volume restrictions When enabled, volume quota information is verified.

This article refers to firmware version 6.3 or higher.
AWS Storage Gateway-VTL supports backing up data to virtual tapes and archiving those tapes in the virtual tape shelf (VTS) using the
Barracuda Backup Export Tool. This article provides the basic steps to configure the Backup Export Tool software for a gateway-virtual tape
library (VTL) and perform a backup/export, and successfully restore data. For more information, see Backup Export Tool.
The Backup Export Tool, free for Barracuda Backup customers, allows Barracuda Backup users to export the historical revisions of data backed
up and stored on a Barracuda Backup appliance or appliances. The Backup Export Tool is installed on a media server in the same network as the
Barracuda Backup appliance. Once installed, users can browse connected Barracuda Backup appliances through the Backup Export Tool, locate
data required for export, and export it to external media such as tape drives, tape libraries, virtual tape libraries (VTL), USB drives, and network
attached storage (NAS). Data can be manually exported, or automatically exported on a schedule for weekly, monthly, and yearly revisions.
The Backup Export Tool was designed to allow users to export backup data to external media for long-term archival or for compliance reasons
which may require data to be stored on tape or other form of external media. The Backup Export Tool is not intended to provide disaster recovery
capability and exporting data from a Barracuda Backup appliance does not remove it from the appliance.
Configure the Backup Export Tool to Work with VTL Devices
After you connect the VTL devices to the Windows client where the Backup Export Tool is installed, open the Backup Export Tool to recognize
your devices. For information about how to connect VTL devices to the Windows client, see Step 4: Connect Your Gateway-VTL Devices to Your
Windows Client in the Amazon Web Services User Guide.
By default, the Backup Export Tool detects and recognizes the gateway-VTL devices.
To discover the VTL devices:
1. Open the Backup Export Tool Administrator on your Windows client. If this is the first time you are opening the Backup Export Tool, once
you connect the gateway-VTL devices to your Windows client, the Backup Export Tool automatically recognizes the gateway-VTL
devices.
2. Click Devices in the left pane:
3. Expand the tree under your Backup Export Tool client:
4. If your tape drives are mapped correctly, they display under Drives:

4.
5. The tapes display under Import-Export Slots:
If the drives are not automatically mapped, see Step 4: Connect Your Gateway-VTL Devices to Your Windows Client in the Amazon Web
Services User Guide.
Import a Tape into the Backup Export Tool
Use the steps in this section to import tapes from your Gateway-VTL into the Backup Export Tool software library.
To import a tape:
1. Select Import-Export Slots in the Backup Export Tool client tree.

2. The Import-Export Slots contain the tapes you created in the AWS Storage Gateway-VTL. In this example, 3 x 100 GiB virtual tapes have
been created, shown in the Import-Exports Slots with an Element Status of Invalid – Media not identified. To insert all available
tapes, select the first Import-Export Slot, press Shift on your keyboard, and click the last Import-Export Slot that shows an Element
Status of Invalid – Media not identified:
3. Click Insert Media in the toolbar:
Make no additional changes to the virtual tapes on the Import-Export Slots page. Taking any additional actions, such as Iden
tify or Format, removes the virtual tapes from the device library and archives them to the VTS.
4. The virtual tapes are inserted into the first available storage slots:

5. Close the Insert Media notification dialog box. In the Backup Export Tool client tree, select Storage Slots. The virtual tapes inserted in
the previous steps display in the first available Storage Slots:
The virtual tapes are now imported and are ready for the first backup/export job. No additional configuration is necessary on the Devices page as
each tape is identified and formatted automatically by the Backup Export Tool during the backup/export process.
Export Data from Barracuda Backup to a Tape
To export data from a Barracuda Backup appliance to a Gateway-VTL:
1. Create a new Backup Job in the Backup Export Tool.

2. Select a tape device to write data to.
For detailed configuration steps, see How to Export Data to AWS Storage Gateway-VTL Using the Backup Export Tool.
Archive a Tape Using the Barracuda Backup Export Tool
When you archive a tape, AWS Storage Gateway moves the tape from the Backup Export Tool tape library to the VTS, that is, the offline storage.
You begin tape archival by ejecting from the tape drive to the storage slot and then exporting the tape from the slot to the VTS by using the
Backup Export Tool.
To archive a tape using the Barracuda Backup Export Tool:
1. Click Devices in the left pane, and expand the tree under your Backup Export Tool client:

2. Click Storage Slots, and select the storage slot containing the tape(s) you want to archive:
3. Right-click the selected storage slot(s), and click Remove Media, or click Remove Media on the toolbar:
4. The tape is removed from the storage slot:

5. The selected storage slot Element Status displays as Empty:
6. In the AWS Storage Gateway console, click your gateway, and click VTL Tape Cartridges. Verify the status of the virtual tape you are
archiving:
Restore Data from an Archived Tape Using the Backup Export Tool
Archived tapes are stored in a VTS which provides offline storage. If you want to access tape data, you must first retrieve the tape from the VTS
back to your gateway. Use the steps in this section to retrieve the tape archived in the preceding section. Note that restoring archived data is a
two-step process:
Retrieve the archived tape from your (VTS) to a gateway-VTL

Restore the data using the Backup Export Tool
Retrieve Archived Tape
To retrieve an archived tape:
1. In the AWS Storage Gateway console navigation pane, click Virtual Tape Shelf (VTS); the console displays all virtual tapes archived by
all of your gateways. Select the virtual tape you want to retrieve, and click Retrieve Tape:
To retrieve an archived tape, the virtual tape status must be ARCHIVED.
2. In the Tape Barcode field of the Retrieve Tape wizard, verify the barcode identifies the virtual tape you want to retrieve:
3. From the Gateway drop-down list, select the gateway you want to retrieve the archived tape to, and click Proceed.
The virtual tape status changes from ARCHIVED to RETRIEVING. Once all data is moved, the status of the virtual tape in the VTS changes to R
ETRIEVED, and the tape displays in your gateway's VTL.
It takes approximately 24 hours to retrieve a tape from the VTS to a gateway; retrieved virtual tapes are read-only.
Restore Data Using the Backup Export Tool
Once the retrieved virtual tape status changes from RETRIEVING to RETRIEVED, use the steps in the article How to Restore Archived Data from
an AWS Storage Gateway Using the Backup Export Tool to import the tape back into the Backup Export Tool and configure a restore job.

When manually performing a data export or configuring a schedule to automatically export weekly and monthly revisions, it is
Once you set up your AWS Storage Gateway-VTL, install and configure the Backup Export Tool on your master server and enable it in the
Barracuda Backup user interface, use the steps in this article to manually export data from a Barracuda Backup appliance to your AWS Storage
Gateway-VTL:
1. Open the Backup Export Tool.

5. Expand your Barracuda Backup appliance tree until you reach the backup sources currently being protected by the Barracuda Backup
appliance:

tree. Note that only weekly, monthly, and yearly revisions are available for export:
Contact Barracuda Networks Technical Support if you need daily revisions.
7. Select the desired backup revision, and expand the tree to drill down into the folder structure. You can navigate the folder structure and
any supported applications that are present, for example, Microsoft SQL, Exchange, Hyper-V:

9. Click Device in the left pane, expand Tape Device in the right pane, and select a single tape device from the list:

9.
If you select multiple tape devices, data is exported to each device simultaneously.
11. Once you select your encryption and compression options, click Configuration in the left pane. Use the Configuration page to specify
how data is written to the selected storage device.
See Configuring Backup Schedule Settings.

12. Once you configure your backup options, click Advanced in the left pane to access advanced options related to email alerts, log files,
barcode filters, and copy policies.
13. When you are done configuring options, click OK in the lower right corer to create the new backup job.
14. Click Jobs and Media in the left pane. The newly created backup/export job should now display in the right pane:
15. Click on the backup job, and select Run in the toolbar, or right-click the backup job and click Run to execute the data export:
16. In the confirmation dialog, click Yes to run the back/export job:

16.
17. Click Status and Logs in the left pane to view the backup/export job status:
18. Allow the backup job to complete:

How to Restore Archived Data from an AWS Storage Gateway Using the Backup Export
Tool
Data exported using the Backup Export Tool cannot be restored back to a Barracuda Backup appliance. This data can be restored
back to the original client system, a different system, or media connected to the master server.
Once you retrieve your archived tape from the Virtual Tape Shelf (VTS) in the AWS Storage Gateway console and the status of the virtual tape is
RETRIEVED, use the following steps to import the tape into the Backup Export Tool and configure a restore job:
1. Click Devices in the left navigation pane, and expand the tree under your Backup Export Tool client:
2. Click Import-Export Slots, and verify the retrieved virtual tape appears in the import-export slot. Once a tape is retrieved from the VTS,
it automatically appears in the first available import-export slot. Verify the Element Status displays as Valid, and the media barcode ma
tches that of the virtual tape in your storage gateway:
3. Select the Import-Export Slot containing your retrieved virtual tape(s), and click Insert Media in the toolbar to insert the tape(s) into a
storage slot:
Make no additional changes to the virtual tapes on the Import-Export Slots page. Taking any additional actions, such as Iden
tify or Format, removes the virtual tapes from the device library and archives them to the VTS.

4. The virtual tape(s) are inserted into the first available storage slots. Close the Insert Media notification dialog box.
5. Click Tasks in the left pane, and double-click Restore:
6. In the New Restore Job dialog box, enter a name to identify your restore job:
7. The Restore Job Properties window displays. All previous backup/export jobs from Barracuda Backup appliances display in the tree
below Network:
8. Expand the tree until you reach the previously exported data you want to recover:
9. Select either the entire folder from the tree or select individual files in the right pane. Once you select the data you want to restore, the Se
lect Destination window displays.
10. Expand the tree under Network and locate a recovery destination for the selected data. The Backup Export Tool recognizes any
computers in the network where the Backup Export Tool is installed. In this example, the recovery folder is titled RESTORE_DATA on
the Backup Export Tool client system:

10.
11. Click OK. Click Device in the left pane, and expand the Tape Device tree.
12. Select a single tape device from the list; this is the device that you are restoring data from:
Once you select a device to restore from, you can optionally click Configuration and Advanced in the left pane to configure
additional options. For more information, see How to Schedule Restore and Verify Jobs and Advanced Restore and Verify
Options.
13. Once all configuration options are configured, click OK.

14. Click Jobs and Media in the left pane; the newly created restore job should now display in the right pane:
15. Right-click the restore job, and click Run, or click on the restore job and click Run in the toolbar to execute the restore job.
16. In the confirmation dialog, click Yes to run the backup/export job:
17. Click Status and Logs in the left pane to view the restore job status:

18. Allow the restore job to complete. Verify the data is successfully restored.


The AWS Storage Gateway is a service connecting an on-premises software appliance with cloud-based storage to provide seamless and secure
integration between an organization’s on-premises IT environment and the AWS storage infrastructure. The service enables you to securely store
data to the AWS cloud for scalable and cost-effective storage. The AWS Storage Gateway supports industry-standard storage protocols that work
with your existing applications. It provides low-latency performance by maintaining frequently accessed data on-premises while encrypting and
storing all of your data in Amazon Simple Storage Service (Amazon S3) or Amazon Glacier.
There are three types of AWS Storage Gateway; the Barracuda Backup Export Tool supports the Storage Gateway-Virtual Tape Library (VTL).
With Gateway-VTL you have a limitless collection of virtual tapes. Each virtual tape can be stored in a Virtual Tape Library backed by Amazon S3
or a Virtual Tape Shelf (VTS) backed by Amazon Glacier. The Virtual Tape Library exposes an industry standard iSCSI interface which provides
the Backup Export Tool online access to the virtual tapes. When you no longer require immediate or frequent access to data contained on a
virtual tape, use the Backup Export Tool to move it from its Virtual Tape Library to your VTS to further reduce your storage costs.
AWS Storage Gateway-VTL with the Backup Export Tool
AWS Storage Gateway-VTL with the Backup Export Tool is designed for customers using Barracuda Backup that want to offload certain data sets
from their Barracuda Backup appliance for the purpose of:
Long-term retention without using up valuable disk space on the Barracuda Backup appliance;
Exporting data which is inefficiently deduplicated and compressed instead of keeping numerous historical revisions on the Barracuda
Backup appliance; and/or
Exporting data for the purpose of freeing up disk space on the local Barracuda Backup appliance to ensure a longer life cycle.
Figure 1 illustrates a typical environment using Barracuda Backup, Backup Export Tool, and AWS Storage Gateway-VTL.
Figure 1. Barracuda Backup and AWS Storage Gateway-VTL Architecture.
Infrastructure
The AWS Storage Gateway’s software appliance is available for download as a virtual machine (VM) image that you install on a host in your
datacenter. Once you install your gateway and associated it with your AWS Account through Amazon’s activation process, you can use the AWS
Management Console to create either Gateway-Cached or Gateway-Stored storage volumes or Gateway-VTL virtual tape libraries that you can
mount as iSCSI devices using your on-premises applications.
Gateway-VTL enables you to seamlessly replace your physical tape infrastructure with a virtual tape infrastructure. Each Gateway-VTL presents
Backup Export Tool with an industry-standard iSCSI-based VTL consisting of a virtual media changer and tape drives. Create virtual tapes in your
VTL using the AWS Management Console. Each VTL can hold up to 1,500 virtual tapes with a maximum aggregate capacity of 1 PB. Virtual
tapes are discovered by the Backup Export Tool using its standard media inventory procedure. Virtual tapes in your VTL are available for
immediate access and are backed by Amazon S3. The Backup Export Tool can read data from or write data to virtual tapes by mounting them to
virtual tape drives using the virtual media changer.
Hardware and Software Requirements
The AWS Storage Gateway VM must be either installed on a host in your datacenter running supported versions of VMware ESXi or Microsoft
Hyper-V, or as an AMI running on an EC2 instance. The gateway VM must be deployed with a minimum set of hardware resources. The AWS
Storage Gateway currently supports Microsoft Windows, Red Hat Enterprise Linux, and VMware ESXi, iSCSI initiators. For additional information,
refer to the AWS Storage Gateway User Guide.

Long Term Retention
For cost-effective long term retention of data requiring infrequent access, you can use the Backup Export Tool to move virtual tapes from one or
more of your VTLs to your VTS backed by Amazon Glacier. Your VTS is automatically created when you activate your first Gateway-VTL. Store
virtual tapes that need to be accessed frequently in a VTL. Data that does not need to be retrieved frequently can be archived to your VTS.
Access to virtual tapes in your VTL is immediate while virtual tapes in your VTS must be retrieved and loaded into a VTL before it can be
accessed. You can retrieve virtual tapes from your VTS using the AWS Management Console. Virtual tapes retrieved from your VTS take
approximately 24 hours before they are automatically loaded into your VTL.
Restore Data
You can retrieve a virtual tape using the AWS Management Console. First select the virtual tape, then choose the VTL into which you want to
load the virtual tape. It takes about 24 hours for the retrieved virtual tape to be available in the selected VTL. Once the virtual tape is available in
the VTL, use the Backup Export Tool to make use of the virtual tape to restore data.
Performance
As the Gateway-VTL sits between your application, AWS, and underlying on-premises storage, the performance you experience is dependent
upon a number of factors including the speed and configuration of your underlying local disks, provisioned host processor and memory, network
bandwidth between your iSCSI initiator and gateway VM, the amount of local storage allocated to the gateway VM, and the bandwidth between
the gateway VM and AWS. For Gateway-VTL, to provide predictable write performance to the Backup Export Tool, it is important that you allocate
enough local cache disk storage to durably buffer data uploaded to AWS. For additional information, refer to the AWS Storage Gateway User
Guide for guidance on sizing cache. Amazon recommends configuring your disks in a redundant array of independent disks (RAID) configuration
to improve performance and to protect against disk failures.
Security
The AWS Storage Gateway encrypts all data in-transit to and from AWS via SSL. All volume and snapshot data stored in AWS using
Gateway-Stored Volumes and Gateway-Cached Volumes, and all virtual tape data stored in AWS using Gateway-VTL, is encrypted at-rest using
Advanced Encryption Standard (AES) 256, a secure symmetric-key encryption standard using 256-bit encryption keys. Additionally, the Backup
Export Tool has optional built-in encryption and compression features.
Storage
Table 1. Storage.
Feature Description
Replication Support for the AWS Storage Gateway-VTL does not replace
replication to either Barracuda Cloud Storage or another Barracuda
Backup appliance. Replication to the Barracuda Cloud or to another
Barracuda Backup appliance is a full disaster recovery solution while
AWS Storage Gateway-VTL is designed for long-term archiving.
Additionally, unlike replication to the Barracuda Cloud or a Barracuda
Backup appliances, the Backup Export Tool does not support System
State data export or bare metal recovery.
Data Reduction The AWS Storage Gateway performs compression of data in-transit
and at-rest, which can reduce both data transfer and storage
charges. All data transfer between the AWS Storage Gateway VM
and AWS, and all data stored in AWS, is compressed. In addition, the
AWS Storage Gateway VM only uploads data that has changed,
minimizing the amount of transferred data.
Bandwidth Throttling use the AWS Management Console to restrict the bandwidth
between your gateway and AWS based on the selected rate. You
can specify individual rates for inbound and outbound traffic.
Data Storage on a Virtual Tape When creating a virtual tape, select from the following sizes: 100 GB,
200 GB, 400 GB, 800 GB, 1.5 TB, and 2.5 TB
Data Storage in VTL Each VTL can store up to 1500 virtual tapes with a maximum
aggregate capacity of 1 PB.
Data Storage on a VTS There is no limit to the amount of data you can store on a VTS.
Access Data
The virtual tape containing your data must be stored in a VTL before you can access it, however, access to the virtual tapes is instantaneous. If
the virtual tape containing your data is in your VTS, you must first retrieve the virtual tape from your VTS. You can retrieve the virtual tape using

the AWS Management Console. First select the virtual tape, then choose the VTL into which you want to load the virtual tape. It takes about 24
hours for the retrieved virtual tape to be available in the selected Virtual Tape Library. Once the virtual tape is available in the Virtual Tape
Library, you can use the Backup Export Tool to make use of the virtual tape to restore data.
Get Started with AWS Storage Gateway
To sign up for the AWS Storage Gateway, go to the AWS Storage Gateway detail page, and create an account or log in with an existing account.
Once logged in, you can begin the AWS Storage Gateway sign-up process. After you sign up, you can begin setting up and activating your
gateway by visiting the AWS Management Console. For details, refer to the Amazon Web Services article Getting Started with AWS Storage
Gateway.
Billing
The Backup Export Tool is free to all Barracuda Backup customers, and Barracuda does not charge a fee to use the Amazon Storage Gateway.
Amazon charges for the Storage Gateway and the cost to store data in their cloud, and $125/per activated virtual gateway per month.
You are billed a monthly fee for each of gateway; this fee is prorated daily. Billing for a gateway begins upon activation and continues
until you delete the gateway from the AWS Management Console or via the API.
You are billed for the virtual tape data you store in AWS. This fee is prorated daily. You are only billed for the portion of virtual tape
capacity that you use, not for the size of the virtual tape you create.
You are billed for Internet data transfer for each GB downloaded from AWS to your gateway. All data transfer for uploading to AWS is
free.
You are charged for the peak concurrent data retrieval in a month.
Table 2. Cost to Store Data in AWS.
VTS Storage $0.007 per GB per month of data stored
VTL Storage $0.030 per GB per month of data stored
VTS Retrieval $0.30 per GB(1)
Virtual Tape Deletion Free(2)
Notes:
(1)Pay only for the highest peak concurrent data retrieval in a month.
(2)There are no charges for deleting virtual tapes from your VTL and VTSf. However, there is a pro-rated charge of $0.021 per gigabyte for
virtual tapes deleted prior to 90 days from your VTS.
For additional storage pricing, refer to the AWS Storage Gateway Pricing.
Concurrent Data Retrieval Charges
Concurrent data retrieval is calculated when a retrieval from VTS is initiated. The concurrent data retrieval is the sum of the size of all virtual tape
retrievals initiated concurrently or concurrently in progress. If the concurrent data retrieval is more than any prior concurrent data retrieval in the
month you are charged for the difference between this new monthly peak and the prior monthly peak. If the concurrent data retrieval is less than
or equal to any prior concurrent data retrieval in the month, the retrieval is free.
Example 1 – You initiate retrieval of a 100 GB virtual tape from your VTS in US East (Northern Virginia) Region. This is the first retrieval
of the month. The prior peak concurrent data retrieval for the month was 0 GB. When the retrieval is initiated the concurrent data
retrieved is 100 GB. 100 GB is your new monthly peak concurrent data retrieval. The charge for the retrieval is the difference between
the prior and the new peak concurrent data retrieval, that is, (100 GB – 0 GB) x $0.30/GB = $30.00.
Example 2 – You initiate retrieval of one virtual tape containing 500 GB of data from your VTS in US East (Northern Virginia) Region.
This is the first retrieval of the month. The prior peak concurrent data retrieval for the month was 0 GB. When the retrieval is initiated the
concurrent data retrieved is 500 GB. 500 GB is your new monthly peak concurrent data retrieval. You are charged the difference
between the prior and new peak concurrent data retrieval, that is, (500 GB - 0 GB) x $0.30 / GB = $150. Twelve hours after initiating the
retrieval of the 500 GB virtual tape you initiate retrieval of a virtual tape containing 600 GB of data. When the second retrieval is initiated
you have two virtual tape retrievals concurrently in progress as any virtual tape retrieval takes about 24 hours to complete. The
concurrent data retrieved is 500 GB + 600 GB = 1100 GB. The new peak concurrent data retrieval for the month is 1100 GB and you are
now charged the difference between the new peak concurrent data retrieval and the existing peak concurrent data retrieval, that is, (1100
GB-500 GB) x $0.30 = $180.
Example 3 – You initiate retrieval of one 500 GB virtual tape from the VTS in US East (Northern Virginia) Region. This is the first retrieval
of the month. The prior peak concurrent data retrieval for the month was 0 GB. When the retrieval is initiated the concurrent data
retrieved is 500 GB which is your new peak concurrent data retrieved. The charge for the retrieval is the difference between the prior and
the new peak concurrent data retrieval, that is, (500 GB – 0 GB) x $0.30/GB = $150.00. The next day, you initiate a retrieval of one 500
GB virtual tape after the first tape retrieval is complete. Because 500 GB is equal to the prior peak concurrent data retrieval of 500 GB,
the second retrieval is free.
Data Charges for Deleting Data

VTS is designed for use cases where data is retained for months, years, or decades. Deleting virtual tapes from a VTS is free if the virtual tape
being deleted has been stored for three months or longer. If a virtual tape is deleted within three months of being archived, you are charged an
early deletion fee. If you delete data from your VTS that is less than three months old, in the US East (Northern Virginia) Region, you are charged
a prorated early deletion fee of $0.03 per GB deleted within three months. For example, if you delete 1 virtual tape containing 1 GB of data 1
month after uploading it, you are charged a $0.02 early deletion fee. If, instead you delete the same virtual tape after 2 months, you would be
charged a $0.01 early deletion fee.

Barracuda Console
Before configuring the IP address and network settings, complete Step 1 - How to Install a Barracuda Backup Server.
Console
The Console interface is a curses application that Barracuda Backup appliances boot into when started. Use the interface to set your locale,
change network settings, enter your License Token and default domain, troubleshoot, or reload the configuration through direct physical access
to the unit. To access and interact with the Console screen, you must plug a keyboard and monitor into your Barracuda Backup appliance.
Navigation
Use the keyboard commands to navigate and make changes to your Barracuda Backup settings through the Barracuda Console.
1. Power on the appliance, and enter your TCP/IP configuration in the black screen. Once configuration is complete, the System
Configuration screen displays.
2. Use the Arrow keys to highlight the desired System Configuration option in the left pane.
3. When the desired section is highlighted, press Enter to enter edit mode.
4. Use the Arrow keys to navigate through the options in the right pane.
5. Press Enter to trigger an action button, or, if you have selected and made changes to an editable field, press Enter to move to the Save
button.
Press Esc to discard changes and return to read mode. Once in read mode, use the Arrow keys to highlight the desired Syste
m Configuration option in the left pane.
6. Press Enter to save your changes and return to the System Configuration options in the left pane. Use the Arrow keys to highlight the
next section you wish to edit.
Interface
Status
When you open the console, the Status page displays:
Language
Select your locale from the Language list:

TCP/IP Configuration
Enter your TCP/IP Configuration details:
Licensing
Enter your License Token and Default Domain:

Troubleshooting
To run network Connectivity Tests, enter the Host/IP address you wish to test, and select the test you wish to run:
System
From the System Configuration page, you can select to Reboot or Shutdown the appliance, Reload Appliance Configuration, and Change
Console Password:

Network Settings
A Barracuda Backup appliance is considered fully online when Local, Internet, and Cloud, display as Up in the Network Status section; note
that it is normal for Internet and Cloud to display as Down for locally controlled appliances:
It is possible to have connectivity to the LAN and Internet but not to Barracuda Networks. This can occur if the system is not linked or if a LAN
firewall is blocking the necessary outbound port 1194. Encrypted traffic is sent out across port 1194 to the Barracuda Networks management
network.
If you wish to restrict the outbound network traffic on port 1194 to the Barracuda Networks specific IP range, contact Barracuda Networks
Technical Support for a listing of required IP addresses to allow.
If a DHCP server is running on the network, it is an easy way to bring Barracuda Backup online. Barracuda Backup requests network IP
information from the DHCP server when it boots, or after it loses network connectivity for any reason. Static IP information can be specified as
well.
If you have questions about Barracuda Console, or need assistance getting your Barracuda Backup appliance online, contact Barracuda
Networks Technical Support.

Online Service Terms

See the Barracuda Website to view Cloud Service Terms.

Barracuda Backup Administrator&#39;s Guide v42

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Barracuda Backup Administrator&#39;s Guide v42

Enviado por

Direitos autorais:

Formatos disponíveis

1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Agents, Tools, and Mobile Access

Copyright © 2015, Barracuda Networks Inc.

What's New in Barracuda Backup

What's New in Version 6.4.02

Replication and Restore to Amazon Web Services (AWS)

Open support tunnel from the web UI [BNBS-28823]

Backup jobs fail due to other process [BNBS-29081]

What's New in Version 6.4.00

New Barracuda Backup Dashboard and Overview pages

HTTPS support for uploading a CA-signed certificate in Local UI

Summary reports display incorrect share names [BNBS-27913]

What's New in Version 6.3.04

Copyright © 2015, Barracuda Networks Inc.

What's New in Version 6.3

What's New in Version 6.2

What's New in Version 6.1

Barracuda introduces Cloud-to-Cloud Backup for Microsoft Office 365

What's New in Version 6.0

New web interface look and feel

What's New in Version 5.4

Copyright © 2015, Barracuda Networks Inc.

Continuing support for Microsoft applications:

What's New in Version 5.2

Barracuda LiveBoot in the Cloud for VMware:

The following feature has been deprecated in version 5.2

What's New in Version 5.1

What's New in Version 5.0

Barracuda LiveBoot for VMware:

Copyright © 2015, Barracuda Networks Inc.

What's New in Barracuda Cloud-to-Cloud Backup

What's New in Cloud-to-Cloud Backup (August, 2017)

The following new major features are added

OneDrive for Business restores are no longer limited to 1 GB [CCB-598]

Copyright © 2015, Barracuda Networks Inc.

Supported Servers and Data Types

Supported Data Sources by Version

Copyright © 2015, Barracuda Networks Inc.

Microsoft Exchange Server Backup

How to Back Up Microsoft Exchange Server 2013 and Higher

Microsoft Exchange Server Restore

Microsoft Exchange Server Recovery and Restoration

Microsoft Exchange Server Troubleshooting

How to Resolve Microsoft Exchange 2010 Large Message Restore Errors

Microsoft Exchange Server Database Availability Group Backup

Microsoft Exchange Server Database Availability Group Troubleshooting

Best Practices for Microsoft Exchange

Copyright © 2015, Barracuda Networks Inc.

Best Practices for Microsoft Exchange

Barracuda Backup provides two different types of Microsoft Exchange backups:

Microsoft Exchange Server Protection

The Barracuda Backup Agent must be installed on each Exchange server

With Barracuda Backup, you can:

Select individual or multiple databases for backup

Install the Barracuda Backup Agent on each node

For details on backing up Exchange DAGs, refer to:

Copyright © 2015, Barracuda Networks Inc.

Transaction log truncation occurs after every backup, Complete or Log.

Barracuda Backup provides the following Microsoft Exchange recovery options:

Overwrite an existing database

Message-Level Exchange Protection

For more information on message-level backup, see:

How to Set Up Microsoft Exchange Server 2013 or Higher Message-Level Backup

Copyright © 2015, Barracuda Networks Inc.

Barracuda Backup Administrator's Guide v42

Barracuda Backup Administrator's Guide v42