Backup Central

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.

We had a similar issue with Aptare and vmware backups. For all vmware
backups, NetBackup was reporting the name of the ESX server as the client
name, and not the name of the VM itself. We kept pressing Symantec, and
they relented and fixed it.
--
Jack Forester, Jr.
Sr. Data Protection Administrator
Global Technology Services - AHS
Mylan, Inc.
5005 Greenbag Road
Morgantown, WV 26501

jack.forester < at > mylan.com

Phone: +1.304.554.6039
Cell: +1.412.805.5313



From: "Kelczewski, Mike" <KELCZ < at > coj.net>
To: "veritas-bu < at > mailman.eng.auburn.edu"
<veritas-bu < at > mailman.eng.auburn.edu>
Date: 12/06/2011 02:17 PM
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage
Console.
Sent by: veritas-bu-bounces < at > mailman.eng.auburn.edu




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.
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



==============================================================================
CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you.
==============================================================================

_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

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.
Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
Tel:608.664.8236 Cell:608.333.6682
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Kelczewski, Mike
Sent: Tuesday, December 06, 2011 1:17 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage Console.




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.

Jack,

I think Aptare gave me you case number to give to Symantec as a reference. They said not the same issue.

Thanks.

-----Original Message-----
From: Jack.Forester < at > mylan.com [mailto:Jack.Forester < at > mylan.com]
Sent: Tuesday, December 06, 2011 3:39 PM
To: Kelczewski, Mike
Cc: veritas-bu < at > mailman.eng.auburn.edu; veritas-bu-bounces < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage Console.

We had a similar issue with Aptare and vmware backups. For all vmware backups, NetBackup was reporting the name of the ESX server as the client name, and not the name of the VM itself. We kept pressing Symantec, and they relented and fixed it.
--
Jack Forester, Jr.
Sr. Data Protection Administrator
Global Technology Services - AHS
Mylan, Inc.
5005 Greenbag Road
Morgantown, WV 26501

jack.forester < at > mylan.com

Phone: +1.304.554.6039
Cell: +1.412.805.5313



From: "Kelczewski, Mike" <KELCZ < at > coj.net>
To: "veritas-bu < at > mailman.eng.auburn.edu"
<veritas-bu < at > mailman.eng.auburn.edu>
Date: 12/06/2011 02:17 PM
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage
Console.
Sent by: veritas-bu-bounces < at > mailman.eng.auburn.edu




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.
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



==============================================================================
CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you.
==============================================================================

_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

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.

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Tuesday, December 06, 2011 3:50 PM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.
Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
[url=Tel:608.664.8236]Tel:608.664.8236[/url] Cell:608.333.6682
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Kelczewski, Mike
Sent: Tuesday, December 06, 2011 1:17 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage Console.




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.

Mike,

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

Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.


"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: Kelczewski, Mike [mailto:KELCZ < at > coj.net]
Sent: Wednesday, December 07, 2011 5:51 AM
To: Lokrantz, Dennis L.; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Tuesday, December 06, 2011 3:50 PM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.
Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
[url=Tel:608.664.8236]Tel:608.664.8236[/url] Cell:608.333.6682
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Kelczewski, Mike
Sent: Tuesday, December 06, 2011 1:17 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage Console.




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.

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?

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Wednesday, December 07, 2011 9:10 AM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



Mike,

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

Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: Kelczewski, Mike [mailto:KELCZ < at > coj.net]
Sent: Wednesday, December 07, 2011 5:51 AM
To: Lokrantz, Dennis L.; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Tuesday, December 06, 2011 3:50 PM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.
Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
[url=Tel:608.664.8236]Tel:608.664.8236[/url] Cell:608.333.6682
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Kelczewski, Mike
Sent: Tuesday, December 06, 2011 1:17 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage Console.




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.

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 Lokrantz
Storage Administrator
Telephone & Data Systems Inc.


"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: Kelczewski, Mike [mailto:KELCZ < at > coj.net]
Sent: Wednesday, December 07, 2011 9:39 AM
To: Lokrantz, Dennis L.
Cc: veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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?

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Wednesday, December 07, 2011 9:10 AM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



Mike,

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

Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: Kelczewski, Mike [mailto:KELCZ < at > coj.net]
Sent: Wednesday, December 07, 2011 5:51 AM
To: Lokrantz, Dennis L.; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Tuesday, December 06, 2011 3:50 PM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.
Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
[url=Tel:608.664.8236]Tel:608.664.8236[/url] Cell:608.333.6682
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Kelczewski, Mike
Sent: Tuesday, December 06, 2011 1:17 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage Console.




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.

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?

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Wednesday, December 07, 2011 12:31 PM
To: Kelczewski, Mike
Cc: 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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 Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: Kelczewski, Mike [mailto:KELCZ < at > coj.net]
Sent: Wednesday, December 07, 2011 9:39 AM
To: Lokrantz, Dennis L.
Cc: veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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?

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Wednesday, December 07, 2011 9:10 AM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



Mike,

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

Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: Kelczewski, Mike [mailto:KELCZ < at > coj.net]
Sent: Wednesday, December 07, 2011 5:51 AM
To: Lokrantz, Dennis L.; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.

From: Lokrantz, Dennis L. [mailto:dennis.lokrantz < at > teldta.com]
Sent: Tuesday, December 06, 2011 3:50 PM
To: Kelczewski, Mike; 'veritas-bu < at > mailman.eng.auburn.edu'
Subject: RE: Exchange 2010 DAG Backups And Aptare Storage Console.



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.
Dennis Lokrantz
Storage Administrator
Telephone & Data Systems Inc.
[url=Tel:608.664.8236]Tel:608.664.8236[/url] Cell:608.333.6682
"The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents." — Nathaniel Borenstein


From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of Kelczewski, Mike
Sent: Tuesday, December 06, 2011 1:17 PM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] Exchange 2010 DAG Backups And Aptare Storage Console.




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.