Object exists, skipping
The client tried to restore the specified object, but the object already existed in the target restore location and the user chose not to replace the existing object.
The object is skipped, a message is logged in dsmerror.log, and restore processing continues with the next object.
The object was skipped because either REPLACE NO was in effect, causing all existing objects to be skipped, or REPLACE PROMPT was in effect, and when prompted, the user chose to skip this object. No additional action is necessary if the decision to skip the object was deliberate. Otherwise the operation can be retried using either REPLACE ALL (automatically replace existing object) or REPLACE PROMPT (prompt the user whether to replace the object).