Docu89683 Data Domain BoostFS For Windows 1.2 Configuration Guide
Docu89683 Data Domain BoostFS For Windows 1.2 Configuration Guide
Version 1.2
Configuration Guide
302-005-020
REV. 01
Copyright © 2018 Dell Inc. or its subsidiaries. All rights reserved.
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.
Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com
Figures 5
Tables 7
User identity...................................................................................31
ACL default permissions................................................................. 31
Chapter 5 Troubleshooting 33
Log information.......................................................................................... 34
Common issues...........................................................................................34
Appendix A Appendix 37
References................................................................................................. 38
l Revision history.................................................................................................. 10
l Introduction to BoostFS..................................................................................... 10
l Supported environments.................................................................................... 10
l Supported applications....................................................................................... 10
Revision history
The following table presents the revision history of this document.
Table 1 Revision history of BoostFS for Windows Configuration Guide, version 1.2
Introduction to BoostFS
Data Domain Boost Filesystem (BoostFS) 1.2 provides a general file-system interface
to the DD Boost library, allowing standard backup applications to take advantage of
DD Boost features.
Advantages of BoostFS
By leveraging the DD Boost technology, BoostFS helps reduce bandwidth, can
improve backup-times, offers load-balancing, allows in-flight encryption, and supports
the Data Domain multi-tenancy feature set.
As a file server system implementation, the BoostFS workflow is similar to CIFS but
also leverages the DD Boost protocol. In addition, BoostFS improves backup times
compared to CIFS and various copy-based solutions.
BoostFS supports single-node Data Domain systems, high-availability (HA) systems,
Extended Retention systems, Data Domain Virtual Edition, and Extended Distance
Protection.
Purpose
This document describes how to install and configure BoostFS on client systems.
Supported environments
Environments that use BoostFS 1.2 must meet the following specifications.
BoostFS for Windows requires the following:
l Data Domain Operating System version 6.1.2 or later
l Windows Server 2012, Windows Server 2012 R2, or Windows Server 2016
Supported applications
BoostFS for Windows supports the following applications:
l Commvault Simpana versions 10 and 11
l Microsoft SQL Server 2012 and 2016
l MySQL Community 5.6. and 5.7
l MySQL Enterprise Manager 5.6 and 5.7
l MongoDB Community 2.6, 3.0, and 3.2
Information about integrating BoostFS with other applications can be found in the
following white paper on the Data Domain Community site: Boost Everywhere - Data
Domain BoostFS Integration Guide: Application Validation and Best Practices for the
DD Boost File System Plug-In.
Boost features supported by BoostFS
Transport Layer Security (TLS) anonymous authentication is supported to provide
encryption.
Note
If you select TLS, be aware that there is no configuration option to enable TLS from
the client. It must be enabled through the Data Domain System.
Supported applications 11
Introduction to BoostFS for Windows
$ ddboost enable
DD Boost enabled
4. Verify distributed segment processing is enabled:
ddboost option show
Option Value
----------------------------------- --------
distributed-segment-processing enabled
virtual-synthetics enabled
fc disabled
global-authentication-mode none
global-encryption-mode medium
----------------------------------- ---------
Note
l If secure multi-tenancy (SMT) is used, the user role must be set as none.
l Users who run backup applications that connect to Data Domain systems
must have their user names configured on the Data Domain system. For
more information, refer to the Data Domain Operating System Administration
Guide.
l Multiple applications can use DD Boost to access a Data Domain system, and
multiple users can be configured for DD Boost access. The username,
password, and role must have already been set up on the Data Domain
system using the DD OS user add command:
user add <user> [password <password>]
[role {admin | limited-admin | security | user | backup-operator |
data-access}]
[min-days-between-change <days>] [max-days-between-change <days>]
[warn-days-before-expire <days>] [disable-days-after-expire <days>]
[disable-date <date>] [force-password-change {yes | no}]
For example, to add a user with a login name of jsmith and a password of
mP34$muk*E with administrative privilege, enter:
$ user add jsmith password mP34$muk*E role admin
Once the user has been created on the Data Domain system, the user must be
made a DD Boost user. To add jsmith to the DD Boost user list, enter:
$ ddboost user assign jsmith
Set the host name and domain name on the Data Domain
system
Set the host name and the domain name on the Data Domain system using the net
set CLI command.
Procedure
1. On the Data Domain system, type the following:
# net set hostname [host]
# net set {domain name [local-domain-name]}
For more information on net commands, see the Data Domain Operating System
Command Reference Guide.
A storage unit name must be unique on any given Data Domain system.
However, the same storage unit name can be used on different Data Domain
systems.
The username owns the storage unit and ensures that only connections with
this username's credentials are able to access this storage unit. See the section
on ddboost storage-unit commands in the Data Domain Operating System
Command Reference Guide for details on command options.
2. Repeat the previous step for each storage-unit needed on the Data Domain
system.
3. If you want to modify a storage unit on the Data Domain system, enter:
After entering the command, the output you see should be similar to the
following:
Note
Enabling or disabling the distributed segment processing option does not require a
restart of the Data Domain file system.
l Installation overview.......................................................................................... 20
l Prerequisites......................................................................................................20
l CBFS driver....................................................................................................... 20
l Components of BoostFS for Windows................................................................ 21
l Upgrade the BoostFS client................................................................................21
l Uninstall the BoostFS client................................................................................21
Installation overview
Install or upgrade BoostFS for Windows by using the provided MSI installer. Do not
change the default settings.
Note
If you are prompted to restart after installing, failure to do so can cause features such
as Explorer integration to not work correctly. If you are not prompted to restart,
restarting is not necessary.
Prerequisites
When installing or upgrading BoostFS for Windows:
l Use an account with administrator rights to run the installer.
l Ensure that there is enough free space to complete the installation, which requires
approximately 7 MB of disk space.
l Deactivate all BoostFS mount points. If any mount points are active, the upgrade
and removal processes fail.
CBFS driver
The MSI installer includes several binary files as well as a device driver from EldoS
Corporation.
BoostFS for Windows uses CBFS, a software interface from EldoS that enables file
systems to exist in user space and not only within a driver in kernel space. This
functionality is similar to that of FUSE on UNIX operating systems. To install BoostFS
for Windows, you must install the CBFS driver from EldoS Corporation.
Figure 2 Windows Security warning for the EldoS Corporation device driver
If another program on the system previously installed the CBFS driver, the driver that
BoostFS installs is installed alongside it and does not affect operation of the other
program.
Note
If you are prompted to restart after upgrading, failure to do so can cause features
such as Explorer integration to not work correctly. If you are not prompted to restart,
restarting is not necessary.
#############################################################################
# BoostFS 1.2 example config file for Windows
#
# The configuration file is divided into sections, delineated by brackets [].
# Options that are to apply to all mount points are in the [global] section.
# More details on the various configuration options can be found in the
# BoostFS manual. Command line options override what is in this file.
#
# Format:
# # - Identifies a comment line, and must be at the start. Configuration
# parameters can be disabled by adding a “#” to the start of the line.
#
# Values which contains spaces should use double quotations around the
# entire value.
#
# No whitespace is allowed between the option and the value, i.e.
# log-dir = \path is not allowed.
#
# Comments are not allowed after the option value pair.
#
#############################################################################
[global]
# Data Domain Hostname or IP address
# data-domain-system=dd2500-1.yourdomain.com
# Storage Unit
# storage-unit=su-name
# Text string that describes the application using boostfs with additional information such
as the version.
# app-info="text_string"
# Maximum number of connections that can be used at the same time (default: 128)
# Min value is 64. Max value is 256.
# max-connections=128
# [\\ddr-name\su-name]
# Drive Letter specifies the Windows drive to map to this UNC mount point
# drive-letter=h:
BoostFS parameters
The following parameters are used to configure BoostFS:
<data-domain-system>
The hostname or IP address of the Data Domain system.
<storage-unit>
The target storage unit on the Data Domain system.
<storage-unit-username>
The username of the storage unit owner on the Data Domain system.
<lockbox-path>
The path to the lockbox file. If this parameter is not set with the CLI or in the
configuration file, the default path is C:\BoostFS\Lockbox
\boostfs.lockbox.
<UNC-mount-path>
The Universal Naming Convention (UNC) path of the mounted storage-unit. The
UNC path must be of the form\\<data-domain-system>\<storage-unit>
<drive-letter>
The drive letter to which the BoostFS mount is mapped.
Note
The command boostfs lockbox set fails if there is an existing Lockbox file in the
same location.
In this example, Z: represents the network share that is accessible by all clients.
Procedure
1. Create the Lockbox with the -l option:
boostfs lockbox set -u <storage-unit-username> -d <data-domain-
system> -s <storage-unit> -l Z:\boostfs.lockbox
Note
After removing a client from the Lockbox, the client can no longer use the
Lockbox and can no longer access any of the Data Domain systems defined in
the Lockbox.
Note
After removing a Data Domain system or storage unit from those that the
Lockbox grants access to, none of the clients that use the Lockbox can access
the system or storage unit.
Where -d specifies the Data Domain system and -s specifies the storage unit.
If no drive letter is specified, the mount is only accessible through the UNC path.
If a BoostFS mount is established with an optional drive letter, the drive letter must be
an unused drive letter. On mount, the drive shows up in the Windows Explorer sidebar
immediately.
After mounting without a drive letter, you can use the Map Network Drive context
option in Explorer or the net use command to map the UNC path to a drive letter.
Option Description
-o log-enabled=<true | false> Enable or disable logging.
Default value: true
Option Description
-o app-info="text_string" Display a text string describing the application
using BoostFS.
Mount on startup
BoostFS is a regular process that the operating system stops when the system
restarts or the user logs off, and BoostFS for Windows mounts do not survive without
the process.
To remount BoostFS mounts during system startup, you can add boostfs mount
commands as part of a system startup or user login script. For information on system
startup and user login scripts, refer to Microsoft documentation.
See the Data Domain Operating System Command Reference Guide for more information
about the ddboost show connections command.
Mount on startup 29
Configuring and using BoostFS for Windows
Compressed restoration
This option reduces bandwidth usage when sending and receiving data, but increases
CPU usage.
When the mount option ddboost-read-compression is set to true, data is
compressed on the server before being sent to the client. When the client receives the
data, it must decompress the data. Sending and receiving compressed data uses less
network bandwidth, but compressing and decompressing the data requires a
significant amount of CPU power. By default, this option is set to false.
l As a command-line option:
boostfs mount -o ddboost-read-compression=true /mnt/bfs-mount
l As an option configured in the boostfs.conf file:
ddboost-read-compression=true
If the BoostFS file system is mounted with a drive letter, you must unmount by using
the drive letter.
If the BoostFS file system is mounted with a drive letter and a mount path, you must
unmount by using the drive letter.
If the BoostFS file system is mounted without a drive letter, you must unmount by
using the UNC mount path.
If the BoostFS file system is mounted using the Map Network Drive option:
1. Disconnect the network drive.
2. Unmount by using the UNC mount path. Do not use the drive letter.
Note
Do not use the Explorer disconnect utility to disconnect a drive that was mapped to a
drive letter with the boostfs mount command.
File security
If the required conditions are met, BoostFS for Windows supports access control lists
(ACLs) on files and directories within the BoostFS mount point.
Note
If ACLs are not used, the Boost user credentials are used for all users who access the
client mount point. Any files or directories that are created in the mount point are fully
accessible by any user with access to the mount point or storage unit.
ACL requirements
l The Data Domain system and the client must be joined to the same Active
Directory domain. If the client is not joined to a domain, ACLs cannot be enabled
during the mount process. If the Data Domain system is not joined to the domain
and ACLs are enabled during the mount process, the mount point is not accessible.
l The local-user-security option must be set to true during mount. This
setting can be applied by using the CLI or the BoostFS configuration file.
User identity
When local-user-security is enabled, the identity of the client user determines
access to a file or directory, not the identity of the storage unit user.
For a user on the client system to access a file in a BoostFS mount point, the ACL on
the file must give that user the required rights. Without Active Directory support for
ACL configuration, a client user on one system may appear to be a different user when
using a different system and be denied access to the file.
If you use ACL functionality with BoostFS for Windows, changing file permissions
by a protocol other than BoostFS for Windows causes the ACLs to be lost.
File
If no inheritance occurs, the default ACL on a file contains:
l No system access control list (SACL)
l A discretionary access control list (DACL) with the following permissions:
Creator of the file—Full control
Group of the creator of the file—Read and execute permissions
Everyone—Read and execute permissions
If inheritance occurs, the ACL on a file contains the permissions inherited from the
parent directory.
Directory
If no inheritance occurs, the default ACL on a directory contains:
l No SACL
l A DACL with the following permissions:
File security 31
Configuring and using BoostFS for Windows
l Log information..................................................................................................34
l Common issues.................................................................................................. 34
Troubleshooting 33
Troubleshooting
Log information
You can use the following log files to diagnose BoostFS problems:
l BoostFS log file
By default, the BoostFS log file is found the directory C:\BoostFS\Logs. The
default name of the file is ddboostfs_<data-domain-
hostname>_<storage-unit>.log, where:
n <data-domain-hostname>
is the hostname or IP address for the BoostFS mount
n <storage-unit>
is the storage-unit name of the BoostFS mount
A typical BoostFS log message appears in the following format:
Date + Time + Procss-ID + Thread-ID + [logging-leve: E - error, W
- warning, I - info, D - debug) + Message-Text
Common issues
Some common issues with BoostFS for Windows can be resolved quickly.
Installation fails
If installing BoostFS Windows fails, verify that:
l There is enough space on the drive on which you are installing BoostFS.
l The VeriSign Class 3 Public Primary Certification Authority - G5 is not blocked.
This root certificate is used to sign the driver.
Mount fails
Table 2 on page 35 explains the causes and resolutions of several common errors
that are encountered when mounting BoostFS.
Mount failed with This error occurs when a To map a drive to the same
error code 183: mount has the same Data mount, use the net use
Cannot create a Domain hostname and command.
file when that file storage-unit name as an
already exists. existing BoostFS mount.
Cannot mount mount- This error usually occurs Review the BoostFS log files
point: unexpected when the DD Boost protocol for more details. Use the
error, please see is not enabled and configured ddboost status command
log for details. on the Data Domain system. on the Data Domain system to
confirm that DD Boost is
enabled.
Invalid mount point This message can appear Review the specific key and
option and value when errors occur during the value in the BoostFS
pair [option=key processing of the BoostFS configuration file and make
from config file ] configuration file. any necessary corrections.
[value= value from
config file]:
Configuration
initialization
failed
Common issues 35
Troubleshooting
l References.........................................................................................................38
Appendix 37
Appendix
References
The following documents, located at Online Support, provide additional and relevant
information. Access to these documents depends on your login credentials. If you do
not have access to a document, contact a sales representative.
l Data Domain BoostFS Integration Guide: Application Validation and Best Practices,
available on https://community.emc.com
l Data Domain Operating System Version Administration Guide
l Data Domain Operating System Version Initial Configuration Guide