Reflexiones

Syntax:

dscli disk protect primary=<DiskID>

<mirror=<DiskID> | server=<Storage server IP address> [protocol=<fc|iscsi>] [-thindisk]

[snapshotarea=<Percentage of mirror to allocate>]>

[-mode:continuous | periodic ][daily [-days:<Every x days>] [-time:<H:M>] | hourly [-hours:<H:M>] ]

[-starttime:<Y-M-D*H:M>] [-diffscan]

[-force] [-nofsscan] [-umappath:path]

Command options and defaults

Option Description

primary Enter the Disk ID.

mirror Optional parameter. When you protect a partition, the mirror must be at least one MB larger than the primary partition. If you do not specify mirror=<DiskID>, mirror disk size will be one MB larger than the primary partition and protection will be defined with all defaults specified below. You should specify a pre-configured storage server to automatically assign the mirror disk.

server Enter either the IP address or hostname of the storage server.

protocol Protocol can be either Fibre Channel or iSCSI. The default is iSCSI if both protocols are enabled. Otherwise the default is the protocol enabled on the server.

-thindisk You can use this option if the size of the primary disk is at least 10 GB.

-mode Periodic protection mode is the default; synchronization between the primary disk and the mirror will occur daily at the current time. You can specify a synchronization schedule with the following details:

 Specify a time for the first synchronization.  Synchronize every x days at a certain time.  Synchronize every x hours.

 Exclude a period of time specified in days and/or hours.

If you specify Continuous mode, all write operations are performed on the protected disk and its mirror at the same time.

If the mirror disk is a remote device managed by CDP, the default snapshot schedule is daily at the current system time in Continuous mode, or based on the synchronization schedule defined for Periodic mode.

snapshotarea If your mirror disk is a remote device managed by CDP,

snapshotarea is the snapshot resource area to be allocated from the mirror disk, between 10 and 99 percent of the mirror.The default value is 50.

-starttime:<Y-M-D*H:M> The default start time for initial synchronization is the current time. You can modify the year, month, day, hour, and minute. A start time earlier than the current time is seen as current

Thindisk

Thin Provisioning allows you to use your storage more efficiently by allocating a minimum amount of space for the virtual resource. When usage thresholds are met, additional storage is allocated as necessary. The maximum size of a disk with thin provisioning is limited to 67,108,596 MB. The minimum permissible size of a thin disk is 10 GB.

Periodic protection mode

Periodicmode is the default. In this mode, I/O operations are performed only on the protected disk and all blocks that are changed after synchronization are flagged. When the next synchronization point is reached, all flagged blocks are synchronized (copied) from the protected disk to the mirror. Unless you specify a daily or hourly synchronization schedule when you initially protect a disk or partition,

synchronization will occur daily at the current time.

If you specify a daily schedule without specifying frequency (every x days), the default for days is 1 (every day).

If you specify an hourly schedule without specifying an option for hours, default for hours is 1 (every hour).

-diffscan Use this option to analyze each synchronization block on- the-fly during synchronization and transmit only changed sectors in the block.

-force You can use this option when the specified mirror disk has partitions.

-nofsscan Use this option to disable the file system scan, which is enabled by default. The file system scan copies only the sectors used by the file system during initial synchronization. Any unallocated space or partition with a file system which is not supported by DiskSafe will be treated as different data. File systems ext2, ext3, ext4, and reiserfs are currently supported.

-umappath:path The default path for the synchronization control map (U-map file) is /usr/local/falconstor/disksafe.

Use this option to designate a different location for storing the U-map file only if instructed to do so by FalconStor Technical Support.

Notes: The U-map file should be hosted on a disk that is at least as reliable as the primary disk. Do not use the iSCSI disk to host the U-map file other than for testing purposes.

For example:

Sample command:

# dscli disk protect primary=sdb server=172.30.10.10 protocol=iscsi snapshotarea=20 -mode:periodic hourly -hours:2:0

You can change the existing synchronization schedule. You can also specify a synchronization schedule if you change from Continuous to Periodic mode.

Continuous protection mode

In Continuousmode, the local disk and its mirror are updated simultaneously. Keep in mind that disk write operations are slower when I/O is mirrored continuously. Example:

# dscli disk protect primary=sdb mirror=sdc -mode:continuous

Disk write operations can also affect synchronization. Options to ’Limit I/O

throughput’ and ’Set maximum pending I/O’ can be used to manage the effect of I/O on mirroring.

Option Description

-mode:periodic daily -days:2 -time:09:30

Synchronization will occur every 2 days, starting today, at 9:30 a.m.

-mode:periodic hourly Synchronization will occur once an hour, starting at the

current time.

-mode:periodic hourly -hours:02:30

Synchronization will occur every 2 hours 30 minutes, starting at the current time.

-mode:periodic hourly -starttime:2015-01- 28*17:12

Synchronization will occur once an hour, starting at 17:12 on January 28, 2015.

-mode:periodic hourly -exclude:17:20-19:30

Synchronization will occur once an hour, starting at the current time, excluding the period between 17:20 and 19:30.

-mode:periodic hourly -exclude:21:00-23:00 -starttime:2015-01- 28*17:20

Synchronization will occur once an hour, excluding the period between 21:00 and 23:00, starting at 17:20 on January 28, 2015