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
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
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
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
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
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
