Data Protection

I got bunch of Unamanged replication pairs, in order to unmap S-Vols from their hosts I need to Unprotect these volumes first, and since they are unmanaged Im unable to do so.

I understand that I need to import these relationships into Protector, however Im unable to locate correct process/steps to perform it. Anyone can point me in correct direction?

Storage:

G600 -> G600

#DataProtection
#StorageManagement

------------------------------
Janis Sirmonts
DnB NORD
------------------------------

Hello

Do you know what version of Ops Center you're running?

Depending on what you have setup you can do this either from the SVP or Ops Center.

Detecting the replication pairs:

For G600 do you have an SVP, if so you can login these and just delete the replication partners, if needed to clean it out.

Else in Ops Center, depending on your version there should be 2 places where you can see the replication partners:


Alternatively in Protector (requires virtual SVP or Physical SVP) there is a report regarding "All Reports", that can show the relationships.

Deleting or cleaning up:
Using the SVP, you should be able to do so here:

In protector you can adopt and then teardown, delete:
Adopting
https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-adopt-a-replication-into-protector
 Teardown:

https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-teardown-the-s-vols-of-a-replication-removed-from-a-data-flow

After it's torndown, you can delete the volume or click the delete volume next to "Static Full Copy" in the GUI.

------------------------------
William Jansen Van Nieuwenhuizen
Hitachi Vantara

Original Message:
Sent: 10-30-2025 09:05
From: Janis Sirmonts
Subject: Unamanged replication pairs,

I got bunch of Unamanged replication pairs, in order to unmap S-Vols from their hosts I need to Unprotect these volumes first, and since they are unmanaged Im unable to do so.

I understand that I need to import these relationships into Protector, however Im unable to locate correct process/steps to perform it. Anyone can point me in correct direction?

Storage:

G600 -> G600

#DataProtection
#StorageManagement

------------------------------
Janis Sirmonts
DnB NORD
------------------------------

Since I dont have SVP I went for adopting relationships into the Protector. Created policy, node, data flow, was able to activate data flow, but initialization fails with following:
11796 Handler call failed: Could not resolve all paths with this handler.
'Source' Sequence 'Application' failed: ResolveApplicationPathsRequest failed for reason: Could not resolve all paths with this handler.. *** Attachment count: 3 ***

Content of attachment3:

Hello

Do you know what version of Ops Center you're running?

Depending on what you have setup you can do this either from the SVP or Ops Center.

Detecting the replication pairs:

For G600 do you have an SVP, if so you can login these and just delete the replication partners, if needed to clean it out.

Else in Ops Center, depending on your version there should be 2 places where you can see the replication partners:


Alternatively in Protector (requires virtual SVP or Physical SVP) there is a report regarding "All Reports", that can show the relationships.

Deleting or cleaning up:
Using the SVP, you should be able to do so here:

In protector you can adopt and then teardown, delete:
Adopting
https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-adopt-a-replication-into-protector
 Teardown:

https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-teardown-the-s-vols-of-a-replication-removed-from-a-data-flow

After it's torndown, you can delete the volume or click the delete volume next to "Static Full Copy" in the GUI.

------------------------------
William Jansen Van Nieuwenhuizen
Hitachi Vantara

Original Message:
Sent: 10-30-2025 09:05
From: Janis Sirmonts
Subject: Unamanged replication pairs,

I got bunch of Unamanged replication pairs, in order to unmap S-Vols from their hosts I need to Unprotect these volumes first, and since they are unmanaged Im unable to do so.

I understand that I need to import these relationships into Protector, however Im unable to locate correct process/steps to perform it. Anyone can point me in correct direction?

Storage:

G600 -> G600

#DataProtection
#StorageManagement

------------------------------
Janis Sirmonts
DnB NORD
------------------------------

Hello Janis

Could you perhaps share:

• The list of 'unmanaged volume pairs' in Administrator
• The 'block host' node you created in protector
• A Screenshot of the data protection flow you configured, can just be the summary as displayed on the destination node in the data flow in protector. 

Since I dont have SVP I went for adopting relationships into the Protector. Created policy, node, data flow, was able to activate data flow, but initialization fails with following:
11796 Handler call failed: Could not resolve all paths with this handler.
'Source' Sequence 'Application' failed: ResolveApplicationPathsRequest failed for reason: Could not resolve all paths with this handler.. *** Attachment count: 3 ***

Content of attachment3:

Hello

Do you know what version of Ops Center you're running?

Depending on what you have setup you can do this either from the SVP or Ops Center.

Detecting the replication pairs:

For G600 do you have an SVP, if so you can login these and just delete the replication partners, if needed to clean it out.

Else in Ops Center, depending on your version there should be 2 places where you can see the replication partners:


Alternatively in Protector (requires virtual SVP or Physical SVP) there is a report regarding "All Reports", that can show the relationships.

Deleting or cleaning up:
Using the SVP, you should be able to do so here:

In protector you can adopt and then teardown, delete:
Adopting
https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-adopt-a-replication-into-protector
 Teardown:

https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-teardown-the-s-vols-of-a-replication-removed-from-a-data-flow

