Contents

Dell PowerProtect 19.6 Data Manager File System Agent User Guide PDF

1 of 51
1 of 51

Summary of Content for Dell PowerProtect 19.6 Data Manager File System Agent User Guide PDF

PowerProtect Data Manager for File System Agent User Guide

Version 19.6

October 2020 Rev. 01

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid

the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Preface.........................................................................................................................................................................................5

Chapter 1: PowerProtect Data Manager for File System Agent Overview.......................................9 PowerProtect Data Manager overview..........................................................................................................................9 Prerequisites......................................................................................................................................................................... 9 Firewall and port considerations.....................................................................................................................................10 PowerProtect Data Manager new deployment overview......................................................................................... 11 PowerProtect Data Manager existing deployment overview...................................................................................11

Chapter 2: Enabling the File System Agent.................................................................................. 13 About the File System agent........................................................................................................................................... 13 Application agent and File System agent coexistence..............................................................................................13 File System agent prerequisites..................................................................................................................................... 15 File System agent limitations...........................................................................................................................................16 Block based backups......................................................................................................................................................... 16 Best practices for File System backups....................................................................................................................... 17 Configure the File System parallel backup setting..................................................................................................... 17 Roadmap for protection with the File System agent................................................................................................ 18 Installing and upgrading the File System agent on Linux......................................................................................... 18

Install the File System agent on Linux.....................................................................................................................18 Upgrade the File System agent on Linux...............................................................................................................20 Uninstall the File System agent on Linux...............................................................................................................22

Installing and upgrading the File System agent on Windows..................................................................................22 Install the File System agent on Windows ............................................................................................................22 Upgrade the File System agent on Windows........................................................................................................24 Uninstall the File System agent on Windows........................................................................................................26

Manage the PowerProtect agent service................................................................................................................... 26 About the PowerProtect agent service................................................................................................................. 26 Start, stop, or obtain the status of the PowerProtect agent service............................................................ 27 Troubleshoot the PowerProtect agent service operations...............................................................................28 Register the PowerProtect agent service to a different server address on Linux..................................... 29 Register the PowerProtect agent service to a different server address on Windows.............................. 29 Recovering the PowerProtect agent service from a disaster..........................................................................30

Chapter 3: Managing Storage, Assets, and Protection.................................................................32 Manage the File System agent...................................................................................................................................... 32 Add protection storage ...................................................................................................................................................33

Troubleshooting protection policy for DD storage unit......................................................................................34 Viewing the DD Boost storage unit password......................................................................................................34

Enable an asset source.................................................................................................................................................... 34 Disable an asset source..............................................................................................................................................35

Discover a File System host........................................................................................................................................... 35 Add a protection policy for File System protection.................................................................................................. 36 Edit the retention period for backup copies............................................................................................................... 38 Delete backup copies....................................................................................................................................................... 39

Contents

Contents 3

Retry a failed backup copy deletion........................................................................................................................40 Export data for deleted backup copies.................................................................................................................. 40 Remove backup copies from the PowerProtect Data Manager database.....................................................41

Exclusion filters...................................................................................................................................................................41 Add an exclusion filter.................................................................................................................................................41 Guidelines for exclusion filters..................................................................................................................................42 Edit or delete an exclusion filter.............................................................................................................................. 43 Apply an exclusion filter to a protection policy.................................................................................................... 44 Remove an exclusion filter from a protection policy...........................................................................................44

Centralized and file-level restore of a File System host..........................................................................................45 Centralized restore of File Systems........................................................................................................................45 File-level restore from File System backups.........................................................................................................46

Troubleshooting File System agent backups.............................................................................................................. 47

Chapter 4: Self-Service Backup and Restore of the File System Agent........................................ 48 Performing self-service backups of File Systems..................................................................................................... 48 Performing self-service restore of a File System host............................................................................................ 49

Using the ddfsadmin utility for File Systems........................................................................................................ 49 Self-service image-level restore of File Systems................................................................................................ 49 Self-service file-level restore of File Systems......................................................................................................50

4 Contents

Preface As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the software or hardware currently in use might not support some functions that are described in this document. The product release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in this document, contact a technical support professional.

NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this document,

go to the Support website https://www.dell.com/support.

Data Domain (DD) is now PowerProtect DD. References to Data Domain or Data Domain systems in this documentation, in

the user interface, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many

cases the user interface has not yet been updated to reflect this change.

Purpose This document describes how to configure and administer the PowerProtect Data Manager software to protect and recover data on the file system host. The PowerProtect Data Manager Administration and User Guide provides additional details about configuration and usage procedures.

Audience This document is intended for the host system administrator who is involved in managing, protecting, and reusing data across the enterprise by deploying PowerProtect Data Manager software.

Revision history The following table presents the revision history of this document.

Table 1. Revision history

Revision Date Description

01 October 27, 2020 Initial release of this document for PowerProtect Data Manager version 19.6.

Compatibility information Software compatibility information for the PowerProtect Data Manager software is provided in the eLab Navigator, available at https://elabnavigator.emc.com/eln/modernHomeDataProtection.

Related documentation The following publications are available on Dell EMC Online Support and provide additional information:

PowerProtect Data Manager Administration and User GuideDescribes how to configure the software. PowerProtect Data Manager Deployment GuideDescribes how to deploy the software. PowerProtect Data Manager Release NotesContains information on new features, known limitations, environment, and

system requirements for the software. PowerProtect Data Manager Security Configuration GuideContains security information. PowerProtect Data Manager AWS Deployment GuideDescribes how to deploy the software to Amazon Web Services

(AWS).

Preface 5

PowerProtect Data Manager Azure Deployment GuideDescribes how to deploy the software to Microsoft Azure. PowerProtect Data Manager Cloud Disaster Recovery Administration and User GuideDescribes how to deploy Cloud DR,

protect VMs in the AWS or Azure cloud, and run recovery operations. PowerProtect Data Manager for Cyber Recovery User GuideDescribes how to install, upgrade, patch, and uninstall the

Dell EMC PowerProtect Cyber Recovery software. PowerProtect Data Manager for File System Agent User GuideDescribes how to configure and use the software with the

File System agent for file system data protection. PowerProtect Data Manager for Microsoft Application Agent Exchange Server User GuideDescribes how to configure

and use the software in a Microsoft Exchange Server environment. PowerProtect Data Manager for Microsoft Application Agent SQL Server User GuideDescribes how to configure and use

the software in a Microsoft SQL Server environment. PowerProtect Data Manager for Oracle RMAN Agent User GuideDescribes how to configure and use the software in an

Oracle Server environment. PowerProtect Data Manager for SAP HANA Agent User GuideDescribes how to configure and use the software in an SAP

HANA Server environment. PowerProtect Data Manager for Storage Direct Agent User GuideDescribes how to configure and use the software with

the Storage Direct agent to protect data on VMAX storage arrays through snapshot backup technology. PowerProtect Data Manager API documentation: https://developer.dellemc.comContains the PowerProtect Data

Manager APIs and includes tutorials to guide to you in their use.

Typographical conventions The following type style conventions are used in this document:

Table 2. Style conventions

Formatting Description

Bold Used for interface elements that a user specifically selects or clicks, for example, names of buttons, fields, tab names, and menu paths. Also used for the name of a dialog box, page, pane, screen area with title, table label, and window.

Italic Used for full titles of publications that are referenced in text.

Monospace Used for:

System code System output, such as an error message or script Pathnames, file names, file name extensions, prompts, and syntax Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.

[ ] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means or for the alternate selections.

{ } Braces enclose content that the user must specify, such as x, y, or z.

... Ellipses indicate non-essential information that is omitted from the example.

You can use the following resources to find more information about this product, obtain support, and provide feedback.

Where to find product documentation https://www.dell.com/support https://www.dell.com/community

6 Preface

Where to get support The Support website https://www.dell.com/support provides access to product licensing, documentation, advisories, downloads, and how-to and troubleshooting information. The information can enable you to resolve a product issue before you contact Support.

To access a product-specific page:

1. Go to https://www.dell.com/support. 2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword.

To search the Knowledgebase:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Knowledge Base. 3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by

typing a product name in the search box, and then selecting the product from the list that appears.

Live chat To participate in a live interactive chat with a support agent:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Contact Support. 3. On the Contact Information page, click the relevant support, and then proceed.

Service requests To obtain in-depth help from Licensing, submit a service request. To submit a service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests.

NOTE: To create a service request, you must have a valid support agreement. For details about either an account or

obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the

Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests. 3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Online communities For peer contacts, conversations, and content on product support and solutions, go to the Community Network https:// www.dell.com/community. Interactively engage with customers, partners, and certified professionals online.

Preface 7

How to provide feedback Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to DPAD.Doc.Feedback@emc.com.

8 Preface

PowerProtect Data Manager for File System Agent Overview

Topics:

PowerProtect Data Manager overview Prerequisites Firewall and port considerations PowerProtect Data Manager new deployment overview PowerProtect Data Manager existing deployment overview

PowerProtect Data Manager overview Use PowerProtect Data Manager with the application agent to perform the following operations:

Automate the configuration of the application agent backup policy and protection storage settings. Create a catalog of backups that are produced by the application agent, and then monitor that catalog data to determine if

retention policies are being adhered to. Manage the life cycle of backups that are created by the application agentthat is, ensure that the backups are marked for

garbage collection based on the rules of the retention policy.

PowerProtect Data Manager does not change the way that the application agent works. DBAs or system/backup administrators create the backups and perform the restores.

Prerequisites Ensure that your environment meets the requirements for a new deployment or upgrade of PowerProtect Data Manager.

Requirements:

A list of hosts that write backups to DD systems is available. DD OS version 6.1 or later and the DD Management Console (DDMC). All models of DD systems are supported.

NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and use

a DD system directly without DDMC.

Application agent 19.6 or earlier. License: A trial license is provided with the PowerProtect Data Manager software. DPS Applications, Backup, and Enterprise

customers can contact Dell EMC Licensing Support for assistance with a permanent PowerProtect Data Manager license. Large environments require multiple PowerProtect Data Manager instances. Contact Champions.eCDM@emc.com for

assistance with sizing requests. The PowerProtect Data Manager 19.6 download file requires the following:

ESXi version 6.5, 6.7, or 7.0. 8 vCPUs, 18 GB RAM, one 100 GB disk, and one 500 GB disk. The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI. TCP port 7000 is open between PowerProtect Data Manager and the application agent hosts.

VMware ESXi server that hosts PowerProtect Data Manager meets the following minimum system requirements:

10 CPU cores 18 GB of RAM for PowerProtect Data Manager Five disks with the following capacities:

Disk 1100 GB Disk 2500 GB

1

PowerProtect Data Manager for File System Agent Overview 9

Disk 310 GB Disk 410 GB Disk 55 GB

One 1-GB NIC

Firewall and port considerations The latest version of the PowerProtect Data Manager Security Configuration Guide provides more details about the port requirements.

Table 3. PowerProtect Data Manager port requirements

Description Communication Port

SSH communications Bidirectional communication between the SSH client and the PowerProtect Data Manager appliance.

22 TCP/UDP

SQL, Oracle, Exchange, SAP HANA, File System

Bidirectional communication between the PowerProtect Data Manager agent and the PowerProtect Data Manager appliance.

Requirement applies to Application Direct and VM Direct.

7000 TCP

REST Server Bidirectional communication between the HTTP client and the PowerProtect Data Manager appliance.

8443 TCP

RESTAPI Server - VM Direct

Bidirectional communication between the PowerProtect Data Manager agent and the PowerProtect Data Manager appliance.

Requirement applies to SQL VM application-aware.

8443 TCP

UI redirect Inbound only. 80 TCP

443

LDAP Outbound only. 389 TCP/UDP

636 TCP

Discovery (devices) Outbound between the PowerProtect Data Manager appliance and the device.

3009 TCPStorage Direct and DD system

5989 TCPSMI-S

443 TCPXtremIO

7225 TCPRecoverPoint

PowerProtect Data Manager agent

Bidirectional communication between the database hosts and the PowerProtect Data Manager appliance.

This requirement applies to both Application Direct and VM Direct.

7000 TCP

Embedded VM Direct service

Outbound. 9090 TCP

10 PowerProtect Data Manager for File System Agent Overview

PowerProtect Data Manager new deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the File System agent.

Steps

1. Design how to group the backups based on the storage requirements and retention policies.

