Dell PowerVault DR4100 Manual de Boas Práticas - Página 36

Procurar online ou descarregar pdf Manual de Boas Práticas para Armazenamento Dell PowerVault DR4100. Dell PowerVault DR4100 41 páginas. Backup and recovery appliance
Também para Dell PowerVault DR4100: Manual de iniciação (10 páginas), Manual (37 páginas), Nota de lançamento (16 páginas), Manual (12 páginas), Manual (24 páginas), Manual (23 páginas), Configuração do Qiuck (1 páginas), Manual (27 páginas), Manual (25 páginas)

Imprimir página

Dell PowerVault DR4100 Manual de Boas Práticas

Establish replication from Seattle1 to Lansing1 using the following command:

replication --add --name < container-name> --role <source | target> --peer <IP address> --

replication_traffic <ip address | hostname> --encryption <none | aes128 | aes256>

On Lansing2 add replication to the 10GB bond using the following command:

system –replication_traffic --add --interface <bond(0-N) | eth(0-N) | lo#>

Create a route from Lansing2 to Lansing1 using the following command:

network --route --add --network <destination_network> --gateway <gateway addresses> --interface

<bond(0-N) | eth(0-N) | lo#>

Create a route from Lansing1 to Lansing2 using the following commands:

network --route --add --network <destination_network> --gateway <gateway addresses> --interface

<bond(0-N) | eth(0-N) | lo#>

10. Establish replication from Lansing1 to Lansing2 using the following command:

replication --add --name < container-name> --role <source | target> --peer <IP address> --

replication_traffic <ip address | hostname> --encryption <none | aes128 | aes256>

DR4100 Best Practice Guide | April 2014

administrator@Seattle1 > replication --add --name backup --role source --peer <IP of 1G

Bond of Lansing1> --replication_traffic <ip address of local 1G interface to be used for

replication| hostname> --encryption aes256

administrator@Lansing2 > system --replication_traffic --add --interface bond0

administrator@Lansing2 > network –route --add --network <Lansing1's 10G network> --

gateway <gateway addresses> --interface bond0

administrator@Lansing1 > network --route --add --network <Lansing2's 10G network> --

gateway <gateway addresses> --<IP of 10Gbond of Lansing1>

administrator@Lansing1 > replication --update --name <source-container-name> --role

source --peer <IP of 10G Bond of Lansing2> --replication_traffic <IP of 10G bond of

Lansing1>

Example