Dennis,

 

Just to confirm.  You are not seeing  the jobs that the name is changing on show up in the Aptare Running and Queued Jobs Summary canned report?  If not, can I pass on your name to Aptare support to contact as to what is different in your environment then mine?

 

 

Mike,

 

I am seeing the name change on the job. At the start it’s the mailbox server and the end of the job it the DAG. And we only have the DAG as the client in the policy. We have 4 mailbox servers in the DAG and are backing up the passive copies so I’m seeing all 4 mailbox servers showing up with jobs running against them and they all show the same behavior you described as to the name changes but I’m not seeing the issue in Aptare that you’re experiencing at all.

 

 

Dennis,

 

Can you run a bperror –L –jobid <jobid> for one of the dag copy backups(i.e. one of the child jobs not the parent job) and see what it is reporting at the start of the backup as client name and what is reporting at the end as client name?  Also verify that your policy for Exchange has only the DAG name as a client?

 

 

Mike,

 

We’re not seeing that behavior in Aptare it appears to be handling the Exchange 2010 backups without an issue at all.

 

 

 

Dennis,

 

Same versions here.  Can you check your Queued and running report in Aptare to see if your Exchange backups are showing there.  That is my issue, since Aptare uses backup id and client name to check to see if a backup completes, it is reporting my Exchange backups as either queued or still running.  In my case the client name at the start of the stream is reporting the physical Exchange server that the DAG is on as the client name, but when the backup id completes it is listing the DAG name as the client name.

 

 

We’re running Aptare and doing the Exchange 2010 backups and we’re not experiencing that problem. Aptare is displaying the mailbox server jobs as finishing but there is no job data to speak of you have to go to the DAG to actually see what the jobs had done. We’re running NBU 7.1.2 and Aptare 8.1.2.

 

 

 

Anybody using Aptare Storage Console and doing Exchange 2010 Backups?  I am having an issue where the reports in Aptare are incorrect because the client name is changing from the physical Exchange server at the start of each stream to the DAG name at the end of the stream.  So Aptare is reporting that those jobs are still running or queued.  Been bounced between Aptare support and Symantec support on this issue.  Aptare is saying client name should not change and Symantec saying that the name changing is how DAG backup work.