Índice analítico
SnapMirror - volume, e espelhamento qtree SnapMirror {on | off} SnapMirror estado [options] [volume | qtree ... ]
SnapMirror initialize [opcións] destino
SnapMirror actualización [opcións] destino
SnapMirror destino quiesce
SnapMirror destino currículo
pausa SnapMirror [options] destino
SnapMirror resync [opcións] destino
destinos SnapMirror [opción] [fonte]
SnapMirror orixe destino de liberación
SnapMirror {tendas | recuperar} volumes tapedevices
SnapMirror tapedevices destino de uso
SnapMirror destino <n> acelerador
SnapMirror abortar [opcións] destino ...
SnapMirror migrar [opcións] orixe destino
A orde SnapMirror se usa para controlar SnapMirror, un método de reflictir volumes e qtrees. Permite ao usuario activar e desactivar calendario e transferencia manual de datos, solicitar información sobre transferencias, iniciar o arranque de transferencia de datos, iniciar unha actualización dun espello, temporalmente actualizacións pausa para un espello, espello romper relacións, ressincronizar espellos rotos, información de destino lista , liberación espellos neno, almacenar imaxes de volume cara a cinta, recuperar imaxes de volume a partir de cinta e transferencias abortar en curso. SnapMirror pode ser usado para replicar volumes ou qtrees. Os procesos e comportamentos implicados son lixeiramente (e ás veces sutilmente) diferente entre os distintos tipos de espelhamento de datos.
O proceso é o destino SnapMirror-driven. A orde initialize SnapMirror comeza a primeira transferencia que deixa o destino con todos os datos sobre a fonte. Antes da transferencia de inicio, o destino debe estar preparado para ser substituído cos datos da fonte; volumes de destino debe ser restrinxida (ver vol), e qtrees destino non debe existir.
Para os espellos assíncronos, o destino periodicamente solicita unha actualización dende a fonte, acepta unha transferencia de datos e grava os datos no disco. Estas transferencias de actualización inclúen só os cambios feitos na fonte dende a transferencia. O programador SnapMirror iníciase estas transferencias automaticamente de acordo con horarios no arquivo snapmirror.conf.
Espellos síncronas inicialmente se comportan de forma asíncrono, pero farán a transición a modo síncrono na primeira oportunidade. Estes espellos poden voltar a modo asíncrono en caso de erro (por exemplo, unha partición de rede entre os filers espelhamento) ou por petición do usuario.
O comando update SnapMirror pode ser usado para iniciar a transferencia dos individuais separadamente dos programados en snapmirror.conf.
Tras a transferencia de inicio, o destino está dispoñible para os clientes, pero nun estado de só lectura. O estado dun destino vai amosar que é snapmirrored (ver aggR, vol, ou qtree para obter máis detalles sobre como ver o estado de destino).
Para utilizar o destino de escritura, así como a lectura, o que é útil cando un desastre fai que a fonte non está dispoñible ou cando quere usar o destino como un volume de proba / qtree, pode rematar a relación SnapMirror co comando break SnapMirror. Este comando cambia o estado do destino de snapmirrored a rota, tornándose escribir nel. O SnapMirror mando resync pode cambiar de volta un destino do ex-estado para snapmirrored e sincronizar os seus contidos a fonte. (Aplicado a unha fonte anterior, SnapMirror resync pode transformalo nun espello do destino ex. Deste xeito, os fondos de fonte eo seu destino pode ser invertida.)
A filer keeps track of all destinations, either direct mirrors or mirrors of mirrors, for each of its sources. This list can be displayed via the snapmirror destinations command. The snapmirror release command can be used to tell a filer that a certain direct mirror will no longer request updates.
To save network bandwidth, tape can be used to prime a new mirror volume instead of the snapmirror initialize command. The snapmirror store command dumps an image of the source to tape. The snapmirror retrieve command restores a volume image from tape and prepares the volume for update transfers over the network. If multiple tapes are used to create a volume image, the snapmirror use command is used to instruct a waiting store or retrieve process to write output or accept input to/from a new tape device. The store and retrieve commands cannot be used with qtrees.
The snapmirror migrate command is used on an existing source and destination pair to make the destination volume a writable "mimic" of the source. The destination assumes the NFS filehandles of the source, helping the filer administrator to avoid NFS re-mounting on the client side.
The snapmirror.conf file on the destination filer's root volume controls the configuration and scheduling of SnapMirror on the destination. See snapmirror.conf for more details on configuration and scheduling of SnapMirror.
Access to a source is controlled with the snapmirror.access option on the source filer. See options and protocolaccess (8) for information on setting the option.
(If the snapmirror.access option is set to "legacy”, access is controlled by the snapmirror.allow file on the source filer's root volume. See snapmirror.allow for more details.)
SnapMirror is a licensed service, and a license must be obtained before the snapmirror command can be used. SnapMirror must be licensed on both source and destination filers. See license for more details.
SnapMirror is supported on regular vfilers, as well as the physical filer named vfiler0. Use vfiler context or vfiler run to issue snapmirror commands on a specific vfiler. See vfiler for details on how to issue commands on vfilers. The use of SnapMirror on vfilers requires a MultiStore license.
When used on a vfiler, a few restrictions apply. The vfiler must be rooted on a volume and SnapMirror sources and destinations cannot be qtrees in shared volumes. Tape devices and Synchronous SnapMirror are not supported on vfilers. For a qtree SnapMirror, the vfiler must own the containing volume of the Qtree.
Cada vfiler ten o seu / etc propia / snapmirror.conf no seu volume de raíz. SnapMirror pode ser activado ou desactivado nunha vfiler de forma independente. SnapMirror comandos emitidos nun vfiler só pode operar en volumes ou qtrees que ten a propiedade exclusiva de.
Para compatibilidade con versións anteriores, o filer física (vfiler0) pode operar en todos os volumes e as qtrees, aínda que sexan de propiedade da vfilers. É altamente recommanded, con todo, que todas as unidades de almacenamento (volumes e qtrees) ser espellada desde calquera vfiler0 ou o vfiler aloxamento, non ambos. Cando as unidades de almacenamento vfiler son espelhados través vfiler0, deixe SnapMirror fóra no vfiler.
A orde SnapMirror ten subcomandos moitos. Case todos os mando ten un argumento destino. Este argumento leva de tres formas diferentes. O formulario utilizado para unha chamada específica depende se está especificando un volume ou unha qtree. Volumes son especificadas polo seu nome:
vol1
Qtrees son especificadas polo seu camiño totalmente cualificado: / Vol/vol1/qtree
Hai un camiño especial que se pode usar para SnapMirror todos os datos nun volume que non residen nun qtree. Este camiño só pode ser usado como unha fonte SnapMirror, nunca un destino SnapMirror. O camiño é especificado como: / Vol/vol1/-
All commands which don't say otherwise can take any of these forms as an argument.
The snapmirror subcommands are:
on
Enables SnapMirror data transfers and turns on the SnapMirror scheduler. This command must be issued before initiating any SnapMirror data transfers with the initialize , update , resync , store , or retrieve subcommands. This command also turns on the SnapMirror scheduler, which initiates update transfers when the time matches one of the schedules in the snapmirror.conf file. This command must be issued on the source side for the filer to respond to update requests from destinations.
off
Aborts all active SnapMirror data transfers and disables the commands which initiate new transfers ( initialize , update , resync , store , and retrieve ), and turns the SnapMirror scheduler off.
The on/off state of SnapMirror persists through reboots, and is reflected by the snapmirror.enable option. This option can be set off and on, and doing so has the exact same effect as the snapmirror on or snapmirror off commands.
status [ -l | -t | -q ] [ volume | qtree ... ]
Reports status of all the SnapMirror relationships with a source and/or destination on this filer. This command also reports whether SnapMirror is on or off. If any volume or qtree arguments are given to the command, only the SnapMirror relationships with a matching source or destination will be reported. If the argument is invalid, there won't be any status in the output.
Without any options, the short form of each relationship's status is displayed. This shows the state of the local side of the relationship, whether a transfer is in progress (and if so, the progress of that transfer), and the mirror lag, ie the amount of time by which the mirror lags behind the source. This is a simple difference of the current time and the source-side timestamp of the last successful transfer. The lag time will always be at least as much as the duration of the last successful transfer, unless the clocks on the source and destination are not synchronized (in which case it could even be negative).
If the -l option is given, the output displays more detailed information for each SnapMirror relationship. If a * is displayed along with relationship status in the short form output of snapmirror status command, then extra special information about that relationship is available, which is visible only with -l option.
If the -t option is given, the output displays the relationships that are active. A relationship is considered as active if the source or destination is involved in:
1. data transfer to or from the network. 2. reading or writing to a tape device. 3. waiting for a tape change.
4. Performing local on-disk processing or cleanup.
If the -q option is given, the output displays the volumes and qtrees that are quiesced or quiescing. See the quiesce command, below, for what this means.
See the Examples section for more information on snapmirror status .
On a vfiler, the status command shows entries related to the vfiler only. On the physical filer, active transfer entries from all vfilers are displayed. Inactive transfers are only displayed on the relevant vfiler. The preferred way to get a comprehensive and more readable list of SnapMirror transfers is to run vfiler run * snapmirror status . It iterators through all vfilers and lists its transfers.
initialize [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c create_dest_snap ] [ -w ] destination
Inicia unha transferencia inicial a través da rede. Unha transferencia inicial, tanto a través da rede ou a partir da cinta é necesaria antes das transferencias de actualización pode ter lugar. A orde de inicio debe ser emitido no filler destino. Se o destino é un volume, hai que limitado (ver vol para obter información sobre como examinar e restrinxir volumes). Se o destino é un qtree, non debe existir (ver qtree para obter información sobre como incluír qtrees). Un qtree xa existe, debe ser renomeado ou eliminar (usando un cliente NFS ou CIFS), ou SnapMirror arrincar para que qtree non vai funcionar.
Se o comando estado SnapMirror relatos de que unha transferencia abortada inicial ten un checkpoint restart, o commmand initialize vai continuar a transferencia de onde parou.
A opción-s especifica un arquivador fonte e do volume ou o camiño qtree, nun formato semellante ao de argumentos minação des_ t. A fonte debe coincidir coa entrada para o destino no arquivo snapmirror.conf. Se non corresponder, a operación imprime unha mensaxe de erro e aborta. Se a opción S-non está definida, a fonte utilizada é o especificado pola entrada para este destino no arquivo snapmirror.conf. Se non o houbera ningunha entrada tal, a operación imprime unha mensaxe de erro e aborta.
A opción-k define a velocidade máxima na que os datos son transferidos a través da rede en kilobytes por segundo. It is used to throttle disk, CPU, and network usage. This option merely sets a maximum value for the transfer speed; it does not guarantee that the transfer will go that fast. If this option is not set, the filer transmits data according to the kbs setting for this relationship in the snapmirror.conf file (see snapmirror.conf ). However, if this option is not set and there is no kbs setting for this relationship in the snapmirror.conf file, the filer transmits data as fast as it can.
The -c option only works for an initialize to a qtree. With this option, SnapMirror creates a snapshot named create_dest_snap on the destination after the initialize has successfully completed (so that it does not compete with any ongoing updates). SnapMirror does not lock or delete this snapshot. create_dest_snap cannot be hourly.x, nightly.x, or weekly.x, because these names are reserved for scheduled snapshots.
The -s option only works for an initialize to a qtree. It designates a snapshot named src_snap from which SnapMirror transfers the qtree, instead of creating a source snapshot and transferring the qtree from the new snapshot. This option is used to transfer a specific snapshot's contents; for example, it can transfer a snapshot that was taken while a database was in a stable, consistent state. SnapMirror does not lock or delete the src_snap . src_snap cannot be hourly.x, nightly.x, weekly.x, snapshot_for_backup.x or snapshot_for_volcopy.x.
A opción-w fai que o comando non voltar en canto a transferencia de inicio comeza. Pola contra, só pode esperar ata a conclusión da transferencia (ou non), momento en que ha imprimir o status de conclusión e despois volver.
actualización [-S fonte] [-k kilobytes] [-s src_snap] [-c create_dest_snap] [-w] destino
Para os espellos assíncronas, unha actualización é inmediatamente iniciado dende a fonte para o destino para actualizar o espello co contido da fonte.
Para os espellos, síncronas, unha instantánea é creado no volume de orixe, que se fai visible para os clientes do volume de destino.
O comando update debe ser emitido no filler destino.
O S-opción define a fonte da transferencia, e funciona do mesmo xeito a actualización como fai para initialize.
A opción-k define o acelerador, en kilobytes por segundo, o da transferencia, e funciona do mesmo xeito a actualización como fai para initialize.
A opción-c só funciona para unha actualización para unha qtree. Con este SnapMirror opción crea unha instantánea chamado create_dest_snap sobre o destino tras a conclusión da actualización (de xeito que non compite con todas as actualizacións en curso). SnapMirror non bloquear ou eliminar este instantáneo. Create_dest_snap non pode ser hourly.x, nightly.x, ou weekly.x, porque estes nomes son reservados para os snapshots programadas.
A opción-s só funciona para unha actualización para unha qtree. Ela designa unha instantánea chamado src_snap a partir do cal traslada o SnapMirror qtree, no canto de crear unha instantánea de orixe e trasladar o qtree do novo instantáneo. Esta opción é usada para transferir o contido de unha instantánea específico, por exemplo, pode transferir unha foto que foi tirada mentres unha base de datos estaba nun estado estable e consistente. SnapMirror non bloquear ou borrar o src_snap. Src_snap non pode ser hourly.x, nightly.x, weekly.x, snapshot_for_backup.x ou snapshot_for_volcopy.x.
A opción-w fai que o comando non voltar en canto a transferencia incremental comeza. Pola contra, só pode esperar ata a conclusión da transferencia (ou non), momento en que ha imprimir o status de conclusión e despois volver.
parar destino
Permite en marcha transferencias para destino para completar despois de que novas transferencias non están permitidas para comezar. Espellos síncronas serán retiradas para síncrono. Outros solicitudes presentados para actualizar este volume ou qtree ha falla ata que a orde currículo SnapMirror aplícase a el.
This command has special meaning to qtree destinations. A qtree destination which is being modified by SnapMirror during a transfer will have changes present in it. These changes will not be exported to NFS or CIFS clients. However, if a snapshot is taken during this time, the snapshot will contain the transitioning contents of the qtree. quiesce will bring that qtree out of a transitioning state, by either finishing or undoing any changes a transfer has made. snapmirror status can report whether a qtree is quiesced or not. The quiesce process can take some time to complete while SnapMirror makes changes to the qtree's contents. Any snapshot taken while a qtree is quiesced will contain an image of that qtree which matches the contents exported to NFS and CIFS clients.
resume destination
Resumes transfers to destination . The snapmirror resume command can be used either to abort a snapmirror quiesce in progress or undo a previously completed snapmirror quiesce . The command restores the state of the destination from quiescing or quiesced to whatever it was prior to the quiesce operation.
break [ -f ] destination
Breaks a SnapMirror relationship by turning a snapmirrored destination into a normal read/write volume or qtree. This command must be issued on the destination filer.
A opción-f forza un salto de SnapMirror entre a relación volume snaplocked sen pedir conformación.
Este comando non altera o arquivo snapmirror.conf. As transferencias regulares para un espello roto fallará.
Para volumes, esta orde ten o mesmo efecto que o opcións vol snapmirrored fóra de orde, e ha eliminar a opción snapmirrored a partir dun volume. The fs_size_fixed volume option will remain on; it must be manually removed from the volume to reclaim any disk space that SnapMirror may have truncated for replication. (See the Options section and vol for more information on these two volume options.)
A destination qtree must be quiesced before it can be broken.
resync [ -n ] [ -f ] [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c create_dest_snap ] [ -w ] destination
Resynchronizes a broken-off destination to its former source, putting the destination in the snapmirrored state and making it ready for update transfers. The resync command must be issued on the destination filer.
The resync command can cause data loss on the destination. Because it is effectively making desti_ n ation a replica of the source, any edits made to the destination after the break will be undone.
For formerly mirrored volumes, the resync command effectively performs a SnapRestore (see vol ) on the destination to the newest snapshot which is common to both the source and the destination. In most cases, this is the last snapshot transferred from the source to the destination, but it can be any snapshot which is on both the source and destination due to SnapMirror replication. If new data has been written to the destination since the newest common snapshot was created, that data will be lost during the resync operation.
For formerly mirrored qtrees, SnapMirror restores data to the file system from the latest SnapMirrorcreated snapshot on the destination volume. Unlike the volume case, it requires this last snapshot in order to perform a resync .
The resync command initiates an update transfer after the SnapRestore or qtree data restoration completes.
The -n option reports what execution of the resync command would do, but does not execute the command.
The -f option forces the operation to proceed without prompting for confirmation.
The -S option sets the source of the transfer, and works the same for resync as it does for initialize .
The -k option sets the throttle, in kilobytes per second, of the transfer, and works the same for resync as it does for initialize .
A opción-c só funciona a un resync para un qtree. Con este SnapMirror opción crea unha instantánea chamado create_dest_snap sobre o destino, tras a transferencia completa resync (de xeito que non compite con todas as actualizacións en curso). SnapMirror non bloquear ou eliminar este instantáneo. Create_dest_snap non pode ser hourly.x, nightly.x, ou weekly.x, porque estes nomes son reservados para os snapshots programadas.
A opción-s só funciona a un resync para un qtree. Ela designa unha instantánea chamado src_snap a partir do cal traslada o SnapMirror qtree, no canto de crear unha instantánea de orixe e trasladar o qtree do novo instantáneo. Esta opción é usada para transferir o contido de unha instantánea específico, por exemplo, pode transferir unha foto que foi tirada mentres unha base de datos estaba nun estado estable e consistente. SnapMirror non bloquear ou borrar o src_snap. Src_snap non pode ser hourly.x, nightly.x, weekly.x, snapshot_for_backup.x ou snapshot_for_volcopy.x.
A opción-w fai que o comando non voltar en canto a transferencia resync comeza. Pola contra, só pode esperar ata a conclusión da transferencia (ou non), momento en que ha imprimir o status de conclusión e despois volver. Esta opción non ten efecto se a opción-n tamén se especifica.
destinos [-s] [fonte]
Lista todos os destinos coñecidos actualmente para as fontes sobre este filler. Para volumes, esta orde tamén lista todos os destinos en cascada, que son todos os volumes que son réplicas de destinos directos. Este comando debería incluír todos os descendentes deses que coñece.
A opción-s inclúe na lista os nomes de instantáneas retidos no volume de orixe por cada destino.
Unha fonte específica que se especifica, só a destinos que o volume será na lista. A fonte pode ser un nome de volume ou un camiño qtree.
fonte de liberación {filler: volume | filler: qtree}
Diga SnapMirror que un espello certo directa xa non vai para solicitar actualizacións.
Se un determinado destino non está indo para solicitar actualizacións, ten que dicir SnapMirror para que non vai máis manter unha instantánea para este destino. Este comando ha eliminar fotos que non son máis necesarias para a replicación ao destino, e pode ser usado para limpar SnapMirror-creados instantáneas despois da pausa SnapMirror soa no lado do destino.
The source argument is the source volume or qtree that the destination is to be released from. The destination argument should be either the destination filer and destination volume name or the destination filer and destination qtree path. You can use a line from the output of the snapmirror destinations command as the set of arguments to this command.
store [ -g geometry ] destination tapedevices
Dumps an image of the destination volume to the tapedevices specified. This is much like the snapmirror initialize command, but from a source volume to a tape device. You can use the tapes and the retrieve command to perform the initial, priming transfer on any restricted volume.
Using the -g option on a snapmirror store will optimize the tape for a particular destination traditional volume. The geometry argument is a string which describes the geometry of the intended destination traditional volume. It can be acquired by using the snapmirror retrieve -g command on that traditional volume. Using this option can increase snapmirror retrieve performance dramatically. The -g option is only effective with traditional volumes.
Only volumes can be stored to or retrieved from tape. Qtrees cannot be stored to or retrieved from tape.
The tapedevices field of this command is a commaseparated list of valid tape devices. See tape for more information on tape device names.
Tape devices are not supported on vfilers. This command runs on the physical filer only.
retrieve { destination tapedevices | -h tapedevice | -g volume }
Restores the image on the tapedevices to the desti_ n ation specified. This is much like the snapmirror initialize command, but from a tape device to a destination volume. If destination is part of a SnapMirror relationship with the source volume from the store performed to create these tapes, the two volumes can be mirrored as if volume had been primed via an initial transfer over the network.
You can use the -h flag to read the header off of the single tapedevice specified. This will provide information on the tape source and index.
The -g option provides the volume geometry string for the specified volume . This string, when given to the snapmirror store -g command, will dramatically improve snapmirror retrieve performance to this volume .
The tapedevices field of this command is a commaseparated list of valid tape devices. See tape for more information on tape device names.
This feature only works for volumes. Qtrees cannot be stored to or retrieved from tape.
Tape devices are not supported on vfilers. This command runs on the physical filer only.
use destination tapedevices
Continues a tape transfer to destination with the specified tapedevices .
Unha tenda ou operación de rescate é executado fóra de cinta, el solicitará que o usuario proporcione outra banda. Tras outra banda recibiu, o comando de uso é chamado para contar o proceso de SnapMirror onde atopalo.
O campo de destino é indicado por arquivador: volume, no caso de recuperar, e arquivador: tapedevices, no caso de tenda.
O campo tapedevices deste comando é unha lista de dispositivos de cinta commaseparated válidos. Ver cinta para obter máis información sobre nomes de dispositivos de cinta.
Dispositivos de cinta non é compatíbel no vfilers. Este comando execútase no filler física só.
acelerador destino <n>
Modifica o valor do acelerador para a transferencia SnapMirror ao destino co valor especificado en kilobytes por segundo. Isto define a velocidade máxima á que os datos son trasfered a través da rede para a transferencia de cadea. Un valor de cero, se pode empregar para desactivar de estrangulamento.
O novo valor será usado só para a transferencia de cadea. A próxima transferencia calendario usará o valor KBS especificado no arquivo snapmirror.conf. Se o valor para a opción KBS no snapmirror.conf cambia, mentres que a transferencia está a suceder, entón o novo valor entrará en vigor dentro de dous minutos.
abortar [-h] destino ...
Aborts currently executing transfers to all specified destination s. It may take a few minutes for a transfer to clean up and abort. This does not stop new updates from starting. If you are interested in stopping further updates use the snapmirror quiesce command.
Any transfer with a restart checkpoint (you can view this via the snapmirror status command) may be restartable; to clear out the restart checkpoint and force any subsequent transfer to start with a fresh snapshot on the source, you can use abort -h on the destination. The -h option specifies that this is a hard abort; the restart checkpoint will be cleared out in addition to the transfer being stopped.
The abort command can be invoked from either the source or the destination filer. However, the -h option is only effective on the destination filer. The option will be ignored if specified on the source filer.
migrate [ -n ] [ -f ] [ -k kilobytes ] [ source_filer :] source_volume [ destination_filer :] desti t ion_volume
snapmirror migrate is run on the filer which holds the source volume. It must be run on two volumes which are already the source and destination of a SnapMirror pair.
snapmirror migrate will transfer data and NFS filehandles from the source_volume to the desti t ion_filer 's destination_volume (if no filer is specified, then migrate assumes the volume is local). If source_filer is specified, then the migrate destination will use that network interface to connect up to the source filer for the transfer of information.
The first thing migrate will do is check the source and destination sides for readiness. Then, it will stop NFS and CIFS service to the source. This will prevent changes to the source volume's data, which will make it appear to clients as though nothing has changed during the migration. It will run a regular SnapMirror transfer between the two volumes. At the end of the transfer, it will migrate the NFS filehandles, bring the source offline, and make the destination volume writable.
The -n flag will make a test run; that is, it will run all the pre-transfer checks, but stop short of transferring data. The -f flag will not prompt the user for confirmation. The -k flag will throttle the speed at which the transfer runs (at kilobytes kilobytes per second), in a manner similar to that used in the snapmirror update command.
Un filler nun par de cluster de failover vai para abaixo, todas as transferencias activas son abortados. O programador SnapMirror e servizos continuarán por volumes do filler abatido. A configuración das relacións SnapMirror son tomadas a partir da opción snapmirror.access o filer abatido ou snapmirror.allow e arquivos snapmirror.conf. Aquí están algúns exemplos de uso do comando SnapMirror: O exemplo a seguir activa o programador conexionado e apagado:
torradeira SnapMirror> na torradeira SnapMirror estado> SnapMirror está conectado. torradeira> SnapMirror off torradeira> SnapMirror estado SnapMirror está desactivado. torradeira>
O exemplo seguinte mostra a situación SnapMirror con transferencias en execución. Dous son os destinos ociosas (ambos do frigorífico), un deles ten un checkpoint restart, e pode reiniciar a configuración dos dous volumes non cambiou desde o punto de verificación foi feita. A transferencia do vol1 para ARC2 só comezou, e está nos estágios iniciais de transferencia. A transferencia da torradeira para neveira está parcialmente rematada, aquí podemos ver o número de megabytes descargados. torradeira> SnapMirror estado SnapMirror está conectado. Destino Estado frigorífico Estado Lag: torradeira casa: Arc1 Snapmirrored 22:09:58 torradeira Idle: vol1 torradeira: ARC2 Snapmirrored 01:02:53 torradeira Transferencia: vol2 neveira: salvos non inicializada - Transferencia (128MB feito) neveira: usuarios torradeira: Arc3 Snapmirrored 10:14:36 Idle con checkpoint restart (12MB feito) torradeira>
O exemplo seguinte presenta estado detallado para unha das relacións SnapMirror enriba especificados como argumento para o comando. El exhibe información adicional sobre instantáneo base, tipo de transferencia, a mensaxe de erro, e última transferencia, etc torradeira SnapMirror> estado-l Arc1 SnapMirror está conectado. Orixe: neveira: Destino casa: torradeira: Arc1 Tipo: Status Volume: Progreso Idle: - Estado: Lag Snapmirrored: 22:09:58 timestamp Mirror: Mer 08 de agosto 16:53:04 GMT 2001 Snapshot Base: torradeira (0001234567) _arc1 0,1 Tipo de Transferencia actual: - Erro na descarga de corrente: - Contido: Replica Tipo de Transferencia Última: Inicializar Tamaño última descarga: 1120000 KB Duración última transferencia: Transferencia 00:03:47 Última De: neveira: home
The following example shows how to get all the volumes and qtrees that are quiesced or quiescing on this filer with the status command.
filer> snapmirror status -q Snapmirror is on. vol1 has quiesced/quiescing qtrees: /vol/vol1/qt0 is quiesced /vol/vol1/qt1 is quiescing vol2 is quiescing
The following example starts writing an image of
vol1 on toaster to the tape on tape device
rst0a and continues with the tape on
rst1a . When the second tape is used up, the example shows how to resume the store using a new tape on
rst0a .
toaster> snapmirror store vol1 rst0a, rst1a snapmirror: Reference Snapshot: snapmirror_tape_5.17.100_21:47:28 toaster> SNAPMIRROR: store to toaster:rst0a, rst1a has run out of tape. toaster> snapmirror use toaster:rst0a, rst1a rst0a toaster> Wed May 17 23:36:31 GMT [worker_thread:notice]: snapmirror: Store from volume 'vol1′ to tape was successful (11 MB in 1:03 minutes, 3 tapes written).
The following example retrieves the header of the tape on tape device
rst0a . It then retrieves the image of
vol1 from the tape on tape device
rst0a .
toaster> snapmirror retrieve -h rst0a Tape Number: 1 WAFL Version: 12 BareMetal Version: 1 Source Filer: toaster Source Volume: vol0 Source Volume Capacity: 16MB Source Volume Used Size: 11MB Source Snapshot: snapmirror_tape_5.17.100_21:47:28 toaster> toaster> snapmirror retrieve vol8 rst0a SNAPMIRROR: retrieve from tape to toaster:vol8 has run out of tape. toaster> snapmirror use toaster:vol8 rst0a SNAPMIRROR: retrieve from tape to toaster:vol8 has run out of tape. toaster> snapmirror use toaster:vol8 rst0a toaster> snapmirror status Snapmirror is on. Source Destination State Lag Status toaster:rst1a, rst0a toaster:dst1 Unknown – Transferring (17MB done) toaster> Wed May 17 23:54:29 GMT [worker_thread:notice]: snapmirror: Retrieve from tape to volume 'vol8′ was successful (11 MB in 1:30 minutes).
The following example examines the status of all transfers, then aborts the transfers to
volm1 and
volm2 , and checks the status again. To clear the restart checkpoint,
snapmirror abort is invoked again.
torradeira> SnapMirror estado SnapMirror está conectado. Destino Estado frigorífico Estado Lag: torradeira casa: volm1 Uninitialized - Transferencia (10GB feito) neveira: torradeira e: volm2 Snapmirrored 01:00:31 Transferencia (4423MB feito) torradeira> SnapMirror abortar torradeira: volm1 volm2 torradeira> SnapMirror estado SnapMirror está en . Destino Estado frigorífico Estado Lag: torradeira casa: volm1 Snapmirrored 00:01:25 frigorífico Idle: torradeira e: volm2 Snapmirrored 01:03:11 Idle con checkpoint restart (7000MB feito) torradeira> SnapMirror abortar torradeira: volm2 torradeira> estado SnapMirror SnapMirror está conectado. Destino Estado frigorífico Estado Lag: torradeira casa: volm1 Snapmirrored 00:02:35 frigorífico Idle: torradeira e: volm2 Snapmirrored 01:04:21 ocioso
O exemplo a seguir examina o estado de todas as transferencias, a continuación, anular as transferencias para volm1 e volm2 coa opción-h e comprobar o estado de novo. No checkpoint restart e salvo. toaster> snapmirror status Snapmirror is on. Source Destination State Lag Status fridge:home toaster:volm1 Uninitialized – Transferring (10GB done) fridge:mail toaster:volm2 Snapmirrored 01:00:31 Transferring (4423MB done) toaster> snapmirror abort -h toaster:volm1 toaster:volm2 toaster> snapmirror status Snapmirror is on. Source Destination State Lag Status fridge:home toaster:volm1 Snapmirrored 00:02:35 Idle fridge:mail toaster:volm2 Snapmirrored 01:04:21 Idle
Here is an example of the use of the
snapmirror migrate command:
toaster> snapmirror migrate home mirror negotiating with destination….
This SnapMirror migration will take local source volume home and complete a final transfer to destination toaster:mirror using the interface named toaster. After that, open NFS filehandles on the source will migrate to the destination and any NFS filehandles open on the destination will be made stale. Clients will only see the migrated NFS filehandles if the destination is reachable at the same IP addresss as the source. The migrate process will not take care of renaming or exporting the destination volume.
As a result of this process, the source volume home will be taken offline, and NFS service to this filer will be stopped during the transfer. CIFS service on the source volume will be terminated and CIFS will have to be set up on the destination.
Are you sure you want to do this? yes nfs turned off on source filer performing final transfer from toaster:home to mirror…. (monitor progress with “snapmirror status”) transfer from toaster:home to mirror successful starting nfs filehandle migration from home to mirror source volume home brought offline source nfs filehandles invalidated destination toaster:mirror confirms migration migration complete toaster> vol status Volume State Status Options root online normal root, raidsize=14 mirror online normal home offline normal toaster> vol rename home temp home renamed to temp you may need to update /etc/exports toaster> vol rename mirror home mirror renamed to home you may need to update /etc/exports toaster> exportfs -a
If a source volume is larger than the replica destination, the transfer is disallowed.
Notes on the snapmirror migrate command:
The migrate command is only a partial step of the process. It is intended to work when an administrator desires to move the data of one volume to another, possibly because they want to move to a new set of disks, or to a larger volume without adding disks.
We intend that migrate be run in as controlled an environment as possible. It is best if there are no dumps or SnapMirror transfers going on during the migration.
The clients may see stale filehandles or unresponsive NFS service while migrate is running. This is expected behavior. Once the destination volume is made writable, the clients will see the data as if nothing has happened.
migrate will not change exports or IP addresses; the new destination volume must be reachable in the same way as the source volume once was.
CIFS service will need to be restarted on the migrate destination.
Here are SnapMirror-related options (see options , protocolaccess , snapmirror , and snapmirror.allow for details on these options):
snapmirror.access
Controls SnapMirror access to a filer.
snapmirror.checkip.enable
Controls SnapMirror IP address checking using snapmirror.allow .
snapmirror.delayed_acks.enable
Controls a SnapMirror networking option.
replication.volume.transfer_limits
Controls increased stream counts. This option is provided to revert stream counts to legacy limits.
replication.volume.reserved_transfers
Guarantees that specified number of volume SnapMirror source/destination transfers always start. This option will reduce the maximum limit on all other transfers types and will be equivalent to maximum number of transfers possible.
snapmirror.enable
Turns SnapMirror on and off. SnapMirror can only be enabled on vfilers which are rooted on volumes.
snapmirror.log.enable
Turns SnapMirror logging on and off.
replication.volume.use_auto_resync
Turns auto resync functionality on and off for Synchronous SnapMirror relations. This option if enabled on Synchronous SnapMirror, destination will update from the source using the latest common base snapshot deleting all destination side snapshots newer than the common base snapshot.
Here are SnapMirror-related volume pseudo-options (see vol for more details):
snapmirrored
Designates that the volume is read-only.
fs_size_fixed
Effectively truncates the filesystem on the destination volume to the size of the source.
Options snapmirror.access , snapmirror.checkip.enable , and snapmirror.enable can be manipulated independently on a per-vfiler basis.
/etc/snapmirror.allow This file controls SnapMirror's access to a source filer. See snapmirror.allow , for details.
/etc/snapmirror.conf
This file controls SnapMirror schedules and relationships. See snapmirror.conf for details.
/etc/log/snapmirror
This file logs SnapMirror activity. See snapmirror for details.
aggr license options qtree vol tape(4) protocolaccess(8) snapmirror(5) snapmirror.allow(5) snapmirror.conf(5)
Índice analítico
Read more... (6038 words, estimated 24:09 mins reading time) Páxinas guía de home , manual de , NetApp , ONTAP , SnapMirror