After it's torndown, you can delete the volume or click the delete volume next to "Static Full Copy" in the GUI.

------------------------------
William Jansen Van Nieuwenhuizen
Hitachi Vantara

Original Message:
Sent: 10-30-2025 09:05
From: Janis Sirmonts
Subject: Unamanged replication pairs,

I got bunch of Unamanged replication pairs, in order to unmap S-Vols from their hosts I need to Unprotect these volumes first, and since they are unmanaged Im unable to do so.

I understand that I need to import these relationships into Protector, however Im unable to locate correct process/steps to perform it. Anyone can point me in correct direction?

Storage:

G600 -> G600

#DataProtection
#StorageManagement

------------------------------
Janis Sirmonts
DnB NORD
------------------------------

Company security policy blocked screenshot upload, so will try provide data differently:

1. Logical devices specified in Block  Node I created:
   99
   100
   110
   147
   223
   225
   226
   227
   228
   229
   231
   232
   233
   234
   235
   236
   237
   238
   239
   240
   241
   242
   243
   244
   245
   246
   247
   248
   249
   250
   251
   252
   253
   254
   255
   Other settings - Block Storage device G600-1; nothing in LDEV exclusion list 
2. List of unmanaged volume pairs:
   | #  | Technology | P-Vol ID       | P-Vol Status | S-Vol ID       | S-Vol Status | Secondary Storage System | Consistency ID | Split Time | Copy Group |
   |----|------------|----------------|--------------|----------------|--------------|---------------------------|----------------|------------|------------|
   | 1  | HA         | 99 (00:00:63)  | PAIR         | 224 (00:00:E0) | PAIR         | 470477                    | -              | -          | -          |
   | 2  | HA         | 100 (00:00:64) | PAIR         | 225 (00:00:E1) | PAIR         | 470477                    | -              | -          | -          |
   | 3  | HA         | 110 (00:00:6E) | PAIR         | 226 (00:00:E2) | PAIR         | 470477                    | -              | -          | -          |
   | 4  | HA         | 147 (00:00:93) | PAIR         | 227 (00:00:E3) | PAIR         | 470477                    | -              | -          | -          |
   | 5  | HA         | 223 (00:00:DF) | PAIR         | 528 (00:02:10) | PAIR         | 470477                    | -              | -          | -          |
   | 6  | HA         | 225 (00:00:E1) | PAIR         | 529 (00:02:11) | PAIR         | 470477                    | -              | -          | -          |
   | 7  | HA         | 226 (00:00:E2) | PAIR         | 530 (00:02:12) | PAIR         | 470477                    | -              | -          | -          |
   | 8  | HA         | 227 (00:00:E3) | PAIR         | 531 (00:02:13) | PAIR         | 470477                    | -              | -          | -          |
   | 9  | HA         | 228 (00:00:E4) | PAIR         | 532 (00:02:14) | PAIR         | 470477                    | -              | -          | -          |
   | 10 | HA         | 229 (00:00:E5) | PAIR         | 533 (00:02:15) | PAIR         | 470477                    | -              | -          | -          |
   | 11 | HA         | 231 (00:00:E7) | PAIR         | 534 (00:02:16) | PAIR         | 470477                    | -              | -          | -          |
   | 12 | HA         | 232 (00:00:E8) | PAIR         | 535 (00:02:17) | PAIR         | 470477                    | -              | -          | -          |
   | 13 | HA         | 233 (00:00:E9) | PAIR         | 536 (00:02:18) | PAIR         | 470477                    | -              | -          | -          |
   | 14 | HA         | 234 (00:00:EA) | PAIR         | 537 (00:02:19) | PAIR         | 470477                    | -              | -          | -          |
   | 15 | HA         | 235 (00:00:EB) | PAIR         | 538 (00:02:1A) | PAIR         | 470477                    | -              | -          | -          |
   | 16 | HA         | 236 (00:00:EC) | PAIR         | 539 (00:02:1B) | PAIR         | 470477                    | -              | -          | -          |
   | 17 | HA         | 237 (00:00:ED) | PAIR         | 540 (00:02:1C) | PAIR         | 470477                    | -              | -          | -          |
   | 18 | HA         | 238 (00:00:EE) | PAIR         | 541 (00:02:1D) | PAIR         | 470477                    | -              | -          | -          |
   | 19 | HA         | 239 (00:00:EF) | PAIR         | 542 (00:02:1E) | PAIR         | 470477                    | -              | -          | -          |
   | 20 | HA         | 240 (00:00:F0) | PAIR         | 552 (00:02:28) | PAIR         | 470477                    | -              | -          | -          |
   | 21 | HA         | 241 (00:00:F1) | PAIR         | 547 (00:02:23) | PAIR         | 470477                    | -              | -          | -          |
   | 22 | HA         | 242 (00:00:F2) | PAIR         | 551 (00:02:27) | PAIR         | 470477                    | -              | -          | -          |
   | 23 | HA         | 243 (00:00:F3) | PAIR         | 556 (00:02:2C) | PAIR         | 470477                    | -              | -          | -          |
   | 24 | HA         | 244 (00:00:F4) | PAIR         | 550 (00:02:26) | PAIR         | 470477                    | -              | -          | -          |
   | 25 | HA         | 245 (00:00:F5) | PAIR         | 558 (00:02:2E) | PAIR         | 470477                    | -              | -          | -          |
   | 26 | HA         | 246 (00:00:F6) | PAIR         | 553 (00:02:29) | PAIR         | 470477                    | -              | -          | -          |
   | 27 | HA         | 247 (00:00:F7) | PAIR         | 549 (00:02:25) | PAIR         | 470477                    | -              | -          | -          |
   | 28 | HA         | 248 (00:00:F8) | PAIR         | 545 (00:02:21) | PAIR         | 470477                    | -              | -          | -          |
   | 29 | HA         | 249 (00:00:F9) | PAIR         | 548 (00:02:24) | PAIR         | 470477                    | -              | -          | -          |
   | 30 | HA         | 250 (00:00:FA) | PAIR         | 557 (00:02:2D) | PAIR         | 470477                    | -              | -          | -          |
   | 31 | HA         | 251 (00:00:FB) | PAIR         | 543 (00:02:1F) | PAIR         | 470477                    | -              | -          | -          |
   | 32 | HA         | 252 (00:00:FC) | PAIR         | 554 (00:02:2A) | PAIR         | 470477                    | -              | -          | -          |
   | 33 | HA         | 253 (00:00:FD) | PAIR         | 544 (00:02:20) | PAIR         | 470477                    | -              | -          | -          |
   | 34 | HA         | 254 (00:00:FE) | PAIR         | 555 (00:02:2B) | PAIR         | 470477                    | -              | -          | -          |
   | 35 | HA         | 255 (00:00:FF) | PAIR         | 546 (00:02:22) | PAIR         | 470477                    | -              | -          | -          |
