Search results for query: *

Hello all, I was getting errors on my tape library that the hard picker was jammed and errors of an orphaned tape. This was causing all backups to fail. One tape was found to be having issues in the picker, while it wasn't jammed it was apparent it should be removed as it had scrapes on it from...

Despite what df -h said, as well as what all other errors displayed and what technical documentation suggested, what resolved this for me was deleting a previous large backup.

Thank you for the resource! I will :) Am starting on page 148 about CMSADM backups. df -h the backup directory is only 11% used The filesystem overall shows 79% used

Learned it's not tape, the filesystem is backed up to "other" where it's a nfs share

It looks like all backups are successful, aside from the filesystem backup kicked off via the Avaya call management system under cmsadm. Unfortunately no error to follow as it got cancelled after taking too long...

You both make very good points and I believe you're right on the money. I think our tapes were full at the time of the backup attempting to be ran. Finding it difficult to confirm but trying again soon!

I believe we use tape because of the reference to cpio, it's possible though we use both because of the mount points I found. We have NetApp and that goes to tape so, tape? We use CMS R17

The logs I'm being referred to aren't helping me isolate what the issue is, maybe someone here will understand? Has this happened to anyone, what fixed it for you, or what should I do? At the end of the backup through Terminal Emulator it stated: ................. 765729 blocks Request failed...