|
|
| Line 1: |
Line 1: |
| <span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">Backup & recovery tasks consist of:</span>
| | Backup & recovery tasks consist of: |
| <ul style="margin-top:0pt;margin-bottom:0pt;">
| |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">source - dataset or zvol with the data we want to back up</span></li>
| |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">source retention plan - schedule plan that states how often snapshots of a resource will be made and how long they will be kept; the shortest interval also manages when and how often the created snapshots will be sent to the destination</span></li>
| |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">destination - a dataset or zvol where we want to keep the backup data; when you choose the dataset as a source in destination only datasets will be available, backups can only be made from a dataset to datasets and a from zvol to zvols</span></li>
| |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">destination retention plan - schedule plan that states in which intervals the received backup snapshots should be kept and for how long</span></li>
| |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">VMware VSphere integration - if we have a datastore created on a source resource before the snapshot of source is made, Vsphere makes a snapshot of every virtual machine on the datastore, so that the data on the datastore will stay consistent (on virtual machines for this snapshot)</span></li>
| |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">task description - your own task description</span></li>
| |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">mbuffer - buffers data stream on source and destination to prevent buffer underruns and, if used correctly, to speed up the whole backup process </span></li>
| |
| </ul>
| |
|
| |
|
| <span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">Tasks can be:</span>
| | *source - dataset or zvol with the data we want to back up |
| <ul style="margin-top:0pt;margin-bottom:0pt;">
| | *source retention plan - schedule plan that states how often snapshots of a resource will be made and how long they will be kept; the shortest interval also manages when and how often the created snapshots will be sent to the destination |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">created without destination - it allows you to create local snapshots creation routine</span></li>
| | *destination - a dataset or zvol where we want to keep the backup data; when you choose the dataset as a source in destination only datasets will be available, backups can only be made from a dataset to datasets and a from zvol to zvols |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">created with local destination - destination can be some other resource on the same or different pool</span></li>
| | *destination retention plan - schedule plan that states in which intervals the received backup snapshots should be kept and for how long |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">created with remote destination - destination servers can be added in the “Destination servers” tab, but also in a wizard</span></li>
| | *VMware VSphere integration - if we have a datastore created on a source resource before the snapshot of source is made, Vsphere makes a snapshot of every virtual machine on the datastore, so that the data on the datastore will stay consistent (on virtual machines for this snapshot) |
| <li><span style="font-size:11pt; font-family:Arial; color:#000000; background-color:transparent; font-weight:400; font-style:normal; font-variant:normal; text-decoration:none; vertical-align:baseline">disabled/enabled - you can stop creating and sending snapshots to destination if required</span></li>
| | *task description - your own task description |
| </ul>
| | *mbuffer - buffers data stream on source and destination to prevent buffer underruns and, if used correctly, to speed up the whole backup process |
| | |
| | <br/>Tasks can be: |
| | |
| | *created without destination - it allows you to create local snapshots creation routine |
| | *created with local destination - destination can be some other resource on the same or different pool |
| | *created with remote destination - destination servers can be added in the “Destination servers” tab, but also in a wizard |
| | *disabled/enabled - you can stop creating and sending snapshots to destination if required |
|
| |
|
|
| |
| [[Category:Help topics]] | | [[Category:Help topics]] |
Backup & recovery tasks consist of:
- source - dataset or zvol with the data we want to back up
- source retention plan - schedule plan that states how often snapshots of a resource will be made and how long they will be kept; the shortest interval also manages when and how often the created snapshots will be sent to the destination
- destination - a dataset or zvol where we want to keep the backup data; when you choose the dataset as a source in destination only datasets will be available, backups can only be made from a dataset to datasets and a from zvol to zvols
- destination retention plan - schedule plan that states in which intervals the received backup snapshots should be kept and for how long
- VMware VSphere integration - if we have a datastore created on a source resource before the snapshot of source is made, Vsphere makes a snapshot of every virtual machine on the datastore, so that the data on the datastore will stay consistent (on virtual machines for this snapshot)
- task description - your own task description
- mbuffer - buffers data stream on source and destination to prevent buffer underruns and, if used correctly, to speed up the whole backup process
Tasks can be:
- created without destination - it allows you to create local snapshots creation routine
- created with local destination - destination can be some other resource on the same or different pool
- created with remote destination - destination servers can be added in the “Destination servers” tab, but also in a wizard
- disabled/enabled - you can stop creating and sending snapshots to destination if required