Link to home
Start Free TrialLog in
Avatar of Mark Lewis
Mark Lewis

asked on

Backup Exec 12.5, Exchange, and BSOD....Great combination!

I have been using BE9.1 forever to back up our Exchange 2003 server running on Windows 2003 Server Standard 32 bit. All was well. We just virtualized our environment and we virtualized Exchange as well as the backup server. This gave me oportunity to upgrade.

I installed a fresh install of BE12.5 on the lone physical server we have now which also runs vCenter if that makes a difference, uninstalled the 9.x backup client from the Exchange box and pushed the new client to the Exchange box from the BE console. I thought all was ok until...

I tried run a job and was getting a C++ Runtime Error. When I click the error, beremote.exe stopped responding and the client service would stop. Not a huge problem because the service would start back up fine but would fail if you ran the backup again. This occurred as soon as BE tried to talk to the agent...ie, no data would back up before the error.

I needed to backup Exchange, so I did the worst possible thing you could do in this situation and I called Symantec support. He had me run some cmd on the Exchange server in the BE folder that uninsatlled the pushed client. After a reboot, he had me copy the RAWS32 folder to the exchange server and install it locally. I did that.  

Now, when I try the backup, I still get the runtime error but with the added bonus of when I click OK the clear the error, my server blue screens and spontaneously reboots itsself. The most worrysome thing about this is the last time it did so, it was stuck on the Windows splash screen (the windows 2003 screen between the POST and the Windows is starting box) for about 10 minutes before it finally came back online. With users screaming for email, you can imagine I was sweating. Anyway, I told support that they were unhelpful and decided not to try another backup until I had some insight from someone who know what they are talking about.

Anyone out there that can help????? Please.
Avatar of big_daddy0690
big_daddy0690
Flag of United States of America image

Please review the following article to make sure your environment is setup correctly.

http://seer.entsupport.symantec.com/docs/288777.htm

If this doesn't lead you to a solution please provide more information on the error message. Do you have the error code from the backup exec log?
Avatar of Mark Lewis
Mark Lewis

ASKER

I looked at the article. Pretty sure the setup is correct. Again, it was working fine with 9.1. Here's a couple of sceens of what I am getting. Not much to go on. Where would I find the error code for BE?
Image2.jpg
Image1.jpg
Just because it was working fine in BE9.1 doesn't mean that it will automatically work in BE12.5. From your description it sounds like you migrated to Exchange 2007, is that correct? There are several prerequisites for BE12.5 and Exchange 2007 that were not required in your old environment. Please verify that all of them are meet and don't just be pretty sure.

To get the job log open Backup Exec, select the Job Monitor tab, right click the job that failed and select properties. In the job log tab click the link "See errors".
Nope, we are still on Exchange 2003. As for the job log, They are all cancelled...no errors. The job would just hang when the remote agent errored out on the Exchange server. Each job that hung, I would cancel the job and then have to restart the BE services to get the job to stop.
I can also stop a hung job by ending bengine.exe versus having to restart the services.

Navigate out to "C:\Program Files\Symantec\Backup Exec\Data". Here you should see several BEX_SERVERNAME_#####.xml files. You can use the search function to find the correct job log by searching for the job by name. For example "Resource Discovery". Also you will need to run the job and set it not to delete after completion. Still setting is in the schedule section of the job properties.
Heres one of the failed logs and thanks much for the help:

 <?xml version="1.0" encoding="UTF-16" ?>
- <joblog>
  <job_log_version version="2.0" />
- <header>
  <filler>======================================================================</filler>
  <server>Job server: GWBPCHEX1</server>
  <name>Job name: Monthly Archive - Databases</name>
  <start_time>Job started: Friday, October 16, 2009 at 9:27:32 AM</start_time>
  <type>Job type: Backup</type>
  <log_name>Job Log: BEX_GWBPCHEX1_00013.xml</log_name>
  <filler>======================================================================</filler>
  </header>
  <media_mount_date>Drive and media mount requested: 10/16/2009 9:27:32 AM</media_mount_date>
- <media_drive_and_media_info>
  <media_mount_date>Drive and media information from media mount: 10/16/2009 9:28:25 AM</media_mount_date>
  <robotic_library_name>Robotic Library Name: DELL 1</robotic_library_name>
  <drive_name>Drive Name: DELL 2</drive_name>
  <slot>Slot: 3</slot>
  <media_label>Media Label: SDLT126</media_label>
  <media_guid>Media GUID: {208b7d41-31bb-4de9-8b37-3a581ddbe54b}</media_guid>
  <media_overwrite_date>Overwrite Protected Until: 12/30/9999 7:00:00 PM</media_overwrite_date>
  <media_append_date>Appendable Until: 12/30/9999 7:00:00 PM</media_append_date>
  <media_set_target>Targeted Media Set Name: Monthly Archive</media_set_target>
  </media_drive_and_media_info>
- <backup>
  <filler>======================================================================</filler>
  <title>Job Operation - Backup</title>
  <append_or_overwrite>Media operation - append.</append_or_overwrite>
  <compression>Compression Type: Hardware [if available, otherwise none]</compression>
  <encryption>Encryption Type: None</encryption>
  <filler>======================================================================</filler>
- <machine>
  <machine_name>GWBMAIL1</machine_name>
  <info>Network control connection is established between 192.168.1.42:1767 <--> 192.168.1.8:10000</info>
  <info>Network data connection is established between 192.168.1.42:1782 <--> 192.168.1.8:37396</info>
- <set>
  <set_resource_name>\\GWBMAIL1\Microsoft Information Store\Primary Store</set_resource_name>
  <tape_name>Family Name: "Media created 10/15/2009 5:49:13 PM"</tape_name>
