Virtualized Exchange Servers in Distributed Configurations
As previously described, Backup Exec supports modern image-level (“agentless”) protection of VMware and Hyper-V virtual machines, including virtual machines hosting applications such as Exchange. It’s important to note that Backup Exec does not currently support image-level backups of virtualized Exchange servers in a distributed configuration. Only virtual standalone Exchange servers are supported for image-level backup and granular recovery.
In order to achieve granular recovery support of virtualized Exchange servers in a distributed configuration, such as an Exchange 2010 Database Availability Group (DAG), the virtual machines must be protected using agent-based backups, which essentially treats each virtual machine as if it were a standalone, physical system.
Note: Backup Exec does not support granular recovery of Exchange 2013 mailbox objects. This functionality is planned for a later release of Backup Exec.
Protection of Physical Exchange Servers
For physical Exchange servers, the Agent for Windows is installed locally to the Exchange server. The Agent for Windows interacts with the physical Exchange server to prepare the Exchange databases for backup and to transmit backup data to the Backup Exec server over the NDMP protocol.
Backup of Physical Exchange Servers
VSS Integration and Physical Exchange Servers
Backups of physical Exchange servers that are captured by the Agent for Windows are snapshot backups performed using Microsoft’s VSS Writers (the only exception is Exchange 2003, which does not have a VSS writer). In most cases, Backup Exec uses a VSS full backup, which ensures that Exchange is placed into a consistent state at the time of backup and also truncates transaction logs, a key element of maintaining a healthy database application over time.
The Agent for Windows can only protect Exchange components of a server after the Agent for Applications and Databases has been licensed within Backup Exec.
Granular Application Recovery of Physical Exchange Servers
In addition to preparing physical Exchange servers for backup and transmitting Exchange backup data to the Backup Exec server for storage, the Agent for Windows also plays a key role during Exchange recovery. For example, the presence of the Agent for Windows locally installed to a physical Exchange server enables the Backup Exec server to directly transmit and restore granular Exchange objects back to the production Exchange environment of an organization.
Offhost Backups of Physical Exchange Servers
Backup Exec also supports offhost backups of physical Exchange servers. Offhost backups help alleviate the processing overhead of backup operations from the physical Exchange server and transfer them to the Backup Exec server.
For more information on Backup Exec and configuring offhost backups of physical Exchange servers, refer to the Backup Exec Administrator’s Guide and the following technote: http://www.symantec.com/docs/HOWTO12231.
Granular Application Recovery of Exchange Virtual Machines
To enhance Backup Exec’s virtual machine protection and recovery capabilities, particularly when the virtual machine is hosting Exchange, the Agent for Windows should be installed into the guest virtual machine itself. In this configuration, Backup Exec can still capture snapshot-based, image-level backups of the destination virtual machine, but can then also offer dynamic application discovery capabilities and granular recovery of Exchange application components, all from a single-pass backup. In other words, even with the Agent for Windows installed to the virtual machine, the backup process remains what is known in the industry as an “agentless” backup; the presence of the Agent for Windows within the virtual machine simply allows for application metadata capture and granular recovery of application objects directly back to the original virtual machine.
Agent for Windows Enables Granular Recovery of Virtualized Exchange Servers
While Backup Exec fully supports protecting virtualized Exchange servers without installing the Agent for Windows to the virtual machine, recovery options are limited in this configuration. When the Agent for Windows is not present on the Exchange virtual machine, Backup Exec has no direct knowledge of Exchange being present on the virtual machine, and recovery options are limited to full virtual machine recovery and file/folder recovery.
Application-specific recovery features are only available when the Agent for Windows is installed to the Exchange virtual machine, which allows Backup Exec to discover the Exchange application and capture the Exchange metadata needed to enable application-specific recovery features.
VSS Integration and Virtualized Exchange Servers
When protecting virtualized Exchange servers, Backup Exec utilizes Microsoft’s VSS service to prepare the Exchange virtual machine for backup and truncation of Exchange transaction logs. For VMware environments, these VSS calls are made to the Agent for Windows on the Exchange virtual machine through interactions with the vStorage API, and involves the VSS writer on the virtual machine. The VSS writer will be either the VSS writer included with VMware Tools, or the Backup Exec VSS writer that is installed with the Agent for Windows. For Hyper-V environments, a similar process happens through interactions with the Hyper-V host via the local Agent for Windows agent installed to the Hyper-V host. The VSS writer that is used to prepare the virtual machine for backup will be either the VSS writer installed to the virtual machine along with Hyper-V Integration Services, or the Backup Exec VSS writer that is installed with the Agent for Windows.
With either VMware or Hyper-V environments, Backup Exec invokes a virtual machine-level VSS full backup, which prepares Exchange for the virtual machine snapshot event and truncates Exchange transaction logs. If the Agent for Windows is installed to the Exchange virtual machine, the VSS backup method can be changed to a VSS copy, which will not truncate log files.
For more information, refer to the following technote: http://www.symantec.com/docs/HOWTO74082.
Uniquely Named Mailbox
To enable key features related to the protection and recovery of Exchange servers, such as granular recovery of Exchange objects, Backup Exec must have access to a uniquely named mailbox within the Exchange infrastructure. Access to this mailbox enables Backup Exec to interact with Exchange and important components within the Exchange Information Store. In order to enable granular recovery of Exchange objects, you must use the appropriate Exchange Server management utility to assign the user account to the Exchange Organization Administrators role (Exchange 2007) or the Exchange Organization Management role (Exchange 2010/2013).
The uniquely named mailbox cannot be hidden in the Exchange Global Address List.
For more information about this mailbox and associated requirements, refer to the Backup Exec Administrator’s Guide or the following technote:
- Ensuring Exchange mailbox name is unique http://www.symantec.com/docs/TECH24691.
Exchange Management Tools
You must install the Exchange Management Tools on the Backup Exec server. The management tools on the Backup Exec server must be the same version or later as the management tools that are on the Exchange Server. For more information about installing the Exchange Management Tools, refer to your Microsoft Exchange documentation.
Protection of Virtualized Exchange Servers
For virtualized Exchange servers, Backup Exec interacts with the Exchange server through the virtual host, either through software APIs provided by the virtual infrastructure (VMware), or through the Agent for Windows installed to the virtual host (Hyper-V). For virtualized Exchange servers, Backup Exec fully supports what is generally known as “agentless” backup, both for VMware as well as Hyper-V environments.
Backup of Virtualized Exchange Servers
For additional information on requirements for protecting Exchange environments using Backup Exec, refer to the Backup Exec Administrator’s Guide and the following technotes:
- General Exchange protection requirements: http://www.symantec.com/business/support/index?page=content&id=HOWTO24128
- Exchange granular recovery requirements: http://www.symantec.com/docs/TECH51740
Note: “Licensing Backup Exec in Exchange Environments” provides more information about the Agent for Applications and Databases licensing.
Exchange Protection Methods and Technology
Backup Exec employs modern, highly advanced, and scalable technology to protect and recover Microsoft Exchange systems. While very easy-to-use, these sophisticated technologies ensure that Microsoft Exchange remains properly protected and ready for recovery events, allowing customers and partners to sleep easy at night, knowing they are prepared to handle any disaster that may befall their Exchange infrastructure.
Supported Exchange Versions
Backup Exec supports all major versions of Microsoft Exchange, including Exchange 2003/2007/2010/2013. Please note that for Exchange 2010/2013 systems, the Backup Exec server must be hosted on 64-bit hardware. For a complete list of supported software platforms and applications, please refer to the Backup Exec Software Compatibility List (SCL): http://entsupport.symantec.com/umi/V-269-1.
Components Used to Protect Exchange
The Backup Exec Server
The primary component used to protect and recover Microsoft Exchange is the Backup Exec server. The Backup Exec server interacts with the Exchange system to prepare the system for backup, to capture backup data selections, to store backup sets to the target storage device, and to perform recovery operations.
The Agent for Windows
For physical Exchange servers, the Backup Exec Agent for Windows is installed to the physical Exchange servers to identify, capture, and transmit Exchange backup data to the Backup Exec server for storage. For Exchange 2007 and later (Exchange 2003 does not have a VSS writer), Exchange backup data is captured through VSS snapshots and transmitted by the Agent for Windows to the Backup Exec server over the NDMP protocol, using a secure (TSL/SSL) and trusted connection.
For virtualized Exchange servers on the VMware vSphere or Microsoft Hyper-V platforms, the virtual machines hosting Exchange are protected using image-level backups through snapshot interactions with the virtual host. In these virtualized configurations, the Agent for Windows can be installed on the Exchange virtual machine to enable application discovery and metadata collection, allowing for granular application recovery features for virtualized Exchange servers. Protection of virtualized Exchange servers without the Agent for Windows installed is also supported, but virtual recovery options are limited to full virtual machine recovery and file/folder recovery.
Additional information on the differences in how Backup Exec can be used to protect physical and virtualized Exchange servers is provided in “The Agent for Applications and Databases.”
The Agent for Applications and Databases
When protecting either physical or virtualized Exchange servers with Backup Exec, a license for the Agent for Applications and Database is required before Backup Exec can perform backup and recovery operations of Exchange application data.
Enabling the Agent for Applications and Databases
Whether the Agent for Applications and Databases license is included or purchased separately depends on the Backup Exec version that is being used. For example, the standard Backup Exec 2012 product allows customers to pick and choose the different agents and options they need to protect their environment, while the Backup Exec 3600 Appliance includes unlimited use of the Agent for Applications and Databases in its core license.
It’s important to note that the Agent for Applications and Databases does not represent a true software agent that needs to be pushed or installed to a physical Exchange server in order to protect it; the license simply unlocks the ability for Backup Exec to interact with and protect Exchange components. The Agent for Applications and Databases also enables the use of Backup Exec’s VFF driver, which is used for advanced granular recovery operations.
We have become a species of information addicts – the “information explosion” is affecting the everyday lives of office workers. What is crystal clear is that we are all suffering from a 21st century ailment – Information Overload – and it is taking over our personal lives, working lives, and our businesses.
Businesses need to protect a broad range of information, generated in a plethora of ways, through multiple applications used by billions of individuals around the world. Organisations not only need to protect their information and IT infrastructure, but need to be aware of how the infrastructure facilitates the sharing and use of the information used by the organisation between, not just connections among colleagues, but linking businesses, from businesses to consumers, as well as between consumers themselves. In other words, all the collaborative environments, and the movement of data while in use.
Accessing work information out of hours, compulsively checking emails, texts and social media and hoarding endless emails and multiple versions of the same file are all symptoms of information overload. But the technology enabling us to be more productive (fantastic mobile devices and faster connectivity) together with the mismanagement of information is actually counter-productive.
Email is Business Critical
Email has become an indispensable way of communicating and transferring data in the modern electronic age. In the year 2010, it was estimated that almost 300 billion emails were sent each day, and around 90 trillion emails were sent every year. Considering the rate at which data continues to increase year-over-year, the number of emails sent today is likely significantly greater. Email is used for many forms of communication, including business critical communications for companies of all sizes.
Companies rely heavily upon email systems to conduct day-to-day business operations, and any significant period where access to email is lost is considered to be highly intolerable.
All email solutions used by modern businesses are based upon a server infrastructure hosting an email software system. Whether hosted locally on physical or virtualized servers, hosted by a partner, or hosted in the cloud, these email software systems support the incredible amount of email transmissions that happen every day, and can be implemented in many different sizes and configurations. Perhaps the most common and popular email system used in the industry today is Microsoft Exchange.
Because Microsoft Exchange plays such a critical role in the ability for organizations to conduct day-to-day business, it’s equally critical that companies employ protection solutions that enable them to quickly and easily recover their Exchange system should a data loss or disaster event occur. Backup and recovery solutions of the highest value will offer features that enable the following:
- Functionality designed specifically for Microsoft Exchange
- Protection of Exchange while it remains online and functional
- Ability to protect physical Exchange servers as well as virtualized Exchange systems
- Support for highly available Exchange configurations
- Adherence to Microsoft best practices for Exchange backup and recovery
- Optimization of secondary (backup) storage using data deduplication technology
- Support for local as well as offsite storage of backup data
- Multiple levels of recovery from a single-pass backup
Symantec Backup Exec
For many years, the Symantec Backup Exec product family has offered market-leading solutions for the protection of Microsoft Exchange, and solves each of the key problems mentioned above. The Agent for Applications and Databases offers purpose-built functionality to ensure Microsoft Exchange is properly protected against disaster and to help partners and customers quickly and easily perform any level of Exchange recovery, whether it’s bare metal recovery of a physical Exchange server, granular recovery of an individual Exchange email, or anything in between.
Key benefits of Backup Exec include the ability to:
- Reduce business downtime
- Eliminate complexity
- Spend less time managing backups
- Ensure critical information on virtual or physical systems is always protected
- Restore data in seconds
- Reduce storage and management costs
- Optimise network utilisation
- Eliminate redundant additional backup jobs
- Provide granular recovery of data for applications and databases
Performance Notes and Recommendations
Configuring Backup Exec’s Deduplication Disk Storage Device
Backup Exec 2012 SP2’s Deduplication Option allows customers to create a single deduplication disk storage device per Backup Exec server. A deduplication disk storage device is where all deduplication blocks are stored, regardless of whether client-side or Backup Exec serve-sider deduplication was used for a specific backup. A Backup Exec server hosting a deduplication disk storage device can hold up to 32 TB of deduplicated data. Note that the deduplication disk storage device is not utilized for backups and restores when appliance deduplication is used. Appliance deduplication stores all backup data on the specific appliance.
Processor Utilization with Client and Server Deduplication
Depending on the type of deduplication used, processor utilization will vary. In general, the deduplication process is not gated or throttled in any way, and is geared towards accomplishing deduplicated backups and restores of deduplicated data as quickly as possible.
Client-side deduplication performs the bulk of deduplication calculations on the client (or source) system. The client-side deduplication process will consume as much of one (1) core of one processor as it can on that client system during deduplication calculations. While the actual amount of processor utilization will depend on the amount of data to be deduplicated and the speed of the processor, expect to see at least 75% processor utilization for that processor core for the duration of deduplication processing. During catalog operations, CPU utilization on the client is very low.
Backup Exec server-side deduplication performs the bulk of the deduplication calculations on the Backup Exec server. Similar to client-side deduplication, the Backup Exec server-side deduplication process will consume as much of one (1) core of one processor as it can on that Backup Exec server system. While the actual amount of processor utilization will depend on the amount of data to be deduplicated and the speed of the processor, expect to see at least 75% utilization for that processor core for the duration of any Backup Exec server-side deduplication backup job. For both client-side and Backup Exec server-side deduplication, initial backup jobs will be the slowest. As time goes on, backup speeds increase as more database fingerprints are created within the database.
For agents that cannot use client-side deduplication (Agent for Mac, etc.) there is no change to system requirements as outlined in the Backup Exec 2012 Administrator’s Guide. This is also true for Windows and Linux Agents that do not choose to use client-side deduplication.
Memory Utilization with Client-side and Backup Exec Server-side Deduplication
With both client-side and Backup Exec server deduplication, the majority of memory consumption takes place on the Backup Exec server. This is primarily a performance optimization geared towards fast and accurate calculation of deduplication fingerprints. On the Backup Exec server, both client-side and Backup Exec server-side deduplication require 8 GB (gigabytes) of free physical memory for the first 5 TB (terabytes) of deduplicated data stored by the Backup Exec server. For storage beyond 5 TB of deduplicated data, a formula of 1.5 x N, where N is the total number of deduplicated storage in terabytes, is used to calculate free memory requirements. For example, if 8 TB of deduplicated data is stored, the Backup Exec server would require at 1.5 x 8 GB, or 12 GB, of free physical memory.
Memory requirements for clients using client-side deduplication are not very stringent. Symantec requires 1.5 GB of free physical memory on each individual client that uses client-side deduplication.
Data Deduplication and Virtual Machine Backups
The Backup Exec 2012 SP2 Agent for VMware and Hyper-V enables optimised, image-level backups of both VMware and Hyper-V virtual machines. This is accomplished by capturing backups through communication with the VMware or Hyper-V virtual host. However, deduplication recommendations differ between VMware and Hyper-V environments being protected by Backup Exec 2012 SP2.
Deduplication of Image-level VMware Backups
While it is possible to utilise client-side deduplication when protecting VMware virtual machines, this configuration requires that backups be processed by locally installed agents within the virtual machines themselves (either the Agent for Windows or the Agent for Linux). This configuration bypasses the optimised, image-level backup capabilities of the Agent for VMware and Hyper-V in VMware environments that take advantage of Backup Exec’s advanced integration with the VMware vStorage API. For this reason, using client-side deduplication in VMware environments is generally not recommended. Backup Exec server-side deduplication is optimal.
Backup Exec Server-side Deduplication of VMware Image-level Backups
Deduplication of Image-level Hyper-V Backups
Client-side deduplication can be used when capturing image-level backups of Hyper-V virtual machines using the Agent for VMware and the Agent for Microsoft Hyper-V. In this configuration, optimised, image-level backups of virtual machines are captured and deduplicated through the Backup Exec Agent for Windows installed locally to the Hyper-V host. It is not necessary to install an individual agent into each Hyper-V virtual machine in order to realise client-side deduplication in Hyper-V environments.
Client-side Deduplication of Hyper-V Image-level Backups
VMDK and VHD Stream Handlers
Backup Exec 2012 SP2 includes stream handler technology designed specifically for image-level backups of VMware and Hyper-V virtual machines captured through the Agent for VMware and Agent for Microsoft Hyper-V. The stream handler technology within Backup Exec operates invisibly, meaning no additional management or configuration adjustments are required on the part of the administrator.
The stream handler technology within Backup Exec applies to both client-side and Backup Exec server-side deduplication. The stream handlers enable variable-length segmenting of VMware (VMDK) and Hyper-V (VHD) disk files during deduplication calculations. This aligns deduplication blocks to file extent boundaries within the virtual disk, and data changes over time within virtual disk files result in fewer unique blocks. This translates into better storage savings across both VMware and Hyper-V backups when using the Backup Exec 2012 SP2 Agent for VMware and Agent for Microsoft Hyper-V in conjunction with the Backup Exec 2012 SP2 Deduplication Option.
Combining the Agent for VMware and the Agent for Microsoft Hyper-V with the Deduplication Option can offer significant storage savings for Backup Exec administrators, allowing them to reduce storage costs by getting the most out of the backup storage resources at their disposal.
Additional information on the Backup Exec 2012 SP2 Agent for VMware and the Agent for Microsoft Hyper-V can be found in the Backup Exec 2012 SP2 Agent for VMware and Hyper-V Technical Feature Brief, and in the Backup Exec 2012 Administrator’s Guide and the Backup Exec 2012 SP2 Administrator’s Guide Addendum.
Data Deduplication and Storing Backups to Tape
An environment with a disk-to-disk-to-tape architecture is fairly common among customers who are interested in deduplication. It’s important to note that all of the Backup Exec 2012 SP2 methods of deduplication mentioned here are disk-based; deduplicated data is never stored directly to tape in its deduplicated form. However, the process of migrating deduplicated data to tape is very simple. Customers simply add an additional stage to their backup workflow that sends the data to tape storage.
Data Deduplication and Storing Backups to Tape
For data that was backed up using client-side or Backup Exec server-side deduplication, the Backup Exec server is responsible for “rehydrating” the deduplicated data – meaning the process of recreating whole files from deduplicated blocks – before transferring the data to tape. There will be some impact to processor and memory usage during the tape stage of the backup workflow due to the rehydration process. While resource consumption varies based on data set, at most the tape stage of the backup workflow will use 100% of one processor core while rehydrating deduplicated data and copying it to tape.
For data that was backed up to a deduplication appliance, the deduplication appliance itself is responsible for “rehydrating” the deduplicated data prior to it being sent to tape.
Modern Data Management and Protection Challenges
Customers of all types and sizes are seeking new and innovative ways to overcome challenges associated with data growth and storage management. While these challenges are not necessarily new, they continue to become more complex and more difficult to overcome due to the following:
- Pace of data growth has accelerated
- Location of data has become more dispersed
- Linkages between data sets have become more complex
Data and storage management challenges are compounded by the need for companies to protect critical data assets against disaster through backup and recovery solutions. In order to maintain backups of critical data assets, additional secondary storage resources are required. This additional layer of backup storage must be implemented wherever backups occur, including central data centers and remote offices.
Storage Efficiencies through Data Deduplication
Backup Exec 2012 includes advanced data deduplication technology that allows companies to dramatically reduce the amount of storage required for backups, and to more efficiently centralize backup data from multiple sites for assured disaster recovery. These data deduplication capabilities are available in the Backup Exec 2012 Deduplication Option.
Backup Exec 2012 Data Deduplication Technology
The data deduplication technology within Backup Exec 2012 breaks down streams of backup data into “blocks.” Each data block is identified as either unique or non-unique, and a tracking database is used to ensure that only a single copy of a data block is saved to storage by that Backup Exec server. For subsequent backups, the tracking database identifies which blocks have been protected and only stores the blocks that are new or unique. For example, if five different client systems are sending backup data to a Backup Exec server and a data block is found in backup streams from all five of those client systems, only a single copy of the data block is actually stored by the Backup Exec server. This process of reducing redundant data blocks that are saved to backup storage leads to significant reduction in storage space needed for backups.
Figure 1: Deduplication Process
The deduplication technology within Backup Exec is applied across all backups managed by a deduplication-enabled Backup Exec server.
Deduplication Methods within Backup Exec 2012
The Backup Exec 2012 Deduplication Option gives backup administrators the flexibility to choose when and where deduplication calculations take place. Three deduplication methods are supported by Backup Exec 2012. These are as follows:
The client-side deduplication method is a software-driven process. Deduplication takes place at the source or protected client, and backup data is sent over the network in deduplicated form to the Backup Exec server. Only unique blocks of backup data are sent to the backup server and saved to backup storage; non-unique blocks are skipped.
Backup Exec Server-side Deduplication
The server-side deduplication method is also a software-driven process. Deduplication takes place after backup data has arrived at the Backup Exec server and just before data is stored to disk (also known as inline deduplication). Only unique blocks of backup data are stored; non-unique blocks are skipped.
Third-party Appliance Deduplication
The third-party appliance deduplication method is a hardware-driven process and is driven by Symantec OpenStorage (OST) APIs. Deduplication takes place on the third-party deduplication appliance (can be in-line or post-process deduplication, for example, ExaGrid or Quantum). Third-party appliance deduplication devices handle all aspects of deduplication.
Administrators can mix and match deduplication methods to fit their unique needs. For example, a single Backup Exec server enabled for deduplication can simultaneously use client-side deduplication for some jobs, server-side deduplication for other jobs, and third-party appliance deduplication for yet another set of jobs.
Figure 2: Deduplication Methods
The different deduplication methods supported by Backup Exec 2012 have various configurations for which they are best suited. The benefits of each method, as well as the configurations for which each method is best suited, will be detailed in the following weeks.
Have you ever seen pictures of the control room in a power generation plant? It’s an entire wall of dials, knobs, and gauges, all telling you important bits of information about the system. That’s great – and probably necessary! – if your only job was to manage that power plant. But as an IT professional, you have lots of daily jobs; some of you manage Exchange, SQL Server, firewalls, security, storage, servers, you name it. Backup and recovery might be only one of the many jobs you do on a daily basis. And here at Symantec, we don’t want your backup application to be like that power plant – we want you to be
able to sit down, do what you need to do, and get on with your day.
Backup Exec has an entirely new user interface. You’re going to like it – it’s simpler, more intuitive, and much easier to navigate. We’ve also taken a lot of time to keep all those great features you are used to in previous versions of Backup
Exec – so this interface is going to appeal to the new Backup Exec user and the seasoned professional. At-a-glance status is easily available in Backup Exec 2012, both from servers you are protecting and from the storage you are using to store your backups. The latest version of Backup Exec is just a cleaner, more intuitive way to manage your backup and recovery environment.
We’ve also included a new way to create and manage backup jobs and policies. No longer do you need an advanced degree in Data Protection to set up disk-to-disk-to-tape backups or replicate data between sites – the new Backup Stages feature shows you, in graphical detail, how your backup data will be transferred, when it will be backed up, and where it’s going to be transferred to.
Speaking of backups, how many of you just want to create backups to protect your critical servers and applications without any headaches? How many of you would rather not pore over every detail of application backups? Well, if that sounds like you, Backup Exec has made it much easier for you to set up backup jobs, because we have included some seriously intelligent defaults – based off our own expertise in data protection and by taking the most successful backup configurations from
our customers and partners – and building them into Backup Exec. If you want to get into the nuts and bolts of backup job creation, however, Backup Exec has all the same great features and customizability you have used before – so you have the right tools to get the job done.
With Backup Exec, we’ve also stepped up our “telemetry” program – gathering non-personally identifiable information from our customers and partners who choose to participate in the program. This gives us invaluable intelligence about how backups and restores are working in the field, and we have used that information extensively to make Backup Exec the easiest to use, full-featured data protection application for physical or virtual environments on the market.
Be one of the first to find out what other new ground breaking backup and recovery features are coming soon in Backup Exec.
Visit the Countdown to Better Backup web site here: http://bit.ly/yenx3z
By Aidan Finley … Symantec’s Aidan Finley talks about simplifying intelligent backup: http://bit.ly/vHJXoa #BetterBackup [Video]
Most important in today’s economic climate is IT’s struggle to manage, control, streamline and provide services to the business. With increasing pressure to do more with less (don’t you love that phrase!), IT needs to reduce risk exposure by improving productivity, driving savings and consolidating suppliers through a standard set of management tools that helps exploit IT assets.
Inevitably over the coming months we will see some massive changes in our working environment. Organisations that are forced to reduce overheads or make massive structural changes are at risk of stretching resources just a little too thin. Conversely, organisational consolidations may suffer from exponential growth of email systems, increased numbers of servers or storage hardware to manage, with minimal resources to do so.
Consequentially organisations need to maintain the status quo by rapidly securing their new technology landscape. But whichever it is, the pressure to do more with less will only increase. So, in today’s uncertain climate, how can IT address the key business risks and opportunities, discover cost savings that are achievable by addressing spiralling utility costs, the data centre power shortage, and the evermore heat-generating equipment.
Organisations are faced with making sense of IT that has, for several years, grown out of control with increased resources that are inefficient and underutilised as well as dispersed and constrained by increased workloads and new deliverables or simply lacking in the skills required to maintain business objectives. Organisation therefore need to plan to address possible risks in the future.
IT’s role needs to be reassessed and be more, centralised strategic, innovative, at a lower cost; as well as being less distributed. How? With Backup Exec and Backup Exec System Recovery providing tools such as centralised granular management – saving in time, cost and resources.
Why buy/upgrade now?
· Optimising data protection for physical and virtual servers (VMware and Microsoft Hyper-V) through new Backup Exec Virtual Agents.
· Take advantage of improved server utilisation through streamlined backup of physical and virtual servers from one single backup application
· Reduce complexity heterogeneous of data recovery
· Meet strict recovery point objectives and service level agreements
· Recovery of critical data in seconds with patent‐pending Granular Recovery Technology (GRT)
· Continuous data protection for Exchange, SQL, file servers and desktops and laptops ensures backup jobs are continuously protected allowing businesses to restore data back to virtually any point in time.
· Infrastructure management – single, central console to run inventory, deploy Backup Exec version upgrades and patches
· Microsoft 2008 – Support for the Complete Windows Server 2008 Portfolio. Backup Exec can be managed from within single EBS Admin Console. Enhanced SharePoint Recovery
· Get the benefit of cost containment, enhanced recovery and execution across physical and virtual environments in the growing Windows and Unix/Linux server arena.