System Save failure after System Restore -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi,

I got valuable advice from this forum recently, when I had to do a system restore from tape after a drive failure, and now I'm back.

You may recall that we discovered that RAID5 had not been implemented so the failed drive required replacement and reformatting of the entire ASP, at which time we engaged RAID5 protection before doing the system restore.
This system (v7r3) previously hosted a v7r1 partition, which was also wiped out when the drives were formatted. We have not recreated that v7r1 partition, and the NWSD and NWSSTG devices are deleted.

Now, when we try to create a new system save, using option 21 on the Go SAVE menu, it appears to complete the task but informs us of errors encountered during the process.
I don't know how to determine which messages are real issues we need to resolve.

For example, does error message CIM0301, CIMOM server job not submitted. Reason code 07 (Required SLP is not installed) really indicate a problem?
Or CPFB923, Management Central Server job was not ended. Reason code 01 (The Management Central Server job is not running). Didn't know I need to start this server, or end it.
There are lots of severity 30 and 40 messages.

Suggestions on proceeding?

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.