- <volume>
  <display_volume_as_alias>Backup of "\\GWBMAIL1\Microsoft Information Store\Primary Store" as ""</display_volume_as_alias>
  </volume>
  <description>Backup set #3 on storage media #1 Backup set description: "Monthly Archive - Databases"</description>
  <backup_type>Backup Method: Full - Database & Logs (flush committed logs)</backup_type>
  <agent_started>Microsoft Exchange Server Agent: Started</agent_started>
  <granular_restore_enabled>The option to enable the restore of individual items from the database backup was selected for this backup.</granular_restore_enabled>
  <start_time>Backup started on 10/16/2009 at 9:29:54 AM.</start_time>
- <OperationErrors Type="exch_store_comm_failure">
  <UMI>V-79-57344-65072</UMI>
  - The Exchange Store service is not responding. Backup set canceled.
  </OperationErrors>
  <end_time>Backup completed on 10/16/2009 at 9:32:28 AM.</end_time>
- <summary>
  <backed_up_exchange_store>Backed up 0 Exchange Server stores</backed_up_exchange_store>
  <new_processed_bytes>Processed 0 bytes in 2 minutes and 34 seconds.</new_processed_bytes>
  <vlm_hist_rateformat2>Throughput rate: 0.000 MB/min</vlm_hist_rateformat2>
  <compression_type_used>Compression Type: Hardware</compression_type_used>
  </summary>
  <empty_set_warning>This backup set may not contain any data.</empty_set_warning>
  <filler>----------------------------------------------------------------------</filler>
  </set>
  </machine>
  </backup>
- <footer>
  <filler>======================================================================</filler>
  <end_time>Job ended: Friday, October 16, 2009 at 9:33:53 AM</end_time>
  <engine_completion_status>Job completion status: Failed</engine_completion_status>
  <filler>======================================================================</filler>
  <completeStatus>6</completeStatus>
  <errorDescription>Final error: 0xe000fe30 - A communications failure has occurred.</errorDescription>
  <errorCategory>Final error category: Server Errors</errorCategory>
  <umiOriginator>79</umiOriginator>
  <justErrorCode>-536805840</justErrorCode>
  </footer>
  </joblog>



Here's the log when the server started rebooting itsself...just seems to stop prematurely:

<?xml version="1.0" encoding="UTF-16"?>
<joblog><job_log_version version="2.0"/><header><filler>======================================================================
</filler><server>Job server: GWBPCHEX1
</server><name>Job name: Backup 00010
</name><start_time>Job started: Friday, October 16, 2009 at 4:43:05 PM
</start_time><type>Job type: Backup
</type><log_name>Job Log: BEX_GWBPCHEX1_00021.xml
</log_name><filler>======================================================================
</filler></header><media_mount_date>
Drive and media mount requested: 10/16/2009 4:43:05 PM
</media_mount_date><media_switch_to_overwrite>
No appendable media could be mounted.
Switching to overwrite operation on scratch media.
</media_switch_to_overwrite><media_drive_and_media_info><media_mount_date>
Drive and media information from media mount: 10/16/2009 4:43:56 PM
</media_mount_date><robotic_library_name>Robotic Library Name: DELL 1
</robotic_library_name><drive_name>Drive Name: DELL 2
</drive_name><slot>Slot: 6
</slot><media_label>Media Label: SDLT151
</media_label><media_guid>Media GUID: {19b627a4-ff60-4df2-9704-14538e57a99e}
</media_guid><media_overwrite_date>Overwrite Protected Until: 12/30/9999 7:00:00 PM
</media_overwrite_date><media_append_date>Appendable Until: 12/30/9999 7:00:00 PM
</media_append_date><media_set_target>Targeted Media Set Name: Keep Data Infinitely - Do Not Allow Overwrite
</media_set_target></media_drive_and_media_info><backup><filler>======================================================================
</filler><title>Job Operation - Backup
</title><append_or_overwrite>Media operation - append.
</append_or_overwrite><compression>Compression Type: Hardware [if available, otherwise none]
</compression><encryption>Encryption Type: None
</encryption><filler>======================================================================
</filler><machine><machine_name>GWBMAIL1</machine_name><info>Network control connection is established between 192.168.1.42:4660 <--> 192.168.1.8:10000
</info><info>Network data connection is established between    192.168.1.42:4665 <--> 192.168.1.8:16428
</info><set><set_resource_name>\\GWBMAIL1\Microsoft Information Store\Primary Store </set_resource_name><tape_name>
Family Name: &quot;Media created 10/16/2009 4:43:05 PM&quot;
</tape_name><volume><display_volume_as_alias>Backup of &quot;\\GWBMAIL1\Microsoft Information Store\Primary Store&quot; as &quot;&quot;
</display_volume_as_alias></volume><description>Backup set #1 on storage media #1
Backup set description: &quot;Backup 00010&quot;
</description><backup_type>Backup Method: Copy - Databases &amp; Logs
</backup_type><agent_started>Microsoft Exchange Server Agent: Started
</agent_started><granular_restore_enabled>The option to enable the restore of individual items from the database backup was selected for this backup.
</granular_restore_enabled><start_time>Backup started on 10/16/2009 at 4:44:08 PM.
</start_time>
Can you also post the remote agent log file from the Exchange server. The path should be similar to this "C:\Program Files\Symantec\Backup Exec\RAWS\logs"
No logs there. Its clean.

C:\Program Files\Symantec\Backup Exec\RAWS\logs\dbagents is clean too.
Hmmm...Anyone have any ideas? I'm afraid to try another backup. Thankjs
Are you running CCleaner or something that might be deleting the logs?
No, nothing running on that machine but Exchange and IIS.It's almost like the agent doesnt get far enough along to create a log before it errors out.
ASKER CERTIFIED SOLUTION
Avatar of Mark Lewis
Mark Lewis

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial