Video Screencast Help
Backup and Recovery Community Blog
Showing posts in English
Dyneshia | 11 Dec 2012 | 0 comments

Providing the following information when creating a GRT Exchange case will not only help the TSE narrow down the issue, but will help resolve your case faster and more efficient.  This information will help the TSE outline an action plan before the first call back and WebEx.

What is GRT ? Granular Recovery Technology allows you to restore, at the most granular level meaning an individual piece of mail rather that the whole database.  If you are unsure you are using GRT , look at your policy attributes.  If the box 'enable granular recovery' is checked, then you are using GRT.  If it is not, please refer to this blog :

https://www-secure.symantec.com/connect/blogs/what-information-and-logs-include-when-creating-exchange-case-support-non-grt

Please provide the following informaiton...

Joan Garcia | 21 Jul 2014 | 0 comments

Today I would like to share a few thoughts about the hidden risks there are when we make decisions or choose new types of technology. Technology by itself is not risky (cloud, replication, snapshots, backup,...) but each kind offers some functionalities but also has some limitations.

Risks usually come when technology is chosen without taking into consideration its limitations and, even more importantly, without understanding that the ultimate responsability lies with organitzation that adopts the new technology and it is also this company which is the most affected when something goes wrong. So, these companies must undestand and try to mitigate these risks everytime they choose a new technology because most of the time SLAs and penalities are meaningless and useless when it comes to a major issue in a critical environment.

To exemplify this point, I'll share the CODESPACES case.