The account team can help with backup storage design.

2. Install DD Management Center (DDMC).

PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

3. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

4. Add external DD systems or DDMC to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

5. Install the File System agent on the appropriate hosts and connect them to PowerProtect Data Manager according to the instructions in the next chapter.

6. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next chapter.

7. Add a protection policy for groups of assets that you want to back up.

NOTE: After you create a centralized protection job, the first backup is a full backup.

The PowerProtect Data Manager Administration and User Guide provides instructions.

8. Add Service Level Objectives to the protection policy to verify that the protected assets meet the Service Level Agreements (SLAs).

The PowerProtect Data Manager Administration and User Guide provides instructions.

9. Now that the configuration is complete, it is recommended to perform a full backup so that PowerProtect Data Manager can detect the proper backup chain.

Without a full backup, PowerProtect Data Manager treats the backups as partial and assumes that you are out of compliance.

10. Monitor protection compliance in the PowerProtect Data Manager dashboard.

PowerProtect Data Manager existing deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the File System agent in an existing environment.

Steps

1. Install DD Management Center (DDMC).

PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

3. Add external DD systems or DDMC to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

4. Upgrade the File System agent or uninstall and then reinstall the agent on the hosts, and connect them to PowerProtect Data Manager according to the instructions in the next chapter.

PowerProtect Data Manager for File System Agent Overview 11

5. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next chapter.

6. Add a protection policy for groups of assets that you want to back up.

NOTE: After you create a centralized protection job, the first backup is a full backup.

The PowerProtect Data Manager Administration and User Guide provides instructions.

7. Add Service Level Objectives to the protection policy to verify that the protected assets meet the Service Level Agreements (SLAs).

The PowerProtect Data Manager Administration and User Guide provides instructions.

8. Now that the configuration is complete, it is recommended to perform a full backup so that PowerProtect Data Manager can detect the proper backup chain.

Without a full backup, PowerProtect Data Manager treats the backups as partial and assumes that you are out of compliance.

9. Monitor protection compliance in the PowerProtect Data Manager dashboard.

12 PowerProtect Data Manager for File System Agent Overview

Enabling the File System Agent

Topics:

About the File System agent Application agent and File System agent coexistence File System agent prerequisites File System agent limitations Block based backups Best practices for File System backups Configure the File System parallel backup setting Roadmap for protection with the File System agent Installing and upgrading the File System agent on Linux Installing and upgrading the File System agent on Windows Manage the PowerProtect agent service

About the File System agent The File System agent enables an application administrator to protect and recover data on the file system host. PowerProtect Data Manager integrates with the File System agent to check and monitor backup compliance against protection policies. PowerProtect Data Manager also enables central scheduling for backups.

You can install the File System agent on the host that you plan to protect by using the installation wizard. Installing and upgrading the File System agent on Linux on page 18 provides instructions.

NOTE: PowerProtect Data Manager supports the coexistence of agents on the same Windows or Linux host for the

following:

Microsoft SQL agent and the File System agent on Windows.

Microsoft Exchange agent and the File System agent on Windows.

Oracle/RMAN agent and the File System agent on Linux.

SAP HANA agent and the File System agent on Linux.

You can now deploy PowerProtect Data Manager and DD Virtual Edition (DDVE) with the File System agent in a Microsoft Azure environment.

Software compatibility information for the PowerProtect Data Manager software and the File System agent is provided in the eLab Navigator, available at https://elabnavigator.emc.com/eln/modernHomeDataProtection.

Application agent and File System agent coexistence PowerProtect Data Manager supports the coexistence of the Microsoft SQL and Exchange application agent with the File System agent on Windows, and the Oracle agent or SAP HANA agent with the File System agent on Linux, which enables you to protect the SQL, Exchange, Oracle, or SAP HANA database with the host file system. The following coexistence scenarios are supported:

Both agents in managed mode (registered to PowerProtect Data Manager) The SQL, Exchange, Oracle, or SAP HANA agent in stand-alone mode, with the File System agent registered to

PowerProtect Data Manager

NOTE: The latest version of each agent must be installed if the agents are registered to PowerProtect Data Manager. The

File System agent is supported in managed mode only.

The steps for installation and usage for each agent are the same.

2

Enabling the File System Agent 13

The table below lists the supported use cases and limitations.

Table 4. Supported cases

Category Supported cases Current limitations

Agent installation and uninstallation

1. New installation of both agents with:

a. SQL application agent, Exchange agent, Oracle RMAN agent, or SAP HANA agent in stand-alone or managed mode.

b. File System agent in managed mode. 2. New installation of an agent in managed mode

with an already existing agent in stand-alone mode.

3. New installation of an agent in stand-alone mode with an already existing agent in managed mode.

4. Repair of an already existing agent installation. 5. Uninstallation of agents.

Uninstalling the last agent installed on the host unregisters the host from PowerProtect Data Manager. Any new agent installation that occurs after the uninstall will have to be newly registered to the PowerProtect Data Manager server.

Similar to the agent installations, uninstallation of each agent is performed separately.

Host registration and unregistration

1. Registration of an installed agent to the PowerProtect Data Manager server.

2. Changing the registration of an already registered agent to a different PowerProtect Data Manager server.

3. Unregistration of agents from the PowerProtect Data Manager server.

Both agents, if operating in managed mode, should be registered to the same PowerProtect Data Manager server only. There is no option to register each agent to a different PowerProtect Data Manager server.

On an already registered host, performing a direct registration (explicitly using register.sh/register.bat) with a different PowerProtect Data Manager server IP will unregister the host from the current PowerProtect Data Manager server and register the host to the new server. Stand- alone agents will continue to operate in stand- alone mode and will not be registered.

Unregistering a host will unregister all of the managed agents installed on that host. Stand- alone agents will not be affected.

After unregistering a host, the host's assets will still display in the UI in order to support restore of these assets to a different host. However, backups will not be initiated on these assets as the protection policies will be disabled.

Backup and restore features

1. Protection policy creation supported on all registered agents.

2. All scheduled protection policy backups are supported on both agents as per individual protection policies.

3. Self-service backups are supported on both agents.

4. Compliance is supported on both agents as per the individual Service Level Agreements (SLAs).

5. Manual backups are supported at the protection policy level and individual asset level through the centralized protection policy workflow.

14 Enabling the File System Agent

File System agent prerequisites Review the following prerequisites before installing and using the File System agent in PowerProtect Data Manager.

Windows and Linux prerequisites

Ensure that your host is a 64-bit system. PowerProtect Data Manager supports only 64-bit hosts. Ensure that your host is a supported operating system version.

Software compatibility information for the PowerProtect Data Manager software is provided in the eLab Navigator, available at https://elabnavigator.emc.com/eln/modernHomeDataProtection.

Both the PowerProtect Data Manager server and client must be a minimum version of 19.3 in order to perform centralized and file-level restore of File Systems in PowerProtect Data Manager.

Ensure that all clocks on both the host and PowerProtect Data Manager are time-synced to the local NTP server to ensure discovery of the backups.

Ensure that the host and the PowerProtect Data Manager network can see and resolve each other.

If PowerProtect Data Manager and the File System agent are registered in a different domain, in order to ensure that asset and copy discovery complete successfully, you must add host entries (IP address and FQDN) on both the client and server. This applies to both Windows and Linux clients. For example, on PowerProtect Data Manager, you would be required to add the File System agent host entries, and on the File System agent, you would be required to add the PowerProtect Data Manager host entries:

1. Browse to the path of the hosts file. For example, on Windows C:\Windows\System32\drivers\etc\hosts, and on Linux /etc/hosts.

2. Add an entry to the hosts file, as in the following:

IP address FQDN common name 10.10.100.100 yourdomain.com yourdomain

LVM/VxVM partitions/volumes are supported. Physical partitions are supported only when using file-based backups. Each volume group on LVM2 or VxVM must have at least 10% free space for a block based backup to succeed. For

successful Windows VSS snapshot during block based backup, the free space requirement is 20%. For any ESXi version 6.5 and earlier host with PowerStore storage attached, the Windows operating system deployment/

installation cannot proceed and File System agent backup and restore operations will fail if the DiskMaxIOSize parameter is not configured with the proper value. Ensure that you set the DiskMaxIOSize to 1024 KB.

Review the limitations in the section File System agent limitations on page 16.

Linux prerequisites

File system discovery requires an ext3, ext4, or XFS file system type. On the Linux hosts that have the UEFI Secure Boot option enabled, block based backup drivers do not load, and the error

message insmod: ERROR: could not insert module /lib/ modules/ 3.10.0-693.el7.x86_64/ extra/nsrbbb.ko: Required key not available appears. As a workaround, you can disable the Secure Boot option.

Ensure that the File System has the /etc/fstab entry. Without the /etc/fstab entry, discovery fails.

To enable file-level restores, complete the following:

1. Log in to the system you are restoring from as root.

2. Install iSCSI client packages.

Refer to the Operating System documentation for the installation procedure.

3. For Service Start, choose Manually, and then click OK. Install the lsb_release package.

Refer to the Operating System documentation for the installation procedure.

Enabling the File System Agent 15

File System agent limitations Review the following limitations related to File System agent support in PowerProtect Data Manager.

Windows and Linux limitations

File System agent block based backups will exclude the following:

Application files such as SQL and Exchange. HyperVisor files. Note that the File System agent is installed primarily in the guest operating system for the backup of

guest file system volumes, and is not dependent on the underlying HyperVisor. Data belonging to individual application writers. Unsupported application writer's files.

It is recommended to use different mount points for each drive. Reusing mount points might cause unexpected issues during File System discovery.

The File System agent does not support non-English operating systems. Software compatibility information for the PowerProtect Data Manager software and the File System agent is provided in the eLab Navigator, available at https:// elabnavigator.emc.com/eln/modernHomeDataProtection.

If a Windows or Linux File System host is unregistered from PowerProtect Data Manager and then re-registered with a different FQDN, because PowerProtect Data Manager recognizes the registration as a new host by its new name, duplicate asset entries will appear in the UIthose for the host registered earlier, as well as for the host registered by the new name. This does not impact backup and restore functionality on the new host.

IPv6 is not supported. Use IPv4 instead. Image-level recovery to a system volume is not supported. The File System agent and application agents use the FQDN for registration. If the File System agent coexists with the

Microsoft SQL, Oracle, or SAP HANA application agent, both agents must use the FQDN. For a protection policy backup with assets from different hosts, the backup status displays as "Failed" in the UI if the backup

of one asset within the policy fails. Running the ddfssv and ddfsrc commands to perform self-service backup and restore of File Systems fails if you provide

the DD host name (instead of IP) for the DFA_SI_DD_HOST variable. If the Bytes of sector sizes of the source and target volumes are different, PowerProtect Data Manager does not support

block based image recoveries. For example, you cannot perform a block based image recovery of a volume that has 4096 as the Bytes of sector size to a volume that has 512 as the Bytes of sector size, and vice versa.

Linux limitations

PowerProtect Data Manager does not support ext4 file systems on SuSE Linux Enterprise Server (SLES) version 11 SP1-SP4 platforms. The ext4 file system is read-only on SLES version 11.

On the Linux hosts that have the UEFI Secure Boot option enabled, block based backup drivers do not load, and the error message insmod: ERROR: could not insert module /lib/ modules/ 3.10.0-693.el7.x86_64/ extra/nsrbbb.ko: Required key not available appears. As a workaround, you can disable the Secure Boot option.

A File System backup might fail with the error Insufficient space exists in the volume group for creating shadow of the volume when there is not enough space in the volume group for a block based backup to succeed. Each volume group on LVM2 or VxVM must have at least 10% free space.

Block based backups Block based backups provide instant access to the backups. The block based backups enable you to mount the backups by using the same file systems that you used to back up the data.

The File System agent's block based backups support the following capabilities:

Mounting of a backup as a file system Mounting of an incremental backup Sparse backup support Backups of operating system-deduplicated file systems as source volumes on Windows

16 Enabling the File System Agent

Forever virtual full backups to Data Domain Data Domain retention lock Recoveries from Data Domain

Block based backups are useful for datasets that are under 10 TB with a single volume under 5 TB, and a daily change rate under 5%.

Best practices for File System backups Consider the following best practices for File System backups.

1. Ensure that subsequent backup schedules do not overlap.

