UCCX Backup Failure

[James Burns]

Hi,

A few weeks back I had a problem with the Unified CM Telephony Service in Partial Service, which caused a few of our JTAPI triggers to lock up. The triggers were cleared by restarting both servers of our UCCX system. After this restart, found the backup process stopped working.

Unified CM Telephony Service partial service was subsequently cleared by

1. dis-associating / re-associate all devices in RMJTAPI.

2. restarting both UCCX servers

3. restarting all Call Manager Nodes.

I was hoping this would clear the backup fault as well however the backup still does not work. Have looked through the MCVD logs for backup_failure as mentioned in a UCCX Troubleshooting document but this text is not included. File location and user credentials unchanged and shown correctly in logs.

Any ideas?

The logs make reference to a maximum file size of 10240 on each server which is is not as large as the actual file size for backing up. Is this significant or is this something which would have no effect on the backup.

Any advice gratefully accepted.

Thanks

James

[rhugo]

Are you getting any other DRF Failure errors?  You could try restarting the DRF Master service and re-running a Manual backup to see if it stalls in real-time?  If it doesn't, but STILL fails for your overnight backup, you could try swapping out the SFTP client.  I know I recently fought this issue with UConn MESSSAGE backup because of a 1 GIG file-size limit with the client I was using.  This may not apply in your situation, since you said current tar file size is > 1 GIG, but its worth looking into.

[Clifford McGlamry · Accepted solution]

You don't mention the version number, but a couple of things I would do:

1.  Set up a new backup location on your workstation/laptop.  See if you can backup to that manually. (testing: can the backup get off the server)

2.  See if you can push the file to the designated backup location from your laptop. (testing: can the backup target receive files)

3.  If it's a windows box, create a local share and see if you can backup to that.

Once you try these things, post your results back along with the UCCX version info and we'll see where we can go.

Cliff

[James Burns]

Clifford,

Thanks for the tips, testing showed it to be a problem with the credentials being used. Need to have a closer look at this as the user ID and password have not changed since it last worked. Problem therefore is regarding permssioning and not UCCX.

Thanks for your help and apologies for the delay getting back to you.

James