View previous topic :: View next topic
|
Author |
Message |
pietras65
New User
Joined: 03 Aug 2013 Posts: 5 Location: Poland
|
|
|
|
Hi All,
I have a question because about 2 hours after issued command backvol cds I received a message like:
Reference value: DFHSM_HSMAMON
DFHSM: FUNCTION NOT PROCESSED FOR THE 5TH TIME BECAUSE OF BACKVOL OPERATION STILL RUNNING.
and after 4 hours:
Reference value: DFHSM_HSMAMON
DFHSM: FUNCTION NOT PROCESSED FOR THE 10TH TIME BECAUSE OF BACKVOL OPERATION STILL RUNNING.
I checked and when I issued command backvol cds after 5 minutes I got information that backvol status SUCCESSFUL. Journal was empty. DFHSM's functions were NOT HELD. DFHSM received and proceeded new requests without problems so I'm wondering why this kind of messages appeared? Could someone try to answer this question?
Kind regards
Piotr |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 580 Location: London
|
|
|
|
BACKVOL CDS won't start while some otehr functions like Primary Space Management or Backup are running, it waits for them to complete |
|
Back to top |
|
|
pietras65
New User
Joined: 03 Aug 2013 Posts: 5 Location: Poland
|
|
|
|
hmm there was problem because journal was full and status of the DFHSM in System Automation was halted, all funtions of DFHSM were HELD. When I ran backvol cds then after several minutes:
- journal was empty
- all DFHSM's functions were NOT HELD
- in the log was information that: BACKVOL status: successful
so I think that backvol ran and finished without problem but later appeared messages like in the topic and I don't know why.. |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 580 Location: London
|
|
|
|
OK, the BACKVOL CDS command does empty the journal after backing it up so that's OK. The CDS backup was probably initiated because the JRNL was full, but if your automation HELD everything perhaps it was trying to complete the HOLD's before starting the BACKVOL CDS. |
|
Back to top |
|
|
|