If a full backup is in progress when the next incremental backup starts, then the incremental backup is promoted to a full backup. If the schedules overlap, the incremental backup continues to get promoted to a full backup because a full backup has not completed. Also, overlapping backup schedules might fail as a result of concurrent snapshots or other limitations that are caused by the underlying system.

To identify the optimal backup window between full backups and the first incremental backup, measure the backup time that is required for a small asset. Use this time as an indicator to assess the backup window for assets that are larger in size. For example:

Data backup speed = asset size / time taken to back up the asset Total backup size = sum of the total size of the assets to be backed up for a full backup Maximum backup window = total backup size / data backup speed Optimal backup window = maximum backup window / parallelism value

You can use the calculations in the example to assess the backup window for subsequent incremental backups based on the data change rate between backups.

2. If the data source is encrypted or compressed, the DD system provides limited deduplication. This increases the time that is taken to back up the data, as compared to data that is not encrypted or compressed.

Configure the File System parallel backup setting PowerProtect Data Manager enables you to run File System backups in parallel to reduce the time taken for backups. This setting defines the maximum concurrent network sessions from the client to the DD system at any given time. You can specify the number of streams to use for the backup in the configuration file .ddfssv.fsagentconfig or through the self-service CLI. However, it is recommended that you set the parallelism value in the configuration file as the parallelism value provided in the configuration file takes precedence over the parallelism value that is provided in the CLI.

NOTE: Backup parallelism is only available on supported Windows systems. Since the parallelism setting is defined at the

host level, you must set the parallelism setting on every Windows host where parallel file system backups are enabled.

To specify the number of streams to use for the backup, you can set the File System parameter --max-host-streams in the .ddfssv.fsagentconfig file that is located in the C:\Program Files\DPSAPPS\fsagent\settings directory on the File System host. This value must be an integer. The default value is 8.

For example, if you set the --max-host-streams parameter value to 6, the File System agent backups run with 6 streams:

--max-host-streams=6

You can also use the command-line option -M to specify the number of streams to use for the backup. For example:

ddfssv -LL -l INCR -z -M 4 -a DFA_SI=TRUE -a DFA_SI_USE_DD=TRUE -a DFA_SI_DD_HOST=protection_storage_system_ip_address -a DFA_SI_DD_USER=protection_storage_user -a DFA_SI_DD_PASSWORD=protection_storage_system_password -a DFA_SI_DEVICE_PATH=protection_storage_device_path I: where:

-a "DFA_SI_DD_HOST=protection_storage_system_ip_address"

Specifies the name of the DD server that contains the storage unit where you want to back up the databases.

-a "DFA_SI_DD_PASSWORD=protection_storage_system_password"

Enabling the File System Agent 17

Specifies the password of the protection storage system user.

-a "DFA_SI_DEVICE_PATH=protection_storage_device_path"

Specifies the name and the path of the protection storage device where you want to direct the backup.

-a "DFA_SI_DD_USER=protection_storage_user"

Specifies the protection storage username. For example, sysadmin.

Recommendations for optimal performance:

Tune the parallelism value based on the resources that are available on your system, including the CPU, the number of assets, and the connection bandwidth to the DD system.

Set the parallelism value equal to the number of CPU cores on the host. Run backups in parallel for several assets that are small in size, as opposed to running backups in parallel for a few assets

that are large in size.

Roadmap for protection with the File System agent The following roadmap provides the steps required to configure the File System agent in PowerProtect Data Manager in order to run protection policies.

Steps

1. Add a storage system.

Add protection storage on page 33 provides information.

2. Install the File System agent on the File System host.

Installing and upgrading the File System agent on Linux on page 18 provides information.

3. Add or approve the File System agent on each File System host.

Manage the File System agent on page 32 provides information.

4. Discover the File system asset.

Discover a File System host on page 35 provides information.

5. Create a protection policy to protect the File System.

Add a protection policy for File System protection on page 36 provides information.

NOTE: You cannot perform a backup to a secondary DD system. You can only restore from a secondary DD system.

Installing and upgrading the File System agent on Linux Learn how to install and upgrade the File System agent on Linux.

Install the File System agent on Linux

Install the File System agent on supported Linux systems using an interactive or silent installation procedure.

Install the File System agent on Linux in interactive mode

Use this interactive procedure to Install the File System agent on supported Linux systems.

Prerequisites

Ensure that you review the prerequisites provided in File System agent prerequisites on page 15. Download the File System agent software package to the Linux host.

18 Enabling the File System Agent

NOTE: If a value is not provided for PowerProtect Server IP in the installation commands, the product is installed without

PowerProtect registration, and no backups can be initiated from the UI.

Steps

1. In the PowerProtect Data Manager UI:

a. Select Agent Downloads from the System Settings menu. b. Select the File System agent download package for Linux, fsagent196_linux_x86_64.tar.gz.

c. Download the package in the location that you want to install the File System agent.

NOTE: Relocating the installation to another partition or mount point on Linux is not supported.

2. Untar the installer by running tar -xvf fsagent196_linux_x86_64.tar.gz.

Then run the command cd fsagent to change the current working directory to the extracted path.

NOTE: To validate the .rpm files prior to the installation step, follow the instructions in Knowledgebase article number

546613 at https://www.dell.com/support/kbdoc/en-us/546613.

3. Run the installation script install.sh.

To run in debug mode, run install.sh --debug.

To get help, run install.sh --help.

NOTE: For installations on Oracle Linux, run install.sh --skip-driver to skip the block based backup driver

installation. The Oracle Linux version 7 platform does not currently support block based backups. Therefore, all backups

performed by the File System agent on Oracle Linux 7 will be file-based backups.

The following .rpm or .deb files are installed as part of the script:

powerprotect-agentsvc.rpm or powerprotect-agentsvc.debInstalls or upgrades the agent service component for File System agent.

ppdm_bbbwt.rpm or ppdm-bbbwt.debInstalls the block based backups driver.

ppdm_fsagent.rpm or ppdm-fsagent.debInstalls the File System agent related files and folders.

4. Type the PowerProtect Data Manager server FQDN or IP address. It is recommended to use the FQDN.

NOTE: If another application agent is already installed on the client and registered to PowerProtect, ensure that you

register the agent with the existing PowerProtect Data Manager server FQDN. When you register the agent with a

PowerProtect Data Manager server that is different from the currently registered server, no warning message displays,

and requests are routed to the newer server instance.

Next steps

If the host is not already whitelisted or approved, add the File System host to the PowerProtect Data Manager server. Manage the File System agent on page 32 provides more information.

Discover File System assets. Discover a File System host on page 35 provides more information.

Install the File System agent on Linux in silent mode

On Linux, review the following commands to perform a silent installation of the File System agent.

NOTE:

The --server option is used to specify the PowerProtect server IP for registration, and is mandatory for silent install.

To validate the .rpm files prior to the installation step, follow the instructions in Knowledgebase article number 546613 at

https://www.dell.com/support/kbdoc/en-us/546613.

Use the following commands to perform a silent installation on Linux:

For silent installation, including registration of the agent with the PowerProtect server, type: install.sh --silent- install --server=

Enabling the File System Agent 19

To run the installer in debug mode during silent installation, type: install.sh --debug --silent-install -- server=

To skip installation of the block based backup driver, type: install.sh --skip-driver --silent-install -- server= .

Upgrade the File System agent on Linux

The File System agent supports a direct upgrade from an earlier version if you are using an earlier version of PowerProtect Data Manager. You can upgrade the PowerProtect Data Manager File System agent on supported Linux systems in interactive or silent mode.

About this task

Upgrade and register the latest version of the PowerProtect Data Manager File System agent for Linux with the same PowerProtect Data Manager server in the same location.

NOTE: When you install or upgrade the File System agent, other app agents on the system must be upgraded to the same

version as the File System agent.

Upgrade the File System agent on Linux in interactive mode

Use this interactive procedure to upgrade the File System agent on supported Linux systems.

Prerequisites

Ensure that you review the prerequisites provided in File System agent prerequisites on page 15. Download the File System agent software package to the Linux host.

Steps

1. In the PowerProtect Data Manager UI:

a. Select Agent Downloads from the System Settings menu. b. Select the File System agent download package for Linux, fsagent196_linux_x86_64.tar.gz.

c. Download the package in the location that you want to install the File System agent.

NOTE: Relocating the installation to another partition or mount point on Linux is not supported.

2. Untar the installer by running tar xvf fsagent196_linux_x86_64.tar.gz.

Then run the command cd fsagent to change the current working directory to the extracted path.

NOTE: To validate the .rpm files prior to the installation step, follow the instructions in Knowledgebase article number

546613 at https://www.dell.com/support/kbdoc/en-us/546613.

3. Run the install.sh script. The following .rpm or .deb files are installed as part of the script:

powerprotect-agentsvc.rpm or powerprotect-agentsvc.debInstalls or upgrades the agent service component for File System agent.

ppdm_bbbwt.rpm or ppdm-bbbwt.debInstalls the block based backups driver.

ppdm_fsagent.rpm or ppdm-fsagent.debInstalls the File System agent related files and folders.

4. Type the PowerProtect Data Manager server FQDN or IP address. It is recommended to use the FQDN.

NOTE: If another application agent is already installed on the client and registered to PowerProtect, ensure that you

register the agent with the existing PowerProtect Data Manager server FQDN. When you register the agent with a

PowerProtect Data Manager server that is different from the currently registered server, no warning message displays,

and requests are routed to the newer server instance.

20 Enabling the File System Agent

Upgrade the File System agent on Linux in silent mode

Use the following commands to perform a silent upgrade of the File System agent on Linux:

NOTE: To validate the .rpm files prior to the upgrade step, follow the instructions in Knowledgebase article number

546613 at https://www.dell.com/support/kbdoc/en-us/546613.

To run the silent agent upgrade, type: install.sh --force-upgrade NOTE: The --force-upgrade command line option does not prompt users to upgrade other agents so that they are

running the same version as the File System agent. Ensure that other agents are running the same version as the File

System agent, otherwise those agents will not work.

To run the silent upgrade and register the agent with a new PowerProtect server, type: install.sh --force-upgrade --server=PowerProtect Server IP

For silent upgrade in debugging mode, type: install.sh --force-upgrade --debug

NOTE: During silent installation/upgrade, the debug output is directed to syslog to be viewed later.

Troubleshooting File System agent upgrade

When you upgrade the File system agent from 19.3 to 19.4 or later version on either Windows or Linux, the required configuration files are copied from the 19.3 installation path to the new installation path for 19.4 or later. In some cases, these files are not copied successfully, which might cause the upgrade to fail. To troubleshoot this issue, complete the following steps.

Prerequisites

NOTE: These steps are required only when upgrading the File System agent from 19.3 or earlier to 19.4 or later.

Steps

1. Verify that the File System agent 19.3 installation path contains the following configuration files:

fsab.rec .app.settings agents.clb agents.clb.FCD If one or more of these files are not present in the File system agent 19.3 installation path, proceed to step 3.

2. If all the required files are present in the File system agent 19.3 installation path, manually copy the files to the installation path for 19.6:

Copy /dpsfsagent/settings/fsab.rec to /dpsapps/fsagent/ settings/fsab.rec

Copy /dpsfsagent/settings/.app.settings to /dpsapps/ fsagent/settings/.app.settings

Copy /dpsfsagent/lockbox/agents.clb to /dpsapps/fsagent/ lockbox/agents.clb

Copy /dpsfsagent/lockbox/agents.clb.FCD to /dpsapps/ fsagent/lockbox/agents.clb.FCD

where is the location of the File system agent installation.

3. If the required files are missing in the installation path for 19.3, perform the following steps to regenerate the files:

a. Set the lockbox in the PowerProtect Data Manager UI:

Go to Protection > Protection Policies. Select the protection policy for the client that is being upgraded, and click Set Lockbox.

b. Run the ddfsadmin sync command. Using the ddfsadmin utility for File Systems on page 49 provides more information.

Enabling the File System Agent 21

Uninstall the File System agent on Linux

On Linux, you can uninstall the File System agent by performing the following steps:

Steps

1. Obtain the uninstall.sh script from the folder extracted from the package fsagent196_linux_x86_64.tar.gz or under /opt/dpsapps/fsagent/bin.

2. Run ./uninstall.sh.

The following message appears:

Other application agents might be using powerprotect-agentsvc. Do you wish to uninstall powerprotect-agentsvc? [y/n]

3. Type Y to confirm that you want to uninstall powerprotect-agentsvc.

