hi,
I actually come across the same thing recently.
Support helped me complete the final steps but I did document some of the commands.
These are pretty destructive commands so you certainly don't want to be have any workloads on the array!
srdata can be destroyed if your not worried about the system reporter data.
Code:
-> stopsr -f
For the pdsld (Preserved data LD), we need to stop the preserved data before we remove them.
Code:
-> showpdata
Code:
-> stoppdata
Code:
-> removeld -rmsys <pdsld name >
Mine looked like this:
removeld -rmsys log0.0
removeld -rmsys log1.0
removeld -rmsys pdsld0.0
removeld -rmsys pdsld0.1
removeld -rmsys pdsld0.2
once you kickoff an admithw it will re-create the areas.
Quote:
Creating logging LD for node 0.
Creating logging LD for node 1.
And the "admin" what was left had to be manually moved from memory.
showldmap admin.usr.0
showldch admin.usr
if you did want to save your SR data volume you can snap it and promote it.
Snapshot protection for .srdata
HP 3PAR OS allows the .srdata VV to have a snp_cpg associated.
CLI only, GUI coming in SSMC 3.x.
This enables snapshotting or physical copy in order to back up SR data.
Then promotesv or VV copy to restore (when SR is stopped)
Example:
cli% setvv -snp_cpg cpg1 .srdata
cli% createsv -ro srdata_backup .srdata
Now if the primary .srdata VV became corrupt or had a database problem the snapshot can be restored
cli% stopsr -f
cli% promotesv srdata_backup
Task 1089 has been started to promote virtual copy srdata_backup
cli% waittask 1089
Task 1089 done
cli% startsr -f