Last month (June 2014), a company called CODESPACES.COM (...

melview1 | 17 Jul 2014 | 1 comment

I wanted to share my problems and solution regarding Backup Exec 2012 and the Service Pack 4 update in hopes it might help others.  I’ve seen several threads on this topic, but the official response from Symantec has always been, “there are no known bengine SP4 issues”, which I’m not convinced of.  My maintenance is not current for reasons I won’t get into, but because of that, I have not filed a tech support request on this topic, but rather figured it out on my own.  I’m evaluating my needs vs BE2014, which I’d reinstate my maintenance for.

My setup is fairly small and simple.  I have 6 servers being backed up, including the BE server.  1 is using an Agent for Applications and Database server and the rest are Agents for Windows.  Each server has its own job that is a backup to disk (external USB3.0).  There are 4 disks, 3 have unique jobs and 1 of them is shared amongst 4 jobs.  No jobs overlap and there is no...

goli123 | 15 Jul 2014 | 1 comment

Hello everyone.

I'm not sure if it's only us that get this problem in the new backup exec (2014) but if it's not just us I would to share the workaround we found with you.

Our Backup exec servers have several network interfaces in different networks and we noticed that if not specified which network interface to use some of the jobs fails. We configured all of our backup jobs to use the correct interface but after we rebooted the server to install some updates we noticed that this settings were lost during the reboot. After a second reboot we saw this problem again and we decided to solve the issue via power-shell script that I'm going to share here with you.

To reset the right network interface to all of our jobs we used this code:

$inter = Get-BENetworkInterface InterfaceName
Get-BEBackupDefinition | Set-BEBackupDefinition -NetworkInterface $inter -NetworkProtocol IPv4 | Save-BEBackupDefinition -Force

After that we created a...

Morten Seeberg | 25 Jun 2014 | 0 comments

FYI - I chased this down via a support case, because I was concerned that this information was so difficult to find and I believe this kind of information should have been more easily available to us(?)

The below issue is referenced in:
http://www.symantec.com/business/support/index?page=content&id=TECH218263

Short summary;: There is risk of corruption in SyBase (EMM and OpsCenter although note only mentions OpsCenter) on RHEL. Issue is between SyBase and RHEL Transparent HugePage features. It is not currently known to support whether issue is fixed in RHEL 6.4/6.5, but no matter what, it requires a fix in SyBase as well, which MAY be included in 7.6.0.3.

Until then, here is the workaround to disable THP in RHEL:

RHEL 6.x: /etc/sysctl.conf #Disable Transparent Huge Pages - Symantec TECH218263 transparent_hugepage = never...

nisharamach | 23 Jun 2014 | 0 comments

Join Symantec Backup Exec experts for a Tweet Chat on Friday, June 27 at 11 a.m. PT / 2 p.m. ET to chat and learn more about Backup Exec 2014.

Backup Exec 2014 released earlier this month brings in a host of powerful features that will help you save time, get more reliable backups, enable fast & easy recovery.

Learn why you should consider upgrading or moving to Backup Exec 2014. Mark your calendars to join the #BETALK chat and plan to discuss the latest features and improvements in Backup Exec 2014 and any particular backup needs that you have.

Topic: Backup Exec 2014 – What’s new?

Date: Friday June 27, 2014

Time: Starts at 11:00 a.m PT / 2:00 p.m ET

Length: One hour

Where:  Twitter.com – Follow hashtag #BETALK

Expert participants:

  • Michael Krutikov...
Elspeth Magoria | 11 Jun 2014 | 0 comments

solve2-img.jpg

 

Virtualize the Right Way and Solve Your Backup and Recovery Challenges With Backup Exec 2014

Learn how to solve your biggest backup challenges at our live streaming event on June 17.  See Backup Exec 2014 in action; hear from Symantec executives, customers and partners; and get the latest tips and tricks for protecting your data.

What will you gain when you can recover anything in minutes, get up to 100% faster backups, and take advantage of an easy to use solution that protects your virtual and physical environments? Find out how you can save time and money, deliver better virtualization, and complete Disaster Recovery with Backup Exec 2014. superior visibility into backups with the job monitor view and multi-server backup jobs; new platform, virtual and application support; intelligent...

John Meaders | 09 Jun 2014 | 0 comments

Earlier this year I was engaged to install NetBackup on a Solaris server which previously used a competing backup product.  This server only backs itself up and is attached to a single drive tape autoloader.  I initially thought I would use a single NetBackup policy to back this server up but it quickly became apparent this wouldn’t work as one filesystem took forever to back up - which would push the backup way beyond the desired 8 hour backup window.

This filesystem contained millions of small files.  At this point, you are probably thinking - simple - just use FlashBackup.  Unfortunately, the customer was only licensed for the Standard client and this project was already an out-of-budget expenditure, so further expenditures would be very difficult.  The other items on this server that needed to be backed up were Oracle dump files, along with the OS directories.

I performed some research and after viewing a couple threads here on Symantec...

Solange Deschatres | 28 May 2014 | 0 comments

At Symantec, we often talk about information and data as the lifeblood of the business, especially in today’s digital world. Whether it’s in the form of financial reports, emails or software — information powers our world. If companies lose that information, or worse yet, entire platforms running that data, business comes to a screeching halt.

Imagine for a moment that your Microsoft Exchange email service is disrupted by data loss – months of information gone. With your system down, you’ve not only lost work but you have to stop doing business, selling products and communicating with your customers. The disruption isn’t just a headache for your IT department; downtime causes frustration across the company. Ultimately, data loss, either accidental or deliberate, costs your business valuable time and money so it’s essential that you protect your information before disaster strikes.

The majority of yesterday’s backup technology isn’t sophisticated enough to protect...

BalaP | 17 Apr 2014 | 1 comment

Hi,

 

After configuring the Backup Exec 3600 Appliance we are getting email for every 10 mins stating proxy error not able to communicate to server to upload call home data.

 

 

CALLHOME status: Not able to upload callhome data

Error: 500 SSL read timeout:

Please contact Symantec Support to resolve this issue.

 

CallHome Proxy Show

 

Proxy Settings

        Server    : https://Ipaddress

        Port      : 8080

     

This issue resolved after adding "s" to http, since the data is sent through secured http.

Thanks,