Product

Platform

Operating system

Error

Symptoms

The regularly scheduled 3 a.m. backup works, but only the Oracle database backup part is successful. In the Oracle backup log file, it shows that the SuccessfulBackup.cmd script is launched after Oracle backup successfully completes, but the backup never happens and there are no error messages anywhere.

If you edited the SuccessfulBackup.cmd script to log its console output to a file, you would see an error message produced by the Legato savegrp command that would otherwise go unseen.

How to reproduce:

Remove the local SYSTEM account from the Legato Administrator’s list. (Or don’t add it in the first place, e.g., as if you are following the Prinergy backup document to the letter.)

More info: The nightly backup command is set up to be launched by the standard NT Schedule service, which normally runs under the local SYSTEM account. If the account that the backup command is going to run under isn’t in Legato’s Administrators list, then the command will fail. So if for some reason the Schedule service runs using a different account, you would have to add that account to Legato instead (or we should figure out a different way of doing it).

Cause

Solution

Add the local SYSTEM account to the Legato Administrator’s list.

Permanent fix: Update the backup document. Fix SuccessfulBackup.cmd to log errors somewhere to make diagnosing problems easier in the future.

Permanent fix:

See also

Keywords

backup, Legato

Technical contact(s)

Stan Yoshida

Submitted by

Date submitted