NOTE:

If you type N, the .rpm files (ppdm_bbbwt.rpm and ppdm_fsagent.rpm) and .deb files (ppdm-bbbwt.deb and

ppdm-fsagent.deb) are uninstalled. However, powerprotect-agentsvc remains in an installed state.

There is no silent uninstall procedure on Linux.

Installing and upgrading the File System agent on Windows Learn how to install and upgrade the File System agent on Windows.

Install the File System agent on Windows

Install the File System agent on supported Windows systems using an interactive or silent installation procedure.

Install the File System agent on Windows in interactive mode

Use this interactive procedure to Install the File System agent on supported Windows systems.

Prerequisites

Ensure that you carry out the prerequisites provided in File System agent prerequisites on page 15. Download the File System agent software package.

Steps

1. In the PowerProtect Data Manager UI:

a. Select Agent Downloads from the System Settings menu. b. Select the File System agent download package for Windows, fsagent196_win_x64.zip.

c. Download the package in the location that you want to install the File System agent.

2. Run the fsagent-19.6.0.0.exe program.

3. Follow the wizard installation steps to provide the installation location and the PowerProtect Data Manager server IP address.

NOTE: If another application agent is already installed on the client and registered to PowerProtect, ensure that you

register the agent with the existing PowerProtect Data Manager server IP. When you register the agent with a

PowerProtect Data Manager server that is different from the currently registered server, no warning message displays,

and requests are routed to the newer server instance.

4. Click Install.

22 Enabling the File System Agent

The following msi files are used for the installation:

AgentService.msiInstalls or upgrades the agent service component for File System agent.

BBBWT.msiInstalls the block based backups driver.

Fsagent.msiInstalls the File System agent related files and folders.

5. Click Finish.

NOTE: If a change occurred to the PowerProtect Data Manager server IP address, the installation completes

successfully but the client registration fails. To re-register the client to the correct IP address, use the Modify option

under Add/Remove programs for the File System agent, and then restart the PowerProtect service agent service on

the client.

Next steps

Windows installer logs are retained at \Users\ \AppData\Local\Temp, and should be consulted in the event of an installation failure.

If the host is not already whitelisted or approved, add the File System host to the PowerProtect Data Manager server. Manage the File System agent on page 32 provides more information.

Discover File System assets. Discover a File System host on page 35 provides more information.

NOTE: If you change the FQDN of the client at any point, use the Modify option under Add/Remove programs to update

the registration information for the File System agent, and then restart the agent service on the client to reregister the

client with the PowerProtect Data Manager server.

Install the File System agent on Windows in silent mode

On Windows, review the following commands to perform a silent installation of the File System agent.

NOTE: The File System agent installer for Windows does not support the --help option. Running the installer program

with --help initiates the actual installation process.

To perform the silent installation to the default path, run:

fsagent-19.6.0.0.exe /s PPDMHostName=

To perform the silent installation to a different path, run:

fsagent-19.6.0.0.exe /s PPDMHostName= ProductInstallPath="D:\alternate_path"

In silent File System agent installation (in the case of coexistence), use the ForceUpgrade=1 option to cause the silent upgrade of common components. If you do not add this option, the silent installation fails.

NOTE: PPDMHostName is a mandatory option in the command line. If a value is not provided, but the agent service

component has been installed by another agent, installation will succeed, but without PowerProtect, and hence it will not be

possible to initiate backups from the UI. If, however, the agent service component has not been installed by another agent,

then installation will fail. Specifying ProductInstallPath is optional, but if used, the value cannot be empty. When the

ProductInstallPath value is provided during upgrade or coexistence, but the install path is not the same as that of the

previously installed File System or already installed agents, installation fails.

Windows installer logs are retained at \Users\ \AppData\Local\Temp, and should be consulted in the event of an installation failure. In silent mode, any error message is logged only in the Windows installer logs.

Enabling the File System Agent 23

Upgrade the File System agent on Windows

The File System agent supports a direct upgrade from an earlier version if you are using an earlier version of PowerProtect Data Manager. You can upgrade the PowerProtect Data Manager File System agent on supported Windows systems in interactive or silent mode.

About this task

Upgrade and register the latest version of the PowerProtect Data Manager File System agent for Windows with the same PowerProtect Data Manager server in the same location.

NOTE: When you install or upgrade the File System agent, other app agents on the system must be upgraded to the same

version as the File System agent.

Upgrade the File System agent on Windows in interactive mode

Use this interactive procedure to upgrade the File System agent on supported Windows systems.

Prerequisites

Ensure that you carry out the prerequisites provided in File System agent prerequisites on page 15. Download the File System agent software package.

Steps

1. In the PowerProtect Data Manager UI:

a. Select Agent Downloads from the System Settings menu. b. Select the File System agent download package for Windows, fsagent196_win_x64.zip.

c. Download the package in the location that you want to install the File System agent.

NOTE: During upgrade, or fresh installation in case of coexistence, the File System agent will be installed on previous

install path of the File System agent, or the path of a previously installed Application agent.

2. Run the fsagent-19.6.0.0.exe program.

3. Follow the upgrade steps in the wizard to provide the installation location and the PowerProtect Data Manager server IP address.

NOTE: If another application agent is already installed on the client and registered to PowerProtect, ensure that you

register the agent with the existing PowerProtect Data Manager server IP. When you register the agent with a

PowerProtect Data Manager server that is different from the currently registered server, no warning message displays,

and requests are routed to the newer server instance.

4. Click Upgrade. The following msi files are used for the installation:

AgentService.msiInstalls or upgrades the agent service component for File System agent.

BBBWT.msiInstalls the block based backups driver.

Fsagent.msiInstalls the File System agent related files and folders.

5. Click Finish.

NOTE: If a change occurred to the FQDN of the client, the installation completes successfully but the registration fails.

To re-register the client to the correct FQDN, use the Modify option under Add/Remove programs for the File

System agent, and then restart the agent service on the client.

24 Enabling the File System Agent

Upgrade the File System agent on Windows in silent mode

Use the following commands to perform a silent upgrade of the File System agent on Windows.

To perform the silent upgrade to the default path, run:

fsagent-19.6.0.0.exe /s PPDMHostName= ForceUpgrade=1

To perform the silent upgrade to a different path, run:

fsagent-19.6.0.0.exe /s PPDMHostName= ForceUpgrade=1 ProductInstallPath="D:\alternate_path"

NOTE: PPDMHostName is a mandatory option in the command line. If a value is not provided, but the agent service

component has been installed by another agent, upgrade will succeed, but without PowerProtect registration, so that it will

not be possible to initiate backups from the UI. However, if the agent service component has not been installed by another

agent, then upgrade will fail. Specifying ProductInstallPath is optional, but if used, the value cannot be empty. When

the ProductInstallPath value is provided during upgrade or coexistence, but the install path is not the same as that of

the previously installed File System or already installed agents, installation fails.

For File System agent silent upgrade, or coexistence where common components are installed on host:

If common components are installed on the host, a File System agent upgrade requires the additional option ForceUpgrade=1.

All agents running on a client must be registered to the PowerProtect Data Manager server and must be upgraded to the same version.

PowerProtect Data Manager does not support agents running different versions on the same client. Setting ForceUpgrade=1 masks the prompt that requests users to upgrade any other agents installed on that client to the same version to which the File System agent is being upgraded.

Troubleshooting File System agent upgrade

When you upgrade the File system agent from 19.3 to 19.4 or later version on either Windows or Linux, the required configuration files are copied from the 19.3 installation path to the new installation path for 19.4 or later. In some cases, these files are not copied successfully, which might cause the upgrade to fail. To troubleshoot this issue, complete the following steps.

Prerequisites

NOTE: These steps are required only when upgrading the File System agent from 19.3 or earlier to 19.4 or later.

Steps

1. Verify that the File System agent 19.3 installation path contains the following configuration files:

fsab.rec .app.settings agents.clb agents.clb.FCD If one or more of these files are not present in the File system agent 19.3 installation path, proceed to step 3.

2. If all the required files are present in the File system agent 19.3 installation path, manually copy the files to the installation path for 19.6:

Copy /dpsfsagent/settings/fsab.rec to /dpsapps/fsagent/ settings/fsab.rec

Copy /dpsfsagent/settings/.app.settings to /dpsapps/ fsagent/settings/.app.settings

Copy /dpsfsagent/lockbox/agents.clb to /dpsapps/fsagent/ lockbox/agents.clb

Copy /dpsfsagent/lockbox/agents.clb.FCD to /dpsapps/ fsagent/lockbox/agents.clb.FCD

Enabling the File System Agent 25

where is the location of the File system agent installation.

3. If the required files are missing in the installation path for 19.3, perform the following steps to regenerate the files:

a. Set the lockbox in the PowerProtect Data Manager UI:

Go to Protection > Protection Policies. Select the protection policy for the client that is being upgraded, and click Set Lockbox.

b. Run the ddfsadmin sync command. Using the ddfsadmin utility for File Systems on page 49 provides more information.

Uninstall the File System agent on Windows

On Windows, you can uninstall the File System agent with the setup file.

Steps

1. Launch fsagent-19.6.0.0.exe.

2. On the Install Modification page, select Remove, and then click Next.

3. On the Configure Uninstallation Options page, select Yes for each common component that you want to uninstall, and then click Remove.

4. On the Complete the Setup page, click Finish.

Silent uninstallation commands

Steps

1. To perform a silent uninstall without uninstalling common components (such as the PowerProtect agent service or BBB), run:

fsagent-19.6.0.0.exe /s /uninstall

2. To perform a silent uninstall while also uninstalling common components, run:

fsagent-19.6.0.0.exe /s /uninstall UnInstallPPDMAgent="1" UnInstallBBBWT="1"

NOTE: If the File System agent is the last agent to be uninstalled, any common component that you do not uninstall

remains on the host. You cannot uninstall the common components from the control panel.

Manage the PowerProtect agent service The PowerProtect agent service provides important functionality for the application agent operations with the PowerProtect Data Manager.

Review the following topics to ensure that you enable and manage the PowerProtect agent service functionality as required for application agent operations.

About the PowerProtect agent service

The PowerProtect agent service is a REST API based service that is installed by the application agent on the application host. The agent service provides services and APIs for discovery, protection, restore, instant access, and other related operations. The PowerProtect Data Manager uses the agent service to provide integrated data protection for the application assets.

This section uses to represent the PowerProtect agent service installation directory. By default, the agent service installation location is C:\Program Files\DPSAPPS\AgentService on Windows and /opt/dpsapps/agentsvc on Linux. All files that are referenced in this section are the relative paths to the agent service installation location.

26 Enabling the File System Agent

The PowerProtect agent service performs the following operations:

Addon detectionAn addon integrates the application agent into the agent service. The agent service automatically detects the addons on the system for each application asset type and notifies the PowerProtect Data Manager. While multiple addons can operate with different asset types, only one agent service runs on the application host. Specific asset types can coexist on the same application host.

DiscoveryThe agent service discovers both stand-alone and clustered database servers (application systems), databases and file systems (assets), and their backup copies on the application agent host. After the initial discovery, when the agent service discovers any new application systems, assets, or copies, the agent service notifies the PowerProtect Data Manager.

Self-service configurationThe agent service can configure the application agent for self-service operations by using information that is provided by the PowerProtect Data Manager. When you add an asset to a protection policy for self- service or centralized protection, or modify the protection policy, including changing the DD Boost credentials, the PowerProtect Data Manager automatically pushes the protection configuration to the agents.

Centralized backupsThe agent service performs the centralized backups as requested by the PowerProtect Data Manager.

Centralized restoresThe agent service performs the centralized restores as requested by the PowerProtect Data Manager.

NOTE: In the current release, the centralized restores are only available for the File System agent and Storage Direct

agent.

Backup deletion and catalog cleanupThe PowerProtect Data Manager deletes the backup files directly from the protection storage when a backup expires or an explicit delete request is received. The PowerProtect Data Manager goes through the agent service to delete the catalog entries from the agent's local datastore.

NOTE: Deletion of any backup copies manually or through the command line is not recommended. PowerProtect Data

Manager deletes all the expired copies as needed.

The agent service is started during the agent installation by the installer. The agent service runs in the background as a service and you do not interact with it directly.

The config.yml file contains the configuration information for the agent service, including several parameter settings that you can change within the file. The config.yml file is located in the directory.

