Mirroring Paths: Difference between revisions
Jump to navigation
Jump to search
migrate>Lu-K Created page with "<span style="font-size:small"><span style="font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 400; font-style: normal; font-variant: nor..." |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Mirroring paths can provide access to disks on the bound node. We call them “remote disks”. You need to add at least one mirroring path to use remote disks. | |||
By adding a mirroring path, an iSCSI bidirectional connection between chosen interfaces is automatically established. It makes it possible to show disks from the other node on both of them. Disks that are from the remote node have added the word “(remote)” to the disk name. | |||
It is recommended to create more than one path that uses different subnetworks and is fast and reliable. | |||
Local and remote status help you to quickly evaluate whether the connection is broken or not. | |||
[[Category:Help topics]] | |||
Latest revision as of 15:00, 27 March 2019
Mirroring paths can provide access to disks on the bound node. We call them “remote disks”. You need to add at least one mirroring path to use remote disks.
By adding a mirroring path, an iSCSI bidirectional connection between chosen interfaces is automatically established. It makes it possible to show disks from the other node on both of them. Disks that are from the remote node have added the word “(remote)” to the disk name.
It is recommended to create more than one path that uses different subnetworks and is fast and reliable.
Local and remote status help you to quickly evaluate whether the connection is broken or not.