3. 
   Description
   For Unamamged pairs on G600
   Status
   Active
   Activated
   11/05/2025 11:52:32
   Modified Since Activation
   No
   Tags
   None
   Policies
   Type
   Active-Active Remote Clone (Global-Active Device)
   Adopt Configuration
   Yes
   Mirror Unit
   h1
   Copy Pace
   Slow (3)
   Secondary Host Groups
   None Selected
   Volume Naming
   Automatically Generated
   Volume Connection Type
   Host Group

------------------------------
Janis Sirmonts
DnB NORD

Original Message:
Sent: 11-05-2025 13:49
From: William Jansen Van Nieuwenhuizen
Subject: Unamanged replication pairs,

Hello Janis

Could you perhaps share:

• The list of 'unmanaged volume pairs' in Administrator
• The 'block host' node you created in protector
• A Screenshot of the data protection flow you configured, can just be the summary as displayed on the destination node in the data flow in protector. 

------------------------------
William Jansen Van Nieuwenhuizen
Hitachi Vantara

Original Message:
Sent: 11-05-2025 05:05
From: Janis Sirmonts
Subject: Unamanged replication pairs,

Since I dont have SVP I went for adopting relationships into the Protector. Created policy, node, data flow, was able to activate data flow, but initialization fails with following:
11796 Handler call failed: Could not resolve all paths with this handler.
'Source' Sequence 'Application' failed: ResolveApplicationPathsRequest failed for reason: Could not resolve all paths with this handler.. *** Attachment count: 3 ***

Content of attachment3:

------------------------------
Janis Sirmonts
DnB NORD

Original Message:
Sent: 10-31-2025 08:54
From: William Jansen Van Nieuwenhuizen
Subject: Unamanged replication pairs,

Hello

Do you know what version of Ops Center you're running?

Depending on what you have setup you can do this either from the SVP or Ops Center.

Detecting the replication pairs:

For G600 do you have an SVP, if so you can login these and just delete the replication partners, if needed to clean it out.

Else in Ops Center, depending on your version there should be 2 places where you can see the replication partners:


Alternatively in Protector (requires virtual SVP or Physical SVP) there is a report regarding "All Reports", that can show the relationships.

Deleting or cleaning up:
Using the SVP, you should be able to do so here:

In protector you can adopt and then teardown, delete:
Adopting
https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-adopt-a-replication-into-protector
 Teardown:

https://docs.hitachivantara.com/r/en-us/ops-center-protector/7.7.x/mk-99prt002/data-protection-workflows/hitachi-block-workflows/how-to-teardown-the-s-vols-of-a-replication-removed-from-a-data-flow

After it's torndown, you can delete the volume or click the delete volume next to "Static Full Copy" in the GUI.

------------------------------
William Jansen Van Nieuwenhuizen
Hitachi Vantara

Original Message:
Sent: 10-30-2025 09:05
From: Janis Sirmonts
Subject: Unamanged replication pairs,

I got bunch of Unamanged replication pairs, in order to unmap S-Vols from their hosts I need to Unprotect these volumes first, and since they are unmanaged Im unable to do so.

I understand that I need to import these relationships into Protector, however Im unable to locate correct process/steps to perform it. Anyone can point me in correct direction?

Storage:

G600 -> G600

#DataProtection
#StorageManagement

------------------------------
Janis Sirmonts
DnB NORD
------------------------------