The agent service periodically starts subprocesses to perform the discovery jobs. You can see the type and frequency of these jobs in the jobs: section of the config.yml file. The job interval unit is minutes.

The agent service maintains a datastore in the /dbs/v1 directory, which contains information about the application system, assets, and backups discovered on the system. The size of the datastore files depends on the number of applications and copies on the host. The agent service periodically creates a backup of its datastore in the /dbs/v1/backups directory, as used to recover the datastore if this datastore is lost.

NOTE: The size of each datastore backup is the same as the datastore itself. By default, a backup is created every hour. To

save space on the file system, you can reduce this datastore backup frequency for large datastores. By default, the

datastore backup is retained for one week. You can change the datastore backup frequency, retention period, and backup

location in the config.yml file.

Start, stop, or obtain the status of the PowerProtect agent service

The PowerProtect agent service is started during the agent installation by the installer. If needed, you can use the appropriate procedure to start, stop, or obtain the status of the agent service.

On Linux, you can start, stop, or obtain the status of the agent service by running the register.sh script that is found in the directory.

To start the agent service:

# register.sh --start

Started agent service with PID - 1234

Alternatively, you can use the following command to start the agent service:

# service agentsvc start

Enabling the File System Agent 27

To stop the agent service:

# register.sh --stop

Successfully stopped agent-service.

Alternatively, you can use the following command to stop the agent service:

# service agentsvc stop To obtain the status when the agent service is running:

# register.sh --status

Agent-service is running with PID - 1234 To obtain the status when the agent service is not running:

# register.sh --status

Agent-service is not running. Alternatively, you can use the following command to obtain the status of the agent service when it is running or not running:

# service agentsvc status

Troubleshoot the PowerProtect agent service operations

To troubleshoot the agent service operations, you can check the agent service log file OpAgentSvc- .log, which is created in \logs on Windows and /logs on Linux. To modify the log level and retention of temporary files, you can modify specific parameter settings in the config.yml file.

About this task

To modify the log level and retention of temporary files, you can perform the following steps.

Steps

1. Stop the agent service by using the appropriate procedure from the preceding topic.

2. Open the config.yml file in an editor.

3. Modify the log-level settings in the following parameters, as required:

NOTE: These parameters are listed in order of decreasing number of messages in the debug information output. The

default log-level is INFO.

DEBUG INFO WARNING ERROR CRITICAL

4. To retain the temporary files, set the keepTempFiles parameter to True in the config.yml file.

NOTE: The agent service and application agent communicate through the temporary files, which are typically deleted

after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to True

permanently, or the temporary files can use excessive space on the file system.

5. Start the agent service by using the appropriate procedure from the preceding topic.

28 Enabling the File System Agent

Register the PowerProtect agent service to a different server address on Linux

The PowerProtect agent service is registered to a particular PowerProtect Data Manager server during the agent installation by the installer. If needed, you can register the agent service to a different PowerProtect Data Manager server address. If there are multiple agents installed on a host, all agents will be re-registered to the new PowerProtect server.

The agent service can only be registered to a single PowerProtect Data Manager server.

On Linux, perform the following steps to register the agent service to a different server address.

1. To unregister from the current PowerProtect Data Manager server, go to the /opt/dpsapps/agentsvc directory and run the unregister.sh script.

2. In the dbs/v1 directory, rename the copies.db file to copies-backup.db.

3. To register the agent service to the different server address, go to the /opt/dpsapps/agentsvc directory, run the register.sh script, and provide the PowerProtect Data Manager server IP address or hostname:

The following command prompts for the new IP address or hostname:

# register.sh

Enter the PowerProtect Data Manager IP address or hostname: 10.0.0.1

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234 The following command includes the new IP address on the command line:

# register.sh --ppdmServer=10.0.0.1

Warning: Changing IP of PowerProtect Server from 192.168.0.1 to 10.0.0.1

Started agent service with PID - 1234 4. Verify that the agentsvc process is started.

5. Verify the agent registration status:

a. In the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

b. In the Application Agents window, select the entry that contains the agent hostname and ensure that the status is Registered.

6. To perform asset discovery for the agent:

a. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources.

The Asset Sources window appears.

b. Select the App/File System Host tab. c. Select the agent hostname and click Discover. At the confirmation prompt, click Yes.

When you select Infrastructure > Assets, the Assets window displays the discovered assets.

Register the PowerProtect agent service to a different server address on Windows

The PowerProtect agent service is registered to a particular PowerProtect Data Manager server during the agent installation by the installer. If needed, you can register the agent service to a different PowerProtect Data Manager server address. If there are multiple agents installed on a host, all agents will be re-registered to the new PowerProtect server.

The agent service can only be registered to a single PowerProtect Data Manager server.

On Windows, perform the following steps to register the agent service to a different server address.

1. To unregister from the current PowerProtect Data Manager server, go to the C:\Program Files\DPSAPPS \AgentService directory and run unregister.bat.

2. In the dbs\v1 directory, rename the copies.db file to copies-backup.db.

Enabling the File System Agent 29

3. To register the agent service to the different server address, run register.bat and provide the new PowerProtect Data Manager server IP address or hostname.

4. Verify the agent registration status:

a. In the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

b. In the Application Agents window, select the entry that contains the agent hostname and ensure that the status is Registered.

5. To perform asset discovery for the agent:

a. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources.

The Asset Sources window appears.

b. Select the App/File System Host tab. c. Select the agent hostname and click Discover. At the confirmation prompt, click Yes.

When you select Infrastructure > Assets, the Assets window displays the discovered assets.

Recovering the PowerProtect agent service from a disaster

You can perform self-service restores of application assets by using a file system or application agent, regardless of the state of the agent service or PowerProtect Data Manager. The information in the this section describes how to bring the agent service to an operational state to continue if a disaster occurs and the agent service datastore is lost.

The agent service periodically creates a backup of its datastore in the /dbs/v1/backups repository. If all these backups are lost, the agent service can still start. The agent service discovers all the application systems, assets, and backup copies on the system again, and notifies PowerProtect Data Manager. Depending on when the failure occurred, the agent service might not be able to find older backup copies for some asset types. As a result, the centralized deletion operations might fail when cleaning up the database vendor catalog or removing older backups that are taken before the asset is added to PowerProtect Data Manager.

By default, the agent service backs up consistent copies of its datastore files to the local disk every hour and keeps the copies for 7 days. Each time the agent service backs up the contents of the datastore, it creates a subdirectory under the /dbs/v1/backups repository. The subdirectories are named after the time the operation occurred, in the format YYYY-MM-DD_HH-MM-SS_epochTime.

By default, the datastore repository is on the local disk. To ensure that the agent service datastore and its local backups are not lost, it is recommended that you back up the datastore through file system backups. You can also change the datastore backup location to a different location that is not local to the system. To change the datastore backup location, update the values in the config.yml file.

Restore the PowerProtect Data Manager agent service datastore

Prerequisites

NOTE: Ensure that the agent service is powered off. Do not start the agent service until disaster recovery is complete.

About this task

You can restore the datastore from the datastore backup repository. If the repository is no longer on the local disk, restore the datastore from file system backups first.

To restore the datastore from a backup in the datastore backup repository, complete the following steps:

Steps

1. Move the files in the /dbs/v1 directory to a location for safe keeping.

NOTE: Do not move or delete any /dbs/v1 subdirectories.

2. Select the most recent datastore backup.

The directories in the datastore backup repository are named after the time the backup was created.

30 Enabling the File System Agent

3. Copy the contents of the datastore backup directory to the /dbs/v1 directory. After the copy operation is complete, the /dbs/v1 directory should contain the following files:

copies.db objects.db resources.db sessions.db

4. Start the agent service.

Enabling the File System Agent 31

Managing Storage, Assets, and Protection

Topics:

Manage the File System agent Add protection storage Enable an asset source Discover a File System host Add a protection policy for File System protection Edit the retention period for backup copies Delete backup copies Exclusion filters Centralized and file-level restore of a File System host Troubleshooting File System agent backups

Manage the File System agent You can add a File System agent, approve and reject pending agent requests, and edit and delete existing agents.

About this task

NOTE: PowerProtect Data Manager supports the coexistence of the following agents on the same Windows or Linux host:

SQL agent and File System agent on Windows.

Exchange agent and File System agent on Windows.

Oracle RMAN agent and File System agent on Linux.

SAP HANA agent and File System agent on Linux.

Steps

1. Select Infrastructure > Application Agents.

2. In the Application Agents window, click Add.

3. In the Add Application/FS Agent window, select one of the following options:

Add FQDN

Perform the following steps:

a. Type the fully qualified domain name (FQDN) for the application agent. b. Specify the date until which the application agent is preapproved. c. Click Save.

CSV Filename

Perform the following steps:

a. Click the Choose File icon. NOTE: The contents of the .CSV file must be in the following format, for example:

"ppdm.dell.com" "ppdm2.emc.com" "ppdm.dellemc.com"

The Explorer window appears.

b. Select the .csv file, and then click Open.

3

32 Managing Storage, Assets, and Protection

The file displays in the Application/FS Agents window.

c. Select the date until which the application or File System agent is preapproved. d. Click Save.

4. The Auto Whitelist option is disabled by default. When Auto whitelist is enabled, all preapproved Application Agents are automatically approved.

If you leave the Auto whitelist option disabled, select an application agent, and then select one of the following options:

Approve Reject Edit Make the required changes. Remove

Add protection storage

About this task

The PowerProtect Data Manager UI enables users with administrator credentials to add the following storage types:

DD Management Center External DD system

NOTE: The most up-to-date software compatibility information for PowerProtect Data Manager is provided in the eLab

Navigator.

When a DD Management Center is added, PowerProtect Data Manager discovers all the supported DD systems that are managed by the DD Management Center. The PowerProtect Data Manager UI displays the discovered DD systems on the Protection Storage tab of the Infrastructure > Storage window. The DD systems that are managed by the DD Management Center are not displayed until discovery is complete. It might take a few minutes for the DD systems to appear in the Storage window.

For each DD system, the DD Management Center that manages the DD system is indicated in the Managed By column in the table.

If a DD system is added directly to PowerProtect Data Manager, the name that was provided for the DD system when it was added to the PowerProtect Data Manager system is displayed in the Managed By column.

NOTE: Data Domain is now PowerProtect DD. References to Data Domain or DD systems in this documentation, in the UI,

and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the UI has

not yet been updated to reflect this change.

Steps

1. Select Infrastructure > Storage.

The Storage window appears.

2. In the Protection Storage tab, click Add.

3. In the Add Storage dialog box, select a storage system (DD System, DD Management Center).

4. Specify the storage system attributes:

a. In the Name field, specify a storage name. b. In the Address field, specify the hostname, fully qualified domain name (FQDN), or the IP address. c. In the Port field, specify the port for SSL communication. Default is 3009.

5. Under Host Credentials click Add, if you have already configured DD credentials that are common across DD systems, select an existing password. Alternatively, you can add new credentials, and then click Save .

6. If a trusted certificate does not exist on the storage system, a dialog box appears requesting certificate approval. Click Verify to review the certificate, and then click Accept.

7. Click Save to exit the Add Storage dialog and initiate the discovery of the storage system.

A dialog box appears to indicate that the request to add storage has been initiated.

8. In the Storage window, click Discover to refresh the window with any newly discovered storage systems. When a discovery completes successfully, the Status column updates to OK.

9. To modify a storage system location, complete the following steps:

Managing Storage, Assets, and Protection 33

A storage system location is a label that is applied to a storage system. If you want to store your copies in a specific location, the label helps you select the correct storage system during policy creation.

a. In the Storage window, select the storage system from the table. b. Click Set Location.

The Set Location window appears. c. Click Add in the Location list.

The Add Location window appears. d. In the Name field, type a location name for the asset, and click Save.

10. To manage MTrees in the Storage window, select the storage system from the table and click View storage units.

Results

PowerProtect Data Manager displays External DD systems only in the Storage window Name column. PowerProtect Data Manager displays DD Management Center storage types in the Managed By column.

Troubleshooting protection policy for DD storage unit

When adding a protection policy in PowerProtect Data Manager, creation of a storage unit on the selected DD system fails if you reach the maximum MTree and Users count on the DD system. PowerProtect Data Manager enables you to finish adding the protection policy without the storage unit. However, if you subsequently run a backup of this protection policy, the backup process is suspended indefinitely with no error message.

