Data Protection
327
Titan SiliconServer
NDMP_BLUEARC_USE_SNAPSHOT_RULE
NDMP_BLUEARC_AWAIT_IDLE
NDMP_BLUEARC_SPARSE_DATA
Possible value
Notes
Snapshot rule name
This variable causes NDMP to back up the latest snapshot created under
the specified snapshot rule. This can be used to backup the contents of a
snapshot that has been taken at a specific time. For instance it can be
used to back up databases.
NDMP does not create or delete snapshots if this variable is set. For a
successful backup, the snapshot should not be deleted until after the
operation has completed. In addition, the snapshot should be kept around
long enough to support incremental backups.
Possible value
Notes
y or n (Default y)
By default the data management engine imposes an interlock to stop
NDMP backups and "adc" copies from the destination of a replication
while a replication copy is actively writing data. This is intended to help
installations that replicate to a volume and back up from there. However,
the lock is held at a volume level and with directory level replication and
it may be desirable to override this action.
To make use of this replication interlock, it is necessary to specify this
rule option on both the replication that is intended to do the waiting, as
well as the replication that is waited upon.
Possible value
Notes
NONE, BASE, or
UPDATE
This setting controls the omission of unset or unchanged data when
backing up or transferring files. A Block Level Replication license is
required to enable this feature. If the setting is NONE (the default) then
files are always sent in their entirety including any unset data areas.
The BASE setting will omit non-initialized areas of files from the data
stream. This is particularly useful for files such as iSCSI LUNs or Database
files where significant parts of the files may not have been written. The
setting of UPDATE includes the BASE setting features but additionally will
send only changed blocks of a file when doing incremental copies or
backups. This setting is not recommended as files backed up in this way
are only partially included in the backup and cannot be recovered from
this single backup - a full correct sequence of backups must be recovered
to recreate the file.
