Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup Exec
Showing posts in English
A L Johnson | 24 Nov 2014 | 17 comments

Solve problems, share knowledge, and earn rewards!

By connecting with your LinkedIn profile and completing a 3 question survey, we'll get to know more about your unique interests to ensure we provide the solutions, technical knowledge, and product ideas most important to you.

As our way of saying "thanks" for taking the time to give us your feedback, from now until the end of the year, we'll give you 100 points towards the Symantec Connect Rewards Program in return!   Just click here:  http://symantec-connect.apps.umbel.com/880/symantec-connect/ to get started.

If you don't have a LinkedIn Profile or would prefer not to connect via LinkedIn, you will be given the option to "Skip"  and you'll be taken straight to the survey.

Thank you for helping us continue to improve your Connect experience. 

@BackupMikko | 18 Dec 2014 | 0 comments

We are excited to announce Amazon Web Service (AWS) Storage Gateway VTL support for Backup Exec 2014. The AWS Storage Gateway VTL enables Backup Exec 2014 customers to expand the powerful media management capabilities of Backup Exec to Cloud Storage.

AWS Storage Gateway VTL integration accelerates IT agility for Backup Exec 2014 customers by seamlessly migrating existing backup jobs to cloud storage by simply adding another job stage or by replacing existing storage destination with the AWS VTL.

The seamless integration enables anybody to take advantage of Cloud Storage benefits like automation, elasticity and Pay-as-you-Go directly from Backup Exec 2014 without spending time and resources learning and managing new products or re-architecting environments.

...

Nick Elmer | 01 Dec 2014 | 0 comments

Backup Exec Install Blog (VC Runtimes)

Backup Exec 2014 has had a warm reception in the field, and it is so good to see the excitement around the product return!  From my point of view, there were only a few customer-facing changes on the install side for this release. One of those changes was a shift in how we install Microsoft Visual C++ Runtimes with the product. This blog will attempt to explain that shift and the reasons behind it.

What is a VC Runtime and why do you care? Well, the Microsoft Visual C++ Runtimes are basically a set of files Microsoft delivers to application vendors, like Symantec, who build Windows applications on top of them. Essentially, runtimes provide the interfaces Backup Exec needs to get work done on a Windows system. They are delivered in two ways:

  1. As a standalone installation package that vendors can install before their application
  2. As a "Merge Module" that gets embedded into a Windows Installer...
Keith Fields | 24 Nov 2014 | 15 comments

We are pleased to announce that the beta program for the next release of Backup Exec, Backup Exec 15, is open for registration. This beta allows new and existing Backup Exec customers the opportunity to test, validate, and provide feedback on this upcoming release.

This beta release can be installed in both lab and production environments in all languages supported by Backup Exec. 

What’s new in Backup Exec 15?

Backup Exec 15 delivers powerful, flexible and easy-to-use backup and recovery for virtual and physical environments. By participating in the beta, you can be among the first to evaluate newly-supported platforms and reliability enhancements. Your feedback on product stability, features, and performance will help us to continue delivering a high quality product that you can trust. Backup Exec 15 includes:

·      Support for VMware vSphere 2015...

Drew Meyer | 10 Oct 2014 | 0 comments

Symantec shipped our first version of Backup Exec software (Backup Exec 10d) nearly 10 years ago to provide small-to medium-sized businesses with fast and reliable data protection. One of our valued customers called the recent release of Backup Exec 2014 “the backup and recovery gold standard” because it delivered the critical platform support he needed to protect both virtual and physical environments. Today we’re here to share some recent milestones and important updates about the Backup Exec product line going forward.

Symantec-BE-Appliance_3600.jpgNew Software for the Backup Exec 3600 Appliance

For Backup Exec 3600 appliance customers, Backup Exec 2014 software with requested support for Windows Server 2012 and Windows Server 2012 R2 is now available for you to download. You should have...

Susie Spencer - BE Product Marketing | 22 Sep 2014 | 20 comments

We’re excited to announce that Backup Exec 2014 Service Pack (SP) 1 is now globally available and includes the following enhancements:

  • Simplified Disaster Recovery (SDR) for Windows Server 2012 R2 and Windows 8.1
  • Oracle 11.2.0.4 support
  • Red Hat Enterprise Linux 5.10 (RHEL) with AOFO (Advanced Open File Option) support
  • Red Hat Enterprise Linux 5.11 (RHEL) without AOFO
  • Microsoft SQL 2014 (Repository)

Customers with existing Backup Exec 2014 deployments can download the Service Pack today at http://www.symantec.com/docs/TECH216178. Availability via Live Update is expected to follow within the next 3 weeks.

Backup Exec 2014 installation media with SP1 embedded will be available 5-7 days after the initial release of the service pack from either the trialware link on backupexec.com as well as FileConnect by visiting...

A L Johnson | 21 Sep 2014 | 0 comments

Symantec Logo.jpg

Let us know if you are going to SpiceWorld Austin this year by signing in with your LinkedIn profile here: http://bit.ly/1oXEVjE and stop by Symantec's booth #3 and find out how you can WIN a LittleBits Electronics Deluxe Kit and GoPro HERO3+ Black Edition!

We will have Product and Tech Support specialists there to answer your questions and share some of the latest white papers from Symantec.

Digital_Kru | 25 Aug 2014 | 0 comments

word cloud.jpg

As an IT administrator, there are few things which conjure more of a sick feeling in the pit of one’s stomach than a disastrous event which corrupts or loses company data. Data is the second currency of a business after actual currency, so losing it is not an option. These disastrous events take all kinds of forms including natural disasters, data breaches from hackers, accidental data deletion, and a myriad of others. Even something as small as an engineer spilling coffee on a system could wipe out the server and any virtual servers running on it.

However, statistically the data shows us that most organizations are not implementing a disaster recovery plan. In 2012, Symantec’s SMB (worldwide organizations with less than 250 employees) disaster preparedness survey found that despite its importance,...

Nick Elmer | 18 Jun 2014 | 2 comments

Today's blog is designed to help some of our customers with an issue they may experience during the upgrade to Microsoft SQL Server 2008 R2 Express with Backup Exec 2014. We are seeing a number of failures that return the following error in the install log: "Failed to install SQL Express BKUPEXEC instance with error -2067922409". If you review the summary.txt for the SQL Server 2008 R2 Express install failure, it will have an error like this "One or more selected features for upgrade have failed the SID check."

What does this mean? Well, the SQL 2005 Express installs (which were done by previous Backup Exec installs) created a few NT security groups for managing access to the Microsoft SQL server services. You can see these groups by going into "Computer Management" MMC snap-in and expanding the "Local Users and Groups" item, and clicking on the groups item. Within that item you should see items like "...

Nick Elmer | 09 Jun 2014 | 8 comments

Hello again! Today, I want to address a question that I anticipate some customers may ask: "Why does Backup Exec 2014 install a 32-bit instance of Microsoft SQL Server 2008 during clean installs and upgrades?"

This topic received much discussion as we were deciding which version of SQL to use for Backup Exec 2014. There were several requirements:

  1. The Microsoft SQL Server 2005 primary instance needed to be replaced due to its age and diminishing support.
  2. We have to support legacy OS platforms like Microsoft Windows 2003 Server and support for newer platforms like Microsoft Windows 2012 R2.
  3. Customers using older releases need a migration path.
  4. Customers may experience failures when upgrading to a newer SQL instance, and they need a clean, workable rollback.

The only version of SQL that met all of those requirements and provided the best solution for our customers was Microsoft SQL Server 2008 32-bit, which:

  • ...