To continue backup operations on this device, you must perform a cleanup on the DD system.

Viewing the DD Boost storage unit password

PowerProtect Data Manager provides a script to retrieve the password of a DD Boost unit that is configured as a backup target.

Prerequisites

This process requires the name of the DD MTree where the DD Boost storage unit resides.

Steps

1. SSH to the PowerProtect Data Manager appliance as the admin user.

2. Navigate to the /usr/local/brs/puppet/scripts directory.

3. Obtain the DD Boost storage unit password by typing the following command:

./get_dd_mtree_credential.py PLC-PROTECTION-1551667983302

Enable an asset source An asset source, such as a vCenter Server, must be enabled in PowerProtect Data Manager before you can add and register the asset source for the protection of assets.

About this task

There are some circumstances where enabling an asset source is not required, such as the following:

For application agents and other agents such as File System and Storage Direct, an asset source is enabled automatically when you register and approve the agent host. For example, if you have not enabled an Oracle asset source but have registered the application host though the API or the PowerProtect Data Manager UI, PowerProtect Data Manager automatically enables the Oracle asset source.

When you upgrade to PowerProtect Data Manager 19.6 from an earlier release, any asset sources that were previously enabled appear in the PowerProtect Data Manager UI. On a new installation, however, no asset sources are enabled by default.

34 Managing Storage, Assets, and Protection

Steps

1. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then click + to reveal the New Asset Source tab.

2. In the pane for the asset source that you want to add, click Enable Source. The Asset Sources window updates to display a tab for the new asset source.

Results

You can now add or approve the asset source for use in PowerProtect Data Manager. For a vCenter Server, Kubernetes cluster, or SMIS Server, select the appropriate tab in this window and click Add. For an application agent, go to Infrastructure > Application Agents and click Add or Approve as required.

Disable an asset source

If you enabled an asset source that you no longer require, and the host has not been registered in PowerProtect Data Manager, perform the following steps to disable the asset source.

About this task

NOTE: An asset source cannot be disabled when one or more sources are still registered or there are backup copies of the

source assets. For example, if you registered a vCenter Server and created policy backups for the vCenter virtual machines,

then you cannot disable the vCenter asset source. But if you register a vCenter Server and then delete the vCenter without

creating any backups, you can disable the asset source.

Steps

1. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab of the asset source that you want to disable. If no host registration is detected, a red Disable button appears.

2. Click Disable.

Results

PowerProtect Data Manager removes the tab for this asset source.

Discover a File System host Perform the following steps to discover a File System host as an asset source in the PowerProtect Data Manager UI.

Steps

1. Select Infrastructure > Asset Sources.

The Asset Sources window appears.

2. Select the App/File System Host tab.

3. Select the file system host and click Discover.

The Discover dialog appears with an option to set the discovery schedule.

4. From the Discovery Schedule list, select the time of day to initiate the discovery, or select Manual to disable scheduled discovery. You can also select the Discover Now checkbox to perform the discovery upon completion of this procedure.

NOTE: From the App/File System Host tab, you can click Discover at any time if any additions or other changes to

your asset sources have taken place outside of the PowerProtect Data Manager environment. Asset discovery is also

initiated by default after registration of the host to PowerProtect Data Manager and at hourly intervals. Discovery time

is based on networking bandwidth. Note that each time you initiate a discovery process, the resources that are

discovered and those that are handling the discovery impact system performance.

5. Click Save.

Managing Storage, Assets, and Protection 35

Results

When the File System is configured correctly, it can be added to a PowerProtect Data Manager protection policy.

Add a protection policy for File System protection Use the PowerProtect Data Manager UI to add a protection policy to protect File System data.

Prerequisites

Review the prerequisites in the section File System agent prerequisites on page 15.

If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection policy. The PowerProtect Data Manager Administration and User Guide provides more information.

Steps

1. Select Protection > Protection Policies.

The Protection Policy window appears.

2. Click Add.

The Add Policy window appears.

3. In the Type page, specify the new protection policies group fields. For example, if you are creating a protection policy for daily backups in the Windows 2012 Server:

a. In the Name field, specify the name of the protection policy. For example, File System Prod.

NOTE: The name that you specify here becomes part of the DD MTree entry.

b. In the Description field, specify a short description of the protection policy. For example, File System Prod Daily Backups

c. In theType field, select File System. d. Click Next.

The Purpose page appears.

4. In the Purpose page, specify the following fields to indicate the purpose of the new protection policy:

a. The type of protection policies group.

For File System, you can select from three types:

To use PowerProtect Data Manager to manage all protection centrally, click Centralized Protection. To use the File System to create local backup protection, click Self-Service Protection. PowerProtect Data

Manager creates a protection policy and manages extra stages. If there are assets within the protection policy that you plan to exclude from data protection operations, click

Exclusion.

b. Click Next. The Assets page appears.

5. Select the unprotected assets that you want to add to the backup of this protection policy group. The window enables you to filter by asset name to locate the required assets.

Also, you can change the assets view to display all assets discovered by PowerProtect Data Manager, or a hierarchical view to display the assets in a tree structure underneath the application host. A hierarchical view might be helpful, for example, if you have added multiple File Systems, so that you can more easily identify which assets belong to which host.

NOTE: PowerProtect Data Manager does not support including CSV and non-CSV volumes in the same protection

policy.

6. Click Next.

If you selected Exclusion in the Purpose page, the Summary page appears. Skip to step 20 on page 38. If you selected Centralized Protection, the File Exclusions page appears. To enable exclusions, click Enable.

a. Select one or more filters to apply, provide the parameters, and click Add Filter.

Click Add a saved filter to use an existing filter or group of filters as a template.

NOTE: Add an exclusion filter on page 41 provides more details about exclusion filters.

36 Managing Storage, Assets, and Protection

b. Enter a name and description for the filter and click Save. If you selected Self-Service Protection, the Schedule page appears.

7. Click + Backup. The Add Primary Backup dialog box appears.

8. Specify the backup schedule fields:

For Centralized Protection:

a. In the Recurrence field, select the interval at which the backup job runs within the window that you specify.

Recurrence relates to Start Time and End Time fields.

When you select Hourly, Daily,Weekly, and Monthly recurrence, you are selecting the interval at which the backup job runs within the window that you specify.

b. Create CopySpecify how often to create a synthetic full backup. A synthetic full backs up only the changed data since the last backup to create a new, full backup.

c. To create a log, click Log, and then specify the interval in minutes. d. In the Keep For field, specify the retention time.

You can extend the retention period for the latest primary backup copy by adding a promotion backup. For example, your regular schedule for daily backups can use a retention period of 30 days, but you can apply promotion backups to keep the full backups taken on Mondays for 10 weeks. Step 9 on page 37 provides instructions.

e. In the Start Time field, specify the time when new backups will be initiated in this policy. f. In the End Time field, specify the time after which no new backup will be initiated in this policy. It does not mean that

any policy that is running is stopped at this time. g. Create FullSelect this option if you want to periodically force a full (level 0) backup, and then specify how often to

create these backups. By default, if you do not select this option, all subsequent backups are incremental backups. NOTE:

It is not mandatory to create periodic full backups. When you select this option, the File System agent creates full

backups as per the schedule selected for these backups. A full backup ensures protection from potential

corruption that can be carried over from previous backups. However, these backups require more time and

resources.

If you do not select this option, the File System agent identifies changes since the last full backup and uses the

previous backup copy to create a new full backup.

h. Click OK.

The Schedule page updates with the newly added backup schedule.

For Self-Service Protection:

a. In the Keep For field, specify the retention time.

You can extend the retention period for the latest primary backup copy. For example, you can keep the daily scheduled backups for 30 days, but keep the full backups taken on Sundays for 90 days. Step 9 on page 37 provides instructions.

b. Click OK.

After completing a backup schedule, you can change any schedule details by selecting the checkbox next to the added schedule and clicking Edit.

9. To extend the retention period for the latest primary backup copy, add a promotion backup:

a. Select the checkbox next to the added schedule and click + Backup. b. In the Add Promotion Backup dialog box, specify a weekly or monthly recurrence for the promotion backup schedule, a

retention period for the backup, and then click OK.

10. To replicate these backups to a remote DD system:

a. Select the checkbox next to the added schedule and click Replicate.

NOTE: You cannot replicate a promotion backup. When you select a promotion backup schedule, the Replicate

button is disabled.

b. Complete the schedule details in the Add Primary Replication dialog box, and then click OK.

NOTE: To enable replication, ensure that you add a remote DD system as the replication location.

Managing Storage, Assets, and Protection 37

11. Select the check box next to the added schedule. When you select the check box, the SLA, Storage Name, and Network interface lists are enabled for selection.

12. From the SLA list, select an existing service level agreement that you want to apply to this schedule, or select Add to create a SLA within the Add Backup Service Level Agreement window.

13. From the Storage Name list:

Select the backup destination from the list of existing DD systems. To add a system, select Add, and complete the details in the Storage Target window.

When you select the destination storage, the Space field updates with the available capacity on the system.

14. From the Network interface list, select a network interface, if applicable.

15. Click Set Storage Quotas to set storage space restrictions for a DD MTree or Storage Unit to prevent the consumption of excess space. There are two kinds of quota limitshard limits and soft limits. You can set either a soft or hard limit or both a soft and hard limit. Both values must be integers, and the soft value must be less than the hard value.

NOTE: When you set a soft limit and the limit is reached, an alert is generated but data can still be written to the DD

system. When you set a hard limit and the limit is reached, data cannot be written to the MTree. All data protection

operations fail until data is deleted from the MTree. The DD Operating System Administration Guide provides more

information about MTree quota configuration.

a. Capacity QuotaControls the total size of precompression data that is written to the DD system. b. Stream QuotaThe number of concurrent streams allowed on the system during data protection operations. Setting a

Stream Quota limit can help ensure that system performance is not impacted negatively if a data protection operation is consuming too many system resources.

16. Select the Retention Lock check box to enable retention locking for these backups on the selected system. PowerProtect Data Manager uses Governance mode for retention locking, which means that the lock can be reverted at any time if necessary.

17. Click Next. The Options page appears.

18. On the Options page, select the additional option if required for the policy:

TroubleshootingSelect this option to enable the debug logs for troubleshooting purposes.

19. Click Next. The Summary page appears.

20. Review the protection policy group configuration details. You can click Edit next to any completed window's details to change any information. When completed, click Finish. An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy.

When the new protection policy is created and assets are added to the protection policy, PowerProtect Data Manager performs backups according to the backup schedule.

21. Click OK to exit the window, or click Go to Jobs to open the Jobs window to monitor the backup of the new protection policy group.

Edit the retention period for backup copies You can edit the retention period of one or more backup copies to extend or shorten the amount of time that backups are retained.

About this task

You can edit the retention period for all asset types and backup types.

Steps

1. Select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to edit the retention period. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

38 Managing Storage, Assets, and Protection

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies from the table, and click Edit Retention.

6. Select one of the following options:

To select a calendar date as the expiration date for backups, select Retention Date. To define a fixed retention period in days, weeks, months, or years after the backup is performed, select Retention

Value. For example, you can specify that backups expire after 6 months.

NOTE: When you edit the retention period for copies that are retention locked, you can only extend the retention

period.

7. When satisfied with the changes, click Save. The asset is displayed in the list with the changes. The Retention column displays both the original and new retention periods, and indicates whether the retention period has been extended or shortened.

Delete backup copies In addition to deleting backups upon expiration of the retention period, PowerProtect Data Manager enables you to manually delete backup copies from the DD system.

About this task

If you no longer require a backup copy and the retention lock is not enabled, you can delete backup copies prior to their expiration date.

Starting with PowerProtect Data Manager version 19.6, you can perform a backup copy deletion that deletes only a specified part of a backup copy chain, without impacting the ability to restore other backup copies in the chain. When you select a specific backup copy for deletion, only that backup copy and the backup copies that depend on the selected backup copy are deleted. For example, when you select to delete a full backup copy, any other backup copies that depend on the full backup copy are also deleted.

Steps

1. Select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more copies from the table that you want to delete from the DD system, and then click Delete.

A preview window opens and displays the selected backup copies.

6. For all asset types, you can choose to keep the latest backup copies or delete them. By default, PowerProtect Data Manager keeps the latest backup copies. To delete the latest backup copies, clear the checkbox next to Include latest copies.

