Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

September 23, 2003 12:00 AM

Solving an Exchange Backup Problem

Windows IT Pro
InstantDoc ID #39952
Rating: (0)

I recently upgraded to VERITAS Software's VERITAS Backup Exec 9.0 to take advantage of the version's new public-folder backup options. But since the upgrade, I can no longer successfully back up my Microsoft Exchange Server system. In fact, running an Exchange backup sometimes results in my Exchange server rebooting. Have you encountered this type of situation?

Yes, this type of server reboot is a known problem in Backup Exec 9.0. (Backup Exec 9.0 can also result in a reboot of Network Appliance's Network Attached Storage—NAS—servers if you aren't careful.) The first thing to do is to make sure that you've properly installed the Backup Exec 9.0 Remote Agent on the Exchange server. To make sure that the agent is installed properly, remove whichever agent is currently on the Exchange system (the Remote Agent from earlier Backup Exec versions is incompatible with Backup Exec 9.0). Then, reboot the system, delete the \veritas directory (I'm assuming that Backup Exec isn't installed directly on your Exchange server; if it is, it shouldn't be), and install the Remote Agent that ships with Backup Exec 9.0.

Next, open the backup job that includes the Exchange server. Go to the job's backup selections and clear the Connect$ check box from the list of directories to be backed up on that server.

Related Content:

ARTICLE TOOLS

Comments
  • Anonymous User
    7 years ago
    Feb 04, 2005

    Because it's retarded. A box consumed with generally a 500mb to 1.5gb Mail store process, doesn't need to be overwhelemed with a bullying process like backup exec server. That software is not only extremely buggy, it's a known concern. Any known concern will never find it's way near my exchange mail store.

  • Ron Rosenkoetter
    9 years ago
    Sep 29, 2003

    One quick question... why shouldn't Backup-Exec be installed directly on an Exchange Server?? Every one of our servered (is that a word? Sites with a server) remote sites has two servers. A DC, and a File\\Exchange Server.

    The File\\Exchange Servers all have DLT Autoloaders attached and are running Backup-Exec 8.6. I've never had any real problems backing up these servers.

    I DO need to upgrade to Backup-Exec 9.0 (We'll be upgrading the DCs to Windows 2003 soon, and only 9.0 can backup Windows 2003 servers). Can you tell me more why you do not recommend Backup software on the same server as Exchange?

    Thanks!

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.