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

Michael G Andersen | 14 Aug 2014 | 0 comments

When troubleshooting database backups, it is important to remember that a database backup is in principle an user initiated backup,
so the backup is actually started from the client by the script/database backup api.

The database backup is more sensitive to name resolution than file backup, partly because of the above

 

 

Places to look for information/things to do:

The activity monitor, probably where you would see the error first.

The bphdb log folder which gives the script exit status, environment information and other things there can help figure out what the issue is.

The dbclient log folder with 777 permission which gives detailed information about the backup done by the database api e.g. rman

The database api's log e.g. rman messagelog

The database's log e.g the alert log for Oracle

The OS system logs, but often this a copy of the messages from the database's logs

...

Shashank_Mulay | 11 Aug 2014 | 6 comments

I am really excited to announce that Symantec Desktop Laptop Option (DLO) 7.6 is generally available!

 

What’s New in DLO 7.6?

This release is based on the theme Proliferation, Stability and Supportability.

 

Proliferation:

  1. Mac Agent: DLO now supports backups on Mac desktops and laptops. Mac OS X support is provided for 10.7, 10.8 and 10.9 OS releases.
  2. Platforms: DLO now supports Windows 2012 R2 for server installation.
  3. Mail Client Support: DLO extends its support to IBM Lotus Notes ® 9.X release.

 

Stability:

  1. Automatic Integrity Checker (AIC): Validates the reliability and integrity of data. AIC runs in the background and does not affect the system performance.
  2. Bandwidth and CPU throttling: Ability to configure the maximum amount of bandwidth and CPU cycles the Desktop and Laptop Option can...
Walker_Yang | 04 Aug 2014 | 0 comments

For some people, it might be a little bit hard to find the documents and patches for NetBackup easily and efficiently. Here provide a simple way to find them, just remember Symantec official web site and simple navigation link, that's all you need to do.

1. Visit Symantec offical web site: www.symantec.com, scroll down and click "Supported Products A-Z".

1.png

2. In the supported product list, choose the product you want. Scroll down and click "NetBackup Enterprise Server"

2.png

3. Now we've entered into NetBackup Enterprise Server Technical Support web. Here we can find the documents and files, as follows:

3.png

4. Click "Documentation", you'll navigate...

Cristiano S. | 25 Jul 2014 | 0 comments

Hello to everyone,

I was facing problems while configuring a backup exec job with Oracle RAC over Linux environment.
I would like to share how it was solved.

Scenario:

Using Symantec Backup Exec 2012, Oracle RAC and Red Hat 6.3

Problem:

While configuring a backup exec job with oracle RAC, on 'Backup Selection' tab it was not possible expand Oracle RAC database tree.

Error messages: Oracle Database "Instance"(Unavailable) or Authentication failed on connection

Solution:

Add O/S user that has DBA privileges (the owner of oracle binaries) to the beoper group
Copy /etc/oratab to /etc/VRTSralus/beoratab
Do not eeplace the dbname entries in /etc/VRTSralus/beoratab with the name of the instance of the RAC database on that machine. Keep the same.
This example uses the root account to configure the...

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 | 2 comments

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