7. To delete the backup copies, in the preview window, click Delete.

NOTE: The delete operation may take a few minutes and cannot be undone.

An informational dialog box opens to confirm the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

When the job completes, the task summary provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC.

An audit log is also generated and provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC. Go to Alerts > Audit Logs to view the audit log.

8. Verify that the copies are deleted successfully from the DD system. If the deletion is successful, the deleted copies no longer appear in the table.

Managing Storage, Assets, and Protection 39

Retry a failed backup copy deletion

If a backup copy is not deleted successfully, you can manually retry the operation.

Steps

1. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

2. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

3. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

4. Select one or more backup copies with the Deletion Failed status from the table, and then click Delete.

You can also filter and sort the list of backup copies by status in the Copy Status column.

The system displays a warning to confirm you want to delete the selected backup copies.

5. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

6. Verify that the copies are successfully deleted from the DD system. If the deletion is successful, the deleted copies no longer appear in the table.

Export data for deleted backup copies

This option enables you to export results of deleted backup copies to a CSV file so that you can download an Excel file of the data.

Steps

1. From the Assets window, select the tab for the asset type for which you want to export results of deleted backup copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

2. Select one or more protected assets from the table and click Export Deleted Copies.

If you do not select an asset, PowerProtect Data Manager exports the data for deleted backup copies for all assets for the specific asset type.

3. Specify the following fields for the export:

a. Time Range

The default is Last 24 Hours.

b. Copy Status

In order to export data for deleted backup copies, the backup copies must be in one of the following states:

Deleted Deleting Deletion Failed Deletion Failed (Agent Catalog)

NOTE: You cannot export data for backup copies that are in an Available state.

4. Click Download. If applicable, the navigation window appears for you to select the location to save the CSV file.

5. Save the CSV file in the desired location and click Save.

40 Managing Storage, Assets, and Protection

Remove backup copies from the PowerProtect Data Manager database

This option enables you to delete the backup copy records from the PowerProtect Data Manager database, but keep the backup copies in the DD system.

About this task

For backup copies that could not be deleted from the DD system, you can remove the backup copies from the PowerProtect Data Manager database. Removing the backup copies from PowerProtect Data Manager does not delete the copies in the DD system.

Steps

1. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

2. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

3. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

4. Select one or more backup copies with the Deletion Failed or Deletion Failed (Agent Catalog) status from the table, and then click Remove from PowerProtect.

For backup copies with the Deletion Failed (Agent Catalog) status, click Remove from PowerProtect to remove the information from PowerProtect Data Manager for any backup copies that were successfully deleted from the DD system but for which the agent catalog was not deleted from the agent host.

The system displays a warning to confirm you want to delete the selected backup copies.

5. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

6. Verify that the copies are deleted from the PowerProtect Data Manager database. If the deletion is successful, the deleted copies no longer appear in the table. The backup copies remain in the DD system.

Exclusion filters Exclusion filters enable you to exclude certain files and folders from protection, based on the filter's conditions (conditions for exclusion).

Use the PowerProtect Data Manager UI to add, edit, and delete exclusion filters for file system files and folders.

When you create or edit a protection policy, you can apply exclusion filters to the protection policy.

When an exclusion filter is applied to a protection policy, the File System Agent performs file-based backups of the protected assets. File-based backups traverse through the entire directory structure of the file system to back up all the files in each directory of the file system. While file-based backups can provide additional capabilities such as exclusion, these backups take longer to complete when compared to block based backups.

NOTE: Exclusion filters cannot be applied to self-service protection policies and to backups taken through self-service CLI.

Add an exclusion filter

Use the PowerProtect Data Manager UI to add filters that exclude specific files and folders based on certain conditions, such as file type, file size, modification time, and file path. When a file or folder meets the conditions, the filter excludes the data from the backup for the protection policy.

About this task

Use this procedure to add up to four filters for a file.

Managing Storage, Assets, and Protection 41

Steps

1. Select Protection > File Exclusion.

The File Exclusion window appears.

2. Click ADD. The Filter Information window appears.

3. In the Filter Name field, type a name for the filter.

4. In the Description field, describe the purpose of the filter.

5. Select a filtering condition. You can add multiple filters.

The filter excludes all files and folders that match these criteria from the backup for the protection policy. When you add multiple conditions, a file is excluded only if it meets all filter conditions. Within a filter, you can add a condition only once.

Available filtering conditions:

File Size Exclude files and folders that are larger or smaller than a specified size. Specify a value in either the Greater than or Less than field.

File type Exclude files or folders based on file type. Specify a file name extension or multiple file name extensions that are separated by commas.

Modified time Exclude files or folders that were modified before or after a certain date. Specify a date in either the After or Before field.

Folder Path Exclude files and folders in a specific path. Specify the file path, and then enclose the file path in quotations.

You can specify an absolute or relative path.

6. When you are finished building the filter, click Add Filters. The new filter appears in the table.

7. You can add up to four filters using the previous steps. When you are finished, click Next.

8. In the Summary confirmation page, verify the filter information and click Finish.

Guidelines for exclusion filters

Review the following guidelines for exclusion filters.

Using wildcards

Supported wildcards include an asterisk (*) to represent zero or more characters and a question mark (?) to represent zero or one character.

NOTE: Be careful when using the wildcard *. Depending on the wildcard location, you can match folders whose name

matches the filter pattern and their contents, even when the names of those files do not match the filter. For example, *\ \log*.txt also excludes files with the .txt extension in a folder whose name starts with log, even if the names of the

files do not start with log

Excluding by file type

The File Type filter enables you to exclude files and folders based on file extension.

You can specify a single extension or multiple file extensions. Separate multiple entries with a comma and do not add a space between entries. You can also specify related extensions by using wildcards. For example, *.doc? matches both .doc files and .docx files.

Excluding by type and path

You can combine extension and path to exclude all files of a particular type without respect to the file location.

For example *\\log*.txt matches all text files (.txt) where the file name starts with log, at any path.

42 Managing Storage, Assets, and Protection

You can also exclude all files of a particular type from a specific path. For example, C:\\abc\\*.txt matches all text files in the folder C:\abc. All matching files under subfolders of that specific path are recursively excluded.

You can combine these guidelines to exclude all files that match a specific name pattern under a particular path. For example, C:\\folder\\log*.txt.

Excluding by file path

The Path filter enables you to exclude files and folders in a specific path.

You can specify an absolute or relative path.

The following table provides examples for excluding files and folders using absolute and relative paths.

Table 5. Absolute and relative path examples

Type of path Folder File

Absolute F:\\folder1\\folder2\\* F:\\folder1\\folder2\\sample.txt In this example, the filter excludes all files and folders under F:\folder1\folder2.

In this example, the filter excludes the sample.txt file under F:\folder1\folder2.

Relative *\\folder1\\folder2\\* *\\folder1\\folder2\\sample.log In this example, the filter excludes all files and folders under any volume with the hierarchy folder1\folder2.

In this example, the filter excludes all sample.log files under any volume with the hierarchy folder1\folder2.

D:\\*\\folder1\folder2\\* D:\\*\\folder1\folder2\\sample.log In this example, the filter excludes all files and folders under any folder in D: with the hierarchy folder1\folder2.

In this example, the filter excludes all sample.log files under any folder in D: with the hierarchy folder1\folder2.

Cloud deployment considerations when using exclusion filters

The use of exclusion filters on PowerProtect Data Manager cloud deployments might result in heavy consumption of metadata.

Edit or delete an exclusion filter

Use the PowerProtect Data Manager to edit or delete an exclusion filter. You can change the filter name, description, logical operator, and the filtering conditions.

Steps

1. Select Protection > Filters.

The Exclusion Filters window appears, which displays the following information:

Name Description Conditions Logical Operator

2. To edit a filter, complete the following tasks:

a. Select a filter, and click Edit. The Edit Exclusion Filter wizard appears.

b. Modify the desired fields, and then click Next. The Summary page appears.

c. Click Finish to save your changes.

3. To delete a filter, select the filter that you want to delete, and then click Delete.

Managing Storage, Assets, and Protection 43

Apply an exclusion filter to a protection policy

When adding or editing a protection policy, you can apply a predefined exclusion filter to the protection policy. The File Exclusions page of the Add Policy or Edit Policy wizard enables you to select an exclusion filter and apply it to a protection policy.

Prerequisites

An exclusion filter must already exist.

About this task

To create a protection policy for file system protection and apply an exclusion filter to it, follow the steps in Add a protection policy for File System protection on page 36.

To apply an exclusion filter to an existing protection policy, complete the following steps:

Steps

1. Select Protection > Protection Policies.

The Protection Policy window appears.

2. Select a protection policy from the list, and then click Edit.

The Summary page appears.

3. Click File Exclusions > Edit. The File Exculsions page appears.

4. Toggle the Disabled switch to enable exclusion.

5. Add a saved filter or build a new filter according to the steps provided in Add an exclusion filter on page 41.

6. Click Next twice, review the details on the Summary page, and click Finish. PowerProtect Data Manager applies the exclusion filter to the protection policy.

Results

After the backup starts, you can view details about the files that are excluded from the protection policy. To view the excluded files:

Open the Jobs window and select the job. Click the Details icon to the left of the job name. In the Task Summary section, click the link that indicates the total number of tasks. Click the Details icon to the left of the task, and then review the protection policy details and excluded files.

Remove an exclusion filter from a protection policy

The File Exclusions page of the Edit Policy wizard enables you to remove an exclusion filter from a protection policy.

Steps

1. Select Protection > Protection Policies.

The Protection Policy window appears.

2. Select a protection policy from the list, and then click Edit.

The Summary page appears.

3. Select File Exclusions > Edit.

4. Clear the check box next to the filter that you want to remove from the protection policy.

5. Click Next.

The Summary page appears.

6. Review the details, and click Finish.

44 Managing Storage, Assets, and Protection

Centralized and file-level restore of a File System host When File Systems are protected within a protection policy in PowerProtect Data Manager, you can recover the File System data using the centralized restore and file-level restore functionality in the PowerProtect Data Manager UI.

Prerequisites for File System restores

Review the following requirements before performing centralized and file-level restores of File Systems:

Both the PowerProtect Data Manager server and client must be at a minimum version of PowerProtect Data Manager 19.3. Ensure that the target or destination volume is not a system volume. Ensure that the File System agent is not installed and running on the target volume. Ensure that there is sufficient space on the target volume for the restore. Ensure that the target or destination volume is not read-only. Cross-platform support for centralized file-level restore is not supported. For example, you cannot recover a Windows

backup on a Linux platform and the opposite way. Review the section Supported platform and OS versions for File System file-level restore on page 47.

Increasing the restore timeout

By default, the mount operation times out after 30 minutes and the backup copy is unmounted. When restoring large files, you can increase the restore timeout. Perform this task if restores for large files timeout before completing.

1. Create a file with the name browsersvc.cmd in one of the following locations:

On Windows, C:\Program Files\DPSAPPS\fsagent\settings On Linux, /opt/dpsapps/fsagent/settings

2. Add the following line to the file, and specify the timeout value. For example:

{ "-resexpiry":"timeout" } where timeout represents 2 minutes.

Centralized restore of File Systems

A File System host image-level restore enables you to recover data from backups of file systems performed in the PowerProtect Data Manager UI.

Prerequisites

Ensure the following for Linux File System hosts:

You have disabled Security-Enhanced Linux (SELinux) by running one of the following relevant commands:

RHEL 7.x or CentOS7.x: setsebool -P nis_enabled 1 RHEL 6.x or CentOS 6.x: setsebool -P allow_ypbind 1 You can also disable SELinux permanently:

1. Open the /etc/sysconfig/selinux file in a text editor.

2. Change the value of SELinux=enforcing from enforcing to disabled.

3. Restart the host machine. 4. Verify the SELinux status by running the getenforce command.

You have installed the iscsiadm utility by installing one of the following relevant packages on the Linux client:

RHEL or CentOS: iscsi-initiator-utils .rpm SLES: open-iscsi .rpm

On SLES, if you want to start the iscsiadm utility for the first time, restart the iSCSI services by running the following command: service open-iscsi restart

Managing Storage, Assets, and Protection 45

On Linux, before performing an image-level restore of the block based backup copy, ensure that you are not logged in to the destination file system asset (volume) for other data protection operations. If you are logged in to the destination asset (volume) for any other data protection operation, the restore fails.

Steps

