Subscribe

DFM 4.0.2 DB backup problem

Hello all,

my problem with the DFM DB backup scheduler is, that the backup won't start at the configured time automatically, it always say "pending".

It's possible to start a sccessful backup by command line without any error messages.

Here are my system parameters:

Operation system:

[root@DFM]# lsb_release -a

LSB Version:    :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch

Distributor ID: RedHatEnterpriseServer

Description:    Red Hat Enterprise Linux Server release 5

Release:        5

DFM version:

[root@DFM]# dfm version

dfm 4.0.2 (4.0.2)

DFM backup diag:

[root@DFM]# dfm backup diag

Sysbase Data Directory:        /opt/NTAPdfm/data

Sysbase Log Directory:         /opt/NTAPdfm/data

Performance Data Directory:  /opt/NTAPdfm/perfdata

Script-plugins Directory:        /opt/NTAPdfm/script-plugins

Reports Archive Directory:     /opt/NTAPdfm/reports/

Plugins Directory:                 /opt/NTAPdfm/plugins

Database Hosting System:    localhost

SnapDrive Installed:              No

Backup Destination:             /backup/DFM_backup/          (That's a NFS mount)

Number of backups possible: 25

Backup Retention Count:     26

Allowed Backup Type:          Archive (ndb)

DB backup scheduler config is:

[root@DFM]#  dfm backup schedule get

Backup Schedule: Weekly on Thursday at 13:00, archive type, currently enabled.

Did I miss somthing to configure or what could be the problem that the scheduler won't start at the configured date?

regards

Thorsten

Re: DFM 4.0.2 DB backup problem

Hi Thorsten,

     Can you check if you see any errors in the dfmscheduler.log under you isntall dir /opt/NTAPdfm/log ?

Regards

adai

Re: DFM 4.0.2 DB backup problem

Hi Adai,

sorry for my late response, I was on vacation.

I checked the dfmscheduler.log file and it has no kontent.

regards

Thorsten

Re: DFM 4.0.2 DB backup problem

The problem has been solved by a hardware crash of the server. After changing the defect components and restarting the server the problem doesn't exist anymore.