Backup Exec Test Run

[Narkis Eatman]

When you run your backups make sure that you run a verify job (Tools / Options/ < verify checkbox checked). The Verify job checks that data can be read or restored from the media. The best way to really ensure your media is being backed up correctly you should run a test restore job.

Glad to hear that you are running the verify on each job to ensure the integrity of the backup sets and the storage on which it resides. Randomly testing a file here and there while not ideal is better than not testing at all. At least you will have some familiarity with the restore process but it is still no substitue for the real thing. I understand that your are limited in the machines you are able to test with so while you are unable to test bare metal restores we may be able to perform some more substancial restore of the apps youre backing up. For example if youre backing up exchange we would be able to test mailbox/Granular restores by redirecting to a test mailbox, or perhaps testing a DB restore by running a D.B. restore to a RSG or RDB depending on what version of exchange. As MrBostn is im curious as to what is is that youre backing up and looking to test.

I see the only real way to do this over and over till you are comfortable is with a VM - to this end I thought I would be able to set up a VM with W7 on it and install BE and have a go. But when I install it, it will only let me install the remote agent. I think it is because the machine is just a workgroup. But when it all hits the fan and you are sourcing a server, I think you are likely to want to test just a backup + any workstation + backup software or even like you can with Acronis, just use their recovery CD. At least if you could see, touch, restore the files you would be a lot more comfortable,

You know, there is an opportunity here and for a while (till internet connections are super fast - still on < 1MBit up), that a company could offer a VM ready, you mail them the drive, they mount it and you get walked through a test restore. I would pay a few hundred for that once a year.

I think it is the same thing when I was using BE and trying to backup CIFs shares on a filer. Its because the BE server tries to connect on port 10000 which is normally used for NDMP on a filer. BE server would expect an agent (process=beremote.exe) on this port but in this case its NDMP listening which it cannot communicate with.

Disable NDMP on the filer or create a symlink to the CIFS share locally on your BE servers file system using the mklink command. Then back this up in the selection list choosing to follow symlinks/mount points.

We're also using BE12 and Ontap 8.1 but with a 3240. Same issue. NDMP is disabled on the filer. We're able to map the CIFS shares on the BE server using the service account but are presented with "a network connection to the server could not be established" when trying to add them as a selection within BE. Our BE server runs Server 2003 and so we can't use Symbiotic Links. Any suggestions?

We are running BE12 and I was experiencing the same problem. Turnin goff ndmpd , really worked. I could connect to shares but would not allow backups or selections. Once I turned off then I could at least backup but what bugs me is, when I test Operator credentials, it reports failed but you I can just open the shares fine on the same machine. I created account called backup op and it has full access to all the shares from windows side (no problem here) but thru BE, When I click on test access it fails. Kind of annoying but at least it is finishes backups. I just wish it was a bit faster. It takes shorter time to back windows boxes than netapp.

I have a media server, Windows Server 2008 SP2 running Backup Exec 2010 R2. The SQL and other Windows agents work but I cannot backup the Exchange 2010 server running Windows Server2008 R2. I have the correct license for the Exchange agent - installed on the media server, and I installed Exchange Management tools on the media server.

The 'Microsoft Exchange Database Availability Group' option is greyed out and if I select the server under a new backup job I can expand the 'Microsoft Information Store' option and see the mail database name but showing 0Kb.

When I try to back it up it gives an error displaying: The job failed with the following error: Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again.

Ben you were the closest, I got it working thanks to help from Gautam Khadse at Symantec. The user used by Backup Exec to do the backup job - in my case a user called backupexec - had to be placed explicitly as a local admin on the Exchange box, regardless of the fact that it had Domain Admin rights (which in my case automatically made this user a local administrator on the Exchange box).

All the other pre-requisites were also followed and the user also had the Exchange Organization Management role. The user's credentials also tested successfully in the new backup job dialogue box. This fix was not in the documentation, but worked for me.

My config is the same, remote agent on the exchange server and I am licensed for exchange. So when I create a new backup job I can drill down to the exchange server, drill down from there and select the "information store". Using brick level backup.

So I guess I am not really answering your question, but possibly asking another. Is there something else I need to be backing up? I have been getting good backups of the information store, and have done restores?

2. Verify Exchange Agent Installation:Check Exchange Agent is installed correctly on Backup Exec media server or if using remote agents, ensure that it is installed correctly on the Exchange server.

3. Ensure Correct Exchange Management Tools Installation:Check correct version of Exchange Management Tools is installed on the media server, also should match with Exchange server's version.

4. Update Selection List:Check if Correct mailbox databases are selected for backup. If the mailbox database is showing as 0KB,then Backup Exec is not able to properly recognize the Exchange database.

5. Check Database Availability Group (DAG) Configuration:If you're using a DAG configuration, ensure that DAG is correctly set up. All DAG members should properly visible to Backup Exec.

9. Review Event Logs:For getting more insights, Check the event logs on both the media server and the Exchange server for any relevant error messages or warnings. then you will get the clear idea about the issue.

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

At Veritas, our aim is to help you with market-leading data protection solution, all the way from easy installation and initial deployment to backing up production workloads with Backup Exec with confidence. There are several tools which can help you automate tasks, maximise performance, diagnose and resolve issues when software fails or your hardware breaks.

Backup Exec ships with a PowerShell module called BEMCLI. One of the changes that we made few years back was move from the old commandline interface (BEMCMD) to BEMCLI. BEMCLI is based on Powershell which is a more powerful scripting language than the DOS commands. Needless to say, to fully exploit BEMCLI, you got to be familiar with Powershell.

The Veritas Quick Assist (VQA) is a diagnostic tool and helps you with Auto-detection of issues (self-help). It also gathers data for Veritas technical support assisted troubleshooting This help support analyse the information they need to troubleshoot issues, but this tool is available for anyone to use.

Veritas Backup Exec Migration Assistant lets you migrate your data from one Backup Exec server (source) to another Backup Exec server (destination). You must run the Migration Assistant on the destination server.

The Cloud Connect Optimizer feature in Backup Exec allows you to quickly test your network and suggests parameters that will help ensure the backup to cloud operations are performing optimally. It does this in an automated fashion thereby saving a lot of time and effort in fine tuning these parameters.

The Backup Exec B2D test tool is a stand-alone tool intended to test the basic functionality of a device as it relates to being used as a Backup-to-Disk device in Backup Exec. If a device passes these tests, it will be treated as fully supported by the Backup Exec tech support team.

It is cloud based monitoring solution from Veritas which allows service providers and administrators of Backup Exec to monitor multiple Backup Exec media servers in a single view. Arcus can get you a quick overview of all Backup Exec deployments without having to connect to all Backup Exec servers one at a time.

The Backup Exec Environment Checker is a utility that can be run on a computer to report if the computer meets theminimum requirements for installation, such as the operating system, disk and physical memory, sufficient logon account privileges.

With the Backup Exec Utility, you can do a variety of tasks like adding, removing, and configuring logical groups of Backup Exec servers or starting database utility operations on the Backup Exec Database (BEDB).

The begather utility brings together the files that help you diagnose issues with Backup Exec components on Linux servers. After you run it, the begather utility displays the name of the Packet file that it creates.

The files that are gathered contain detailed information regarding installation, diagnostics, and error reporting. Reviewing these files before contacting technical support can reveal the source of the issue.

The Backup Exec Debug Monitor, or SGMon, is a diagnostic tool that captures debug output from Backup Exec and saves it in debug logs. SGMon debug logs can help you troubleshoot backup issues. Furthermore, debug logs can help Technical Support diagnose and repair problems.

c80f0f1006