1. In the PowerProtect Data Manager UI, select Recovery > Assets and select the File System tab.

The Recovery window displays all of the file systems available for recovery.

2. Select the checkbox next to the desired file system and click View Copies.

You can also use the Search field, the filter in the Name column to search on specific criteria to locate a specific file system.

The Recovery > Assets window provides a map view in the left pane and copy details in the right pane.

When a file system is selected in the map view, the file system name displays in the right pane with the copy locations underneath. When you select a specific location in the left pane to view the copies, for example, on a DD system, the copies on that system display in the right pane.

3. Click DD, and then select from one of the available copies that display in the table.

4. In the right pane, select the checkbox next to the file system backup you want to restore, and then click Restore. The Restore wizard appears.

5. On the Select Target Location page, choose from one of the following options, and then click Next.

Restore to originalRestore the file system to the original location. Restore to a new location on the original hostSelect the destination file system asset (volume) from the list of available

assets on the host. Restore to a new hostBrowse from the available hosts to locate and select a destination host and file system.

NOTE: If the destination file system asset already contains some data, this data will be overwritten.

6. On the Summary page:

a. Review the information to ensure that the restore details are correct. b. Click Restore.

7. Go to the Jobs window to monitor the restore. A restore job appears with a progress bar and start time.

File-level restore from File System backups

A file-level restore enables the administrator to recover individual files from backups of File Systems that were created in PowerProtect Data Manager.

Prerequisites

Review the section Supported platform and OS versions for File System file-level restore on page 47 for supported platform and operating system versions.

PowerProtect Data Manager supports file-level restore only if the backup or replica is on a DD system device.

Steps

1. In the PowerProtect Data Manager UI, go to Recovery > Assets and select the File Systems tab.

The Recovery window displays the file systems that are available for recovery.

2. Select the check box next to the file system and click View Copies.

You can also use the filter in the Name column to search for the name of the specific file system or click the File Search button to search on specific criteria.

The Recovery > Assets window provides a map view in the left pane and copy details in the right pane.

When a file system is selected in the map view, the file system name appears in the right pane with the copy locations underneath. When you select a specific location in the left pane to view the copies, for example, on a DD system, the copies on that system appear in the right pane.

3. If the backup is on a DD system, click DD, and then select from one of the available copies that display in the table.

46 Managing Storage, Assets, and Protection

4. In the right pane, select the check box next to the file system backup you want to restore, and then click File Level Restore. The File level restore wizard appears.

5. On the Select target host and mount page, choose from one of the following options, and then click Mount.

Restore to same or original machine. Restore to alternate host.

6. When the mount is complete, click Next. The Select folder and files to recover page appears.

7. On the Select folder and files to recover page:

a. Expand individual folders to browse the original file system backup, and select the objects that you want to restore to the destination file system.

You can also use the filter in the Name column to search for the name of the specific object.

b. Click Next. The Select restore location page appears.

8. On the Select restore location page:

a. Select the destination drive. Alternatively, choose the Overwrite files in restore location option, in which case existing files on the destination drive will be overwritten.

b. Browse the folder structure of the destination file system to select the folder where you want to restore the objects. c. Click Next.

9. On the Summary page:

a. Review the information to ensure that the restore details are correct. b. Click Finish.

10. Go to the Jobs window to monitor the restore. A restore job appears with a progress bar and start time.

Supported platform and OS versions for File System file-level restore

File system file-level restore is only supported for the following platforms and operating system versions.

NOTE: Platforms/operating systems are qualified for file-level restore support using the default File System for these

platforms:

RedHat Enterprise Linux version 6.x, 7.x up to 7.7, and 8.x SuSE Linux Enterprise Server versions 11 SP1, 11 SP 2, 11 SP3, 11 SP4, 12, 12 SP1, 12 SP2, 12 SP3, 12 SP4, and 15 SP1 CentOS versions 6.x, 7.x up to 7.6 Windows 2012, 2012 R2, 2016, and 2019 for NTFS and ReFS

Linux platforms require an ext3, ext4, or XFS file system type.

NOTE: The most up-to-date software compatibility information for PowerProtect Data Manager is provided in the eLab

Navigator, available at https://elabnavigator.emc.com/eln/modernHomeDataProtection.

Troubleshooting File System agent backups

Issue

On Linux, the block based incremental backups consistently fail and display a message similar to save: Block Based Error subsystem error while performing Block Based Backup.

Workaround

Check if any other process is already accessing the snapshot, or delete the snapshot manually, and then try again.

Managing Storage, Assets, and Protection 47

Self-Service Backup and Restore of the File System Agent

Topics:

Performing self-service backups of File Systems Performing self-service restore of a File System host

Performing self-service backups of File Systems A host with the File System Agent installed requires a PowerProtect Data Manager server to back up file systems. However, an administrator can configure a retention policy only instead of a complete backup.

To back up file systems manually and use PowerProtect Data Manager for compliance purposes, register the host to PowerProtect Data Manager, create a self-service protection policy, and configure only the retention policy.

NOTE: To enable self-service protection, select Self-Service Protection when you create the File Systems protection

policy in the PowerProtect Data Manager UI.

After a host is registered with PowerProtect Data Manager and assets are added to a self-service protection policy, use the ddfssv command to run self-service or manual backups on the host file system assets, as in the following example:

ddfssv -LL -l FULL -a DFA_SI_DD_HOST=IPv4 address -a DFA_SI_DD_USER=username (for example, PLC-Protection) -a DFA_SI_DEVICE_PATH=device path (for example, /PLCProtection/LVMs/2)) where:

-l {full | incr}

Specifies the type of the backup to perform such as full (full), or incremental (incr). The default value is full.

-a "DFA_SI_DD_HOST= "

Specifies the name of the DD server that contains the storage unit where you want to back up the databases.

-a "DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit where you want to direct the backup.

-a "DFA_SI_DD_USER= "

Specifies the protection storage username.

You must register the hostname and the protection storage username in the lockbox to enable the Microsoft application agent to retrieve the password for the registered user.

These details are provided in the .app.settings file on both Linux and Windows hosts. If the default installation path was used, the .app.settings file is at /opt/dpsapps/fsagent/settings on a Linux host and C:\Program Files \DPSAPPS\fsagent\settings on a Windows host. More information about how to use the admin utility to query the list of backups for an asset, see Using the ddfsadmin utility for File Systems on page 49.

NOTE: This command uses only the retention period that was specified when the self-service protection policy was

created.

To perform a self-service backup, use the storage unit and username that was created on the DD system when the policy was created. PowerProtect Data Manager discovers these backups and enables centralized restore operations. You can also perform a manual restore operation.

4

48 Self-Service Backup and Restore of the File System Agent

Performing self-service restore of a File System host When File Systems are protected within a protection policy in PowerProtect Data Manager, you can recover the File System data using the centralized PowerProtect Data Manager restore functionality, or directly using the self-service restore feature. The following section describes the procedure for self-service restore of File Systems.

Prerequisites for File System restores

Before performing centralized or self-service File System restores:

Ensure that the target or destination volume is not a system volume. Ensure that the File System agent is not installed and running on the target volume. Ensure that there is sufficient space on the target volume for the restore.

Using the ddfsadmin utility for File Systems

The ddfsadmin utility provides the following command line options for File System recovery.

ddfsadmin backup query

Before running the ddfsrc command to perform a self-service image-level restore of File Systems, you can use the ddfsadmin backup command to query a list of all the local and remote backups taken for a particular host, as shown in the following:

ddfsadmin backup query -local -v=volume name -t=time value [h = hour,d = days,w = weeks,m = months] queries the local record file for listing backups.

ddfsadmin backup query -remote -d=Protection storage system -s=storage unit -u=username - p=DD password -c=hostname -v=volume name -t=time value [h = hour,d = days,w = weeks,m = months] queries the record file on the protection storage system for listing backups.

Example usage

ddfsadmin backup query -local -v="C:\\" -t=5 will display a list of local backups in C:\ taken within the last five days.

ddfsadmin sync

The following is the usage for the ddfsadmin sync command:

sync -local options: Sync local record file with record file on DD sync -remote options: Sync remote record file with file in the local options: -d=

: Protection storage system host IP -u=
: Protection storage system username -s=
: Protection storage system device path -p=
: Protection storage system password.[Optional]

Example usage

ddfsadmin sync -local -d x.x.x.x -u username -s /dev_path

Self-service image-level restore of File Systems

You can perform self-service image-level restores of file systems to the original location by using the ddfsrc command. Note that this restore is not supported in the following scenarios:

When the restore destination is the C:\ volume, which can result in the operating system becoming unavailable. When the restore destination is a volume with the File System agent installed.

Self-Service Backup and Restore of the File System Agent 49

NOTE: To perform File System restore to an alternate location, use the centralized restore method in the PowerProtect

Data Manager UI, as described in the section Centralized restore of File Systems on page 45.

Before running ddfsrc, use the ddfsadmin backup command to list the local backups for a particular host and obtain the ID of the save set you want to restore. Using the ddfsadmin utility for File Systems on page 49 provides more information about the ddfsadmin backup command.

To restore from a particular backup, specify the ID of the save set as an input to the ddfsrc command, as in the following example:

ddfsrc -h DFA_SI_DEVICE_PATH=device path (for example, /fsa2) -h DFA_SI_DD_HOST=Protection storage system IPv4 address -c BackupClientHostName (for alternate host restore) -h DFA_SI_DD_USER=Protection storage system username (for example, sysadmin) -h DFA_SI_DD_PASSWORD=Protection storage system password -S 1551407738 -r file path (for example, /volume1_ext3) -i y.

where:

-h "DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit that contains the backup.

-h "DFA_SI_DD_HOST= "

Specifies the name of the protection storage system server that contains the backup.

When you have a remote (secondary) protection storage system server that has replicated databases to restore, type the name of the secondary server. A user on the secondary protection storage system server must be in the same group as the primary protection storage system server.

-h "DFA_SI_DD_USER= "

Specifies the protection storage system username.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

-h "DFA_SI_DD_PASSWORD= "

Specifies the password of the protection storage system user.

A password is only required in this command if restoring to a new host. If you are a file system administrator and need the password to use for a particular storage system, storage unit and user, contact the backup administrator. If restoring to the original host, the password will be picked up from the lockbox.

Self-service file-level restore of File Systems

You can perform self-service file-level restores of File Systems using the ddfsrc command with the -I option.

Before starting the command, create a file that contains the list of files to be restored. Provide the location of this file as an input to the -I option, as shown in the following example.

ddfsrc command with input file specified

ddfsrc -h DFA_SI_DEVICE_PATH=Protection storage unit -h DFA_SI_DD_HOST=Protection storage system IP address -c BackupClientHostName (for alternate host restore) -h DFA_SI_DD_USER=Protection storage system username -h DFA_SI_DD_PASSWORD=Protection storage system password -S savetime-value -I path-of-file-containing-list-of-files-for-restore -i R -d destination-path-for-restoring-files The following steps provide more detail:

1. Use the ddfsadmin command to list all the available backups. If you know the save set ID of the backup from which you want to restore, skip this step.

For example, the following command lists all backups taken in the last 55 days.

[root@XXXX ~]# ddfsadmin backup query -local -t=55d 2. Create an input file that contains the list of files to restore.

For example:

[root@XXXX ~]# cat flr.txt /new_ext3/file.txt

50 Self-Service Backup and Restore of the File System Agent

The flr.txt file specifies a single file to restore (file.txt).

3. Run the ddfsrc command. Ensure that you provide the complete path to the input file that you created.

NOTE: Do not provide a relative path. If you provide a relative path, the command fails.

For example:

ddfsrc -h DFA_SI_DEVICE_PATH=Protection storage unit -h DFA_SI_DD_HOST=Protection storage</

Manualsnet FAQs

If you want to find out how the 19.6 Dell works, you can view and download the Dell PowerProtect 19.6 Data Manager File System Agent User Guide on the Manualsnet website.

Yes, we have the File System Agent User Guide for Dell 19.6 as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The File System Agent User Guide should include all the details that are needed to use a Dell 19.6. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell PowerProtect 19.6 Data Manager File System Agent User Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell PowerProtect 19.6 Data Manager File System Agent User Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell PowerProtect 19.6 Data Manager File System Agent User Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell PowerProtect 19.6 Data Manager File System Agent User Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell PowerProtect 19.6 Data Manager File System Agent User Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.