Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

False status report when backing up Lotus Domino encrypted files : Job successfull althought Job details shows databases are skipped

Updated: 21 May 2010 | 2 comments
Stefan Wilski's picture
0 0 Votes
Login to vote

Hello,
After submitting case number 240-973-473 and submitting the following suggestion :

http://www.symantec.com/connect/idea/lotus-domino-encrypted-files-are-skipped-during-backup-job-summary-reports-completed-status-suc

I wonder if someone else can confirm the behaviour of Backup Exec 12.5 sp2 and the Domino Agent.
I understand the agent can not backup Domino encrypted databases.
In version 9.2 of BENT, I used to have a "job completed with exception", and the list of skipped databases. In the job details, I had the return code describing the dababases skipped are encrypted.

In version 12.5 of BENT, the same backup job on the same databases ends with a nice , but false to my eyes "Job completed successfully".
When browsing the job details, I see the encrypted .NSF being skipped by the backup.

This is missleading.
On one side I read job completed successfull, on the other side I have databases not backed up, without any kind of notification.

What is your experience and your toughts ?

Comments

AshutoshTamhankar's picture
13
Jul
2009
0 Votes 0
Login to vote

This indeed is a data

This indeed is a data threatening situation. You might want to check your remote agent / lotus notes agent debug logs and compare it with those in http://support.veritas.com/docs/300953, to see if any of the lotus notes agent related APIs are returning any errors. Is the backup also reported as successful with no exceptions after uninstalling BEWS 12.5 SP2? So have you decided to keep the databases unencrypted for the time being? 

Stefan Wilski's picture
16
Jul
2009
0 Votes 0
Login to vote

Case 240-973-473 has been re-opened

The case has been re-opened by the second level support. They asked me to turn on the Debug mode and send them the resulting log file.