Video Screencast Help
Search Video Help Close Back
to help

Backup and Recovery Community Blog

Showing posts tagged with 2012
Showing posts in English
PackMatt73 | 04 Jun 2013 | 0 comments
Location: 

 Google+ - http://buex.ec/beISOse

Time: 

 Wed, 12 June, 2013 - 13:00 - 14:00 EDT

Are you a Backup Exec user?  Do you ever have wild ideas about how you could better use this solution?  Ever run into a technical issue?  How would you feel about Hanging Out for an hour with a Systems Engineer & a Technical Support Engineer to go through whatever is on your mind regarding Backup Exec?

Backup Exec is pleased to announce a series of Google+ Hangouts beginning Wednesday 12 June at 1.00 pm EDT/10.00 am EDT 

These hangouts will be open...

Iesa Behbehani | 04 Jun 2013 | 0 comments

Backup Exec is pleased to announce that we are having a Google+ hangout on Wednesday June 12, 2013 at 1pm EDT / 10am PDT.  Our Focus is to have an open discussion with customers, partners, and employees about any questions or concerns regarding Backup Exec 2012.  Joining us will be two of Symantec's most knowledgeable technical experts.  Travis Larson, an Inside Systems Engineer and Michael McNally, a Technical Support Engineer will be fielding questions throughout the...

lmosla | 29 May 2013 | 0 comments

To get an accurate snapshot of your system requirements the first steps are to determine what supported deduplication storage device and the type of deduplication you are going to use prior to installing the Deduplication Option.
Use the Hardware Compatibility List to help establish the storage device type.

Storage Types:
There are currently two main options to choose from:
1. Backup Exec Deduplication disk storage devices:
o A 64-bit Backup Exec server.
o A Backup Exec server with either one quad-core processor or two dual-core processors.
o The location needs to be on a dedicated / non-removable volume.
o This dedicated volume must have at least 5GB of free space.

2. OpenStorage devices:
o The OpenStorage device requires a plug in or...

PackMatt73 | 16 May 2013 | 0 comments

 

A bank without money is not going to attract any customers. And while it’s unlikely that a sinkhole will suddenly appear and swallow up a vault, there is an important resource in business today that is all too vulnerable: information.

According to the latest State of Information Survey from Symantec, roughly half of an organization’s value can be attributed to the information it is generating and storing. And like the bank that needs to be able to loan out its funds to generate revenue through earning interest, information does companies no good if employees and customers can’t gain access to what they need.

There are a variety of factors that can put business information at risk today. Natural disasters, accidental deletions and malicious outsiders can all be as damaging to the average business as a robbery to a bank. In case disaster does strike, organizations need to know they have a solution that...

PackMatt73 | 10 May 2013 | 1 comment

 

Location: 

 Google+ Hangout (link below)

Time: 

 Fri, 10 May, 2013 - 13:00 - 14:00 EDT

 

Greetings Fans of Virtualization!

I have rounded up 2 Microsoft MVPs & a vmware vExpert for a G+ Hangout today at 1.00 EDT to discuss a White Paper they co-authored:

Virtual Machine Backup & Recovery: Five Critical Decisions...

@BackupMikko | 08 May 2013 | 0 comments

How far along are you on your virtualization journey? Most organizations already have more than half of their systems virtualized and are currently virtualizing their most business critical applications.

Now you are facing the challenge of keeping your ever-expanding virtual environment protected while providing the required service level for the business critical physical systems. Managing two separate isolated environments increases complexity and introduces potential for gaps in the data protection strategy if not carefully planned and implemented.

A poorly planned data protection strategy will not only increase risk to the data but will also consume more storage, restrict your recovery options and increase the time spent managing the environment. This is why it is important to understand the options and pitfalls when building a data protection strategy for virtual and mixed environments.

Host-level Integration and Virtual Machine optimized...

AshutoshTamhankar | 23 Apr 2013 | 0 comments

 

Snapshots created for a virtual machine on an ESX host, may not be deleted after a backup if the remote agent crashes abnormally during the backup operation. So that such orphaned backup exec snapshots can be deleted automatically, following registry key could be set:
 
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\VMware Agent
 
Key name Value Data type
AutoOrphanSnapshotRemoval 1 = Orphaned snapshots created by Backup Exec are deleted at the beginning of the backup. REG_DWORD

 

More information here: http://www.symantec.com/business/support/index?page=content&id=TECH200709

AshutoshTamhankar | 24 Apr 2013 | 0 comments

 

Simplified Disaster Recovery (SDR) works with Backup Exec when you run backup jobs that include all critical system component selections. For each computer that you protect with this type of backup job, Backup Exec creates a disaster recovery information file for that computer. A disaster recovery information file contains computer-specific information for the computer being backed up. Computer-specific information includes details such as hard disk layout, storage drivers, network drivers, and system version details. It also includes Backup Exec catalog details such as backup set information and recovery point details. Each disaster information recovery file uses the file name <computer_name>.DR.
 
If you uncheck files/folders from a critical resource, the green light for SDR goes off and no .DR file is create for the backup. Sometimes you might want to exclude files/folders which are temporary for example. Following registry change...
AshutoshTamhankar | 17 Apr 2013 | 0 comments
The size of the read and write buffers used for the VWware API (VDDK) by Backup Exec can be tuned using the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\VMware Agent
 
"Enable Buffered Reads"=dword:00000001
"Number of Read Buffers"=dword:00000004
"Size of Read Buffers"=dword:00000400
"Enable Buffered Writes"=dword:00000001
"Number of Write Buffers"=dword:00000004
"Size of Write Buffers"=dword:00000400

More info

If you are looking at tuning performance of your backups generally, recommend you to go through the Backup Exec 2012 performance tuning guide:

The...

lmosla | 12 Apr 2013 | 0 comments

LiveUpdate's task is to keep Backup Exec fit, healthy, and up to date.

Times to run LiveUpdate:

For new installations:

When having issues with Backup Exec

Periodically during scheduled times

When upgrading Backup Exec:

  • Run LiveUpdate following a new installation.

Note: Keep checking for LiveUpdates until LiveUpdate is completely up to date and there isn’t any updates left to install (Reboot as necessary).

  • Run LiveUpdate before and after a Backup Exec upgrade.
  • Schedule LiveUpdate at convenient times when there aren’t any jobs scheduled.  The Backup Exec services are restarted during updates.

Note:  Avoiding SQL Conflicts: When Backup Exec is installed use Backup Exec own inbuilt SQL instance (SQL Express) to host the Backup Exec database.  Do not use a SQL instance that is used in production. When updates are ran...