Werrej
snapmirror - volum, u duplikazzjoni qtree snapmirror {fuq | off} snapmirror istat [għażliet] [volum | qtree ... ]
snapmirror Initialize [għażliet] destinazzjoni
snapmirror aġġornament [għażliet] destinazzjoni
snapmirror quiesce destinazzjoni
snapmirror destinazzjoni jerġa
waqfa snapmirror [għażliet] destinazzjoni
snapmirror resync [għażliet] destinazzjoni
destinazzjonijiet snapmirror [Għażla] [source]
snapmirror rilaxx sors destinazzjoni
snapmirror {maħżen | irkuprata} volum tapedevices
snapmirror tapedevices destinazzjoni użu
snapmirror throttle <n> destinazzjoni
snapmirror abort [għażliet] ... destinazzjoni
snapmirror jemigraw [għażliet] destinazzjoni sors
Il-kmand snapmirror huwa użat biex jikkontrolla SnapMirror, metodu ta 'tirrifletti volumi u qtrees. Hija tippermetti lill-utent biex jippermettu u jiskonnettja skedati u trasferimenti manwali ta 'data, informazzjoni talba dwar it-trasferimenti, tibda t-trasferiment tad-data initializing, bidu aġġornament ta' mera, temporanjament aġġornamenti nieqaf għal mera, break relazzjonijiet mera, resynchronize mirja miksur, informazzjoni destinazzjoni lista , tfal mirja rilaxx, il-volum stampi taħżen tejp, jirkupraw immaġini volum minn tejp, u trasferimenti abort għaddejjin. SnapMirror jista 'jintuża biex jirreplika volumi jew qtrees. Il-proċessi u l-imgieba involuti huma ftit (u xi kultant sottili) differenti bejn it-tipi varji ta 'data duplikazzjoni.
The SnapMirror process is destination-driven. The snapmirror initialize command starts the first transfer which primes the destination with all the data on the source. Prior to the initial transfer, the destination must be ready to be overwritten with the data from the source; destination volumes must be restricted (see vol ), and destination qtrees must not yet exist.
For asynchronous mirrors, the destination periodically requests an update from the source, accepts a transfer of data, and writes those data to disk. These update transfers only include changes made on the source since the last transfer. The SnapMirror scheduler initiates these transfers automatically according to schedules in the snapmirror.conf file.
Synchronous mirrors will initially behave asynchronously, but will transition to synchronous mode at first opportunity. These mirrors may return to asynchronous mode on error (eg a network partition between the mirroring filers) or at the request of the user.
The snapmirror update command can be used to initiate individual transfers apart from the scheduled ones in snapmirror.conf .
After the initial transfer, the destination is available to clients, but in a read-only state. The status of a destination will show that it is snapmirrored (see aggr , vol , or qtree for more details on displaying the destination state).
Biex tuża l-destinazzjoni għall-kitba kif ukoll qari, li huwa utli f'każ ta 'diżastru jagħmel is-sors disponibbli jew meta inti tixtieq li tuża l-destinazzjoni bħala volum tat-test / qtree, inti tista' tintemm ir-relazzjoni SnapMirror mal-kmand waqfa snapmirror. Dan il-kmand bidliet istatus id-destinazzjoni tal minn snapmirrored għal imkisser off, u b'hekk jagħmilha writable. Il-kmand resync snapmirror jistgħu jbiddlu lura l-istatus ta 'destinazzjoni qabel li snapmirrored u se resynchronize kontenut tiegħu mal-sors. (Meta applikata għal sors ta 'qabel, snapmirror resync tista jibdluh mera tad-destinazzjoni qabel. B'dan il-mod, ir-rwoli ta' sors u destinazzjoni jistax jitreġġa 'lura.)
A filer żżomm kont ta 'destinazzjonijiet kollha, jew mirja diretti jew mirja ta' mirja, għal kull sorsi tiegħu. Din il-lista tista 'tintwera permezz ta' l-kmand destinazzjonijiet snapmirror. Il-kmand rilaxx snapmirror jistgħu jintużaw biex tgħid filer li 1 mera dirett ċerti se aġġornamenti talba ma jibqgħux.
Biex jiffrankaw bandwidth netwerk, tejp jistgħu jintużaw biex prime volum mera ġdida minflok il-kmand initialize snapmirror. Il-miżbliet snapmirror kmand maħżen immaġni tas-sors għall-tejp. Il-kmand irkuprata snapmirror tirrestawra dehra volum minn tejp u jipprepara l-volum għal trasferimenti aġġornament fuq in-netwerk. Jekk tejps multipli huma użati biex tinħoloq immaġini volum, il-kmand użu snapmirror huwa użat li tordna lill-maħżen ta 'stennija jew irkuprata proċess li tikteb produzzjoni jew jaċċettaw input lejn / minn apparat tejp ġdid. Il-kmandijiet store and retrieve ma jistgħux jintużaw ma 'qtrees.
Il-kmand jemigraw snapmirror hija użata fuq sors eżistenti u par destinazzjoni li jagħmlu l-volum destinazzjoni writable "jimitaw" tas-sors. Id-destinazzjoni jassumi r-filehandles NFS tas-sors, tgħin lill-amministratur filer biex jevitaw NFS mill-ġdid immuntar fuq it-naħa tal-klijent.
Il-fajl snapmirror.conf fuq il-volum għerq il-filer destinazzjoni tal jikkontrolla l-konfigurazzjoni u l-iskedar ta 'SnapMirror fuq id-destinazzjoni. Ara snapmirror.conf għal aktar dettalji dwar konfigurazzjoni u l-iskedar ta 'SnapMirror.
Aċċess għal sors huwa kkontrollat bl-għażla snapmirror.access fuq il-filer sors. Ara għażliet u protocolaccess (8) għall-informazzjoni dwar it-twaqqif l-għażla.
(Jekk l-għażla snapmirror.access huwa ssettjat għal "wirt", l-aċċess huwa kkontrollat mill-fajl snapmirror.allow fuq il-volum għerq il-filer ikkonċernat. Ara snapmirror.allow għal aktar dettalji.)
SnapMirror huwa servizz liċenzjat, u liċenzja għandha tinkiseb qabel l-kmand snapmirror jistgħu jintużaw. SnapMirror għandhom ikunu liċenzjati kemm fuq is-sors u filers destinazzjoni. Ara liċenzja għal aktar dettalji.
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.
Each vfiler has its own /etc/snapmirror.conf file in its root volume. SnapMirror can be turned on or off on a vfiler independently. SnapMirror commands issued on a vfiler can only operate on volumes or qtrees it has exclusive ownership of.
For backward compatibility, the physical filer (vfiler0) can operate on all volumes and all qtrees, even if they are owned by vfilers. It is highly recommanded, however, that all storage units (volumes and qtrees) be mirrored from either vfiler0 or the hosting vfiler, not both. When vfiler storage units are mirrored via vfiler0, leave snapmirror off on the vfiler.
The
snapmirror command has many subcommands. Nearly every command takes a
destination argument. This argument takes three different forms. The form used for a particular invocation depends on whether you're specifying a volume or a qtree.
Volumes are specified by their name:
vol1
Qtrees are specified by their fully-qualified path:
/vol/vol1/qtree
There is a special path that can be used to SnapMirror all the data in a volume which does not reside in a qtree. This path can only be used as a SnapMirror source, never a SnapMirror destination. The path is specified as:
/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 trasferimenti kollha attivi SnapMirror tad-data u tiddiżattiva l-kmandi li tibda trasferimenti ġodda (initialize, aġġornament, resync, taħżen, u jerġgħu jieħdu lura), u jibdel il-Scheduler SnapMirror off.
Il-mixgħul / mitfi istat ta 'SnapMirror tippersisti permezz reboots, u huwa rifless mill-għażla snapmirror.enable. Din l-għażla tistax tiġi paċuta u fuq, u dan għandu l-istess effett eżatt kif il-snapmirror fuq jew snapmirror off jikkmanda.
istatus ['l |-t | q] [volum | qtree ... ]
Rapporti istatus ta 'l-relazzjonijiet ma' SnapMirror sors u / jew destinazzjoni fuq dan filer. Dan il-kmand jirrapporta wkoll jekk SnapMirror huwa fuq jew off. Jekk xi volum jew argumenti qtree huma mogħtija lill-kmand, biss ir-relazzjonijiet ma 'SnapMirror sors tqabbil jew destinazzjoni se jiġu rrapurtati. Jekk l-argument mhuwiex validu, mhux se jkun hemm kwalunkwe status fil-produzzjoni.
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
Starts an initial transfer over the network. An initial transfer–either over the network or from tape–is required before update transfers can take place. The initialize command must be issued on the destination filer. If the destination is a volume, it must be restricted (see vol for information on how to examine and restrict volumes). If the destination is a qtree, it must not already exist (see qtree for information on how to list qtrees). If a qtree already exists, it must be renamed or removed (using an NFS or CIFS client), or snapmirror initialize to that qtree will not work.
If the snapmirror status command reports that an aborted initial transfer has a restart checkpoint, the initialize commmand will restart the transfer where it left off.
Il-S-għażla tispeċifika filer sors u l-volum jew il-passaġġ qtree, f'format simili għal dik ta 'argumenti eżaminazzjoni des_ t. Is-sors għandha taqbel mal-dħul għad-destinazzjoni fil-fajl snapmirror.conf. Jekk ma taqbilx ma ', l-operazzjoni stampi messaġġ ta' żball u aborts. Jekk lS-għażla ma tkunx stabbilita, is-sors użat huwa dak speċifikat mid-dħul għal dik id-destinazzjoni fil-fajl snapmirror.conf. Jekk ma jkunx hemm tali dħul, l-operazzjoni stampi messaġġ ta 'żball u aborts.
Il-k-għażla jistabbilixxi l-veloċità massima li biha data hija trasferita fuq in-netwerk fl-kilobytes kull sekonda. Huwa użat biex throttle disk, CPU, u l-użu tan-netwerk. Din l-għażla sempliċement tistabbilixxi valur massimu għall-veloċità tat-trasferiment; ma tiggarantix li t-trasferiment se jmorru li mgħaġġel. Jekk din l-għażla ma tkunx stabbilita, il-filer jittrasmetti data skond id-Kbs jistabbilixxu għal din ir-relazzjoni fil-fajl snapmirror.conf (ara snapmirror.conf). Madankollu, jekk din l-għażla mhuwiex stabbilit u m'hemm l-ebda kuntest Kbs għal din ir-relazzjoni fil-fajl snapmirror.conf, il-filer jittrasmetti data malajr kemm jista '.
Il-c-unika għażla taħdem għal initialize għal qtree. B'din l-għażla, SnapMirror toħloq stampa msemmija create_dest_snap dwar id-destinazzjoni wara l-initialize temm b'suċċess (sabiex ma jikkompetix ma 'kwalunkwe aġġornamenti kontinwi). SnapMirror ma jissakkar jew tħassar din l-istampa. Create_dest_snap ma tistax tkun hourly.x, nightly.x, jew weekly.x, għaliex dawn l-ismijiet huma riservati għal Snapshots skedati.
-I-unika għażla taħdem għal initialize għal qtree. Tinnomina stampa jismu src_snap minnu SnapMirror jittrasferixxi l-qtree, minflok ma jinħolqu stampa sors u trasferiment tal-qtree mill-istampa l-ġdida. Din l-għażla jintuża biex jittrasferixxi kontenut 1 snapshot speċifiku fuq; per eżempju, jista 'jittrasferixxi stampa li ttieħdet waqt database kienet stabbli, l-istat konsistenti. SnapMirror ma jissakkar jew iħassar il-src_snap. Src_snap ma tistax tkun hourly.x, nightly.x, weekly.x, snapshot_for_backup.x jew snapshot_for_volcopy.x.
Lw-għażla tikkawża l-kmand ma jmorrux lura ladarba t-trasferiment inizjali jibda. Minflok, se stenna sakemm it-trasferiment itemm (jew tonqos), f'liema ħin se jistampaw l-istatus tlestija u mbagħad jirritornaw.
aġġornament [S sors] [-k kilobytes] [-s src_snap] [-c create_dest_snap] [w] destinazzjoni
Għal mirja mhux sinkroniku, aġġornament immedjatament beda mill-għajn sa l destinazzjoni biex taġġorna l-mera mal-kontenut tas-sors.
Għal mirja sinkroniku, stampa hija maħluqa fuq il-volum sors li ssir viżibbli għall-klijenti tal-volum destinazzjoni.
Il-kmand aġġornament għandu jinħareġ fuq il-filer destinazzjoni.
Il-S-għażla settijiet-sors tat-trasferiment, u jaħdem l-istess għal aġġornament bħal ma tagħmel għall initialize.
Il-k-għażla settijiet-throttle, fil kilobytes kull sekonda, tat-trasferiment, u jaħdem l-istess għal aġġornament bħal ma tagħmel għall initialize.
Il-c-unika għażla jaħdem għal aġġornament għal qtree. Ma 'dan SnapMirror għażla toħloq stampa msemmija create_dest_snap dwar id-destinazzjoni wara l-tikkompleta aġġornament (sabiex ma jikkompetix ma' kwalunkwe aġġornamenti kontinwi). SnapMirror ma jissakkar jew tħassar din l-istampa. Create_dest_snap ma tistax tkun hourly.x, nightly.x, jew weekly.x, għaliex dawn l-ismijiet huma riservati għal Snapshots skedati.
Il s-unika għażla jaħdem għal aġġornament għal qtree. Tinnomina stampa jismu src_snap minnu SnapMirror jittrasferixxi l-qtree, minflok ma jinħolqu stampa sors u trasferiment tal-qtree mill-istampa l-ġdida. Din l-għażla jintuża biex jittrasferixxi kontenut 1 snapshot speċifiku fuq; per eżempju, jista 'jittrasferixxi stampa li ttieħdet waqt database kienet stabbli, l-istat konsistenti. SnapMirror ma jissakkar jew iħassar il-src_snap. Src_snap ma tistax tkun hourly.x, nightly.x, weekly.x, snapshot_for_backup.x jew snapshot_for_volcopy.x.
Lw-għażla tikkawża l-kmand ma jmorrux lura ladarba t-trasferiment inkrementali jibda. Minflok, se stenna sakemm it-trasferiment itemm (jew tonqos), f'liema ħin se jistampaw l-istatus tlestija u mbagħad jirritornaw.
quiesce destinazzjoni
Tippermetti fil-progress trasferimenti lil destinazzjoni biex jitlesta wara li t-trasferimenti ġodda mhumiex permessi biex tibda. Mirja sinkroniku se jittieħdu mill-modalità sinkroniku. Kwalunkwe talba oħra biex taġġorna dan il-volum jew qtree se jonqsu sa l-kmand jerġa snapmirror hija applikata għaliha.
Dan il-kmand għandu tifsira speċjali għal destinazzjonijiet qtree. A destinazzjoni qtree li qed tiġi modifikata mill SnapMirror matul trasferiment se jkollhom bidliet preżenti fiha. Dawn il-bidliet mhux ser jiġu esportati lill-klijenti NFS jew CIFS. Madankollu, jekk kopja tittieħed matul dan iż-żmien, l-istampa se jkun fih il-kontenut transizzjonijiet tal-qtree. Quiesce se ġġib dik qtree barra ta 'stat transizzjoni, jew mill-irfinar jew undoing kwalunkwe bidliet trasferiment għamlet. Istatus snapmirror jista tirrapporta jekk 1 qtree huwa quiesced jew le. Il-proċess quiesce jistgħu jieħdu xi żmien biex jitlesta filwaqt SnapMirror jagħmel tibdiliet kontenut tal-qtree tal. Kull stampa meħuda waqt li qtree huwa quiesced se jkun fiha l-immaġni ta 'dik qtree li jaqbel mal-kontenut esportati lill-klijenti NFS u CIFS.
jerġa destinazzjoni
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.
The -f option forces a snapmirror break between snaplocked volume relationship without prompting for conformation.
This command does not modify the snapmirror.conf file. Any scheduled transfers to a broken mirror will fail.
For volumes, this command has the same effect as the vol options snapmirrored off command, and will remove the snapmirrored option from a 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 .
The -c option only works for a resync to a qtree. With this option SnapMirror creates a snapshot named create_dest_snap on the destination after the resync transfer completes (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 a resync 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.
The -w option causes the command not to return once the resync transfer starts. Instead, it will wait until the transfer completes (or fails), at which time it will print the completion status and then return. This option has no effect if the -n option is also specified.
destinations [ -s ] [ source ]
Lists all of the currently known destinations for sources on this filer. For volumes, this command also lists any cascaded destinations; these are any volumes which are replicas of direct destinations. This command will list all such descendants it knows about.
The -s option includes in the listing names of snapshots retained on the source volume for each destination.
If a specific source is specified, only destinations for that volume will be listed. The source may either be a volume name or a qtree path.
release source { filer : volume | filer : qtree }
Tell SnapMirror that a certain direct mirror is no longer going to request updates.
Jekk destinazzjoni partikolari m'għadux se jitlob aġġornamenti, għandek tgħid lit SnapMirror sabiex ma jibqax iżomm stampa għal dik id-destinazzjoni. Dan il-kmand se tneħħi Snapshots li m'għadhomx meħtieġa għar-replikazzjoni għal dik id-destinazzjoni, u jistgħu jintużaw biex tnaddaf SnapMirror-maħluqa Snapshots wara waqfa snapmirror tinħareġ fuq in-naħa destinazzjoni.
L-argument sors huwa l-volum sors jew qtree li d-destinazzjoni għandha tkun rilaxxata minn. L-argument destinazzjoni għandu jkun jew il-filer destinazzjoni u l-isem volum destinazzjoni jew il-filer destinazzjoni u l-path qtree destinazzjoni. Tista 'tuża linja mill-produzzjoni tal-kmand destinazzjonijiet snapmirror bħala s-sett ta' argumenti għal dan il-kmand.
maħżen ['g ġeometrija] destinazzjoni tapedevices
Miżbliet immaġni tal-volum destinazzjoni għall-tapedevices speċifikati. Dan huwa ħafna bħall-kmand initialize snapmirror, iżda minn volum sors ma 'apparat tejp. Tista 'tuża l-tapes u l-kmand irkuprata biex iwettqu t-trasferiment inizjali priming, fuq kull volum ristrett.
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 .
If a store or retrieve operation runs out of tape, it will prompt the user to provide another tape. After another tape has been provided, the use command is invoked to tell the SnapMirror process where to find it.
The destination field is specified by filer : volume in the case of retrieve , and filer : tapedevices in the case of store .
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.
throttle <n> destination
Modifies the throttle value for the snapmirror transfer to the destination with the specified value in kilobytes per second. This sets the maximum speed at which the data is trasfered over the network for the current transfer. A value of zero can be used to disable throttling.
The new value will be used only for the current transfer. The next scheduled transfer will use the kbs value specified in the snapmirror.conf file. If the value for the kbs option in the snapmirror.conf is changed while transfer is going on, then the new value will take effect within two minutes.
abort [ -h ] destination …
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.
Il-kmand abort jistgħux jiġu invokati jew mill-sors jew il-filer destinazzjoni. Madankollu, il-h-għażla hija effettiva biss fuq il-filer destinazzjoni. L-għażla se jiġu injorati jekk speċifikat fuq il-filer sors.
jemigraw [n] [-f] [-k kilobytes] [source_filer:] source_volume [destination_filer:] destinazzjoni t ion_volume
jemigraw snapmirror għandu jseħħ fuq l filer li jkollu l-volum sors. Għandu jiġi jimxu fuq żewġ volumi li huma diġà is-sors u destinazzjoni ta 'par SnapMirror.
jemigraw snapmirror se trasferiment tad-data u filehandles NFS mill-source_volume għall-destinazzjoni t ion_filer "i destination_volume (jekk l-ebda filer huwa speċifikat, allura jemigraw jassumi l-volum huwa lokali). Jekk source_filer huwa speċifikat, allura l-destinazzjoni jemigraw se jużaw dik network interface għall-konnessjoni sa l-filer sors għat-trasferiment ta 'informazzjoni.
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.
If one filer in a cluster failover pair goes down, any active transfers are aborted. The SnapMirror scheduler and services will continue for volumes on the downed filer. The configurations of the SnapMirror relationships are taken from the downed filer's
snapmirror.access option or
snapmirror.allow and
snapmirror.conf files.
Here are a few examples of use of the
snapmirror command:
The following example turns the scheduler on and off:
toaster> snapmirror on toaster> snapmirror status Snapmirror is on. toaster> snapmirror off toaster> snapmirror status Snapmirror is off. toaster>
The following example presents the
snapmirror status with transfers running. Two are idle destinations (both from fridge); one of these has a restart checkpoint, and could be restarted if the setup of the two volumes has not changed since the checkpoint was made. The transfer from
vol1 to
arc2 has just started, and is in the initial stages of transferring. The transfer from toaster to icebox is partially completed; here, we can see the number of megabytes transferred.
toaster> snapmirror status Snapmirror is on. Source Destination State Lag Status fridge:home toaster:arc1 Snapmirrored 22:09:58 Idle toaster:vol1 toaster:arc2 Snapmirrored 01:02:53 Transferring toaster:vol2 icebox:saved Uninitialized – Transferring (128MB done) fridge:users toaster:arc3 Snapmirrored 10:14:36 Idle with restart checkpoint (12MB done) toaster>
The following example presents detailed status for one of the above snapmirror relationships specified as argument to the command. It displays extra information about base snapshot, transfer type, error message, and last transfer, etc.
toaster> snapmirror status -l arc1 Snapmirror is on. Source: fridge:home Destination: toaster:arc1 Type: Volume Status: Idle Progress: – State: Snapmirrored Lag: 22:09:58 Mirror Timestamp: Wed Aug 8 16:53:04 GMT 2001 Base Snapshot: toaster(0001234567)_arc1.1 Current Transfer Type: – Current Transfer Error: – Contents: Replica Last Transfer Type: Initialize Last Transfer Size: 1120000 KB Last Transfer Duration: 00:03:47 Last Transfer From: fridge: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 maħżen vol1 rst0a, rst1a snapmirror: Referenza Snapshot: snapmirror_tape_5.17.100_21: 47:28 toaster> SNAPMIRROR: maħżen li toaster: rst0a, rst1a jispiċċaw ta 'tape. toaster> użu snapmirror toaster: rst0a, rst1a rst0a toaster> Wed Mejju 17 23:36:31 GMT [worker_thread: Avviż]: snapmirror: Aħżen minn "vol1 'volum li tejp kienet ta' suċċess (11 MB fil-minuti 1:03, 3 tejps bil-miktub).
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.
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 toaster:volm1 volm2 toaster> snapmirror status Snapmirror is on. Source Destination State Lag Status fridge:home toaster:volm1 Snapmirrored 00:01:25 Idle fridge:mail toaster:volm2 Snapmirrored 01:03:11 Idle with restart checkpoint (7000MB done) toaster> snapmirror abort 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
The following example examines the status of all transfers, then aborts the transfers to
volm1 and
volm2 with the
-h option and checks the status again. No restart checkpoint is saved.
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)
Table of Contents
Read more... (6038 words, estimated 24:09 mins reading time) 
