Delphix

User Guide
January, 2016

Delphix User Guide

You can find the most up-to-date technical documentation at:
docs.delphix.com The Delphix Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to: [email protected]
2016 Delphix Corp. All rights reserved.
Delphix and the Delphix logo and design are registered trademarks or trademarks of Delphix Corp. in the United States and/or other jurisdictions.
All other marks and names mentioned herein may be trademarks of their respective companies.
Delphix Corp.
275 Middlefield Road, Suite 50
Menlo Park, CA 94025

1. _Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 What's New for Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Release 3.1 - 3.1.x.x Known Issues and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Release 3.2 - 3.2.x.x Known Issues and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3 Release 4.0 - 4.0.x.x Known Issues and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4 Release 4.1 - 4.1.x.x Known Issues and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.5 Release 4.2 - 4.2.x.x Known Issues and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6 Release 4.3 - 4.3.x.x Known Issues and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.7 Release 5.0-5.0.x.x Known Issues and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2. _QuickStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Quick Start Guide for The Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Oracle Quick Start Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1.1 Set Up an Oracle Single Instance or RAC Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1.2 Link an Oracle Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1.3 Provision an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 PostgreSQL Quick Start Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2.1 Add a PostgreSQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2.2 Link a PostgreSQL Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2.3 Provision a PostgreSQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 MySQL Quick Start Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3.1 Add a MySQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3.2 Link a MySQL dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3.3 Provision a MySQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4 SQL Server Quick Start Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4.1 Set Up a SQL Server Target Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4.2 Set Up a SQL Server Source Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4.3 Link a SQL Server Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4.4 Provision a SQL Server VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5 SAP ASE Quick Start Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5.1 Add an SAP ASE Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5.2 Link an SAP ASE Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5.3 Provision an SAP ASE VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.6 Create a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.7 Delete a dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.8 Delete a VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.9 Disable a dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3. _SysAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 System Installation, Configuration, and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Installation and Initial Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1.1 Supported Web Browsers and Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1.2 Virtual Machine Requirements for VMware Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1.3 Virtual Machine Requirements for AWS/EC2 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1.4 General Network and Connectivity Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1.5 Checklist of Information Required for Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1.6 Virtual Machine Requirements for OpenStack with the KVM Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Installation and Initial System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.1 The delphix_admin and sysadmin User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.2 Using HostChecker to Confirm Source and Target Environment Configuration . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.3 Installing the Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.4 Setting Up Network Access to the Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.5 Customizing the Delphix Engine System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.6 Setting Up the Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2.7 Retrieving the Delphix Engine Registration Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 Factory Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Managing System Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 System Administrators and Delphix Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 Adding New System Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 Changing System Administrator Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Deleting and Suspending System Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.5 Reinstating System Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Capacity and Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 An Overview of Capacity and Performance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 Setting Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3 Deleting Objects to Increase Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.4 Changing Snapshot Retention to Increase Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.5 Delphix Storage Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.6 Adding and Expanding Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Viewing Action Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13
14
17
24
29
38
46
57
69
78
82
83
84
85
87
89
91
92
94
96
98
99
101
103
105
106
108
109
111
113
114
115
117
119
120
121
122
123
124
125
126
127
130
131
133
134
136
137
138
139
140
143
144
148
149
150
151
152
153
154
155
156
157
159
160
161
162
167
168
169
170

3.4.3 System Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.4 Viewing System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5 Accessing Audit Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.6 Creating Support Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.7 Setting Support Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.8 Setting SysLog Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.9 Diagnosing Connectivity Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.10 Email (SMTP) Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 Configuration Options for Improved Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1 Network Performance Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1.1 Optimal Network Configuration Parameters for the Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1.2 Network Operations Using the Delphix Session Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1.3 Network Performance Tool (iPerf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.2 Storage Performance Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.2.1 Optimal Storage Configuration Parameters for the Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.2.2 Storage Performance Tool (fio) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.3 Host Performance Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.3.1 Target Host Configuration Options for Improved Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2 Performance Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.1 Performance Analytics Tool Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.2 Working with Performance Analytics Graphs in the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.3 Performance Analytics Statistics Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.4 Performance Analytics Tool API Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.5 Performance Analytics Case Study: Using a Single Statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.6 Performance Analytics Case Study: Using Multiple Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4. _DelphixAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Users, Permissions, and Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.1 Users, Groups, and Permissions: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.2 User Privileges for Delphix Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.3 Adding Delphix Users and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.4 Editing, Deleting, and Suspending Delphix Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.5 Assigning Group and Object Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.6 Adding and Deleting Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.7 Adding Delphix Admin Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.8 Managing Individual Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Managing Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2.1 Managing Policies: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2.2 Creating Custom Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2.3 Creating Policy Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2.4 Policies and Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2.5 Configuring Retention on Individual Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Oracle Environments and Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Oracle Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1.1 Supported Operating Systems and DBMS Versions for Oracle Environments . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1.2 Requirements for Oracle Source Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1.3 Requirements for Oracle Target Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1.4 Network and Connectivity Requirements for Oracle Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1.5 Sudo File Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1.6 Sudo Privilege Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Managing Oracle Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.1 Using HostChecker to Validate Oracle Source and Target Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.2 Adding an Oracle Single Instance or RAC Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.3 Adding a Database Installation Home to an Oracle Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.4 Adding a Database to an Oracle Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.5 Discovering Oracle Pluggable Databases in an Oracle Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.6 Adding a Listener to an Oracle Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.7 Changing the Host Name or IP Address for Oracle Source and Target Environments . . . . . . . . . . . . . . . . . . . .
4.2.2.8 Editing Oracle Environment Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.9 Managing Oracle Environment Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.10 Enabling Linking and Provisioning for Oracle Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.11 Deleting an Oracle Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.12 Refreshing an Oracle Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Managing Oracle, Oracle RAC, and Oracle PDB Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.1 Linking an Oracle Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.2 Linking an Oracle Pluggable Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.3 Advanced Data Management Settings for Oracle dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.4 Using Pre- and Post-Scripts with Oracle dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.5 Enabling Validated Sync for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.6 Linking dSources from an Encrypted Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

174
177
178
179
180
181
182
183
186
187
188
189
192
195
198
199
200
207
208
213
214
216
219
220
222
223
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
246
247
248
249
251
255
258
261
265
266
267
270
272
273
274
275
276
277
278
279
280
281
282
283
285
287
289
290
291

4.2.3.7 Linking Oracle Physical Standby Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.3.8 Specifying External Data Directories for Oracle dSources and VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.9 Linking to Oracle dSources with RMAN Compression or Encryption Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.10 Upgrading dSources after an Oracle Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.11 Enabling and Disabling Oracle dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.12 Detaching and Re-Attaching Oracle dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.13 Deleting an Oracle dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.14 Provisioning from a Replicated Oracle dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.15 Oracle dSource Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.16 Oracle Source Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.17 Oracle LiveSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.17.1 Oracle LiveSource User Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.18 Replication Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.19 Replication Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3.20 Performing Final Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Provisioning VDBs from Oracle, Oracle RAC, and Oracle PDB Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.1 Provisioning Oracle VDBs: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.2 Provisioning an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.3 Provisioning an Oracle Virtual Pluggable Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.4 Customizing Oracle VDB Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.4.1 Customizing Oracle VDB Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.4.2 Customizing VDB File Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.5 Provisioning a VDB from an Encrypted Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.6 Time Flows for RAC Provisioning of VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.6.1 TimeFlow Patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.7 Enabling and Disabling an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.8 Provisioning from a Replicated Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.9 Rewinding an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.10 Refreshing an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.11 Deleting an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.12 Migrating an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.13 Upgrading an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4.14 Migrate a vPDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5 Customizing Oracle Management with Hook Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5.1 Oracle Hook Operation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6 Listener and JDBC Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6.1 Adding JDBC Connection String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6.1.1 Adding a New JDBC Connection String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6.2 Verifying the Listener Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6.2.1 Verifying the JDBC Connection String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 SQL Server Environments and Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 SQL Server Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1.1 Requirements for SQL Server Source Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1.2 Requirements for SQL Server Target Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1.3 Requirements for SQL Server Validated Sync Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1.4 Supported Operating Systems, Server Versions, and Backup Software for SQL Server . . . . . . . . . . . . . . . . . .
4.3.1.5 SQL Server Operating System Compatibility Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1.6 SQL Server Target Host iSCSI Configuration Parameter Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1.7 Network and Connectivity Requirements for SQL Server Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1.8 Delphix as a Backup Solution to SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Managing SQL Server Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.1 Setting Up SQL Server Environments: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.2 Using HostChecker to Validate SQL Server Source and Target Environments . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.3 Adding a SQL Server Standalone Target Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.4 Adding a SQL Server Source Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.5 Changing the Host Name or IQN of a SQL Server Target or Staging Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.6 Editing SQL Server Environment Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.7 Managing SQL Server Environment Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.8 Deleting a SQL Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.9 Refreshing a SQL Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.10 Enabling Linking and Provisioning for SQL Server Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2.11 Adding a SQL Server Failover Cluster Target Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3 Managing SQL Server Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.1 Linking a dSource from a SQL Server Database: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.2 Linking a SQL Server dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.3 Upgrading a dSource after a SQL Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.4 Migrating a SQL Server Staging Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.5 Changing the Staging Target Environment for a SQL Server dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.6 Advanced Data Management Settings for SQL Server dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.7 Enabling and Disabling SQL Server dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.8 Detaching and Re-Attaching SQL Server dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

292
295
297
298
299
300
301
302
303
305
307
310
321
322
323
325
326
329
332
334
340
342
343
344
345
348
349
350
351
352
353
354
356
357
360
363
364
365
366
367
368
369
370
372
374
375
378
380
381
384
387
388
391
393
395
396
399
400
401
402
403
404
406
407
408
410
411
412
413
415
416

4.3.3.9 Deleting a SQL Server dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.3.10 Provisioning from a Replicated SQL Server dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3.11 SQL Server dSource Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4 Provisioning VDBs from SQL Server dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.1 Provisioning SQL Server VDBs: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.2 Provisioning a SQL Server VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.3 File Permissions for SQL Server VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.4 Extended Properties for SQL Server VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.5 Upgrading SQL Server VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.6 Migrating a SQL Server VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.7 Renaming a SQL Server VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4.8 Rewinding a SQL Server VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.5 Customizing SQL Server Management with Pre- and Post-Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.6 Customizing SQL Server Management with Hook Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.6.1 SQL Server Hook Operation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 PostgreSQL Environments and Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 PostgreSQL Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1.1 Requirements for PostgreSQL Source Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1.2 Requirements for PostgreSQL Target Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1.3 Supported Operating Systems and Database Versions for PostgreSQL Environments . . . . . . . . . . . . . . . . . . .
4.4.1.4 Network and Connectivity Requirements for PostgreSQL Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2 Managing PostgreSQL Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.1 Setting Up PostgreSQL Environments: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.2 Using HostChecker to Validate PostgreSQL Source and Target Environments . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.3 Adding a PostgreSQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.4 Adding an Installation to a PostgreSQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.5 Adding a Database Cluster to a PostgreSQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.6 Editing PostgreSQL Environment Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.7 Managing PostgreSQL Environment Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.8 Deleting a PostgreSQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.9 Refreshing a PostgreSQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.10 Enabling Staging, Linking and Provisioning for PostgreSQL Environments . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2.11 Changing the Host Name or IP Address for PostgreSQL Source and Target Environments . . . . . . . . . . . . . .
4.4.3 Managing PostgreSQL Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.1 Linking PostgreSQL Data Sources: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.2 Linking a PostgreSQL dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.3 Advanced Data Management Settings for PostgreSQL Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.4 Using Pre- and Post-Scripts with PostgreSQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.5 Enabling and Disabling PostgreSQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.6 Detaching and Re-Attaching PostgreSQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.7 Deleting a PostgreSQL dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3.8 PostgreSQL dSource Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4 Provisioning VDBs from PostgreSQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.1 Provisioning PostgreSQL VDBs: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.2 Provisioning a PostgreSQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.3 Enabling and Disabling PostgreSQL VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.4 Refreshing a PostgreSQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.5 Deleting a PostgreSQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.6 Migrating a PostgreSQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.7 Provisioning a PostgreSQL VDB from a Replicated dSource or VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.8 PostgreSQL VDB Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4.9 Customizing PostgreSQL VDB Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.5 Customizing PostgreSQL Management with Hook Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.5.1 PostgreSQL Hook Operation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 MySQL Environments and Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1 MySQL Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1.1 Requirements for MySQL Source Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1.2 Requirements for MySQL Target/Staging Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1.3 Network and Connectivity Requirements for MySQL Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1.4 Supported Operating Systems and Database Versions for MySQL Environments . . . . . . . . . . . . . . . . . . . . . . .
4.5.2 Managing MySQL Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.1 Setting Up MySQL Environments: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.2 Using HostChecker to Validate MySQL Source and Target Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.3 Adding a MySQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.4 Adding an Installation to a MySQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.5 Adding a MySQL Server to a MySQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.6 Editing MySQL Environment Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.7 Changing the Host Name or IP Address for MySQL Source and Target Environments . . . . . . . . . . . . . . . . . . . .
4.5.2.8 Deleting a MySQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.9 Managing MySQL Environment Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2.10 Refreshing a MySQL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

417
418
419
421
422
423
425
426
427
428
429
430
431
433
437
439
440
441
443
444
445
448
449
450
452
454
455
456
457
458
459
460
461
462
463
464
466
468
469
470
471
472
474
475
476
478
479
480
481
482
483
485
486
489
492
493
494
495
496
499
500
501
502
504
506
507
508
509
510
511
512

4.5.2.11 Enabling Staging, Linking, and Provisioning for MySQL Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5.3 MySQL Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.1 Linking MySQL Data Sources: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.2 Linking a MySQL dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.3 Advanced Data Management Settings for MySQL Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.4 Using Pre- and Post-Scripts with MySQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.5 Deleting a MySQL dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.6 Detaching and Re-Attaching MySQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.7 Enabling and Disabling MySQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3.8 MySQL dSource Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4 Provisioning VDBs from MySQL dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.1 Provisioning MySQL VDBs: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.2 Provisioning a MySQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.3 Customizing MySQL VDB Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.4 Provisioning a MySQL VDB from a Replicated dSource or VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.5 Enabling and Disabling MySQL VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.6 Deleting a MySQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.7 Migrating a MySQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.8 Refreshing a MySQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4.9 MySQL VDB Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.5 Customizing MySQL Management with Hook Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.5.1 MySQL Hook Operation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 SAP ASE Environments and Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1 SAP ASE Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.1 Requirements for SAP ASE Source Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.2 Requirements for SAP ASE Target Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.3 Network and Connectivity Requirements for SAP ASE Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.4 Supported Operating Systems and Database Versions for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2 Managing SAP ASE Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.1 Managing SAP ASE Environments: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.2 Using HostChecker to Validate SAP ASE Source and Target Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.3 Adding an SAP ASE Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.4 Editing SAP ASE Environment Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.5 Changing the Host Name or IP Address of an SAP ASE Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.6 Deleting an SAP ASE Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.7 Managing SAP ASE Environment Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.8 Refreshing an SAP ASE Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.9 Enabling Linking and Provisioning for SAP ASE Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3 Managing SAP ASE Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.1 Linking SAP ASE Data Sources: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.2 Linking an SAP ASE Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.3 Advanced Data Management Settings for SAP ASE dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.4 Using Pre- and Post-Scripts with SAP ASE Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.5 Deleting an SAP ASE dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.6 Detaching and Re-Attaching SAP ASE dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.7 Enabling and Disabling SAP ASE dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3.8 SAP ASE dSource Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4 Provisioning VDBs from SAP ASE dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.1 Provisioning SAP ASE VDBs: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.2 Provisioning an SAP ASE VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.3 Provisioning an SAP ASE VDB from a Replicated VDB or dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.4 Enabling and Disabling SAP ASE VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.5 Deleting an SAP ASE VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.6 Migrating an SAP ASE VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.7 Refreshing an SAP ASE VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.8 Rewinding an SAP ASE VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4.9 SAP ASE VDB Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5 Customizing SAP ASE Management with Hook Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5.1 SAP ASE Hook Operation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 DB2 Environments and Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.1 DB2 on Delphix: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2 DB2 Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2.1 DB2 Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2.2 Network and Connectivity Requirements for DB2 Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2.3 Requirements for DB2 Hosts and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3 Managing DB2 Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3.1 Setting Up DB2 Environments: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3.2 Adding a DB2 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3.3 Editing DB2 Environment Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3.4 Managing DB2 Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3.5 Managing DB2 Users and Instance Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

513
514
515
516
518
520
521
522
524
525
527
528
529
531
532
533
534
535
536
537
539
542
545
546
547
549
550
553
554
555
557
559
560
561
562
563
564
565
566
567
568
570
572
573
574
575
576
577
578
579
581
582
583
584
585
586
587
589
592
595
596
598
599
600
602
604
605
607
609
610
611

4.7.3.6 Deleting a DB2 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.3.7 Refreshing a DB2 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4 Managing DB2 Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.1 DB2 dSource Icon Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.2 Linking a dSource from a DB2 Database: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.3 Linking a DB2 dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.4 Deleting a DB2 dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.5 Enabling and Disabling DB2 dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.6 Advanced Data Management Settings for DB2 dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.7 Using Pre- and Post-Scripts with DB2 dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4.8 Provisioning from a Replicated DB2 dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.5 Provisioning VDBs from DB2 dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.5.1 Provisioning DB2 VDBs: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.5.2 Provisioning a DB2 VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.5.3 Database Permissions for Provisioned DB2 VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.5.4 Upgrading DB2 VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.5.5 Rewinding a DB2 VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.6 Customizing DB2 Management with Hook Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.6.1 DB2 Hook Operation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5. _Data Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Backup and Recovery Strategies for the Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Backup and Recovery Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.3 Mapping Requirements to Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.4 Backup Solution Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 Replication Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2 Replication Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.3 Replication User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.4 Configuring Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.4.1 Enabling Replicated Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.5 Replicas and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.6 Failing Over a Replica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.7 Updating Replication User Credentials from Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.8 Provisioning from Replicated Data Sources or VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Selective Data Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 Selective Data Distribution Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 Selective Data Distribution Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.3 Selective Data Distribution User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.4 Configuring Selective Data Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.5 Selective Data Distribution and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 V2P: Virtual to Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Virtual to Physical: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2 V2P with an Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2.1 Move an Oracle VDB to a Physical ASM or Exadata Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.3 V2P with a SQL Server VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.4 V2P with a PostgreSQL dSource or VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.5 V2P with an SAP ASE dSource or VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.6 Manually Recovering a Database after V2P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.7 Customizing Target Directory Structure for Database Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.8 V2P with Unstructured Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.9 V2P with a MySQL VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6. _Delphix Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Delphix Masking Quick Start Guide - An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Masking Engine Terms Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 Masking Engine Install, System Configuration, and Network Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3 Prepare Data for Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.4 Masking Engine Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.4.1 Add an Application and Create a New Environment and Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.4.2 Create Data Masking Rule Sets, Algorithms, and Inventories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.4.3 Mask Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.5 Provisioning Masked VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.5.1 Troubleshoot Provisioning Errors for Masked VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.6 Masking API Calls to Run a Masking Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.7 Advanced Integrated Delphix Masking Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Masking Engine User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 Chapter 1: Masking Engine Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1.1 Basic Tasks for a Database File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1.2 Certify Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1.3 Create and Define a Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1.4 Create and Define Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

612
613
614
615
617
619
624
625
626
627
628
629
630
631
633
635
636
637
640
643
644
645
647
649
651
653
654
656
659
665
668
670
671
672
673
674
675
677
679
685
688
689
690
691
694
697
698
699
700
701
703
704
705
706
709
711
713
714
716
719
724
726
733
734
736
738
741
742
743
744
745

6.2.1.5 Create or Import an Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.1.6 Masking Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1.7 Profile Data and Define Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1.8 Provision Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1.9 Start Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2 Chapter 2: Masking Engine Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2.1 Profiling Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2.2 Provisioning and/or Subsetting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2.3 Masking Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2.4 Certifying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3 Chapter 3: Understand and Manage the Masking Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.1 Managing Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.2 Managing Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.3 Mainframe Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.4 Managing Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.5 Managing the Masking Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.6 Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.7 File Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.8 Tokenization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.9 Monitor Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.10 Scheduler Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.11 Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.12 Admin Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3.13 Risk Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4 Restarting Delphix Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Masking Engine Admin Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.1 Managing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.1.1 The Settings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2 Managing Algorithm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.1 Algorithm Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.2 Adding New Masking Engine Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.3 Secure Lookup Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.4 Segmented Mapping Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.5 Segmented Mapping Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.6 Mapping Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.7 Binary Lookup Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.8 Tokenization Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.9 Min Max Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.10 Data Cleansing Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.11 Free Text Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.2.12 Free Text Redaction Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.3 Managing Domain Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.3.1 Adding New Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.4 Managing Profiler Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.4.1 Profiler Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.4.2 Adding New Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.4.3 Adding or Editing a Profiler Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.4.4 Practical Profiling Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.5 Managing Roles Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.5.1 Roles Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.5.2 Adding Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.6 Managing Mapping Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.6.1 Adding Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.7 Managing File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.7.1 To create a new file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.7.2 To Import a New File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.7.3 To delete a file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.8 Managing Remote Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.8.1 To define a remote server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.8.2 To edit a remote server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.8.3 To delete a remote server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.9 Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.9.1 The Users Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.9.2 Creating and Editing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.10 Utilization Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.10.1 The Utilization Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.11 Accessing Information About Your Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.11.1 The About Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.12 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.12.1 Configuring a Boot Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

746
747
748
749
750
751
752
753
754
756
757
758
760
762
763
767
772
779
781
788
789
791
793
794
795
796
798
799
800
801
815
816
817
818
819
821
822
823
826
827
828
829
830
832
833
837
838
840
842
843
845
846
847
848
849
851
852
853
854
856
857
858
859
861
862
863
864
865
866
867
869

6.3.1.12.2 Configuring a Security Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.1.13 User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.13.1 Storing Database Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.13.2 Authenticating Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.13.3 Authorizing Users (Roles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.14 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.14.1 Configuring Masking Engine to use Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.14.2 Configuring Log File Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.14.3 Configuring the Default Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.14.4 Restarting Masking Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.15 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.15.1 Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.15.2 Stack Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.15.3 Application Server Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.15.4 Database Server Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1.15.5 Backups and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Release Notes for Delphix Masking 4.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7. _XPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Cross-Platform Provisioning of Oracle Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 Cross-Platform Provisioning of Oracle dSources: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.2 Enabling Oracle dSources for Cross-Platform Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.3 Provisioning an Oracle dSource across Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.4 Creating Scripts for Cross-Platform Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8. _Unstructured Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Unstructured Files: Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 Unstructured Files Environment Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.1 Unstructured Files on Unix Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.1.1 Requirements for Unix Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.1.2 Network and Connectivity Requirements for Unix Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.1.3 Sudo Privilege Requirements and File Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.1.4 Managing Unix Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.2 Unstructured Files on Windows Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.2.1 Requirements for Windows Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.2.2 Network and Connectivity Requirements for Windows Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.2.3 Managing Windows Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.2.4 Options for Linking Unstructured Files on Windows Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1.2.5 Network and Connectivity Requirements for Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.2 Linking Unstructured Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.3 Provisioning Unstructured Files as vFiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.4 Customizing Unstructured Files with Hook Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.4.1 Unstructured Files Hook Operation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.4.1.1 Managing Data Operations for vFiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.5 Creating Empty vFiles from the Delphix Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.6 Restoring Data from Unstructured Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9. _Virtualizing Oracle Enterprise Business Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Virtualizing Oracle Enterprise Business Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Oracle EBS + Delphix: Conceptual Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Oracle EBS R12.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.1 Source EBS R12.2 Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.2 Virtual EBS R12.2 Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.3 Preparing a Source EBS R12.2 Instance for Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.4 Linking a Source EBS R12.2 Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.5 Preparing Target EBS R12.2 Environments for Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.6 Provisioning a Virtual EBS R12.2 Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.6.1 Monitoring EBS R12.2 dbTechStack Provisioning Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2.6.2 Monitoring EBS R12.2 appsTier Provisioning Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 Oracle EBS R12.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.1 Source EBS R12.1 Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.2 Virtual EBS R12.1 Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.3 Preparing a Source EBS R12.1 Instance for Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.4 Linking a Source EBS R12.1 Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.5 Preparing Target EBS R12.1 Environments for Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.6 Provisioning a Virtual EBS R12.1 Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.6.1 Monitoring EBS R12.1 dbTechStack Provisioning Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3.6.2 Monitoring EBS R12.1 appsTier Provisioning Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4 Oracle EBS 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4.1 Source EBS 11i Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4.2 Virtual EBS 11i Instance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4.3 Preparing a Source EBS 11i Instance for Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4.4 Linking a Source EBS 11i Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4.5 Preparing Target EBS 11i Environments for Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

870
871
872
873
874
875
878
879
880
881
882
883
884
885
886
887
888
891
892
893
894
895
896
897
898
899
900
901
903
906
908
911
912
914
916
919
920
922
924
926
929
932
938
939
941
942
943
945
946
947
949
951
954
956
961
962
963
964
965
966
968
971
973
979
980
981
982
983
984
986
989

9.1.4.6 Provisioning a Virtual EBS 11i Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1.4.6.1 Monitoring EBS 11i dbTechStack Provisioning Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4.6.2 Monitoring EBS 11i appsTier Provisioning Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5 Managing Data Operations of Virtual EBS Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.1 Starting and Stopping a Virtual EBS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.2 Rewinding a Virtual EBS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.3 Refreshing a Virtual EBS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.4 Enabling and Disabling a Virtual EBS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.5 Deleting a Virtual EBS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.6 Modifying the appsTier Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.7 Replicating a Virtual EBS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5.8 Upgrading a Delphix Engine hosting a Virtual EBS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6 Virtual EBS Instance Recipes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6.1 Configuring a Jet Stream Data Template for EBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6.2 Managing the APPS Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6.3 Refreshing a Target dbTier Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10. _Mission Control Delphix Admin User Guide (2015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Getting Started with Mission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Delphix Engine Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Search and Run Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 Filter, Organize, and Extract Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5 Understanding the Graphs Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.6 Mission Control Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7 Support for Mission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11. _JetStream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 Jet Stream Admin Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1 Getting Started with Jet Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.2 Jet Stream Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.3 Navigating the Jet Stream Admin Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.4 Understanding Jet Stream User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.5 Understanding Jet Stream Data Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.6 Understanding How to Manage Data Template Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.7 Understanding Jet Stream Data Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.8 Understanding Bookmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.9 Understanding Jet Stream Usage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.10 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.11 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Jet Stream Data User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.2 Jet Stream User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.3 Jet Stream Data Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.4 Working with Data Operations and Sources in a Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.5 Understanding Jet Stream Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.6 Jet Stream Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.7 Jet Stream Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12. _Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Command Line Interface Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1 Command Line Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1.1 Connecting to the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1.2 CLI Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1.3 Managing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1.4 Managing Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1.5 Array Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1.6 Untyped Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.1.7 CLI Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.2 Delphix Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.2.1 Object Type Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.2.2 Object Names and References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.2.3 Databases and Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.2.4 Asynchronous Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.3 Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.3.1 CLI Help and Display Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.3.2 CLI Context Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.3.3 CLI Object Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.3.4 CLI Property Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.3.5 CLI Miscellaneous Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.4 CLI Cookbook: Common Workflows, Tasks, and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.4.1 CLI Cookbook: Authentication and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.4.1.1 CLI Cookbook: Configuring Key-Based SSH Authentication for Automation . . . . . . . . . . . . . . . . . . . . . .
12.1.4.1.2 CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users . . . . . . . . . . . . . . . . . .
12.1.4.2 CLI Cookbook: System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

991
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1011
1012
1013
1014
1024
1031
1033
1036
1038
1039
1040
1042
1043
1045
1048
1052
1059
1063
1072
1073
1080
1081
1082
1084
1085
1090
1103
1113
1116
1117
1118
1119
1121
1122
1124
1125
1126
1127
1128
1129
1132
1133
1134
1135
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1149
1151

12.1.4.2.1 CLI Cookbook: Configuring A Second Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152

12.1.4.2.2 CLI Cookbook: Adding A Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
12.1.4.2.3 CLI Cookbook: Changing the Default Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154
12.1.4.2.4 CLI Cookbook: How to Change a Delphix User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
12.1.4.2.5 CLI Cookbook: Creating Alert Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
12.1.4.2.6 CLI Cookbook: Retrieve Capacity Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
12.1.4.3 CLI Cookbook: Hosts and Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163
12.1.4.3.1 CLI Cookbook: Adding a UNIX Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
12.1.4.3.2 CLI Cookbook: Adding a SQL Server Source Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166
12.1.4.3.3 CLI Cookbook: Setting Multiple Addresses for a Target Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
12.1.4.3.4 CLI Cookbook: How to Change Environment User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168
12.1.4.4 CLI Cookbook: Source Databases and dSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170
12.1.4.4.1 CLI Cookbook: Detaching and Attaching an Oracle dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171
12.1.4.4.2 CLI Cookbook: Disabling LogSync for a dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173
12.1.4.4.3 CLI Cookbook: Enabling Oracle Validated Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174
12.1.4.4.4 CLI Cookbook: Linking a Microsoft SQL Server Database Loading from a Specific Full Backup of the
Source Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175
12.1.4.4.5 CLI Cookbook: Linking a Microsoft SQL Server Database Loading from the Last Full Backup of the Source
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
12.1.4.4.6 CLI Cookbook: Linking to a Single Instance Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1178
12.1.4.4.7 CLI Cookbook: Listing Data Source Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180
12.1.4.4.8 CLI Cookbook: Detaching and Attaching a SQL Server dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181
12.1.4.4.9 CLI Cookbook: How to Change Database User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
12.1.4.5 CLI Cookbook: VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185
12.1.4.5.1 CLI Cookbook: Changing the SID of Oracle RAC VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186
12.1.4.5.2 CLI Cookbook: Oracle VDB Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1188
12.1.4.5.3 CLI Cookbook: Provisioning a Single Instance Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1190
12.1.4.5.4 CLI Cookbook: Provisioning a SQL Server VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
12.1.4.5.5 CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
12.1.4.5.6 CLI Cookbook: Rolling Forward a VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
12.1.4.5.7 CLI Cookbook: Refresh a VDB from a Specific Timepoint or Latest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1198
12.1.4.5.8 CLI Cookbook: Repairing a Timeflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199
12.1.4.5.9 CLI Cookbook: Changing SGA Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200
12.1.4.5.10 CLI Cookbook: Rolling Back a VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
12.1.4.5.11 CLI Cookbook: Creating a VDB Config Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203
12.1.4.5.12 CLI Cookbook: Creating a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
12.1.4.5.13 CLI Cookbook: Provisioning a SAP ASE VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
12.1.4.5.14 CLI Cookbook: Taking a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207
12.1.4.5.15 CLI Cookbook: Determining the Snapshot used to provision a VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
12.1.4.5.16 CLI Cookbook: Detaching and Attaching a SAP ASE dSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1210
12.1.4.6 CLI Cookbook: Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214
12.1.4.6.1 CLI Cookbook: Adding a Replication Spec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
12.1.4.6.2 CLI Cookbook: Deleting a Replication Spec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
12.1.4.6.3 CLI Cookbook: Failing Over a Namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
12.1.4.6.4 CLI Cookbook: Triggering Immediate Execution of a Replication Spec . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
12.1.4.7 CLI Cookbook: JetStream Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1220
12.1.4.7.1 CLI Cookbook: How to Delete a JetStream Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
12.1.4.7.2 CLI Cookbook: How to Delete a JetStream Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1222
12.2 Web Service API Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223
12.2.1 API Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224
12.2.2 Web Service Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225
12.2.3 Web Service Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227
12.2.4 CLI to Web Services Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229
12.2.5 GUI API Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231
12.2.6 API Cookbook: Common Tasks, Workflows, and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234
12.2.6.1 API Cookbook: Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
12.2.6.2 API Cookbook: Host Environment Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
12.2.6.3 API Cookbook: List Alerts and List Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
12.2.6.4 API Cookbook: List dSources and VDBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238
12.2.6.5 API Cookbook: List Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
12.2.6.6 API Cookbook: Refresh VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
12.2.6.7 API Cookbook: Example Provision Of An Oracle VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241
12.2.6.8 API Cookbook: Stop/Start a VDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
12.2.7 CLI to Python Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245
12.2.8 Python Cookbook: Adding a UNIX Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247

Delphix User Guide 2016 Delphix

_Release

13

Delphix User Guide 2016 Delphix

What's New for Delphix Engine

The Delphix Engine 5.0 provides a bounty of features, bug fixes, and performance improvements.
EBS Multi-node appsTier Support
Integrated Masking
Masked VDB Provisioning
Selective Data Distribution
DB2 Support
DB2 LUW
Better Data Security
Support for Encrypted Microsoft SQL Server Backups
Password-protected ASE Backups
Expanded Platform Support
Easy Oracle RAC Node Changes
Support for Oracle Custom Environment Variables
Expanded Version Support
ASE
Improved Jet Stream
Jet Stream Bookmark Cleaning
Multi-owner Data Containers
Technical Improvements
UX Change
Faster Start
Improved Masking Workflows
ZFS Improvements
Compressed ZFS Send/Receive
Windows Target Environments
Add Windows target environments w/ GUI

EBS Multi-node appsTier Support

Delphix can now support the automated deployment of EBS with multi-node application tiers, enabling the creation of non-production
environments that have multi-node topologies. To find additional information about EBS Multi-nodes, see Oracle EBS + Delphix: Conceptual
Overview.

Integrated Masking
Masked VDB Provisioning
You can now create masked copies of data at VDB provision time, using masking jobs defined on the masking engine that run when you provision
or refresh the VDB. It

is now even easier to mask copies of production and deliver secure data across teams. From
one streamlined workflow, admins can define how/what needs to be masked, who can access the data, and
distribute that masked data. To find additional information about masked VDB provisioning, see Provisioning
Masked VDBs.
Selective Data Distribution
You can now replicate masked data directly to a target Delphix engine, while ensuring unmasked sensitive
data does not leave the production site. This feature is critical for implementing a hybrid cloud deployment in which you want only
masked data in the cloud, as well as other cases in which you want only masked data in target systems, such as offshore QA and outsourced
analytics. For more information about selective data distribution, see Selective Data Distribution Overview.

14

Delphix User Guide 2016 Delphix

DB2 Support
DB2 LUW
DB2 LUW will be available on a single machine, single partition DBs on versions 10.1 and above. We will support customers on AIX 6.1+ and
Redhat 6.5+. For more information about DB2 LUW, see DB2 on Delphix: An Overview.

Better Data Security

Support for Encrypted Microsoft SQL Server Backups
Delphix enables you to load password-protected encrypted MSSQL backups taken by LiteSpeed and RedGate. You will also be able to use
point-in-time provisioning between snapshots. For more information about encrypted Microsoft SQL Server backups, see Advanced Data
Management Settings for SQL Server dSources.

Password-protected ASE Backups

Delphix now enables you to extract and load password-protected ASE backups. For more information about password-protected ASE backups,
see Linking an SAP ASE Data Source.

Expanded Platform Support

Easy Oracle RAC Node Changes
You can now add or remove nodes dynamically on Oracle RAC target host VDBs. For more information, see Provisioning Oracle VDBs: An
Overview.

Support for Oracle Custom Environment Variables

Delphix now allows you to dictate custom environment variables that you can set prior to any administrative action, such as provision, start, stop,
rollback, or refresh. For more information, see Provisioning an Oracle VDB.

Expanded Version Support

ASE
ASE 15.0.3 on AIX 5.3
ASE 15.5 on AIX 5.3
ASE 15.7 on AIX 6.1 and RHEL 5.6
Support for provisioning ASE 15.7 to multi-node Veritas clusters 5.1 on RHEL 5 & 6 (no failover support)
MySQL Enterprise Edition 5.6 support on Solaris 11, RHEL 6.2, 6.3, 6.4
For more details, visit Supported Operating Systems and Database Versions for SAP ASE.

Improved Jet Stream

Jet Stream Bookmark Cleaning
You can create expiration dates for your Jet Stream bookmarks, so the Delphix Engine will remove them automatically and reclaim space. For
more information about setting an expiration date for a bookmark, see Understanding Bookmarks and Working with Data Operations and
Sources in a Container.

Multi-owner Data Containers

15

Delphix User Guide 2016 Delphix

Now Jet Stream users can share ownership of a single data container. For more information on multi-owner data containers, see Jet Stream
Data Concepts and Working with Data Operations and Sources in a Container.

Technical Improvements
UX Change
Faster Start
For users with a large number of databases, application startup time will be significantly faster.

Improved Masking Workflows

The masking engine is integrated into one OVA. You can now associate masking jobs with a source. You can select masking jobs from a
drop-down menu and get started faster. For more information about masking workflows, see Delphix Masking Quick Start Guide - An Overview
.

ZFS Improvements
Compressed ZFS Send/Receive
Performance of replication across a WAN (for example, to the cloud) is now improved with send stream pre-compression. This will lower CPU use
and improve bandwidth in cases where CPU performance was a bottleneck, or where compression was not previously enabled for replication. All
replications are now sent compressed so there is no longer a "compressed" checkbox in the replication UI. There is no additional CPU cost,
because the data is compressed when it is first written, rather than as it is being replicated. Reported replication throughput may be lower
because the amount of compressed data sent is reported, rather than the amount of uncompressed data. For more information see, Configuring
Replication.

Windows Target Environments

Add Windows target environments w/ GUI
You can now add a Windows standalone target environment with the Delphix admin GUI, where you can specify a target hosts
address/port/credentials. For more information, see Adding a SQL Server Standalone Target Environment.

16

Delphix User Guide 2016 Delphix

Release Notes
Welcome to the 5.0 release of the Delphix Engine database virtualization system.
5.0 Upgrade Matrix
Tested Browser Configuration Matrix
Supported Oracle DBMS Versions and Operating Systems for Source and Target Environments
Supported DBMS Versions
Supported Operating Systems
Supported SQL Server Versions, Operating Systems, and Backup Software
Supported Versions of Windows OS
Supported Versions of SQL Server
Supported SQL Server Backup Software
Supported PostgreSQL Versions and Operating Systems
Supported DBMS Versions
Supported Operating Systems
Supported SAP ASE Versions and Operating Systems
Supported MySQL Versions and Operating Systems
Supported DBMS Versions
Supported MySQL Storage Engine
Licenses and Notices

5.0 Upgrade Matrix

Upgrades to Delphix Engine 5.0 are supported from 4.2.0.0 and above.
5.0.0.0 5.0.0.1 5.0.0.2 5.0.1.0
4.1 and prior
4.2 - 4.3
5.0.0.0
5.0.0.1
5.0.0.2
Key:
Color

Supported?

VDB Downtime Required? 1

No

N/A

Yes

Required

Yes

Not Required

Yes

Optional 2

1. VDB Downtime is caused by a reboot of the Delphix Engine when DelphixOS is modified by an upgrade.
2. VDB Downtime may be optional for an upgrade when a release contains DelphixOS changes that are also optional. In such a scenario,
the DelphixOS changes may be deferred (see documentation on Deferred OS Upgrade).

Tested Browser Configuration Matrix

OS Supported

Browsers Supported

Adobe Flash/Flex

Minimum Memory

Windows XP Professional SP3

Firefox, Chrome

10.x

4GB

Windows Vista SP2

Internet Explorer 9.x

10.x

4GB

17

Delphix User Guide 2016 Delphix

Windows 7

Internet Explorer 9.x, 10.x, 11.x

10.x

4GB

Windows 7

Firefox, Chrome

10.x

4GB

Windows 7 x64

Internet Explorer 9.x, 10.x, 11.x

10.x

4GB

Windows 7 x64

Firefox, Chrome

10.x

4GB

Mac OS X

Firefox, Chrome

9.0.3 (6531.9)

4GB

Supported Oracle DBMS Versions and Operating Systems for Source and Target Environments
Source and Target OS and DBMS Compatibility
The source and target must be running the same DBMS/Operating System combination (for example, Oracle 10.2.0.4 on RHEL 5.2) in
order to successfully provision a VDB to the target. If the DBMS versions are compatible, the OS version on a target host can be
different from the OS version on the source host.

Supported DBMS Versions

Oracle 9.2.0.8
Oracle 10.2
Oracle 11.1
Oracle 11.2
Oracle 12.1
Oracle 9.2.0.8
The Delphix Engine has limited support for Oracle 9.2.0.8 and cannot link to a database that has a compatibility setting lower than
9.2.0.8.
Delphix features supported with Oracle 9.2.0.8:
dSource

VDB

SnapSync

Yes

No

LogSync

No

No

Rewind

Not Applicable

No

V2P (virtual to physical)

Yes

No

RAC

No

No

Standby Database

No

No

Oracle 10.2.0.4
The Delphix Engine does not support Oracle 10.2.0.4 databases using Automatic Storage Management (ASM) that do not have the
patch set for Oracle Bug 7207932. This bug is fixed in patch set 10.2.0.4.2 onward.

18

Delphix User Guide 2016 Delphix

Supported Operating Systems

Operating System

Version

Processor Family

Solaris

9, 10U5 - 10U11, 11U1, 11U2

SPARC

Solaris

10U5 - 10U11, 11U1, 11U2

x86_64

Red Hat Enterprise Linux

4.7, 4.8, 4.9

5.3 - 5.11
6.0 - 6.6

x86_64

Oracle Enterprise Linux

5.3 - 5.11
6.0 - 6.6

x86_64

Novell SUSE Linux Enterprise Server

10, 10SP1, 10SP2, 10SP3

11, 11SP1, 11SP2, 11SP3

x86_64

AIX

5.3, 6.1, 7.1

Power

HP-UX

11i v2 (11.23)

IA64

11i v3 (11.31)
Delphix supports all 64-bit OS environments for source and target, though 64-bit Linux environments also require that a 32-bit version of glibc
installed
Required HP-UX patch for Target Servers

PHNE_37851 - resolves a known bug in HP-UX NFS client prior to HP-UX 11.31.

Supported SQL Server Versions, Operating Systems, and Backup Software

Supported Versions of Windows OS
Windows Server 2003 SP2, 2003 R2
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012, 2012

R2

Delphix supports only 64-bit versions of Windows on target hosts and validated-sync-target hosts.
Target hosts and validated-sync-target hosts running Windows Server 2003 SP2 or 2003 R2 must install the hotfix documented in KB
943043.

For Windows 2008 R2

Updates NTFS.sys and uNTFS.dll

KB Article Number(s): 967351

Language: All (Global)

Platform: x64

19

Delphix User Guide 2016 Delphix

Location: (http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix385766/7600/free/44135
1_intl_x64_zip.exe)

Updates MSISCI.sys

KB Article Number(s): 2277122

Language: All (Global)

Platform: x64

Location: (http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix388733/7600/free/44067
5_intl_x64_zip.exe)

For Windows 2008 SP2

https://support.microsoft.com/en-us/kb/948275/
Ntfs.sys and untfs.dll for windows server 2008 SP2
In order to install NTFS.sys first go to c:\windows\system32\drivers, right click on ntfs.sys go to properties and check the tab
details In the details Tab check the file Version if the file version is less than 6.0.6002.22811 the one mentioned here
In order to install uNTFS.dll first go to c:\windows\system32, right click on untfs.dll go to properties and check the tab details In the
details Tab check the file Version if the file version is less than 6.0.6002.22811 the one mentioned here
Run the below mentioned commands.
Package: NTFS.sys and uNTFS.dll
--------------------------------------------------------------------------------------------------------------------KB Article Number(s): 967351
Language: All (Global)
Platform: x64
Location: (http://hotfixv4.microsoft.com/Windows%20Vista/sp3/Fix385798/6000/free/441782_intl_x64_zip.exe)

Download the file mentioned in the above link

Save the file in a folder named TEST under C drive.
Extract the zipped file.
Run the below mentioned command.

Expand -f:* c:\TEST\(write the complete details of the file with extension .msu).msu c:\TEST
Expand -f:* c:\TEST\(write the complete details of the file with extension .cab).cab c:\TEST
pkgmgr /ip /m:c:\Test\update-bf.mum

There are further restrictions on supported Windows and SQL Server versions for SQL Server Failover Cluster target environments.
See Adding a SQL Server Failover Cluster Target Environment for details.

20

Delphix User Guide 2016 Delphix

Supported Versions of SQL Server

SQL Server Version

Delphix Version

SQL Server 2005 (9.0)

Delphix 3.x

SQL Server 2008 (10.0)

Delphix 3.x

SQL Server 2008 R2 (10.5)

Delphix 3.x

SQL Server 2012 (11.0)

Delphix 3.1.2 and beyond

SQL Server 2014 (12.0)

Delphix 4.1.3 and beyond

Delphix supports SQL Server AlwaysOn Availability Groups as a dSource but creation of a VDB on AlwaysOn Availability Groups is not
supported. Delphix

supports Windows Server Failover Cluster (WSFC) as a dSource and also as a target

(VDB).

Supported SQL Server Backup Software

The Delphix Engine interacts with source database backups in the following ways:
When linking a new source database, the Delphix Engine can use an existing full backup to load the source database data
When performing a sync of an existing dSource, the Delphix Engine can use an existing full backup
After the dSource is created, the Delphix Engine picks up any new backups that are taken on the source database and applies them to
the copy of the source database on the Delphix Engine. This includes:
Transaction log backups for databases in Full or Bulk-Logged recovery models
Differential and full backups for databases in Simple recovery model
Delphix currently supports the following backup software for source database backups:
SQL Server native backups
Quest/NetVault LiteSpeed
If the source database is backed up with LiteSpeed, the source and the staging environments must have LiteSpeed installed on
them. The version of LiteSpeed on the staging environment must be the same or higher than that on the source. Delphix
currently supports LiteSpeed v5.0.0.0 to v8.x.
Red Gate SQL Backup Pro
If the source database is backed up with SQL Backup Pro, the source and the staging environments must have SQL Backup Pro
installed on them. The version of SQL Backup Pro on the staging environment must be the same as that on the source. Delphix
currently supports SQL Backup Pro v7.3 and onwards.

In versions 4.3.3.0 and newer Delphix supports encrypted backups; if you are running an older version of the Delphix Engine (v 4.3.2.x 3.0) encrypted backups are not supported.

Supported PostgreSQL Versions and Operating Systems

This topic describes supported operating systems and database versions for PostgreSQL.
Source and Target OS and DBMS Compatibility
The source and target environments must be running the same DBMS/Operating System combination (for example, PostgreSQL 9.2 on
RHEL 6.3) in order to successfully perform linking and provisioning.

Supported DBMS Versions

DBMS

Version

Processor Family

21

Delphix User Guide 2016 Delphix

PostgreSQL

9.2, 9.3, 9.4

x86_64

EnterpriseDB Postgres Plus Advanced Server

9.2, 9.3, 9.4

x86_64

Supported Operating Systems

Operating System

Version

Processor Family

Red Hat Enterprise Linux 5

RHEL 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 5.10,5.11

x86_64

Red Hat Enterprise Linux 6

RHEL 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6

x86_64

Supported SAP ASE Versions and Operating Systems

This topic describes supported operating systems and database versions for SAP ASE.

Source and Target OS and DBMS Compatibility

The source and target must be running the same DBMS/Operating System combination, (although users can run different different
patch/sp levels) in order to successfully provision a VDB to the target. For example, if the source is running SAP ASE 16, the target can
be running ASE 16SP1. The Operating System platform must be the same between the source and target, even when the operating
system version may differ. For example, if the source is running Red Hat Enterprise Linux 6.2 x86_64 then the target could be running
Red Hat Enterprise Linux 6.4 x86_64, but not Solaris 10 SPARC.

DBMS Versions

Operating System Versions / Processor Family

SAP Adaptive Server Enterprise (ASE) 12.5

Red Hat Enterprise Linux 5.x / x86_64

Veritas Cluster Server

Solaris 10 / x86_64, SPARC

SAP Adaptive Server Enterprise (ASE) 15.03

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64

SuSE Linux Enterprise Server 11.x
Solaris 10 / x86_64, SPARC
AIX 5.3 / POWER

SAP Adaptive Server Enterprise (ASE) 15.5

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64

Solaris 10 / x86_64, SPARC
AIX 5.3 / POWER

SAP Adaptive Server Enterprise (ASE) 15.7

Red Hat Enterprise Linux 5.x / x86_64

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64
Solaris 10 / x86_64, SPARC
AIX 6.1, 7.1 / POWER

SAP Adaptive Server Enterprise (ASE) 16

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64

Solaris 10 / x86_64, SPARC

Supported MySQL Versions and Operating Systems

This topic describes supported operating systems and database versions for MySQL.

22

VCS 5.1 on RHEL 5 & 6

Delphix User Guide 2016 Delphix

Source and Target OS and DBMS Compatibility

The source and target environments must be running the same DBMS/Operating System combination (for example, MySQL 5.6 on
RHEL 6.3) in order to successfully perform linking and provisioning.

Supported DBMS Versions

DBMS Versions

Operating System Versions

Processor Family

MySQL Community Edition GA 5.5, 5.6

RHEL 6.2, 6.3, 6.4

x86_64

MySQL Community Edition >=5.7.7

RHEL 6.2, 6.3, 6.4

x86_64

MySQL Enterprise Edition GA 5.6

Solaris 11, RHEL 6.2, 6.3, 6.4

x86_64

MariaDB Server 10.0 GA Series (>=10.0.10)

RHEL 6.2, 6.3, 6.4

x86_64

MariaDB Enterprise 10.0 GA Series (>=10.0.10)

RHEL 6.2, 6.3, 6.4

x86_64

Supported MySQL Storage Engine

Storgage Engine
InnoDB

Licenses and Notices

Highstock software products is owned and licensed through Highsoft AS.

23

Delphix User Guide 2016 Delphix

Release 3.1 - 3.1.x.x Known Issues and Changes

These are the known issues and workarounds for Delphix Engine Release 3.1 - 3.1.x.x
Release 3.1.3.0 Changes
Bug Fixes
Upgrading to Release 3.1.3.0
Release 3.1 Known Issues
Installation and Configuration Issues
Don't Change the Time Zone of the Delphix Engine
Solution
Host Checker Script Requirements
Linux Systems: Shared Memory Size and SGA_TARGET
Solution
HP-UX Systems: Cannot locate db Instances in a Custom SQL*Net Configuration
Solution
Delphix Engine Must be an Invited Node
Workaround
Archive Log Issues
Failure in Fetching Missing Archive Logs
Solution
Best Practice for Fetching Archive Logs
Online Redo Logs on Raw Devices
VDB and dSource Issues
Sample Schemas on Oracle 11.2 (11.2.0.1)
Workaround
Ulimits for the Linking or Provisioning User
Take New Snapshots after Changing Database Configuration Parameters
A Full Audit Directory Causes VDB Provisioning to Fail
Standby Database Support
Provisioning Can Fail if the _fix_control Parameter is Set in the Primary
Known issues in SQL Server Support
Source database upgrades
Provisioning to a higher SQL Server version if the source is SQL Server 2005
SQL Server 2005 databases with Full Text Catalogs
Running the manual recovery script after V2P

Release 3.1.3.0 Changes

Bug Fixes
Bug
Number

Description

24248

Creating cluster environment needs to ignore environments in namespaces

24339

Should not be allowed to resume initial load while the dSource is disabled.

24471

Confusing error message during Oracle cluster discovery when users have a database with duplicate db unique name in
another environment.

24528

delphix still tries to provision if the validate_host.sh script fails

24532

replication log spew at default level

24549

Cannot log in to the CLI via console when the stack is down

24618

Powering off Delphix Engine while snapsync is running causes zero blocks in datafiles

24622

incremental replication of SQL Server is slow

24

Delphix User Guide 2016 Delphix

24688

session stats dump with jmxtool

24689

replication throughput tracking

24694

IndexOutOfBoundsException when enabling a dSource after deleting its most recent snapshot

24707

sysadmin and delphix_admin are able to sftp into the delphix appliance

24714

recovery fails when we create a new datafile in a new subdir

24764

provisioning fails post 3.1.2. upgrade

24791

event init.ora parameter has incorrect quoting when provisioning VDBs

24804

Unable to provision VDB duplicate end points discovered on host

24833

Expand single thread dispatch to include policies that spawn jobs

24836

panic from dbuf_free_range() while doing a zfs receive

24840,25189

The Performance UI is completely blank.

24871

Space in the shared backup location breaks sync from existing backup

24879

JVM is consuming 100% of CPU on dlpx-scale1

24881

bad monitor requests filling log file

24888

Attaching dSource fails when source.name are not set

24890

VDB unavailable when failed to create control file.

24894

Multiple Workers for VDB Logsync prevents stack from coming up

24895

Initial load fails with ORA-01013

24922

Provisioning a vdb after upgrade fails with ORA-350

24952

Timeflowranges are asked for too aggressively

24962

VDB Refresh permissions in GUI should match permissions in backend

24965

ztest failure: assertion refcount_count(

24969

After upgrade 2.7.x to 3.0.6.0 no JDBC string works

24981

db_domain not used in JDBC connection entry when using wildcard notation in VDB config

24988

GUI object filtering based on search string

24999

IntroView can be very slow when gui starts up

25000

DatabaseNavView takes a lot of time at startup time

25001

Performance: Replication Spec Component calls way many invalidations

25012

Incremental replication failed on longevity java.io.FileNotFoundException

25050

SQL Server Linking from Environment Management screen does not select the database

25065

stmf_itl_task_start() must check for ilu->ilu_kstat_io is non-null

25066

Possible memory leak in the iSCSI code

25067

stmf_do_itl_dereg() has mysterious drv_usecwait(10)

25072

Refreshing the source environment gets rid of the LiteSpeed version on the source

25107

leaked hold from dmu_send_impl() if dump_bytes() fails

25108

zfs recv of a send -RD stream panics

25199

Oracle VDB snapshot fails with exception.oracle.vdb.snapshot.missing_archivelogs

25

Delphix User Guide 2016 Delphix

25381

Delphix VM shoots up to 100% utilization, with large number of UCP java threads spinning on locks

25465

Upgrade fails due to unlinked dSource with snapsync policy

Upgrading to Release 3.1.3.0

Upgrades to Release 3.1.3.0 are supported for Release 2.7.2.0 and above.
Delphix Customer Support will provide and install any patch or upgrade that is needed for an existing Delphix Engine installation.
All dSources must be suspended and VDBs shut down prior to an upgrade or patch.
Suspended or in-progress jobs will be removed, and cannot be resumed after upgrade is complete.

Release 3.1 Known Issues

Installation and Configuration Issues
Don't Change the Time Zone of the Delphix Engine
There is a known limitation with changing the time zone of the Delphix Engine after user data objects and snapshots have been created.
In particular, if the time zone is moved backward (e.g., Pacific Time to Hawaiian time), events and snapshots can appear out of order.
This limitation will be addressed in a future release.
Solution

Retain the original time zone specified during initial configuration.Source and Target Environment Issues

Host Checker Script Requirements

Running the Host Checker Script, chkHost.pl, requires Perl, and Java release 1.5.0_22 or higher.
Do not run chkHost.pl as the superuser (root). Run this script as the Oracle user.

Linux Systems: Shared Memory Size and SGA_TARGET

On Linux systems that are used as target hosts: before provisioning, compare the SGA_TARGET configuration parameter for the VDB with the
shared memory size in /dev/shm. The shared memory configured on the target host should match the SGA memory target. You can check the
value of the configuration parameter during the VDB provisioning process. In the Target Environment screen of the provisioning wizard, click the
Advanced link, and then scroll down to view the value of the parameter under DB Configuration. See Provisioning an Oracle VDB and Custo
mizing Oracle VDB Configuration Settings for more information.
Solution

If the size of SGA_TARGET is larger than /dev/shm, the administrator should reduce SGA_TARGET in the VDB configuration parameter, and save
a named template for use in provisioning other VDBs.
Alternatively, increase the /dev/shm size in /etc/fstab.

HP-UX Systems: Cannot locate db Instances in a Custom SQL*Net Configuration

When SQL*Net configuration files are not located in their standard location on the host, the Delphix Engine db_instance_inspector cannot
locate instances, including for provisioned VDBs.
The TNS_ADMIN environment variable is used to override the default location, usually $ORACLE_HOME/network/admin on UNIX hosts. On
many platforms, the Delphix toolkit is able to extract the TNS_ADMIN variable from running listener processes. On HP-UX, however, this is not
done as there's no public interface available for accomplishing this.
Solution

In some cases, it may be possible to add the TNS_ADMIN to the ssh environment that Delphix Engine uses:
1. Set PermitUserEnvironment to yes in sshd_config.
2.
26

Delphix User Guide 2016 Delphix

2. Restart sshd daemon

3. Add TNS_ADMIN=<loc> to ~/.ssh/environment for the respective OS user used by Delphix.

Delphix Engine Must be an Invited Node

If the network administrator has defined TCP.INVITED_NODES and TCP.VALIDNODE_CHECKING in $ORACLE_HOME/network/admin, make
sure that the IP address of the Delphix Engine is included in the list of invited nodes.
For example:
TCP.INVITED_NODES=(172.18.100.52,172.16.100.217)
TCP.VALIDNODE_CHECKING=yes
If Delphix Engine is not included in the list of invited nodes, there will be an error:
ORA-12537: TNS:connection closed
Workaround

Add the IP address of the Delphix Engine to the list of invited nodes in $ORACLE_HOME/network/admin.

Archive Log Issues

Failure in Fetching Missing Archive Logs
The "Fetch missing archive log" operation might fail if the target path (e.g. a path to the Flash Recovery Area) points to files that cannot be read
by the OS user given to Delphix Engine for dSource creation or VDB provisioning.
Solution

Make sure all files in the target path are readable by the OS user given to Delphix Engine.

Best Practice for Fetching Archive Logs

Instead of using the Repair tool to fetch missing logs automatically, create a temporary directory and copy the necessary logs (specified by the i
information icon) into the temporary directory. The Repair tool can then be pointed to that location and will repair the snapshot. This method is
much more efficient than using the Repair tool alone.

Online Redo Logs on Raw Devices

The LogSync feature is not available in Archive + Online Redo mode if your Oracle source database stores online redo logs on a raw device.
When adding a dSource choose the Archive Only mode for LogSync. For an existing dSource, the LogSync mode can be set on the back of the
dSource card.

VDB and dSource Issues

Sample Schemas on Oracle 11.2 (11.2.0.1)
If the Oracle examples that come with 11.2.0.1 are installed in your source database, Delphix Engine VDB provisioning produces a number of
error messages. No data loss is associated with these errors.
Workaround

Remove the Oracle sample schemas from the source database before provisioning VDBs.

Ulimits for the Linking or Provisioning User

If a non-Oracle install user is being used for either adding a dSource or provisioning VDBs, make sure that the ulimit settings for this user
match those for the Oracle install user on the remote host, and are sufficient to run Oracle instances.

Take New Snapshots after Changing Database Configuration Parameters

After changing a database configuration parameter on a VDB or dSource (such as setting db_16k_cache_size to support new 16KB block size
tablespaces), immediately take a snapshot to capture the new configuration parameters.

27

Delphix User Guide 2016 Delphix

A Full Audit Directory Causes VDB Provisioning to Fail

Delphix Engine sets the Oracle database parameter audit_trail setting to none and the audit_sys_operations parameter to false so
that VDB provisioning will not generate any audit files. However, VDB provisioning may still fail with ORA-09817 if the $ORACLE_HOME/rdbms/a
udit directory fills up.

Standby Database Support

Many prior limitations with linking physical standby databases have been lifted in the Delphix Engine 3.0 release. See Linking Oracle
Physical Standby Databases for details.

Provisioning Can Fail if the _fix_control Parameter is Set in the Primary

In some cases, the primary database has the undocumented _fix_Control parameter set as a result of patches applied on the primary that
have not been applied to the Oracle Home on the standby.
Where _fix_Control has been set on the primary but not on the standby, VDB provisioning can fail with an error from Oracle: 'ORA-00940:
invalid ALTER command.

Known issues in SQL Server Support

Source database upgrades
If a source database linked as a dSource gets upgraded to a higher SQL Server version, you will need to go through the standard upgrade
process outlined in Upgrading a dSource after a SQL Server Upgrade and perform a sync on the database after the upgrade.

Provisioning to a higher SQL Server version if the source is SQL Server 2005
If the source for a VDB is SQL Server 2005, then you can't provision to SQL Server 2008 or 2008R2 directly.

SQL Server 2005 databases with Full Text Catalogs

We currently don't support SQL Server 2005 databases with full text catalogs. This will be supported in a future release of the product.

Running the manual recovery script after V2P

Running the manual recovery script Provision.ps1 after V2P may receive the following error message:
The term 'dlpxzfree' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

This is because the utility dlpxzfree.exe is not in path. It does not affect the execution and functionality of the
script.
This error message will not be shown in a future release of the product.

28

Delphix User Guide 2016 Delphix

Release 3.2 - 3.2.x.x Known Issues and Changes

These are the known issues, workarounds, and changes for Delphix Engine Release 3.2 - 3.2.x.x
Release 3.2.7.0 Changes
Bug Fixes
Upgrading to Release 3.2.7.0
Upgrading MS SQL Server dSources
Upgrading with Replication
Release 3.2.6.0 Changes
Bug Fixes
Release 3.2.5.1 Changes
Bug Fixes
Release 3.2.5.0 Changes
Bug Fixes
Release 3.2.4.2 Changes
Bug Fixes
Release 3.2.4.1 Changes
Bug Fixes
Release 3.2.4.0 Changes
Bug Fixes
Release 3.2.3.1 Changes
Bug Fixes
Release 3.2.3.0 Changes
Release 3.2.2.1 Changes
Bug Fixes
Release 3.2.2.0 Changes
Bug Fixes
Release 3.2.1.0 Changes
Bug Fixes
Release 3.2.0.0 Changes
Release 3.2 Known Issues
Installation and Configuration Issues
Don't Change the Time Zone of the Delphix Engine
Workaround
Host Checker Script Requirements
Linux Systems: Shared Memory Size and SGA_TARGET
Solution
HP-UX Systems: Cannot locate db Instances in a Custom SQL*Net Configuration
Solution
Delphix Engine Must be an Invited Node
Workaround
Archive Log Issues
Failure in Fetching Missing Archive Logs
Solution
Best Practice for Fetching Archive Logs
Online Redo Logs on Raw Devices
VDB and dSource Issues
Sample Schemas on Oracle 11.2 (11.2.0.1)
Workaround
Ulimits for the Linking or Provisioning User
Take New Snapshots after Changing Database Configuration Parameters
A Full Audit Directory Causes VDB Provisioning to Fail
Standby Database Support
Provisioning Can Fail if the _fix_control Parameter is Set in the Primary
Known issues in SQL Server Support
Source database upgrades
Provisioning to a higher SQL Server version if the source is SQL Server 2005
SQL Server 2005 databases with Full Text Catalogs

29

Delphix User Guide 2016 Delphix

Running the manual recovery script after V2P

Single Quotation Marks (') in File Names and File Paths

Release 3.2.7.0 Changes

Bug Fixes
Bug Number

Description

26227 28456 31134 31134 31135 31136 31137 31220 31221 31223 31226 31226 31461
32266 32268 32269 32342 32290

MSSQL fixes and improvements

28456 29555 29792 29861 31694 30110 31573

Snapsync fixes and improvements

31142

Security fix

31153

Support for 12 character SIDs on Oracle

31908

Fix an issue where the Delphix Engine

management service could hang

31989

Performance fix for cached reads

Upgrading to Release 3.2.7.0

Upgrades to Release 3.2.7.0 are supported for Release 3.0.1.0 and above.
Delphix Customer Support will provide and install any patch or upgrade that is needed for an existing Delphix Engine installation.
All dSources must be suspended and VDBs shut down prior to an upgrade or patch.
Suspended or in-progress jobs will be removed, and cannot be resumed after upgrade is complete.

Upgrading MS SQL Server dSources

After upgrade to 3.2, a new snapshot must be taken on any MS SQL Server dSources with no snapshots or dSources that are under
replication. Until a new snapshot is taken disabling the dSource will fail.

Upgrading with Replication

In 3.2, authentication to the replication target no longer uses NDMP user credentials. This requires the user to manually update an
existing replication configuration on the replication source with a desired Delphix user with admin privileges on the replication target
after upgrade.
Replication is configured through the System > Replication screen (or replication spec in the CLI). Under Replication Target
Settings make sure you set the username and password to a user that has admin privileges on the target.

Release 3.2.6.0 Changes

Bug Fixes
Bug Number

Description

26741, 27779, 30748

Fixes for database delete on SQL Server

28221

Fixed a GUI issue when adding LUNs

30812, 30576

Replication fixes

30

Delphix User Guide 2016 Delphix

30763

Fixed an issue where provisioning a single instance dSource to a RAC target would fail

30617

Fixed an issue where rollback of a VDB would fail with RMAN-07517

30450

Fixed an issue with CLI validation of non-sys user fields fails on existing valid connection string

30412

Lowered the frequency of notifications requested by the GUI

30366

Fixed a GUI issue related to unlinked SQL Server dSources

30161

Fixed an issue where the management stack could run out of memory

29964

Fixed an issue with displaying times and SCNs from the latest archive logs

29960

Fixed an issue with the test JDBC connectivity API

29905

Improved error messages

29850, 30552

Windows connector fixes

29698

Fixed an issue where point-in-time provisioning to a bookmark would fail

28622, 30027

Fixed issues with scroll bars in the GUI

29373

Fixed an issue with icons on the capacity screen

Release 3.2.5.1 Changes

Bug Fixes
Bug Number

Description

29978

Fixes an issue related to Oracle standby database where datafiles are added during a dSource SnapSync

30109

Fixes an issue where connecting to a VDB (created from a standby dSource) fails when using a non-sys user

30147

Fixed an issue where provision from the last SCN of a dSource (created from a standby database) might fail

30148

Increases a timeout for starting up a VDB

30149

Fixes an issue where provision may fail when using file mapping when mapping with a large # of datafiles with long names

30245

Fixes an issue where the VDB status is shown as unknown on Solaris and HP-UX platforms.

Release 3.2.5.0 Changes

Bug Fixes
Bug Number

Description

29499

Fixed an issue with SQL Server VDBs not starting automatically following a reboot of the target host.

29991, 29758, 29853,

29854, 29855

VDBs are now stopped at 95% of storage capacity and automatically restarted once storage capacity drops below
90%.
dSources will stop pulling new data from sources at 85%. Once the usage goes below 82%, we will resume pulling
data again.

29359

Fixed an issue with iSCSI target being offlined due to task abort timeouts

29662

Fixed an issue with retention policy execution sometimes resulting in fault.policy.log.retention.old.snapshot

29156

Fixed a problem where you would get exception.oracle.dbc.query.failed during SnapSync if v$rman_configuration
has more than one entry for snapshot controlfile

29050, 29049

Fixed user permissions related issues

31

Delphix User Guide 2016 Delphix

29539

Fixed an issue where a running job would not be recorded in job history

29881, 29696

Fixed a issues with logfile retention related to multiple TimeFlows

28972, 29657, 29686,

29688

Fixes to address naming and structure of Oracle data files and temp files

30010

Fixed an issue where RAC VDB rollback would fail due to "Failed to apply logs in database recovery"

27633, 29540

Fixed issues that could result in ORA-00600 during provisioning

29207

Fixed a GUI issue where updating the source database user credential from the dSource cards could give an error
message

29687

Fix to workaround Oracle note 387210.1 which restricts the value of MAXLOGHISTORY on Oracle versions
10.2-10.2.0.0 ans 11.1-11.1.0.6

29321

Fixed a GUI issue with updating the target principal of an existing replication configuration

29697

Fixed an issue where VDB log retention could fail to delete a log

27478, 27388

Fixed issues with setting the prefix length of an static addresses

29584, 29566, 28998,

28598

Performance improvements

28540, 28541, 29426

Improved error messages

29274, 29275,

Improvements to No Open Resetlogs VDBs

Release 3.2.4.2 Changes

Bug Fixes
Bug Number

Description

29386

Fixed an issue where SnapSync would fail

29273

Fixed an issue where certain characters in VDB config templates would cause provisioning failures

Release 3.2.4.1 Changes

Bug Fixes
Bug Number

Description

29301

Fixed an issue where replication would unexpectedly fail

29286

Improved performance when provisioning when RAC is enabled

Release 3.2.4.0 Changes

Bug Fixes
Bug Number

Description

29100

SQL Server VDB status now monitors more states

28707

Fixed an issue with SQL Server LogSync where provisioning needed the stopat to be in the source's
timezone

28474

Improved performance of VDB snapshots under load

28962

Fixed an issue where Pre-Provisioning against a standby would generate an error

32

Delphix User Guide 2016 Delphix

28904

Provision a VDB from a standby should allow the user to specify a non-SYS user

28821

Fixed an upgrade where VDBs would not start after upgrade

28741, 28742

Improved error messages related to VDB startup

28466

Fixed an issue where RAC discovery would fail

28870, 28894

Snapshot control file on non-ASM path now supported

28934

Fixed an issue where the management stack could run out of memory

28916

Fixed an issue where the GUI could disable the staging source instead of the linked source

28867

Fixed an issue where the database management screen would display garbled data

28684

Fixed an issue where the GUI's might not handle timezones with half hour offsets properly

28878

Fixed an issue where NotificationDrop objects got sent to old clients

28780, 28792, 29058, 29082,

28479

Delphix Session Protocol Enhancements

28779

Replication performance improvements

28526

Fixed an issue where upgrade would fail

Release 3.2.3.1 Changes

Bug Fixes
Bug Number

Description

28559, 28050

Fixed issues related to SQL Server environment timezones

Release 3.2.3.0 Changes

Bug Fixes
Bug Number

Description

28435

Fixed an issue with the GUI could show an action script error during the provisioning wizard

28364, 28373

Fixed issues related to block formatting during SnapSync

28261

SQL Server now supports backup paths which include $ and ' characters

28208

Fixed an issue when failing over a replicated Windows host

28160, 27881

Object notification enhancements

28085, 28077, 27931

Fixed security issues

27953

Fixed an issue where an exception would be raised in some cases when detecting database privileges

27926

Fixed an issue with attaching a VDB on SQL Server

27892

Fixed an issue where Delphix would pick the incorrect archive logs, causing provisioning to fail

27827

Fixed an issue where stopping the auth service would fail

27789

Monitor SQL Server VDBs to check if new data/log files have been added to non-Delphix storage

27738

Fixed an issue where Environment Management does not show correct version for SQL Server environment

27737

Fixed an issue where environment discovery would not identify disk space problem

27736

Fixed an issue with umask requirements when not using Oracle user

33

Delphix User Guide 2016 Delphix

27652, 26880, 26879

Fixed issues with LogSync and usage of archive logs

27484

Fixed an issue where VDB enable would fail if the file list changed since the last snapshot

27432, 27386

Fixed problems related to iSCSI initiator IQN uniqueness

26951

Fixed an issue where system under extreme load could run out of heap space

Release 3.2.2.1 Changes

Bug Fixes
Bug Number

Description

28186

Fixed an issue with provisioning from VDB snapshots created in Delphix 2.7.x or earlier

27808

Fixed an issue when upgrading with domain and system users with the same name

Release 3.2.2.0 Changes

Added support for Red Hat Enterprise Linux version 6.3 and 6.4

Bug Fixes
Bug Number

Description

27810

Fixed an issue with high SCNs having an incorrect range

27808

Performance improvement when provisioning VDBs from VDBs

27770, 27750,
27613

Fixed an issue where log retention on Windows did not free up space

27657

Fixed an issue where ORA-01152 error messages during provisioning would incorrectly display warnings

27636

Fixed an issue when doing initial load from an Oracle 9i database would fail

27624

Fixed an issue where the Delphix Engine could crash while receiving a replication update

27616

Fixed an issue with the SCN End stamp not displaying when taking a snapshot

27595

Fixed an issue where cached browser data could cause incorrect strings to be displayed in the GUI after upgrading a
Delphix Engine

27582

Fixed an issue where resource monitor workers where not removed when restarting the management stack

27530

Destination port is now configurable for replication

27492

Fixed an issue where SQL Server pre-provisioning fails if a file is renamed on the source

27449

Fixed an issue where tab navigation skips "Toolkit Path" when adding "Standalone Host" in the "Add Environment" wizard

27445, 27208

Fixed an issue where an initial load does not generate a fault on a NOLOGGING operation

27443

Fixed an issue with not properly checking for X$KCCFE privileges on source databases

27420

Fixed an issue with deleting a namespace after replication failover when doing circular replication

27353

Fixed an issue where provisioning from SQL Server 2005 to SQL Server 2008 would be allowed

27261

Fixed an issue where the GUI would no longer require the email address to be set for delphix_admin

27230

Fixed an issue with the SCN range not displaying correctly on snapshots

26423

Fixed an issue where upgrading the staging instance would not be properly detected

34

Delphix User Guide 2016 Delphix

24037

Fixed an issue when multiple SQL files with has the same physical file name

Release 3.2.1.0 Changes

Bug Fixes
Release 3.2.1.0 contains a fix for Internet Explorer running in IE7 compatibility mode not working with the Delphix GUI among several other fixes.

Release 3.2.0.0 Changes

The Dashboard button has moved from the center of the upper page to 'Manage->Dashboards'.
The Enabled/Disabled slider has moved to the back of the dSource and VDB cards.
There is a new way to set up the initial network config, which is detailed upon first log in or at Setting Up Network Access to the
Delphix Engine.
The limit on the number of snapshots that can be retrieved by the GUI has been lifted from 250 to 1500.
It is now possible to refresh a VDB that is a parent of other VDBs. The children VDBs are not affected by the refresh.

Release 3.2 Known Issues

Installation and Configuration Issues
Don't Change the Time Zone of the Delphix Engine
There is a known limitation with changing the time zone of the Delphix Engine after user data objects and snapshots have been created.
In particular, if the time zone is moved backward (e.g., Pacific Time to Hawaiian time), events and snapshots can appear out of order.
This limitation will be addressed in a future release.
Workaround

Retain the original time zone specified during initial configuration.Source and Target Environment Issues

Host Checker Script Requirements

Running the Host Checker Script, chkHost.pl, requires Perl, and Java release 1.5.0_22 or higher.
Do not run chkHost.pl as the superuser (root). Run this script as the Oracle user.

Linux Systems: Shared Memory Size and SGA_TARGET

On Linux systems that are used as target hosts: before provisioning, compare the SGA_TARGET configuration parameter for the VDB with the
shared memory size in /dev/shm. The shared memory configured on the target host should match the SGA memory target. You can check the
value of the configuration parameter during the VDB provisioning process. In the Target Environment screen of the provisioning wizard, click the
Advanced link, and then scroll down to view the value of the parameter under DB Configuration. See Provisioning an Oracle VDB and Custo
mizing Oracle VDB Configuration Settings for more information.
Solution

If the size of SGA_TARGET is larger than /dev/shm, the administrator should reduce SGA_TARGET in the VDB configuration parameter, and save
a named template for use in provisioning other VDBs.
Alternatively, increase the /dev/shm size in /etc/fstab.

HP-UX Systems: Cannot locate db Instances in a Custom SQL*Net Configuration

When SQL*Net configuration files are not located in their standard location on the host, the Delphix Engine db_instance_inspector cannot
locate instances, including for provisioned VDBs.
The TNS_ADMIN environment variable is used to override the default location, usually $ORACLE_HOME/network/admin on UNIX hosts. On
many platforms, the Delphix toolkit is able to extract the TNS_ADMIN variable from running listener processes. On HP-UX, however, this is not
done as there's no public interface available for accomplishing this.

35

Delphix User Guide 2016 Delphix

Solution

In some cases, it may be possible to add the TNS_ADMIN to the ssh environment that Delphix Engine uses:
1. Set PermitUserEnvironment to yes in sshd_config.
2. Restart sshd daemon
3. Add TNS_ADMIN=<loc> to ~/.ssh/environment for the respective OS user used by Delphix.

Delphix Engine Must be an Invited Node

If the network administrator has defined TCP.INVITED_NODES and TCP.VALIDNODE_CHECKING in $ORACLE_HOME/network/admin, make
sure that the IP address of the Delphix Engine is included in the list of invited nodes.
For example:
TCP.INVITED_NODES=(172.18.100.52,172.16.100.217)
TCP.VALIDNODE_CHECKING=yes
If Delphix Engine is not included in the list of invited nodes, there will be an error:
ORA-12537: TNS:connection closed
Workaround

Add the IP address of the Delphix Engine to the list of invited nodes in $ORACLE_HOME/network/admin.

Archive Log Issues

Failure in Fetching Missing Archive Logs
The "Fetch missing archive log" operation might fail if the target path (e.g. a path to the Flash Recovery Area) points to files that cannot be read
by the OS user given to Delphix Engine for dSource creation or VDB provisioning.
Solution

Make sure all files in the target path are readable by the OS user given to Delphix Engine.

Best Practice for Fetching Archive Logs

Instead of using the Repair tool to fetch missing logs automatically, create a temporary directory and copy the necessary logs (specified by the i
information icon) into the temporary directory. The Repair tool can then be pointed to that location and will repair the snapshot. This method is
much more efficient than using the Repair tool alone.

Online Redo Logs on Raw Devices

The LogSync feature is not available in Archive + Online Redo mode if your Oracle source database stores online redo logs on a raw device.
When adding a dSource choose the Archive Only mode for LogSync. For an existing dSource, the LogSync mode can be set on the back of the
dSource card.

VDB and dSource Issues

Sample Schemas on Oracle 11.2 (11.2.0.1)
If the Oracle examples that come with 11.2.0.1 are installed in your source database, Delphix Engine VDB provisioning produces a number of
error messages. No data loss is associated with these errors.
Workaround

Remove the Oracle sample schemas from the source database before provisioning VDBs.

Ulimits for the Linking or Provisioning User

If a non-Oracle install user is being used for either adding a dSource or provisioning VDBs, make sure that the ulimit settings for this user
match those for the Oracle install user on the remote host, and are sufficient to run Oracle instances.

36

Delphix User Guide 2016 Delphix

Take New Snapshots after Changing Database Configuration Parameters

After changing a database configuration parameter on a VDB or dSource (such as setting db_16k_cache_size to support new 16KB block size
tablespaces), immediately take a snapshot to capture the new configuration parameters.

A Full Audit Directory Causes VDB Provisioning to Fail

Delphix Engine sets the Oracle database parameter audit_trail setting to none and the audit_sys_operations parameter to false so
that VDB provisioning will not generate any audit files. However, VDB provisioning may still fail with ORA-09817 if the $ORACLE_HOME/rdbms/a
udit directory fills up.

Standby Database Support

Many prior limitations with linking physical standby databases have been lifted in the Delphix Engine 3.0 release. See Linking Oracle
Standby Databases for details.

Provisioning Can Fail if the _fix_control Parameter is Set in the Primary

In some cases, the primary database has the undocumented _fix_Control parameter set as a result of patches applied on the primary that
have not been applied to the Oracle Home on the standby.
Where _fix_Control has been set on the primary but not on the standby, VDB provisioning can fail with an error from Oracle: 'ORA-00940:
invalid ALTER command.

Known issues in SQL Server Support

Source database upgrades
If a source database linked as a dSource gets upgraded to a higher SQL Server version, you will need to go through the standard upgrade
process outlined in Upgrading a dSource after a SQL Server Upgrade and perform a sync on the database after the upgrade.

Provisioning to a higher SQL Server version if the source is SQL Server 2005
If the source for a VDB is SQL Server 2005, then you can't provision to SQL Server 2008 or 2008R2 directly.

SQL Server 2005 databases with Full Text Catalogs

We currently don't support SQL Server 2005 databases with full text catalogs. This will be supported in a future release of the product.

Running the manual recovery script after V2P

Currently running the manual recovery script Provision.ps1 after V2P may get the following error message:
The term 'dlpxzfree' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

This is because the utility dlpxzfree.exe is not in path. It does not affect the execution and functionality of the
script.
This error message will not be shown in a future release of the product.
Single Quotation Marks (') in File Names and File Paths
We currently don't support single quotation marks (') used in Delphix connector installation paths and database backup file names and paths.

37

Delphix User Guide 2016 Delphix

Release 4.0 - 4.0.x.x Known Issues and Changes

These are the known issues, workarounds, and changes for Delphix Engine Release 4.0 - 4.0.x.x
Release 4.0.6.1 Changes
Management Service Fixes
Release 4.0.6.0 Changes
Management Service Fixes
Release 4.0.5.0 Changes
Management Service Fixes
DelphixOS Fixes
Release 4.0.4.0 Changes
Amazon EC2 Support
Bug Fixes
Release 4.0.3.0 Changes
Bug Fixes
Release 4.0.2.0 Changes
Bug Fixes
Release 4.0.1.0 Changes
Bug Fixes
Release 4.0.0.1 Changes
Bug Fixes
Release 4.0.0.0 Changes
Release 4.0 Known Issues
Cross-Platform Provisioning Issues
Replica Provisioning Fails
VDB Refresh Takes a Long Time
Application Data Issues (EBS and Unstructured File Virtualization)
Detach of a dSource Fails
Oracle RAC Environments Not Supported
SQL Server Issues
Issues With Upgrades From Delphix 3.1
Issues With Upgrades From Delphix 3.2.3.0 or Older
PostgreSQL Issues
Replication is not Supported
Staging Environment Reboot Not Handled Correctly
Issues With Hooks
Script Output Not Included in Job Information
Performance Analytics Issues
Network Interface Statistics Occasionally Contain Invalid Values
Other Issues
Spurious Job in the Job History

Release 4.0.6.1 Changes

Management Service Fixes
Bug Number

Description

37126

Delphix Engine fails to boot following deferred OS upgrade from 4.0.3.0 or later

36983

restarting a canceled or suspended initial SnapSync does not resume from where it left off

37149

internal metadata database race condition may cause failure during upgrade from 3.1 or 3.2

Release 4.0.6.0 Changes

38

Delphix User Guide 2016 Delphix

Management Service Fixes

Bug Number

Description

32231

no input validation for timeflowPoint.location when creating bookmark, results in server error when rolling back to bookmark

32232

bookmark filter by database is ignored

32233

duplicate Bookmarks names for the same dSource time flow can be erroneously created

32457

SQL Server SnapSync performance improvement

33449

Delphix Engine may not come up if restarted during replication

35602

recovery errors during Oracle VDB provisioning

35605

$ character in SQL Server passwords results in inability to determine recovery model

35780

switchover to standby with Oracle flashback can result in duplicate snapshots displayed in Delphix Engine GUI

35989

address possible internal error during upgrade from 3.1 or 3.2

36087

fix possible resource leak if an error occurs at the start of replication

36231

internal server error if invalid input is provided to xpp/defaults API

36235

newly provisioned Oracle VDB may have no snapshot

36244

source continuity for Oracle dSources (allow SnapSync to continue after source is rolled back)

36284

provide mechanism to purge unusable Oracle logs

36412

admin email address can accidentally get set to null

36462

shutdown of an Oracle VDB with LogSync enabled can cause SCN gaps in timeflow

36497

SQL Server Post-Scripts for VDBs run as incorrect user

36736

Oracle v2p fails with large number of datafiles

Release 4.0.5.0 Changes

Management Service Fixes
Bug Number

Description

35961,36089

Delphix Engine metadata can be corrupted when the system is restarted (see technical bulletin
)

35554

ASM source datafiles can be deleted when provisioning a VDB back to a source environment (see technical bulletin)

33451

enable the configuration of SNMP TRAP instead of INFORM for Delphix alerts to workaround environments where
TRAPs are not acknowledged

34030

SQLServer VDB refresh fails with a server error

35045,35449

fix a possible upgrade issue with Delphix Engines that have SQLServer dSources or VDBs

34220

GUI not rendering sources and groups properly after having popped up an error dialog

34332

cannot delete a VDB template when the template name is too long

35381

faults count on the menu bar does not matches the faults count in the active faults list

35466

add a scroll bar to the active jobs tab

35491

user alerted of a fault but the GUI faults list is empty

35540

increase SnapSync policy timeout limit from 24 hours to 168 hours (1 week)

39

Delphix User Guide 2016 Delphix

35701

blank error popups sometimes displayed and eventually result in runtime exceptions

35704

GUI does not show error message when VDB provisioning fails due to a mount failure

35712

unable to set the SnapSync policy timeout to 0 using the GUI

34888

network outage can cause Oracle V2P job to fail with a server error

34884

canceling an Oracle V2P job hangs if the host is unreachable

34584

Oracle logsync can erroneously start fetching old logs resulting in missing log alerts

35439

Delphix Engine can generate a flood of alert emails if an alert profile contains an invalid email address

34786

analytics disk IO section is empty on IE 8 when Read or Write is selected

34471

unable to disable VDB when environment is unavailable

34583

the Finish and Back buttons do not work when provision a replicated VDB

35400

unable to scroll to bottom of environment list after 4.0.3.0 upgrade

35402,35488,35489

miscellaneous GUI fixes for faults

32735

filtering by job type does not work for certain values

35312

DSP performance improvement (impacts SnapSync, replication, and Oracle Export)

34766

Delphix Engine upgrade can fail if incremental SnapSync job is in progress

33717

Oracle VDB provisioning via CLI uses a listener from the wrong environment

34851

Oracle RAC attachSource failing with snapshot control file must be accessible to all nodes

35713

add the ability to launch a job via policy with no time limit

35044

the Delphix Management Service is not automatically restarted if it fails

DelphixOS Fixes
Bug Number

Description

33924

TCP performance problem causing low throughput for connections traversing one or more routers

35174

upgrade openssl to 1.0.1h (security advisory)

Release 4.0.4.0 Changes

Amazon EC2 Support
As the basis for the Delphix Compliance Engine, version 4.0.4.0 adds support for the Amazon EC2 platform.

Bug Fixes
Bug Number

Description

34716

upgrade Tomcat to version 7.0.53

35012, 35018

stop exporting a writable /public filesystem

Release 4.0.3.0 Changes

Bug Fixes

40

Delphix User Guide 2016 Delphix

Bug Number

Description

32600

alert sysadmin when logfile storage runs out of space

32952

add option to disable non-LDAP users

32955

mechanism for limiting which IP addresses are reachable via ssh

33306

infinite loop when enumerating storage devices

33338

GUI: vFiles migrate button should be enabled when vFiles is disabled

33351

runtime exception when migrating vFiles

33607, 33965

support for Compliance Engine

33652

renaming database files during provisioning can result in enqueue timeout

33686

"object already exists" error when failing over appdata with builtin toolkit

33788

Oracle logsync can fail with an internal error after upgrade to 4.0

33837

allow user with 'sudo mount' to be different from owner of provisioned appdata files

33864

non domain admin users don't get prompt back when they issue a DB_DELETE job (last notification does not arrive)

33903

internal error trying to provision appdata to s10 target because id doesn't support -u option

33904

cli error assigning an authorization on a target in a namespace

33937

updating AppData VDB parameters on vFiles card in GUI overwrites password with "******"

33978

need to preserve case when editing and saving VDB config template contents

33989

EBS toolkit PATH should include /usr/ccs/bin

34058

after the currently selected VDB Template is saved, it should always be auto-refreshed

34059

GUI: problem editing a VDB template while creating a VDB

34064

storage device notifications posted before device cache set

34073

support for BoKS in target environments

34075

dSource name is shown instead of VDB name in Refresh VDB confirmation dialog

34388

updating hook operations on appdata in GUI fails with internal error

34427

EBS-app toolkit missing expect logic for db domain name, file system owner and startup

34509

stack-only upgrade

Release 4.0.2.0 Changes

Bug Fixes
Bug
Number

Description

31280

problem creating two bookmarks with the same name

31454

improve efficiency of SQL query used by Oracle logsync

31695

container update notifications not being sent for enabling or disabling of Oracle dSources

32053

handle Postgres staging environment reboots

32059

cannot add an environment if it contains an Oracle database whose db_unique_name is equal to an existing dSource

32061

Delphix Engine now drops all IP packets containing source routes

41

Delphix User Guide 2016 Delphix

32063

explicitly set the anon option on nfs shares

32420

fix out-of-range issue when upgrading from 3.2.3.0 or older and SQL Server environments are in different timezones than the
Delphix Engine

32593

XPP log file path is displayed incorrectly in faults

32703

fix a panic in DxFS

32733

allow user to pick staging environment for replica XPP

32862

add support for Postgres replica provisioning

32973

collapsed groups spontaneously expand after 30-60 seconds

32992

expanding a group or container details should not expand any group folder

32994

add support for linux systems without stdbuf

33002

VDB migration fails when parent's archive logs have been removed

33072

can't start SQL Server VDB after upgrading with the VDB in a stopped state

33129

add support for hosts configured with Etc timezone format

33209

snapsync can fail with an internal error when linking to an Oracle database on AIX

33251

unable to disable VDB when its database on MSSQL does not exist

33252

add a delayed retry to SQL Server transaction log pickup before generating an alert

33352

renaming a group causes its folder to automatically expand

33373

fix GUI memory leaks

33388

grant permissions to SQL server instance owner during VDB enable

33389

unable to refresh SQL Server host - object already exists

Release 4.0.1.0 Changes

Bug Fixes
Bug Number

Description

31278

missing container name in the "add dSource" wizard

31279

GUI rendering issue when a long VDB note is used

31281

cross-platform provisioning from a replicated dSource

31392

restart SQL Server VDBs in RECOVERY_PENDING state following a target reboot

31398

fix a problem with RECOVERY_PENDING SQL Server VDBs not being restarted after a target reboot

31459

retention policy should use last change time instead of creation time for calculating snapshot retention eligibility

31648

hostchecker doesn't print an error if inventory.xml has the wrong permissions

31649

hostchecker should not query for BCT when Oracle version is 9.X

31650

hostchecker crashes if Oracle oratab does not exist

31687

analytics screen disk I/O graph loses its lower summary row when selecting a specific latency range

31728

hostchecker erroneously reports that Oracle may not be functioning properly

31754

disabling or enabling a system user is not reflected in the GUI until the browser is refreshed

31825

cannot manage both Postgres and SQL Server dSources from the GUI

42

Delphix User Guide 2016 Delphix

32042

internal error during cross-platform provisioning due to a lower-case tablespace name

32110

'excludes' and 'followSymlinks' properties of AppDataLinkParameters do not appear in CLI while linking

32115

spurious jobs are executed as part of the management stack startup

32129

the capacity graph displays inconsistent data

32151

internal error during cross-platform provisioning

32188

errors during the export phase of cross-platform provisioning are not displayed

32227

reduce CPU impact of SQL command run on Oracle targets used to discover database user privileges

32250

cross-platform provisioning fails if the database has an offline datafile

32305

fix for point-in-time provisioning from a replicated Postgres dSource

32306

vfiles source is erroneously disabled following a failed provisioning job

32362

cross-platform provisioning user script is not replicated

32376

SQL Server snapshot corruption occurs if a source is disabled before Delphix Engine upgrade

32413

snapsync performance improvement

32435

failure provisioning an Oracle VDB if the source contains a datafile with spaces in the filename

32508

cross-platform provisioning experiences internal error if user script output is less than 256 characters

32512

network interface analytics graph doubles throughput and packet counts

32525

analytics screen cosmetic improvements

32526

analytics screen cosmetic improvements

32527

network interface analytics graph vertical axis scale is too large

32528

navigating on the analytics timeline erases graph data from the screen

32537

fix for Postgres point-in-time provisioning after replication

32614

GUI support for additional mount points for vfiles

32644

cross-platform provisioning does not save storage space

32704

scalability issue in the GUI that caused "Flash plugin not responding" popups in the browser

32766

GUI can become unresponsive for minutes after login

32858

fix for a Delphix Engine memory leak

32859

support for Oracle RAC to single instance in the EBS toolkit

32873

run adpreclone in the pre-snapshot EBS toolkit hook

32875

provide default values for EBS toolkit parameters

Release 4.0.0.1 Changes

Bug Fixes
Bug Number

Description

32755

fix for an OS panic in DxFS

Release 4.0.0.0 Changes

Delphix network services are increasingly using the Delphix Session Protocol. In this release, SnapSync, V2P, and the Unix Connector

43

Delphix User Guide 2016 Delphix

(used to run Oracle and Postgres hooks) have been re-architected use the protocol. This places new network connectivity requirements
on the product and the hosts that interact with Delphix Engines. See Network and Connectivity Requirements section of the
documentation for details.
VDB Pre/Post-Scripts have been superseded by the new Hook Operations feature. Any post-scripts configured on existing VDB will
automatically be converted to Configure Clone hook operations as part of the upgrade to 4.0. Pre-scripts are no longer supported and will
be removed on upgrade.
Delphix Engine upgrade images are now signed by Delphix, and signatures are verified prior to upgrade. This ensures that only updates
authorized by Delphix can be applied to a Delphix Engine.
The Oracle and PostgreSQL VDB provisioning wizard includes a screen for configuring user-defined hooks to be run during specified
VDB operations. See the documentation for further details.
A summary of storage capacity metrics is now displayed on the main screen after login.
Most of the performance monitoring functionality that was previously accessible via the Performance screen has been re-implemented
and moved to the new Performance Analytics screen.
New advanced data management options are available from the Oracle dSource wizard. See the documentation for further details.
Policies may now be expressed using cron format. The Delphix Engine uses expressions compatible with the Quartz CronTrigger
scheduler.
New VDB Configuration Templates GUI screen.

Release 4.0 Known Issues

Cross-Platform Provisioning Issues
Replica Provisioning Fails

Doing cross-platform provisioning of a VDB from a replicated dSource fails with an internal error. To work around this, create a VDB of the
replicated dSource, and do a cross-platform provision of the VDB.
VDB Refresh Takes a Long Time

The time taken to refresh of a cross-platform provisioned VDB is similar to the time taken for cross-platform provisioning. This is because the
refresh process re-provisions the VDB, including much of the cross-platform provisioning logic. We are investigating how to improve this in a
future release.

Application Data Issues (EBS and Unstructured File Virtualization)

Detach of a dSource Fails

Detaching an Application Data dSource fails with an internal error. There is no workaround.
Oracle RAC Environments Not Supported

Application data repositories cannot currently be created in Oracle RAC environments.

SQL Server Issues

Issues With Upgrades From Delphix 3.1

If any dSource is disabled prior to upgrade and enabled after upgrade the following issues are seen:
Validated sync might fail with a fault stating that the most recent transaction log failed to be restored.
Even if validated sync succeeds, provisioning a VDB from a snapshot after the upgrade will fail with an internal error as the VDB cannot
be recovered. Provisioning from any snapshot taken prior to upgrade continues to work.
If a dSource is disabled after the upgrade, the subsequent enable can fail with an error stating that the dSource could not be enabled as
the corresponding staging source could not be enabled.
This can be resolved by doing a sync on the dSource after the upgrade.
Issues With Upgrades From Delphix 3.2.3.0 or Older

If the source host and Delphix Engine are in separate timezones provisioning VDBs after upgrade from snapshots taken before upgrade may fail
with timestamp out of range errors. Provisioning from snapshots taken after upgrade works correctly.

44

Delphix User Guide 2016 Delphix

PostgreSQL Issues
Replication is not Supported

There are some problems associated with provisioning a VDB from a replicated PostgreSQL dSource. Replication is not yet fully supported with
PostgreSQL.
Staging Environment Reboot Not Handled Correctly

If a staging environment is rebooted, the pg_receivexlog process starts writing log files to the local filesystem instead of the NFS directory
mounted from Delphix. This results in missing logs, and the inability to re-enable the staging environment after it has been disabled.

Issues With Hooks

Script Output Not Included in Job Information

The output of user scripts is not included in the job information unless the script fails (exits with a non-zero exit code). This can make it difficult to
diagnose problems with scripts if they are doing something unexpected but not failing.

Performance Analytics Issues

Network Interface Statistics Occasionally Contain Invalid Values

Statistics for network interface bytes/sec and packets/sec occasionally include invalid negative values. This is exhibited in the GUI as large spikes
in the respective graphs. This has only been observed on systems with multiple network interfaces.

Other Issues
Spurious Job in the Job History

When the Delphix Engine starts up, a spurious job is always run with summary, "Restore the application containers to a consistent state in the
event of a failure during an operation." This job is spurious and does not affect any system state. It can safely be ignored.

45

Delphix User Guide 2016 Delphix

Release 4.1 - 4.1.x.x Known Issues and Changes

These are the known issues and workaround for Delphix Engine release 4.1 - 4.1.x.x
Release 4.1.6.0 Changes
Management Server Fixes
Release 4.1.5.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.1.4.0 Changes
Management Server Fixes
Release 4.1.3.2 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.1.3.1 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.1.3.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.1.2.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.1.1.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.1.0.0 Changes
Release 4.1 Known Issues
Rebooting
Must Disable Performance Mode Before Rebooting
SAP ASE Issues
No Fine Grained Progress Monitoring
Must Disable "net password encryption reqd"
Point in time provisioning on ASE 12.5 is not supported
Oracle 12c Pluggable Database Issues
Cross-Platform Provisioning Issues
Source Validation First
Unsupported Oracle Features
VDB Refresh Takes a Long Time
Application Data for Windows Issues (Unstructured File Virtualization)
Toolkits and Hook Operations Not Yet Supported

Release 4.1.6.0 Changes

Management Server Fixes
Bug Number

Description

DLPX-34837

RMAN recovery should limit to use disk channels

DLPX-35993

Standby dSource has Missing Archive Logs Sequence {0}

DLPX-35671

Check for Oracle bug 13075226 fails on 11.2.0.3 with patch installed

DLPX-35672

Oracle snapsync prescript fails if the script returns successful status but stderr has content

DLPX-34581

450K+ executions of query ran in LogSync code in prod database

DLPX-35855

MSSQL provisioning with LogSync creates VDB with recovery model of FULL

46

Delphix User Guide 2016 Delphix

DLPX-35809

MSSQL pre-provisioning trying to open backup files in write mode

DLPX-35872

MSSQL Recovery model not set during V2P

DLPX-35746

Refactor iSCSI mount script to avoid running diskparts as much as possible

DLPX-35667

Handles to vds.exe increased because Diskpart doesn't call exit explicitly

DLPX-36015

Faults raised for recovered error - TLog was busy

DLPX-35668

ASE GUI does not set loadBackupServerName when Remote Backup Server selected

DLPX-34958

Deleting a container results in exception.executor.object.missing

DLPX-34824

RFE: see the template name on the back of the VDB card with a pencil for edit

DLPX-35888

Performance Management UI always shows no data

DLPX-32228

After applying a policy to a VDB or Group, the server need to notify the client of the changes

DLPX-35334

Waiting SNMP listener threads caused Delphix to run out of memory and hang

DLPX-32792

Replication manifests contain passwords

DLPX-35931

ReplicationMetadataReceiver cleanupNexus does not handle null nexus

DLPX-35358

ReplicationStreamScheduler should not store a reference to the manifest

DLPX-32985

RuntimeException constructed in SshExecSessionImpl.close

DLPX-34854

Need to rotate stdout.log

DLPX-29991

hs_err_pid files from java crashes are removed when stack restarts

DLPX-29992

RFE: capture hs_err_pid files in support logs bundle

DLPX-35484

MDS upgrade scripts for 4.1.5.0

DLPX-34865

Java core taken on OutOfMemory cannot be used for reference backtracing

DLPX-35948

Upgrade netty from 3.6.3 to 3.9.4

Release 4.1.5.0 Changes

Management Server Fixes
Bug
Number

Description

DLPX-32566

Can't create Jet Stream branch with latest data from the template

DLPX-32865

Jet Stream should replicate DVCBranchActivityDOs

DLPX-32585

Jet Stream LatestTime should always use SemanticTimeflowLocation.LATEST_POINT

DLPX-35304

test_add_and_delete_multiple_vdbs_concurrently fails due to exception.oracle.targetscripts.db.recovery during vPDB

provisioning

DLPX-31885

Creating a Jet Stream branch at now doesn't include latest changes on Oracle VDBs

DLPX-34757

concurrentRefreshOfContainersInSameTemplates Jet Stream unit test failure

DLPX-34649

Jet Stream should use rollback instead of refresh when appropriate

DLPX-34191

Jet Stream objects are not listed in web api page

DLPX-34414

Jet Stream only tracks initial timeflows of data template's data sources

DLPX-34390

Refactor Jet Stream time drift calculation for engine time API

DLPX-32565

Refactor Jet Stream TimelineParametersConverterImpl to be easier to understand

47

Delphix User Guide 2016 Delphix

DLPX-34117

Remove Oracle SnapSync reliance on RFN

DLPX-32958

Oracle SnapSync failure with NPE in updateProgressingDataFileState

DLPX-34620

Oracle SnapSync failed for read only datafile on dSource, regression introduced by fix for 34064 Remove SnapSync reliance on
RFN

DLPX-34396

Oracle SnapSync job stuck at zero percent complete, client Java in lwp_cond_wait

DLPX-31765

Oracle SnapSync fails when database has '_fix_control string 5909305:ON' set to non-null value

DLPX-33317

Handle special characters in drop restore point logic in doDisableFlashback.sh

DLPX-33122

Oracle 12c failed vPDB provision or failed vPDB enable due open vPDB failures are not handled, partially provisioned vPDB is
left around

DLPX-33121

get_pdb_status script function needs to validate if PDB is in RESTRICTED mode

DLPX-32991

NFS acl interferes with SAP archival process

DLPX-33320

Oracle purgeLogs not working as expected

DLPX-34335

When archived logs are in recovery area, directories can be created with incorrect permissions.

DLPX-33123

Expect script exception should maps to OracleTargetscriptsExceptions, instead of vanilla DelphixUserException

DLPX-34622

Unsubstituted strings in removeUnneededZFSFiles() in oracle.snapsync.impl.SnapSyncJob.java

DLPX-34011

MSSQL export storage container after validation during enable

DLPX-34009

MSSQL Standardize SQL script generation

DLPX-33198

Incorrect handling of failover instances for Availability Groups

DLPX-33294

MSSQL VDB enable job hung up behind other sql jobs

DLPX-32519

Refresh/Provision can fail for MSSQL during standby phase if exclusive lock fails

DLPX-32572

MSSQL Provisioning should only switch to standby and back when doing point-in-time restores

DLPX-32571

MSSQL Provisioning should only mount source-archive when doing a point in time restore

DLPX-34423

MSSQL VDB monitoring broken

DLPX-34010

Able to delete Primary User when environment is an AG cluster and no databases are linked

DLPX-34007

Failed operations leaving MSSQL database in single user mode

DLPX-31383

We should inform customer when we detect that iSCSI initiator is not running

DLPX-31081

Continuation of "MSSQL Backup set appears to have been deleted for a snapshot"

DLPX-34808

Throw DUE to contact support if symptoms for DLPX-34135 are seen

DLPX-28057

Error message when ppt MSSQL instance owner cant read backup location can be improved

DLPX-33049

Workaround from 38187 leaves MSSQL VDB in restoring state after disable/enable

DLPX-34084

Able to break MSSQL provisioning by connecting to VDB before provisioning had completed

DLPX-34712

ASEHostEnvironmentDiscoveryProvider.discoverInstances discovers incorrect UID/GID for ASE processes

DLPX-34005

ASE environment discovery assumes user's default database is master

DLPX-34728

Sybase ASE toolkit subdirectories should be created with group write

DLPX-34650

AppData rollback should not run toolkit 'provision' hook

DLPX-31395

message_action for DB_SYNC needs improvement for AppData

DLPX-32894

PgSQLWALSegmentDO constraint violation in PgSQLBaseLogProcessor

DLPX-33001

ssh does not have inactivity timeout

48

Delphix User Guide 2016 Delphix

DLPX-34793

Refreshing environment after target server rebuild results in spurious connection error

DLPX-34044

UnixMounter broken for key based authentication

DLPX-34214

Bump up the default socket buffers for replication

DLPX-33303

Sanitize product names on upgrade

DLPX-35323

4.1.5.0 to trunk upgrade fails with checksum mismatch for migration

DLPX-33248

Add new 4.1.x migration files for MDS unit tests

DLPX-34662

DFE Error while retrieving MDS version on upgrade to trunk

DLPX-31685

Quota on rpool/update is too small

DLPX-34658

Implement generic ObjectReference-based locking strategy

DLPX-34640

pfexec on solaris ends up calling dlpx_pfexec

DLPX-32665

mkdir/rmdir no longer run without elevated privileges

DLPX-34745

Not trying to run rmdir without dlpx_pfexec

DelphixOS Fixes
Bug Number

Description

DLPX-31490, DLPX-34665

Increase default idm send/receive buffer sizes

DLPX-34215

traverse_prefetcher does not prefetch enough

Release 4.1.4.0 Changes

Management Server Fixes
Bug Number

Description

DLPX-32834

V2ASM for RAC database should use SRVCTL stop instead of SQLPLUS shutdown abort

DLPX-32832

move-to-asm.sh fails with "Use Oracle install user to run this script" error

DLPX-32666

use 'SQBHEADERONLY' as opposed to 'HEADERONLY' for reading Redgate backup headers

DLPX-31381

enable MSSQL dsource failing staging db already exists

DLPX-33045

validated MSSQL sync logs expected interrupts to the error log

DLPX-32726

fix internal error while discovering MSSQL cluster environment backup software

DLPX-32518

support using the original backup location with MSSQL dSources

DLPX-31978

opportunity to improve efficiency of finding MSSQL backup file

DLPX-31945

MSSQL discovery does not detect Redgate backup software when the Redgate GUI client is not installed

DLPX-32684

getting ASE instance ports fails when client character set is different from server character set

DLPX-31827

jobs with percentComplete of 100 should have a jobState=COMPLETED

DLPX-33262

admin app appears in 30% of the screen height

DLPX-33281

JetStream should not come up in IE7 mode when actually in IE9 compatibility mode

DLPX-32913

hard to see the pencil to switch from scn to level based backups on back of dSource card

DLPX-32821

capacity screen has wrong units for retention periods

DLPX-32806

snapshots aren't retrieved more than once on capacity screen

49

Delphix User Guide 2016 Delphix

DLPX-32607

capacity screen snapshots pulldown screen takes minutes to display snapshots

DLPX-32284

provide a warning banner on the login page to warn people when they are using too-old a browser

DLPX-32209

"dSource is unlinked" display for each click on dSource

DLPX-30951

GUI can get confused during storage configuration resulting in spurious "in use" error

DLPX-29317

duplicate usernames fail to login to Server Setup interface

DLPX-33293

standardize long, float, and double API types into integer and number

DLPX-33292

consolidate API JsonType enums

DLPX-34069

fix internal error under some conditions during stack startup

DLPX-34051

fix internal error while processing alerts during upgrade

DLPX-33190

fix internal error in replication after upgrade

DLPX-33062

fix internal error in incremental replication on MSSQL / ASE due to dataset is busy

DLPX-32388

fix internal error in TransactionalFilesystemManager during on stack startup when deleting deadbeats

DLPX-32672

fix internal error in StorageConfigurationManagerImpl blocking storage setup

DLPX-32824

add unit testing for upgrades

Release 4.1.3.2 Changes

Management Server Fixes
Bug Number

Description

39605

remove instrumentation which causes benign memory free to crash the management server

DelphixOS Fixes
Bug Number

Description

39598

fix free of invalid memory address when enabling a network interface

Release 4.1.3.1 Changes

Management Server Fixes
Bug Number

Description

39193

increase TCP tunables to maximize NFS read throughput on 10Gbit networks

DelphixOS Fixes
Bug Number

Description

39198

increase network I/O ring sizes to maximize throughput on 10Gbit networks

Release 4.1.3.0 Changes

Management Server Fixes

50

Delphix User Guide 2016 Delphix

Bug Number

Description

38548

Refresh/rewind/stop-start of VDB on Linux fails, leaving stale mounts

38046

Hook execution not generating job events nor updating completion percentage

38007

Internal error getting current redo log status for Oracle DB

38200

Query returning duplicate entries for an Oracle tempfile

37893

Need to verify compatibility before plugging Oracle 12c vPDB into a target CDB

37369

Oracle SnapSync stuck in failure loop causing performance problems

37712

Oracle provisioning failed while creating file under the datafile mount

37697

Internal error during initial SnapSync of Oracle 12c PDB when environment user is changed from the environment

37817

Logs needed for Oracle snapshot: compare deleted logs on dSource to missing logs in snapshot

38364

Improve reporting for Oracle archive-log-current failures

38436

SQL Server 2014 Support

38219

SQL Server internal_version ranges are incorrect

38470

SQL Server provision fails when source DB was in read-only mode when backed up

38201

Could not redo log record when sync'ing SQL Server dSource

37756

Failure during refresh where SSMS cannot drop database because it is currently in use

37663

Add support for Sybase ASE version 12.5

38361, 38820

Add support for Sybase ASE on Solaris

38006

Internal error deleting PostgreSQL database

38316

AppData SnapSync jobs stuck at 0% when the connector does not start

37997

Connector needs to support larger payload

37460

Could not start remote shell because of pattern matching failure

38730

Checking mounts fails when findmnt is not installed

38488

Refactor environment monitor check success logic

37981

Internal error in environment monitor during MSSQL file deletion

38329

Hostchecker failing for option 4: JDBC connect to dSources

38480

Fix hostchecker check for option 4: Check Oracle DB Instance

38489

Hostchecker should display errors more prominently

38490

Hostchecker claims it is using oci, but in reality it is using thin

38194

Snapsyncs are hanging at 0% after upgrade to 4.1.1.0

37532

Bumping the API version in the PAM module shouldn't require an OS upgrade

38162

Internal database upgrade is broken in 4.1.3.0

38772

Rolling back after a failed upgrade does not work

38670

Remove SSLv3 for CVE-2014-3566

37883

Jet Stream is not clearing the previous segment field of a segment when that object is deleted

37749

Add a link to Jet Stream Capacity Information KB article on the Capacity page

36798

Gather additional debugging information by forcing stack crash on out-of-memory conditions

51

Delphix User Guide 2016 Delphix

37884

Generating a support bundle may use a non-admin user, resulting in incomplete bundle data

38098

Internal error sending support bundle

38203

SNMP trap varbind data is out of order which confuses the Tivoli Netcool SNMP implementation

38287

Add "Copy Data Engine" product type

37998

Fix exception handling code so that it is idempotent

38103, 37847, 37844,

Unit testing improvements

37839, 37842, 37843,

37846, 37840, 37841

DelphixOS Fixes
Bug Number

Description

37650, 37777, 37778, 37779

Improve filesystem prefetch (and disable it by default)

37965

Storage LUNs failing to expand, although visible in "Sysadmin > Capacity" screen

38349

Update Bash version

Release 4.1.2.0 Changes

Management Server Fixes
Bug Number

Description

35193

Provisioning fails with "Failed to rename datafile" when dSource has no valid tempfiles

37541

Linking and provisioning PDBs on SPARC fails Provision against PDB into SPARC CDB hangs

37618

PDB provision fails on SPARC with exception.oracle.targetscripts.pdb.plug

36877

Linking Oracle on SPARC sometimes fails

36917

Deleting a 12.1.0.2 VDB Failed with ORA-65179

36899

Provision against 12.1.0.2 PDB failed to open database after recovery

36292

Need to leave the auxiliary CDB around when PDB provisioning fails

37818

Fixed internal error in PDB linking for in a RAC CDB

37162

Need to include PDB$SEED datafiles in CDB snapshots

36780

Oracle Source Continuity: detect and throw an error on vPDB resetlogs

36778

Oracle Source Continuity: add support for PDB resetlogs

36752

RMAN command file filename length can exceed filesystem limit

36289

_controlfile_enqueue_timeout should not be overriden during Oracle provisioning

37062

SnapSync should fail if post RMAN queries time out

36611

Oracle connection verification does not check v$rman_configuration when linking

37055

SnapSync hangs after archived log backups when LogSync is disabled and no archived logs need backup

36120

Check and set umask before switching archive logs as part of SnapSync

37668

MSSQL dSources in simple mode not able to pull in new full backups

36379

MSSQL provisioning fails when requested from API version 1.1.1 or lower

52

Delphix User Guide 2016 Delphix

37158

SAP ASE warning is not sent if "Discover SAP ASE" option was not set

37157

Log backup for SAP ASE changes the snapshot time of the first backup when not required

36846

Internal error during sync on a replicated SAP ASE dSource after failover

36640

Change JDBC driver to jConnect for SAP ASE databases for better progress reporting

36466

AppData toolkit calling stop scripts on delete of failed provision

37297

Fix internal error in pre-provisioning

37242

Fix V2P failure due to "Could not change permissions for file"

37476

Auto-refresh the capacity management page

37437

Refreshing cluster environment failed with internal error

36797

Add debugging information to help diagnose out-of-memory issues

37054

ntpq -p times out when using IPv6

37493

Hostchecker needs to check group permissions

37492

Hostchecker tarball should include a top level directory

37371

Hostchecker permissions check is too strict for target servers

37060

In some shells, pluggable sudo may require passwordless sudo

37044

Add tool to help support engineers create host privilege elevation profiles

37236

VDBs not automatically disabled when upgrading OS following deferred OS upgrade

37494

Creating a Jet Stream bookmark with LATEST_TIMESTAMP doesn't work as intended for Oracle dSources

37043

Deleting Jet Stream container can leave mount points with stale file handles

37357

Jet Stream bookmark at now does not actually create a bookmark at now

37299

Deadlock detected in Jet Stream bookmark query

36766

Improved an error message related to policy cutoff times

DelphixOS Fixes
Bug Number

Description

37402

Minor filesystem tuning improves I/O performance in some cases

Release 4.1.1.0 Changes

Management Server Fixes
Bug Number

Description

36710

Disable / enable prevents backup history from running

36178

Pre-provisioning is using production memory settings which is overwhelming target servers

36565

Preserve dSource across RESETLOGS for non-12c Oracle DBs

37207

End timestamp for a log fetched by LogSync in Archive Redo mode can be incorrect

36256

GUI crashes on jobs with tons of events

35789

Recovery errors during provisioning

36735

V2P fails with large number of datafiles

53

Delphix User Guide 2016 Delphix

36982

SnapSync resumed initial load will backup files that have already been backed up

36796

Creating more than one VDB template fails

36175

SnapSync failure with internal error

36398

Internal error in ASE DB deletion

36109

ASE DB container runtime output should be formatted for timezone

36745, 36936

Windows AppData source derivative can not be replicated

37240

Add XPP support for SYSTEM dictionary managed tables

37239

Depending on the order of datafiles retrieved from database, XPP will fail with internal error

36624

Provide simple HTML report of XPP activities

36519

Event list on back of active job is in reverse order

36054

All dSources appear to be unlinked after reloading page

36631

Clicking on a dSource in databases list fails

35604

Recovery model of dSources shows None

35878

Switching timeflows failed for 12c VDB

35853

Add dSource "Advanced" should be taken out for PDB linking

35323

NPM-enabled VDBs will not be mounted after Delphix reboots if the VDB was disabled earlier

36935

JVM hung in forkAndExec on Solaris host due to deadlock in PKCS11 crypto library

36174

Can't delete a disabled MSSql dSource when environment disabled

36413

delphix_admin email address incorrectly got unset

36567

Need a way to purge unusable logs

36060

PKCS11 consumes too much native memory on Delphix for SSL sessions

36719

Provision validation doesn't use -nosuid for mount of /public

35621

Upgrading Delphix with an LDAP server using MD5 authentication makes LDAP unconfigurable

36146

Check registration status of appliance from server admin pages

36900

Enable challenge-response PAM module on release OVAs only

36960

Improper use of sizeof compromises challenge-response PAM module

36974

Add a tunable to control the "static attributes check period"

36975

Add a tunable to disable remote checks in the environment monitor

36613

Minimum OS version not set correctly for stack-only ugrade

37125

Upgrading stack-only from 4.1 to 4.1.1 renders system unbootable

36850

Upgrading stack-only from 4.1 to 4.1.1 fails because PostgreSQL times out

37122

Rare upgrade issue when upgrading from 3.2.6+ to 4.0.6.0

35988

Rare upgrade issue when upgrading from 3.2 to 4.1

DelphixOS Fixes
Bug Number

Description

37219

Rare kernel panic on 4.1.0.0

54

Delphix User Guide 2016 Delphix

Release 4.1.0.0 Changes

Delphix network services are increasingly using the Delphix Session Protocol. SnapSync, V2P, and the Unix Connector (used to run
Oracle, PostgreSQL, and SAP ASE hooks) have been re-architected to use the protocol. This places new network connectivity
requirements on the product and the hosts that interact with Delphix Engines. See Network and Connectivity Requirements for more
details.
A network benchmarking tool has been added to the Delphix Engine for testing network performance when setting up new environments
and when debugging network performance anomalies. See Network Performance Tool (iPerf) for more details.
The queries that Oracle LogSync uses have been improved to generate even less impact on the source database.
If you mouse over an object that is showing a warning / fault, a tooltip will now appear with a description of the fault.
Oracle V2P has new advanced data transfer options. See the Oracle V2P documentation for more details.
Cross-platform provisioning has new GUI support for cross-platform script deletion and downloading, plus a new report which displays a
summary of activity. Some additional unsupported Oracle setups are now noticed earlier in the process of performing a cross-platform
transformation and reported as errors. See the documentation for cross-platform requirements.
The "Provision" job in previous versions has been split into separate "Provision" and "Snapshot" jobs.
It is now possible to launch a job from a policy without specifying an execution timeout limit.
Performance and accuracy improvements were made for the Performance Analytics screen.

Release 4.1 Known Issues

Rebooting
Must Disable Performance Mode Before Rebooting
If there are any VDBs with performance mode enabled, performance mode must be turned off for those VDBs prior to reboots and upgrade.
Otherwise, they may not be mounted correctly after the reboot. Performance mode can be re-enabled after the reboot has completed.

SAP ASE Issues

No Fine Grained Progress Monitoring
Fine grained progress monitoring of linking and validated sync operations is not supported. Progress can be determined by manually inspecting
the log file of the ASE Backup Server process used for the link and validated sync operations.

Must Disable "net password encryption reqd"

The ASE "net password encryption reqd" sp_configure option must be disabled.

Point in time provisioning on ASE 12.5 is not supported

For Sybase ASE 12.5, point in time provisioning is not supported in version 4.1.3.x and 4.1.4.x.

Oracle 12c Pluggable Database Issues

When using an Oracle 12c pluggable database (PDB) with your Delphix Engine, the following features do not work as expected:
Virtual-to-Physical (V2P) functionality is not supported for PDBs.
Pre-provisioning is not supported for PDBs.
Virtual PDB migration to a different single container database (CDB) is not supported.
Linking PDBs in physical standby or Active Data Guard CDBs is not supported.
PDB source attach is not supported.
The initial SnapSync for a PDB is not resumable.
Provisioning a PDB Data Source linked from a RAC CDB to a non-RAC CDB is not supported.

Cross-Platform Provisioning Issues

Source Validation First
The Data Source / VDB validation has to run on the source first. Otherwise, you can replica provision a same-platform VDB from the source and

55

Delphix User Guide 2016 Delphix

run cross platform validation against that.

Unsupported Oracle Features

The Oracle Label Security and Database Vault features will cause cross-platform provisioning to fail.

VDB Refresh Takes a Long Time

The time taken to refresh a cross-platform provisioned VDB is similar to the time taken for cross-platform provisioning. This is because the refresh
process re-provisions the VDB, including much of the cross-platform provisioning logic. We are investigating how to improve this in a future
release.

Application Data for Windows Issues (Unstructured File Virtualization)

Toolkits and Hook Operations Not Yet Supported
Application Data for Windows only supports unstructured file virtualization. Additional Application Data features on UNIX platforms, such as hook
operations on vFiles and toolkits, will be supported on Windows in a future release.

56

Delphix User Guide 2016 Delphix

Release 4.2 - 4.2.x.x Known Issues and Changes

These are the known issues and workarounds for Delphix Engine release 4.2 - 4.2.x.x
Release 4.2.5.0 Changes
Management Server Fixes
Release 4.2.4.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.2.3.1 Changes
Management Server Fixes
Release 4.2.3.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.2.2.1 Changes
Management Server Fixes
Release 4.2.2.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.2.1.1 Changes
Management Server Fixes
Release 4.2.1.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.2.0.3 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.2.0.2 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.2.0.1 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.2.0.0 Changes
Release 4.2 Known Issues
Benign Faults on Oracle Cluster Homes
SAP ASE Issues
Oracle 12c Pluggable Database Issues
Cross-Platform Provisioning Issues
Unsupported Oracle Features
Unstructured Files and Oracle Enterprise Business Suite

Release 4.2.5.0 Changes

Management Server Fixes
Bug Number

Description

DLPX-38636

unable to create shared memory segment due to large segspt_minfree

DLPX-38542

Deleting a Postgres dSource while host is offline causes DFE loop

DLPX-38774

dsources should be taken out of performance mode on upgrade

DLPX-38773

It should not be possible to enable PerformanceMode on dSources

DLPX-39109

NPE in FaultManagerImpl#postErrorEvent

DLPX-38970

Windows cluster refresh fails with script not found

57

Delphix User Guide 2016 Delphix

DLPX-38955

DB_SYNC code should avoid doing an attach database after rollback

DLPX-38954

Windows Mounter should check if the LUN is mounted

DLPX-38953

MSSQL write cache enabled on dSource can cause NTFS corruption

DLPX-38885

AppData AIX mount options include cio and intr when not needed

DLPX-38884

mount options for Solaris should not include 'noacl'

DLPX-38874

AppData NFS mounting options should include "noac" when Additional Mount Points in use

DLPX-38861

Upgrade to 4.2.4.1 gets dSource out of NPM mode but associated filesystems are not mounted - zfs state

DLPX-38657

ASE linking fails after patching due to dump message change

DLPX-38775

NPM is left on following validated sync

DLPX-38368

Race between retention and settings of previousTimeflow during refresh leads to NPE in replication

DLPX-38219

RESTORE HEADERONLY fails for SQL 2014 + SP1

DLPX-37701

Sybase DB discovery fails when /tmp is mount noexec

DLPX-38563

mds upgrade scripts for 4.2.4.0

Release 4.2.4.0 Changes

Management Server Fixes
Bug Number

Description

DLPX-38490

Setting 'Data Operator' and 'Reader' privileges via GUI fails after upgrade

DLPX-38462

doesInitiatorExist does not check for null IQNs

DLPX-38442

MSSQL iSCSI view gets deleted on export

DLPX-38408

GUI - new user privileges dropdown menu can be glitchy on Chrome and IE

DLPX-38407

Consider renaming the new 'Refresher' user privilege

DLPX-38406

GUI - AppData vFiles with 'Reader' privileges still has a 'snapshot' button

DLPX-38405

Cannot refresh VDB with 'refresher' privileges via GUI

DLPX-38387

VDB provision to Oracle 9.2.0.8 standard edition fails with ORA-00439

DLPX-38386

Unable to add dSource due to ORA-00604 and ORA-01882

DLPX-38356

Serialization state manager must be stated before reaper

DLPX-38272

DE upgrade removes pam.conf needed for Challenge/Response feature

DLPX-38243

Create GUI for new data and read only user roles

DLPX-38235

Add data and read only user roles

DLPX-38195

MDB ::arc_compression_stats hangs in support bundle generation

DLPX-38137

Bump API version to 1.5.3 for 4.2.4 after exposing device removal

DLPX-37875

expose device removal APIs

DLPX-37864

Include IOPS, MBPS along with avg/min/max/stdev latency in test results

DLPX-37845

mds upgrade scripts for 4.2.2.1 & 4.2.3.0

DLPX-37831

inconsistent replication stats after job is resumed

DLPX-37768

reporting warning 4.2.2.0 --SSH configuration file '/export/home/delphix' is group readable.

58

Delphix User Guide 2016 Delphix

DLPX-37698

ORA-39165 during schema export due to username with special character

DLPX-37676

Need to explicitly set the CHARSET for ASE JDBC connections

DLPX-37675

Support RESTRICT_IP tunable for ASE

DLPX-37637

Installer might get stuck without error log instead of running the silent installer

DLPX-37548

additionalMountPoints does not mount to additional environments

DLPX-37517

Oracle 12c does not work with connection information

DLPX-37492

snapshot controlfile on non-ASM shared location is still failing

DLPX-37465

windows connector cannot be installed on hosts that do not have mssql installed

DLPX-37371

synchronize ebs adpreclone database and dbtechstack on same host

DLPX-37135

java.lang.AssertionError: unexpected executor context in job

DLPX-37073

enable device removal apis for 4.2

DelphixOS Fixes
Bug Number

Description

DLPX-38193

panic with null pointer from sys_tick()

DLPX-37766

nlockmgr failing to start after reboot leads to environment failures

Release 4.2.3.1 Changes

Management Server Fixes
Bug Number

Description

DLPX-38031

Add new logos for Delphix Express

Release 4.2.3.0 Changes

Management Server Fixes
Bug Number

Description

DLPX-37687

dx_install_archive: rpool is not a valid ZFS pool

DLPX-37667

java.lang.OutOfMemoryError: unable to create new native thread

DLPX-37595

upgrade job completes before reboot

DLPX-37499

Null pointer error when viewing admin app due to free version check

DLPX-37458

host based clients stuck upon session reset

DLPX-37422

Delphix Express

DLPX-37420

DUE exception handling for SnapSync jobs

DLPX-37414

mds upgrade scripts for 4.2.2.0

DLPX-37412

Consider switching capacity pages to have a refresh button

DLPX-37411

The maximum number of entries in the pie graph on usage overview page should be 10

DLPX-37382

EBS adpreclone script exits 0 even during failure

59

Delphix User Guide 2016 Delphix

DLPX-37378

[IE-11] drop-down menu for owner on container creation page is not visible

DLPX-37376

Make the toolkit size available check more sophisticated

DLPX-37375

Extend the oracle home detection improvements to the Oratab check

DLPX-37374

Oracle DB Instance check should only run for Oracle Sources

DLPX-37373

Explicit timeouts for EBS stop scripts

DLPX-37372

EBS 12.2 appsTier snapsync should fail if server is down

DLPX-37307

V2P Recovery should ignore RMAN-07518 warnings

DLPX-37306

native OOM issues not surfaced by libumem

DLPX-37302

API to map REFRESH, RESTORE, RESET operation to the time for the previous snapshot

DLPX-37300

Jet Stream UI needs to use new API to get time for last tickmark prior to REFRESH, RESET, RESTORE

DLPX-37282

Handle symlinks in toolkit check

DLPX-37279

Spurious fault.policy.log.retention.old.snapshot faults possible

DLPX-37277

"Unable to purge logs" occurs even when dSource is unlinked/disabled

DLPX-37256

test_usage_bookmark_externally_referenced_container failed in dvc regression on 4.2.3.0

DLPX-37251

Allow non-standard homes in 12.1 and 11i appsTier provisioning

DLPX-37230

SerializationStateManager is not syncing manifest on receive

DLPX-37205

After upgrading to 4.2.1.1 VDB configuration template parameters do not display during provisioning

DLPX-37201

Cannot increase Oracle V2P file concurrency to more than 10

DLPX-37196

EBS DB_SYNC fails if Apache not installed on DB Tier

DLPX-37195

enable zpool features on upgrade

DLPX-37193

After upgrade to 4.2 stack doesn't start up because a fault has no message associated with it

DLPX-37181

Large number of phonehome timeouts cannot be cleared

DLPX-37152

PGSQL_INSTALL already exists

DLPX-37151

Better reporting of parsing failures when linking postgresql database

DLPX-37150

pgsql host checker for versions 9.3 and 9.4

DLPX-37147

invalid credentials fault broken

DLPX-37146

`sunrpc.tcp_slot_table check` should only run on target machines

DLPX-37145

Better separation of "source" checks and "target" checks

DLPX-37085

DSP: illegal transition from FREE to ZOMBIE

DLPX-37078

configuration service leaks file descriptor

DLPX-37053

Prevent null timezones in dlpx_policy

DLPX-37042

Basic support for postgresql 9.3 and 9.4

DLPX-36883

Oracle provision scripts affected adversely by customer turning SET TIMING ON in their SQLPLUS init file

DLPX-36869

No Postgres installation found when provisioning

DLPX-36850

Fix version command in CLI to be sychronous

DLPX-36780

Translator for configTemplate and configParam conflict

DLPX-36774

callout export sometimes fails if user tablespaces are readonly

60

Delphix User Guide 2016 Delphix

DLPX-36743

VDB provision takes long time in doRenameDatafiles, dSource has ASM datafiles, target host does not have ASM

DLPX-36660

12c OJDBCAccessorImpl#getConId() needs sanity check before return zero con_id

DLPX-36632

ASE support for AIX

DLPX-36521

Continued WARNING alerts: "Command exited with a non-zero status"

DLPX-36441

upgrade tests fail due to missing chap secret

DLPX-36299

Dropping VDB with cross references fails

DLPX-36298

NPE in cloneNewTimeflow() during SnapSync

DLPX-36164

iscsicli doesn't parse ASCII correctly

DLPX-36001

Oracle Validated Sync fails with ORA-01157 during post provision query

DLPX-35932

iSCSI CHAP

DLPX-35892

Live Source Gear stuck in waiting after it is created

DLPX-32667

Policy enforcement runs and alerts on disabled VDBs

DelphixOS Fixes
Bug Number

Description

DLPX-37443

ZFS "hangs" while deleting file

DLPX-37430

native heap OOM issues don't cause core dumps

Release 4.2.2.1 Changes

Management Server Fixes
Bug Number

Description

DLPX-37083

Alert for permissions on CRS home

DLPX-37254

Instance listed in oratab file is not running fault should be removed

DLPX-36921

UEM raising faults for permissions on CRS home for single instances

DLPX-37506

add instrumentation to help root-cause DLPX-37365

Release 4.2.2.0 Changes

Management Server Fixes
Bug
Number

Description

DLPX-36658

VDBs not re-enabled if environment fails to refresh

DLPX-37040

Upgrade action is shown as cancelable in action panel

DLPX-37032

Latency values not showing up on Performance Analytics page

DLPX-37025

deferred os upgrade with OsTooOld due to faulty comparison

DLPX-36944

Run V020140710__fhloston_pre_post_scripts_windows_appdata upgrade script conditionally

DLPX-36896

MSqlJDBCConnectionUtil cannot connect to master for case sensitive collations

61

Delphix User Guide 2016 Delphix

DLPX-36894

IllegalStateException: Property value null is not a known schema type

DLPX-36873

Oracle log link worker does not properly end contexts

DLPX-36867

NPE(s) after upgrade to 4.2.1.1 preventing Faults from being shown in GUI

DLPX-36781

Continued WARNING alerts: "Command exited with a non-zero status"

DLPX-36768

NPE in MSSqlPreProvisioningWorker#raiseFault

DLPX-36723

Do not send emails about ignored faults

DLPX-36721

4.2.1.1failed in fhloston_migrate_serialization_state.java:168 on a replication source

DLPX-36715

DFE deserializing Oracle source on bundle upgrade

DLPX-36714

intactfinancial upgrade to 4.2.1.1 failed in flyway script execution

DLPX-36699

cli and backend disagree on source.operations.configureClone type

DLPX-36685

NPE in FaultManagerImpl.java on bundle upgrade

DLPX-36682

MongoDB should be restarted periodically to prevent it from consuming too much memory

DLPX-36671

ssh_config requirements not listed in 4.2 documentation

DLPX-36659

MongoDB timeout window too short sometimes

DLPX-36656

source.host.mismatch exception upgrading Ontario Teachers bundle

DLPX-36616

IllegalStateException: pending sync action in unexpected state

DLPX-36592

NPE upgrading clorox support bundle to 4.2.2.0

DLPX-36571

migration_list for 4.2.1.1

DLPX-36569

After upgrading to 4.2.1.0 debug log files roll over in 3 hours due to logging MDS queries

DLPX-36545

Source Continuity creates unnecessary source-archive file system on zfs

DLPX-36524

After upgrading to 4.2.1.0 debug log files roll over in 3 hours due to logging MDS queries

DLPX-36488

Oracle V2P should support configuration of underlying DSP config options

DLPX-36483

Support ASE 16

DLPX-36429

Eliminate wildcard imports from our codebase

DLPX-36418

If host IP address exists in duplicate environments (RAC and standalone), disable of one prevents refresh of other

DLPX-36413

Dropping VDB with cross references fails

DLPX-36407

mds upgrade scripts for 4.2.1.0

DLPX-36403

The UI shows that a JS bookmark's data has been cleaned up by retention

DLPX-36352

EBS 12.2 toolkit *determine-run-edition.sh does not work properly on Solaris

DLPX-36337

Remove setInterval() calls

DLPX-36300

dSource card layout allows drawing confirmation buttons out of visible area

DLPX-36287

Clean-up and optimize old storage container stats capacity code

DLPX-36281

NPE in test_validate_xpp_with_invalid_timeflow_point

DLPX-36279

AppData staging should not allow you to choose an incompatible staging environment

DLPX-36277

Windows Appdata staging dsource card contents don't fit within box

DLPX-36247

Fix text strings in live source ui-part 2

DLPX-36190

No compatible Oracle Installation Home from Provision VDB

62

Delphix User Guide 2016 Delphix

DLPX-36182

VDB Refresh doesn't honor "Open Database After Provision" selection

DLPX-36128

hostchecker.sh does not extract and use bundled jdk when it should

DLPX-36108

Oracle 12c - PdbPlug and PdbOpen exception handling made wrong assumption, causing incomplete clean up after provision
failure

DLPX-36079

stack on upgraded replication target does not come up after vm is unregistered and reregistered

DLPX-36021

Add PowerShell test toolkit

DLPX-35992

Navigation in Jet stream is broken with non en-US locale

DLPX-35985

XPP needs to handle 12c APEX user

DLPX-35983

NPE in MSSqlPreProvisioningWorker.java

DLPX-35935

Fix text strings in live source ui

DLPX-35934

Pages scroll bar only displays up to the first 4 pages when dSource is selected

DLPX-35933

Long MSSql LSNs create scroll bar on dSource and VDB snapshots

DLPX-35705

add compression statistics to support bundle

DLPX-35638

vdb rewind fails during recovery

DLPX-35559

i18n for flex, action and schema encoding

DLPX-35524

Time selector flyouts sometimes show when clicking timeline

DLPX-34562

startLiveSourceResync hang against multiple Live Source almost at the same time

DLPX-34557

Consolidate Windows mounting and unmounting

DLPX-34518

Live Source Validation Logic

DLPX-32668

SMTP Auth can not be successfully disabled once enabled

DLPX-35883

Add '::kmastat' to support bundle

DelphixOS Fixes
Bug Number

Description

DLPX-36529

kmem reap thread gets blocked in reclaim callback

DLPX-35303

track arc buf compressed size

DLPX-36416

NULL pointer dereference when activating a partially added metaslab

DLPX-36511

verify failed in zio_done(): BP_EQUAL(bp, io_bp_orig)

DLPX-36189

add tunables to combat scheduling delay of kernel threads

Release 4.2.1.1 Changes

Management Server Fixes
Bug Number

Description

DLPX-36535

HOST references remain in MDS after upgrade to 4.2

Release 4.2.1.0 Changes

Management Server Fixes

63

Delphix User Guide 2016 Delphix

Bug Number

Description

DLPX-36355

Engine becomes slow after storage migration and removing device from ESX

DLPX-36349

Upgrade migration failed, unexpected character in LinkedSourceOperations

DLPX-36348

Capacity API calls get extremely slow with large number of snapshots

DLPX-36347

cannot create AppData dSource using older webservice versions

DLPX-36336

Remove setInterval() calls

DLPX-36321

dx_verify subject to SMF and postgres race conditions

DLPX-36319

IllegalStateException upgrading MDS with DB_SYNC in WAITING state

DLPX-36262

mds upgrade scripts for 4.2.0.3

DLPX-36259

Trying to edit the database user for a vPDB fails with "virtual database is enabled"

DLPX-36251

Unable to update AppData Staging Mount Base from GUI

DLPX-36236

Running toolkit scripts fails on win2003

DLPX-36233

dx_upgrade should pass -v before version argument when calling dx_verify

DLPX-36227

Updating the env user for an AppData Staging dsource leads to crash

DLPX-36221

ZfsService.getAllSnapshotsSorted returns incorrect number of snapshots

DLPX-36215

Upgrade translator V020150119__fhloston_stream_state specifies manifest path incorrectly

DLPX-36214

4.1.6.0 upgrade scripts

DLPX-36196

AssertionError: object reaper service was never started

DLPX-36195

AssertionError: object reaper service was never started

DLPX-36194

clearing read-only attribute failed for disk

DLPX-36186

explicitly say no to rac in dbtechstack adcfgclone

DLPX-36173

dx_verify.sh tries to mount root even if it's already mounted

DLPX-36168

AppData toolkit mounts fail on windows

DLPX-36115

SyncDir.ps1 fails when running on Windows 2003 with robocopy error

DLPX-36098

Enable live source fails due to DFE after replication failover

DLPX-36082

"read" in dlpx_pfexec script may not accept empty input from /dev/null, need terminating "\n"

DLPX-36071

Pause and resume of Oracle V2P during database recovery phase results in crash dump

DelphixOS Fixes
Bug Number

Description

DLPX-36111

allocation throttled zio gets stuck behind other tasks in taskq

DLPX-36017

correct the dcenter_group for os-gate's .delphixrc file on 4.2 branch

Release 4.2.0.3 Changes

Management Server Fixes
Bug Number

Description

64

Delphix User Guide 2016 Delphix

DLPX-36165

JNA leaking CallbackReferences, leads to native memory exhaustion

DLPX-36163

After VPDB Rewind always shows one snapshot

DLPX-36162

Exception on start up if LiveSource present

DLPX-36135

After VPDB Rewind always shows one snapshot

DLPX-36085

Cannot import PowerShell Script operation template

DLPX-36073

mds upgrade scripts for 4.2.0.2

DLPX-36052

dx_verify fails from 4.2 to trunk due to class path errors

DLPX-36042

MDSVerify fails on DCoD due to flyway placeholders

DLPX-36018

AppData Staging dSource not showing correct environment users

DLPX-36014

Faults raised for recovered error - TLog was busy

DLPX-35963

NPE in TrileadC3ConnectionImpl.java

DLPX-35957

EBS 12.2 AppsTier vFiles sync failed

DLPX-35799

Engine restarts when clicking V2P on Windows

DLPX-35691

Switchtimeflow can't handle NULL or not ready current timeflow

DLPX-35646

Do not allow Agile Masking to be enable in 4.2.0.0

DelphixOS Fixes
Bug Number

Description

DLPX-36111

allocation throttled zio gets stuck behind other tasks in taskq

DLPX-36017

correct the dcenter_group for os-gate's .delphixrc file on 4.2 branch

Release 4.2.0.2 Changes

Management Server Fixes
Bug Number

Description

DLPX-35669

ASE GUI does not set loadBackupServerName when Remote Backup Server selected

DLPX-35856

Crash dump due to lack of a schema for job target OracleExportDO

DLPX-35867

Parent jobs mark finished before children on stack startup

DLPX-35938

mds upgrade scripts for 4.2.0.1

DLPX-35649

Interim solution for bug DLPX-30538 Check for Oracle bug 13075226 fails on 11.2.0.3 with patch installed

DLPX-35711

Adding more than one hook operation template is slow and the templates window doesn't update

DLPX-35709

Sorting hook operation templates leads to hung gui

DLPX-35758

Unable to add MSSql Clustered VDB as data source to a Template

DLPX-35954

VDB refresh policy can't be set at the group level

DLPX-35787

retention deletes livesource resync timeflow

DLPX-35979

Windows Create vFiles wizard does not allow PowerShell scripts for Hooks

DLPX-35871

Provision against LS snapshot which has read only datafiles failed

DLPX-35710

Source.name should be a required field when adding a live source

65

Delphix User Guide 2016 Delphix

DLPX-35757

Cluster VDBs failing on vDTully30s and 32s when lower numeric Node is owner of the SQL instance

DLPX-35885

MSSQL initial load failing, QueryRestorePercentComplete stops running

DLPX-35953

VPDB Migration GUI is all Black

DelphixOS Fixes
Bug Number

Description

DLPX-35826

vioif mtu cannot be set to values other than 1500

Release 4.2.0.1 Changes

Management Server Fixes
Bug
Number

Description

DLPX-35522

Client could do a better job of checking version number

DLPX-35549

Windows AppData Replication tests fail with 'Cannot untar tar file'

DLPX-35557

unexpected manufacturer value in smbios causes boot to hang in RHEL KVM

DLPX-35560

IllegalArgumentException refreshing a transformed VDB

DLPX-35561

flex doesn't show up after rebuild delphix engine with localized properties files

DLPX-35562

MSSQL cluster VDB provision/export must change disk signature on non-cluster host

DLPX-35564

test_data_container_disable_enable fails Create Jet Stream data container for Appdata on Windows

DLPX-35565

java.lang.StringIndexOutOfBoundsException: String index out of range: -1 when adding live source to dsource with altered
log_archive_config

DLPX-35566

Navbar and actions sidebar are broken after page navigation

DLPX-35589

Migrate VPDB from RAC to RAC failed with exception.db.genericvdb.disabled

DLPX-35614

Linking hooks for AppData windows cannot be saved

DLPX-35616

Intermittent failed to unmount error on windows

DLPX-35631

Intermittent failed to unmount error on windows

DLPX-35680

MDS upgrade to 4.2 fails with NPE due to missing aseVirtualSource.operations

DLPX-35703

addLiveSource fails with NPE

DLPX-35731

Show the template name on the back of the VDB card with a pencil for edit

DLPX-35738

Snapsync fails with internal error when offline tablespace is made online

DLPX-35750

User exception in the environment monitor check when VDB is on a clustered SQL instance

DLPX-35751

Querying iSCSI LU number should take iSCSI view into account for MSSQL cluster VDBs

DLPX-35752

MSSQL cluster VDB provision/export must change disk signature on non-cluster host

DLPX-35753

Provisioning clustered VDBs fail if provisioned with LogSync

DLPX-35760

Validated sync failing with mount errors in hpuxrac5

DLPX-35761

Horizontal scroll bar on back of vFiles card when viewing hook scripts

DLPX-35762

Hook operations gui for empty vfiles should not have before and after refresh hooks

66

Delphix User Guide 2016 Delphix

DLPX-35763

AppData linking wizard summary screen has scrollbars with a long 'path to exclude'

DLPX-35780

ASE: Temporary VDB used by V2P is left around after V2P completed

DLPX-35784

mssql pre-provisioning trying to open backup files in write mode

DLPX-35810

Jet stream bookmark usage data doesn't work as expect

DLPX-35811

StorageUtilTest#getSnapshotCapacityBucketsPolicyOrManual failed

DLPX-35823

Offline datafiles error message should use AFN not name

DLPX-35824

Limit file printing to one per line in the datafile info message during snapsync

DLPX-35829

genericcontainer.cannot.remove.only.snapshot thrown by retention

DLPX-35832

Cannot manually delete snapshot after VDB refresh

DLPX-35842

Oracle provision wizard hook operations have null view model

DLPX-35848

MSSql provisioning with LogSync creates VDB with recovery model of FULL

DLPX-35853

mds upgrade scripts for 4.2.0.0

DLPX-35863

MSSQL Recovery model not set during V2P

DLPX-35880

The Timezone for MSSql VDBs is displayed twice on the card

DelphixOS Fixes
Bug Number

Description

DLPX-35797

disable hole filling

Release 4.2.0.0 Changes

ASE support has been expanded to include ASE 12.5 on RHEL 5.x as well as full support for Solaris 10 machines backed by both the
x86 and SPARC processor architectures. See Supported Operating Systems and Database Versions for SAP ASE for more details.
The live job view has been replaced by the Action sidebar which more clearly presents complex jobs and actions and has a modern
visual style.
The Delphix Engine can be configured to push audit events to an external system via syslog.
MSSQL databases can be linked without the use of purpose built third-party backup software by taking copy-only full backups on a
pre-defined schedule. See Supported Operating Systems, Server Versions, and Backup Software for SQL Server for more
information.
Additional diagnostics are automatically performed for common connectivity errors. See Diagnosing Connectivity Errors for more
information.
Read performance of frequently accessed blocks on systems with many vCPUs and write performance to fragmented pools have been
improved.
Storage devices used by the Delphix Engine can now be removed. See Delphix Storage Migration for more information.
The replication UI has been redesigned

in javascript/html for an improved user experience. See Replication User

Interface for more information.

A tool for measuring the performance of the storage devices provided to the Delphix Engine has been added
to the CLI. See Storage Performance Tool (fio) for more information.
A new screen has been added which displays the space usage of Jet Stream templates, users, containers, bookmarks, and branches .
See Understanding Jet Stream Usage for more information.
Support for running the Delphix Engine in private OpenStack clouds on the KVM hypervisor as well as in the AWS GovCloud security
zone is new in Delphix Engine 4.2. All existing Delphix workflows are supported in both of these new environments.
MSSQL VDBs can now be provisioned to SQL Server Failover Cluster instances. SQL Server Failover Cluster instances are
automatically discovered when adding a Windows Failover Cluster target environment as described in Adding a SQL Server Failover
Cluster Target Environment . See Provisioning a SQL Server VDB for additional information.
A "resetlogs" operation on an Oracle source database (commonly caused by standby failover, database PITR, flashback database) will
automatically trigger a full resync during the next SnapSync.
Replication jobs can be resumed after certain failures without retransmitting data that was successfully transferred.
Oracle V2P jobs can be suspended and resumed without retransmitting data.

67

Delphix User Guide 2016 Delphix

A new feature has been added to the CLI for showing and fetching missing logs on a timeflow. See TimeFlow Patching for more
information.
The ability to ignore persistent diagnostic faults and to mark all active faults as resolved has been added. See System Faults for more
information.
VDB refresh and rewind operations can now be undone.
The queries run against source databases by Oracle LogSync have been made more efficient and buffered writing has been added to
improve LogSync's write performance.
EBS support has been expanded to include EBS 12.2 and EBS 11i.
The historical capacity data API has been augmented to allow obtaining capacity data at arbitrary intervals.
Database config templates can be associated with a repository and a container such that any time the data in the container is deployed
on the associated repository we fall back on the config template if no template has been explicitly specified . This feature can be used to
enable Oracle validated sync on a staging environment that is under-equipped relative to its source. See Provisioning Oracle VDBs: An
Overview#RepositoryTemplates for more information.

Release 4.2 Known Issues

Benign Faults on Oracle Cluster Homes
Sophisticated error detection logic has been added to the Delphix Engine to verify that Oracle homes meet the documented criteria for linking.
This logic may incorrectly run against Oracle Cluster homes resulting in benign faults. Faults raised against cluster homes can be
programmatically ignored when they appear using the ignore faults feature introduced in 4.2.

SAP ASE Issues

You may encounter issues with your ASE instances in the following cases:
ASE instances use case insensitive sort orders and file names are not specified/preserved in a case-preserving way.
ASE instances have multiple listeners and not all listeners can be used by the Delphix Engine.

Oracle 12c Pluggable Database Issues

When using an Oracle 12c pluggable database (PDB) with your Delphix Engine, the following features do not work as expected:
Virtual-to-Physical (V2P) functionality is not supported for PDBs.
Pre-provisioning is not supported for PDBs.
PDB source attach is not supported.
The initial SnapSync for a PDB is not resumable.
Provisioning a PDB Data Source linked from a RAC CDB to a non-RAC CDB is not supported.
Linking and provisioning an entire CDB is not supported
Provisioning a PDB into a virtual CDB is not supported
XPP for multi-tenant databases is not supported

Cross-Platform Provisioning Issues

Unsupported Oracle Features
The Database Vault feature will cause cross-platform provisioning to fail.

Unstructured Files and Oracle Enterprise Business Suite

The Additional Mount Points feature available for Unstructured Files and Oracle Enterprise Business Suite does not work as intended on
versions of the Delphix Engine between 4.2.0.0 and 4.2.4.0. On these affected version, all configured Additional Mount Points will mount to the
primary target environment instead of the additional environments specified.

68

Delphix User Guide 2016 Delphix

Release 4.3 - 4.3.x.x Known Issues and Changes

These are the known issues and workarounds for Delphix Engine release 4.3 - 4.3.x.x
Release 4.3.4.0 Changes
Management Server Fixes
Release 4.3.3.0 Changes
Management Server Fixes
Release 4.3.2.1 Changes
Management Server Fixes
Release 4.3.2.0 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.3.1.0 Changes
Management Server Fixes
Release 4.3.0.3 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.3.0.2 Changes
Management Server Fixes
Release 4.3.0.1 Changes
Management Server Fixes
DelphixOS Fixes
Release 4.3.0.0 Changes
Release 4.3 Known Issues
SAP ASE Issues
Oracle 12c Pluggable Database Issues
Cross-Platform Provisioning Issues
Unsupported Oracle Features
Toolkit Scripts on *nix

Release 4.3.4.0 Changes

Management Server Fixes
Bug
Number

Description

DLPX-41399

AIX ps output doesn't conform to posix standards leading to exception.environment.ps.invalid.output

DLPX-41649

ASE snapsync hangs when master transaction log becomes full

DLPX-40390

databaseCapacity API always returns zero for actualUsedSize

DLPX-41936

listHostByDomain unit test sporadic failures

DLPX-41582

Delphix can't find the ASE dump file when dumping to device with compression syntax

DLPX-39767

Need to rotate stmf_cfg.log

DLPX-40041

HP-UX 11iV3 does not support the noacl mount option

DLPX-41525

java.lang.OutOfMemoryError: Metaspace preventing jobs and EnvironmentMonitorTask from running

DLPX-40350

Cannot provision Oracle VDB from source with datafile names that only differ by a space char at the end.

DLPX-41195

Cannot provision appdata toolkit via GUI from a replicated dSource

DLPX-40458

doRenameDatafiles.sh in AIX with /bin/sh fails with out of memory error when database has 12K+ datafiles

DLPX-41570

[Gonzales] Improve JSON parsing performance

DLPX-41569

[Gonzales] Turn off fault list and user profile UI until needed

69

Delphix User Guide 2016 Delphix

DLPX-41140

Oracle db_user credentials are not used for vDB refreshes

DLPX-40686

Lift restrictions for lower case SIDs in EBS 12.2 appsTier

DLPX-41209

If user name of owner of dataserver process is too long, ps outputs uid, causing add of Dsource to fail with internal error

DLPX-41408

Provision against datafile with more than one space at the end causes provision to fail

DLPX-41402

V2P against dSource has extra space at the end of a datafile got server restart

DLPX-41411

Implement JDBC connection pooling for ASE

DLPX-41650

executeWithProgress crashes Retryer

DLPX-41349

ASE created too many audit log events on source

DLPX-41581

Support for ASE password protected dump files

DLPX-41373

SnapSync fails with missing datafile

DLPX-41619

SourceAttributesRetrieverTask running constantly

DLPX-41629

GUI for ASE password protected dump files

DLPX-41490

ase backup file discovery croaks on hidden subdirectories with identical files

DLPX-41659

MSSQL timeflow point with NULL LSN causes NPE in getProvisionableTimeflowRangeBySnapshot

DLPX-41679

java.lang.RuntimeException: [class com.delphix.appliance.server.util.ProcessExplorer$ProcessResult] is not a valid

BundleParam initialization type

DLPX-41681

Provisioning from snapshot that does not exist leads to NPE instead of Delphix Error

DLPX-41696

upgrade scripts for 4.3.3.0

DLPX-41726

add/bump API version 1.6.2

DLPX-41730

MSSQL internal version query should run against MASTER

DLPX-41762

Delphix can't find the ASE trans dump file with compression syntax when log sync is enabled

DLPX-41820

dSources not picking up transaction log backups

Release 4.3.3.0 Changes

Management Server Fixes
Bug Number

Description

DLPX-41316

missing one analytics datapoint per minute and hour

DLPX-41256

TCP stats collection causes analytics compression to consume all of stacks memory

DLPX-41255

Add missing index for analytics_datapoint table - REVERT

DLPX-41224

isFilesystemHeld races with serialization state updating point's state

DLPX-41211

4.3.3 needs updated dmsuite 4.7.2 (again)

DLPX-40616

Bump API version to 1.6.1 for 4.3.3.0 after introducing a preRollback hook

DLPX-40601

Virtual hooks should include a pre-rewind hook (frontend)

DLPX-40600

Virtual hooks should include a pre-rewind hook (backend)

DLPX-40591

Unable to delete windows host environments if they are already unreachable

DLPX-40576

MSSQL Encrypted Backups

DLPX-40575

MSSQL split stack support

70

Delphix User Guide 2016 Delphix

DLPX-40568

Operation Durations do not appear unless "Create Branch" operation has occured

DLPX-40546

Add missing index for analytics_datapoint table

DLPX-40523

Glacial progress in support_json_bundle.sh

DLPX-40512

unable to delete jetstream template

DLPX-40473

support for litespeed version 8.x

DLPX-40460

GUI is unable to expand LUN

DLPX-40448

nightly build failing with ENOMEM

DLPX-40372

Adding an HPUX environment fails with ps error

DLPX-40349

Unable to delete Jetstream container in UI if container needs recovery

DLPX-40323

All EBS Lua should use RunBash instead of RunCommand

DLPX-40315

upgrade scripts for 4.3.2.0 and 4.3.2.1

DLPX-40289

Replication UI is very slow on a system with many containers

DLPX-40270

DSP Throughput Test QueueDepth doesn't go above 64

DLPX-40263

DSP CLI Throughput test compression option doesn't work

DLPX-40210

4.3.3 should have DMSuite version 4.7.2

DLPX-40204

On a resumed initial backup if many datafiles need backup, the backup command is too long and causes RMAN to fail

DLPX-40194

Weekly operation counts and durations stop working beyond one week

DLPX-40129

Add branch activities for template created prior to 4.1.6

DLPX-40125

AppData dSource card has missing source parameter values

DLPX-40115

Adjust DSP sizing parameters to support SnapSync against large databases

DLPX-40066

Missing translator in Gallifrey for doubleSync

DLPX-40043

V2P failed with AssertionError in FileProgressManager.updateFileProgress

DLPX-40042

ASE get_ase_instance_ports.sh sources installation artifact file SYBASE.env

DLPX-40036

Appdata virtual source status does not automatically resolve when status is fixed

DLPX-39511

MSSQL virtual source enable after upgrade failed saying primary database file is incorrect

DLPX-38893

fault.oracle.source.oratab.unlisted.instance should converted to a warning

DLPX-37832

attachsource on 4.2 now requires postSync/preSync parameters by default and are confusing to set.

Release 4.3.2.1 Changes

Management Server Fixes
Bug Number

Description

DLPX-40142

Delphix deletes customers archived log backups to sbt-tape

DLPX-40231

4.3.x does not properly check for minimum supported upgrade version

Release 4.3.2.0 Changes

Management Server Fixes

71

Delphix User Guide 2016 Delphix

Bug Number

Description

DLPX-40092

ProcessExplorer does not capture cmdline arguments correctly on Solaris

DLPX-40064

NPE hit when refreshing AppData Restoration Dataset

DLPX-40032

Need to Support MySQL 5.6.26 Enterprise Commercial Version

DLPX-40031

ProcessExplorerTest should not expect a number of calls / call ordering

DLPX-40030

MySQL environment variable extraction broken on Solaris

DLPX-40004

MySQL DB_SYNC job hangs in replication stream state tests

DLPX-39957

MSSQL fix environment error handling

DLPX-39939

libiconv linker error for bash on sunos x86

DLPX-39886

Status script exit errors are not throwing faults.

DLPX-39865

ASE: Compatible repositories is broken for sybase

DLPX-39714

Staging Server Processor Continually Maxed at 100% CPU Utilization

DLPX-39703

CREATE_CONTROL_FILE_ERROR in V2P/DB_EXPORT

DLPX-39568

mds upgrade scripts for 4.3.1.0

DLPX-39540

AppData vFiles card boolean sliders are too long and card contents glitch and disappear

DLPX-39531

Quiesce MSSQL containers in parallel during upgrade

DLPX-39526

fix for DLPX-36370 accidentally reverted DLPX-37692

DLPX-39518

Ratio display as n/a in GUI

DLPX-39512

ASE Virtual Sources are not auto-enabled after self-service upgrade

DLPX-39503

4.2 format status script causes errors in 4.3.1

DLPX-39489

ASE ValidatedSync rollback logic should attempt to use UNMOUNT before falling back to DROP DATABASE

DLPX-39458

IllegalStateException thrown in DTraceDataCollector

DLPX-39440

Improve the role of data management toolkits in release process

DLPX-39436

CLI objname.js should only list APIs that are visible to the user

DLPX-39413

Don't leak notification channels when creating new APISessionDO for existing HttpSession

DLPX-39383

Unable to delete the failed action

DLPX-39342

Hook template can't be edited if it has % sign

DLPX-39237

mgmt service spuriously fails to start due to chown failure

DLPX-39209

Number of Hooks are inconsistent for Live Source GUI

DLPX-38889

MDS PENDING_UPDATE state incorrect for stable source DB

DLPX-40152

4.3.2.0 upgrade failed "dlpx_namespace_filesystem_mapping" does not exist

DelphixOS Fixes
Bug Number

Description

DLPX-39572

adding a DHCP address fails with a DFE

DLPX-39179

i/o larger than 1MB (from device removal) breaks mpt

DLPX-39167

ztest: hits vd->vdev_top_zap != 0 assertion when removing log device

72

Delphix User Guide 2016 Delphix

Release 4.3.1.0 Changes

Management Server Fixes
Bug
Number

Description

DLPX-39385

java.lang.RuntimeException: [class com.delphix.appliance.server.dco.host.WindowsHostDO] is not a valid BundleParam

initialization type.

DLPX-39384

NPE at system summary screen

DLPX-39358

CLONE - Configs with toolkit defined params should not be manually created or updated

DLPX-39352

Upgrade to 4.2.4.1 gets dSource out of NPM mode but associated filesystems are not mounted - mds state

DLPX-39351

Upgrade to 4.2.4.1 gets dSource out of NPM mode but associated filesystems are not mounted - zfs state

DLPX-39350

xpp validation fails when delphix database user does not have 'select any dictionary' privilege

DLPX-39348

MSSqlBackupSetTest lookupFirstFullDBBackupSetComplex2 can fail

DLPX-39317

Missing type during DynamicEnumParameter to Delphix constraint conversion

DLPX-39306

mds upgrade scripts for 4.3.0.3

DLPX-39277

Initial setup hangs on create domain with VirtualBox

DLPX-39274

Failure in forceSendReceiveTest

DLPX-39269

Existing AppData repositories in 4.2 and upgrade to 4.3 leads to duplicated repositories

DLPX-39249

Race between serialization point becoming inactive and reaper checking for holds

DLPX-39239

SMTP Configuration does not persist when set.

DLPX-39195

Initial setup can't proceed past Storage Setup or Setup Summary screens

DLPX-39114

Stack crashes when trying to create more than 800 worker threads

DLPX-39024

Replication fails with LDAP error on target, but user auth works

DLPX-38819

dsources should be taken out of performance mode on upgrade

DLPX-38818

It should not be possible to enable PerformanceMode on dSources

DLPX-38712

Remove cleanup hook from toolkit

DLPX-38703

mgmt smf startup failure sometimes leaves 'java' process running

DLPX-38699

EBS appsTier vFiles GUI card contents can overflow with a long INST_TOP value

DLPX-36278

Windows Appdata staging provision wizard slightly cuts off content on the right

DLPX-39528

mds upgrade scripts for 4.2.5.0

DLPX-39399

IllegalArgumentException while deleting jet stream data container

DLPX-39482

daoFactory.getsStorageContainer should return an Optional

DLPX-39502

Setup sometimes hangs on VirtualBox creating domain

DLPX-39522

Management stack crash when doing a resynchronize (redoBaseBackup) on postgres

Release 4.3.0.3 Changes

Management Server Fixes
Bug Number

Description

73

Delphix User Guide 2016 Delphix

DLPX-39224

EOL api whitelist

DLPX-39200

NPE in ObjectReaperTest

DLPX-39198

ant dev causes inconsistent schemas

DLPX-39174

Hooks UI does not show up in linking wizard

DLPX-39155

mds upgrade scripts for 4.3.0.2

DLPX-39147

Finding the first- and latest backup sets for an mssql timeflow grows very slow over time

DLPX-39138

Add JVM options to facilitate observability

DLPX-39134

mds upgrade scripts for 4.3.0.1

DLPX-39127

Enable RAC VPDB will fail with exception.oracle.dbc.database.notopen

DLPX-39107

Got Exception During Linking/SnapSync a dSource on MySQL 5.7 Installation with GTID Enabled

DLPX-39105

login screen should say IE8 is unsupported (not deprecated)

DLPX-38994

network analytic code is making too many DNS queries, blocks dtrace reading threads

DLPX-38993

analytics LocalTCPStatsCollector filling up info logs

DLPX-38872

Click Next button from Add dSource but did not go to next screen

DLPX-38858

IllegalArgumentException: No enum constant MSSqlDBContainerDO.ValidatedSyncMode.FULL_OR_INCREMENTAL

DLPX-38853

MSSQL 15k partitions support breaks 2005 test runs

DLPX-38851

MySQL 5.6.22 changes behavior of relay_log_recovery

DLPX-38714

Manifest files lost with MDS postgres upgrade to 9.4

DLPX-38705

Restoration Dataset sourceConfigs should be filtered from environment page and dSource wizard

DLPX-38701

oratab entries for RAC databases are not checked correctly

DelphixOS Fixes
Bug Number

Description

DLPX-39146

system hung waiting on free segment

Release 4.3.0.2 Changes

Management Server Fixes
Bug Number

Description

DLPX-39088

Uploading old appdata toolkit causes NPE in Gallifrey translators

DLPX-39080

Delphix Express registration is done twice

DLPX-39078

Delphix Express Update phone home to call home an hour after stack startup if first time or if it hasn't been a week

DLPX-39003

Remove toolkit script dump from user-visible exceptions

DLPX-38997

Warehouse Upgrade button is missing

DLPX-38969

Windows cluster refresh fails with script not found

DLPX-38835

GUI needs to hide migrate warehouse button

DLPX-38716

No hook operations for SQL Server VDBs

DLPX-38713

GUI different from documentation when showing hooks.

74

Delphix User Guide 2016 Delphix

DLPX-38696

MSSQL VDB refresh can fail trying to set recovery mode to 'UNKNOWN'

DLPX-38693

Getting Exception While Migrating a VDB to Remote Host

DLPX-38691

V2P and Provision buttons should be disabled for Conspro

DLPX-38686

unrevert DLPX-28695 sql upgrade scripts need to be valid HyperSQL and PostgreSQL at the same time

DLPX-38673

Unmount and unexport unused LUNs for mssql staging and target dbs

DLPX-38672

test_mssql_snapshot_dsource fails in nightly trunk run

Release 4.3.0.1 Changes

Management Server Fixes
Bug
Number

Description

DLPX-38959

mds upgrade scripts for 4.3.0.0

DLPX-38906

Upgrade script needed for hanging references fixed by DLPX-37621

DLPX-38877

NexusResetException treated as fatal again

DLPX-38873

AppData NFS mounting options should include "noac" when Additional Mount Points in use

DLPX-38852

java.lang.NullPointerException
com.delphix.appliance.node.webapp.ApplicationInitializer.onStartup(ApplicationInitializer.java:218)

DLPX-38842

Incorrect user used for tmp file during toolkit execution

DLPX-38815

Cannot add Unstructured Files to windows host

DLPX-38807

Tunable oracle.vdb.redolog_zfs_record_size_kb is not working

DLPX-38771

Migrate a warehouse to a different target and got NPE

DLPX-38711

AppData linking wizard summary screen has scrollbars with a long 'path to exclude'

DLPX-38707

Provision vFiles wizard Target Environment and Summary views don't show scrollbar with many dynamic params

DLPX-38697

Relax feature installation error handling to prevent warehouse lockout

DLPX-38681

CONSPRO needs to stop unsupported operations early

DLPX-38668

Provision VDB should remove uncheck number for cluster provision

DelphixOS Fixes
Bug Number

Description

DLPX-38822

Delphix VMs configured with DHCP networking default fail to configure network interfaces if no DHCP server is present

DLPX-38683

Device removal in 4.2 and upgrade to 4.3 results in reboot loop

Release 4.3.0.0 Changes

Delphix now supports MySQL as a data platform. To find additional information about MySQL, click MySQL to get started.
Delphix express is a free version of Delphix available to individuals and small team applications after registering on http://community.de
lphix.com. For additional information about Delphix Express, go to the Delphix Express Quick Start Guide.
Customers can now provision an instance of Oracle EBS in a single Jet Stream data container. Delphix will allow users to specify the
order of operations in which an entire application will be provisioned.To find additional information Jet Stream Ordered Sources, see Ord
ered Sources.
Users can now recover unmutated copies of data for restoration and backup on Oracle EBS in addition to provisioning data into non-prod
environments. To find additional information about Restoration Satasets for EBS, see Restoration Datasets.

75

Delphix User Guide 2016 Delphix

Delphix now uses CHAP authentication to secure iSCSI connections, which will eliminate the possibility of unauthorized connections. For
more information click iSCSI Configuration.
DSP integration with SOCKS leaves the firewall in control of applications and provides a clean connection across a firewall for data
transfer. F or more information, r efer to Configuring Network in Replication.
Delphix will now support SAP ASE on the AIX operating platform . Customers using ASE on AIX can now integrate Delphix with this
platform.
Delphix will fully support SAP ASE Version 16 with this update
Delphix now supports PostgreSQL 9.3 on OSes.
Delphix now supports PostgreSQL 9.4 on OSes.
Delphix now provides support for the AWS GovCloud region.
Users can customize the redo log size while provisioning a vdb and disabling the archive log mode. This will improve VDB provision time
and runtime performance.
Duplicate data source names are no longer allowed in JetStream. Existing duplicate names will be uniquified on upgrade.
JetStream users can now go back to the last snapshot before a REFRESH, RESTORE, or RESET operation.
Oracle 12c w/APEX users will no longer cause Unix to Linux validation to fail.
Cross-Site Request Forgery (CSRF) headers are now required on all browser requests. This is handled automatically by the Delphix GUI.
If you see a "403 Forbidden" error you may need to refresh the page or clear the browser cache.
The User Roles for accessing/viewing Delphix objects has changed. Please see User Roles for more details.
The IO Report Card has been modified to include IOPS, throughput (MBps) along with avg/min/max/stdev latency. For more info please
see the IO Report Card documentation.
Ignored faults will no longer be notified via email. Please see faults for more information on fault handling.
A warning will now be raised if an MSSQL Server source changes its recovery model.

Release 4.3 Known Issues

SAP ASE Issues
You may encounter issues with your ASE instances in the following cases:
ASE instances use case insensitive sort orders and file names are not specified/preserved in a case-preserving way.
ASE instances have multiple listeners and not all listeners can be used by the Delphix Engine.

Oracle 12c Pluggable Database Issues

When using an Oracle 12c pluggable database (PDB) with your Delphix Engine, the following features do not work as expected:
Virtual-to-Physical (V2P) functionality is not supported for PDBs.
Pre-provisioning is not supported for PDBs.
PDB source attach is not supported.
The initial SnapSync for a PDB is not resumable.
Linking and provisioning an entire CDB is not supported
Provisioning a PDB into a virtual CDB is not supported
XPP for multi-tenant databases is not supported
Provisioning a RAC PDB Data Source into a non-RAC CDB is only supported if the customer is on Oracle 12.2.0.2 and they have applied
an Oracle patch that fixes the following Oracle bug:
Bug 19637186: RAC OPTION MISMATCH PRODUCES ERROR VIOLATION DURING PDB PLUG IN

Cross-Platform Provisioning Issues

Unsupported Oracle Features
The Database Vault feature will cause cross-platform provisioning to fail.

Toolkit Scripts on *nix

Toolkit status scripts on *nix based systems may not upgrade correctly if they contain the character %. This will lead to the associated source
reporting being in an unknown state. A workaround exists where this problem can be fixed by uploading a new version of the toolkit after
upgrade. The DB2 toolkit is affected by this known issue.

76

Delphix User Guide 2016 Delphix

77

Delphix User Guide 2016 Delphix

Release 5.0-5.0.x.x Known Issues and Changes

Release 5.0.0.0 Changes
The Delphix Engine 5.0 provides a bounty of features, bug fixes, and performance improvements.
EBS Multi-node appsTier Support
Integrated Masking
Masked VDB Provisioning
Selective Data Distribution
DB2 Support
DB2 LUW
Better Data Security
Support for Encrypted Microsoft SQL Server Backups
Password-protected ASE Backups
Expanded Platform Support
Easy Oracle RAC Node Changes
Support for Oracle Custom Environment Variables
Expanded Version Support
ASE
Improved Jet Stream
Jet Stream Bookmark Cleaning
Multi-owner Data Containers
Technical Improvements
UX Change
Faster Start
Improved Masking Workflows
ZFS Improvements
Compressed ZFS Send/Receive
Windows Target Environments
Add Windows target environments w/ GUI

EBS Multi-node appsTier Support

Delphix can now support the automated deployment of EBS with multi-node application tiers, enabling the creation of non-production
environments that have multi-node topologies. To find additional information about EBS Multi-nodes, see Oracle EBS + Delphix: Conceptual
Overview.

Integrated Masking
Masked VDB Provisioning
You can now create masked copies of data at VDB provision time, using masking jobs defined on the masking engine that run when you provision
or refresh the VDB. It

is now even easier to mask copies of production and deliver secure data across teams. From
one streamlined workflow, admins can define how/what needs to be masked, who can access the data, and
distribute that masked data. To find additional information about masked VDB provisioning, see Provisioning
Masked VDBs.
Selective Data Distribution
You can now replicate masked data directly to a target Delphix engine, while ensuring unmasked sensitive
data does not leave the production site. This feature is critical for implementing a hybrid cloud deployment in which you want only
masked data in the cloud, as well as other cases in which you want only masked data in target systems, such as offshore QA and outsourced
analytics. For more information about selective data distribution, see Selective Data Distribution Overview.

78

Delphix User Guide 2016 Delphix

DB2 Support
DB2 LUW
DB2 LUW will be available on a single machine, single partition DBs on versions 10.1 and above. We will support customers on AIX 6.1+ and
Redhat 6.5+. For more information about DB2 LUW, see DB2 on Delphix: An Overview.

Better Data Security

Support for Encrypted Microsoft SQL Server Backups
Delphix enables you to load password-protected encrypted MSSQL backups taken by LiteSpeed and RedGate. You will also be able to use
point-in-time provisioning between snapshots. For more information about encrypted Microsoft SQL Server backups, see Advanced Data
Management Settings for SQL Server dSources.

Password-protected ASE Backups

Delphix now enables you to extract and load password-protected ASE backups. For more information about password-protected ASE backups,
see Linking an SAP ASE Data Source.

Expanded Platform Support

Easy Oracle RAC Node Changes
You can now add or remove nodes dynamically on Oracle RAC target host VDBs. For more information, see Provisioning Oracle VDBs: An
Overview.

Support for Oracle Custom Environment Variables

Delphix now allows you to dictate custom environment variables that you can set prior to any administrative action, such as provision, start, stop,
rollback, or refresh. For more information, see Provisioning an Oracle VDB.

Expanded Version Support

ASE
ASE 15.0.3 on AIX 5.3
ASE 15.5 on AIX 5.3
ASE 15.7 on AIX 6.1 and RHEL 5.6
Support for provisioning ASE 15.7 to multi-node Veritas clusters 5.1 on RHEL 5 & 6 (no failover support)
MySQL Enterprise Edition 5.6 support on Solaris 11, RHEL 6.2, 6.3, 6.4
For more details, visit Supported Operating Systems and Database Versions for SAP ASE.

Improved Jet Stream

Jet Stream Bookmark Cleaning
You can create expiration dates for your Jet Stream bookmarks, so the Delphix Engine will remove them automatically and reclaim space. For
more information about setting an expiration date for a bookmark, see Understanding Bookmarks and Working with Data Operations and
Sources in a Container.

Multi-owner Data Containers

Now Jet Stream users can share ownership of a single data container. For more information on multi-owner data containers, see Jet Stream
Data Concepts and Working with Data Operations and Sources in a Container.

79

Delphix User Guide 2016 Delphix

Technical Improvements
UX Change
Faster Start
For users with a large number of databases, application startup time will be significantly faster.

Improved Masking Workflows

The masking engine is integrated into one OVA. You can now associate masking jobs with a source. You can select masking jobs from a
drop-down menu and get started faster. For more information about masking workflows, see Delphix Masking Quick Start Guide - An Overview
.

ZFS Improvements
Compressed ZFS Send/Receive
Performance of replication across a WAN (for example, to the cloud) is now improved with send stream pre-compression. This will lower CPU use
and improve bandwidth in cases where CPU performance was a bottleneck, or where compression was not previously enabled for replication. All
replications are now sent compressed so there is no longer a "compressed" checkbox in the replication UI. There is no additional CPU cost,
because the data is compressed when it is first written, rather than as it is being replicated. Reported replication throughput may be lower
because the amount of compressed data sent is reported, rather than the amount of uncompressed data. For more information see, Configuring
Replication.

Windows Target Environments

Add Windows target environments w/ GUI
You can now add a Windows standalone target environment with the Delphix admin GUI, where you can specify a target hosts
address/port/credentials. For more information, see Adding a SQL Server Standalone Target Environment.

Release 5.0 Known Issues

SAP ASE Issues
You may encounter issues with your ASE instances in the following cases:
ASE instances use case insensitive sort orders and file names are not specified/preserved in a case-preserving way.
ASE instances have multiple listeners and not all listeners can be used by the Delphix Engine.

Oracle 12c Pluggable Database Issues

When using an Oracle 12c pluggable database (PDB) with your Delphix Engine, the following features do not work as expected:
Virtual-to-Physical (V2P) functionality is not supported for PDBs.
Pre-provisioning is not supported for PDBs.
PDB source attach is not supported.
The initial SnapSync for a PDB is not resumable.
Linking and provisioning an entire CDB is not supported
Provisioning a PDB into a virtual CDB is not supported
XPP for multi-tenant databases is not supported
LiveSource is not supported on linking a PDB dSource
Provisioning a RAC PDB Data Source into a non-RAC CDB is only supported if the customer is on Oracle 12.2.0.2 and they have applied
an Oracle patch that fixes the following Oracle bug:

80

Delphix User Guide 2016 Delphix

Bug 19637186: RAC OPTION MISMATCH PRODUCES ERROR VIOLATION DURING PDB PLUG IN

Cross-Platform Provisioning Issues

Unsupported Oracle Features
If Database Vault feature is enabled, cross-platform provisioning will fail.

Toolkit Scripts on *nix

Toolkit status scripts on *nix based systems may not upgrade correctly if they contain the character %. This will lead to the associated source
reporting being in an unknown state. A workaround exists where this problem can be fixed by uploading a new version of the toolkit after
upgrade. The DB2 toolkit is affected by this known issue.

81

Delphix User Guide 2016 Delphix

_QuickStart

82

Delphix User Guide 2016 Delphix

Quick Start Guide for The Delphix Engine

These topics describe the basic processes for setting up environments, setting up dSources, provisioning VDBs, and then deleting dSources and
VDBs.
These topics are excerpted from the larger user guide, and are intended to provide you with a quick overview of basic procedures for working with
database objects in the Delphix Engine. This guide does not cover setting up and configuring the Delphix Engine, and the requirements of your
installation and database platform may require more detailed instructions. We highly recommend that you read the topics linked from the topics in
this guide, as well as the conceptual overview topics included at the beginning of each chapter of the user guide, before undertaking complex
operations with the Delphix Engine.
Create a Group
SQL Server Quick Start Topics
Set Up a SQL Server Target Environment
Set Up a SQL Server Source Environment
Link a SQL Server Data Source
Provision a SQL Server VDB
Oracle Quick Start Topics
Set Up an Oracle Single Instance or RAC Environment
Link an Oracle Data Source
Provision an Oracle VDB
PostgreSQL Quick Start Topics
Add a PostgreSQL Environment
Link a PostgreSQL Data Source
Provision a PostgreSQL VDB
SAP ASE Quick Start Topics
Delete a VDB
Delete a dSource
Disable a dSource

83

Delphix User Guide 2016 Delphix

Oracle Quick Start Topics

These topics, which are excerpted from the larger User Guide, are intended to provide you with a quick overview of working with Oracle database
objects in the Delphix Engine. Before undertaking any of these procedures we strongly recommend that you read the topics in the Oracle
Support and Requirements section.
Set Up an Oracle Single Instance or RAC Environment
Link an Oracle Data Source
Provision an Oracle VDB

84

Delphix User Guide 2016 Delphix

Set Up an Oracle Single Instance or RAC Environment

Prerequisites
See the topics Requirements for Oracle Target Hosts and Databases and Supported Operating Systems and DBMS Versions for
Oracle Environments
There can be one Oracle unique database name (DB_UNIQUE_NAME) per Delphix Engine. For example, if you provision a VDB with a
database unique name "ABC" and later try to add an environment which has a source database that also has a database unique name of
"ABC", errors will occur.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the Plus icon next to Environments.
5. In the Add Environment dialog, select Unix/Linux.
6. Select Standalone Host or Oracle Cluster, depending on the type of environment you are adding.
7. For standalone Oracle environments enter the Host IP address.
8. For Oracle RAC environments, enter the Node Address and Cluster Home.
9. Enter an optional Name for the environment.
10. Enter the SSH port.
The default value is 22.
11. Enter a Username for the environment.
See Requirements for Oracle Target Hosts and Databases for more information on the required privileges for the environment user.
12. Select a Login Type.
For Password, enter the password associated with the user in Step 10.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

13. For Password Login, click Verify Credentials to test the username and password.
14. Enter a Toolkit Path.
The toolkit directory stores scripts used for Delphix Engine operations, and should have a persistent working directory rather than a
temporary one. The toolkit directory will have a separate sub-directory for each database instance. The toolkit path must have 0770
permissions and at least 345MB of free space.
15. Click OK.

Post-Requisites
After you create the environment, you can view information about it:
1. Click Manage.
2. Select Environments.
3. Select the environment name.

85

Delphix User Guide 2016 Delphix

Related Links
Requirements for Oracle Target Hosts and Databases
Supported Operating Systems and DBMS Versions for Oracle Environments

86

Delphix User Guide 2016 Delphix

Link an Oracle Data Source

This topic describes the process of linking to a source database and creating a dSource.
Prerequisites
Procedure
Related Links

Prerequisites
Make sure you have the correct user credentials for the source environment, as described in Requirements for Oracle Target Hosts
and Databases.
If you are linking a dSource to an Oracle or Oracle RAC physical standby database, you should read the topic Linking Oracle Physical
Standby Databases.
If you are using Oracle Enterprise Edition, you must have Block Change Tracking (BCT) enabled as described in Requirements for
Oracle Source Hosts and Databases.
The source database should be in ARCHIVELOG mode and the NOLOGGING option should be disabled as described in Requirements
for Oracle Source Hosts and Databases.
You may also want to read the topic Advanced Data Management Settings for Oracle dSources.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Select Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing Oracle Environment Users.

6. Enter your login credentials for the source database and click Verify Credentials.
If you are linking a mounted standby, click Advanced and enter non-SYS login credentials as well. Click Next. See the topics under Link
ing Oracle Physical Standby Databases for more information about how the Delphix Engine uses non-SYS login credentials.
7. In Add dSource/Add Environment wizard, the Toolkit Path can be set to /tmp (or any unused directory).
8. Select a Database Group for the dSource, and then click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. See the topics under Users, Permissions, and Policies for more information.
9. Select an Initial Load option.
By default, the initial load takes place upon completion of the linking process. Alternatively, you can set the initial load to take place
according to the SnapSync policy, for example if you want the initial load to take place when the source database is not in use, or after a
set of operations have taken place.
10. Select whether the data in the database is Masked.
This setting is a flag to the Delphix Engine that the database data is in a masked state. Selecting this option will not mask the data.
11. Select a SnapSync policy.
See Advanced Data Management Settings for Oracle dSources for more information.
12. Click Advanced to edit LogSync, Validated Sync, and Retention policies.
See Advanced Data Management Settings for Oracle dSources for more information.
13. Click Next.
14. Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card, and also make modifications to its policies

87

Delphix User Guide 2016 Delphix

and permissions. In the Databases panel, click on the Open icon to view the front of the dSource card. The card will then flip, showing
you information such as the Source Database and Data Management configuration. For more information, see Advanced Data
Management Settings for Oracle dSources .

Related Links
Advanced Data Management Settings for Oracle dSources
Requirements for Oracle Source Hosts and Databases
Requirements for Oracle Target Hosts and Databases
Linking dSources from an Encrypted Oracle Database
Linking Oracle Physical Standby Databases
Users, Permissions, and Policies
Managing Oracle Environment Users

88

Delphix User Guide 2016 Delphix

Provision an Oracle VDB

Prerequisites
You will need to have linked a dSource from a source database, as described in Linking an Oracle Data Source, or have already
created a VDB from which you want to provision another VDB
You will need to have the correct OS User privileges on the target environment, as described in Requirements for Oracle Target Hosts
and Databases
If you want to use customized database configuration settings, first create a VDB Config Template as described in Customizing Oracle
VDB Configuration Settings
If you are creating a VDB from a dSource linked to an encrypted database, make sure you have copied the wallet file to the target
environment as described in Provisioning a VDB from an Encrypted Oracle Database

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource.
6. Select a dSource snapshot.
See Provisioning by Snapshot and LogSync in this topic for more information on provisioning options.
You can take a snapshot of the dSource to provision from by clicking theCamera icon on the dSource card.

7. Optional: Slide the LogSync slider to the open the snapshot timeline, and then move the arrow along the timeline to provision from a
point of time within a snapshot.
You can provision from the most recent log entry by opening the snapshot timeline, and then click the red Arrow icon next to
the LogSync Slider.

8. Click Provision.
The Provision VDB panel will open, and the fields Installation Home,Database Unique Name, SID, Database Name, Mount Base,
andEnvironment User will auto-populate with information from the dSource.
9. If you need to add a new target environment for the VDB, click the green Plusicon next to the Filter Target field, and follow the
instructions in Adding an Oracle Single Instance or RAC Environment.
10. Review the information for Installation Home, Database Unique Name, SID, and Database Name and edit as necessary.
11. Review the Mount Base and Environment User and edit as necessary.
The Environment User must have permissions to write to the specified Mount Base, as described in Requirements for Oracle Target
Hosts and Databases. You may also want to create a new writeable directory in the target environment with the correct permissions,
and use that as the Mount Base for the VDB.
12. Select Provide Privileged Credentials if you want to use login credentials on the target environment other than those associated with
the Environment User.
13. Click Advanced to select Oracle Node Listeners or enter any VDB configuration settings or file mappings.
For more information, see Customizing Oracle VDB Configuration Settings and Customizing VDB File Mappings.
If you are provisioning to a target environment that is running a Linux OS, you will need to compare the SGA_TARGET configur
ation parameter with the shared memory size in /dev/shm. The shared memory configured on the target host should match
the SGA memory target. You can check this by opening the Advanced settings, and then finding the value for SGA_TARGETun
der DB Configuration.

14. Click Next.

15. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
16. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
17.
89

Delphix User Guide 2016 Delphix

17. Click Next.

18. Enter any operations that should be run at Hooks during the provisioning process.
For more information, see Customizing Oracle Management with Hook Operations.
19. Click Next.
20. Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the
VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database and its Data
Management settings.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any particular snapshot, either by time or SCN.
Provisioning
By
Snapshot

Description

Provision by
Time

You can provision to the start of any snapshot by selecting that snapshot card from the Timeflow view, or by entering a value in
the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.

Provision by
SCN

You can use the Slide to Provision by SCN control to open the SCN entry field. Here, you can type or paste in the SCN you
want to provision to. After entering a value, it will "snap" to the start of the closest appropriate snapshot.

When provisioning by LogSync information, you can provision to any point in time, or to any SCN , within a particular snapshot. The TimeFlow
view for a dSource shows multiple snapshots by default. To view the LogSync data for an individual snapshot, use the Slide to Open LogSync c
ontrol at the top of an individual snapshot card.
Provisioning
By LogSync

Description

Provision
bySCN

Use the Slide to Open LogSync and Slide to Provision bySCN controls to view the range of SCNs within that
snapshot.Drag the red triangle to the LSN that you want to provision from. You can also type or paste in the specific SCN you
want to provision to. Note that if the SCN doesn't exist, you will see an error when you provision.

Provision by
Time

Use the Slide to Open LogSync control to view the time range within that snapshot. Drag the red triangle to the point in time
that you want to provision from. You can also enter a date and time directly.

Related Links
Linking an Oracle Data Source
Requirements for Oracle Target Hosts and Databases
Customizing Oracle VDB Configuration Settings
Provisioning a VDB from an Encrypted Oracle Database
Adding an Oracle Single Instance or RAC Environment
Customizing VDB File Mappings

90

Delphix User Guide 2016 Delphix

PostgreSQL Quick Start Topics

These topics, which are excerpted from the larger User Guide, are intended to provide you with a quick overview of working with PostgreSQL data
sources in the Delphix Engine. Before undertaking any of these procedures we strongly recommend that you read the topics in the PostgreSQL
Support and Requirements section.
Add a PostgreSQL Environment
Link a PostgreSQL Data Source
Provision a PostgreSQL VDB

91

Delphix User Guide 2016 Delphix

Add a PostgreSQL Environment

This topic describes how to add a PostgreSQL source environment to the Delphix Engine.

Prerequisites
Make sure your environment meets the requirements described in the following topics:
Requirements for PostgreSQL Source Hosts and Databases
Requirements for PostgreSQL Target Hosts and Databases
Supported Operating Systems and Database Versions for PostgreSQL Environments

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Unix/Linux in the operating system menu.
6. Select Standalone Host.
7. Enter the Host IP address.
8. Enter an optional Name for the environment.
9. Enter the SSH port.
The default value is 22.
10. Enter a Username for the environment.
For more information about the environment user requirements, see Requirements for PostgreSQL Target Hosts and Databases and
Requirements for PostgreSQL Source Hosts and Databases.
11. Select a Login Type.
For Password, enter the password associated with the user in Step 9.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

12. For Password Login, click Verify Credentials to test the username and password.
13. Enter a Toolkit Path.
See Requirements for PostgreSQL Target Hosts and Databases and Requirements for PostgreSQL Source Hosts and Databases
for more information about the toolkit directory requirements.
14. Click OK.
As the new environment is added, you will see two jobs running in the Delphix Admin Job History, one to Create and Discover an
environment, and another to Create an environment. When the jobs are complete, you will see the new environment added to the list in
the Environments panel. If you don't see it, click the Refresh icon in your browser.

Post-Requisites
After you create the environment, you can view information about it by selecting Manage > Environments, and then select the
environment name.

92

Delphix User Guide 2016 Delphix

Related Links
Setting Up PostgreSQL Environments: An Overview
Requirements for PostgreSQL Source Hosts and Databases
Requirements for PostgreSQL Target Hosts and Databases
Supported Operating Systems and Database Versions for PostgreSQL Environments
Adding an Installation to a PostgreSQL Environment

93

Delphix User Guide 2016 Delphix

Link a PostgreSQL Data Source

This topic describes the basic procedure for linking a dSource from a PostgreSQL database to the Delphix Engine.

Prerequisites
Make sure you have the correct user credentials for the source environment, as described in Requirements for PostgreSQL Source
Hosts and Databases
You may also want to read the topic Advanced Data Management Settings for PostgreSQL Data Sources.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Select Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing PostgreSQL Environment Users.

6. Enter your login credentials for DB Cluster User and DB Cluster Password.
7. Click Advanced to enter a Connection Database.
The Connection Database will be used when issuing SQL queries from the Delphix Engine to the linked database. It can be any existing
database that the DB Cluster User has permission to access.
8. Click Next.
9. Select a Database Group for the dSource, and then click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. See the topics under Users, Permissions, and Policies for more information.
10. Select a SnapSync Policy, and, if necessary, a Staging Installation for the dSource.
The Staging installation represents the PostgreSQL binaries that will be used on the staging target to backup and restore the linked
database to a warm standby.
11. Click Advanced to select whether the data in the data sources is Masked, to select a Retention Policy, and to indicate whether any pre
or post scripts should be executed during the dSource creation.
For more information, see Advanced Data Management Settings for PostgreSQL Data Sources and Using Pre- and Post-Scripts
with PostgreSQL dSources.
12. Click Next.
13. Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card, and also make modifications to its policies
and permissions. In the Databases panel, click on the Open icon to view the front of the dSource card. The card will then flip, showing
you information such as the Source Database and Data Management configuration. For more information, see Advanced Data
Management Settings for PostgreSQL Data Sources.

Related Links
Advanced Data Management Settings for PostgreSQL Data Sources
Requirements for PostgreSQL Target Hosts and Databases
Using Pre- and Post-Scripts with PostgreSQL dSources
Users, Permissions, and Policies

94

Delphix User Guide 2016 Delphix

95

Delphix User Guide 2016 Delphix

Provision a PostgreSQL VDB

This topic describes how to provision a virtual database (VDB) from a PostgreSQL dSource.

Prerequisites
You will need to have linked a dSource from a source database, as described in Linking a PostgreSQL dSource, or have already
created a VDB from which you want to provision another VDB

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource.
6. Select a dSource snapshot.
See Provisioning by Snapshot and LogSync in this topic for more information on provisioning options.
You can take a snapshot of the dSource to provision from by clicking the Camera icon on the dSource card.

7. Optional: Slide the LogSync slider to the open the snapshot timeline, and then move the arrow along the timeline to provision from a
point in time within a snapshot.
8. Click Provision.
The VDB Provisioning Wizard will open, and the fields Installation, Mount Base, and Environment User will auto-populate with
information from the environment configuration.
9. Enter a Port Number.
The TCP port upon which the VDB will listen.
10. Click Advanced to enter any VDB configuration settings.
For more information, see Customizing PostgreSQL VDB Configuration Settings.
11. Click Next to continue to the VDB Configuration tab.
12. Modify the VDB Name if necessary.
13. Select a Target Group for the VDB.
14. Click the green Plus icon to add a new group, if necessary.
15. Select a Snapshot Policy for the VDB.
16. Click the green Plus icon to create a new policy, if necessary.
17. Click Next to continue to the Hooks tab.
18. Specify any Hooks to be used during the provisioning process.
For more information, see Customizing PostgreSQL Management with Hook Operations.
19.

Click Next to continue to the Summary tab.

20. Click Finish.

When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the
VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database and its Data
Management settings.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any snapshot by selecting that snapshot card from the Timeflow view, or by
entering a value in the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.
When provisioning by LogSync information, you can provision to any point in time within a particular snapshot. The TimeFlow view for a dSource
shows multiple snapshots by default. To view the LogSync data for an individual snapshot, use the Slide to Open LogSync control at the top of
an individual snapshot card to view the time range within that snapshot. Drag the red triangle to the point in time that you want to provision from.
You can also enter a date and time directly.

96

Delphix User Guide 2016 Delphix

Related Links
Linking a PostgreSQL dSource
Requirements for PostgreSQL Target Hosts and Databases
Using Pre- and Post-Scripts with dSources and VDBs
Customizing PostgreSQL VDB Configuration Settings

97

Delphix User Guide 2016 Delphix

MySQL Quick Start Topics

These topics, which are excerpted from the larger User Guide, are intended to provide you with a quick overview of working with MySQL
database objects in the Delphix Engine. Before undertaking any of these procedures we strongly recommend that you read the topics in the MyS
QL Support and Requirements section.

98

Delphix User Guide 2016 Delphix

Add a MySQL Environment

This topic describes how to add a MySQL source environment to the Delphix Engine.

Prerequisites
Make sure your environment meets the requirements described in the following topics:
Requirements for MySQL Source Hosts and Databases
Requirements for MySQL Target/Staging Hosts and Databases
Supported Operating Systems and Database Versions for MySQL Environments

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Unix/Linux in the operating system menu.
6. Select Standalone Host.
7. Enter the Host IP address.
8. Enter an optional Name for the environment.
9. Enter the SSH port.
The default value is 22.
10. Enter a Username for the environment.
For more information about the environment user requirements, see Requirements for MySQL Target/Staging Hosts and Databases a
nd Requirements for MySQL Source Hosts and Databases.
11. Select a Login Type.
For Password, enter the password associated with the user in step 9.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

12. For Password Login, click Verify Credentials to test the username and password.
13. Enter a Toolkit Path.
For more information about the toolkit directory requirements, see Requirements for MySQL Target/Staging Hosts and Databases an
d Requirements for MySQL Source Hosts and Databases.
14. Click OK.
As the new environment is added, you will see two jobs running in the Delphix Admin Job History, one to Create and Discover an
environment, and another to Create an environment. When the jobs are complete, you will see the new environment added to the list in
the Environments tab. If you do not see it, click the Refresh icon in your browser.

Post-Requisites
To view information about an environment after you have created it:
1. Click Manage.
2.
99

Delphix User Guide 2016 Delphix

2. Select Environments.
3. Select the environment name.

Related Links
Setting Up MySQL Environments: An Overview
Requirements for MySQL Source Hosts and Databases
Requirements for MySQL Target/Staging Hosts and Databases
Supported Operating Systems and Database Versions for MySQL Environments
Adding an Installation to a MySQL Environment

100

Delphix User Guide 2016 Delphix

Link a MySQL dSource

This topic describes the basic procedure for linking a dSource from a MySQL database to the Delphix Engine.

Prerequisites
Make sure you have the correct user credentials for the source environment, as described in Requirements for MySQL Source Hosts
and Databases
You may also want to read the topic Advanced Data Management Settings for MySQL Data Sources.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing MySQL Environment Users.

6. Enter your login credentials for DB Username and DB Password.

7. Click Next.
8. Select a Database Group for the dSource.
9. Click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies.
10. Select the Initial Load type.
a. If selecting Existing MySQL Backup, provide the Path to the backup and select the Dump Type.
11. Select a SnapSync Policy, a Staging Installation, and a Staging Port for the dSource.
The Staging installation represents the MySQL binaries that will be used on the staging target to backup and restore the linked
database to a replication slave.
12. If you want to enable LogSync, check the LogSync checkbox.
13. Click Advanced to select a Retention Policy and to manually specify replication coordinates.
For more information, see Advanced Data Management Settings for MySQL Data Sources.
14. Click Next.
15. Specify any operations to run before and after the initial sync.
For more information, see Using Pre- and Post-Scripts with MySQL dSources.
16. Click Next.
17. Review the dSource Configuration and Data Management information.
18. Click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active Jobs in
the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will change to a
dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card, and also make modifications to its policies
and permissions. In the Databases panel, click the Open icon to view the front of the dSource card. The card will then flip, showing you
information such as the Source Database and Data Management configuration. For more information, see Advanced Data
Management Settings for MySQL Data Sources.

Related Links

101

Delphix User Guide 2016 Delphix

Requirements for MySQL Source Hosts and Databases

Advanced Data Management Settings for MySQL Data Sources
Managing MySQL Environment Users
Requirements for MySQL Target/Staging Hosts and Databases
Using Pre- and Post-Scripts with MySQL dSources
Users, Permissions, and Policies

102

Delphix User Guide 2016 Delphix

Provision a MySQL VDB

This topic describes how to provision a virtual database (VDB) from a MySQL dSource.

Prerequisites
You must have already:
linked a dSource from a source database, as described in Linking a MySQL dSource
or,
created a VDB from which you want to provision another VDB

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Click My Databases.
4. Select a dSource.
5. Select a dSource snapshot.
For more information on provisioning options, see Provisioning by Snapshot or LogSync below.
6. Optional: Slide the LogSync slider to open the snapshot timeline, and then move the arrow along the timeline to provision from a point
in time within a snapshot.
7. Click Provision.
The VDB Provisioning Wizard will open, and the fields Installation, Mount Base, and Environment User will auto-populate with
information from the environment configuration.
8. Enter a Port Number. This is the TCP port upon which the VDB will listen.
9. Click Advanced followed by clicking the green Plus icon (Add Parameter) to add new or update existing VDB configuration settings on
the template provided.
For more information, see Customizing MySQL VDB Configuration Settings.
10. Click Next to continue to the VDB Configuration tab.
11. Modify the VDB Name if necessary.
12. Select a Target Group for the VDB.
13. If necessary, click the green Plus icon to add a new group.
14. Select a Snapshot Policy for the VDB.
15. If necessary, click the green Plus icon to create a new policy.
16. Click on LogSync option to enable LogSync process for point-in-time provisioning/refresh.
17. Click Next to continue to the Hooks tab.
18. Specify any Hooks to be used during the provisioning process.
For more information, see Customizing MySQL Management with Hook Operations.
19.

Click Next to continue to the Summary tab.

20. Verify all the information displayed for the VDB is correct.
21. Click Finish.
When provisioning starts, you can view progress of the job in the Databases panel or in the Job History panel of the Dashboard. When
provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the VDB in the Da
tabases panel and click the Open icon, you can view its card, which contains information about the database and its Data Management settings.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any snapshot by selecting that snapshot card from the Timeflow view, or by
entering a value in the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.
When provisioning by LogSync information, you can provision to any point in time within a particular snapshot. The TimeFlow view for a dSource
shows multiple snapshots by default. To view the LogSync data for an individual snapshot, use the Slide to Open LogSync control at the top of
an individual snapshot card to view the time range within that snapshot. Drag the red triangle to the point in time from which you want to provision.
You can also enter a date and time directly.

103

Delphix User Guide 2016 Delphix

Related Links
Linking a MySQL dSource
Requirements for MySQL Target/Staging Hosts and Databases
Using Pre- and Post-Scripts with dSources and VDBs
Customizing MySQL VDB Configuration Settings

104

Delphix User Guide 2016 Delphix

SQL Server Quick Start Topics

These topics, which are excerpted from the larger User Guide, are intended to provide you with quick overview of how to work with SQL Server
database objects in the Delphix Engine. Before undertaking any of these procedures we strongly recommend that you read the topics in the SQL
Server Support and Requirements section.
Set Up a SQL Server Target Environment
Set Up a SQL Server Source Environment
Link a SQL Server Data Source
Provision a SQL Server VDB

105

Delphix User Guide 2016 Delphix

Set Up a SQL Server Target Environment

This topic describes how to add a SQL Server standalone target environment to the Delphix Engine.
Prerequisites
Procedure
Post-Requisites
Related Links
As explained in Setting Up SQL Server Environments: An Overview, you can use SQL Server targets for three purposes in a Delphix Engine
deployment:
They can host a target environment for the provisioning of Virtual Databases (VDBs)
They can host a staging database for a linked dSource and run the validated sync process
They can serve as a proxy host for database discovery on source hosts
Regardless of the specific purpose, all Windows targets must have the Delphix Connector installed to enable communication between the host
and the Delphix Engine. The instructions in this topic cover initiating the Add Target process in the Delphix Engine interface, running the Delphix
Connector installer on the target machine, and then verifying that the target has been added in the Delphix Engine interface.

Prerequisites
Make sure that your target environment meets the requirements described in Requirements for SQL Server Target Hosts and
Databases.
On the Windows machine that you want to use as a target, you will need to download the Delphix Connector software through the
Delphix Engine interface, install it and then register that machine with the Delphix Engine.

Procedure
Flash Player Required for Connector Download
A Flash player must be available on the target host to download the Delphix Connector when using the Delphix GUI. If the target host
does not have a Flash player installed, you can download the connector directly from the Delphix Engine by navigating to this URL: ht
tp://<name of your Delphix Engine>/connector/DelphixConnectorInstaller.msi
1. From the machine that you want to use as a target, start a browser session and connect to the Delphix Engine GUI using the
delphix_admin login.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Windows in the operating system menu.
6. Select Target.
7. Select Standalone.
8. Click the download link for the Delphix Connector Installer.
The Delphix Connector will download to your local machine.
9. On the Windows machine that you want to want to use as a target, run the Delphix Connector installer. Click Next to advance through
each of the installation wizard screens.
The installer will only run on 64-bit Windows systems. 32-bit systems are not supported.

a. For Connector Configuration, make sure there is no firewall in your environment blocking traffic to the port on the target
environment that the Delphix Connector service will listen to.
b. For Select Installation Folder, either accept the default folder, or click Browse to select another.
c. Click Next on the installer final 'Confirm Installation' dialog to complete the installation process and then Close to exit the Delphix
Connector Install Program.
10. Return to the Delphix Engine interface.
11. Enter the Host Address, Username, and Password for the target environment.
12. Click Validate Credentials.
13. Click OK to complete the target environment addition request.

106

Delphix User Guide 2016 Delphix

13.
14. As the new environment is added, you will see two jobs running in the Delphix Admin Job History, one to Create and Discover an
environment, and another to Create an environment. When the jobs are complete, you will see the new environment added to the list in
the Environments panel.

Post-Requisites
1. On the target machine, in the Windows Start Menu, click Services.
2. Select Extended Services.
3. Ensure that the Delphix Connector service has a Status of Started.
4. Ensure that the Startup Type is Automatic.

Related Links
Setting Up SQL Server Environments: An Overview
Requirements for SQL Server Target Hosts and Databases

107

Delphix User Guide 2016 Delphix

Set Up a SQL Server Source Environment

This topic describes how to add a SQL Server source environment.

Prerequisites
You must have already set up SQL Server target environments, as described in Adding a SQL Server Standalone Target
Environment
You will need to specify a target environment that will act as a proxy for running SQL Server instance and database discovery on
the source, as explained in Setting Up SQL Server Environments: An Overview
Make sure your source environment meets the requirements described in Requirements for SQL Server Target Hosts and Databases

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Windows in the operating system menu.
6. Select Source.
a. If you are adding a Windows Server Failover Cluster (WSFC), add the environment based on which WSFC feature the source
databases use:
i. Failover Cluster Instances
Add the environment as a standalone source using the cluster name or address.
ii. AlwaysOn Availability Groups
Add the environment as a cluster source using the cluster name or address.
b. Otherwise, add the environment as a standalone source.
7. Select a Connector Environment.
Connector environments are used as proxy for running discovery on the source. If no connector environments are available for selection,
you will need to set them up as described in Adding a SQL Server Standalone Target Environment. Connector environments must:
have the Delphix Connector installed
be registered with the Delphix Engine from the host machine where they are located.
8. Enter the Host Address, Username, and Password for the source environment.
9. Click Validate Credentials.
10. Click OK, and then click Yes to confirm the source environment addition request.
As the new environment is added, you will see multiple jobs running in the Delphix Admin Job History to Create and Discover an
environment. In addition, if you are adding a cluster environment, you will see jobs to Create and Discover each node in the cluster and
their corresponding hosts. When the jobs are complete, you will see the new environment added to the list in the Environments panel. If
you don't see it, click the Refresh icon.

Related Links
Setting Up SQL Server Environments: An Overview
Adding a SQL Server Standalone Target Environment
Adding a SQL Server Failover Cluster Target Environment
Requirements for SQL Server Target Hosts and Databases

108

Delphix User Guide 2016 Delphix

Link a SQL Server Data Source

This topic describes how to link a dSource from a Microsoft SQL Server database.
Prerequisites
Procedure
Related Links

Prerequisites
Be sure that the source database meets the requirements described in Requirements for SQL Server Target Hosts and Databases
You must have already set up a staging target environment as described in Setting Up SQL Server Environments: An Overview and A
dding a Windows Target Environment
Maximum Size of a Database that Can Be Linked
If the staging environment uses the Windows 2003 operating system, the largest size of database that you can link to the
Delphix Engine is 2TB. This is also the largest size to which a virtual database (VDB) can grow.
For all other Windows versions, the maximum size for databases and VDBs is 32TB.
In both cases, the maximum size of the database and resulting VDBs is determined by the operating system on the staging target host.

Failover cluster environments cannot be used for staging

When linking a dSource, you cannot use SQL Server failover cluster instances as staging instances. When linking, select a standalone
SQL Server instance to use.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials or as the owner of the database from which you want to
provision the dSource.
2. Click Manage.
3. Select Databases.
4. Select Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing SQL Server Environment Users.

6. Enter your login credentials for the source database.

7. Click Verify Credentials.
8. Click Next.
9. Select a Database Group for the dSource.
10. Click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies .
If your data source name contains non-ASCII characters, you will need to change the default dSource name to something that
uses only ASCII characters.

11. Select the method for the Initial Load.

For details on initial load options, see Linking a dSource from a SQL Server Database: An Overview .
12. Enter a backup path from which the source database backups will be available for the Delphix Engine to restore. A backup path follows
a UNC naming convention as: \\hostname\sharename\possible additional directory
Alternatively, select Autodiscover to have the Delphix Engine automatically locate the backups by querying MSDB.
13. Select the target environment for creating the staging database for validated sync.
14.
109

Delphix User Guide 2016 Delphix

14. Select a standalone SQL Server instance on the target environment for hosting the staging database.
15. Select whether the data in the database is Masked.
16. Select whether you want LogSync enabled for the dSource. For more information, see Advanced Data Management Settings for SQL
Server dSources.
LogSync Disabled by Default
For SQL Server data sources, LogSync is disabled by default. For more information about how LogSync functions with SQL
Server data sources, see Managing SQL Server Data Sources.

17. Cl ick Advanced to edit retention policies and specify pre- and post-scripts. For details on pre- and post-scripts, refer to Customizing
SQL Server Management with Pre- and Post-Scripts. Additionally, if the source database's backups use LiteSpeed or RedGate
password protected encryption, you can supply the encryption key the Delphix Engine should use to restore those backups.
18. Click Next.
19. Review the dSource Configuration and Data Management information.
20. Click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync. You can monitor these jobs by clicking Active Jobs in
the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the database icon will change to a dSou
rce icon on the Environments > Databases screen, and the dSource will appear in the list of My Databases under its assigned group.
You can view the current state of Validated Sync for the dSource on the dSource card itself.
The dSource Card
After you have created a dSource, the dSource card allows you to view information about it and make modifications to its policies and
permissions. In the Databases panel, click the Open icon to view the front of the dSource card. You can then flip the card to see
information such as the Source Database and Data Management configuration. For more information, see the topic Advanced Data
Management Settings for SQL Server dSources.

Related Links
Users, Permissions, and Policies
Setting Up SQL Server Environments: An Overview
Linking a dSource from a SQL Server Database: An Overview
Advanced Data Management Settings for SQL Server dSources
Adding a SQL Server Standalone Target Environment
Requirements for SQL Server Target Hosts and Databases
Using Pre- and Post-Scripts with SQL Server dSources

110

Delphix User Guide 2016 Delphix

Provision a SQL Server VDB

Prerequisites
You will need to have linked a dSource from a source database, as described in Linking a SQL Server dSource, or have already
created a VDB from which you want to provision another VDB.
You should already have set up Windows target environments and installed the Delphix Connector on them, as described in Adding a
SQL Server Standalone Target Environment.
Make sure you have the required privileges on the target environment as described in Requirements for SQL Server Target Hosts and
Databases.
If you are provisioning to a different target environment than the one where the staging database has been set up, you need to make sure
that the two environments have compatible operating systems, as described in Requirements for SQL Server Target Hosts and
Databases. For more information on the staging database and the validated sync process, see Setting Up SQL Server Environments:
An Overview.

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource.
6. Select a means of provisioning.
See Provisioning by Snapshot and LogSync in this topic for more information.
7. Click Provision.
The Provision VDB panel will open, and the Database Name and Recovery Model will auto-populate with information from the
dSource.
8. Select a target environment from the left pane.
9. Select an Instance to use.
10. If the selected target environment is a Windows Failover Cluster environment, select a drive letter from Available Drives. This drive will
contain volume mount points to Delphix storage.
11. Specify any Pre or Post Scripts that should be used during the provisioning process.
For more information, see Using Pre- and Post-Scripts with SQL Server dSources.
12. Click Next.
13. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
14. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
15. Click Next.
16. If your Delphix Engine system administrator has configured the Delphix Engine to communicate with an SMTP server, you will be able to
specify one or more people to notify when the provisioning is done. You can choose other Delphix Engine users, or enter email
addresses.
17. Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the
VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database and its Data
Management settings.

You can select a SQL Server instance that has a higher version than the source database and the VDB will be automatically upgraded.
For more information about compatibility between different versions of SQL Server, see SQL Server Operating System Compatibility
Matrices.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any particular snapshot, either by time or LSN.
You can take a new snapshot of the dSource and provision from it by clicking the Camera icon on the dSource card.

111

Delphix User Guide 2016 Delphix

Provisioning
By
Snapshot

Description

Provision by
Time

You can provision to the start of any snapshot by selecting that snapshot card from the TimeFlow view, or by entering a value
in the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.

Provision by
LSN

You can use the Slide to Provision by LSN control to open the LSN entry field. Here, you can type or paste in the LSN you
want to provision to. After entering a value, it will "snap" to the start of the closest appropriate snapshot.

If LogSync is enabled on the dSource, you can provision by LogSync information. When provisioning by LogSync information, you can provision
to any point in time, or to any LSN, within a particular snapshot. The TimeFlow view for a dSource shows multiple snapshots by default. To view
the LogSync data for an individual snapshot, use the Slide to Open LogSync control at the top of an individual snapshot card.
Provisioning
By LogSync

Description

Provision by
Time

Use the Slide to Open LogSync control to view the time range within that snapshot. Drag the red triangle to the point in time
that you want to provision from. You can also enter a date and time directly.

Provision by
LSN

Use the Slide to Open LogSync and Slide to Provision by LSN controls to view the range of LSNs within that snapshot. You
must type or paste in the specific LSN you want to provision to. Note that if the LSN doesn't exist, you will see an error when
you provision.

Related Links
Linking a SQL Server dSource
Adding a SQL Server Standalone Target Environment
Adding a SQL Server Failover Cluster Target Environment
Requirements for SQL Server Target Hosts and Databases
Setting Up SQL Server Environments: An Overview
Using Pre- and Post-Scripts with dSources and SQL Server VDBs

112

Delphix User Guide 2016 Delphix

SAP ASE Quick Start Topics

113

Delphix User Guide 2016 Delphix

Add an SAP ASE Environment

Prerequisites
See Requirements for SAP ASE Source Hosts and Databases.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the Plus icon next to Environments.
5. In the Add Environment dialog, select Unix/Linux.
6. Select Standalone Host.
7. Enter the Host IP address.
8.

Enter an optional Name for the environment.

9. Enter the SSH port.

The default value is 22.
10. Enter a Username for the environment.
11.

Select a Login Type.

12. For Password, enter the password associated with the user in Step 10.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

13. For Password Login, click Verify Credentials to test the username and password.
14. Enter a Toolkit Path.
The toolkit directory stores scripts used for Delphix Engine operations. It must have a persistent working directory rather than a temporary
one. The toolkit directory will have a separate sub-directory for each database instance. The toolkit path must have 0770 permissions.
15. Click the Discover SAP ASE checkbox.
16. Enter a Username for an instance on the environment.
17. Enter the Password associated with the user in Step 15.
18. Click OK.

Post-Requisites
After you create the environment, you can view information about it by selecting Manage > Environments and then selecting the environment
name.

Related Links
Link an SAP ASE Data Source

114

Delphix User Guide 2016 Delphix

Link an SAP ASE Data Source

This topic describes the process of linking to a source database and creating a dSource.
Prerequisites
Procedure
Related Links

Prerequisites
1. Ensure a correct set up the source and target environment, as described in Managing SAP ASE Environments
2. Before you can link a data source in a Veritas Cluster Server (VCS) environment, the following static configuration parameter for Delphix
engine needs to be manually added by a support contact to avoid failure. This is because each node in a VCS environment typically
has more than one IP address for fail over purposes. By default, the Delphix engine will only interface with a single IP address from the
source host, unless the following configuration is added:
PRO.RESTRICT_TARGET_IP=false
3. The Delphix engine configuration must be modified and can be found with the following path name:
/var/delphix/server/etc/delphix_config_override.properties
4. Finally, the Delphix engine stack needs to be manually restarted in order for the new configuration to take effect.

Dump file requirements

Database and transaction log dumps which will be used by Delphix must be taken using native ASE format.
Dump devices are not supported, database and transaction dumps which will be used by Delphix must be taken to filesystem
files.
If ASE dump compression is being used the dumps must be generated using the compression = compress_level syntax. The
older compress::compress_level syntax is not supported.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing SAP ASE Environment Users.

6. Enter your login credentials for the source database.

7. Click Verify Credentials.
8. Click Next.
9. Select a Database Group for the dSource.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies.
10. Click Next.
11. Select an Initial Load option and enter any additional settings needed. There are three different options for the initial load of the
dSource:
New Full Backup Let Delphix create a new full backup file and load it. Note that when Delphix creates the backup, it is
dumped to Delphix storage, not the Backup Location specified in the next step.
Most Recent Existing Full Backup Find the most recent existing full backup file in the Backup Location and load it.
Specific Existing Full Backup Specify which backup files in the Backup Location you want to load.

115

Delphix User Guide 2016 Delphix

12. Enter the Backup Location. This is the directory where the database backups are stored. Delphix recursively searches this location, so
the database backups or transaction logs can reside in any subdirectories below the path entered.
13. Optionally, enter the Load Backup Server Name. If you have multiple backup servers in your staging environment, you can specify the
name of the backup server here to load database dumps and transaction logs into the staging database. If you leave this parameter
empty, the server designated as "SYB_BACKUP" will be used.
14. Select environment and ASE instance name.

15. Enable or disable LogSync.

16. Select Backup Location Type.
17. Click Advanced to edit Retention policies and External Data Directory.
18. Click Next.
19. Specify any Pre and Post Scripts.
20. Review the dSource Configuration and Data Management information.
21. Click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card. You can also make modifications to its
policies and permissions. To view the front of the dSource card, click the Open icon in the Databases panel. The card will then flip,
showing you information such as the Source Database and Data Management configuration.

Related Links
Managing SAP ASE Environments
Requirements for SAP ASE Target Hosts and Databases
Managing SAP ASE Environment Users
Users, Permissions, and Policies

116

Delphix User Guide 2016 Delphix

Provision an SAP ASE VDB

This topic describes how to provision a virtual database (VDB) from a SAP ASE dSource.

Prerequisites
Before you provision an SAP ASE VDB, you must:
Have linked a dSource from a source database, as described in Linking an SAP ASE Data Source, or have already created a VDB from
which you want to provision another VDB
Have set up target environments as described in Adding an SAP ASE Environment
Ensure that you have the required privileges on the target environment as described in Requirements for SAP ASE Target Hosts and
Databases
If you are provisioning to a target environment that is different from the one in which you set up the staging database, you must make
sure that the two environments have compatible operating systems, as described in Requirements for SAP ASE Target Hosts and
Databases. For more information on the staging database and the validated sync process, see Managing SAP ASE Environments: An
Overview.

Procedure
1. Login to the Delphix Admin application.
2. Click Manage
3. Select Databases.
4. Click My Databases.
5. Select a dSource.
6. Select a means of provisioning.
For more information, see Provisioning by Snapshot and LogSync.
7. Click Provision.
The Provision VDB panel will open, and the Instance and Database Name fields will auto-populate with information from the dSource.
8. Select whether to enable Truncate Log on Checkpoint database option for the VDB.
9. Click Next.
10. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
11. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
12. Click Next.
13. Specify any Hooks to be used during the provisioning process.
For more information, see Customizing SAP ASE Management with Hook Operations.
14. If your Delphix Engine system administrator has configured the Delphix Engine to communicate with an SMTP server, you will be able to
specify one or more people to notify when the provisioning is done. You can choose other Delphix Engine users or enter email
addresses.
15. Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and it will be listed in the Databases panel. If you
select the VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database
and its Data Management settings.

Provisioning by Snapshot
You can provision to the start of any snapshot by selecting that snapshot card from the TimeFlow view, or by entering a value in the time entry
fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.

Provisioning by LogSync
If LogSync is enabled on the dSource, you can provision by LogSync information. When provisioning by LogSync information, you can provision
to any point in time within a particular snapshot. The TimeFlow view for a dSource shows multiple snapshots by default. To view the LogSync
data for an individual snapshot, use the Slide to Open LogSync control at the top of an individual snapshot card. Drag the red triangle to the
point in time from which you want to provision. You can also enter a date and time directly.

117

Delphix User Guide 2016 Delphix

Related Links
Linking an SAP ASE Data Source
Adding an SAP ASE Environment
Requirements for SAP ASE Target Hosts and Databases
Managing SAP ASE Environments: An Overview
Customizing SAP ASE Management with Hook Operations

118

Delphix User Guide 2016 Delphix

Create a Group
Before you can link to a dSource or provision a VDB, you will need to create a group that will contain your database objects. Permissions and
policies for database objects are also determined within the group, as described in Users, Groups, and Permissions: An Overview.
When you first start up the Delphix Engine, a default group, <New Group>, is already defined. You can edit the name of this group, as well as
the policies and permissions associated with it, to use as your first group, or you can create a group as described in the following steps.
Groups for dSources and VDBs
Since policies and permissions for database objects are set by the group they belong too, you may want to create two groups, one for
dSources, one for VDBs, so you can set policies and permissions by object types.
Excerpt not found
The page: Adding and Deleting Groups was found, however the excerpt named: Procedure was not found. Please check/update the excerpt
name.

119

Delphix User Guide 2016 Delphix

Delete a dSource
Prerequisites
You cannot delete a dSource that has dependent VDBs. Before deleting a dSource, make sure all dependent VDBs have been deleted
as described in Delete a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Select Manage.
3. Select Databases.
4. Select My Databases.
5. In the Databases panel, select the dSource you want to delete.
6. Click the Trash Can icon.
7. Click Yes to confirm.

Deleting a dSource will also delete all snapshots, logs, and descendant VDB Refresh policies for that database. The deletion
cannot be undone.

120

Delphix User Guide 2016 Delphix

Delete a VDB
This topic describes how to delete a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Click My Databases.
4. Select the VDB you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

121

Delphix User Guide 2016 Delphix

Disable a dSource
This topic describes how to enable and disable dSources for operations such as backup and restore.
For certain processes, such as backing up and restoring the source database, you may want to temporarily disable your dSource. Disabling a
dSource turns off communication between the dSource and the source database, but does not tear down the configuration that enables
communication and data updating to take place. When a disabled dSource is later enabled, it will resume communication and incremental data
updates from the source database according to the original policies and data management configurations that you set.
Disabling a dSource is also a prerequisite for several other operations, like database migration and upgrading the dSource after upgrade of the
associated data source.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the dSource you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the dSource again, move the slider control from Disabled to Enabled, and the dSource will continue to function as
it did previously.

122

Delphix User Guide 2016 Delphix

_SysAdmin

123

Delphix User Guide 2016 Delphix

System Installation, Configuration, and Management

These topics describe installation and initial system configuration of the Delphix Engine, as well as topics related to system administration, such
as user management and system monitoring.
Installation and Initial Configuration Requirements
Installation and Initial System Configuration
Upgrading the Delphix Engine
Factory Reset

124

Delphix User Guide 2016 Delphix

Installation and Initial Configuration Requirements

These topics cover requirements for installing and configuring the Delphix Engine, including network and connectivity requirements, memory and
storage requirements, and supported web browsers and operating systems. It also includes topics on requirements for specific database
platforms, such as Oracle and Oracle RAC clusters, and Microsoft SQL Server.
Supported Web Browsers and Operating Systems
Virtual Machine Requirements for VMware Platform
Virtual Machine Requirements for AWS/EC2 Platform
General Network and Connectivity Requirements
Checklist of Information Required for Installation and Configuration
Virtual Machine Requirements for OpenStack with the KVM Hypervisor

125

Delphix User Guide 2016 Delphix

Supported Web Browsers and Operating Systems

This topic describes the Web browsers and operating systems that have been tested for use with the Delphix Engine management console.
The Delphix Engine management console requires http access to the server through a Web browser with a Flash plug-in. Supported browsers
and operating systems are listed in this table:

Tested Browser Configuration Matrix

OS Supported

Browsers Supported

Adobe Flash/Flex

Minimum Memory

Windows XP Professional SP3

Firefox, Chrome

10.x

4GB

Windows Vista SP2

Internet Explorer 9.x

10.x

4GB

Windows 7

Internet Explorer 9.x, 10.x, 11.x

10.x

4GB

Windows 7

Firefox, Chrome

10.x

4GB

Windows 7 x64

Internet Explorer 9.x, 10.x, 11.x

10.x

4GB

Windows 7 x64

Firefox, Chrome

10.x

4GB

Mac OS X

Firefox, Chrome

9.0.3 (6531.9)

4GB

126

Delphix User Guide 2016 Delphix

Virtual Machine Requirements for VMware Platform

This topic covers the virtual machine requirements, including memory and data storage, for installation of the Delphix Engine on a VMware
virtualization platform.
Ideally, the Delphix Engine Virtual Machine should be placed on a server where it will not contend with other VMs for network, storage or compute
resources. The Delphix Engine is an I/O intensive application, and deploying it in an environment where it must share resources with other virtual
machines, especially in configurations that involve sharing I/O channels, disk spindles, and network connections, can significantly reduce virtual
database performance.
Component

Requirements

Notes

Virtualization
Platform

VMware ESX/ESXi 6.x (recommended),VMware

ESX/ESXi 5.x (supported), VMware ESX/ESXi 4.x
(supported)

VMware ESX/ESXi 5.0 or higher is recommended for better

performance. Delphix Engine is tested and supported on
ESX/ESXi versions up to 6.0 Update 1

Virtual CPUs

8 vCPUs

CPU resource shortfalls can occur under high I/O throughput

conditions. CPU reservation is strongly recommended for
the Delphix VM, so that Delphix is guaranteed the full
complement of vCPUs even when resources are
overcommitted.

Memory

128 GB vRAM (recommended)

64GB vRAM (minimum)

The Delphix Engine uses its memory to cache database

blocks. More memory will provide better read performance.
Memory reservation is required for the Delphix VM.
Performance of the Delphix Engine will be significantly
impacted by over-comittment of memory resources in the
ESX Server. Reservation ensures that the Delphix Engine
will not stall while waiting for its memory to be paged in by
the ESX Server.

Do Not Allocate All Memory to the Delphix

Engine
Never allocate all available physical memory to the
Delphix VM. Memory for the ESX Server to
perform hypervisor activities must be set aside
before assigning memory to Delphix and other
VMs. The default ESX minimum free memory
requirement is 6% of total RAM. When free
memory falls below 6%, ESX starts swapping out
the Delphix guest OS. We recommend leaving
about 8-10% free to avoid swapping.
For example, when running on an ESX Host with
512GB of physical memory, no more than 470GB
(92%) should be allocated to the Delphix VM (and
all other VMs on that host).

Network

1. The .ova is pre-configured to use one virtual

Ethernet adapter of type VMXNET 3. If additional
virtual network adapters are desired, they should
also be of type VMXNET 3.
2. A 10GbE NIC in the ESX Server is recommended.
3. If the network load in the ESX Server hosting the
Delphix Engine VM is high, dedicate one or more
physical NICs to the Delphix Engine.

127

Jumbo frames are highly recommended to reduce CPU

utilization and increase network throughput. (typically
10-20% throughput improvement)
For environments having only Gigabit networks, it is possible
to aggregate several physical 1GbE NICs together to
increase network bandwidth (but not necessarily to reduce
latency). Refer to the VMware Knowledge Base article NIC
Teaming in ESXi and ESX. Do not aggregate NICs in the
Delphix Engine VM.
See General Network and Connectivity Requirements for
information about specific port configurations, and Network
Performance Configuration Options for information about
network performance tuning

Delphix User Guide 2016 Delphix

SCSI
Controller

LSI Logic Parallel

When adding virtual disks make sure that they are evenly
distributed across 4 virtual SCSI controllers. Spreading the disks
across all available SCSI controllers will ensure optimal IO
performance from the disks. For example, a VM with 4 SCSI
controllers and 6 virtual disks should distribute the disks across
the controllers as follows:
disk1 = SCSI(0:0)
disk2 = SCSI(0:1)
disk3 = SCSI(1:0)
disk4 = SCSI(1:1)
disk 5 = SCSI(2:0)
disk 6 = SCSI(3:0)

General
Storage
Configuration

Storage used for Delphix must be provisioned from

storage that provides data protection, e.g. by using RAID
levels with data protection features, or equivalent
technology. The Delphix Engine product does not protect
against data loss originating at the hypervisor or SAN
layers.
See Optimal Storage Configuration Parameters for
the Delphix Engine

Delphix VM
Configuration
Storage

1. The Delphix VM configuration should be stored in a

VMFS volume (often called a "datastore").

Delphix
Engine
System Disk
Storage

1. The Delphix Engine system disk should be stored in

a VMDK.

2. The VMFS volume should have enough available

space to hold all ESX configuration and log files
associated with the Delphix Engine.

2. The Delphix .ova file is configured for a 150GB

system drive. The VMFS volume where the .ova is
deployed should therefore have at least 150GB of
free space prior to deploying the .ova.
3. The VMFS volume must be located on shared
storage in order to use vMotion and HA features.

128

If a memory reservation is not enabled for the Delphix

Engine (in violation of memory requirements stated above),
then space for a paging area equal to the Delphix Engine's
VM memory must be added to the VMFS volume containing
the Delphix VM configuration data.
The VMDK for the Delphix Engine System Disk Storage is
often created in the same VMFS volume as the Delphix VM
definition. In that case, the datastore must have sufficient
space to hold the Delphix VM Configuration, the VDMK for
the system disk, and a paging area if a memory reservation
was not enabled for the Delphix Engine.

Delphix User Guide 2016 Delphix

Database
Storage

1. VMDKs or RDMs operating in virtual compatibility

mode can be used for database storage.
2. A minimum of 4 VMDKs or RDMs should be
allocated for database storage.
3. If using VMDKs:
Each VMDK should be in a different VMFS
volume
Each VMDK should be the only VMDK in its
VMFS volume
The VMFS volumes should be assigned to
dedicated physical LUNs on redundant storage.
The VMFS volumes should not be shared with
the ESX Server Console or any other Virtual
Machines.
On vSphere 5.x, the VMDKs should be created
with the Thick Provision Eager Zeroed option.
On vSphere 4.x, it is necessary to use a
two-step process to create VMDKs that are thick
provisioned and eager-zeroed. The VMDKs
should be first provisioned with the Thick option
(Thin provisioning not selected). After creating
the VMDK, use the ESX vmkfs command to
write zeroes to the VMDK before importing the
VMDK into the Delphix Engine.
4. All VDMKs or RDMs should be of the same size.
5. The physical LUNs used for VMFS volumes and
RDMs should be of the same type in terms of
performance characteristics such as latency, RPMs,
and RAID level. In addition, the total number of disk
drives that comprise the set of physical LUNs should
be capable of providing the desired aggregate I/O
throughput (MB/sec) and IOPS (Input/Output
Operations per Second) for all virtual databases that
will be hosted by the Delphix Engine.

Allocating a minimum of 4 VMDKs or RDMs for database

storage enables the Delphix File System (DxFS) to make
sure that its file systems are always consistent on disk
without additional serialization. This also enables the Delphix
Engine to achieve higher I/O rates by queueing more I/O
operations to its storage.
Provisioning VMDKs from isolated VMFS volumes on
dedicated physical LUNs:
Reduces contention for the underlying physical LUNs
Eliminates contention for locks on the VMFS volumes
from other VMs and/or the ESX Server Console
Enables higher availability of the Delphix VM by allowing
vSphere to vMotion the VM to a different ESX host in
the event of a failure of the Delphix ESX host
If the underlying storage array allocates physical LUNs by
carving them from RAID groups, the LUNs should be
allocated from different RAID groups. This eliminates
contention for the underlying disks in the RAID groups as the
Delphix Engine distributes IO across its storage devices.
If the storage array allocates physical LUNs from storage
pools comprising dozens of disk drives, the LUNs should be
distributed evenly across the available pools.
Using thin-provisioned LUNs in the storage array for VMFS
volumes can be useful if you anticipate adding storage to the
Delphix Engine in the future. In this case, the LUNs should
be thin-provisioned with a size larger than the amount of of
storage that will be initially allocated to the Delphix Engine.
When you want to add more storage to the Delphix Engine,
use vSphere to expand the size of the VMDKs. Be sure to
specify that the addtional storage is is also thick-provisione
d and eager-zeroed.

6. The physical LUNs used for VMFS volumes can be

thin-provisioned in the storage array.
7. For best performance, the LUNs used for RDMs
should not be thin-provisioned in the storage array,
but should be thick-provisioned with a size equal to
the amount of storage that will be initially allocated to
the Delphix Engine. The RDM can be expanded in
the future when more storage is needed.
8. Shared storage is required in order to use vMotion
and HA features.
In addition to making sure the latest VMware patches have been applied, check with your hardware vendor for updates specific to your hardware
configuration.
Known Issues
According to the following HP advisory, "On HP ProLiant servers configured with any of the HP Smart Array Controllers listed in the Scope
section (below) and running VMware ESXi 5.0, 5.1, or 5.5, or Red Enterprise Hat Linux 6 or 7, an out-of-memory condition may lead to a server
halt and purple screen after upgrading to HP Smart Array Controller Driver (hpsa) Version 5.x.0.58-1 (ESXi 5.0 and ESXi 5.1), Version
5.5.0.58-1 (ESXi 5.5), or Version 3.4.4-125 (Red Hat Enterprise Linux).":
http://h20564.www2.hp.com/hpsc/doc/public/display?docId=c04302261

129

Delphix User Guide 2016 Delphix

Virtual Machine Requirements for AWS/EC2 Platform

This topic covers the virtual machine requirements, including memory and data storage, for installation of the Delphix Engine on Amazon's Elastic
Cloud Compute platform.
Component

Requirements

Instance
Types

Storage
Optimized
Instances
i2.2xlarge
i2.4xlarge
i2.8xlarge

Notes
The Delphix Engine most closely resembles a storage appliance and performs best when
provisioned using a storage optimized instance type
Larger instance types provide more CPU, which can prevent resource shortfalls under high I/O
throughput conditions
Larger instances also provide more memory, which the Delphix Engine uses to cache database
blocks. More memory will provide better read performance.

Network
Configuration

Virtual
Private
Cloud
Static Public
IP
Security
Group
Configuration

You must deploy the Delphix Engine and all of the source and target environments in a VPC network
to ensure that private IP addresses are static and do not change when you restart instances.
When adding environments to the Delphix Engine, you must use the host's VPC (static private) IP
addresses.
The EC2 Delphix instance must be launched with a static public IP address; however, the default
behavior for VPC instances is to launch with a dynamic public IP address which can change
whenever you restart the instance. A static public IP address can only be achieved by using
assigned AWS Elastic IP Addresses.
The default security group will only open port 22 for secure shell (SSH) access. You must modify the
security group to allow access to all of the networking ports used by the Delphix Engine and the
various source and target platforms. See General Network and Connectivity Requirements for
information about specific port configurations.
See Network Performance Configuration Options for information about network performance
tuning

EBS
Configuration

EBS
Provisioned
IOPS
Volumes
EBS
Optimized
Instance
(except for
i2.xlarge
instance
type)

All attached storage devices must be EBS volumes. Delphix does not support the use of instance
store volumes.
Because EBS volumes are connected to EC2 instances via the network, other network activity on
the instance can affect throughput to EBS volumes. EBS optimized instances provide guaranteed
throughput to EBS volumes and are required (for instance types that support it) in order to provide
consistent and predictable storage performance. The i2.8xlarge instance type does not support EBS
optimized instances; however, this instance type supports 10 Gigabit networking that often provides
suitable performance.
Use EBS volumes with provisioned IOPs in order to provide consistent and predictable performance.
The number of provisioned IOPs depends on the estimated IO workload on the Delphix Engine.
Provisioned IOPs volumes must be configured with a volume size at least 30 GiB times the number
of provisioned IOPs. For example, a volume with 3,000 IOPS must be configured with at least 100
GiB.
I/O requests of up to 256 kilobytes (KB) are counted as a single I/O operation (IOP) for provisioned
IOPs volumes. Each volume can be configured for up to 4,000 IOPs.

General
Storage
Configuration

Allocate initial storage equal to the size of the physical source databases. For high redo rates and/or
high DB change rates, allocate an additional 10-20% storage.
Add storage when storage capacity approaches 30% free
Keep all EBS volumes the same size. Add new storage by provisioning new volumes of the same
size.
Maximize Delphix Engine RAM for a larger system cache to service reads
Use at least 3 EBS volumes to maximize performance. This enables the Delphix File System (DxFS)
to make sure that its file systems are always consistent on disk without additional serialization. This
also enables the Delphix Engine to achieve higher I/O rates by queueing more I/O operations to its
storage.
See Optimal Storage Configuration Parameters for the Delphix Engine

130

Delphix User Guide 2016 Delphix

General Network and Connectivity Requirements

This topic covers the general network and connectivity requirements for the Delphix Engine, including connection requirements, port allocation,
and firewall and Intrusion Detection System (IDS) considerations. For platform-specific network and connectivity requirements, see the relevant
topics under the Requirements section for each platform.

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con

131

Delphix User Guide 2016 Delphix

figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

Related Links
Network and Connectivity Requirements for DB2 Environments
Network and Connectivity Requirements for Unix Environments
Network and Connectivity Requirements for PostgreSQL Environments
Network and Connectivity Requirements for SQL Server Environments
Network and Connectivity Requirements for Windows Environment
Network and Connectivity Requirements for Oracle Environments
Network and Connectivity Requirements for SAP ASE Environments
Network and Connectivity Requirements for MySQL Environments
Network and Connectivity Requirements for Windows Environments

132

Delphix User Guide 2016 Delphix

Checklist of Information Required for Installation and Configuration

This topic describes the information that is required for initial installation and configuration of the Delphix Engine.

Information Required for Installation

Name of the Delphix Engine
Network configuration with static DHCP lease or static IP address
Static IP address in CDIR notation (for example, 10.80.142.82/24) (not required for static DHCP configuration)
Subnet mask
Gateway IP address
DNS server IP address(es)
Domain of the Delphix Engine installation, such as mydelphix.com
Selection of storage devices for the operating system disks. See Virtual Machine Requirements for VMware Platform for more
information on memory and storage requirements.

Information Required for Initial Configuration

NTP server used for setting system time (optional)
DNS server for name resolution (not required for static IP configuration or if DHCP supplies the DNS servers)
Web proxy server (if used)
SMTP server to support email notification
IP address or name (for example, smtp.gmail.com) and port number
Email address from which you want the Delphix Engine to send email
If using LDAP for authentication, server information, including name or IP address and port number
If using SNMP for notifications, server name and IP address, port number, and community string
Desired password for sysadmin user (this default user can be replaced) - For the ServerSetup application
IP address or name and port number
Email address for messages sent to the sysadmin user
Desired password for delphix_admin user (this default user can be replaced) - For the Delphix Admin application
See The delphix_admin and sysadmin User Roles for more information.
Email address for messages sent to the delphix_admin user

Related Links
Virtual Machine Requirements for VMware Platform
The delphix_admin and sysadmin User Roles

133

Delphix User Guide 2016 Delphix

Virtual Machine Requirements for OpenStack with the KVM Hypervisor

This topic covers the virtual machine requirements, including memory and data storage, for installation of the Delphix Engine on an OpenStack
compute node running on the KVM virtualization platform.
The Delphix Engine Virtual Machine (VM) should be placed on a compute node where it will not contend with other VMs for network, storage, or
compute resources. The Delphix Engine is an I/O intensive application; deploying it in an environment where it must share resources with other
virtual machines can significantly reduce virtual database performance, especially in configurations that involve sharing I/O channels, disk
spindles, and network connections.

Component
Virtualization
Platform

Requirements

Notes

Ubuntu versions >= 12.04 and RHEL

versions >= 6 are the supported Linux
versions for the OpenStack compute node.
KVM doesn't have its own versioning
system; the KVM version is simply the
version of the Linux kernel you are running.
OpenStack versions >= Havana (2013.2) are
supported.
Required OpenStack services for administering
Delphix include Compute (Nova), Image (Glance),
Block Storage (Cinder), Networking (Neutron) or
legacy networking (Nova Network).

Virtual CPUs

Memory

8 vCPUs
vCPUs must be model Westmere (preferred if
supported by physical CPU), Nehalem, Penryn, Conr
oe, or kvm64.

128 GB vRAM (recommended)

64 GB vRAM (minimum)

To set the vCPU model for your compute node, add the following
lines to the [libvirt] section of nova.conf (see list to the left
for acceptable cpu_model values):

cpu_mode = custom
cpu_model = Westmere
virt_type = kvm
The Delphix Engine uses its memory to cache database
blocks. More memory will provide better read performance.
Memory overcommit should be disabled on the compute
node by setting where the Delphix VM is running, if possible.
Overcommit causes the Delphix Engine to stall while waiting
for its memory to be paged in by the compute node. You can
disable Overcommit by adding the following line to the [DEF
AULT] section of nova.conf:

ram_allocation_ratio = 1.0
Alternatively, you can simply run the Delphix Engine as the
sole VM on the OpenStack Compute node where it is
located.
Network

If the network load is high in the compute node hosting

the Delphix Engine VM, dedicate one or more physical
NICs to the Delphix Engine.

134

A 10GbE NIC in the compute node is recommended.

The Delphix Engine installation image is pre-configured to
use one virtual Ethernet adapter of type virtio. If you want
additional virtual network adapters, they should also be of
type virtio.
You can launch instances in either a Networking (Neutron)
or legacy (Nova Networking) network.
Jumbo frames are supported.
See General Network and Connectivity Requirements for
information about specific port configurations, and Network
Performance Configuration Options for information about
network performance tuning.

Delphix User Guide 2016 Delphix

Delphix
Engine
System Disk
Storage

The Delphix Engine system disk must be created from

the installation image with format qcow2.
The Delphix Engine installation image is configured for
a 150GB system drive. The physical location where
the volume is deployed should therefore have at least
150GB of free space prior to deploying the Delphix
Engine VM.

Database
Storage
Configuration

Use the OpenStack Block Storage service (Cinder) for

provisioning volumes for database storage.
Allocate at least 3 volumes for database storage.
All volumes should have the same capacity.
If the Block Storage driver for provisioning storage
allows it, volumes should be thick provisioned and
eager zeroed.
Volumes should be assigned to dedicated physical
LUNs on redundant storage.
The physical resources used for volume storage
should be of the same type in terms of performance
characteristics such as latency, RPMs, and RAID
level.

Allocate initial storage equal to the size of the physical

source databases. For high redo rates and/or high DB
change rates, allocate an additional 10-20% storage.
Add storage when storage capacity approaches 70% used.
Use at least 3 volumes to maximize performance. This
enables the Delphix File System (DxFS) to make sure that
its file systems are always consistent on disk without
additional serialization. This also enables the Delphix Engine
to achieve higher I/O rates by queueing more I/O operations
to its storage.
The set of disk drives that comprise the set of physical LUNs
must be capable of providing the desired aggregate I/O
throughput (MB/sec) and IOPS (Input/Output Operations per
Second) for all virtual databases that will be hosted by the
Delphix Engine.
Different Block Storage drivers will have different
configuration options. For generalized advice on setting up
high-performance Delphix Engine database storage, see O

ptimal Storage Configuration Parameters for

the Delphix Engine.

135

Delphix User Guide 2016 Delphix

Installation and Initial System Configuration

These topics describe the initial installation and configuration of the Delphix Engine, the delphix_admin and sysadmin roles, and using the system
console.
The delphix_admin and sysadmin User Roles
Using HostChecker to Confirm Source and Target Environment Configuration
Installing the Delphix Engine
Setting Up Network Access to the Delphix Engine
Customizing the Delphix Engine System Settings
Setting Up the Delphix Engine
Retrieving the Delphix Engine Registration Code

136

Delphix User Guide 2016 Delphix

The delphix_admin and sysadmin User Roles

This topic describes the function of the delphix_admin and sysadmin roles.
After installation, the Delphix Engine creates a sysadmin user with the initial password sysadmin. The sysadmin launches the initial ServerSetu
p configuration application and has access to a command-line system administration console. Through the command line console or the
ServerSetup application the sysadmin can also undertake typical system administration duties such as managing memory, storage, and support
logs for the Delphix Engine, and performing upgrades and patches.
When the Delphix Admin interface launches, the delphix_admin can log in using the username delphix_admin and password delphix.
After initial configuration, the delphix_admin user manages the Delphix Engines user data objects: dSources, virtual databases (VDBs), users,
groups, and related policies and resources, all collectively referred to as the Delphix Engine Domain. The delphix_admin user manages the
Delphix Engine domain using either the Command Line Interface (CLI) or the browser-based Delphix Admin application.
Email addresses are required inputs for both the sysadmin and delphix_admin accounts, and you can create additional sysadmin and
delphix_admin users as described in the topics under Managing System Administrators.

Related Links
Managing System Administrators

137

Delphix User Guide 2016 Delphix

Using HostChecker to Confirm Source and Target Environment Configuration

This topic describes the HostChecker script that is used to check the configuration of source and target environments.
The HostChecker is a standalone program which validates that host machines are configured correctly before the Delphix Engine uses them as
data sources and provision targets.
Please note that HostChecker does not communicate changes made to hosts back to the Delphix Engine. If you reconfigure a host, you must
refresh the host in the Delphix Engine in order for it to detect your changes.
You can run the tests contained in the HostChecker individually, or all at once. You must run these tests on both the source and target hosts to
verify their configurations. As the tests run, you will either see validation messages that the test has completed successfully, or error messages
directing you to make changes to the host configuration.
See these topics for more specific information about the tests that are run for each data platform supported by the Delphix Engine;
Using HostChecker to Validate MySQL Source and Target Environments
Using HostChecker to Validate Oracle Source and Target Environments
Using HostChecker to Validate SAP ASE Source and Target Environments
Using HostChecker to Validate PostgreSQL Source and Target Environments
Using HostChecker to Validate SQL Server Source and Target Environments

138

Delphix User Guide 2016 Delphix

Installing the Delphix Engine

This topic describes how to install the Delphix Engine from the OVA file.

Prerequisites
Read the requirement and support information in the Installation and Initial Configuration Requirements topics.

Procedure to install an OVA

Use the Delphix-supplied OVA file to install the Delphix Engine. The OVA file is configured with many of the minimum system requirements and
deploys to one 150 GB hard disk with 8 vCPUs and 64GB RAM. The underlying storage for the install is assumed to be redundant SAN storage.
1. Download the OVA file from the Delphix download site or obtain it from your Delphix solutions architect.
2. Login using the vSphere client to the vSphere server (or vCenter Server) where you want to install the Delphix Engine.
3. In the vSphere Client, select File > Deploy OVA Template.
4. Browse to the OVA file.
5. Click Next.
6. Select a hostname for the Delphix Engine.
This hostname will also be used in configuring the Delphix Engine network.
7. Select the data center where the Delphix Engine will be located.
8. Select the Cluster and the ESX host.
9. Select a data store that has at least 166 GB free space. This will need to be larger if you plan to increase the size of memory on the VM
from 16GB.
10. Select a disk format.
Thick provisioning is the recommended default configuration. In vSphere 5.0, choose Eager Zeroed.
11. Select the virtual network you want to use.
If using multiple physical NICs for link aggregation, you must use vSphere NIC teaming. Do not add multiple virtual NICs to the Delphix
Engine itself. The Delphix Engine should use a single virtual network. For more information, see Optimal Network Configuration
Parameters for the Delphix Engine.
12. Click Finish.
The installation will begin and the Delphix Engine will be created in the location you specified.

Procedure to install an AMI

Use the Delphix-supplied AMI file to install the Delphix Engine.
1. On the Delphix download site, click the AMI you would like to share and accept the Delphix License agreement. Alternatively, follow a link
given by your Delphix solutions architect.
2. On the Amazon Web Services Account Details form presented:
a. Enter your AWS Account Identifier, which can be found here: https://console.aws.amazon.com/billing/home?#/account. If
you want to use the GovCloud AWS Region, be sure to enter the ID for the AWS Account which has GovCloud enabled.
b. Select which AWS Region you would like the AMI to be shared in. If you would like the AMI shared in a different region, contact
your Delphix account representative to make the proper arrangements.
3. Click Share.
The Delphix Engine will appear in your list of AMIs in AWS momentarily.
4. Reference the Installation and Configuration Requirements for AWS/EC2 when deploying the AMI.

Post-Requisites
After installing the server, follow the procedures in these topics to specify and customize the Delphix Engine network and to make modifications to
the memory size, number of CPUs, and number of disks used for storage.
Setting Up Network Access to the Delphix Engine
Customizing the Delphix Engine System Settings

139

Delphix User Guide 2016 Delphix

Setting Up Network Access to the Delphix Engine

This topic describes how to configure the Delphix Engine network during initial installation.

Prerequisites
Follow the initial installation instructions in Installing the Delphix Engine.
NAT Configuration
Delphix communicates it's IP address in application layer data and this cannot be translated by NAT
You can configure a Delphix Engine to use either a dynamic (DHCP) IP address or a static IP address.

Procedure
1. Power on the Delphix Engine and open the Console.
2. Wait for the Delphix Management Service and Delphix Boot Service to come online.
3. Press F2 to access the sysadmin console.
4. Enter sysadmin@SYSTEM for the username and sysadmin for the password.
5. You will be presented with a description of available network settings and instructions for editing.

140

Delphix User Guide 2016 Delphix

Delphix Engine Network Setup

To access the system setup through the browser, the system must first be configured
for networking in your
environment. From here you can configure the primary interface, DNS, hostname, and
default route. When DHCP is
configured, all other properties are derived from DHCP settings.
To see the current settings, run 'get'. To change a property, run 'set
<property>=<value>'. To commit your changes,
run 'commit'. To exit this setup and return to the standard CLI, run 'discard'.
defaultRoute
'1.2.3.4').

IP address of the gateway for the default route (e.g.

dhcp
Boolean value indicating whether DHCP should be used for the
primary interface. Setting this value
to 'true' will cause all other properties (address, hostname,
and DNS) to be derived from the DHCP
response
dnsDomain

DNS Domain (e.g. 'delphix.com').

dnsServers
DNS server(s) as a list of IP addresses (e.g.
'1.2.3.4,5.6.7.8').
hostname
'myserver').

Canonical system hostname, used in alert and other logs (e.g.

primaryAddress
'1.2.3.4/22').

Static address for the primary interface in CIDR notation (e.g.

Current settings:
defaultRoute: 192.168.1.1
dhcp: false
dnsDomain: example.com
dnsServers: 192.168.1.1
hostname: Delphix
primaryAddress: 192.168.1.100/24
6. Configure the hostname. If you are using DHCP, this step can be skipped.

delphix network setup update *> set hostname=<hostname>

The hostname should be the same name you entered during the server installation.

7. Configure DNS. If you are using DHCP, this step can be skipped.

delphix network setup update *> set dnsDomain=<domain>

delphix network setup update *> set dnsServers=<server1-ip>[,<server2-ip>,...]
8. Configure either a static or DHCP address:

DHCP Configuration
delphix network setup update *> set dhcp=true

141

Delphix User Guide 2016 Delphix

Static Configuration
delphix network setup update *> set dhcp=false
delphix network setup update *> set primaryAddress=<address>/<prefix-len>
The static IP address must be specified in CIDR notation (for example, 192.168.1.2/24)

9. Configure a default gateway. If you are using DHCP, this step can be skipped.

delphix network setup update *> set defaultRoute=<gateway-ip>

10. Commit your changes. Note that you can use the get command prior to committing to verify your desired configuration.

delphix network setup update *> commit

Successfully committed network settings. Further setup can be done through the
browser at:
http://<address>
Type 'exit' to disconnect, or any other commands to continue using the CLI.
11. Check that the Delphix Engine can now be accessed through a Web browser by navigating to the displayed IP address, or hostname if
using DNS.
12. Exit setup:

delphix> exit

142

Delphix User Guide 2016 Delphix

Customizing the Delphix Engine System Settings

This topic describes how to customize the initial system set up requirements for memory, number of CPUs, storage disks, and network
configuration.
The OVA file that you use to install the Delphix Engine is configured for the minimum system requirements. You can customize these to match the
capabilities of your specific system.

Prerequisites
Follow the initial installation instructions in Installing the Delphix Engine.

Procedure
1. Shut down the guest operating system and power off the Delphix Engine.
2. Under Getting Started, select Edit Virtual Machine Settings.
3. You can now customize the system settings.
Setting

Options

Memory
Size

Set to 64GB or larger based on sizing analysis. In the Resource Allocation panel, ensure that Reserve all guest memory is
checked.

Number of
CPUs

Allocate 8 vCPUs or more based on your Delphix licensing. vCPUs should be fully reserved to ensure that the Delphix Engine
does not compete for CPU cycles on an overcommitted host.

Disks for
Data
Storage

Add virtual disks to provide storage for user data such as dSources and VDBs. The underlying storage must be redundant. Add
a minimum of 150GB per storage disk. All virtual disks should be the same size and have the same performance
characteristics. If using VMFS, use thick provisioned, eager zeroed disks. To alleviate IO bottlenecks at the virtual controller
layer, spread the virtual disks across all 4 virtual SCSI controllers.

Data
Storage
Multipathing
Policy

For EMC storage, the multipathing policy should always be set to roundrobin (default for 5.X). Additionally, change the IO
Operation Limit from the default of 1000 to 1. This should be strongly considered for other storage platforms as well.

Network

The network configuration is set to have a VMXNET3 network adapter. VMXNET3 is a tuned network interface that is included
with the VMtools provided in the OVA file.
It will be assigned to VM Network

See VMware KB article EMC VMAX and DMX Symmetrix Storage Array Recommendations for Optimal Performance on
VMware ESXi/ESX

JUMBO Frames
VMXNET3 supports Ethernet jumbo frames, and you can use this to maximize throughput and minimize CPU utilization.
Adding Link Aggregation via VMware NIC Teaming
To increase throughput or for failover, add multiple physical NICs to the vSwitch that is connected to the Delphix Engine. To
increase throughput, NIC Teaming must use the Route Based on IP Hash protocol for load balancing. See VMware KB article
Troubleshooting IP-Hash outbound NIC selection.
Dedicate Physical NICs to the Delphix Engine
For best performance, assign the Delphix Engine to network adapters that are used exclusively by Delphix.

Post-Requisites
After making any changes to the system settings, power on the Delphix Engine again and proceed with the initial system configuration as
described in Setting Up the Delphix Engine.

143

Delphix User Guide 2016 Delphix

Setting Up the Delphix Engine

This topic describes how to set up the initial system configuration for the Delphix Engine, including system time, storage, web proxy, SMTP
server, email to Delphix Support, and LDAP authentication.

Prerequisites
You must have Delphix sysadmin privileges to perform the following procedures. For more information, see The delphix_admin and sysadmin
User Roles .
Click on the Server Setup link in the lower left corner of the default Delphix login dialog box, and login to the Delphix Setup user interface as s
ysadmin, as shown here...

The URL for this Server Setup screen will be http://<Delphix

Engine>/login/index.html#serverSetup.

Procedure
The setup procedure uses a wizard process to take you through five configuration screens:
System Time
Network
Storage
Serviceability
Authentication Service
1. Connect to the Delphix Engine at http://<Delphix Engine>/login/index.html#serverSetup.
The ServerSetup application will launch when you connect to the server.
Enter your sysadmin login credentials, which initially defaults to the username syadmin, with the initial default password of sysadmin.
On first login, you will be prompted to change the initial default password.
2. Click Next.

System Time
1. Select an option for maintaining the system time.
Option

Notes

Set NTP
Server

After selecting this option, select an NTP server from the list, or click Add NTP Server to manually enter a server.
Be aware that you can highlight more than one NTP Server entry in order to select more than one.
When configuring a Delphix Engine on VMware, be sure to configure the NTP client on the host to use the same
servers that you enter here. On a vSphere client, the NTP client is set in the Security Profile section of the
configuration process.

144

Delphix User Guide 2016 Delphix

Manually
Select Time
and Date

Click Use Browser Time and Date to set the system time, or select the date and time by using the calendar and
clock displays. Then select the Time Zone.
If you select Use Browser Time and Date, the date and time will persist as your local time, even if you change the
time zone.
Snapshots from dSources and VDBs reflect the time zone of the source or target environment, not that of the Delphix
Engine.

2. Be sure to choose the appropriate time zone for the Delphix Server, using the drop-down list in the lower left-hand corner of this page.
3. Click Next.

Network Configuration
The initial out-of-the-box network configuration in the OVA file is set to use a VMXNET3 network adapter.
1. Under Network Interfaces, click Settings.
2. The first Network Interface is Enabled by default.
3. Select DHCP or Static network addressing.
For Static addressing, enter an IP Address and Subnet Mask.
The static IP address must be specified in CIDR notation (for example, 192.168.1.2/24)

4. Select whether to use Jumbo Frames.

VMXNET3 supports Ethernet jumbo frames, which can be used to maximize throughput and minimize CPU utilization.
Please first review Delphix Support Knowledge Base article KB028 to ensure that you understand the implications of using Ethernet
jumbo frames.
5. Click Save.
6. Repeat for any other interfaces you have added to the virtual machine (VM) that you wish to configure. They will not be enabled by
default.
7. Under Routing, enter a Default Gateway.
8. Under DNS Services, enter a DNS Domain Name and DNS Server.
9. Click Next.

Storage
The Delphix Engine automatically discovers and displays storage devices. For each device, set the Usage Assignment to Data and set the Stor
age Profile to Striped.
You can associate additional storage devices with the Delphix Engine after initial configuration, as described in Adding and Expanding Storage
Devices.
Storage Disk Usage Assignment Options
There are three options for storage disk usage assignment:
Data
Once you set the storage unit assignment for a disk to Data and save the configuration, you cannot change it again.
Unassigned
These are disks being held for later use.
Unused
These disks can be configured later to add capacity for existing data disks.

The Minimum Number of Storage Disks

Configure at least 4 disks for storage of user data. This makes the Delphix Engine storage manager function more efficiently, since
duplicated metadata can be distributed across multiple disks.

Serviceability
1. If a Web Proxy Server is necessary for your environment, select Use a Web Proxy and enter the required information.

145

Delphix User Guide 2016 Delphix

1.
2. If you want the Delphix Engine to send information to the Delphix Support site periodically over https (SSL), select Phone Home Service
enabled. This feature requires a connection to the internet and will use the Web Proxy Server configuration.
Please be aware that the Phone Home Service only sends occasional support log bundles outbound from the Delphix Engine
to Delphix Support website. There is no way to enable inbound access to the Delphix Engine.
3. Select Use an SMTP Server and enter the required information to enable email notifications for events and alerts.

When a critical fault occurs with the Delphix Engine, it will automatically send an email alert to the delphix_admin user. Make sure that
you configure the SMTP server so that alert emails can be sent to this user. See System Faults for more information.

Authentication Service
To avoid configuration issues, consult with your lightweight directory access protocol (LDAP) administrator before attempting to set up
LDAP authentication of users for the Dephix Engi
1. Select Use LDAP to enable LDAP authentication of users.
2. Enter the LDAP Server IP address or hostname, and Port number.
3. Select the Authentication method.
4. Select whether you want to Protect LDAP traffic with SSL/TLS.
If you select this option, you must import the server certificate.
5. When you are done with the LDAP configuration, click Test Connection.
6. Click Next.

LDAP Authentication When Adding Users

If LDAP has been set up as the authentication service for the Delphix Engine, you must add new users with LDAP as their
authentication mechanism. For more information, see Adding Delphix Users and Privileges . Note that you can only add individual
LDAP users, not groups.

Registration
If the Delphix Engine has access to the external Internet (either directly or through a web proxy), then you can auto-register the Delphix Engine:
1. Enter your Support Username and Support Password.
2. Click Register.
If external connectivity is not immediately available, you must perform manual registration.
1. Copy the Delphix Engine registration code in one of two ways:
a. Manually highlight the registration code and copy it to clipboard. Or,
b. Click Copy Registration Code to Clipboard.
2. Transfer the Delphix Engine's registration code to a workstation with access to the external network Internet. For example, you could
e-mail the registration code to an externally accessible e-mail account.
3. On a machine with access to the external Internet, please use your browser to navigate to the Delphix Registration Portal at http://regist
er.delphix.com.
4. Login with your Delphix support credentials (username and password).
5. Paste the Registration Code.
6. Click Register.

While your Delphix Engine will work without registration, we strongly recommend that you register each Delphix Engine as part of setup.
Failing to register the Delphix Engine will impact its supportability and security in future versions.

Summary
1. The final summary form will enable you to review your configurations for System Time, Network, Storage, Serviceability, and
Authentication. Click Modify to change the configuration for any of these server settings.
2. If you are ready to proceed, then click Finish.
3. Click Yes to confirm that you want to save the configuration.
4.
146

Delphix User Guide 2016 Delphix

4. Click OK to acknowledge the successful configuration.

5. There will be a wait of several minutes as the Delphix Engine completes configuration.

Post-Requisites
After configuration is complete, the Delphix Engine will restart and launch the browser-based Delphix Admin user interface. The URL for
this will be http://<Delphix Engine>/login/index.html#delphixAdmin.
After the Delphix Admin interface launches, the delphix_admin can login using the initial default username delphix_admin and the initial
default password delphix. On first login, you will be prompted to change the initial password.
You can access the Server Setup interface at any time by navigating to http://<Delphix Engine>/login/index.html#serverS
etup and entering the sysadmin credentials.

Related Links
The delphix_admin and sysadmin User Roles
System Faults
Adding Delphix Users and Privileges
Adding and Expanding Storage Devices

147

Delphix User Guide 2016 Delphix

Retrieving the Delphix Engine Registration Code

This topic describes how to retrieve the registration code for a Delphix Engine. We strongly recommend that you perform registration as a part of
Delphix Engine setup. However, you can also retrieve the registration code for a Delphix Engine after setup.

Procedure
1. You can retrieve the Delphix Engine Registration Code through the ServerSetup application after logging in with the sysadmin credentia
ls.
2. In the Registration panel, click View.
3. The Registration Code is displayed in the bottom half of the Registration window.
4. If your local machine is connected to the external Internet, you can auto-register the Delphix Engine:
a. Enter your Support Username and Support Password.
b. Click Register.
5. If external connectivity is not immediately available, you must register manually.
a. Copy the Delphix Engine registration code by either manually highlighting and copying to clipboard or clicking Copy
Registration Code to Clipboard.
b. Transfer the Delphix Engine's registration code to a location with an external network connection. For example, you could e-mail
the registration code to an externally accessible e-mail account.
c. On a machine with external network access, use your browser to navigate to the Delphix Registration Portal at https://register.d
elphix.com.
d. Login with your support credentials.
e. Paste the Registration Code.
f. Click Register.

While your Delphix Engine will work without registration,

we strongly recommend that you register each Delphix Engine

as part of setup. Failing to register the Delphix Engine will impact its supportability and security in future
versions.

Post-Requisites
Following registration, you will receive an e-mail confirming the registration of your Delphix Engine.

148

Delphix User Guide 2016 Delphix

Factory Reset
This topic describes the process for returning the Delphix Engine to "factory default" settings. This completely removes all DATA and
CONFIGURATION.

Prerequisites
It is recommend to shut down and remove all VDBs before resetting the Delphix Engine. Failure to do so could possibly lead to stale data mounts
in target environments. (NFS, for *nix environments, or iSCSI I/O errors in Windows environments) For the same reason, disable all dSources that
use pre-provisioning (all SQL Server dSources, and any Oracle dSources with validated sync enabled).

Use Factory Reset only when a complete reset and reconfiguration of the Delphix Engine is necessary, as all Delphix Engine objects
will be de-allocated.

Procedure

1. Connect to the ServerSetup GUI (e.g. http://DelphixEngine/login/index.html#serverSetup, or http://DelphixEngine/ and select

"Server Setup")
2. Login as sysadmin or with other system administrator credentials.
3. Select Factory Reset from the menu

Alternative procedure via Command Line Interface (CLI)

1. Connect to the CLI via SSH
2. Login as sysadmin or with other system administrator credentials.
3. "system ; factoryReset ; commit ; exit"

149

Delphix User Guide 2016 Delphix

Managing System Administrators

These topics describe setting up and managing system administrators for the Delphix Engine.
System Administrators and Delphix Users
Adding New System Administrators
Changing System Administrator Passwords
Deleting and Suspending System Administrators
Reinstating System Administrators

150

Delphix User Guide 2016 Delphix

System Administrators and Delphix Users

This topic describes the different kinds of users in Delphix, including sysadmin and delphix_admin.

System Administrators
Delphix system administrator users are responsible for managing the Delphix Engine itself, but not the objects (Environments, dSources, VDB's)
within the server. For example, a system administrator is responsible for setting the time on the Delphix Engine and its network address, restarting
it, creating new system administrator users (but not Delphix users), and other similar tasks.
The sysadmin user is the default system administrator user. While this user can be suspended, it may not be deleted. When the Delphix Admin
interface launches, the delphix_admin can log in using the username delphix_admin and password delphix.

System administrators administer the Delphix Engine through the ServerSetup interface, which is accessed through
a Web browser at http:<Delphix Engine>/ServerSetup.html,as well as through the command line
interface accessible via ssh.

Delphix Users
Delphix users are responsible for managing the objects within the Delphix Engine. These include:
dSources
VDBs
Groups
Policies
Space and Bandwidth
Replication Services
Backup and Restore
A Delphix user can be marked as a Delphix Admin. Delphix Admins have three special privileges:
They can manage other Delphix users
They implicitly have Owner privileges for all Delphix objects
They can create new groups and new environments
The delphix_admin is the default Delphix user provided with a Delphix Engine and is a Delphix Admin. Like the sysadmin user, delphix_admin
can not be deleted. When the Delphix Admin interface launches, the delphix_admin can log in using the username delphix_admin and
password delphix.
A Delphix Admin user accesses objects with the Delphix Engine Admin Interface, which is accessed through a Web browser at http:<Delphix
Engine>/Server.html.

Updating Credentials
System administrator users can change the password of any other system administrator user. Delphix Admin users can change the password of
any other Delphix user (including other Delphix Admins). Regular Delphix users can change their own passwords but must provide their old
password to do this.

151

Delphix User Guide 2016 Delphix

Adding New System Administrators

This topic describes how to add system administrators to the Delphix Engine.

Procedure
1. Launch the ServerSetup application and log in using sysadmin level credentials.
2. In the System User Management panel, click +.
3. Enter the required information.
4. Click Save.

152

Delphix User Guide 2016 Delphix

Changing System Administrator Passwords

This topic describes how to change system administrator passwords on the Delphix Engine.

Procedure
1. Launch the ServerSetup application and log in using sysadmin level credentials.
2. In the System User Management panel, click the user whose password you want to change.
3. Select Change Password?
4. Enter the new password in the New Password and Verify New Password fields.
5. Click OK.

153

Delphix User Guide 2016 Delphix

Deleting and Suspending System Administrators

This topic describes how delete and suspend system administrators on the Delphix Engine.

Procedure
1. Launch the ServerSetup application and log in using the sysadmin (or other system administrator) credentials.
2. In the System User Management panel, click the user you want to suspend or delete.
3. Suspend the user by clicking the red, crossed circle icon in the in the lower left corner of the System User Management panel.
4. Delete the user by clicking the trash can icon in the lower left corner of the panel.

Suspending the sysadmin User

The sysadmin user is a required user for the Delphix Engine. This user cannot be deleted, but can be suspended. Suspending the
sysadmin user prevents that user from being able to log into ServerSetup or to the console via ssh. The sysadmin user can still log into
the console on the install machine, even if the sysadmin account has been suspended.

154

Delphix User Guide 2016 Delphix

Reinstating System Administrators

This topic describes how to reinstate system administrators whose accounts have been suspended.

Procedure
1. Launch the ServerSetup application and log in using system administrator credentials.
2. In the System User Management panel, click on the name of the user you want to reinstate.
3. Reinstate the user by clicking the yellow checkmark icon in the in the lower left corner of the System User Management panel.

155

Delphix User Guide 2016 Delphix

Capacity and Resource Management

These topics describe procedures and concepts for capacity and resource management.
An Overview of Capacity and Performance Information
Setting Quotas
Deleting Objects to Increase Capacity
Changing Snapshot Retention to Increase Capacity
Delphix Storage Migration
Adding and Expanding Storage Devices

156

Delphix User Guide 2016 Delphix

An Overview of Capacity and Performance Information

This topic describes the Delphix Engine performance reservoir and capacity threshold warnings, and various ways to obtain information about
capacity and resource usage for the Delphix Sever.

The Performance Reservoir and Capacity Threshold Warnings

In order to obtain best performance, the Delphix Engine requires a performance reservoir of 15% of the total quota for storage space. As storage
capacity approaches this threshold, the following system faults occur:
When 78% of the total storage quota is reached, a Warning fault is triggered. You can resolve this fault by deleting objects in the Delphix
Engine, adding storage, or changing policies, as described in the topics Adding and Expanding Storage Devices, Deleting Objects to
Increase Capacity, and Changing Snapshot Retention to Increase Capacity.
When 85% of the total storage quota is reached, a Critical fault is triggered, and the Delphix Engine will enter into Maintenance Mode.
When this occurs:
All pending link, sync, refresh, and provisioning processes will be cancelled, and no new operations can be initiated
Policy operations such as SnapSync, Snapshot, and Refresh are suspended for all platforms
dSources stop pulling in new changes. LogSync is suspended for all Oracle and PostgreSQL dSources. Validated sync is
disabled for SQL Server dSources.
No Virtual Database (VDB) snapshots can be taken
When 95% of the total storage quota is reached, a second Critical fault is triggered for SQL Server. All SQL Server VDBs stop in order
to maintain data integrity.
To take the system out of Maintenance Mode, increase the storage capacity. This can be done by adding storage devices, deleting objects, or
changing policy settings. When you have increased the storage capacity, the system will automatically exit Maintenance Mode.
When the system falls below 95% of the total storage quota, you can manually start SQL Server VDBs that had stopped
When the system falls below 90% of the total storage quota, SQL Server VDBs that had stopped will automatically start
When the system falls below 82% of the total storage quota:
New link, sync, refresh and provisioning operations are allowed
Policy operations such as SnapSync, Snapshot, and Refresh resume for all platforms
dSources start pulling in new changes from their corresponding data sources. LogSync is resumed for Oracle and PostgreSQL
dSources. Validated sync is enabled for SQL Server dSources.
See Setting Quotas for more information.

Ways to View Capacity Usage

You can access capacity and performance information for the Delphix Engine through several different means, including the TimeFlow view, the
Dashboard view, and the Capacity screen.

The TimeFlow View

You can access the TimeFlow view by clicking the Delphix Logo in the Delphix Admin application, or selecting Databases > My Databases.
The TimeFlow view provides three summary performance metrics:
VDBS - all VDBs on the Delphix Engine. Inactive VDBs are greyed out.
TimeFlow Ratio - the total of Delphix Engine storage against the projected usage in a traditional physical database
Consolidation Ratio - the amount of space that dSources and VDBs occupy compared to the amount that would be occupied by a
traditional physical database

The Dashboard View

You can access the Dashboard view in the Delphix Admin application by clicking Dashboard in the top menu bar. Note that the Dashboard
view provides only summary information about capacity and performance. You must access the Capacity and Performance screens in the Reso
urces menu to manage storage space and database objects.
The Dashboard view provides more detailed information about the overall performance of the Delphix Engine and its network in five panels:
Job History - all jobs that have been initiated in the system and their outcome

157

Delphix User Guide 2016 Delphix

Capacity Management - the amount of physical storage available and what is currently used
TimeFlow Ratio - see above
VDB Ratio - a measure of the amount of physical space that would be occupied by the database content against the amount of storage
occupied by that same database content as VDBs.
Performance Management - the amount of network bandwidth available and the amount that VDBs are currently utilizing, as well as
information about specific VDB network usage

The Capacity Screen

You can access the Capacity screen through the Resources menu in the Delphix Admin application.
The Capacity screen provides a view of storage allocation for dSources, VDBs, and Snapshots by group and objects within the group, as well as
a summary metric. You can also access a graph view of the Capacity screen by clicking Graph View in the upper right corner of the screen. This
view shows Available Space as green, Used Capacity as blue, and Reserved Space as yellow.
Grid Column

Notes

Name

Name of the group or database object. Click the expand icon next to a group name to see the objects in that group.

Date
Quota

The maximum amount of storage space allocated to the group or object, also known as the ceiling. See Setting Quotas for
more information. You can see quota allocations for groups and objects in the Graph view of the Capacity screen.

Used

Amount of storage space used by the group or object.

Unvirtualized

Estimated amount of space that the group or object would occupy in an unvirtualized state.

Ratio

The amount of storage space occupied by the group or object in the unvirtualized state as opposed to the amount of space it
occupies as a virtual object. This can also be thought of as the "de-duplication ratio."

Keep Until

For Snapshots, the number of days it is retained as set by the Snapshot Retention Policy. See the topics under Managing
Policies for more information.

Summary
Metric

Notes

dSource
Ratio

The total amount of storage space occupied by the sources of all dSources as opposed to the amount of storage space occupied
by the dSources themselves.

VDB
Ratio

The total amount of storage space occupied by the databases that are the sources for the VDBs as opposed to the amount of
storage space occupied by the VDBs.

TimeFlow
Ratio

The total amount of storage space occupied by all snapshots multiplied by their unvirtualized size as opposed to the amount of
storage space occupied by the virtualized snapshots, archive logs, and temp files.

Related Links
Adding and Expanding Storage Devices
Changing Snapshot Retention to Increase Capacity
Deleting Objects to Increase Capacity
Managing Policies
Setting Quotas

158

Delphix User Guide 2016 Delphix

Setting Quotas
This topic describes how to set quotas for database objects.

Procedure
1. Log into the Delphix Admin application with delphix_admin credentials.
2. Select Resources > Capacity.
3. In the Quotas column, click next to the group or object for which you want to set a quota.
4. Enter the amount of storage space you want to allocate for a quota.
5. Click outside the column again to set the amount.

Quotas and Low Space Errors

Be very careful setting quotas. As a group or virtual database (VDB) approaches the quota level, snapshots may fail and logs may not
be captured, causing LogSync to fail. If quotas prevent logs from being written to snapshots, or if a low space condition arises, the
Delphix Engine will halt.
When a low space condition arises, the Delphix Engine will generate an Out of Space error message. If you do not correct the low
space condition, the server will enter Maintenance Mode. This will disable all SnapSyncs, LogSyncs, and growth of VDBs, including
VDB archive logs. If the situation is severe enough, it may require the assistance of Delphix Support to recover the system.

159

Delphix User Guide 2016 Delphix

Deleting Objects to Increase Capacity

This topic describes how to delete database objects to create additional capacity.
Deleting unused or outdated objects should be a regular part of Delphix Engine administration. This is especially important to prevent low space
errors, which can cause the Delphix Engine to stop.

Procedure
1. Log into the Delphix Admin application using delphix_admin credentials.
2. Select Resources > Capacity.
3. Select the groups or objects you want to delete.
As you select items, you will see them added to the Total Capacity of Objects Selected for Deletion.
4. Click Delete.

Dependencies
If there are dependencies on the SnapShot you will not be able to delete the SnapShot free space; the dependencies rely on the data
associated with the SnapShot.If there are dependencies on the SnapShot you will not be able to delete the SnapShot free space; the
dependencies rely on the data associated with the SnapShot.

160

Delphix User Guide 2016 Delphix

Changing Snapshot Retention to Increase Capacity

This topic describes how to manage capacity by changing the Snapshot discard date on the Capacity screen.
The accumulation of snapshots can have a substantial effect on capacity. For this reason, it is important that you set the snapshot frequency
policy to accurately reflect the rate of change in your database, and set snapshot and log retention policies that are appropriate for your desired
ability to recover Delphix Engine objects. See the topics under Managing Policies for more information. If you want to discard snapshots outside
of a set policy, you can change the number of days they are retained on the Capacity screen.

Procedure
1. Log into the Delphix Admin application using delphix_admin credentials.
2. Select Resources > Capacity.
3. Click in the Keep Until column for the snapshot you want to edit.
4. Select the number of days you want to preserve the snapshot.
5. Click outside the column to set the change.

Deleting Snapshots Associated with VDBs

Snapshots that have been used to provision Virtual Databases cannot be deleted.

161

Delphix User Guide 2016 Delphix

Delphix Storage Migration

Getting Started
Understanding Delphix Storage Migration
Limitations of Delphix Storage Migration
User Interface
Device Removal for Storage Migration
Getting the UUID of a RDM Disk from VMware, via the vSphere GUI
Related Links

Getting Started
Delphix storage migration is a new feature available in Delphix Engine version 4.3. This feature allows you to remove storage devices from your
Delphix Engine, provided there is sufficient unused space, thus allowing you to repurpose the removed storage device to a different server. You
can also use this feature to migrate your Delphix Engine to different storage by adding the new storage devices and then removing the old storage
devices.

Understanding Delphix Storage Migration

Delphix storage migration is a multi-step process:
1. Identify a storage device for removal. The device you choose will depend on your use case.
a. To remove extra storage that is unused, you can select any device for removal. For best performance, select the device with the
least allocated space; typically, this is the device that you added most recently. The allocated space is defined by the usedSize
property of the storage device:

areece-test1.dcenter 'Disk10:2'> ls
Properties
type: ConfiguredStorageDevice
name: Disk10:2
bootDevice: false
configured: true
expandableSize: 0B
model: Virtual disk
reference: STORAGE_DEVICE-6000c293733774b7bb0e4aea83513b36
serial: 6000c293733774b7bb0e4aea83513b36
size: 8GB
usedSize: 7.56MB
vendor: VMware

b. To migrate the Delphix Engine to new storage, add storage devices backed by the new storage to the Delphix Engine, then
remove all the devices on the old storage.
2. Use the Delphix command line interface (CLI) to initiate the removal of your selected device.
3. Data will be migrated from the selected storage device to the other configured storage devices. This process will take longer the more
data there is to move; for very large disks, it could potentially take hours. You can cancel this step if necessary.
4. The status of the device changes from configured to unconfigured and an alert is generated to inform you that you can safely detach
the storage device from the Delphix Engine. After this point, it is not possible to undo the removal, although it is possible to add the
storage device back to the Delphix Engine.
5. Use the hypervisor to detach the storage device from the Delphix Engine. After this point, the Delphix Engine is no longer using the
storage device, and you can safely re-use or destroy it.

Limitations of Delphix Storage Migration

Currently, it is possible to remove an unlimited number of devices by means of Delphix storage migration. After a removal, the Delphix Engine
uses memory to track the removed data. In the worst-case scenario, this could be as much as 1GB of memory per 1TB of used storage. Note that
this is used storage; the overhead of removing a 1TB device with only 500MB of data on it will be much lower than the overhead of removing a
10GB device with 5GB of data on it.

162

Delphix User Guide 2016 Delphix

User Interface
Delphix storage migration is currently available exclusively via the CLI. There are 3 entry points:

storage/remove

The status of the current or most recent removal, including the total memory used by all removals up to

this point

storage/device $device/removeVerify

Returns the predicted effect of removing the selected device, or an

error if the device cannot be removed

storage/device $device/remove

Begins the evacuation and removal of the selected device

Device Removal for Storage Migration

1. Identify which device you want to remove.
a. If you are using a VMware RDM disk, note the UUID of the device by looking at its name in the vSphere GUI. For more
information, see this Getting the UUID of a RDM Disk from vmware, via the vSphere GUI.
b. If you are using a VMware virtual disk, note the UUID of the device via the vSphere API. See the section of this VMware KB
article on how to get the UUID of your virtual disk .
c. In EC2, note the attachment point for example, /dev/sdf.
d. In KVM, note the UUID.
2. Login to the Delphix CLI as a sysadmin user and navigate to storage/device.
3.

Type cd storage/device.

4. Select your device:

areece-test1.dcenter storage device> ls
Objects
NAME
CONFIGURED SIZE EXPANDABLESIZE
Disk10:2 true
8GB
0B
Disk10:0 true
24GB 0B
Disk10:1 true
8GB
0B
Disk10:3 true
8GB
0B
areece-test1.dcenter.dcenter storage device> select Disk10:2

5. (VMware only) Confirm that your disk selection is correct by validating that the serial matches your UUID:
areece-test1.dcenter storage device 'Disk10:2'> ls
Properties
type: ConfiguredStorageDevice
name: Disk10:2
bootDevice: false
configured: true
expandableSize: 0B
model: Virtual disk
reference: STORAGE_DEVICE-6000c2909ccd9d3e4b5d62d733c5112f
serial: 6000c2909ccd9d3e4b5d62d733c5112f
size: 8GB
usedSize: 8.02MB
vendor: VMware

6. Execute removeVerify to confirm that removal will succeed. Validate the amount of memory/storage used by the removal:
areece-test1 storage device 'Disk10:2'> removeVerify
areece-test1 storage device 'Disk10:2' removeVerify *> commit
type: StorageDeviceRemovalVerifyResult
newFreeBytes: 15.85GB
newMappingMemory: 3.14KB
oldFreeBytes: 23.79GB
oldMappingMemory: 0B

7. Execute remove to start the device evacuation:

areece-test1 storage device 'Disk10:2'> remove
areece-test1 storage device 'Disk10:2' remove *> commit
Dispatched job JOB-1
STORAGE_DEVICE_REMOVAL job started for "Disk10:2".

163

7.
Delphix User Guide 2016 Delphix

0.63GB out of 0.68GB remaining.

0.59GB out of 0.68GB remaining.
...
8. Wait for device evacuation to complete. Alternatively, you can cancel the evacuation. Do NOT detach the device from the Delphix
Engine in your hypervisor until after the data evacuation has completed. The screenshot below illustrates a progress bar for
completion.

9. Once the device evacuation has completed, the job will finish and a fault will be generated. Detach the disk from your hypervisor and the
fault will clear on its own. An example of the fault created is seen below.

When using VMDKs, deleting the wrong VMDK could cause data loss. Therefore, it is highly advisable to detach the device, then verify
that the Delphix Engine continues to operate correctly, and lastly delete the VMDK.

Getting the UUID of a RDM Disk from VMware, via the vSphere GUI
1. In the ESX graphical user interface (GUI), select your VM.
2. Click Edit settings.
3. If not already displayed, select the Hardware tab.
4. Select the device you want to remove.
5.

Click Manage Paths.

164

Delphix User Guide 2016 Delphix

The UUID of the device appears in the title bar, as seen below.

165

Delphix User Guide 2016 Delphix

Related Links
Adding and Expanding Storage Devices

166

Delphix User Guide 2016 Delphix

Adding and Expanding Storage Devices

This topic describes adding and expanding storage devices after initial configuration. Delphix recommends expanding existing storage whenever
possible; if it is not possible to expand Delphix recommends adding new LUNs of equal size to the existing storage pool.

Prerequisites
If you are expanding a storage device after initial configuration, first make sure to add capacity to it using the storage management tools available
through the device's operating system. In vSphere, for example, you can add capacity using Edit System Settings.

Procedure
1. Launch the ServerSetup application and log in using the sysadmin credentials.
2. In the Storage section of the Server Setup Summary screen, click Modify.
3. The Delphix Engine should automatically detect any new storage devices.
If a newly added storage device does not appear in in the Storage section of the Server Setup Summary screen, click Rediscover.
4. Select Expand for each device that you want to expand.
The Expand checkbox appears next to the name of devices that have added capacity (in other words, the underlying LUN has been
expanded), and the Unused column indicates how much capacity is available for each device. Newly-added devices will have a
drop-down in the Usage Assignment column. Set the Usage Assignment to DATA for newly-added devices that you wish to add to the
storage pool.
5. Click OK.

WARNING: DO NOT REMOVE A CONFIGURED STORAGE DEVICE

Do not remove a configured storage device or reduce its capacity. Removing or reducing a configured storage device will cause a fault
with the Delphix Engine, and will require the assistance of Delphix Support for recovery.

Related Links
Setting Up the Delphix Engine

167

Delphix User Guide 2016 Delphix

System Monitoring
These topics describe system monitoring features.
Configuring SNMP
Viewing Action Status
System Faults
Viewing System Events
Accessing Audit Logs
Creating Support Logs
Setting Support Access Control
Setting SysLog Preferences
Diagnosing Connectivity Errors
Email (SMTP) Alerts

168

Delphix User Guide 2016 Delphix

Configuring SNMP
This topic describes how to configure SNMP.
SNMP is a standard protocol for managing devices on IP networks. The Delphix Engine can be configured to send alerts to an external SNMP
manager.

Prerequisites
At least one SNMP manager must be available, and must be configured to accept SNMPv2 InformRequest notifications.
Delphix's MIB (Management Information Base) files must be installed on the SNMP manager or managers. These MIB files describe the
information that the Delphix Engine will send out. They are attached to this topic.

Procedure
1. Choose the Server Setup option at the Delphix Engine login screen.

2. Log into the Server Setup application of the Delphix Engine using the sysadmin username and password in the Delphix Setup login
screen.
3. Select Engine Setup.
4. On the Delphix Engine Setup screen, select Delphix Engine Preferences > SNMP Configuration.
5. Set the severity level of the messages you want to be sent to the SNMP manager(s).
6. Click the + icon.
7. Enter an SNMP Manager hostname / IP address.
Provide a community string and adjust the port number if necessary.
8. Click Save.
The newly-entered manager will appear in the list.
9. An attempt will be made to connect with the SNMP manager by transmitting an informational level message. If a response
is received from the manager within 20 seconds, a checkmark will appear along with the manager entry. If not, a red X will appear
check your settings and try again.

169

Delphix User Guide 2016 Delphix

Viewing Action Status

Action Sidebar Procedure
Description
Sub-action
Errors
Procedure to Open the Dashboard

This topic describes how to view the status of actions for the Delphix Engine.
To view the status of actions that are currently running on the Delphix Engine, open the Action sidebar. To view details of currently-running and
completed jobs, open the Dashboard.

Action Sidebar Procedure

1. Login to the Delphix Admin or ServerSetup application.
Depending on the width of the window, the Action sidebar may be automatically displayed on the right of the screen.
2. To see the Action sidebar, click Action on the top navigation bar.

Description
The Action sidebar consists of two sections. The top section lists actions that are currently running on the Delphix Engine. The bottom section,
labeled Recently completed, contains actions which have recently completed.
Each action is initially collapsed and only presents the title of the action. Click an action to expand it and see more details such as progress,
elapsed time, and a description of the operation in progress.
The following is an example of the Action sidebar when a Link action is running.

Action sidebar, Link, Version 4.2.0

If you are a Delphix Admin or a System Admin, you will be able to see all actions of your respective application. If you are not an admin user, you
will only see actions you have permissions to see.
The following is an example of the Action sidebar when a Link action is running.

170

Delphix User Guide 2016 Delphix

Action sidebar, Link, Version 4.2.0

Sub-action
Each action may contain one or several sub-actions which represent the execution of a subset of the action itself. Click an action to see its
sub-actions and their respective details. Note that the list of sub-actions is created dynamically during the execution of the action.
The following is an example of an Environment Refresh action and its sub-actions.

Action sidebar, Refresh, Version 4.2.0

171

Delphix User Guide 2016 Delphix

Action sidebar, Refresh, Version 4.2.0

Errors
When an error condition occurs during the execution of an action, the background color of the action's box becomes red, and the action remains
in the top section until you dismiss it.
1. Click the action title to expand it.
The action will expand to display a description of the error, suggestions to resolve it, and sometimes the raw output of command
execution.
To dismiss the action:
1. Click the X next to the action displaying an error.
The following is an example of an action failure displayed in the Action sidebar.

Action sidebar, Failure, Version 4.2.0

172

Delphix User Guide 2016 Delphix

The following is an example of an action failure displayed in the Action sidebar.

Action sidebar, Failure, Version 4.2.0

Procedure to Open the Dashboard

1. Login to the Delphix Admin application using delphix_admin credentials.
2. Click Dashboard in the top menu bar.
The Jobs panel displays all jobs that have been initiated by the Delphix Engine, and their status.
3. Click Settings to set date range and filter criteria for jobs.
4. Click Search.
5. To view details for a job, click the information icon.

173

Delphix User Guide 2016 Delphix

System Faults
Overview
Viewing Faults
Addressing Faults
Fault Lifecycle Example
Related Links

Overview
This topic describes the purpose and function of system faults.
System faults describe states and configurations that may negatively impact the functionality of the Delphix Engine which can only be resolved
through active user intervention. When you login to the Delphix Admin application as a delphix_admin, the number of outstanding system faults
appears on the right-hand side of the navigation bar at the top of the screen. Faults serve as a record of all issues impacting the Delphix Engine
and can never be deleted. However, ignored and resolved faults are not displayed in the faults list.

System Faults indicator in the navigation bar

Viewing Faults
To view the list of active system faults:
1. Click Faults on the right-hand side of the navigation bar.
2. Click any fault in the list to expand it and see its details.
Each fault is comprised of six parts:
Severity How much of an impact the fault will have on the system. A fault may have a severity of either Warning or Critical. A Warning
Fault implies that the system can continue despite the fault but may not perform optimally in all scenarios. A Critical Fault describes an
issue that breaks certain functionality and must be resolved before some or all functions of the Delphix Engine can be performed.
Date The date the fault was diagnosed by the Delphix Engine.
Target Object The object that the fault was posted against
Title A short descriptive summary of the fault
Details A detailed summary of the cause of the fault
User Action The action you can take to resolve the fault.

174

Delphix User Guide 2016 Delphix

Parts of each system fault

Addressing Faults
After viewing a fault and deciding on the appropriate course of action, you can address the fault through the user interface (UI). You can mark a
fault as Ignored or Resolved. If you have fixed the underlying cause of the fault, mark it as Resolved. Note that if the fault condition persists, it
will be detected in the future and re-diagnosed. You can mark the fault as Ignored if it meets the following criteria:
The fault is caused by a well-understood issue that cannot be changed
Its impact to the Delphix Engine is well understood and acceptable
In this case, the fault will not be re-diagnosed even if the fault condition persists. You will receive no further notifications.
To address a fault follow the steps below.
1. In the top menu bar, click Faults.
2. In the list of faults, click a fault date/name to view the fault details.
3. If the fault condition has been resolved, click Mark Resolved.
Note that if the fault condition persists it will be detected in the future and re-diagnosed.
4. If the fault condition describes a configuration with well-understood impact to the Delphix Engine that cannot be changed, you can ignore
the fault by clicking Ignore.
Note that an ignored fault will not be diagnosed again even if the underlying condition persists.

When a critical fault occurs, the Delphix Engine immediately sends an email to the delphix_admin. Make sure you have
configured an SMTP server so that this email can be sent. See Setting Up the Delphix Engine for more information.

Fault Lifecycle Example

175

Delphix User Guide 2016 Delphix

Below is an image of the fault card for the fault "TCP slot table entries below recommended minimum."

The Details section of the fault explains that the sunrpc.tcp_slot_table_entries property on frodo.dcenter.delphix.com is set to a value that is
below the recommended minimum of 128. The User Action section instructs you to adjust the value of the sunrpc.tcp_slot_table_entries property
upward to the recommended minimum. The process for adjusting this property differs between operating systems. To resolve the underlying
issue, search "how to adjust sunrpc.tcp_slot_table_entries" using a search engine and find that the second result is a link to the Delphix
community forum describing how to resolve this issue. After following the instructions applicable to your operating system, return to the Delphix UI
and mark the fault Resolved.

Related Links
Setting Up the Delphix Engine

176

Delphix User Guide 2016 Delphix

Viewing System Events

This topic describes how to view system event information.

Procedure
1. Launch the Delphix Admin application and log in with delphix_admin credentials.
2. Select System > Event Viewer.
3. Select a time range.
4. Click Search.

177

Delphix User Guide 2016 Delphix

Accessing Audit Logs

This topic describes how to access audit logs. The audit log provides a record of all actions that were initiated by a policy or user, regardless of
whether that action was successful.

Procedure
1. Log into the Delphix Admin application using delphix_admin credentials.
2. Select System > Audit Logs.
3. Select an audit log time range.
4. Click Search.

178

Delphix User Guide 2016 Delphix

Creating Support Logs

This topic describes how to create support bundles and manage server access control for Delphix Support.
Support bundles are used by Delphix Support as diagnostic tools for resolving Delphix Engine issues and routine maintenance. Support bundles c
an be transferred directly to Delphix Support or downloaded. No customer-specific data is included in the support bundle information, all
passwords and personal data are either encrypted or omitted. This is an outbound only connection from the Delphix Engine.

Procedure
Using the GUI:
1. Log into the Delphix Admin application using delphix_admin credentials.
2. Select System > Support Logs
3. Select Transfer or Download.
a. If you select Download, then the support bundle will be downloaded as a ".tar" file into a folder on your workstation
b. If you select Transfer, then the support bundle will be uploaded over HTTPS to Delphix Support. If you have configured an
HTTP proxy, it will be used to send the support bundle.
c. If there is a support case involved, please enter the case number to associate the bundle to the case
4. Click OK.
a. If you had selected Download and have the ".tar" file in a folder on your workstation, please upload that file to Delphix Support
via the website at "http://upload.delphix.com".
b. If there is a support case involved, please enter the case number (again) to associate the bundle to the case

You can also access support log functionality in the ServerSetup application using sysadmin credentials. Click Support Bundles in
the top menu bar.

Using the CLI

1. ssh into your Delphix Engine

ssh <delphix_user>@<delphixengine>
2. Run the upload operation

delphix
delphix
delphix
delphix

> service
service > support
service support > bundle
service support bundle > upload

3. Commit the operation

delphix service support bundle upload *> commit

179

Delphix User Guide 2016 Delphix

Setting Support Access Control

This topic describes how to set the Support Access Control for Delphix Support.
Support access control enables Delphix Support to access your instance of the Delphix Engine for a defined period of time using an access token.

Procedure
1. Log into the ServerSetup application using sysadmin credentials.
2. Select Server Preferences > Support Access.
3. Click Enable.
4. Set the time period during which you want to allow Delphix Support to have access to your instance of the Delphix Engine.
5. Click Generate Token.
Provide the token to Delphix Support to enable access to your server.

180

Delphix User Guide 2016 Delphix

Setting SysLog Preferences

Syslog is a widely used standard for message logging. It permits the separation of the software that generates messages, the system that stores
them, and the software that reports and analyzes them. Delphix makes use of syslog as one of the standard mechanisms, along with SNMP and
email, to distribute important user and system events, such as alerts, faults, and audits. In the case of Delphix, each Delphix Engine acts as a
syslog client which propagates the events to a centralized syslog server.
The network protocol over which Delphix Engine communicates with the syslog server is standardized in RFC 5424. As a protocol, it supports
using either UDP (RFC 5426) or TCP (RFC 6587) as the underlying transport and optional TLS mapping has been introduced to encrypt the
messages over the wire for security purposes (RFC 5425). However, as of this release, we only support syslog over UDP with no encryption,
which implies that syslog messages are always sent in the clear and may be lost during transmission and delivered out of order due to the
limitations of UDP.
To configure for syslog support, you must specify the communication end point to which the syslog server listens, which includes the hostname or
IP address of the syslog server and an optional port number. The latter defaults to 514 according to the syslog standard but it can be changed if
necessary.
System and user events generated by Delphix are always forwarded immediately to the syslog server, which ensures timely delivery of important
events that may require immediate action.
A couple of different output formats are supported for messages delivered over syslog, namely, TEXT and JSON. The TEXT format is the default.
To change the message format, as of this release, you must do so via the CLI.

Procedure
1. Log into the ServerSetup application using sysadmin credentials.
2. Select Server Preferences > Syslog Configuration.
3. Select the severity level of the messages you want sent to the SysLog server.
4. Click Add Server.
5. Enter the SysLog server hostname/IP address and port number.
6. Click Add.
7. Click Enable.

181

Delphix User Guide 2016 Delphix

Diagnosing Connectivity Errors

Prior to the current release, when the Delphix Engine ran into an error operating on an external database or environment, it reported the
immediate error that it had encountered; there was no mechanism for automatic analysis of the root causes of failures. The current release
includes infrastructure for automatic diagnosis of errors. When one of these errors occurs, the Delphix Engine now launches of a set of tests to
locate the root cause of the problem and present the result of the diagnosis. This will help you easily identify the true sources of errors such as
closed ports or misconfigured routers.
Failed Actions
The Delphix Engine communicates failures in two different manners: actions that fail to complete, and faults. To view failed actions:
1. In the top right-hand corner of the Delphix user interface (UI), click Actions.
2. For more information about why the action failed, click the () icon to show the error dialog as seen in the image below.

This shows a popup message with more information about the problem and what actions to take to resolve it. For some errors, the Delphix Engine
will be able to diagnose the problem further and display this extra information under Diagnosing Information. In the screenshot above, the job
failed because the Delphix Engine was unable to lookup the host address.
Viewing Active Faults
A fault symbolizes a condition that can affect the performance or functionality of the Delphix Engine and must be addressed. Faults can be either
warnings or critical failures that prevent the Delphix Engine from functioning normally. For example, a problem with a source or target environment
can cause SnapSync or LogSync policy jobs to fail. Faults will show up as active as long as:
The error is still occurring, or
You have chosen to manually resolve it or ignore it
For example, if a background job fails, it will create a fault that describes the problem. To view any active faults:
1. In the top right-hand corner of the Delphix UI, click Faults.
This brings up a popup box listing all active faults.

The screenshot above illustrates a fault with regard to database network connectivity. The Delphix Engine will mark an object with a warning
triangle to indicate that it is affected by an external problem. You can view more details of the fault by looking at the active faults and their fault
effects.

182

Delphix User Guide 2016 Delphix

Email (SMTP) Alerts

Overview
Configuring the SMTP Gateway
Alert Profiles
Creating Alert Profiles
Profile Filters
Action Types
Email Format Options

Overview
The configuration for SMTP-based alerts has two components:
Configuration of an SMTP gateway by the Delphix system administrator
Configuration of one or more alert profiles (if needed)

Configuring the SMTP Gateway

Prior to having email-based alerts function properly, many organizations require that an SMTP gateway be configured, through which all outbound
email is sent.
1. Contact the appropriate administrator for your site in order to determine the proper SMTP gateway settings.
2. Log into the Delphix Engine as sysadmin or another user with system administrator privileges.
3. On the system summary page, locate the Serviceability section, and click Modify:
4. If not checked already, check the box next to Use an SMTP Server?
5. At a minimum, fill in the required information:
a. SMTP Server Name of IP Address
b. SMTP port
c. From Email Address
This will be the email address from which all alert email will be sent
6. Click Test in order to verify that youre able to receive email properly
7. Click OK to save changes
For further information, see the Serviceability section of Setting Up the Delphix Engine.

Alert Profiles
The Delphix Engine sends out notifications based on alert profiles. An alert profile contains various filtering options; if all conditions are met, a
notification is sent.
Alert profiles can define the following things:
Where to send the alert (email address)
Which alert severity to send (Critical, Warning, Informational, Audit)
Which objects to monitor (dSources, VDBs)
Which event types to monitor
By default the Delphix Engine has a single alert profile configured with the following parameters:
Where to send the alert: Email Address defined for user delphix_admin
Which alert severity to send: CRITICAL or WARNING
Which objects to monitor: ALL
Which event types to monitor: ALL
Using the CLI, it is possible to:
Modify the system default alert profile
Create additional profiles in addition to the default one
Set multiple actions for a single profile, such as "email dephix_admin" and "email [email protected]".

183

Delphix User Guide 2016 Delphix

Creating Alert Profiles

1. ssh into your engine using your delphix_admin username and password

ssh delphix_admin@yourdelphixengine
2. Go into your alerts and list the alerts you already have

delphix > alert

delphix alert > ls
3. Create your profile

delphix alert > profile

delphix alert profile > create
delphix alert profile create * > ls
4. Set Actions and Severity Filter

delphix alert profile create *> set actions.0.type=<AlertActionEmailList or

AlertActionEmailUser>
delphix alert profile create *> set actions.0.addresses.0=<email address to send to>
delphix alert profile create *> set actions.0.addresses.1=<additional email address>
delphix alert profile create *> set actions.0.addresses.2=<additional email address>
delphix alert profile create *> ls
delphix alert profile create *> set severityFilter=
delphix alert profile create *> set
severityFilter=<AUDIT|WARNING|CRITICAL|INFORMATIONAL>

Valid Values for Parameters

actions.0.type:
AlertActionEmailList: This type of alert is used to create an alert for any number of users. When this type is selected,
an email address may be defined in each element of the "actions.0.addresses" array as illustrated above.
AlertActionEmailUser: This type of alert is created for the email address of the user currently logged into the command
line interface. The "actions.0.addresses" array is not available for this type.
actions.0.severityFilter:
INFORMATIONAL
WARNING
CRITICAL
AUDIT

5. Commit your changes

delphix alert profile create *> commit

Profile Filters
As seen above, you can define what types of alerts are sent out to the various email addresses using the severityFilter filter. The three filter
types are:
Filter

Purpose

Example

severityFilter

Filter the alert being sent based on severity (critical,

warning, informational)

severityFilter=CRITICAL

184

This would send alerts for critical events on the engine

Delphix User Guide 2016 Delphix

eventFilter

Filter on the type of event being generated.

eventFilter=fault.*
This would only send alerts out based on faults generated on the
engine

targetFilter

Filter on events related to a particular source or target

database

targetFilter=Group/DB
This would only send out alerts related to the database DB located
in the group Group

These filters can be combined.

Action Types
When the action type is set to AlertActionEmailUser, the alert is created for the email address of the user currently logged into the command line
interface. The "actions.0.addresses" array is not available for this type.
Set action type to AlertActionEmailList in order to create an alert for any number of users. When this type is selected, an email address may be
defined in each element of the "actions.0.addresses" array as illustrated above.

Email Format Options

You can send plain text as well as structured JSON. JSON can be useful for constructing solutions which will parse the email and perform further
actions (notify, escalate, log).
To change the format, while updating an alert profile:

delphix alert profile ALERT_PROFILE-X update *> set actions.0.format=<JSON|TEXT>

185

Delphix User Guide 2016 Delphix

Performance Tuning
These topics describe how to use the performance analytics tool to improve performance of the Delphix Engine. Additionally, the topics that
describe specific configuration recommendations for hosts, networks, and storage to improve performance.
Configuration Options for Improved Performance
Network Performance Configuration Options
Optimal Network Configuration Parameters for the Delphix Engine
Network Operations Using the Delphix Session Protocol
Network Performance Tool (iPerf)
Network Performance Tool notes - Restricted
Storage Performance Configuration Options
Optimal Storage Configuration Parameters for the Delphix Engine
Storage Performance Tool (fio)
Storage Performance Tool notes - Restricted
Host Performance Configuration Options
Target Host Configuration Options for Improved Performance
Performance Analytics
Performance Analytics Tool Overview
Working with Performance Analytics Graphs in the Graphical User Interface
Performance Analytics Statistics Reference
Performance Analytics Tool API Reference
Performance Analytics Case Study: Using a Single Statistic
Performance Analytics Case Study: Using Multiple Statistics

186

Delphix User Guide 2016 Delphix

Configuration Options for Improved Performance

These topics describe configuration options to maximize the network, storage, database, and host performance for a Delphix Engine installation.
Network Performance Configuration Options
Optimal Network Configuration Parameters for the Delphix Engine
Network Operations Using the Delphix Session Protocol
Network Performance Tool (iPerf)
Network Performance Tool notes - Restricted
Storage Performance Configuration Options
Optimal Storage Configuration Parameters for the Delphix Engine
Storage Performance Tool (fio)
Storage Performance Tool notes - Restricted
Host Performance Configuration Options
Target Host Configuration Options for Improved Performance

187

Delphix User Guide 2016 Delphix

Network Performance Configuration Options

These topics describe configuration options to maximize the network performance of a Delphix Engine deployment.
Optimal Network Configuration Parameters for the Delphix Engine
Network Operations Using the Delphix Session Protocol
Network Performance Tool (iPerf)
Network Performance Tool notes - Restricted

188

Delphix User Guide 2016 Delphix

Optimal Network Configuration Parameters for the Delphix Engine

This topic describes basic network performance considerations for the Delphix Engine.

Network Architecture and Latency

All VDB I/O operations are serviced over the network. Delphix uses NFS as the primary transport for Oracle VDBs, and iSCSI+NTFS for MS SQL
VDBs. The network architecture, latency, and capacity between the Delphix Engine and the target environment are the key network components
for improving performance of a Delphix deployment. Latency between the Delphix Engine and the source environment is not as critical for best
performance of VDBs.
For optimal performance of VDBs, round-trip latency between the Delphix Engine and the target environment should be kept under 1 millisecond,
and preferably in the range of 300 microseconds. If network latency exceeds 500 microseconds, the VDBs will not perform as well as a database
connected to physical storage.
Latency can be introduced by having to route the network packets across multiple networks, or by the presence of routers, switches, and firewalls
between the Delphix Engine and the target environment. Best practices to reduce network latency include:
Keep the Delphix Engine on the same subnet as the target environment
Reduce the number of hops between the Delphix Engine and the target environment
Reduce the number of switches in the network. Each switch can add 50 - 100 microseconds of latency to the network.
Reduce the number of routers in the network. Each router can add 500 - 1000 microseconds of latency in a network, and the
round trip for an I/O operation could increase by as much as 1 - 2 milliseconds.
There should be no firewalls between the Delphix Engine and the target environment.
When linking the Delphix Engine to a source database across a WAN, consider the time needed for the initial link and load. It may be
necessary to schedule the load operation as multiple steps across multiple days.

A Common WAN Deployment Architecture

189

Delphix User Guide 2016 Delphix

Deployment of the Delphix Engine on Separate Sub-Nets

Network Throughput and Bandwidth

Network throughput measures the rate at which data can be sent continuously between two servers on a network. Network throughput is affected
by network latency, but the dominant factor affecting throughput is the bandwidth of the network. As a point of comparison, consider the
bandwidth available for three types of Ethernet networks:
Ethernet Type

Network Bandwidth

100Mb Ethernet (100Base-T)

~=10MB/sec

Gigabit Ethernet (GbE)

~=100MB/sec

10 Gigabit Ethernet (10GbE)

~=1GB/sec

Low network throughput can impact the Delphix Engine in a number of ways:
Increasing the amount of time it takes to perform a SnapSync operation, both for initial load and subsequent regular snapshots
Managing LogSync operations in a high change environment
Poor VDB performance when an application is performing large sequential I/O operations, such as sequential table scans for reporting or
business intelligence, or RMAN backups of the VDB.
Delphix Engine throughput must exceed the sum of the peak I/O loads of all VDBs. Delphix incorporates an I/O-Collector toolkit to collect I/O data
from each production source database and pre-production server.
Best practices to improve network throughput include:

190

Delphix User Guide 2016 Delphix

Use 10 Gigabit Ethernet (10GbE)

Use a dedicated storage network
If you are concerned about your network throughput, you can test it with the open source tool netio. You will need to work with Delphix Support to
install netio on the Delphix Engine and run the tests.

191

Delphix User Guide 2016 Delphix

Network Operations Using the Delphix Session Protocol

This topic describes how the Delphix Engine uses the Delphix Service Protocol (DSP) for network operations, and how this affects features such
as replication, V2P, and SnapSync.

Overview
Delphix Session Protocol, or DSP, is a communication protocol that operates at the session and presentation layer in the Open Systems
Interconnection (OSI) model.

DSP supports the request-reply pattern for communication between two networked peers. In

contrast to the traditional remote

procedure call (RPC) models, which focus exclusively on low level details such as data encoding and wire framing,
DSP implements a generic session layer that supports a number of advanced functionalities desired for network
communication, including:
Full duplex remote operation execution and end-to-end cancellation support
Advanced connectivity model with connection trunking and ordered delivery
Fault resilience with automatic connection and session recovery, exactly-once semantics, and optional data digest
High performance with concurrent execution, session flow control, optional data compression and bandwidth throttling
Built-in security support with pluggable SASL authentication mechanisms and optional TLS encryption
Asynchronous model for session management and remote operation
Most of the features above are essential to the proper operation of a distributed application and yet non-trivial to implement. By offering them in
the framework, we can significantly simplify the development of enterprise quality distributed applications.
DSP is officially registered with the Internet Assigned Numbers Authority under the service name of dlpx-sp and port number 8415.
Currently, DSP supports the Java language binding and provides a java based service framework for distributed applications.

Key Concepts
The foundation of DSP is built on top of a few key abstractions, namely, exchange, task, nexus, and service. For an overview of how DSP
works and the features it provides, lets start with these abstractions.
An exchange refers to an application defined protocol data unit which may be a request or a response. DSP supports the request-response
pattern for communication. For each request sent, there is a corresponding response which describes the result of the execution. An application
protocol is made up of a set of exchanges.
A nexus (a.k.a., session) refers to a logical conduit between the client and server application. In contrast, a transport connection (a.k.a.,
connection) refers to a physical link. A nexus has a separate naming scheme from the connection, which allows it to be uniquely and persistently
identified independent of the physical infrastructure. A nexus has a different lifecycle than the connection. It is first established over a leading

192

Delphix User Guide 2016 Delphix

connection. After it comes into existence, new connections may be added and existing ones removed. It must have at least one connection to
remain operational but may live on even after all connections are lost. Nexus lifecycle management actions, such as create, recover, and destroy,
are always initiated by the client with the server remaining passive.
A nexus has dual channels, namely, the fore channel and the back channel. The fore channel is used for requests initiated from the client to the
server; and the back channel from the server to the client. From a request execution perspective, the nexus is full duplex and the channels are
functionally identical, modulo the operational parameters that may be negotiated independently for each channel. A channel supports a number of
features for request processing, such as ordered delivery, concurrent execution, remote cancellation, exactly-once semantics, and throughput
throttling.
A service refers to a contract that consists of all exchanges (both the requests and the corresponding responses) defined in an application
protocol. Given the full duplex nature of request execution in DSP, part of the service is fulfilled by the server and the remaining by the client,
where the client and server are from the nexus management perspective.
A task implements a workflow that typically involves multiple requests executed in either or both directions over the nexus. A task is a
self-contained building block, available in the form of a sharable module including both the protocol exchanges and implementation, that can be
easily integrated into other application protocols. A library of tasks may significantly simplify distributed application development by making it more
of an assembly experience.
The following is a diagram that illustrates the key abstractions and how they are related to each other.

Security
As a network protocol, DSP is designed with security in mind from the onset. It supports strong authentication as well as data encryption. It follows
a session based authentication model which requires each connection to authenticate before it is allowed to join the session. Authentication is
performed using the Simple Authentication and Security Layer (SASL) framework, a standard based pluggable security framework. The currently
supported SASL mechanisms include DIGEST-MD5, PLAIN with TLS, CRAM, and ANONYMOUS. Optionally, TLS encryption may be negotiated
between the client and the server for data privacy.

Performance
DSP offers a number of features to enable the support for high performance network applications. For example, it allows multiple requests to be
exchanged in both directions simultaneously, which provides effective pipelining of data transfer to minimize the impact of network latency while
ensuring the total ordering at the same time. It supports trunking that can effectively aggregate the throughput across multiple connections, which
is crucial for long fat network (LFN) and 10GigE. It also provides optional compression support which boosts performance over bandwidth limited
network. We have observed, through both internal benchmarking and in customer environment, DSP based applications delivering multi GigE in
an ideal environment and getting a performance boost of as much as x10 in bandwidth limited settings.

Resiliency
DSP automatically recovers from transient connection loss without any application involvement. It may also detect random data corruption on the
wire and automatically recovers from it. In both cases, outstanding requests are retried once the fault condition is resolved.
DSP offers control over a remotely executing request. Once a request is initiated, the application may cancel it at any time before completion. In
the rare event of a session loss, a new session creation request will be held until the old session has been reinstated. It ensures that we never
leave any unknown or unwanted activities on the remote side and provides better predictability and consistency guarantees over an otherwise
unreliable network.

193

Delphix User Guide 2016 Delphix

Diagnosability
Application exceptions encountered during remote execution of a request are communicated back to the initiator through DSP. A standard Java
API is used to facilitate the handling of remote exceptions that is in many ways identical to local ones.
DSP provides detailed information and statistics at the session level. The information may be used to examine the state of the session as well as
diagnose performance problems. It is currently exposed via an internal support tool called jmxtool.

Supported Applications
Replication is the first feature to take advantage of DSP. It has been rebuilt on top of DSP and shipping in the field since 3.1. In the latest release,
a number of host based applications, such as SnapSync, V2P, and Delphix connector, use DSP as well.

194

Delphix User Guide 2016 Delphix

Network Performance Tool (iPerf)

Overview
This iperf-based Network Performance Tool executes a synthetic workload on the network to evaluate the performance characteristics available
between the Delphix Engine and Target servers. The Network Performance Tool is a feature that is only available from the command line
interface (CLI).

Prerequisites
The network performance tool measures network performance between a Delphix Engine and an environment host. You must have added an
environment in order to use this tool. At this time, this tool only supports Unix environments, while windows environments must be tested
manually.
This transmission control protocol (TCP) throughput test uses TCP port 50001 by default. The port can also be configured on a
per-test-run basis. For the duration of a given throughput test, a server on the receiver will be listening on this port. For a transmit test,
the receiver is the remote host; for a receive test, the receiver is the Delphix Engine.

Running the Network Test via CLI - Latency

The network latency test measures network round-trip latency by transmitting ICMP echo requests (like the ping utility) and measuring the time to
receive replies from the remote host. To execute a test:
1. Login as a domain user to the Delphix Engine CLI using ssh.
2. Create a network latency test

delphix> network test latency

delphix network test latency> create
delphix network test latency create *>
3. You must set remoteHost to the name of an environment host already configured in the Delphix engine. Use 'get' to see other optional
arguments. Modify the test parameters as needed and commit to start the test.

delphix network test latency create *> set remoteHost=oracletarget

delphix network test latency create *> get
type: NetworkLatencyTestExecuteParameters
remoteHost: oracletarget
requestCount: 20
requestSize: 8B
delphix network test latency create *> commit
Dispatched job JOB-20
NETWORK_LATENCY_TEST_EXECUTE job started for
"oracletarget-2014-06-20T18:57:28.659Z".
Executing network latency test.
NETWORK_LATENCY_TEST_EXECUTE job for "oracletarget-2014-06-20T18:57:28.659Z"
completed successfully.
4. The job will be submitted and visible in the Delphix Engine GUI
5. Retrieve the test results. All times are in microseconds.

195

Delphix User Guide 2016 Delphix

delphix network test latency> list

NAME
AVERAGE
oraclesource-2014-06-20T18:57:28.659Z 872
delphix network test latency> select oraclesource-2014-06-20T18:57:28.659Z
delphix network test latency "oraclesource-2014-06-20T18:57:28.659Z"> get
type: NetworkLatencyTest
name: oraclesource-2014-06-20T18:57:28.659Z
average: 872
endTime: 2014-06-20T18:57:48.558Z
loss: 0
maximum: 2755
minimum: 294
reference: NETWORK_LATENCY_TEST-2
remoteAddress: 172.16.203.184
remoteHost: oraclesource
requestCount: 20
requestSize: 8B
startTime: 2014-06-20T18:57:28.659Z
stddev: 527

Running the Network Test via CLI - Throughput

The network throughput test measures sustained throughput using a synthetic workload to or from a remote host. To execute a test:
1. Login as a domain user to the Delphix Engine CLI using ssh.
2. Create a network throughput test.

delphix> network test throughput

delphix network test throughput> create
delphix network test throughput create *>
3. You must set remoteHost to the name of an environment host already configured in the Delphix engine. Use 'get' to see other optional
arguments. Modify the test parameters as needed and commit to start the test.

196

Delphix User Guide 2016 Delphix

delphix network test throughput create *> set remoteHost=oraclesource

delphix network test throughput create *> ls
Properties
type: NetworkThroughputTestParameters
blockSize: 128KB
direction: TRANSMIT
duration: 30
numConnections: 0
port: 50001
receiveSocketBuffer: 4MB
remoteHost: oraclesource
sendSocketBuffer: 4MB
delphix network test throughput create *> commit
Dispatched job JOB-21
NETWORK_THROUGHPUT_TEST_EXECUTE job started for
"oraclesource-2014-06-20T19:30:12.566Z".
Executing network throughput transmit test.
Measuring throughput with variable number of connections: 1.
Measuring throughput with variable number of connections: 2.
Measuring throughput with variable number of connections: 4.
Measuring throughput with variable number of connections: 6.
Measuring throughput with variable number of connections: 8.
Measuring maximum sustained throughput for 30 seconds with 8 connections.
NETWORK_THROUGHPUT_TEST_EXECUTE job for "oraclesource-2014-06-20T19:30:12.566Z"
completed successfully.
4. The job will be submitted and visible in the Delphix Engine GUI
5. Retrieve the test results

delphix network test throughput> list

NAME
DIRECTION
STATE
THROUGHPUT
oraclesource-2014-06-20T19:30:12.566Z TRANSMIT
COMPLETED 695.6Mbps
delphix network test throughput> select oraclesource-2014-06-20T19:30:12.566Z
delphix network test throughput "oraclesource-2014-06-20T19:30:12.566Z"> get
type: NetworkThroughputTest
name: oraclesource-2014-06-20T19:30:12.566Z
endTime: 2014-06-20T19:31:15.041Z
numConnections: 8
parameters:
type: NetworkThroughputTestParameters
blockSize: 128KB
direction: TRANSMIT
duration: 30
numConnections: 0
port: 50001
receiveSocketBuffer: 4MB
remoteHost: oraclesource
sendSocketBuffer: 4MB
reference: NETWORK_THROUGHPUT_TEST-2
remoteAddress: 172.16.203.184
startTime: 2014-06-20T19:30:12.566Z
state: COMPLETED
throughput: 695.6Mbps

197

Delphix User Guide 2016 Delphix

Storage Performance Configuration Options

These topics describe options for maximizing the storage performance of a Delphix Engine deployment.
Optimal Storage Configuration Parameters for the Delphix Engine
Storage Performance Tool (fio)
Storage Performance Tool notes - Restricted

198

Delphix User Guide 2016 Delphix

Optimal Storage Configuration Parameters for the Delphix Engine

This topic describes minimum capacity and throughput requirements for storage devices used with the Delphix Engine.
Storage for the Delphix Engine must be able to sustain the aggregated Input/Output Operations Per Second (IOPS) and throughput (MBPS)
requirements of all its Virtual Databases. Throughput required for data source synchronization (SnapSync and LogSync) must also be supported.
The Delphix Engine requires storage for:
Item

Description

A copy of
each Source
Database

The copies are compressed.

Unique Block
Changes in
VDBs

When changes are made to a VDB, the Delphix Engine stores the changes in new blocks associated with only that VDB. The
new blocks are compressed.

Timeflow for
dSources
and VDBs

The TimeFlow kept for each dSource and VDB comprises snapshots of the database (blocks changed since the previous
snapshot) and archive logs. The retention period for this history of changes is determined by polices established for each
dSource and VDB. The TimeFlow is compressed.

In addition to the storage for these items, the Delphix Engine requires 30% free space in its storage for best performance. See An Overview of
Capacity and Performance Information and related topics for more details on managing capacity for the Delphix Engine.
Best practices for storage performance include:
Initial storage equal to the size of the physical source databases. For high redo rates and/or high DB change rates, allocate an additional
10-20% storage.
Add storage when storage capacity approaches 30% free
Use physical LUNS allocated from storage pools or RAID groups that are configured for availability
Never share physical LUNs between the Delphix Engine and other storage clients.
Keep all physical LUNs the same size. Add new storage by provisioning new LUNs of the same size.
Provision storage using VMDKs or RDMs operating in virtual compatibility mode.
VMDKs should be Thick Provisioned, Eager Zeroed. The underlying physical LUNs can be thin provisioned.
Physical LUNs used for RDMs should be thick provisioned.
Measure or estimate the required IOPS and manage the storage disks to provide this capacity. It is common to use larger numbers of
spindles to provide the IOPS required.
Physical LUNs carved from RAID 1+0 groups or pools with dedicated spindles provide higher IOPS performance than other
configurations
Maximize Delphix Engine vRAM for a larger system cache to service reads
Example
There are two production dSources, totalling 5 TB in size. 5 VDBs will be created for each. Sum of read and write rates on the production source
database is moderate (1000 iops), sum of VDB read rate is moderate (950 iops), and VDB update rate is low (50 iops).
Initial storage equal to 5TB, provisioned as 5 x 1 TB physical LUNs, Thin Provisioned. Allow for expansion of the LUNs to 2TB.
Provision as 5 x 950 GB Virtual Disks. VMDKs must be Thick Provisioned, Eager Zeroed. Using 1 TB LUNs allows expansion to 2 TB
(ESX 5.1 limit).
The storage provisioned to the Dephix Engine storage must be able to sustain 1000 IOPs (950 + 50). For this reason, each physical LUN
provisioned to the Delphix Engine must be capable of sustaining 200 IOPs. IOPs on the source databases are not relevant to the Delphix
Engine.
64GB Delphix Engine vRAM for a large system cache

Related Topics
Optimal Network Configuration Parameters for the Delphix Engine
An Overview of Capacity and Performance Information

199

Delphix User Guide 2016 Delphix

Storage Performance Tool (fio)

Overview
This fio-based Storage Performance Tool executes a synthetic workload to evaluate the performance characteristics of the storage assigned to
the Delphix Engine. The Storage Performance Tool is a feature that is only available from the command line interface (CLI). Because the test is
destructive, the Storage Performance Tool can only be run prior to setting up the Delphix Engine, or when adding new storage devices.

Prerequisites
Prior to setting up the Delphix Engine, the admin can login to the Delphix CLI using a sysadmin account to launch the Storage Performance Tool.
Because the test is destructive, it will only run against storage which has not been allocated to Delphix for use by the engine. If the storage has
already been allocated but is is acceptable to lose all the data on Delphix, a factory reset can be used to wipe out all data and configuration,
allowing the Delphix-assigned storage to be re-tested.

Running the Storage Test via CLI

1.

Login as the sysadmin user to the Delphix Engine CLI using ssh.
a. If the Delphix Engine has not been setup yet, the network setup prompt appears. Discard the command.

delphix network setup update *> discard

delphix>
2. Create a storage test.

delphix> storage test

delphix storage test> create
delphix storage test create *>
3. Use 'get' to see other optional arguments. Modify the test parameters as needed and commit to start the test.

delphix storage test create *> get

type: StorageTestParameters
devices: (unset)
duration: 120
initializeDevices: true
initializeEntireDevice: false
testRegion: 128GB
tests: ALL
delphix storage test create *> commit
STORAGE_TEST-1
Dispatched job JOB-1
STORAGE_TEST_EXECUTE job started for "SYSTEM".
Initializing storage test.
Starting storage device initialization.
ETA: 1:28:44.
Storage device initialization complete.
Starting storage benchmarking.
Starting random read workload with 4 KB block size and 8 jobs.
Starting random read workload with 4 KB block size and 16 jobs.
Starting random read workload with 4 KB block size and 32 jobs.
Starting random read workload with 4 KB block size and 64 jobs.
Starting random read workload with 8 KB block size and 8 jobs.
Starting random read workload with 8 KB block size and 16 jobs.
Starting random read workload with 8 KB block size and 32 jobs.
Starting random read workload with 8 KB block size and 64 jobs.
Starting sequential write workload with 1 KB block size and 4 jobs.
Starting sequential write workload with 4 KB block size and 4 jobs.
Starting sequential write workload with 8 KB block size and 4 jobs.
Starting sequential write workload with 16 KB block size and 4 jobs.

200

Delphix User Guide 2016 Delphix

Starting sequential write workload with 32 KB block size and 4 jobs.

Starting sequential write workload with 64 KB block size and 4 jobs.
Starting sequential write workload with 128 KB block size and 4 jobs.
Starting sequential write workload with 1024 KB block size and 4 jobs.
Starting sequential write workload with 1 KB block size and 16 jobs.
Starting sequential write workload with 4 KB block size and 16 jobs.
Starting sequential write workload with 8 KB block size and 16 jobs.
Starting sequential write workload with 16 KB block size and 16 jobs.
Starting sequential write workload with 32 KB block size and 16 jobs.
Starting sequential write workload with 64 KB block size and 16 jobs.
Starting sequential write workload with 128 KB block size and 16 jobs.
Starting sequential write workload with 1024 KB block size and 16 jobs.
Starting sequential read workload with 64 KB block size and 4 jobs.
Starting sequential read workload with 64 KB block size and 8 jobs.
Starting sequential read workload with 64 KB block size and 16 jobs.
Starting sequential read workload with 64 KB block size and 32 jobs.
Starting sequential read workload with 64 KB block size and 64 jobs.
Starting sequential read workload with 128 KB block size and 4 jobs.
Starting sequential read workload with 128 KB block size and 8 jobs.
Starting sequential read workload with 128 KB block size and 16 jobs.
Starting sequential read workload with 128 KB block size and 32 jobs.
Starting sequential read workload with 128 KB block size and 64 jobs.
Starting sequential read workload with 1024 KB block size and 4 jobs.
Starting sequential read workload with 1024 KB block size and 8 jobs.
Starting sequential read workload with 1024 KB block size and 16 jobs.
Starting sequential read workload with 1024 KB block size and 32 jobs.
Starting sequential read workload with 1024 KB block size and 64 jobs.
Storage benchmarking complete.
Generating results.

201

Delphix User Guide 2016 Delphix

Storage test completed successfully.

STORAGE_TEST_EXECUTE job for "SYSTEM" completed successfully.
delphix storage test>
4. The job will be submitted and visible in the Delphix Engine GUI
5. Retrieve the test results

delphix storage test> select STORAGE_TEST-1

delphix storage test 'STORAGE_TEST-1'> result
delphix storage test 'STORAGE_TEST-1' result *> commit
Test Results
-----------Test ID:
1
Test System UUID: 564dc710-7bb1-c064-12c2-2659032acf1b
Start Time:
03-Feb-2015 10:52:31 -0800
End Time:
03-Feb-2015 12:20:25 -0800
Test Grades:
Test Name
-------------------------------

Latency
-------------------------Average 95th %ile
Grade
------- ------------2.16
4.77
A1.62
3.73
A
62.60
182.00
D
1.30
2.61
C
10.19
26.00
D

Random 8K Reads w/ 16 jobs

Random 4K Reads w/ 16 jobs
Sequential 1M Reads w/ 4 jobs
Sequential 1K Writes w/ 4 jobs
Sequential 128K Writes w/ 4 jobs

Load Scaling
--------------Scaling
Grade
----------0.89
poor
0.54
fair
1.40
bad
0.07
good
1.35
bad

Grading Key:
Test Name
Grade: A+
-------------------Small Random Reads
2.0
Large Seq Reads
12.0
Small Seq Writes
0.5
Large Seq Writes
2.0

A
---4.0
14.0
1.0
4.0

A---6.0
16.0
1.5
6.0

B
---8.0
18.0
2.0
8.0

B---10.0
20.0
2.5
10.0

C
---12.0
22.0
3.0
12.0

C---14.0
24.0
3.5
14.0

D
----> 14.0
> 24.0
> 3.5
> 14.0

IO Summary:
Test Name
IOPS
--------------------------- ----------------------------------------

Throughput (MBps)
-----------------

Latency (msec)

Average

Min

Max

-------

-------

-------

StdDev
------Rand 4K
1.72
Rand 4K
5.12
Rand 4K
17.56
Rand 4K
30.09
Rand 8K
0.27
Rand 8K

Reads w/ 8 Jobs

15703

61.34

0.50

0.05

754.74

Reads w/ 16 Jobs

15631

61.06

1.00

0.05

1347.10

Reads w/ 32 Jobs

15972

62.39

1.95

0.05

1231.40

Reads w/ 64 Jobs

17341

67.74

3.62

0.05

1750.10

Reads w/ 8 Jobs

15151

118.37

0.52

0.05

45.18

Reads w/ 16 Jobs

16457

128.58

0.95

0.05

501.90

202

Delphix User Guide 2016 Delphix

3.57
Rand 8K Reads w/ 32 Jobs
16.93
Rand 8K Reads w/ 64 Jobs
30.03
Seq 1K Writes w/ 4 Jobs
0.26
Seq 4K Writes w/ 4 Jobs
0.27
Seq 8K Writes w/ 4 Jobs
0.28
Seq 16K Writes w/ 4 Jobs
0.26
Seq 32K Writes w/ 4 Jobs
0.38
Seq 64K Writes w/ 4 Jobs
2.26
Seq 128K Writes w/ 4 Jobs
4.75
Seq 1M Writes w/ 4 Jobs
42.24
Seq 1K Writes w/ 16 Jobs
6.86
Seq 4K Writes w/ 16 Jobs
7.76
Seq 8K Writes w/ 16 Jobs
7.91
Seq 16K Writes w/ 16 Jobs
8.05
Seq 32K Writes w/ 16 Jobs
8.10
Seq 64K Writes w/ 16 Jobs
4.40
Seq 128K Writes w/ 16 Jobs
4.32
Seq 1M Writes w/ 16 Jobs
32.05
Seq 64K Reads w/ 4 Jobs
0.15
Seq 64K Reads w/ 8 Jobs
0.41
Seq 64K Reads w/ 16 Jobs
7.41
Seq 64K Reads w/ 32 Jobs
20.02
Seq 64K Reads w/ 64 Jobs
34.37
Seq 128K Reads w/ 4 Jobs
0.25
Seq 128K Reads w/ 8 Jobs
0.42
Seq 128K Reads w/ 16 Jobs
6.46
Seq 128K Reads w/ 32 Jobs
19.87
Seq 128K Reads w/ 64 Jobs
36.79
Seq 1M Reads w/ 4 Jobs
0.75

16908

132.10

1.84

0.05

1336.10

16865

131.76

3.71

0.05

1505.50

22053

21.54

0.18

0.04

168.14

24937

97.41

0.16

0.04

152.17

22946

179.27

0.17

0.04

120.19

18003

281.31

0.22

0.05

81.24

12993

406.05

0.30

0.05

40.33

6429

401.83

0.62

0.06

116.19

3614

451.86

1.10

0.08

200.12

388

388.83

10.28

0.27

832.57

25965

25.36

0.60

0.04

814.84

25610

100.04

0.61

0.04

1022.50

25183

196.75

0.62

0.04

910.55

23433

366.14

0.66

0.04

948.57

19327

604.00

0.81

0.05

1180.50

9313

582.08

1.71

0.06

711.96

3369

421.14

4.75

0.08

69.12

481

481.06

33.22

0.27

269.88

16912

1057.20

0.23

0.05

40.36

18862

1178.10

0.42

0.05

78.57

20352

1272.50

0.77

0.06

900.81

20750

1296.10

1.50

0.06

1231.60

21146

1321.70

2.95

0.06

2440.30

11649

1456.30

0.34

0.06

53.66

15995

1999.50

0.49

0.06

32.21

17413

2176.80

0.90

0.07

1057.60

17874

2234.30

1.76

0.07

1355.40

17523

2190.50

3.58

0.07

1926.20

1404

1404.20

2.84

0.31

64.38

203

Delphix User Guide 2016 Delphix

Seq 1M
0.46
Seq 1M
3.20
Seq 1M
34.64
Seq 1M
54.39

Reads w/ 8 Jobs

2360

2360.70

3.38

0.32

17.60

Reads w/ 16 Jobs

3876

3876.50

4.10

0.33

429.44

Reads w/ 32 Jobs

4732

4732.60

6.69

0.29

1305.70

Reads w/ 64 Jobs

4730

4730.10

13.33

0.32

1847.90

IO Histogram:
Test Name
us50
ms20
ms50 ms100 ms250 ms500
--------------------------- --------- ----- ----- ----- ----Rand 4K Reads w/ 8 Jobs
0
1
0
0
0
0
Rand 4K Reads w/ 16 Jobs
0
1
0
0
0
0
Rand 4K Reads w/ 32 Jobs
0
2
0
0
0
0
Rand 4K Reads w/ 64 Jobs
0
3
1
0
0
0
Rand 8K Reads w/ 8 Jobs
0
1
0
0
0
0
Rand 8K Reads w/ 16 Jobs
0
2
1
0
0
0
Rand 8K Reads w/ 32 Jobs
0
3
2
0
0
0
Rand 8K Reads w/ 64 Jobs
0
8
4
1
0
0
Seq 1K Writes w/ 4 Jobs
0
1
0
0
0
0
Seq 4K Writes w/ 4 Jobs
0
1
0
0
0
0
Seq 8K Writes w/ 4 Jobs
0
1
0
0
0
0
Seq 16K Writes w/ 4 Jobs
0
1
0
0
0
0
Seq 32K Writes w/ 4 Jobs
0
2
1
0
0
0
Seq 64K Writes w/ 4 Jobs
0
7
3
0
0
0
Seq 128K Writes w/ 4 Jobs
0
16
5
2
0
0
Seq 1M Writes w/ 4 Jobs
0
0
24
57
14
4
Seq 1K Writes w/ 16 Jobs
0
1
0
0
0
0
Seq 4K Writes w/ 16 Jobs
0
1
0
0
0
0
Seq 8K Writes w/ 16 Jobs
0
2
1
0
0
0
Seq 16K Writes w/ 16 Jobs
0
4
2
0
0
0
Seq 32K Writes w/ 16 Jobs
0
16
8
2
0
0

us100
s1
--------0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

204

us250
s2
--------0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

us500
s5
--------2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
4
0
2
0
1
0
0
0
0
0
0
0
0
0
0
0
1
0
1
0
0
0
0
0
0
0

ms1

ms2

ms4

ms10

-----

-----

-----

-----

46

41

39

47

10

64

22

75

16

41

49

66

20

72

18

85

53

36

44

44

41

47

27

57

10

55

30

56

33

76

55

34

46

42

43

38

12

67

23

74

Delphix User Guide 2016 Delphix

Seq
81
Seq
2
Seq
0
Seq
2
Seq
8
Seq
53
Seq
27
Seq
1
Seq
9
Seq
29
Seq
45
Seq
1
Seq
1
Seq
0
Seq
0
Seq
0
Seq
0
Seq

64K Writes w/ 16 Jobs

12
3
1
128K Writes w/ 16 Jobs
85
7
4
1M Writes w/ 16 Jobs
1
4
45
64K Reads w/ 4 Jobs
1
0
0
64K Reads w/ 8 Jobs
3
1
0
64K Reads w/ 16 Jobs
27
5
1
64K Reads w/ 32 Jobs
59
8
4
64K Reads w/ 64 Jobs
29
42
25
128K Reads w/ 4 Jobs
5
1
0
128K Reads w/ 8 Jobs
5
2
0
128K Reads w/ 16 Jobs
45
6
2
128K Reads w/ 32 Jobs
65
24
8
128K Reads w/ 64 Jobs
8
54
29
1M Reads w/ 4 Jobs
66
23
8
1M Reads w/ 8 Jobs
1
33
52
1M Reads w/ 16 Jobs
1
5
70
1M Reads w/ 32 Jobs
1
4
19
1M Reads w/ 64 Jobs

0
0

0
0

0
0

0
9

0
3

0
0

0
0

0
0

0
0

0
0

0
0

0
0

0
0

0
0
0

0
0

0
0

0
0

0
0

0
0
1
0

0
0

3
0

8
0

11
0

205

29

59

15

74

14

10

75

64

0
0

6
0

1
0

58

0
0

15

0
0

11

0
0

0
0

0
0

0
0

0
0

0
0

38

0
0

1
0

Delphix User Guide 2016 Delphix

10

40

32

delphix storage test 'STORAGE_TEST-1'>

206

11

Delphix User Guide 2016 Delphix

Host Performance Configuration Options

These topics describe configuration options to maximize host performance in a Delphix Engine deployment.
Target Host Configuration Options for Improved Performance

207

Delphix User Guide 2016 Delphix

Target Host Configuration Options for Improved Performance

This topic describes configuration options to maximize the performance of a target host in a Delphix Engine deployment.

OS-Specific Tuning Recommendations for Oracle Databases

Solaris

When exclusively using Oracle's Direct NFS Feature (dNFS), it is unnecessary to tune the native NFS client. However, tuning network
parameters is still relevant and may improve performance.

Tuning the Kernel NFS Client

On systems using Oracle Solaris Zones, the kernel NFS client can only be tuned from the global zone.

On Solaris, by default the maximum I/O size used for NFS read or write requests is 32K. When Oracle does I/O larger than 32K, the I/O is broken
down into smaller requests that are serialized. This may result in poor I/O performance. To increase the maximum I/O size:
1. As superuser, add to the /etc/system file:

* For Delphix: change the maximum NFS block size to 1M

set nfs:nfs3_bsize=0x100000
2. Run this command:

# echo "nfs3_bsize/W 100000" | mdb -kw

It is critical that the above command be executed exactly as shown, with quotations and space. Errors in the command may
cause a system panic and reboot.

Tuning TCP Buffer Sizes

On systems using Oracle Solaris Zones, TCP parameters, including buffer sizes, can only be tuned from the global zone or in
exclusive-IP non-global zones. Shared-IP non-global zones always inherit TCP parameters from the global zone.
Solaris 10
It is necessary to install a new Service Management Facility (SMF) service that will tune TCP parameters after every boot. These are samples of
the files needed to create the service:
File

Installation location

dlpx-tcptune

/lib/svc/method/dlpx-tcptune

dlpx-tune.xml

/var/svc/manifest/site/dlpx-tune.xml

1. As superuser, download the files and install in the path listed in the Installation location in the table.
2. Run the commands:

#
#
#
#

chmod 755 /lib/svc/method/dlpx-tcptune

/usr/sbin/svccfg validate /var/svc/manifest/site/dlpx-tune.xml
/usr/sbin/svccfg import /var/svc/manifest/site/dlpx-tune.xml
/usr/sbin/svcadm enable site/tcptune

Verify that the SMF service ran after being enabled by running the command:

# cat `svcprop -p restarter/logfile tcptune`

208

Delphix User Guide 2016 Delphix

You should see output similar to this:

[ May 14 20:02:02 Executing start method ("/lib/svc/method/dlpx-tcptune start"). ]

Tuning TCP Network Parameters
tcp_max_buf adjusted from 1048576 to 16777216
tcp_cwnd_max adjusted from 1048576 to 4194304
tcp_xmit_hiwat adjusted from 49152 to 4194304
tcp_recv_hiwat adjusted from 128000 to 16777216
[ May 14 20:02:02 Method "start" exited with status 0. ]
Solaris 11
As superuser
Run the following commands:

#
#
#
#

ipadm
ipadm
ipadm
ipadm

set-prop
set-prop
set-prop
set-prop

-p
-p
-p
-p

max_buf=16777216 tcp
_cwnd_max=4194304 tcp
send_buf=4194304 tcp
recv_buf=16777216 tcp

Linux/Redhat/CentOs
Tuning the Kernel NFS Client

In Linux, the number of simultaneous NFS requests is limited by the Remote Procedure Call (RPC) subsystem. The maximum number of
simultaneous requests defaults to 16. Maximize the number of simultaneous requests by changing the kernel tunable sunrpc.tcp_slot_tabl
e_entries value to 128.
RHEL4 through RHEL5.6

1. As superuser, run the following command to change the instantaneous value of simultaneous RPC commands:

# sysctl -w sunrpc.tcp_slot_table_entries=128
2. Edit the file /etc/modprobe.d/modprobe.conf.dist and change the line:

install sunrpc /sbin/modprobe --first-time --ignore-install sunrpc && { /bin/mount

-t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs > /dev/null 2>&1 || :;
to

install sunrpc /sbin/modprobe --first-time --ignore-install sunrpc && { /bin/mount

-t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs > /dev/null 2>&1 ; /sbin/sysctl -w
sunrpc.tcp_slot_table_entries=128; }
Improper changes to the modprobe.conf.dist file may disrupt use of NFS on the system. Check with your system administrator
or operating system vendor for assistance. Save a copy of the modprobe.conf.dist in a directory other than /etc/modprobe.d
before starting.

RHEL 5.7 through RHEL 6.2

1. As superuser, run the following command to change the instantaneous value of simultaneous RPC commands:

# sysctl -w sunrpc.tcp_slot_table_entries=128
2. If it doesn't already exist, create the file /etc/modprobe.d/rpcinfo with the following contents:

options sunrpc tcp_slot_table_entries=128

RHEL 6.3 onwards
Beginning with RHEL 6.3, the number of RPC slots is dynamically managed by the system and does not need to be tuned. Although the sunrpc.

209

Delphix User Guide 2016 Delphix

tcp_slot_table_entries tuneable still exists, it has a default value of 2, instead of 16 as in prior releases. The maximum number of
simultaneous requests is determined by the new tuneable, sunrpc.tcp_max_slot_table_entries, which has a default value of 65535.

Tuning TCP Buffer Sizes

1. As superuser, add or replace the following entries in /etc/sysctl.conf.

Note: the *rmem, *wmem parameter values are minimum recommendations, so no change is needed if already set to higher values.

net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_sack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_rmem = 4096 16777216 16777216
net.ipv4.tcp_wmem = 4096 4194304 16777216
2. Run the command:

/sbin/sysctl -p

IBM AIX
Tuning the Kernel NFS Client

On AIX, by default the maximum I/O size used for NFS read or write requests is 64K. When Oracle does I/O larger than 64K, the I/O is broken
down into smaller requests that are serialized. This may result in poor I/O performance. IBM can provide an Authorized Program Analysis Report
(APAR) that allows the I/O size to be configured to a larger value.
1. Determine the appropriate APAR for the version of AIX you are using:
AIX Version

APAR Name

6.1

IV24594

7.1

IV24688

2. Check if the required APAR is already installed by running this command:

# /usr/sbin/instfix -ik IV24594

If the APAR is installed, you will see a message similar to this:

All filesets for IV24594 were found.

If the APAR is not yet installed, you will see a message similar to this:

There was no data for IV24594 in the fix database.

3. Download and install the APAR, as necessary. To find the APARs, use the main search function at http://www.ibm.com/us/en/,
specifying the name of the APAR you are looking for from step 1.
A system reboot is necessary after installing the APAR

4. Configure the maximum read and write sizes using the commands below:

# nfso -p -o nfs_max_read_size=524288
# nfso -p -o nfs_max_write_size=524288
5. Confirm the correct settings using the command:

# nfso -L nfs_max_read_size -L nfs_max_write_size

You should see an output similar to this:

210

Delphix User Guide 2016 Delphix

NAME CUR DEF BOOT MIN MAX UNIT TYPE

DEPENDENCIES
-------------------------------------------------------------------------------nfs_max_read_size 512K 64K 512K 512 512K Bytes D
-------------------------------------------------------------------------------nfs_max_write_size 512K 64K 512K 512 512K Bytes D
--------------------------------------------------------------------------------

Tuning Delayed TCP Acknowledgements

By default AIX implements a 200ms delay for TCP acknowledgements. However, it has been found that disabling this behaviour can provide
significant performance improvements.
To disable delayed ACKs on AIX the following command can be used:

# /usr/sbin/no -o tcp_nodelayack=1
To make the change permanent use:

# /usr/sbin/no -o -p tcp_nodelayack=1
HP-UX
Tuning the Kernel NFS Client

On HP-UX, by default the maximum I/O size used for NFS read or write requests is 32K. When Oracle does I/O larger than 32K, the I/O is broken
down into smaller requests that are serialized. This may result in poor I/O performance.
1. As superuser, run the following command:

# /usr/sbin/kctune nfs3_bsize=1048576
2. Confirm the changes have occurred and are persistent by running the following command and checking the output:

# grep nfs3 /stand/system

tunable nfs3_bsize
1048576

Tuning TCP Buffer Sizes

1. As superuser, edit the /etc/rc.config.d/nddconf file, adding or replacing the following entries:

TRANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_recv_hiwater_def
NDD_VALUE[0]=16777216
#
TRANSPORT_NAME[1]=tcp
NDD_NAME[1]=tcp_xmit_hiwater_def
NDD_VALUE[1]=4194304
In this example, the array indices are shown as 0 and 1.In the actual configuration file, each index used must be strictly
increasing, with no missing entries. See the comments at the beginning of /etc/rc.config.d/nddconf for more
information.

2. Run the command:

/usr/bin/ndd -c
3. Confirm the settings:

211

Delphix User Guide 2016 Delphix

# ndd -get /dev/tcp tcp_recv_hiwater_def

16777216
# ndd -get /dev/tcp tcp_xmit_hiwater_def
4194304

OS-Specific Tuning Recommendations for SQL Server Databases

These are our recommendations for Windows iSCSI initiator configuration. Please note that the parameters below will affect all applications
running on the Windows target host, so you should make sure that the following recommendations do not contradict best practices for other
applications running on the host.
For targets running Windows Server, the iSCSI initiator driver timers can be found at: HKLM\SYSTEM\CurrentControlSet\Control\Class\
{4D36E97B-E325-11CE-BFC1-08002BE10318}\<Instance Number>\<Parameters> . Please see How to Modify the Windows
Registry on the Microsoft Support site for details about configuring registry settings.
Registry Value

Type

MaxTransferLength

Default

Recommended

Comments

REG_DWORD 262144

131072

This controls the maximum data size of an I/O request. A value

of 128K is optimal for the Delphix Engine as it reduces
segmentation of the packets as they go through the stack.

MaxBurstLength

REG_DWORD 262144

131072

This is the negotiated maximum burst length. 128K is the

optimal size for the Delphix Engine.

MaxPendingRequests

REG_DWORD 255

512

This setting controls the maximum number of outstanding

requests allowed by the initiator. At most this many requests
will be sent to the target before receiving response for any of
the requests.

131072

This is the negotiated

MaxRecvDataSegmentLength.

MaxRecvDataSegmentLength REG_DWORD 65536

Related Links
SQL Server Target Host iSCSI Configuration Parameter Recommendations
Set Up a SQL Server Target Environment

212

Delphix User Guide 2016 Delphix

Performance Analytics
These topics describe how to use the Performance Analytics tool to optimize the performance of a Delphix Engine deployment.
Performance Analytics Tool Overview
Working with Performance Analytics Graphs in the Graphical User Interface
Performance Analytics Statistics Reference
Performance Analytics Tool API Reference
Performance Analytics Case Study: Using a Single Statistic
Performance Analytics Case Study: Using Multiple Statistics

213

Delphix User Guide 2016 Delphix

Performance Analytics Tool Overview

This topic describes the Performance Analytics tool and illustrates some basic uses of it.

Introduction
The performance analytics tool allows introspection into how the Delphix Engine is performing. The introspection techniques it provides are tuned
to allow an iterative investigation process, helping to narrow down the cause associated with the performance being measured. Performance
analytics information can be accessed through the Delphix Admin application, as described in Working with Performance Analytics Graphs in
the Graphical User Interface, as well as the CLI and the web services API, as described in other topics in this section. The default statistics that
are being collected on the Delphix Engine include CPU utilization, network utilization, and disk, NFS, and iSCSI IO operations (see Performance
Analytics Statistics Reference for details).
The performance tool operates with two central concepts: statistics and statistic slices.

Statistics
Each statistic describes some data that can be collected from the Delphix Engine. The first piece of information a statistic provides is its type,
which you will use as a handle when creating a statistic slice. It also gives the minimum collection interval, which puts an upper bound on the
frequency of data collection. The actual data a statistic can collect is described through a set of axes, each of which describe one "dimension" of
that statistic. For example, the statistic associated with Network File System (NFS) operations has a latency axis, as well as an operation type
axis (among many others), which allows users to see NFS latencies split by whether they were reads or writes.
Each axis has some important information embedded in it.
The name of the axis provides a short description of what the axis collects and is used when creating a statistic slice
A value type, which tells you what kind of data will be collected for this axis. The different value types are integer, boolean, string, and
histogram. The first three are straightforward, but statistic axes with a histogram type can collect a distribution of all the values
encountered during each collection interval. This means that instead of seeing an average NFS operation latency every collection
interval, you can see a full distribution of operation latencies during that interval. This allows you to see outliers as well as the average,
and observe the effects of caching on the performance of your system more easily.
A constraint type, which is only relevant while creating a statistic slice, and will be described in more detail below
One last bit of information that an axis provides makes the most sense after seeing how datapoints are queried. In the most basic situation, you
would only collect one axis of a statistic, such as the latency axis from the NFS operations statistic. When you ask for data, you would get back a
datapoint for every collection interval in the time range you requested. These datapoints would be grouped into a single stream.

However, if you had collected the operation type axis as well as the latency axis, you would get two streams of datapoints: one for read
operations, and one for write operations.

214

Delphix User Guide 2016 Delphix

Because the operation axis applies to many datapoints, the datapoints returned are split into two streams, and the operation axis is stored with
the top-level stream instead of with each datapoint in the streams. However, the latency axis will be different for each datapoint in a stream, so it
is not an attribute of the stream, but instead an attribute of the datapoint.

Statistic Slices
Statistics describe what data can be collected and are auto-populated by the system, but statistic slices are responsible for actually collecting the
data, and you must create them manually when you want to collect some performance data. Each slice is an instantiation of exactly one statistic,
and can only gather data which is described by that statistic. "Slices" are so named because each one provides a subset of the information
available from the parent statistic it is associated with. A statistic can be thought of as describing the axes of a multidimensional space, whereas
you typically will only want to collect a simpler slice of that space due to the large number of axes available.
When you specify a slice, there are several fields which you must supply:
The statistic type this slice is associated with. This must be the same type as the statistic of which this is an instantiation.
The collection interval, which must be greater than the minimum collection interval the parent statistic gives
The axes of the parent statistic this slice will collect
Finally, a slice can place constraints on axes of its parent statistic, allowing you to limit the data you get back. For instance, if you're trying to
narrow down the cause of some high NFS latency outliers, it may be useful to filter out any NFS latencies which are shorter than one second. To
do this, you would place a constraint on the latency axis of an NFS operation slice that states that the values must be higher than one second.
You can constrain any axis in the same fashion, and each axis' description in the parent statistic gives a constraint type which can be applied to it.
This allows you to place different types of constraints on the latency axis (which is a number measured in nanoseconds) than the operation type
axis (which is an enum that can take the values "read" or "write").

Persisting Analytics Data

Data collected by slices is persisted temporarily on the Delphix Engine. Performance data is guaranteed to be available at the finest resolution for
6 hours, then is compressed to per-minute data and held for 7 days, and finally compressed to per-hour data and held for 30 days. If data of a
certain resolution will be needed longer than these limits, you should instruct the slice to remember the data permanently until you are done using
it. The commands to manage this are listed in the Performance Analytics Tool API Reference.

Related Links
The Performance Analytics Tool API Reference provides a detailed list of all statistics which can be collected, what their axes
represent, and how those axes can be constrained, and outlines all management operations which are available.
Working with Performance Analytics Graphs in the Graphical User Interface

215

Delphix User Guide 2016 Delphix

Working with Performance Analytics Graphs in the Graphical User Interface

This topic describes the performance analytics graphs that are available in the Delphix Engine graphical user interface, and the controls for
changing the views of those graphs.

Accessing the Performance Analytics Graphs

1. Log into the Delphix Admin application using delphix_admin credentials.
2. In the Resources menu, select Performance Analytics.
3. Use the controls described below to view statistics and their related graphs.

General Graph Display and Controls

Control
Name

Control Description

Usage

Graph
Selector

Specifies which graphs are displayed.

View a graph by selecting the checkbox next to its name. To hide a graph,
clear the checkbox.

Zoom
Level

Controls the time range of data displayed in the

graph. Available values are 1 minute, 1 hour, and 1
day. By default 1 minute is selected.

Select Minute, Hour, or Day to change the Zoom Level.

Shown
Data
Timeline

Displays timestamps of data points in the graph.

Available
Data
Timeline

Displays navigable time ranges for historical data.

216

Delphix User Guide 2016 Delphix

Timeline
Selector

Specifies the start and end time for the currently

displayed data. The range displayed is controlled by
the Zoom Level.

Drag the Timeline Selector to view statistics for a specific time in the past,
or click the scroll bar arrows to view the desired time period. You can also
use the slider controls within the Timeline Selector to change the length of
time for which data is displayed.
When the Timeline Selector is aligned to the right of the timeline, it
represents live data that is updated every second. If the Timeline Selector
is moved from right alignment with the timeline, the data displayed is
historical and no live updates are displayed. To resume live data updates,
move the Timeline Selector back to the right-aligned position representing
the current time. The data will be refreshed to the latest data, and live
updates will resume every second.

Graph
Legend

If more than one set of information is presented on

the graph, the Graph Legend displays a description
and color for each set and allows a user to toggle
that set off and on.

To hide a set of information, click on the set name within the Graph
Legend. Data representing that set is removed from the graph, and the
set's name is greyed out. To show a set that has been hidden, click on the
set name.

For example, in the network graph there can be

multiple network interfaces, and for each network
interface the graph displays four statistics (bytes
sent, bytes received, packets sent, packets
received). When a user toggles off a specific
network interface, all four statistics corresponding to
that interface are hidden from the screen.
The color for lines representing bytes sent
and packets sent is the same. Similarly,
the color for lines representing bytes
received and packetsreceived is the same.
This makes it easier to correlate the
number of bytes and number of packets
sent/received for a given network
interface.

Latency, Timeline Page, and Tooltip Graph Display and Controls

Control
Name

Control Description

Usage

217

Delphix User Guide 2016 Delphix

Timeline
Page
Left/Right
Button

Scrolls Available Data Timeline by a specified time range

depending on the current Zoom Level.

When the Zoom Level is set to Minute, click Timeline Page Left. The
Available Data Timeline is changed to show the time period for the
previous hour prior.

Graph
Value
Tooltip

Shows a value, along with the time stamp, for a specific

data point.

Mouse over a data point on the graph to view the tooltip.

Latency
Range
Selector (
shown on
latency
heatmaps
only)

Controls the lower and upper limits for displayed latency

buckets.

Drag the lower and upper controls to drill down into a specific range of
latency buckets. Latency buckets that fall outside of the selected range
are summarized, the lower row representing latency buckets that are
below the lower limit, and the upper row representing latency buckets
that are below the upper limit of the latency range selector. Use
Latency Range Selector to view more detailed distribution of latencies
for a specific range.

Latency
Outlier
Selector (
shown on
latency
heatmaps
only)

Hides infrequent latencies (outliers) based on a

percentage threshold. Its range is 0%-10%, with the
default of 0%. The percentage establishes a threshold
below which buckets are considered "outliers" and are
hidden from the graph. Each bucket is assigned a
percentage based on the ratio of its count vs the
maximum count of any bucket in the graph.

Drag the control to the desired percentage threshold.

Related Links
Performance Analytics Statistics Reference

218

Delphix User Guide 2016 Delphix

Performance Analytics Statistics Reference

This topic describes the various performance statistics that are available for the Delphix Engine and how they can be used to analyze and
improve performance.
The Delphix Engine is shipped with a default set of statistics that are collected on Delphix Engine virtual appliance, as listed below. The statistics
are stored for up to 30 days for historical analysis.
Statistic

Description

CPU
Utilization

Total CPU utilization for all CPUs. This statistic includes both kernel and user time.

Network
Throughput

Measures throughput in bytes and packets, broken down by sent vs. received data and by network interface. Each network
interface shows four graphed lines: bytes sent, bytes received, packets sent, and packets received. To help easily correlate
bytes and packets, the same color is used for both bytes and packet values.

Disk IO

Measures a number of IO operations, and the latencies and throughput of the underlying storage layer. The statistic is
represented by the graphs - a column chart for IO operations, a heat map for latency distribution, and a line chart for throughput.
IO operations are grouped by reads and writes. A shaded rectangle on a latency heat map represents an IO operation (read or
write) which falls within a particular time range (bucket). The shading of rectangles depends on the number of IO operations that
fall within a particular bucket - the higher the count the darker the shading.

NFS

Measures a number of IO operations and the latencies and throughput of the NFS server layer in the Delphix Engine. Its
graphical representation is similar to the Disk IO graph. It is useful to diagnose performance of dSources and VDBs that use
NFS mounts (Oracle, PostgreSQL).

iSCSI

Measures the number of IO operations, and the latencies and throughput, of the iSCSI server layer in the Delphix Engine. Its
graphical representation is similar to the Disk IO graph. It is useful to diagnose performance of Microsoft SQL Server dSources
and VDBs.

Related Links
Working with Performance Analytics Graphs in the Graphical User Interface
Performance Analytics Tool Overview

219

Delphix User Guide 2016 Delphix

Performance Analytics Tool API Reference

This topic describes basic commands and command syntax for using the Performance Analytics tool.

Statistic Types
More documentation can be found about each statistic type through the CLI and webservices API, but the following table provides more
information about how similar I/O stack statistic types relate to each other.
Statistic Type

Description

NFS_OPS

Provides information about Network File System operations. This is the entrypoint to the Delphix Engine for all
Oracle database file accesses.

iSCSI_OPS

Provides information about iSCSI operations. This is the entrypoint to the Delphix Engine for all SQL Server file
accesses.

VFS_OPS

This layer sits immediately below NFS_OPS and iSCSI_OPS, and should give almost exactly the same latencies,
assuming no unexpected behavior is occurring.

DxFS_OPS

This layer sits immediately below VFS_OPS, and the two of them should give almost exactly the same latencies.

DxFS_IO_QUEUE_OPS

This layer sits below DxFS_OPS, but the latencies will differ from that layer because this layer batches together
operations to increase throughput.

DISK_OPS

This layer sits below DxFS_IO_QUEUE_OPS at the bottom of the I/O stack, and measures interactions the Delphix
Engine has with disks.

CPU_UTIL

This is unrelated to the layers of the I/O stack - it measures CPU utilization on the Delphix Engine.

TCP_STATS

Statistics for all established TCP connections on the Delphix Engine.

Statistic Axis Information

Values are returned when a slice's data is queried. Each axis has a value type, which specifies how the data will be returned.
Value Type

Description

INTEGER

The value is returned as an integer. For information about what units the integer is measured in, read the documentation for the
related datapoint or datapoint stream type.

BOOLEAN

The value is returned as a boolean.

STRING

The value is returned as a string. This is used for enum values as well, although the set of strings which can be returned is
limited.

HISTOGRAM

The value is returned as a log-scale histogram. The histogram has size buckets whose minimum and maximum value get
doubled. Histograms are returned as JSON maps, where the keys are the minimum value in a bucket and the values are the
height of each bucket.
Here is an example histogram. Notice that buckets with a height of zero are not included in the JSON object, and that keys and
values are represented as strings.

{
"32768": "10",
"65536": "102",
"262144": "15",
"524288": "2"
}

Axis constraints are used to limit the data which a slice can collect. Each axis specifies a constraint type which can be used to limit that axis'
values.
Constraint Type

Description

220

Delphix User Guide 2016 Delphix

BooleanConstraint

A superclass which constraints on boolean values must extend. Currently, the only subclass is BooleanEqualConst
raint, which requires that a boolean axis equal either true or false (depending on user input).

EnumConstraint

A superclass which constraints on enum values must extend. Currently, the only subclass is EnumEqualConstrain
t, which requires that an enum axis be equal to a user-specified value.

IntegerConstraint

A superclass which constraints on integer values must extend. Subclasses include IntegerLessThanConstraint,
IntegerGreaterThanConstraint, and IntegerEqualConstraint, which map to the obvious comparators for
integers.

NullConstraint

This class signifies that an axis cannot be constrained. This makes the most sense for axes which provide an average
value - placing a constraint on an average doesn't make sense because you are not able to include or discard a
particular operation based on what its effects would be on the average of all operations.

PathConstraint

A superclass which constraints on file path values must extend. Currently, the only subclass is PathDescendantCon
straint, which requires that a path value must be a descendant of the specified path (it must be contained within it).
This only applies to paths on the Delphix Engine itself, and all paths used must be canonical Unix paths starting from
the root of the filesystem.

StringConstraint

A superclass which constraints on string values must extend. Currently, the only subclass is StringEqualsConstr
aint, which requires that a string value must equal a user-specified string.

Statistic Slice Commands

Command

Description and Usage Examples

getData

This is used to fetch data from a statistic slice which has been collecting data for a while. It returns a datapoint
set, which is composed of datapoint streams, which contain datapoints. For a full description, see the Performan
ce Analytics Tool Overview.

rememberRange

This is used to ensure that data collected during an ongoing investigation doesn't get deleted unexpectedly. If this
is not used, data is only guaranteed to be persisted for 24 hours. If it is used, data will be remembered until a
corresponding call to stopRememberingRange is made.

stopRememberingRange

This is used to allow previously-remembered data to be forgotten. The data will be forgotten on the same
schedule as brand new data, so you will have at least 24 hours before data which you have stopped remembering
is deleted. This undoes the rememberRange operation.

pause

This command pauses the collection of a statistic slice, causing no data to be collected until resume is called.

resume

This command resumes the collection of a statistic slice, undoing a pause operation.

Related Links
The Performance Analytics Tool Overview gives an overview of how all the pieces on this page interact.
The case studies (Performance Analytics Case Study: Using a Single Statistic, Performance Analytics Case Study: Using
Multiple Statistics) give command-by-command examples with extensive explanation.

221

Delphix User Guide 2016 Delphix

Performance Analytics Case Study: Using a Single Statistic

This topic describes how to perform a sample performance investigation with one statistic from the Performance Analytics tool.

Introduction
The Delphix Engine uses Network File System (NFS) as the transport for Oracle installations. An increase in the NFS latency could be causing
sluggishness in your applications running on top of Virtual Databases. This case study illustrates how this pathology can be root caused using the
analytics infrastructure. This performance investigation uses one statistic to debug the issue, and utilizes the many axes of that statistic to filter
down the probably cause of the issue. This technique uses an approach of iteratively drilling down by inspecting new axes of a single statistic,
and filtering the data to only include information about the operations that appear slow. This technique is valuable for determining which use
patterns of a resource might be causing the system to be sluggish. If you isolate a performance issue using this approach, but aren't sure what is
causing it or how to fix it, Delphix Support can provide assistance for your investigation.
The following example inspects the statistic which provides information about NFS I/O operations on the Delphix Engine. This statistic can be
collected a maximum of once every second, and the axes it can collect, among others, are:
latency, a histogram of wait times between NFS requests and NFS responses
size, a histogram of the NFS I/O sizes requested
op, whether the NFS requests were reads or writes
client, the network address of the NFS client which was making requests
Roughly the same performance information can be obtained from the iSCSI interface as well.

Investigation
Because the NFS layer sits above the disk layer, all NFS operations that use the disk synchronously (synchronous writes and uncached reads)
will have latencies which are slightly higher than those of their corresponding disk operations. Usually, because disks have very high seek times
compared to the time the NFS server spends on CPU, disk operations are responsible for almost all of the latency of these NFS operations. In the
graphical representation, you can see this by looking at how the slower cluster of NFS latencies (around 2ms-8ms) have similar latencies to the
median of the disk I/O (around 2ms-4ms). Another discrepancy between the two plots is that the number of disk operations is much lower than the
corresponding number of NFS operations. This is because the Delphix filesystem batches together write operations to improve performance.
If database performance is not satisfactory and almost all of the NFS operation time is spent waiting for the disks, it suggests that the disk is the
slowest piece of the I/O stack. In this case, disk resources (the number of IOPS to the disks, the free space on the disks, and the disk throughput)
should be investigated more thoroughly to determine if adding more capacity or a faster disk would improve performance. However, care must be
taken when arriving at these conclusions, as a shortage of memory or a recently-rebooted machine can also cause the disk to be used more
heavily due to fewer cache hits.
Sometimes, disk operations will not make up all of the latency, which suggests that something between the NFS server and the disk (namely,
something in the Delphix Engine) is taking a long time to complete its work. If this is the case, it is valuable to check whether the Delphix Engine is
resource-constrained, and the most common areas of constraint internal to the Delphix Engine are CPU and memory. If either of those is too
limited, you should investigate whether expanding the resource would improve performance. If no resources appear to be constrained or more
investigation is necessary to convince you that adding resources would help the issue, Delphix Support is available to help debug these issues.
While using this technique, you should take care to recognize the limitations that caching places on how performance data can be interpreted. In
this example, the Delphix Engine uses a caching layer for the data it stores, so asynchronous NFS writes will not go to disk quickly because they
are being queued into larger batches, and cached NFS reads won't use the disk at all. This causes these types of NFS operations to return much
more quickly than any disk operations are able to, resulting in a very large number of low-latency NFS operations in the graph above. For this
reason, caching typically creates a bimodal distribution in the NFS latency histograms, where the first cluster of latencies is associated with
operations that only hit the cache, and the second cluster of latencies is associated with fully or partially uncached operations. In this case,
cached NFS operations should not be compared to the disk latencies because they are unrelated. It is possible to use techniques described in the
first example to filter out some of the unrelated operations to allow a more accurate mapping between disk and NFS latencies.

Related Links
The Performance Analytics Tool API Reference gives a full list of the commands, axes, and data types used by the analytics tool.

222

Delphix User Guide 2016 Delphix

Performance Analytics Case Study: Using Multiple Statistics

This topic describes how to perform a sample performance investigation with multiple statistics from the Performance Analytics tool.
Introduction
Investigation
Setup
Analysis
Related Links

Introduction
This case study illustrates an investigation involving more than one metric. In typical performance investigations you will need to peel out multiple
layers of the stack in order to observe the component causing the actual performance pathology. This case study specifically examines sluggish
application performance caused due to slow IO responses from the disk sub-system. This example will demonstrate a technique of looking at the
performance of each layer in the I/O stack to find which layer is responsible for the most latency, then looking for constrained resources that the
layer might need to access. This technique is valuable for finding the most-constrained resource in the system, potentially giving actionable
information about resources that can be expanded to increase performance.
For the following example, we will inspect latency at two layers: the Network File System (NFS) layer on the Delphix Engine, and the disk layer
below it. Both of these layers provide the latency axis, which gives a histogram of wait times for the clients of each layer.

Investigation
The analytics infrastructure enables users to observe the latency of multiple layers of the software stack. This investigation will examine the
latency of both layers, and then draw conclusions about the differences between the two.

Setup
To measure this data, create two slices. When attempting to correlate data between two different statistics, it can be easier to determine
causation when collecting data at a relatively high frequency. The fastest that each of these statistics will collect data is once per second, so that
is value used.

1. A slice collecting the latency axis for the statistic type NFS_OPS.

/analytics
create
set name=slice1
set statisticType=NFS_OPS
set collectionInterval=1
set collectionAxes=latency
commit
2. A slice collecting the latency axis for the statistic type DISK_OPS.

/analytics
create
set name=slice2
set statisticType=DISK_OPS
set collectionInterval=1
set collectionAxes=latency
commit
After a short period of time, read the data from the first statistic slice.

223

Delphix User Guide 2016 Delphix

select slice2
getData
setopt format=json
commit
setopt format=text
The same process works for the second slice. The setopt steps are optional but allow you to see the output better via the CLI. The output for the
first slice might look like this:

224

Delphix User Guide 2016 Delphix

{
"type": "DatapointSet",
"collectionEvents": [],
"datapointStreams": [{
"type": "NfsOpsDatapointStream",
"datapoints": [{
"type": "IoOpsDatapoint",
"latency": {
"512": "100",
"1024": "308",
"2048": "901",
"4096": "10159",
"8192": "2720",
"16384": "642",
"32768": "270",
"65536": "50",
"131072": "11",
"524288": "64",
"1048576": "102",
"2097152": "197",
"4194304": "415",
"8388608": "320",
"16777216": "50",
"33554432": "20",
"67108864": "9",
"268435456": "2"
},
"timestamp": "2013-05-14T15:51:40.000Z"
}, {
"type": "IoOpsDatapoint",
"latency": {
"512": "55",
"1024": "130",
"2048": "720",
"4096": "6500",
"8192": "1598",
"16384": "331",
"32768": "327",
"65536": "40",
"131072": "14",
"262144": "87",
"524288": "42",
"1048576": "97",
"2097152": "662",
"4194304": "345",
"8388608": "280",
"16777216": "22",
"33554432": "15",
"134217728": "1"
},
"timestamp": "2013-05-14T15:51:41.000Z"
}, ...]
}],
"resolution": 1
}
For the second slice, it might look like this:

225

Delphix User Guide 2016 Delphix

{
"type": "DatapointSet",
"collectionEvents": [],
"datapointStreams": [{
"type": "DiskOpsDatapointStream",
"datapoints": [{
"type": "IoOpsDatapoint",
"latency": {
"262144": "1",
"524288": "11",
"1048576": "13",
"2097152": "34",
"4194304": "7",
"8388608": "2",
"16777216": "3",
"33554432": "1"
},
"timestamp": "2013-05-14T15:51:40.000Z"
}, {
"type": "IoOpsDatapoint",
"latency": {
"262144", "5",
"524288", "10",
"1048576", "14",
"2097152", "26",
"4194304", "7",
"8388608", "4",
"16777216", "2"
},
"timestamp": "2013-05-14T15:51:41.000Z"
}, ...]
}],
"resolution": 1
}
The data is returned as a set of datapoint streams. Streams hold the fields that would otherwise be shared by all the datapoints they contain, but
only one is used in this example because there are no such fields. Streams are discussed in more detail in the Performance Analytics Tool
Overview. The resolution field indicates how many seconds each datapoint corresponds to, which in our case matches the requested collec
tionInterval. The collectionEvents field is not used in this example, but lists when the slice was paused and resumed to distinguish
between moments when no data was collected because the slice was paused, and moments when there was no data to collect.
Graphically, these four histograms across two seconds look like this:

226

Delphix User Guide 2016 Delphix

227

Delphix User Guide 2016 Delphix

Analysis
Because the NFS layer sits above the disk layer, all NFS operations that use the disk synchronously (synchronous writes and uncached reads)
will have latencies which are slightly higher than those of their corresponding disk operations. Usually, because disks have very high seek times
compared to the time the NFS server spends on CPU, disk operations are responsible for almost all of the latency of these NFS operations. In the
graphical representation, you can see this by looking at how the slower cluster of NFS latencies (around 2ms-8ms) have similar latencies to the
median of the disk I/O (around 2ms-4ms). Another discrepancy between the two plots is that the number of disk operations is much lower than the
corresponding number of NFS operations. This is because the Delphix filesystem batches together write operations to improve performance.
If database performance is not satisfactory and almost all of the NFS operation time is spent waiting for the disks, it suggests that the disk is the
slowest piece of the I/O stack. In this case, disk resources (the number of IOPS to the disks, the free space on the disks, and the disk throughput)
should be investigated more thoroughly to determine if adding more capacity or a faster disk would improve performance. However, care must be
taken when arriving at these conclusions, as a shortage of memory or a recently-rebooted machine can also cause the disk to be used more
heavily due to fewer cache hits.
Sometimes, disk operations will not make up all of the latency, which suggests that something between the NFS server and the disk (namely,
something in the Delphix Engine) is taking a long time to complete its work. If this is the case, it is valuable to check whether the Delphix Engine is
resource-constrained, and the most common areas of constraint internal to the Delphix Engine are CPU and memory. If either of those is too
limited, you should investigate whether expanding the resource would improve performance. If no resources appear to be constrained or more
investigation is necessary to convince you that adding resources would help the issue, Delphix Support is available to help debug these issues.
While using this technique, you should take care to recognize the limitations that caching places on how performance data can be interpreted. In
this example, the Delphix Engine uses a caching layer for the data it stores, so asynchronous NFS writes will not go to disk quickly because they
are being queued into larger batches, and cached NFS reads won't use the disk at all. This causes these types of NFS operations to return much
more quickly than any disk operations are able to, resulting in a very large number of low-latency NFS operations in the graph above. For this
reason, caching typically creates a bimodal distribution in the NFS latency histograms, where the first cluster of latencies is associated with
operations that only hit the cache, and the second cluster of latencies is associated with fully or partially uncached operations. In this case,
cached NFS operations should not be compared to the disk latencies because they are unrelated. It is possible to use techniques described in the
first example to filter out some of the unrelated operations to allow a more accurate mapping between disk and NFS latencies.

Related Links
The Performance Analytics Tool API Reference gives a full list of the commands, axes, and data types used by the analytics tool.

228

Delphix User Guide 2016 Delphix

_DelphixAdmin

229

Delphix User Guide 2016 Delphix

Users, Permissions, and Policies

These topics describe concepts and tasks related to the Delphix Domain and working with Groups.
Users and Groups
Users, Groups, and Permissions: An Overview
User Privileges for Delphix Objects
Adding Delphix Users and Privileges
Editing, Deleting, and Suspending Delphix Users
Assigning Group and Object Ownership
Adding and Deleting Groups
Adding Delphix Admin Users
Managing Individual Profile Information
Managing Policies
Managing Policies: An Overview
Creating Custom Policies
Creating Policy Templates
Policies and Time Zones
Configuring Retention on Individual Snapshots

230

Delphix User Guide 2016 Delphix

Users and Groups

These topics describe how to work with users and groups to assign permissions for objects in the Delphix Engine.
Users, Groups, and Permissions: An Overview
User Privileges for Delphix Objects
Adding Delphix Users and Privileges
Editing, Deleting, and Suspending Delphix Users
Assigning Group and Object Ownership
Adding and Deleting Groups
Adding Delphix Admin Users
Managing Individual Profile Information

231

Delphix User Guide 2016 Delphix

Users, Groups, and Permissions: An Overview

This topic describes the basic concepts behind Groups and the Delphix Domain, and information that can be found on the Group card.

Groups and the Delphix Domain

As described in the topics under Managing System Administrators, a Delphix Engine installation is based on two levels of object ownership.
The top level is the Delphix Domain. The Delphix Domain is the top level container of all objects in the Delphix Engine installation, and is
administered by users with Delphix Admin credentials.
Beneath the Delphix Domain are Groups. A Delphix Admin user creates groups, but can assign owner or auditor privileges over groups and
objects within them. All dSources and VDBs are created within a group.The topic User Privileges for Delphix Objects describes the exact object
privileges associated with the Owner and Auditor roles within a group.
When you first install the Delphix Engine, it automatically creates a first group, <New Group>. You can edit the name of this group to begin
creating your own groups.

The Use of Groups

Creating groups helps you manage policies and privileges over objects within that group. Policies can be created as policy templates, and when
applied at the group level, they extend over all objects within that group. See Creating Policy Templates for more information. Group privileges
function in the same way. When object privileges are created for users at the group level, those privileges apply to all objects of that type within
the group. When new objects are created or added to the group, the policies and privileges you have created at the group level will be applied to
them.
Databases are added to groups as part of the dSource creation process. See Linking an Oracle Data Source for more information.

The Group Card

You can find information about a group, such as its allocation, total storage used, and total storage free, on the group card. When you log into
the Delphix Admin application, all groups are listed in the Databases panel. Click the Expand icon next to a group to view its information. You
can also access the list of databases by selecting My Databases from the Databases menu.

Related Links
User Roles in the Delphix Domain
Linking an Oracle Data Source
Creating Policy Templates

232

Delphix User Guide 2016 Delphix

User Privileges for Delphix Objects

This topic describes the user privileges for Delphix objects.

Provisioner, Owner, Data Operator, and Reader Privileges

The user privileges on Delphix objects consist of four types, Provisioner, Owner, Data Operator, and Reader which the Delphix Admin user
assigns. These privileges apply both to objects, such as dSources and Virtual Databases (VDBs), and to groups, which are containers that hold
those objects.
The Delphix Admin user can assign privileges to groups, dSources and VDBs. Privileges are inherited, meaning that privileges assigned to a
group are effective for the dSources and VDBs contained in that group.
If a user does not have a privilege in relation to an object or group, then he or she has no visibility into that object or group.
All commands are limited by the privilege level of the user who is executing them. For example, a user with Reader privileges cannot execute the
Virtual to Physical command.
Owner Rights for Target Group
In order to provision a VDB to a target group, you must also have owner privileges for that group.

Roles and Privileges for Delphix Objects

Role

Object Privileges

Group Privileges

Provisioner

Can access statistics on the dSource, VDB, or

snapshot such as usage, history, and space
consumption
Can provision VDBs from owned dSources and VDBs

Can access statistics on all dSources, VDBs, or snapshots in

the group such as usage, history, and space consumption
Can provision VDBs from all dSources and VDBs in the group

Owner

Can provision VDBs from owned dSources and VDBs

Can perform Virtual to Physical (V2P) from owned
dSources
Can access the same statistics as an Reader
Can refresh or rollback VDBs
Can snapshot dSources and VDBs

Can provision VDBs from all dSources and VDBs in the group
Can refresh or rollback all VDBs in the group
Can snapshot all dSources and VDBs in the group
Can perform Virtual to Physical (V2P) from owned dSources
Can apply Custom policies to dSources and VDBs
Can create Template policies for the group
Can assign Owner privileges for dSources and VDBs
Can access the same statistics as an Provisioner, Data
Operator, or Reader

Data
Operator

Can access statistics on the dSource, VDB, or

snapshot such as usage, history, and space
consumption
Can refresh or rollback VDBs
Can snapshot dSources and VDBs

Can access statistics on all dSources, VDBs, or snapshots in

the group such as usage, history, and space consumption
Can refresh or rollback all VDBs in the group
Can snapshot all dSources and VDBs in the group

Reader

Can access statistics on the dSource, VDB, or

snapshot such as usage, history, and space
consumption

Can access statistics on all dSources, VDBs, or snapshots in

the group such as usage, history, and space consumption

Related Links
Adding Delphix Users

233

Delphix User Guide 2016 Delphix

Adding Delphix Users and Privileges

This topic describes how to add Delphix users and assign them privileges on objects.

Prerequisites
If you intend to validate user logins using LDAP authentication, make sure a system administrator has configured LDAP as described in Setting
Up the Delphix Engine.

Procedure
1. Launch the the Delphix Admin application and log in as delphix_admin and the password delphix.
2. Select Manage > Users.
3. Click Add User.
A new user profile will open on the right side.
4. Enter user name, email, and password information for the new user.
5. Clear the Delphix Admin selection, if necessary, and click Save.
A Privileges tab will be added to the user profile. See User Privileges for Delphix Objects for more information about privileges.
6. Assign the user Owner or Auditor privileges for appropriate Delphix objects.
Assigning Owner and Auditor Privileges
Assigning Owner privileges at the Group level conveys ownership privileges over all objects in that group. Click the expand
icon next to each group name to see all objects in that group.
You can also assign ownership privileges only for specific objects in a group. You do not have to assign owner or auditor
privileges for all Delphix objects, only those for which you want to grant the user specific access.

Related Links
Setting Up the Delphix Engine
Adding Delphix Admin Users
User Privileges for Delphix Objects

234

Delphix User Guide 2016 Delphix

Editing, Deleting, and Suspending Delphix Users

This topic describes how to suspend or delete Delphix users, and how to edit user information.
The delphix_admin user
The user named delphix_admin cannot be deleted since this is a user created by the Delphix Engine. However, you can suspend it.

Procedure
1. Launch the the Delphix Admin application and log in as a Delphix Admin user.
2. Select Manage > Users.
3. Click the user's name to open the user's profile panel.
4. Edit the user's profile information or object privileges as necessary.
5. Click the suspend icon to suspend that user.
6. Click the trash can icon to delete the user.
Deleting a user cannot be undone.

235

Delphix User Guide 2016 Delphix

Assigning Group and Object Ownership

This topic describes how to assign group and object ownership to users in the Delphix Domain.

Procedure
1. Log into the Delphix Admin application as a user with Delphix Admin privileges.
2. Select Manage > Users.
3. For an existing user, click the user name to the open the User Profile manager.
4. Click the Privileges tab.
5. Assign Owner or Auditor rights for groups or objects within groups.
You do not have to assign a specific owner or auditor right for each object.
6. Click Commit when finished.
7. For new users, follow the instructions in Adding Delphix Users and Privileges. When you click Save, the User Profile manager will
reload, and then you can follow steps 4 - 6 to assign privileges.

Related Links
Adding Delphix Users and Privileges
User Privileges for Delphix Objects

236

Delphix User Guide 2016 Delphix

Adding and Deleting Groups

This topic describes how to add and delete groups within the Delphix Domain.
Adding a Group
Deleting a Group

Adding a Group
1. Log into the Delphix Admin application as a user with Delphix Admin privileges.
2. In the Databases menu, select Add New Group.
3. Enter a Group Name and an optional description.
4. Click OK.

At Least One Group Must Exist

At least one group must always exist on the Delphix Engine in order to link a dSource. If you delete the last group, you will need to
create a new group in order to create a dSource.

Deleting a Group
1. Log into the Delphix Admin application as a user with Delphix Admin privileges or group OWNER privileges for the target group.
2. Open the group card in the Databases panel by selecting the target group
3. Click the Trash Can icon.
4. Click OK.

Deleting Groups Containing Objects

A group cannot be deleted if it contains VDBs or dSources. All databases within a group must be deleted prior to deleting the group.

237

Delphix User Guide 2016 Delphix

Adding Delphix Admin Users

This topic describes how to add Delphix Admin users.

Prerequisites
You must be a Delphix Admin user to create another Delphix Admin user.

Procedure
1. Launch the the Delphix Admin application and log in.
2. Select Manage > Users.
3. Click Add User.
A new user profile panel will open on the right side.
4. Enter user name, email, and password information for the new user.
5. Select Delphix Admin.
Unlike ordinary Delphix users, Delphix Admin users are not shown a Privileges tab. This is because they have full privileges over all
objects.
6. Click Save.

238

Delphix User Guide 2016 Delphix

Managing Individual Profile Information

This topic describes how individual users can manage personal settings such as personal information, passwords, event notifications, and
session timeouts. It also describes how users can view their privileges for Delphix objects.

Procedure
1. After logging in, click your name in the menu bar.
2. Click Profile.
3. Edit profile information as necessary.
4. Select options for the event level that will trigger a notification email.
5. Select a time period for Session Timeout.
6. Click Password to edit your password.
7. Click OK when finished.
8. Click Privileges to see your privileges (Auditor or Owner) for Delphix objects.

239

Delphix User Guide 2016 Delphix

Managing Policies
These topics describe creating and managing SnapSync, LogSync, Retention, and VDB Refresh policies.
Managing Policies: An Overview
Creating Custom Policies
Creating Policy Templates
Policies and Time Zones
Configuring Retention on Individual Snapshots

240

Delphix User Guide 2016 Delphix

Managing Policies: An Overview

This topic describes the types of policies that you can use to to manage database objects in the Delphix Engine.
There are four categories of policies that the Delphix Engine uses in conjunction with database objects:
SnapSync How often snapshots of a source database are taken for a dSource.
SnapSync and SQL Server Databases
SnapSync policies only apply to Oracle databases and dSources. For information on how Microsoft SQL Server dSources stay
in sync with the source database, see Setting Up SQL Server Environments: An Overview.

VDB Snapshot How often snapshots are taken of the virtual database (VDB).
Retention How long snapshots and log files are retained for dSources and VDBs.
VDB Refresh A destructive process that is used only if you need to re-provision VDBs from their sources at regular intervals. The
default setting for this policy is None.
Setting the VDB Refresh Policy Interval
Since VDB Refresh is a re-provisioning process, it is important to set the policy interval for an amount of time that will allow the
VDB to fully re-provision before another refresh takes place. For example, if you set the VDB Refresh policy to initiate a refresh
every 15 minutes, it is possible that the VDB will not fully re-provision in that amount of time, and your refresh process will fail.

There can additionally be default, custom, or template policies for each of these categories.
Policy
Type

Description

Who Can Set

Default

Default policies exist at the domain level and are applied across all objects in a category. You can modify the
settings for a default policy in a a category, but you cannot change the name default.

Users with
Delphix
Admin
credentials

Custom

Custom policies can only be applied to a specific database object. These cannot be saved to be used with other
objects. You can create custom policies for dSources during the dSource linking process, as described in the Lin
king and Advanced Data Management Settings topics for each database platform type. See also Creating
Custom Policies.

Users with
Delphix
Admin
credentials
Group and
object
owners

Template

Template policies are named policies that can be saved and applied to other database objects and to groups.
These are created on the Policy Management screen.See Creating Policy Templates for more information.

Users with
Delphix
Admin
credentials
Group and
object
owners

Setting Different Policies for Objects in a Group

Policies applied at the group level will affect all objects in that group. If you want to set different policies for objects in a group, apply the
policies at the group level first, then apply policies at the object level.

241

Delphix User Guide 2016 Delphix

Creating Custom Policies

This topic describes creating custom policies based on cron expressions for specific database objects or groups.
Custom policies are created by editing a policy associated with a database object, either during its creation or through the Policy Management sc
reen after it has been created. For information about creating custom policies for dSources and VDBs during the linking and provisioning
processes, see the Linking and Provisioning topics listed for each data platform.

Procedure
1. Login to the Delphix Admin application as a user with Delphix Admin privileges.
2. Click Manage.
3. Select Policies.
4. Select the policy for the object or group your want to modify.
5. Click Apply New Policy.
6. Enter Name for the policy.
7. Select Customized.
8. Enter the cron expressions you want to use for the policy. The expected format is compatible with the Quartz CronTrigger scheduler.
9. Choose either Weekly, Hours or Minutes, or Custom for Scheduled By.
10. Click OK.

242

Delphix User Guide 2016 Delphix

Creating Policy Templates

This topic describes how to create policy templates that can be applied to groups and database objects.
Unlike custom policies, template policies can be saved and applied to other groups and database objects. See the topics under Users,
Permissions, and Policies for more information on using policies with groups.

Procedure
1. Log into the Delphix Admin application as a user with Delphix Admin privileges.
2. Select Manage > Policies.
3. Click Modify Policy Templates.
4. Under the category where you want to create the template, click Add New Policy.
5. Enter a Name for the template.
6. Enter the cron expressions you want to use for the new policy. The expected format is compatible with the Quartz Cron Trigger schedul
er.
7. Click OK.

Post-Requisites
You can apply the new policy by selecting the appropriate policy category for an existing object or group, and then select the template
policy

Related Links
Users, Permissions, and Policies

243

Delphix User Guide 2016 Delphix

Policies and Time Zones

Policies and Time Zones
You can configure the SnapSync, VDBSnapshot, and VDBRefresh policies with the time zone in which the policy should be scheduled.

To edit the time zone of a policy:

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Policies.
4. Select the policy.
5. In the policy card, click the pencil icon.
6. Select the appropriate time zone from the dropdown list.
Note: Retention

and Quota policies are not schedulable and do not need a time zone.

Upgrading to Version 4.2 or higher:

Prior to version 4.2, a policy operated under the time zone of the policys target. For example, a SnapSync Policy scheduled for 4:00am every day
that targeted a dSource in Eastern Standard Time (EST) and a dSource in Pacific Standard Time (PST) fired twice a day: once at 4:00am EST
and once at 4:00am PST.

To maintain the same behavior of the Delphix Engine after upgrade, the upgrade process clones existing policies
with these clones differing only in their time zone. After upgrading, you may notice that the names of policies change
to include the time zones in which they operate.
Note: Default

policies are not cloned and always operate under the time zone of the Delphix Engine.

Example Upgrade of an Engine

Pre-Upgrade

Sample Policy Dashboard, Version 4.0.0

Post-Upgrade

Sample Policy Dashboard, Version 4.2

In this example, the dSources and VDBs originally operated under either EST (America/New_York) or CST
(America/Mexico_City), and new policies were created to reflect this.

Original Policy

New Policies

UserSnapSync

UserSnapSync (America/Mexico_City)
UserSnapSync (America/New_York)

SnapshotTest

SnapshotTest (America/Mexico_City)
SnapshotTest (America/New_York)

244

Delphix User Guide 2016 Delphix

UserRefresh

UserRefresh (America/Mexico_City)
UserRefresh (America/New_York)

After an upgrade, ensure that the policies are configured as expected; it may have been unclear prior to this upgrade when policies were actually
firing.
Also, after upgrading to 4.2 or higher, you may consolidate/clean-up the clones and these changes will persist through future upgrades. If you go
to the policy tab, and click on a policy you should see a timezone field. This timezone field is editable. So for example, if you had "VDB_SNAP
(US/Arizona)" and "VDB_SNAP (America/Phoenix)", you could delete one of the duplicates (they are both from the same time zone in this case),
make sure the timezone field is set to the desired time zone and rename the remaining policy to "VDB_SNAP".

245

Delphix User Guide 2016 Delphix

Configuring Retention on Individual Snapshots

This topic describes adding a custom retention definition for individual snapshots. This value will override that of the policy currently assigned to
the container, for example if 'forever' is selected then the snapshot will no longer be deleted via the retention policy.

Procedure
1. Log into the Delphix Admin application as a user with Delphix Admin privileges.
2. Select Resources > Capacity.
3. Expand the object (dsource or vdb) to modify.
4. Expand the snapshots. (it may take a few minutes for the individual snapshots to appear)
5. Configure the desired value in the 'keep until' column, either the number of days or tick forever.

246

Delphix User Guide 2016 Delphix

Oracle Environments and Data Sources

247

Delphix User Guide 2016 Delphix

Oracle Support and Requirements

These topics describe specific requirements for Oracle environments, such as user privileges, and the supported versions of Oracle DBMS and
compatible operating systems.
Network and Connectivity Requirements for Oracle Environments
Requirements for Oracle Source Hosts and Databases
Requirements for Oracle Target Hosts and Databases
Sudo File Configurations
Sudo Privilege Requirements This topic describes the rationale behind specific sudo privilege requirements for working

with the Delphix Engine.

Supported Operating Systems and DBMS Versions for Oracle Environments

248

Delphix User Guide 2016 Delphix

Supported Operating Systems and DBMS Versions for Oracle Environments

This topic describes the Oracle Database Management System (DBMS) versions that are supported by Delphix, as well as the compatible
operating systems (OS), for use on target and source environments.
Source and Target OS and DBMS Compatibility
The source and target must be running the same DBMS/Operating System combination (for example, Oracle 10.2.0.4 on RHEL 5.2) in
order to successfully provision a VDB to the target. If the DBMS versions are compatible, the OS version on a target host can be
different from the OS version on the source host.

Supported DBMS Versions

Oracle 9.2.0.8
Oracle 10.2
Oracle 11.1
Oracle 11.2
Oracle 12.1
Oracle 9.2.0.8
The Delphix Engine has limited support for Oracle 9.2.0.8 and cannot link to a database that has a compatibility setting lower than
9.2.0.8.
Delphix features supported with Oracle 9.2.0.8:
dSource

VDB

SnapSync

Yes

No

LogSync

No

No

Rewind

Not Applicable

No

V2P (virtual to physical)

Yes

No

RAC

No

No

Standby Database

No

No

Oracle 10.2.0.4
The Delphix Engine does not support Oracle 10.2.0.4 databases using Automatic Storage Management (ASM) that do not have the
patch set for Oracle Bug 7207932. This bug is fixed in patch set 10.2.0.4.2 onward.

Supported Operating Systems

Operating System

Version

Processor Family

Solaris

9, 10U5 - 10U11, 11U1, 11U2

SPARC

Solaris

10U5 - 10U11, 11U1, 11U2

x86_64

Red Hat Enterprise Linux

4.7, 4.8, 4.9

5.3 - 5.11
6.0 - 6.6

x86_64

Oracle Enterprise Linux

5.3 - 5.11
6.0 - 6.6

x86_64

Novell SUSE Linux Enterprise Server

10, 10SP1, 10SP2, 10SP3

11, 11SP1, 11SP2, 11SP3

x86_64

249

Delphix User Guide 2016 Delphix

AIX

5.3, 6.1, 7.1

Power

HP-UX

11i v2 (11.23)

IA64

11i v3 (11.31)
Delphix supports all 64-bit OS environments for source and target, though 64-bit Linux environments also require that a 32-bit version of glibc
installed
Required HP-UX patch for Target Servers
PHNE_37851 - resolves a known bug in HP-UX NFS client prior to HP-UX 11.31.

250

Delphix User Guide 2016 Delphix

Requirements for Oracle Source Hosts and Databases

This topic describes the requirements for Oracle source environments and databases. Virtual databases (VDBs) are created from these source
environments.
Source Host Requirements
OS Specific Requirements
AIX
HP-UX
Linux
Solaris
Auto-Discovery Requirements (Highly Recommended)
Source Database Requirements
Additional requirements for RAC sources
Troubleshooting Add Environment
Troubleshooting Linking
Related Links

Source Host Requirements

1. Create an operating system user (delphix_os). This user is easily created by the createDelphixOSUser.sh script.
a. Profile and privileges should be the same as the Oracle user (oracle) on the host.
For example, delphix_os should have the same environment variable settings ($PATH, $ORACLE_HOME, etc.)
and ulimit settings, as oracle.
Shortcut: Source the oracle login script from the delphix_os login script.

b. Group memberships:
i. The user's primary group must be the UNIX group that is mapped to OSDBA by the Oracle installation. This is typically
the dba group on the host.
Oracle 12c
For Oracle 12c and later versions of Oracle databases, the delphix_os user can also use OSBACKUPDBA as
its primary group. This is typically the backupdba group on the host.

ii. If the Oracle install group (typically oinstall), exists on the host, it should be set as a secondary group for the user.
iii. If the Oracle ASM groups (typically asmadmin and asmdba) exist on the host, they should be assigned to the user as
secondary groups.
2. There must be a directory on the source host where the Delphix Engine Toolkit can be installed, for example: /var/opt/delphix/Toolkit.
a. The delphix_os user must own the directory.
b. The directory must have permissions -rwxrwx--- (0770), but you can also use more permissive settings.
c. The directory should have 1.5GB of available storage: 400MB for the toolkit and 400MB for the set of logs generated by each
client that runs out of the toolkit.

3. The Delphix Engine must be able to make an SSH connection to the source host (typically port 22)

OS Specific Requirements
AIX
None

HP-UX
None

251

Delphix User Guide 2016 Delphix

Linux
On 64-bit Linux environments, there must be a 32-bit version of glibc.

How to Check for 32-bit glibc on 64-bit Linux

$ rpm -qa|grep glibc
glibc-devel-2.12-1.107.el6_4.5.x86_64 <=== 64-bit
glibc-devel-2.12-1.107.el6_4.5.i686 <==== 32-bit
glibc-2.12-1.107.el6_4.5.x86_64
glibc-common-2.12-1.107.el6_4.5.x86_64
glibc-headers-2.12-1.107.el6_4.5.x86_64
glibc-2.12-1.107.el6_4.5.i686 <======== 32-bit

Solaris
On a Solaris host, gtar must be installed. Delphix uses gtar to handle long file names when extracting the toolkit files into the toolkit directory on
a Solaris host. The gtar binary should be installed in one of the following directories:

/bin:/usr
/bin:/sbin:/usr
/sbin:/usr/contrib
/bin:/usr/sfw
/bin:/opt/sfw
/bin:/opt/csw/bin

Auto-Discovery Requirements (Highly Recommended)

Delphix can automatically discover your Oracle Homes and Databases by examining the inventory and oratab files, and by examining the listener
setup to determine connection information. Successful autodiscovery requires read access to these and related files.
In most environments, delphix_os group membership is sufficient to perform auto-discovery.
If you have overridden Oracle's group permission structure, you may need to modify privileges to allow auto-discovery.
Unless you have used a custom TNS_ADMIN setting, elevated access to ps (pargs on Solaris) is not required
You can skip autodiscovery and manually add Oracle Homes and Databases.
1. The ORATAB file must exist (typically in /etc/oratab or /var/opt/oracle/oratab) and be readable by delphix_os.
2. Read access to either /etc/orainst.loc or /var/opt/oracle/orainst.loc.
3. Read access to the Oracle inventory file (inventory.xml) identified by the contents of orainst.loc (for example, $INVENTORY_HO
ME/ContentsXML/inventory.xml).
4. Permission to run pargs on Solaris hosts and ps on AIX, HP-UX, Linux hosts, as super-user.
This permission is usually granted via sudo authorization of the commands. See the topic Sudo Privilege Requirements for further
explanation of this requirement, and Sudo File Configurations for examples of file configurations.

Source Database Requirements

1. Source databases must be in ARCHIVELOG mode to ensure that redo logs are archived. (Mandatory). Archive logs are required to
make SnapSyncs consistent and provisionable.
2. There must be a database user (delphix_db) created by the createDelphixDBUser.sh script. This script is part of the HostChecker
bundle, and grants SELECT privileges on specific system tables for the user. See the topics Using HostChecker to Validate Oracle
Source and Target Environments for more about using the HostChecker bundle.
Oracle pluggable databases

252

Delphix User Guide 2016 Delphix

For an Oracle pluggable database, there must be one database user (delphix_db) for the pluggable database and one
common database user (c##delphix_db) for its container database. The createDelphixDBUser.sh script can create both
users.

3. Enable Block Change Tracking (BCT). (Highly Recommended). Without BCT, incremental SnapSyncs must scan the entire
database.
BCT is an Enterprise Edition feature.

See Linking Oracle Physical Standby Databases for restrictions on enabling BCT on Oracle Physical Standby databases.

Enter this command to enable BCT:

alter database enable block change tracking using file '<user specified file>;
4. Enable FORCE LOGGING. (Highly Recommended). This prevents NOLOGGING operations on Source Databases. Oracle requires
FORCE LOGGING for proper management of standby databases.
Enter this command to enable FORCE LOGGING:

SQL> ALTER DATABASE force logging;

If you do not enable FORCE LOGGING and NOLOGGING operations take place, you will get a Fault from Delphix. If you must
use NOLOGGING to meet specific performance criteria, take a new snapshot of the source database after doing the
NOLOGGING operations to bring the dSource up-to-date before provisioning VDBs. To avoid repeated Faults, you can disable
"Diagnose Nologging" on your dSource.

5. If the online redo log files are located on RAW or ASM devices, then the Delphix Engine LogSync feature can operate in Archive Only m
ode only.

Additional requirements for RAC sources

If the source host is a node in a RAC cluster, Delphix will attempt to use all nodes and crsctl for it's operations.
1. delphix_os must exist on all nodes in the cluster.
2. delphix_os must have the same configuration on all nodes in the cluster, including profile, ulimits, user id, group membership, etc.
3. The Delphix Toolkit must be installed in the same directory on each of the nodes in the source cluster
4. delphix_os must have execute permission on crsctl and srvctl on each node in the cluster.

Example: This shows that the group dba has read/write/execute permission on the
database resources
$ crsctl get hostname
node2

5. All datafiles and archive logs must be located on storage shared by all of the cluster nodes. Each node in the cluster must be able to
access archive logs from all other nodes. This is an Oracle Best Practice, and a requirement for Delphix.

Troubleshooting Add Environment

LDAP/NIS User
If the delphix_os user is a LDAP/NIS user, it must be a member of the dba and oinstall groups in /etc/groups locally in order for
Oracle commands to run properly.

253

Delphix User Guide 2016 Delphix

1. Read access to $ORACLE_HOME and all underlying files and directories.

2. The delphix_os user must have read and execute permissions on each directory in the path leading to the toolkit directory. For example,
when the toolkit is stored in /var/opt/delphix/Toolkit, the permissions on /var, /var/opt, and /var/opt/delphix should allow read and execute
for others (for example, -rwxr-xr-x).

Troubleshooting Linking
For each Oracle Home which you will use with dSources, the delphix_os user should have:
1. Execute permission for the programs in $ORACLE_HOME/bin.
2. The $ORACLE_HOME/bin/oracle executable must have the SETUID and SETGID flags set. Permissions on the oracle binary must
be -rwsr-sx (06751) but you can also use more permissive settings.

Related Links
Requirements for Oracle Target Hosts and Databases
Using HostChecker to Confirm Source and Target Environment Configuration
Sudo File Configurations
Sudo Privilege Requirements

254

Delphix User Guide 2016 Delphix

Requirements for Oracle Target Hosts and Databases

This topic describes the user privileges, and environment discovery requirements, that are required for Oracle and Oracle RAC target hosts and
databases, collectively referred to a target environments.

Target Host Requirements

1. Create an operating system user (delphix_os). This user is easily created by the createDelphixOSUser.sh script.
a. Profile and privileges should be the same as the Oracle user (oracle) on the host.
For example, delphix_os should have the same environment variable settings ($PATH, $ORACLE_HOME, etc.) and ulimit setti
ngs, as oracle.
Shortcut: Source the oracle login script from the delphix_os login script.

b. Group memberships:
i. The user's primary group must be the UNIX group that is mapped to OSDBA by the Oracle installation. This is typically
the dba group on the host.
Oracle 12c
For Oracle 12c and later versions of Oracle databases, the delphix_os user can also use OSBACKUPDBA
as its primary group. This is typically the backupdba group on the host.

ii. If the Oracle install group (typically oinstall), exists on the host, it should be set as a secondary group for the user.
iii. If the Oracle ASM groups (typically asmadmin and asmdba) exist on the host, they should be assigned to the user as
secondary groups.
2. There must be a directory on the source host where the Delphix Engine Toolkit can be installed, for example: /var/opt/delphix/Too
lkit.
a. The delphix_os user must own the directory.
b. The directory must have permissions -rwxrwx--- (0770), but you can also use more permissive settings.
c. The directory should have 1.5GB of available storage: 400MB for the toolkit and 400MB for the set of logs generated by each
client that runs out of the toolkit.
3. There must be an empty directory (e.g. /delphix or /mnt/provision/ ) that will be used as a container for the mount points that are created
when provisioning a VDB to the target host. The group associated with the directory must be the primary group of the delphix_os user
(typically dba). Group permissions for the directory should allow read, write, and execute by members of the group.
4. The following permissions are usually granted via sudo authorization of the commands. See Sudo Privilege Requirements for further
explanation of the commands, and Sudo File Configurations for examples of the /etc/lsudoers file on different operating systems.
a. Permission to run mount, umount, mkdir, rmdir, ps as super-user.
b. Permission to run pargs on Solaris hosts and ps on AIX, HP-UX, Linux hosts, as super-user.
c. If the target host is an AIX system, permission to run the nfso command as super-user.
5. Write permission to the $ORACLE_HOME/dbs directory
6. An Oracle listener process should be running on the target host. The listener's version should be equal to or greater than the highest
Oracle version that will be used to provision a VDB.
7. NFS client services must be running on the target host.
8. The Delphix Engine must be able to make an SSH connection to the target host (typically port 22)

OS Specific Requirements
AIX, HP-UX

None
Linux

On 64-bit Linux environments, there must be a 32-bit version of glibc.

How to Check for 32-bit glibc on 64-bit Linux
$ rpm -qa|grep glibc

255

Delphix User Guide 2016 Delphix

glibc-devel-2.12-1.107.el6_4.5.x86_64 <=== 64-bit

glibc-devel-2.12-1.107.el6_4.5.i686 <==== 32-bit
glibc-2.12-1.107.el6_4.5.x86_64
glibc-common-2.12-1.107.el6_4.5.x86_64
glibc-headers-2.12-1.107.el6_4.5.x86_64
glibc-2.12-1.107.el6_4.5.i686 <======== 32-bit

Solaris

On a Solaris host, gtar must be installed. Delphix uses gtar to handle long file names when extracting the toolkit files into the toolkit directory on
a Solaris host. The gtar binary should be installed in one of the following directories:
/bin:/usr
/bin:/sbin:/usr
/sbin:/usr/contrib
/bin:/usr/sfw
/bin:/opt/sfw
/bin:/opt/csw/bin

Auto-Discovery Requirements (Highly Recommended)

Delphix can automatically discover your Oracle Homes and Databases by examining the oratab and/or inventory files, and by examining the
listener setup to determine connection information. Successful auto-discovery requires read access to these and related files.
In most environments, delphix_os group membership is sufficient to perform auto-discovery.
If you have overridden Oracle's group permission structure, you may need to modify privileges to allow auto-discovery.
Unless you have used a custom TNS_ADMIN setting, elevated access to ps (pargs on Solaris) is not required
You can skip autodiscovery and manually add Oracle Homes and Databases.
1.The ORATAB file must exist (typically in /etc/oratab or /var/opt/oracle/oratab) and be readable by delphix_os.
2. Read access to either /etc/orainst.loc or /var/opt/oracle/orainst.loc.
3. Read access to the Oracle inventory file (inventory.xml) identified by the contents of orainst.loc (for example, $INVENTO
RY_HOME/ContentsXML/inventory.xml).
Oracle Target Container Databases Requirements
To provision an Oracle pluggable database, there must be a running Oracle multitenant container database in the target environment. In the
multitenant container database, there must be a common database user (c##delphix_db) created by the createDelphixDBUser.sh script. This
script is part of the HostChecker bundle, and grants SELECT privileges on specific system tables for the user. See the topics Using
HostChecker to Validate Oracle Source and Target Environments for more about using the HostChecker bundle.

Additional requirements for RAC sources

If the source host is a node in a RAC cluster, Delphix will attempt to use all nodes and crsctl for it's operations.
1. delphix_os must exist on all nodes in the cluster.
2. delphix_os must have the same configuration on all nodes in the cluster, including profile, ulimits, user id, group membership, etc.
3. The Delphix Toolkit must be installed in the same directory on each of the nodes in the source cluster
4. delphix_os must have execute permission on crsctl and srvctl on each node in the cluster.
Example: This shows that the group dba has read/write/execute permission on the database resources

Example: This shows that the group dba has read/write/execute permission on the
database resources
$ crsctl getperm resource ora.trois.db
Name: ora.trois.db
owner:ora112:rwx,pgrp:dba:rwx,other::r-5. All datafiles and archive logs must be located on storage shared by all of the cluster nodes. Each node in the cluster must be able to

256

Delphix User Guide 2016 Delphix

5.
access archive logs from all other nodes. This is an Oracle Best Practice, and a requirement for Delphix.

LDAP/NIS User

Troubleshooting Add Environment

LDAP/NIS User
If the delphix_os user is a LDAP/NIS user, it must be a member of the dba and oinstall groups in /etc/groups locally in
order for Oracle commands to run properly.
1. Read access to $ORACLE_HOME and all underlying files and directories.
2. The delphix_os user must have read and execute permissions on each directory in the path leading to the toolkit directory. For
example, when the toolkit is stored in /var/opt/delphix/Toolkit, the permissions on /var, /var/opt, and /var/opt/delphix should
allow read and execute for others (for example, -rwxr-xr-x).

Troubleshooting Provisioning
1. The $ORACLE_HOME/bin/oracle executable must have the SETUID and SETGID flags set. Permissions on the oracle
binary must be -rwsr-sx (06751) but more permissive settings can also be used.

Related Links
Requirements for Oracle Source Hosts and Databases
Using HostChecker to Validate Oracle Source and Target Environments
Network and Connectivity Requirements for Oracle Environments
Sudo Privilege Requirements
Sudo File Configurations

257

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for Oracle Environments

General Port Allocation
General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration
Network and Connectivity Requirements for Oracle
Port Allocation for Oracle Environments
Outbound from the Delphix Engine Port Allocation
Inbound to the Delphix Engine Port Allocation

General Port Allocation

The Delphix Engine makes use of the following network ports regardless of the type of database platform:

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and

258

Delphix User Guide 2016 Delphix

the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

Network and Connectivity Requirements for Oracle

IP connections must exist between the Delphix Engine and source and target environments.
For source environments, Delphix Engine uses an SSH connection to each source host, an HTTP connection from each source
environment to Delphix Engine, and a DSP connection to the Delphix Engine. The Delphix Engine uses SQL*Net connections to the
DBMS on the source environment.
For target environments, Delphix uses an SSH connection to each target environment, and an NFS connection to Delphix Engine.
Delphix Engine uses SQL*Net connections to the virtual databases on the target environment.

scp Availability
The scp program must be available in the environment in order to add an environment.

Port Allocation for Oracle Environments

The following diagram describes the port allocations for Oracle environments. It illustrates the ports that we recommend to be open from
Delphix to remote services, to the Delphix Engine, and to the Target Environments.

The Delphix Engine makes use of the following network ports for Oracle dSources and VDBs:

259

Delphix User Guide 2016 Delphix

Outbound from the Delphix Engine Port Allocation

Protocol

Port Numbers

Use

TCP

22

SSH connections to source and target environments

TCP

xxx

Connections to the Oracle SQL*Net Listener on the source and target environments (typically port 1521)

Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP/UDP

111

Remote Procedure Call (RPC) port mapper used for NFS mounts
Note: RPC calls in NFS are used to establish additional ports, in the high range 32768-65535, for supporting
services. Some firewalls interpret RPC traffic and open these ports automatically. Some do not; see below.

TCP

1110

NFS Server daemon status and NFS server daemon keep-alive (client info)

TCP/UDP

2049

NFS Server daemon from VDB to the Delphix Engine

TCP

4045

NFS lock daemon/manager

TCP

8341

Sending data from source to the Delphix Engine (for LogSync)

TCP

8415

SnapSync control and data from source to the Delphix Engine

V2P control and data from the target environment to the Delphix Engine.

UDP

33434 33464

Traceroute from source and target database servers to the Delphix Engine (optional)

UDP/TCP

32768 65535

NFS mountd and status services, which run on a random high port. Necessary when a firewall does not
dynamically open ports.

260

Delphix User Guide 2016 Delphix

Sudo File Configurations

This topic describes sudo file privilege configurations for using the Delphix Engine with various operating systems and for specific security
requirements.

Configuring sudo Access on Solaris SPARC for Source and Target Environments
Sudo access to pargs on the Solaris operating system is required for the detection of listeners with non-standard configurations on both source
and target environments. Super-user access level is needed to determine the TNS_ADMIN environment variable of the user running the listener
(typically oracle, the installation owner). From TNS_ADMIN, the Delphix OS user delphix_os can derive connection parameters.

Example: Solaris /etc/sudoers entries for a Delphix Source

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD:/usr/bin/pargs
On a Solaris target, sudo access to mount, umount, mkdir and rmdir is also required.

Example: Solaris /etc/sudoers entries for a Delphix Target

User_Alias DELPHIX_USER=delphix_os
Cmnd_Alias DELPHIX_CMDS= \
/usr/sbin/mount, \
/usr/sbin/umount, \
/usr/bin/mkdir, \
/usr/bin/rmdir, \
/usr/bin/pargs
DELPHIX_USER ALL=(ALL) NOPASSWD: DELPHIX_CMDS
Configuring sudo Access on Linux for Source and Target Environments
Sudo access to ps on the Linux operating system is required for the detection of listeners with non-standard configurations on both source and
target environments. Super-user access level is needed to determine the TNS_ADMIN environment variable of the user running the listener
(typically oracle, the installation owner). From TNS_ADMIN, the Delphix OS user delphix_os can derive connection parameters.

Example: Linux /etc/sudoers entries for a Delphix Source

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD:/bin/ps
On a Linux target, sudo access to mount, umount, mkdir and rmdir is also required.

Example: Linux /etc/sudoers file for a Delphix Target

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD: \
/bin/mount, /bin/umount, /bin/mkdir, /bin/rmdir, /bin/ps

Configuring sudo Access on AIX for Source and Target Environments

Sudo access to ps on the AIX operating system is required for the detection of listeners with non-standard configurations on both source and
target environments. Super-user access level is needed to determine the TNS_ADMIN environment variable of the user running the listener
(typically oracle, the installation owner). From TNS_ADMIN, the Delphix OS user delphix_os can derive connection parameters.

261

Delphix User Guide 2016 Delphix

Example: AIX /etc/sudoers entries for a Delphix Source

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD:/bin/ps
In addition to sudo access to the mount, umount, mkdir, rmdir, and ps commands on AIX target hosts, Delphix also requires sudo access to n
fso. This is required on target hosts for Delphix to monitor the NFS read write sizes configured on the AIX system. Super-user access level is
needed to run the nfso command.

Example: AIX /etc/sudoers File for a Delphix Target

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD: \
/bin/mount, \
/bin/umount, \
/bin/mkdir, \
/bin/rmdir, \
/bin/ps, \
/usr/sbin/nfso
Configuring sudo Access on HP-UX for Source and Target Environments
No sudo privileges are required on source environments running HP-UX. The HP-UX OS does not allow the delphix_os user to determine TNS_
ADMIN environment variable setting for the oracle user. This means that non-standard listener configurations, with non-default TNS_ADMIN settin
gs, cannot be auto-discovered.
On the HP-UX target, sudo access to mount, umount, mkdir and rmdir is required as with other operating systems.

Example: HP-UX /etc/sudoers file for a Delphix Target

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD:/sbin/mount, /sbin/umount, /bin/mkdir, /bin/rmdir
Other Examples of Limiting sudo Access for the Delphix OS User to the VDB Mount Directory Only
In situations where security requirements prohibit giving the Delphix user root privileges to mount, unmount, make directory, and remove directory
on the global level, it is also possible to configure the sudoers file to provide these privileges on the virtual database mount directory only, as
shown in these two examples.
Example 1

This example restricts the delphix_os user's use of sudo privileges to the directory /oracle.
Note that wildcards are allowed for the options on mount and umount because those commands expect a fixed number of arguments after the
options. The option wildcard on the mount command also makes it possible to specify the file-system being mounted from the Delphix Engine.
But wildcards are not acceptable on mkdir and rmdir because they can have any number of arguments after the options. For those commands
you are required to specify the exact options (-p, -p -m 755) used by the Delphix Engine.

262

Delphix User Guide 2016 Delphix

Example /etc/sudoers File Configuration on the Target Environment for sudo Privileges on the
VDB Mount Directory Only
Defaults:delphix_os !requiretty
delphix_os ALL=(root) NOPASSWD:
/bin/mount *
/oracle/*,
/bin/umount *
/oracle/*,
/bin/umount
/oracle/*,
/bin/mkdir -p
/oracle/*,
/bin/mkdir -p -m 755 /oracle/*,
/bin/mkdir
/oracle/*,
/bin/rmdir
/oracle/*,
/bin/ps

\
\
\
\
\
\
\
\

Example /etc/sudoers File Configuration on the Source Environment to grant Super-User

privileges when running PS
Defaults:delphix_os !requiretty
delphix_os ALL=(root) NOPASSWD: /bin/ps

Example 2

This example restricts the delphix_os user's use of sudo privileges to the directory /mnt/delphix.
This example demonstrates a very restrictive syntax for the mount and umount commands. The umount command allows no user-specified
options. The mount command specifies the Delphix Engines server name (or IP address) on the mount command so as to limit which file
systems can be mounted.

A Second Example of Configuring the /etc/sudoers File on the Target Environment for Privileges
on the VDB Mount Directory Only
/usr/sbin/umount "", \
/usr/sbin/mount "", \Defaults:delphix_os !requiretty
delphix_os ALL=(root) NOPASSWD: \
/usr/sbin/mount
<delphix-server-name>* /mnt/delphix/*, \
/usr/sbin/mount *
<delphix-server-name>* /mnt/delphix/*, \
/usr/sbin/mount
<delphix-server-ip>*
/mnt/delphix/*, \
/usr/sbin/mount *
<delphix-server-ip>*
/mnt/delphix/*, \
/usr/sbin/mount "", \
/usr/sbin/umount
/mnt/delphix/*, \
/usr/sbin/umount *
/mnt/delphix/*, \
/usr/bin/mkdir [*]
/mnt/delphix/*, \
/usr/bin/mkdir
/mnt/delphix/*, \
/usr/bin/mkdir -p
/mnt/delphix/*, \
/usr/bin/mkdir -p -m 755 /mnt/delphix/*, \
/usr/bin/rmdir
/mnt/delphix/*, \
/usr/bin/ps, \
/bin/ps
Considerations for sudo access and account locking
The Delphix Engine tests its ability to run the mount command using sudo on the target environment by issuing the sudo mount com
mand with no arguments. Many of the examples shown in this topic do not allow that, and in those cases the attempt will be blocked. In
most situations, this does not cause a problem.
Similarly, the ps or pargs command is used for target environment operations such as initial discovery and refresh. The most
restrictive sudo setups might not allow the commands ps (pargs), mkdir, and rmdir; strictly speaking, Delphix can still function
without these privileges (see Sudo Privilege Requirements for a full explanation).

263

Delphix User Guide 2016 Delphix

However, some users configure the security on the target environments to monitor sudo failures and lock out the offending account
after some threshold. In those situations, the delphix_os account can become locked. One work-around for this situation is to increase
the threshold for locking out the user account. Another option is to modify /etc/sudoers to permit the delphix_os user to run ps
(pargs), mkdir, rmdir, and mount command without parameters.

Related Links
Sudo Privilege Requirements
Requirements for Oracle Source Hosts and Databases
Requirements for Oracle Target Hosts and Databases

264

Delphix User Guide 2016 Delphix

Sudo Privilege Requirements

This topic describes the rationale behind specific sudo privilege requirements for working with the Delphix Engine.
Privilege

Sources

Targets

Rationale

ps | pargs

Optional,
Optional,
Delphix auto-discovery uses the TNS_ADMIN environment variable of Oracle Listener
Strongly
Strongly
processes with non-standard configurations to derive their connection parameters. An
Recommended Recommended Oracle Listener is normally owned by a different user (oracle) than the delphix_os user.
The Delphix Engine needs sudo access to pargs on the Solaris OS or ps on other OSes
to examine the environment variables of those Listener processes.
This privilege is optional in all cases, since you can manually configure dSources and
VDBs. It is also optional when using a standard TNS_ADMIN location.
Optional

Delphix dynamically makes and removes directories under the provisioning directory
during VDB operations. This privilege is optional, provided the provisioning directory
permissions allow the delphix os user to make and remove directories.

mount/umount Not Required

Required

Delphix dynamically mounts and unmounts directories under the provisioning directory
during VDB operations. This privilege is required because mount and umount are
typically reserved for superuser.

nfso (AIX only)

Required

Delphix monitors NFS read and write sizes on an AIX target host. It uses the nfso comm
and to query the sizes in order to optimize NFS performance for VDBs running on the
target host. Only a superuser can issue the nfso command.

mkdir/rmdir

Not Required

Not Required

Related Links
Requirements for Oracle Source Hosts and Databases
Requirements for Oracle Target Hosts and Databases
Sudo File Configurations

265

Delphix User Guide 2016 Delphix

Managing Oracle Environments

These topics describe special tasks and concepts for Oracle environments.
Using HostChecker to Validate Oracle Source and Target Environments
Adding an Oracle Single Instance or RAC Environment
Adding a Database Installation Home to an Oracle Environment
Adding a Database to an Oracle Environment
Discovering Oracle Pluggable Databases in an Oracle Environment
Adding a Listener to an Oracle Environment
Changing the Host Name or IP Address for Oracle Source and Target Environments
Editing Oracle Environment Attributes
Managing Oracle Environment Users
Enabling Linking and Provisioning for Oracle Databases
Deleting an Oracle Environment
Refreshing an Oracle Environment
Virtual Warehouse

266

Delphix User Guide 2016 Delphix

Using HostChecker to Validate Oracle Source and Target Environments

What is HostChecker?
Prerequisites
Procedure
Non-Interactive Mode
Tests Run
Checking Hosts Post-Deployment
Related Links

What is HostChecker?
The HostChecker is a standalone program which validates that host machines are configured correctly before the Delphix Engine uses them as
data sources and provision targets.
Please note that HostChecker does not communicate changes made to hosts back to the Delphix Engine. If you reconfigure a host, you must
refresh the host in the Delphix Engine in order for it to detect your changes.
You can run the tests contained in the HostChecker individually, or all at once. You must run these tests on both the source and target hosts to
verify their configurations. As the tests run, you will either see validation messages that the test has completed successfully, or error messages
directing you to make changes to the host configuration.
The Oracle HostChecker is distributed as a set of Java files and executables. You can find these files and executables in 5 distinct tarballs, each
containing a different jdk corresponding to a particular platform (OS + processor). Together, these tarballs comprise the set of platforms supported
by Delphix. When validating Oracle hosts during a new deployment, it is important to download the appropriate tarball for the host you are
validating. Tarballs follow the naming convention "hostchecker_<OS>_<processor>.tar." For example, if you are validating a linux x86 host, you
should download the tarball named hostchecker_linux_x86.tar.
The Oracle HostChecker is also included in the Delphix Toolkit which is pushed to every environment managed by the Delphix Engine. It can be
found in /<toolkit-path>/<Delphix_COMMON>/client/hostchecker.

Prerequisites
Make sure your Oracle environment meets the requirements described in Requirements for Oracle Source Hosts and Databases and
Requirements for Oracle Target Hosts and Databases
At minimum, the hostchecker requires Java 6 to run. However, the Java 6 binaries are included in each of the platform specific
hostchecker tarballs and will be extracted if necessary.

Procedure
1. Download the appropriate HostChecker tarball for your platform from https://download.delphix.com/. Tarballs follow the naming
convention "hostchecker_<OS>_<processor>.tar". For example, if you are validating a linux x86 host you should download the
hostchecker_linux_x86.tar tarball.
2. Create a working directory and extract the HostChecker files from the HostChecker tarball.

mkdir dlpx-host-checker
cd dlpx-host-checker/
tar -xf hostchecker_linux_x86.tar
3. Run the sh script contained within:

sh hostchecker.sh
This will extract the JDK included in the tarball (if necessary) and invoke the hostchecker.

ora10205@bbdhcp:/home/ora10205/hostchecker-> sh hostchecker.sh
Installed version of Java (version: 1.4.2) is not compatible with the hostchecker.
Java version 1.6 or greater required.
Using the JDK from the included tarball (already extracted).

267

Delphix User Guide 2016 Delphix

Don't Run as Root

Do not run the HostChecker as root; this will cause misleading or incorrect results from many of the checks.

4. Select which checks you want to run.

Run Tests without the Interface
You can also run checks without spawning the interface. Enter --help to get a list of arguments you can pass to the
HostChecker.

5. Enter the requested arguments as the checks are made.

6. Read the output of the check.
The general format is that severity increases as you scroll down the output. First comes informational output, then warnings, then errors.
Internal Errors
If you see a message that starts with Internal Error, please forward it to Delphix Support immediately. This represents a
potential bug in the HostChecker, and not necessarily a problem with your environment.

7. Error or warning messages will explain any possible problems and how to address them. Resolve the issues that the HostChecker
describes. Don't be surprised or undo your work if more errors appear the next time you run HostChecker, because the error you just
fixed may have been masking other problems.
8. Repeat steps 3 - 7 until all the checks return no errors or warnings.

Non-Interactive Mode
The Java hostchecker can also be invoked in non-interactive mode. Each check is associated with a numeric flag; the association can be
displayed using the -help input flag. To run a particular check pass in the associated flag.

java -jar hostchecker.jar -help

usage: java -jar hostchecker.jar [OPTIONS]
-0
Check homedir permissions
-1
Check network port access
-10
Check toolkit path
-2
Check the Oracle CRS home
-3
Check the Oracle installation
-4
Check Oracle DB Instance
-5
Check the oratab file
-6
Check for ssh connectivity
-7
Check sshd_config for timeout configuration
-8
Check user sudo privileges
-9
Check sunrpc.tcp_slot_table_entries
-all
Execute all checks
-help
Print this message
-input <arg>
Input to hostchecker as a JSON string
In non-interactive mode, the input parameters necessary to run the checks must be passed to the hostchecker as a JSON string using the -input f
lag.

java -jar hostchecker.jar -0 -1 -10 -2 -3 -5 -6 -7 -8 -9 -input

'{"toolkitPath":"/work","applianceIP":"kfc-trunk.dcenter.delphix.com","sudoCredentials":{
"username":"ora10205","password":"ora10205"},"sshCredentials":{"username":"ora10205","pas
sword":"ora10205"},"port":"4000","source":true,"oracleCRSHome":"/work"}'
Tests Run
Test

Applicable
Platforms

Oracle
Source

Oracle
Target

Description

268

Delphix User Guide 2016 Delphix

Check Host
Secure Shell
(SSH)
Connectivity

All

Verifies that the environment is accessible via SSH

Check Tool Kit

Path

All

Verifies that the toolkit installation location is suitable for example, that it has the proper
ownership, permissions, and enough free space

Check Home
Directory
Permissions

All

Verifies that the host can be accessed via SSH using public key authentication. If you do
not need this feature, you can ignore the results of this check, or you can choose not to
run it.

Check Inventory
Access

All

Verifies that the current user has access to the Oracle inventory file

Check Oracle
Installation

All

Verifies basic information about the Oracle installation on the system, including that
various files are in expected locations, that they are formatted properly, and that they
have the correct permissions

Check ORATAB
File

All

Verifies that the oratab file is in an expected location and is formatted appropriately. You
only need to run this on source machines.

Check Oracle
DB Instance

All

Verifies more specific information both about the installation of oracle on the system and
about the various databases. Information includes not only file locations, formatting, and
permissions, but also the presence of DB listeners, database settings, oracle versions,
oracle user permissions, and more. You only need to run this on source machines.

Check Oracle
CRS Installation

All

Check OS User
Privileges

All

Check
SnapSync
Connectivity

All

Check
transmission
control protocol
(TCP) slot table
entries

Verifies settings related to Oracle CRS. You only need to run this on machines that have
CRS set up.

Verifies that the operating system user can execute certain commands with necessary
privileges via sudo. You only need to run this on target environments. See the topic Sudo
Privilege Requirements for more information.

Linux
RHEL
4.0-5.6

Verifies that the source host is able to connect to the Delphix Engine at port 8415 for
SnapSync
X

Check that the maximum number of (TCP) RPC requests that can be in flight is at least
128.

Checking Hosts Post-Deployment

The hostchecker is included in the Delphix toolkit directory on all machines that are added to Delphix and can be used to validate a host's
configuration at any time. To run the hostchecker simply invoke it using the java binary. Note that the JDK is also included in the Delphix toolkit
directory and can be used to run the hostchecker if no suitable version of java is installed on the host.

cd <Delphix Toolkit Directory>/Delphix_COMMON_<server-id>/client/hostchecker

/<Delphix Toolkit Directory>/Delphix_COMMON_<server-id>/java/jdk/bin/java -jar
hostchecker.jar

Related Links
Requirements for Oracle Source Hosts and Databases
Requirements for Oracle Target Hosts and Databases

269

Delphix User Guide 2016 Delphix

Adding an Oracle Single Instance or RAC Environment

This topic describes how to add a new Oracle or Oracle RAC environment.

Prerequisites
See the topics Requirements for Oracle Target Hosts and Databases and Supported Operating Systems and DBMS Versions for
Oracle Environments
There can be one Oracle unique database name (DB_UNIQUE_NAME) per Delphix Engine. For example, if you provision a VDB with a
database unique name "ABC" and later try to add an environment which has a source database that also has a database unique name of
"ABC", errors will occur.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the Plus icon next to Environments.
5. In the Add Environment dialog, select Unix/Linux.
6. Select Standalone Host or Oracle Cluster, depending on the type of environment you are adding.
7. For standalone Oracle environments enter the Host IP address.
8. For Oracle RAC environments, enter the Node Address and Cluster Home.
9. Enter an optional Name for the environment.
10. Enter the SSH port.
The default value is 22.
11. Enter a Username for the environment.
See Requirements for Oracle Target Hosts and Databases for more information on the required privileges for the environment user.
12. Select a Login Type.
For Password, enter the password associated with the user in Step 10.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

13. For Password Login, click Verify Credentials to test the username and password.
14. Enter a Toolkit Path.
The toolkit directory stores scripts used for Delphix Engine operations, and should have a persistent working directory rather than a
temporary one. The toolkit directory will have a separate sub-directory for each database instance. The toolkit path must have 0770
permissions and at least 345MB of free space.
15. Click OK.

Post-Requisites
After you create the environment, you can view information about it:
1. Click Manage.
2. Select Environments.
3.
270

Delphix User Guide 2016 Delphix

3. Select the environment name.

Related Links
Requirements for Oracle Target Hosts and Databases
Supported Operating Systems and DBMS Versions for Oracle Environments

271

Delphix User Guide 2016 Delphix

Adding a Database Installation Home to an Oracle Environment

This topic describes how to add a database installation home.
When you add an environment with the Delphix Admin application, all database installation homes on it are automatically discovered. However, if
a database installation home is not automatically discovered, you can add it manually to the environment.

Procedure
1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > Environments.>
3. Click Databases.
4. Click the green Plus icon next to Add Installation Home.
5. Enter the Installation Home.
6. Click the Check icon when finished.

Related Links
Adding a Database to an Oracle Environment

272

Delphix User Guide 2016 Delphix

Adding a Database to an Oracle Environment

Prerequisites
Procedure
Related Links
This topic describes adding a source database to an environment.
When you add an environment with the Delphix Admin application, all database instances that are running on it are automatically discovered.
However, if a database is not automatically discovered, you can add it manually to the environment.

Prerequisites
Make sure your source database meets the requirements described in Requirements for Oracle Source Hosts and Databases, as well
as general database user requirements as described in Requirements for Oracle Target Hosts and Databases.
Before adding a database, the installation home of the database must exist in the environment. If the installation home does not exist in
the environment, follow the steps in Adding a Database Installation Home to an Oracle Environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. Choose the installation home where the database is installed. Click the Up icon next to the the installation home path to show details if
needed.
6. Click the green Plus icon next to Add Databases.
7. Enter the Database Unique Name, Database Name, and Instance Name.
8. When finished, click the Check icon.

Related Links
Requirements for Oracle Source Hosts and Databases
Requirements for Oracle Target Hosts and Databases
Adding a Database Installation Home to an Oracle Environment

273

Delphix User Guide 2016 Delphix

Discovering Oracle Pluggable Databases in an Oracle Environment

When you add an environment with the Delphix Admin application, all Oracle database instances that are running on
it are automatically discovered. These include multitenant container database instances. However, pluggable
databases are not discovered. This topic describes how to discover Oracle pluggable database in the Oracle
environment.
Prerequisites
Make sure that the multitenant container database and its pluggable databases meet the requirements described in Requirements for
Oracle Source Environments and Databases.
Make sure that the multitenant container database is already discovered by the Delphix Engine. If the container database does not exist
in the environment, follow the steps in Adding a Database to an Oracle Environment.

Procedure
1. Login into the Delphix Admin application using Delphix Admin credentials
2. Select Manage > Environments.
3. Click Databases.
4. Choose the installation which has the multitenant container database and click the Up icon next to the the installation path to show
details.
5. Click "Discover CDB" next to the multitenant container database.
6. Enter the credentials for the multitenant container database and click the Check icon.
7. After pluggable databases are discovered, an Up button appears next the the container database. Click on it to see all discovered
pluggable databases.

Related Links
Requirements for Oracle Source Environments and Databases
Adding a Database to an Oracle Environment

Adding a Database Installation Home to an Oracle Environment

274

Delphix User Guide 2016 Delphix

Adding a Listener to an Oracle Environment

This topic describes how to add listeners for an Oracle environment.
When you add an environment with the Delphix Admin application, all listeners that are running on it are automatically discovered. However, if a
listener is not automatically discovered, you can add it manually to the environment.

Procedure
1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > Environments.
3. In the Environments panel, click on the name of an environment to view its basic information.
4. Next to Listeners, click the green Plus icon to add a Listener Service.
5. Enter a Name for the new Listener Service, and an IP address for its Endpoint.
6. Click the green Plus icon next to Add Endpoints to enter additional endpoints.
7. Click the Check icon to save your changes.

275

Delphix User Guide 2016 Delphix

Changing the Host Name or IP Address for Oracle Source and Target Environments
This topic describes how to change the host name or IP address for source and target environments, and for the Delphix Engine.
Procedure
For Source Environments
For VDB Target Environments
For the Delphix Engine

Procedure
For Source Environments
1. Disable the dSource as described in Enabling and Disabling SAP ASE dSources.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the dSource.

For VDB Target Environments

1. Disable the VDB as described in Enabling and Disabling SAP ASE VDBs.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the VDB.

For the Delphix Engine

1. Stop all running VDBs by clicking the red Stop button on the VDB card.
2. Disable all dSources as described in Enabling and Disabling SAP ASE dSources.
3. You can use either the command line interface or the Server Setup application to change the IP address of the Delphix Engine.
a. To use the command line interface, press F2 and follow the instructions described in Setting Up Network Access to the
Delphix Engine.
b. To use the Server Setup application, go to to System > Server Setup in the Delphix Admin interface, or click Server Setup in
the Delphix Engine login screen.
i. In the Network panel, click Modify.
ii. Under DNS Services, enter the new IP address.
iii. Click OK.
4. Refresh all Environments by clicking the blue/green Refresh symbol on the Environments screen.
5. Enable all dSources as described in Enabling and Disabling SAP ASE dSources.
6. Start all VDBs by clicking the Start button on the VDB card.

Using Custom init.ora or spfile.ora Files

If you are are using custom init.ora or sfpfile.ora files with your Oracle VDBs, you should use the Oracle command line
interface (sqlplus/srvctl) to shut down any active VDBs and copy the parameter files to a backup location. Complete the steps
above, then replace the files and re-start the VDB from the Oracle command line to restore your custom settings. See Customizing
VDB File Mappings for more information about customizing init.or and other configuration files.

276

Delphix User Guide 2016 Delphix

Editing Oracle Environment Attributes

This topic describes how to edit attributes of an environment such as name, host address, ssh port, or toolkit path, as well as descriptions of more
advanced attributes for specific data platforms.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials or as the owner of an environment.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of an environment to view its attributes.
5. Under Attributes, click the Pencil icon to edit an attribute.
6. Click the Check icon to save your edits.

Common Editable Attributes

Attribute

Description

Environment
Users

The users for that environment. These are the users who have permission to ssh into an environment, or access the
environment through the Delphix Connector. See the Requirements topics for specific data platforms for more information on
the environment user requirements.

Host
Address

The IP address for the environment host.

Notes

Any other information you want to add about the environment.

Oracle Attributes
Attribute

Description

Environment
Name (RAC)

The Environment Name field under Attributes is used to provide the name of the environment host in the case of cluster
environments. This field defaults to the IP address of the host unless you specify another name.

Cluster User
(RAC)

The user who has permission to access the cluster home.

Virtual IP
(RAC)

The IP address that will failover to another node in the cluster when a failure is detected. Click the green + to add another
virtual IP domain and IP address.

Listeners

The listener used to connect incoming client requests to the database. See Adding a Listener to an Oracle Environment fo
r more information.

SSH Port

The port used for secure shell connection to the host.

Toolkit Path

The directory used for storing Delphix toolkit files.

Under the Sho

w Details link

Remote Listener: a network name that resolves to an address or address list of Oracle Net remote listeners. Click the
green + to add a remote listener.
SCAN: Single Client Access Name that is used to allow clients to access cluster databases. Click the green + to add a
SCAN.
SCAN Listener: Listener used with SCAN to establish client connections to the database. Click the green + to add a
SCAN listener name and endpoints.

277

Delphix User Guide 2016 Delphix

Managing Oracle Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure

Prerequisites
Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

278

Delphix User Guide 2016 Delphix

Enabling Linking and Provisioning for Oracle Databases

This topic describes how to enable and disable staging, provisioning, and linking for databases.
Before you can use a database as a dSource, you must first make sure that you have defined a staging environment and enabled linking to it.
Similarly, before you can provision a virtual database (VDB) to a target database, you must make sure that you have enabled provisioning to
it.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. To enable or disable staging, slide the button next to Use as Staging to Yes or No.
6. To enable or disable provisioning, slide the button next to Allow Provisioning to On or Off.

279

Delphix User Guide 2016 Delphix

Deleting an Oracle Environment

This topic describes how to delete an environment.

Prerequisites
You cannot delete an environment that has any dependencies, such as dSources or virtual databases (VDBs). These must be deleted before you
can delete the environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, select the environment you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

280

Delphix User Guide 2016 Delphix

Refreshing an Oracle Environment

This topic describes how to refresh an environment.
After you make changes to an environment that you have already set up in the Delphix Admin application, such as installing a new database
home, creating a new database, or adding a new listener, you may need to refresh the environment to reflect these changes.
During environment discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the
toolkit are:
A JRE
Delphix jar files
The hostchecker utility
Scripts for managing the environment and/or VDBs
Delphix Connector log files
Delphix then executes some of these scripts to discover information about the objects in your environment (where the databases are installed,
the database names, information required to connect to these databases, etc.). In some environments (Windows in particular), the scripts are
customized to fit the customers environment.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of the environment to you want to refresh.
5. Click the Refresh icon.
To refresh all environments, click the Refresh icon next to Environments.

281

Delphix User Guide 2016 Delphix

Managing Oracle, Oracle RAC, and Oracle PDB Data Sources

These topics describe specific options and tasks for linking dSources from Oracle and Oracle RAC databases.
Linking an Oracle Data Source
Linking an Oracle Pluggable Database
Advanced Data Management Settings for Oracle dSources
Using Pre- and Post-Scripts with Oracle dSources
Enabling Validated Sync for Oracle
Linking dSources from an Encrypted Oracle Database
Linking Oracle Physical Standby Databases
Specifying External Data Directories for Oracle dSources and VDBs
Linking to Oracle dSources with RMAN Compression or Encryption Enabled
Upgrading dSources after an Oracle Upgrade
Enabling and Disabling Oracle dSources
Detaching and Re-Attaching Oracle dSources
Deleting an Oracle dSource
Provisioning from a Replicated Oracle dSource
Oracle dSource Icon Reference
Oracle Source Continuity
Oracle LiveSources
Oracle LiveSource User Workflows
Replication Prerequisites
Replication Verification
Performing Final Replication

282

Delphix User Guide 2016 Delphix

Linking an Oracle Data Source

This topic describes the process of linking to a source database and creating a dSource.
Prerequisites
Procedure
Related Links

Prerequisites
Make sure you have the correct user credentials for the source environment, as described in Requirements for Oracle Target Hosts
and Databases.
If you are linking a dSource to an Oracle or Oracle RAC physical standby database, you should read the topic Linking Oracle Physical
Standby Databases.
If you are using Oracle Enterprise Edition, you must have Block Change Tracking (BCT) enabled as described in Requirements for
Oracle Source Hosts and Databases.
The source database should be in ARCHIVELOG mode and the NOLOGGING option should be disabled as described in Requirements
for Oracle Source Hosts and Databases.
You may also want to read the topic Advanced Data Management Settings for Oracle dSources.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Select Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing Oracle Environment Users.

6. Enter your login credentials for the source database and click Verify Credentials.
If you are linking a mounted standby, click Advanced and enter non-SYS login credentials as well. Click Next. See the topics under Link
ing Oracle Physical Standby Databases for more information about how the Delphix Engine uses non-SYS login credentials.
7. In Add dSource/Add Environment wizard, the Toolkit Path can be set to /tmp (or any unused directory).
8. Select a Database Group for the dSource, and then click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. See the topics under Users, Permissions, and Policies for more information.
9. Select an Initial Load option.
By default, the initial load takes place upon completion of the linking process. Alternatively, you can set the initial load to take place
according to the SnapSync policy, for example if you want the initial load to take place when the source database is not in use, or after a
set of operations have taken place.
10. Select whether the data in the database is Masked.
This setting is a flag to the Delphix Engine that the database data is in a masked state. Selecting this option will not mask the data.
11. Select a SnapSync policy.
See Advanced Data Management Settings for Oracle dSources for more information.
12. Click Advanced to edit LogSync, Validated Sync, and Retention policies.
See Advanced Data Management Settings for Oracle dSources for more information.
13. Click Next.
14. Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card, and also make modifications to its policies

283

Delphix User Guide 2016 Delphix

and permissions. In the Databases panel, click on the Open icon to view the front of the dSource card. The card will then flip, showing
you information such as the Source Database and Data Management configuration. For more information, see Advanced Data
Management Settings for Oracle dSources .

Related Links
Advanced Data Management Settings for Oracle dSources
Requirements for Oracle Source Hosts and Databases
Requirements for Oracle Target Hosts and Databases
Linking dSources from an Encrypted Oracle Database
Linking Oracle Physical Standby Databases
Users, Permissions, and Policies
Managing Oracle Environment Users

284

Delphix User Guide 2016 Delphix

Linking an Oracle Pluggable Database

This topic describes how to link an Oracle 12c pluggable database to the Delphix Engine to create a dSource.

Prerequisites
Make sure the Delphix Engine has already discovered the multitenant container database and its pluggable databases. If the container
database does not exist in the environment, follow the steps in Adding a Database to an Oracle Environment. If the pluggable
database you want to link does not exist in the environment, follow the steps in Discovering Oracle Pluggable Databases in an Oracle
Environment.
You should have Block Change Tracking (BCT) enabled for the container database, as described in Requirements for Oracle Source
Hosts and Databases.
The container database should be in ARCHIVELOG mode and the NOLOGGING option should be disabled, as described in Requireme
nts for Oracle Source Hosts and Databases.

Procedure
1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > Databases > Add dSource.
Alternatively, on the Environment Management screen, you can click Add dSource next to the pluggable database name to start the
dSource creation process.
3. In the Add dSource wizard, select the source pluggable database.
If the container database is shown but the pluggable database is not, select the container database, enter its database
credentials, and click Verify Credentials. The Delphix Engine will discover and list all pluggable databases in the container
database. Select the pluggable database from the list.

4. Enter your login credentials for the source database and click Verify Credentials.
5. Click Next.
6. Select a Database Group for the dSource.
7. Click Next.
8. Select an Initial Load option.
By default, the initial load takes place upon completion of the linking process. Alternatively, you can set the initial load to take place
according to the SnapSync policy. For example, you can set the initial load to take place when the source database is not in use, or after
a set of operations have taken place.
9. Select a SnapSync policy.
See Advanced Data Management Settings for Oracle dSources for more information.
10. Click Advanced to edit Oracle Sync Options Settings and Retention policies.
See Advanced Data Management Settings for Oracle dSources for more information.
11. Click Next.
12. Review the dSource Configuration and Data Management information.
13. Click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the database icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.
Link/Sync of the Multitenant Container Database
The DB_Link job will also link the pluggable database's multitenant container database if it has not been linked yet.
You can also initiate a DB_Sync job for the container database.

Related Links
Adding a Database to an Oracle Environment
Discovering Oracle Pluggable Databases in an Oracle Environment
Requirements for Oracle Source Hosts and Databases

285

Delphix User Guide 2016 Delphix

Advanced Data Management Settings for Oracle dSources

286

Delphix User Guide 2016 Delphix

Advanced Data Management Settings for Oracle dSources

Accessing Data Management Settings
During the dSource linking process
On the back of the dSource card
In the top menu bar
Retention Policies
Benefits of Longer Retention
Oracle Initial Load Options
Oracle SnapSync Policy Settings
Oracle LogSync Policy Settings
Oracle Validated Sync Settings
Oracle Sync Options Settings
This topic describes advanced data management settings for dSources.
When linking a dSource, you can use custom data management settings to improve overall performance and match the needs of your specific
server and data environment. If no specific settings are required, leverage default data management settings.

Accessing Data Management Settings

There are three ways to set or modify data management settings for dSources:
During the dSource linking process

1. In the Data Management panel of the Add dSource wizard, click Advanced.
On the back of the dSource card

1. Under Data Management, click the field next to Retention Policy

2. Click the Edit icon.
3. For SnapSync and Retention policies, click the policy name. This will open the Policy Management screen.
In the top menu bar

1. Click Manage.
2. Select Policies. This will open the Policy Management screen.
3. Select the policy for the dSource you want to modify.
4. Click Modify.
For more information, see Creating Custom Policies and Creating Policy Templates.

Retention Policies
Retention policies define the length of time that the Delphix Engine retains snapshots and log files to which you can rewind or provision objects
from past points in time. The retention time for snapshots must be equal to, or longer than, the retention time for logs.
To support longer retention times, you may need to allocate more storage to the Delphix Engine. The retention policy in combination with the
SnapSync policy can have a significant impact on the performance and storage consumption of the Delphix Engine.

Benefits of Longer Retention

With increased retention time for snapshots and logs, you allow a longer (older) rollback period for your data.
Common use cases for longer retention include:
SOX compliance
Frequent application changes and development
Caution and controlled progression of data
Reduction of project risk
Speed of rollback / restore to older points in time

287

Delphix User Guide 2016 Delphix

With LogSync enabled, you can customize both the retention policy and the SnapSync policy to access logs for longer periods of time, enabling
point-in-time rollback and provisioning.

Oracle Initial Load Options

Select whether you want the initial load to take place immediately, or according to the SnapSync schedule. Set Masked, select Yes or No to
indicate whether the sourcedata is already masked.

Oracle SnapSync Policy Settings

The SnapSync policy determines how often snapshots are taken of the source database. In the Default SnapSync policy, a snapshot is taken
daily at 3:30 AM local time, and will time-out after four hours. If SnapSync does not complete within this four hour period, it will resume at the next
scheduled daily time, until the process is complete. Click the Edit icon to change the Default SnapSync policy, or click the Add icon to create a
new SnapSync policy. See Creating Policy Templates for more information.

Oracle LogSync Policy Settings

Enabled - LogSync fetches log files from the source database, enabling the ability to provision a VDB from a specific point in
time or, a database change number (SCN in the case of Oracle databases. LogSync must be enabled for this provisioning
functionality to work. LogSync is disabled if the source database is detected to be mounted but not open.
Archive Only, Archive and Online Redo - these settings determine whether LogSync fetches logs from archive storage in the
source database file system, or both the file system and online redo logs. Setting Archive Only permits the use of LogSync with
raw devices or Oracle Automatic Storage Management devices. If LogSync detects that online redo logs reside on a raw device
or ASM storage then it will automaticallyenter into Archive Only mode, regardless of the mode that was chosen.
LogSync for Oracle Standby Databases
LogSync must be enabled for Oracle physical standby databases in Level Backup mode and using Real Time Apply. See Linking
Oracle Physical Standby Databases.

LogSync for Oracle Pluggable Databases

LogSync policy settings for Oracle pluggable databases must be set at their corresponding container databases.

Oracle Validated Sync Settings

Oracle validated sync is disabled by default. When enabled, validated sync is performed immediately after every subsequent SnapSync. See Ena
bling Validated Sync for Oracle for more information.

Oracle Sync Options Settings

Compression - enable compression of backup data sent over the network. Default is Enabled.
Bandwidth Limit - select the network bandwidth limit in units of MB/s between Source and Delphix Engine. Default is 0, or no
bandwidth limit enforced.
Number of Connections - select the number of TCP connections to use between Source and Delphix Engine.
Multiple connections may improve network throughput especially over long distance and highly congested networks. Default is 1.
Encrypted Linking - turn on encryption between Source and Delphix Engine. Default is Disabled.
Data Load Channels
The channel settings determine the number of channels and data files per backup set. While these settings can be increased,
you should consider potential adverse effects on the performance of database operations on the Source server.
Number of Channels - set the number of RMAN channels used during SnapSync. Default is 2.
Files per Channel - maximum number of data files in a backup set.
The product of files-per-channel and channels determines the maximum number of data files concurrently backed up by
RMAN. Default is 5.
Block Checking - enable logical block validation by RMAN. Checking is CPU intensive and will slow down SnapSync. Default is
Disabled.
Level Backup - enable LEVEL backup mode.
LEVEL backups should only be used to workaround Oracle bug 10146187 on physical standby sources. Switching from SCN to
LEVEL mode will force a LEVEL 0 backup. See Linking Oracle Physical Standby Databases for more information. Default is
Disabled or SCN Backup mode.

288

Delphix User Guide 2016 Delphix

Using Pre- and Post-Scripts with Oracle dSources

Contexts for Oracle Pre- and Post-Scripts
Specifying Arguments for Oracle and Scripts
An Example with Three Arguments
An Example with an Apostrophe
This topic describes the use of pre- and post-scripts with dSources.
For each script, you can add the script path and its arguments when linking a dSource in one of two ways. Either:
During the Add dSource wizard process, in the Data Management screen, click Advanced.
or
On the back of the dSource card, click the Pencil icon next to the Pre Script and Post Script fields.
To update pre- and post-script information:
1. Flip over the dSource card.
2. Click on the Pencil icon next to the Pre Script and Post Script fields.
3. When finished, click the check mark icon.
Note that pre-scripts are executed before the SnapSync policy, and if the script fails, SnapSync will fail as well. In the case of a post-script, the
script will execute after SnapSync is complete. If a post-script fails, you will see an error message.

Contexts for Oracle Pre- and Post-Scripts

For Oracle dSources, each time that the SnapSync policy for a dSource executes, a pre- or post-script can be run as part of the process.
For Oracle single instance environments, pre- and post-scripts must exist and be readable on the source environment for SnapSync.
For clustered environments (for example, Oracle RAC), scripts must exist and be readable on all nodes. This allows the Delphix Engine
to read the scripts even if cluster nodes are down.
Allowed Script Type for Oracle
For Oracle, dSource scripts must be text scripts only.

Specifying Arguments for Oracle and Scripts

You can specify multiple arguments for a script. In the Pre or Post Script field, enter the path to the script, and then list the arguments. If the
argument contains spaces, enclose it in single or double quotes. You can escape single quotes within the argument with a backslash.

An Example with Three Arguments

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh one "second argument in double
quotes" 'third argument in single quotes'
An Example with an Apostrophe
/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh 'I\'d rather be in Hawaii.'

289

Delphix User Guide 2016 Delphix

Enabling Validated Sync for Oracle

This topic describes the validated sync process for Oracle databases using both the Delphix Engine Graphic User Interface (GUI) and Command
Line Interface (CLI)
Traditional Oracle dSource snapshots require some recovery during provisioning. By configuring validated sync for Oracle, the Delphix Engine will
select a compatible Oracle installation and apply the recovery necessary to provision a snapshot immediately after each SnapSync. Snapshots
that have been through this validated sync process step do not require recovery during provisioning.
The Delphix Engine may be unable to perform validated sync on a physical standby database in Real Time Apply mode. This is
because the standby may apply changes before copying the logs that contain those changes. Without the logs necessary to perform
recovery, validated sync cannot be executed. However, you can still provision the snapshot when the archive logs become available on
the standby.

Prerequisite - Designating a Staging Host

In order to validate an Oracle dSource snapshot after a sync, the Delphix Engine requires a host with an Oracle installation that is compatible with
the dSource. This machine is known as the staging host. You must explicitly designate which machines you want the Delphix Engine to use as
staging hosts. All machines that have been marked as staging hosts are added to a pool. During sync validation, the Delphix Engine will select a
compatible host from the pool, export the requisite archived redo logs and datafiles, and execute Oracle media recovery on the host. Follow these
steps to designate a staging host.
1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > Environments.
3. In the Environments panel, select the environment you want to designate as staging.
4. Next to Environment Details, select Databases.
5. Scroll down to the installations you want to designate as staging and slide the Use as Staging control to Yes.
To configure validated sync for multiple dSources with different Oracle versions, you must designate a compatible staging source for each. If
multiple compatible staging sites exist, the Delphix Engine will select one at random.
The validated sync process will consume some resources on the staging host when snapshots are taken. Designating a performance
critical host as a staging host is not recommended.

The default OS user for the staging host must have access to the Oracle installation that will be used to perform recovery during
validated sync.

Oracle Pluggable Database

Validated sync for Oracle pluggable databases is not supported in this release.

Procedure - Enabling Validated Sync

Oracle validated sync can be enabled at link time or on any existing dSource.
1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > Databases > My Databases.
3. In the Databases panel, select the dSource for which you want to enable sync validation.
4. Move the slider control for Sync Validation from Disabled to Enabled.

Video

Related Links
CLI Cookbook: Enabling Oracle Validated Sync

290

Delphix User Guide 2016 Delphix

Linking dSources from an Encrypted Oracle Database

This topic describes the behavior of the Delphix Engine when linking to a dSource based on an encrypted Oracle database.
Beginning with version 10gR2, Oracle supports the encryption of permanent tablespaces using Transparent Data Encryption (TDE). You can link
dSources from databases using TDE by following the basic procedure described in Linking an Oracle Data Source. However, in order to
provision a VDB from a dSource that is linked to an encrypted database, you must copy wallet files from the physical database in the source
environment to the target environment. See Provisioning a VDB from an Encrypted Oracle Database for more information.

Related Links
Linking an Oracle Data Source
Provisioning a VDB from an Encrypted Oracle Database

291

Delphix User Guide 2016 Delphix

Linking Oracle Physical Standby Databases

This topic describes special considerations for linking Oracle Physical Standby databases.
The Delphix Engine supports linking both Physical (redo apply) and Logical (SQL apply) Standby databases.
Using Block Change Tracking (BCT) on a Physical Standby Database
Delphix recommends enabling Block Change Tracking (BCT) on a Primary or Standby source database.
See Physical Standby Database Support Matrix in this topic for restrictions on enabling BCT on a standby database.
BCT for primary databases is stable and recommended since version 10.2.0.5.
BCT for physical standby databases isavailable since version 11.1.0.6, however it requires an Active Data Guard license.
Release 11.1.0.6: BCT on physical standby is unstable.
Release 11.1.0.7: BCT requires a patch for Oracle bug 7613481
Release 11.2.0.2: BCT requires patches for Oracle bugs 10170431, 12312133
Release 11.2.0.3: BCT requires patches for Oracle bugs 12312133, 16052165
Patches Required
Enabling BCT on a physical standby database without these patches is not recommended due to serious performance and
stability issues.

Physical Standby Database Support Matrix

Oracle Version

Apply
Mode

Notes

10.2.0.x, 11.2.0.4,
12.x in
SCN Backup Mode

Archive
Apply
mode

No special restrictions.

Real
Time
Apply
mode

LogSync must be enabled (default).

Archive
Apply
mode

Due to Oracle bug 10146187, redo apply must be stopped and the database opened in read-only mode
during SnapSync.
See the section on Stopping and Restarting Redo Apply.

Real
Time
Apply
mode

LogSync must be enabled (default).

11.1.0.x, 11.2.0.2,
11.2.0.3 in SCN
Backup Mode

Due to Oracle bug 10146187, redo apply must be stopped and the database opened in read-only mode
during SnapSync.
See the section on Stopping and Restarting Redo Apply.
Due to Oracle Bug 13075226, which results in a hang during the restart of Redo Apply, BCT must be
disabled on the standby database.
Both Oracle bug 10146187 and 13075226 are fixed starting from Oracle 11.2.0.4. There is no need to
configure stop and restart of Redo Apply or disable BCT if the Physical Standby Database is at version
11.2.0.4 or above.

11.1.0.x, 11.2.0.2,
11.2.0.3 in
Level Backup Mode

Archive
Apply
mode

No special restrictions.
But see the section on Mandatory Requirements for Using Level Backup Mode.

Real
Time
Apply
mode

LogSync must be enabled (default).

But see the section on Mandatory Requirements for Using Level Backup Mode.

Using Level Backup Mode for Physical Standby Sources

SnapSync defaults to SCN Backup mode. This is the ideal mode because it ensures that Delphix backups do not interfere with production

292

Delphix User Guide 2016 Delphix

backup streams.
However, SCN Backup mode requires stopping/restarting redo apply for Physical Standbys on Oracle versions 11.1.0.x, 11.2.0.2, 11.2.0.3
because of Oracle bug 10146187 listed in the support matrix. For these specific Oracle versions, using Level Backup mode is a better option
provided the requirements below are satisfied.

Mandatory Requirements for Using Level Backup Mode

No use of RMAN for backups on the Physical Standby database
OR ALL of the following conditions must be true
1. Oracle 11.2.0.2 or later version
2. All RMAN backups must use tags
3. RMAN CROSSCHECK commands must specify tags
4. RMAN DELETE commands must specify tags
5. RMAN DUPLICATE commands must specify tags
6. Set CONTROL_FILE_KEEP_TIME to 365

Failure to meet all of these requirements will cause external RMAN backups to be incomplete or result in corrupt SnapSync snapshots.
Switching from SCN to LEVEL mode will force a new LEVEL 0 backup.

Stopping and Restarting Redo Apply

Oracle bug 10146187 requires stopping of redo apply before an SCN-based incremental backup can be issued. These scripts can be used as
pre- and post-scripts during the dSource linking process to stop and restart Redo Apply. See Using Pre- and Post-Scripts with Oracle
dSources for more information about scripts.
SnapSync pre-script: stopStandbyApply.sh.template
SnapSync post-script: startStandbyApply.sh.template
These scripts must be modified for local use, particularly in regard to whether the physical standby database operates in MOUNTED or OPEN
mode.
Failure to properly customize these scripts could violate your Oracle license terms by running redo apply on an open database, which
requires an Oracle Active Data Guard license.

Linking and Provisioning a Mounted Standby

For databases that are in the mounted state, the Delphix database user account must be SYS (having the SYSDBA role), SYSBACKUP (having
the SYSBACKUP role) or SYSDG (having the SYSDG role). However, for an open standby (Active Data Guard) database, only a regular
database user account is required.
Connecting to a mounted standby with a SYS user account requires that the mounted standby be configured with a password file. Delphix does
not capture the password file during SnapSync, and for this reason cannot provision or sync validate a database with a SYS user. A secondary,
regular database user account can be specified through either the Delphix Admin application or CLI. This database user will then be used to
connect to the database during provisioning and validated sync. Note that the SYS user is still required to perform snapshots of the source
database.
In the Delphix Admin application, the non-SYS user can be specified from within the Add dSource wizard, or on the back of the Oracle dSource
Card after linking.

Setting the Non-Sys User on the Oracle dSource Card

1.

Create the delphix_db user in the primary database.

2.

Log into the Delphix Admin application using delphix_admin credentials.

3.

In the Manage menu, select Databases > My Databases.

4.

Select the Oracle dSource for which you want to add a non-SYS user.

5.

Click the dSource's Expand icon to open the dSource card, then click the Flip icon on the card to view the
back.

6.
293

Delphix User Guide 2016 Delphix

6.

Click the Edit button next to Non-SYS User.

7. Enter a non-SYS user and credentials that exist on the standby.

8. Click the Accept button to save this user and associated credentials.
The non-SYS user will be used to connect to all VDBs provisioned from snapshots of this dSource that are created after the non-Sys user has
been set.

Setting the Non-Sys User with the Command Line Interface

SYSBACKUP and SYSDG roles are only available in Oracle 12.1 and later releases.

1. Select the source config of the mounted standby.

delphix> sourceconfig select pomme

2. Execute the update command.

delphix sourceconfig "pomme"> update

3. Set the nonSysUser and nonSysCredentials to a non-SYS user that exists on the standby.

delphix sourceconfig "pomme" update *> set nonSysUser=<non-sys-username>

delphix sourceconfig "pomme" update *> set nonSysCredentials.type=PasswordCredential
delphix sourceconfig "pomme" update *> set
nonSysCredentials.password=<non-sys-password>
4. Commit the operation.

delphix sourceconfig "pomme" update *> commit

Related Links
Linking an Oracle Data Source
Advanced Data Management Settings for Oracle dSources
Using Pre- and Post-Scripts with Oracle dSources

294

Delphix User Guide 2016 Delphix

Specifying External Data Directories for Oracle dSources and VDBs

This topic describes the process for including external data files with dSource snapshots and VDBs.
In the Advanced section of the Data Management screen during the dSource linking process, and on the back of the dSource card after its
created, you can specify the directory for any external data files that should be included with the dSource snapshots.

External File Import for the Delphix Engine and VDBs

The Delphix Engine will not fetch external tables or external data types such as BFILE. Instead, in order to link external data files to the source
database and make it available to the Delphix Engine, you must create a directory in the file system and the database. Any data files in the
directory you specify will be applied, recursively, to the dSource.
External data will be provisioned to each VDB that is created from this dSource. You will need to update the external file/data type definition to
point to the new location after creating VDBs. Provisioning a VDB with external data creates a directory named external in the VDB mount point
location.

Configuring the rsync Command Location for an Environment

Files from the external data directory are fetched using the rsync command installed in the source environment. In order to SnapSync a dSource
with an external data directory, rsync must be installed in the source environment. If rsync is installed in a non-standard location, the path to the
rsync command can be configured in the Environment Details for the source environment on the Environment Management screen.

Example of Attaching and Redirecting External Data Files for Oracle Databases
This example uses two environments:
1. 172.16.200.446 as the source environment
dinosaur as the source database
2. 172.16.200.447 as the target environment
vdino as the target database

Linking a dSource
1. Create an external data directory and an external data file, and attach the directory to the source database.
a. Log into 172.16.200.446 as the environment user.
b. Create a physical directory on the source environment.
$ mkdir /work/extdata
c. Create a directory in Oracle.

$ sqlplus / as sysdba
SQL> create or replace directory extdata as '/work/extdata';
d. Create a text file /work/extdata/exttab.dat.

$ cat > /work/extdata/exttab.dat

1, aaa
2, bbb
3, ccc
^C
e. Create an external table exttab.

$ sqlplus / as sysdba
SQL> create table exttab (id number, text varchar2(10))
2 organization external (default directory extdata
location('exttab.dat'));
f. Query the table.

295

f.

Delphix User Guide 2016 Delphix

SQL> select * from exttab;

ID TEXT
---------- ---------1 aaa
2 bbb
3 ccc
2. During the process of linking the dSource to the Dinosaur database, or on the back of the dSource card after creating the link, enter /wo
rk/extdata in the External Data Directory field.

Provisioning a VDB
1. Provision vdino from Dinosaur.
2. Modify the directory extdata in vdino
a. Log into the target environment 172.16.200.447
b. Set SID to vdino

$ export ORACLE_SID=vdino
c. A query to exttabwill fail.

$ sqlplus / as sysdba
SQL> select * from exttab
select * from exttab
*
ERROR at line 1:
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-04063: unable to open log file EXTTAB_23394.log
OS error No such file or directory
ORA-06512: at "SYS.ORACLE_LOADER", line 19
3. Modify directory to the new location.

SQL> create or replace directory extdata as '/mnt/provision/vdino/external';

4. Query exttabagain.

SQL> select * from exttab;

ID TEXT
---------- ---------1 aaa
2 bbb
3 ccc

Related Links
Linking an Oracle Data Source
Provisioning an Oracle VDB

296

Delphix User Guide 2016 Delphix

Linking to Oracle dSources with RMAN Compression or Encryption Enabled

This topic describes the behavior of the Delphix Engine when linking to a dSource with RMAN compression or encryption enabled.
In earlier versions of the Delphix Engine, the dSource linking process would fail if RMAN compression or encryption was enabled. In order for the
linking process to complete, the administrator was required to ensure that compression was not enabled for device type SBT_TAPE, and that
encryption was also not enabled.
Beginning with Delphix Engine version 2.7, linking a dSource will succeed if compression or encryption is enabled, but the RMAN backup that
creates the dSource will not be compressed or encrypted. This is true in the case where the administrator has enabled compression for tape, and
in the case where the administrator is using OSB and has enabled encryption for tape.
You can check the RMAN compression and encryption settings with the commands show device type and show encryption for
database, respectively.

Related Links
Linking an Oracle Data Source

297

Delphix User Guide 2016 Delphix

Upgrading dSources after an Oracle Upgrade

This topic describes how to upgrade dSources after an Oracle database upgrade.

Prerequisites
Do not suspend LogSync on the Delphix Engine during an Oracle upgrade of the source environment. LogSync will detect the Oracle version
change, and automatically update this information on the Delphix Engine for all the associated dSources and VDBs. Follow all Oracle instructions
and documentation.

Procedure
There are 2 ways to apply a PSU (Patch Set Update)/Oracle upgrade:
A) Apply to existing ORACLE_HOME. (best if on Delphix v4.1.x or higher.)
B) Create new ORACLE_HOME (could clone existing one) and then apply the PSU to the new ORACLE_HOME.
For a dSource using option A:
1) Follow Oracle documentation, patch the ORALCE_HOME and the database.
2) Refresh the Environment in the GUI.
For a dSource using option B:
1) Refresh the Environment from the Delphix GUI and verify that the new ORACLE_HOME is picked up and in the databases tab as an ORACLE
Installation.
2) Follow all Oracle documentation, patch the production database etc.
3) Go to the Delphix GUI flip the dSource card over and use the Upgrade Icon on the bottom to switch the ORACLE_INSTALLATION to the new
(verified in step 1).

Updating the Oracle User after an Upgrade

There may be cases when you upgrade the Oracle home and the Oracle User (who owns the binary) is a different user than the
previous Oracle User. You will then need to update the Oracle User for each environment, and then re-connect each dSource and VDB
to the upgraded Oracle home using the new Oracle User.
The new Oracle User must be in the same OS group (for example, dba or oinstall) as the previous one.
1. Log into the Delphix Admin application using delphix_admin credentials.
2. Select Manage > Environments.
3. Select the environment where you want to add the user.
4. Next to Environment Users, click the Pencil icon to add the new user.
5. Set the new user as the default user.
6. Follow the procedure to upgrade the dSources and VDBs described in this topic.

298

Delphix User Guide 2016 Delphix

Enabling and Disabling Oracle dSources

This topic describes how to enable and disable dSources for operations such as backup and restore.
For certain processes, such as backing up and restoring the source database, you may want to temporarily disable your dSource. Disabling a
dSource turns off communication between the dSource and the source database, but does not tear down the configuration that enables
communication and data updating to take place. When a disabled dSource is later enabled, it will resume communication and incremental data
updates from the source database according to the original policies and data management configurations that you set.
Disabling a dSource is also a prerequisite for several other operations, like database migration and upgrading the dSource after upgrade of the
associated data source.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the dSource you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the dSource again, move the slider control from Disabled to Enabled, and the dSource will continue to function as
it did previously.

299

Delphix User Guide 2016 Delphix

Detaching and Re-Attaching Oracle dSources

Detaching a dSource
Attaching a dSource
This topic describes how to detach dSources and re-attach them to a different source database.
Each dSource contains an association with the source database, as well as the data it has pulled from the source database up to that point. It is
possible to detach, or unlink, a dSource from its source database. This breaks the association with the source database without affecting the data
within the Delphix Engine. Detached dSources and their source databases have these properties:
You can use detached dSources as the source of virtual database (VDB) provisioning operations.
You can re-link the source database as a different dSource.

Detaching a dSource
1. Login to the Delphix Admin application as a user with OWNER privileges on the dSource, group, or domain.
2. Click Manage.
3. Select My Databases.
4. Select the database you want to unlink or delete.
5. Click the Unlink icon.
A warning message will appear.
6. Click Yes to confirm.

Attaching a dSource
Rebuilding Source Databases and Using VDBs
In situations where you want to rebuild a source database, you will need to detach the original dSource and create a new one
from the rebuilt data source. However, you can still provision VDBs from the detached dSource.
1. Detach the dSource as described above.
2. Rename the detached dSource by clicking the Edit icon in the upper left-hand corner of the dSource card, next to its
name.
This is necessary only if you intend give the new dSource the same name as the original one. Otherwise, you will see
an error message.
3. Create the new dSource from the rebuilt database.
You will now be able to provision VDBs from both the detached dSource and the newly created one, but the detached dSource
will only represent the state of the source database prior to being detached.

The attach operation is currently only supported from the command line interface (CLI). Full GUI support will be added in a future release. Only
databases that represent the same physical database can be re-attached
1. Login to the Delphix CLI as a user with OWNER privileges on the dSource, group, or domain.
2. Select the dSource by name using database select <dSource>.
3. Run the attachSource command.
4. Set the source config to which you want to attach using set source.config=<newSource>. Source configs are named by their
database unique name.
5. Set any other source configuration operations as you would for a normal link operation.
6. Run the commit command.

Backup Mode for Attaching Oracle dSources

For Oracle dSources, the SnapSync backup option should be set to SCN Backup mode. Level Backup mode is based on information
stored in the the database control file. If the control file of the newly attached database does not contain information about the previous
backups, an initial backup will be created. In addition, Block Change Tracking will not be in sync, and the next SnapSync will need to
read the entire database to determine which blocks have changed. See Advanced Data Management Settings for Oracle dSources f
or more information about Backup Mode.

300

Delphix User Guide 2016 Delphix

Deleting an Oracle dSource

Prerequisites
Procedure
This topic describes how to delete a dSource.

Prerequisites
You cannot delete a dSource that has dependent virtual databases (VDBs). Before deleting a dSource, make sure that you have deleted all
dependent VDBs as described in Deleting a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the Databases panel, select the dSource you want to delete.
6. Click the Trash Can icon.
7. Click Yes to confirm.

Deleting a dSource will also delete all snapshots, logs, and descendant VDB Refresh policies for that database. You cannot
undo the deletion.

301

Delphix User Guide 2016 Delphix

Provisioning from a Replicated Oracle dSource

This topic describes how to provision from a replicated dSource or virtual database (VDB). The process for provisioning from replicated objects is
the same as the typical VDB provisioning process, except that first you need to select the replica containing the replicated object.
Prerequisites
Procedure
Post-Requisites

Prerequisites
You must have replicated a dSource or a VDB to the target host, as described in Replication Overview.
You must have added a compatible target environment on the target host.

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB you want to provision.
6. The provisioning process is now identical to the process for provisioning standard objects.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

302

Delphix User Guide 2016 Delphix

Oracle dSource Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

303

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

304

Delphix User Guide 2016 Delphix

Oracle Source Continuity

Oracle Source Continuity Overview
In earlier versions of the Delphix Engine, when an Oracle database underwent a resetlogs operation, the user was required to re-link the Oracle
source. This meant that the Oracle database had to be completely backed up and stored again on the Delphix Engine. If any VDBs were
provisioned from the dSource and needed to be saved, the old dSource had to be renamed and saved, resulting in a possible doubling of storage
space consumed on the Delphix Engine. The old virtual databases (VDBs) could not be refreshed to the relinked dSource. Beginning with Delphix
Engine version 4.1.1.0/4.0.6.0, the Oracle database no longer requires you to re-link sources after a resetlogs operation. The Delphix Engine will
detect this condition, automatically take a new full backup, and create a new timeflow for the next SnapSync of the source . Benefits

of the

Oracle source continuity feature include:

Lower storage costs and easier administration.
Only the changed blocks of the new SnapSync backup will be stored on the Delphix Engine. Because of the way the Delphix
Engine handles duplicate blocks, the full backup is likely have a storage requirement similar to an incremental backup.
Existing VDBs provisioned from previous snapshots for the source will remain.

You can use and refresh those VDBs to the new snapshot.
The improved user workflow replaces the old user workflow, which directed users to troubleshoot when SnapSync would fail. Begin Oracle Source
Continuity in the following way:
1. The database undergoes a resetlogs operation.
2. If LogSync is enabled, it generates a fault and stops.
3. Start SnapSync. The SnapSync does a full restore of the database to a new timeflow, clears the fault, and restarts LogSync. If you
created VDBs prior to the resetlogs operation, they will still exist after the SnapSync; you can refresh them from the new snapshot.

Creating a New Timeflow

When LogSync detects the resetlogs operation, it will still stop and generate a fault.

LogSync must stop, because a new timeline has

been created on the database. This usually happens because the database has been rewound to a past point. The
transaction logs being generated on the new timeline are out of sync and conflict with logs from the old timeline. The
data files are also out of sync with the data files on the Delphix Engine. You must create a corresponding new
timeflow on the Delphix Engine to store the new logs and new versions of the data files. This requires taking a new
backup of the database. The following screenshot shows an example of a fault from a resetlogs operation being
detected. Note the fault and that LogSync is inactive.

Version 4.2.0

Once LogSync detects the resetlogs operation and throws the fault, no more changes will be be retrieved from the
database until you start a new SnapSync. This SnapSync will take a full backup, clear the fault, and restart
LogSync. Only the new snapshot and timeflow will be visible in the dSource TimeFlow view in the graphical user

305

Delphix User Guide 2016 Delphix

interface (GUI). Previous snapshots and timeflow will still exist and be visible through the command line interface
(CLI) and the Capacity Timeflow view of the GUI. The following screenshot shows the same Delphix Engine after a
SnapSync has been performed. Note that the fault has been cleared, LogSync is now active, and only the new
snapshot is visible in the GUI.

Version 4.2.0
The following CLI output shows that the old and new timeflow and snapshots are still available. The name of the original timeflow for the database
is "default." The name of the new timeflow that was created during the SnapSync is "CLONE@2015-01-15T17:07:20."
delphix> /timeflow list display=name,container
NAME

CONTAINER

'CLONE@2015-01-15T17:07:20'

dbdhcp1

default

dbdhcp1

delphix> /snapshot list display=name,container,timeflow

NAME

CONTAINER

TIMEFLOW

'@2015-01-16T00:50:08.784Z'

dbdhcp1

default

'@2015-01-16T00:52:13.685Z'

dbdhcp1

default

'@2015-01-16T00:53:46.873Z'

dbdhcp1

default

'@2015-01-16T00:55:18.079Z'

dbdhcp1

default

'@2015-01-16T01:08:02.411Z'

dbdhcp1

'CLONE@2015-01-15T17:07:20'

The old snapshots and timeflow will still be subject to logfile and snapshot retention policies. You can also delete the snapshots manually. In
addition, you can use the CLI to provision from the old timeflow.

306

Delphix User Guide 2016 Delphix

Oracle LiveSources
Oracle LiveSources Overview
Understanding Oracle LiveSources
Understanding How to Use Oracle LiveSources
Oracle LiveSources Quickly Sync with Consistent Snapshots
Oracle LiveSources Use Resync and Apply
LiveSource Resync is a two-step operation consisting of:
Pre-requisites: Configuration and Installation of Staging Environments To Host a Standby Database
Related Links

Oracle LiveSources Overview

Prior to Delphix Engine version 4.2, users ran reports against virtual databases (VDBs) that they created with the Delphix Engine. Although this
workflow helped them offload the reporting load from production, the data in the VDBs was not updated asynchronously. If users wanted newer
data, they had to stop their reporting applications, refresh their VDBs, and resume. In the current release, you can run reports against data that is
constantly being updated. There is one live data feed per source database that is linked as a dSource on the Delphix Engine. You can point your
reporting applications to this live feed. Additionally, you will continue to have all existing Delphix functionality from the dSource, such as creating
read/write VDBs.

Understanding Oracle LiveSources

Oracle LiveSources leverage native Oracle Active Data Guard technology to keep a standby database up-to-date with changes happening on the
source. The standby database is kept open for reads while it applies changes from the source. You can now connect to this standby database for
real-time reporting needs. Using Delphix in conjunction with Active Data Guard gives you the ability to get both live up-to-date data and historical
points in time from which you can provision virtual databases.

Understanding How to Use Oracle LiveSources

Oracle LiveSources Provide a Read-Only Live Data Stream from Delphix
You can convert an Oracle dSource to a LiveSource, which is a real-time read-only feed of the linked source. You can access the LiveSource
using a JDBC string. Internally, a LiveSource is a standby database instance tracking the Linked Source in real time managed mode and opened
in read-only mode.
Understanding Oracle LiveSources with Data Age and Threshold
One of the important utilities of a LiveSource is that it provides a real-time feed of the linked Source. In some instances, due to slow networks or
other reasons, the LiveSource might fall behind the Linked Source it is tracking. When adding a LiveSource the user can specify a data age
threshold. If the LiveSource falls behind the linked source by more than the data age threshold, a fault will be generated and you will be informed.

The Data Age of the LiveSource is displayed on the LiveSource timeflow. A spinning gear, as seen below, indicates
that the LiveSource standby database instance is actively receiving data from the source database. Delphix
continuously monitors the standby instance and notifies users of any abnormalities.

Users can change the Data Age Threshold at any time by flipping the LiveSource card and updating the threshold
value in the card as seen below.

307

Delphix User Guide 2016 Delphix

Oracle LiveSources Quickly Sync with Consistent Snapshots

Taking snapshots of a LiveSource is instantaneous since the standby database for the LiveSource is constantly receiving data from the source
database and recovering it. Taking snapshots occurs instantaneously by taking a filesystem level snapshot of the data on the Delphix Engine
without requiring a RMAN backup of the source database. All LiveSource snapshots are consistent; as a result, provisioning from LiveSource
snapshots is fast, because no database recovery needs to happen.

Oracle LiveSources Use Resync and Apply

Resync is a way to refresh the LiveSource to the current point in the linked source. The

following situations require a Resync to be

performed:
There are unresolvable gaps in the log sequence for example, logs from the source database deleted before the primary database
could ship them over to the LiveSource standby.
The source database was taken through a point in time recovery / flashback, resulting in a changed incarnation.
The source database contains non-logged changes. In this case, a Resync is needed only if you are interested in moving the non-logged
data over to the LiveSource.
The LiveSource is significantly behind the source database due to network communication issues or large amount of writes.

LiveSource Resync is a two-step operation consisting of:

Start Resync Start Resync performs

an incremental backup of the source database to transfer the latest changes

to the Delphix Engine. This operation does not affect the availability of the LiveSource.
Apply Resync Data Applying

the Resync data will perform one more incremental backups from the source
database to ensure up to date data, and recreate the LiveSource instance while preserving all the
configurations. This operation requires downtime for the LiveSource.
If the prepared resync data is no longer needed or resync data has become obsolete (for example, another
controlled change has been done on the source database), you can discard the current resync data with Disca
rd Resync Data. The next Resync will refetch data from the source database.

308

Delphix User Guide 2016 Delphix

Pre-requisites: Configuration and Installation of Staging Environments To Host a Standby Database

Oracle Active Data Guard Required

The LiveSource feature requires an Active Data Guard license. Delphix uses Active Data Guard to replicate changes
from the source database to a standby database that it creates on the staging environment.
Network Requirements
LiveSource requires a Data Guard connection between the source and the standby database which utilizes TNS listeners associated with the
databases.
Database Requirements
LiveSource requires Enterprise Edition of Oracle Database.

Oracle Support Matrix

LiveSource Supports:

LiveSource Does Not Support:

Oracle 11g and non-consolidated Oracle 12c

Oracle Standard Edition on the source and staging environments

SI and RAC source databases

Consolidated 12c databases

Physical and standby source databases

LiveSources running on a RAC

Related Links
Oracle LiveSource User Workflows

309

Delphix User Guide 2016 Delphix

Oracle LiveSource User Workflows

Please use the following documentation as a guide to identify and act on common Oracle LiveSource User Workflows. The following table of
contents includes steps for how to convert a dSource into a LiveSource, provision from a LiveSource, sync a LiveSource, convert a LiveSource
back to a dSource, and many other data procedures.
Converting to LiveSource from a dSource
Convert to LiveSource, Section 1 of 6 in the LiveSource Wizard
Convert to LiveSource, Section 2 of 6 in the LiveSource Wizard
Convert to LiveSource, Section 3 of 6 in the LiveSource Wizard
Convert to LiveSource, Section 4 of 6 in the LiveSource Wizard
Convert to LiveSource, Section 5 of 6 in the LiveSource Wizard
Convert to LiveSource, Section 6 of 6 in the LiveSource Wizard
Setting up Log Transport between a dSource or Primary Database and a LiveSource or Standby Database
Removing a LiveSource
Performing a Snapshot on a LiveSource
Provisioning from a LiveSource Timeflow
Enabling, Disabling, and Detaching a LiveSource
Resyncing a LiveSource + Applying the Resync
Discarding Resync Data
Prerequisites
Applying Resync Data
Prerequisites
Procedure
Migrating a LiveSource
Upgrading a LiveSource
Related Links

Converting to LiveSource from a dSource

To get a live feed to the source database data through the Delphix Engine, you must first link the database to the Delphix Engine to create a
dSource. You can then convert the dSource into a LiveSource by following the steps outlined below:
1.

In the left-hand panel, click the dSource.

2.

Flip the dSource card.

3.

Click Convert to LiveSource, as highlighted above. This launches the Convert to LiveSource wizard.

Convert to LiveSource, Section 1 of 6 in the LiveSource Wizard

1. Enter a DB Unique Name for the LiveSource.

2. Enter a Database SID for the LiveSource.

310

Delphix User Guide 2016 Delphix

Note: The LiveSource database name must be same as the database name of the primary database; therefore, this value is read-only.

Convert to LiveSource, Section 2 of 6 in the LiveSource Wizard

Select the environment on which the LiveSource will be created:

1. Select an Environment User for the LiveSource instance.
2. Enter the Mount Point for the LiveSource instance.
3. Select Listeners as needed. If you enable Auto Select Listeners, the Delphix Engine will pick the first available listener from the
environment.

4. Click Next.
Convert to LiveSource, Section 3 of 6 in the LiveSource Wizard

The image below illustrates where a user is to configure virtual database (VDB) templates and DB configuration parameters.
1.

Select VDB configuration templates for the LiveSource.

2.

Enter additional DB configuration parameters for the LiveSource.

311

Delphix User Guide 2016 Delphix

3.

Click Next.

Convert to LiveSource, Section 4 of 6 in the LiveSource Wizard

1. The image below illustrates where you will enter the data age warning threshold for the LiveSource.
If the data in LiveSource lags behind the source database by more than this threshold, the Delphix Engine will raise a fault and notify you
.

2.

Click Next.

Convert to LiveSource, Section 5 of 6 in the LiveSource Wizard

1. As seen in the image below, you can enter the operations to be performed on initial conversion. These operations are performed after
the Delphix Engine has created the standby database for the LiveSource.

312

Delphix User Guide 2016 Delphix

2. Click Next.

Note: These operations will also be performed when resyncing a LiveSource.

Convert to LiveSource, Section 6 of 6 in the LiveSource Wizard

1. As seen in the image below, review the configuration summary.

2.

Click Covert to begin the conversion.

Setting up Log Transport between a dSource or Primary Database and a LiveSource or Standby Database

After adding a LiveSource instance, you must configure the log transport between the dSource or primary database and the LiveSource or
standby database. For details on configuring a standby database, refer to the Oracle Data Guard Concepts and Administration guide.

At source/primary database:
1. Configure the LOG_ARCHIVE_CONFIG parameter to enable the sending of redo logs to remote destinations and the receipt of remote
redo logs (the LiveSource instance). For example:
alter system set log_archive_config='DG_CONFIG=(sourcedb,livesource)' scope=both;
2.

Configure the

LOG_ARCHIVE_DEST_n parameter to point the redo logs to the LiveSource instance. For example:
alter system set log_archive_dest_2='SERVICE=livesource ASYNC VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE)
DB_UNIQUE_NAME=livesource scope=both;

3. Set up tnsnames.ora in both source and target sites.

4. Create a passwd file for the LiveSource into the target site.
5.
313

Delphix User Guide 2016 Delphix

4.
5.

Configure the corresponding LOG_ARCHIVE_DEST_STATE_n parameter to identify whether the log transport is
enabled. For example:
alter system set log_archive_dest_state_2='ENABLE' scope=both;

6.

Configure the STANDBY_FILE_MANAGEMENT parameter to enable automatic standby file management. For example:
alter system set standby_file_management='AUTO' scope=both;

At the Staging Environment where the LiveSource standby database environment is running:
1. Configure the FAL_SERVER parameter to point to the primary database for proper fetch archive log function. For example:
ALTER system SET
fal_server='service="(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sourcedb.dcenter.delphix.com)(PORT=152
1))(CONNECT_DATA=(SERVICE_NAME=sourcedb)(SERVER=DEDICATED)))"';
2.

If not already created, configure a password file for Data Guard.

Removing a LiveSource

1. In the left-hand panel, click the LiveSource.

2.

Flip the LiveSource card.

3. Click Convert to dSource, as highlighted in the lower right-hand corner of the LiveSource card below:

Performing a Snapshot on a LiveSource

As seen in the image below, you can take a snapshot of a LiveSource by clicking the camera icon on the front of the LiveSource card.
LiveSource snapshots are instantaneous, Quick Provision snapshots and dont require an RMAN backup of the source database.

Provisioning from a LiveSource Timeflow

Provisioning from a LiveSource timeflow is the same process as provisioning from a snapshot for dSource
timeflow. The only difference is that you will select a LiveSource and a LiveSource snapshot.

314

Delphix User Guide 2016 Delphix

Enabling, Disabling, and Detaching a LiveSource

A LiveSource is enabled the same way as a regular dSource.

1. Click Manage.
2. Select Databases.
3. Select My Databases.
4. Select the LiveSource to enable.
5. On the back of the LiveSource card, move the slider control from Disabled to Enabled.
6. Click Yes to acknowledge the warning.

Note: When you enable the LiveSource, the Delphix Engine will recreate the standby database on the staging environment.

A LiveSource is disabled the same way as a regular dSource.

1. Click Manage.
2. Select Databases.
3. Select My Databases.
4. Select the LiveSource to disable.
5. On the back of the LiveSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.

Note: Disabling a LiveSource shuts down the standby database that Delphix manages on the staging environment.

You can detach a LiveSource in the same way as detaching a regular dSource. Detaching a LiveSource will implicitly
convert the LiveSource into a regular dSource. After a dSource is re-attached, you can convert it back into a
LiveSource.
Resyncing a LiveSource + Applying the Resync

Resync is a way to refresh the LiveSource to the current point in the linked source. Resync is a multi-phase operation comprised of the following:
Perform Resync
1.

Click Manage.

2.

Select Databases.

3.

Select My Databases.

4.

Flip the LiveSource card.

5. Click the Start Resync Data icon, as highlighted in the image below.

315

Delphix User Guide 2016 Delphix

The LiveSource can stay up while the Resync is in progress.

Discarding Resync Data
Prerequisites

Resync is started and ready to apply

After Resync has finished, you can choose to not apply but rather discard the data that was brought over from the
source database as part of Resync. To discard the data:
1. Click Manage.
2. Select Databases.
3. Select My Databases.
4. Flip the LiveSource card.
5.

Click the Discard Resync Data icon, as highlighted in the image below.

316

Delphix User Guide 2016 Delphix

Applying Resync Data

Prerequisites

Resync started and ready to apply

Procedure

1. Click Manage.
2. Select Databases.
3. Select My Databases.
4. Flip the LiveSource card.
5.

Click the Apply Resync Data, as highlighted in the image below.

If the apply resync data process failed, first investigate and resolve the cause of failure, such as a full disk. Then
follow the procedure to start resync.

317

Delphix User Guide 2016 Delphix

Migrating a LiveSource

1. Click Manage.
2. Select Databases.
3. Select My Databases.
4. Flip the LiveSource card.
5.

Disable the dSource.

6.

Click the Migrate icon on the lower right-hand side of the LiveSource card, as seen below:

318

Delphix User Guide 2016 Delphix

7. Update the environment, user, and repository, as illustrated in the image below:

8. Enable the dSource.

Note: After the LiveSource is migrated to a different staging environment, you must ensure that the log transport between the source
database and the LiveSource instance on the new staging environment is set up correctly.

Upgrading a LiveSource

If the source database for the LiveSource has been upgraded, users would have to inform Delphix of the updated Oracle installation and the
associated environment user for both the source database and the LiveSource. This can be done by following the steps below:
1. Click Manage.
2. Select Databases.
3. Select My Databases.
4.

Flip the Live Source card.

5.

Disable the LiveSource.

6.

On the back of the LiveSource card, click the upgrade icon in the lower right-hand corner, as highlighted in
the image below.

319

Delphix User Guide 2016 Delphix

7. Specify the new installation and environment user for the Linked Source and the LiveSource, as illustrtaed in the image below.

8. Enable the LiveSource.

Related Links

Oracle LiveSources Overview

320

Delphix User Guide 2016 Delphix

Replication Prerequisites
Delphix Version
Basic Connectivity
Storage
User

Delphix Version
As mentioned previously, the source primary Delphix Engine and the replica target Delphix Engine must be exactly the same Delphix version. If
you attempt to establish replication between non-matching versions, you will receive an error.

Basic Connectivity
Verify that the source primary engine can reach the replica target engine on your network. If there is a firewall between the two, verify that port
8415 is open from the source to the target.

Storage
The target replica Delphix Engine must have space available in order to retain the objects being copied from the source primary Delphix Engine.
In order to verify this, perform the following:
1. On the source primary engine, login to the administrative GUI as delphix_admin or a similar user.
2. Click the Resources menu.
3. Select Capacity.
4. On the resulting Capacity Management screen, make note of the size of any object or group of objects that you plan on replicating to the
target.
5. Add together all objects you plan on replicating to have a total sum of the space required.
6. On the target replica engine, login to the administrative GUI as delphix_admin or a similar user.
7. Click the Manage menu.
8. Select Dashboard.
9. In the upper right-hand corner, under Capacity Management, verify that Available Space has enough capacity to hold the total object
size from the source primary engine plus enough space left over to be under the warning and critical space alerts for your site.

If adding the Primary objects to the replica will put used capacity over the warning or critical disk thresholds for your site, add additional
storage capacity before you configure replication.

User
In order to configure replication, you must use a username and password with administrative privileges on the target. This can be delphix_admin
or any other user with administrative privileges on the target.

321

Delphix User Guide 2016 Delphix

Replication Verification
Once the initial replication is complete, you can verify that all wanted objects have been replicated to the target by examining the namespace(s)
showing on the target:
1. On the target Delphix Engine, login to the administrative GUI as delphix_admin or another user with administrative privileges.
2. Click System.
3. Select Namespaces.

The network name of the source Delphix engine(s) will appear on the left-hand side of the screen, and the replicated objects related to
the selected engine on the right-hand side.
The example screenshot below shows the objects replicated from a Delphix Engine that has the network name source."

If the target engine is unable to resolve the IP address of the source Delphix Engine to a name, the namespace will be listed as
the IP address of the source. You can give the namespace a different name by clicking the pencil (
namespace name, located above Databases.

) icon next to the

4. If there is more than one namespace listed, select the namespace on the left that you need to verify.
5. Verify that all desired objects from the source have been replicated to the target by reviewing the databases, groups, and environments
that are showing for the selected namespace.

322

Delphix User Guide 2016 Delphix

Performing Final Replication

In order to get the most up-to-date objects from the source system, it is advised to perform a final replication from the source to the target.
1. Login to the source Delphix Engine as delphix_admin or another user with administrative privileges.
2. Click System.
3. Select Replication.
4. Click Run Now to start the replication process.

Replication Target Settings

5. Click OK to confirm.

Trigger Replication Confirmation Dialog

6. Click OK acknowledge.

Replication Settings Successfully Triggered Replication Dialog

7. To monitor the replication job:
a. Click Active Jobs in the upper right-hand corner.
or
a.
323

Delphix User Guide 2016 Delphix

a. Click Manage.
b. Select Dashboard and monitor the replication job there.
Once the final replication job is complete, you are ready to failover the namespace to the target Delphix Engine.

324

Delphix User Guide 2016 Delphix

Provisioning VDBs from Oracle, Oracle RAC, and Oracle PDB Sources
These topics describe concepts and tasks for provisioning a VDB from an Oracle, Oracle RAC or Oracle PDB Source.
Provisioning Oracle VDBs: An Overview
Provisioning an Oracle VDB
Provisioning an Oracle Virtual Pluggable Database
Customizing Oracle VDB Configuration Settings
Customizing Oracle VDB Environment Variables
Customizing VDB File Mappings
Provisioning a VDB from an Encrypted Oracle Database
Time Flows for RAC Provisioning of VDBs
TimeFlow Patching
Enabling and Disabling an Oracle VDB
Provisioning from a Replicated Oracle VDB
Rewinding an Oracle VDB
Refreshing an Oracle VDB
Deleting an Oracle VDB
Migrating an Oracle VDB
Upgrading an Oracle VDB
Migrate a vPDB

325

Delphix User Guide 2016 Delphix

Provisioning Oracle VDBs: An Overview

This topic describes basic concepts behind the Oracle virtual database (VDB) provisioning process.
Working with Snapshots and LogSync
Target Environments for VDBs
Customizing VDB Online Redo Logs
VDB Redo Log Delphix Default and Minimum Values
Customizing VDB Configuration Settings and File Paths
Customizing RAC VDB Instance Configuration
Repository Templates
Related Links
A dSource is a virtualized representation of a physical or logical source database. As a virtual representation, it cannot be accessed or
manipulated using database tools. Instead, you must create a Virtual Database (VDB) from a dSource snapshot. A VDB is an independent,
writeable copy of a dSource snapshot. You can create VDBs from other VDBs. Once a VDB has been provisioned to a target environment, you
can implement a snapshot policy for that VDB, to capture changes within it as if it were any other logical or physical database.

Working with Snapshots and LogSync

When you first create a dSource from a physical or logical database, SnapSync takes an initial snapshot of the database; it then continues to take
snapshots based on your SnapSync policy settings. If LogSync is also enabled, you can use log files in conjunction with the snapshot to provision
a VDB that represents the exact state of the source database at a point in time.
Snapshots accumulate over time. To view a snapshot:
1. In the Delphix Admin application, click My Databases.
2. Select a dSource.
Each snapshot is represented as a card that includes information about the source database, operating system, end stamp, and snapshot SCN.
You can scroll through these cards to select the one you want, or you can enter a date and time to search for a specific snapshot.
If LogSync is enabled, you will also see a LogSync slider control at the top of the snapshot card. If you slide this control to the right to open
LogSync, you will see a pointer that you can move along a timeline to select the exact time from which you want to provision a VDB.
Once a VDB has been provisioned, you can also take snapshots of it, either manually or through a VDB Snapshot policy. You can then provision
additional VDBs from these VDB snapshots. To view VDB snapshots:
1. In the Delphix Admin application, click My Databases.
2. Select the VDB.

Target Environments for VDBs

It is possible to provision a VDB to the same source environment that contains the dSource, but performance and efficiency improve if the
dSource and VDB are located in different environments. For example, if you attempt to provision an encrypted database to its source
environment, the provisioning will fail because of two instances attempting to access the same wallet file.
The source and target environments must have the same operating system and database types. For example, if the source environment is using
Oracle Enterprise Linux 6.0 as the operating system and is running Oracle 10gR2 as its DBMS, then the target environment must have this same
configuration. There are also specific requirements for the target environment user. The supported operating systems for source and target
environments are described in Supported Operating Systems and DBMS Versions for Oracle Environments. User requirements are
described in Requirements for Oracle Target Hosts and Databases.

Customizing VDB Online Redo Logs

When you provision a VDB, you can customize the online redo log size, as well as the number of redo log groups per Oracle thread. The Delphix
Engine only allows one size value to be used for all online redo log size.
Using a large redo log size or groups will increase the VDB provision time. This is especially true in the case of an Oracle RAC VDB with a large
number of RAC instances. Choose a smaller redo log size and groups for faster VDB provision time.
You will not be able to change the online redo log size and groups using the Delphix interface after the VDB is provisioned.
Although you can directly log on to the VDB to change your redo log size or number of redo log groups after the VDB is provisioned, your changes
will disappear when the VDB is refreshed or rewound. They will be replaced by the Delphix settings you entered previously during provisioning.
Online Redo Log Size and Number of Groups can be set during VDB Provisioning as shown below.

326

Delphix User Guide 2016 Delphix

VDB Redo Log Delphix Default and Minimum Values

The default online redo log size setting is the size recorded in the parent snapshot.
The minimum redo log file size for all Oracle versions is 4M.
The default online redo log groups setting is 3.
The minimum number of redo log groups is 2.

Customizing VDB Configuration Settings and File Paths

When you provision a VDB, you have the option of customizing its configuration settings and the file paths that it will use on the target
environment. To view the default configuration settings and file paths during the provisioning process, click Advanced in the Target Environment
screen of the Provision VDB wizard. For more information, see Customizing Oracle VDB Configuration Settings and Customizing VDB File
Mappings.

Customizing RAC VDB Instance Configuration

RAC instance properties can be customized during the provisioning of a RAC VDB or after provisioning the RAC VDB. For each RAC instance the
following instance properties can be customized:
Oracle instance number
Oracle instance name
Cluster node
The Oracle Cluster environment chosen as the provision target environment determines the set of available cluster nodes to be used during
provisioning. You can choose all or some of the available cluster nodes to form their RAC VDB. After provisioning, you can add and remove
cluster nodes from an existing RAC VDB. A minimum of one cluster node is required.
The maximum number of cluster nodes you can expand your RAC VDB into is limited by the Oracle Cluster environment. For example using
Oracle Clusterware a you could configure a cluster environment to have four nodes. In this case the maximum cluster node any RAC database
running on this cluster could have is four. When Delphix discovers the Oracle cluster from the target cluster environment, it knows the total
number of cluster nodes this Oracle cluster is configured with and where are each of these nodes is located (what host, what IP, etc.). When a
RAC VDB is provisioned into this discovered cluster environment, you are presented with the choice of choosing all or a subset of the cluster
nodes. If the you specify the RAC VDB to only use two of the four available cluster nodes, the result will be a two node RAC VDB.
The following screen shot provides an example of the provisioning wizard where the Oracle instance is configured.

Repository Templates

327

Delphix User Guide 2016 Delphix

Repository templates are a new feature introduced in the Fhloston release. The primary use case and motivation for this new capability is to
provide the Delphix administrator with control over the Oracle database parameters used during the staging phase of the VDB provisioning
process. It is useful to be able to control these configuration parameters when the physical capabilities of the staging machine, such as CPU
count and memory, are inferior to the physical capabilities of the machines hosting the source database repository.
The repository template is a relationship between three entities:
A database repository The entity that contains database instances on host environments
A database container An entity that represents all of the physical data associated with the database
A VDB configuration template A list of database configuration parameter names and values that you can save on the Delphix Engine to
use at a later time
During the staging process, if you do not specify a repository template, then by default the Delphix Engine will use the configuration parameters
taken from the source database to configure the staged database. These parameters may not be appropriate, because the machine used for
staging may be physically inferior to the machine hosting the source database.
Instead, the Delphix administrator can create a VDB configuration template, which would be appropriate for the physical machine hosting staging
repository. (See Create VDB Config Template. ) Then the admin can create a repository template entry which will bind together the VDB
configuration template, database repository, and database container. This instructs the Delphix Engine to use configuration parameters from the
VDB configuration template whenever the database container is staged on the database repository specified, instead of the parameters on the
source database.
Currently, repository template relations can only be created via the command line interface (CLI) in repository->template.
1. Switch to the repository->template context and create a new template entry.
delphix> repository template
delphix> create
delphix repository template create *> set name=RepositoryTemplate1
delphix repository template create *> set container=DBContainer1
delphix repository template create *> set repository=DBRepostory1
delphix repository template create *> set template=DBTemplate1
delphix repository template create *> commit

Related Links
Supported Operating Systems and DBMS Versions for Oracle Environments
Requirements for Oracle Target Hosts and Databases
Customizing Oracle VDB Configuration Settings
Customizing VDB File Mappings

328

Delphix User Guide 2016 Delphix

Provisioning an Oracle VDB

This topic describes how to provision a virtual database (VDB) from a dSource or another VDB.
Prerequisites
Procedure
Provisioning by Snapshot or LogSync
Adding or Removing RAC VDB Cluster Node After a VDB is Provisioned
Prerequisites
Procedure
Related Links

Prerequisites
You must have already done one of the following:
linked a dSource from a source database, as described in Linking an Oracle Data Source
or
created a VDB from which you want to provision another VDB
You will need to have the correct OS User privileges on the target environment, as described in Requirements for Oracle Target Hosts
and Databases.
If you want to use customized database configuration settings, first create a VDB Config Template as described in Customizing Oracle
VDB Configuration Settings.
If you are creating a VDB from a dSource linked to an encrypted database, make sure you have copied the wallet file to the target
environment, as described in Provisioning a VDB from an Encrypted Oracle Database.

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource.
6. Select a dSource snapshot.
See Provisioning by Snapshot and LogSync in this topic for more information on provisioning options.
You can take a snapshot of the dSource from which to provision. To do so, click the Camera icon on the dSource card.

7. Optional: Slide the LogSync slider to open the snapshot timeline, and then move the arrow along the timeline to provision from a point
of time within a snapshot.
You can provision from the most recent log entry by opening the snapshot timeline, and then clicking the red Arrow icon next
to the LogSync Slider.

8. Click Provision.
The Provision VDB panel will open, and the fields Installation Home, Database Unique Name, SID, Database Name, Mount Base,
and Environment User will auto-populate with information from the dSource.
9. If you need to add a new target environment for the VDB, click the green Plus icon next to the Filter Target field, and follow the
instructions in Adding an Oracle Single Instance or RAC Environment.
10. Review the information for Installation Home, Database Unique Name, SID, and Database Name. Edit as necessary.
11. Review the Mount Base and Environment User. Edit as necessary.
The Environment User must have permissions to write to the specified Mount Base, as described in Requirements for Oracle Target
Hosts and Databases. You may also want to create a new writeable directory in the target environment with the correct permissions and
use that as the Mount Base for the VDB.
12. Select Provide Privileged Credentials if you want to use login credentials on the target environment that are different from those
associated with the Environment User.
13. Click Advanced to customize the VDB online log size and log groups, archivelog mode, Oracle Node Listeners, additional VDB

329

Delphix User Guide 2016 Delphix

13.
configuration settings or file mappings, or custom environment variables.
For more information, see Customizing VDB online redo logs, Customizing Oracle VDB Configuration Settings, Customizing VDB
File Mappings, and Customizing Oracle VDB Environment Variables.
If you are provisioning to a target environment that is running a Linux OS, you will need to compare the SGA_TARGET configur
ation parameter with the shared memory size in /dev/shm. The shared memory configured on the target host should match
the SGA memory target. You can check this by opening the Advanced settings, and then finding the value for SGA_TARGET un
der VDB Configuration Templates.

14. Click Next.

15. Select a Target Group for the VDB.
If necessary, click the green Plus icon to add a new group.
16. Select a Snapshot Policy for the VDB.
If necessary, click the green Plus icon to create a new policy.
17. Click Next.
18. Enter any operations that should be run at Hooks during the provisioning process.
For more information, see Customizing Oracle Management with Hook Operations.
19. Click Next.
20. Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated and listed in the Databases panel. If you select the
VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database and its Data
Management settings.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any particular snapshot, either by time or SCN.
Provisioning
By
Snapshot

Description

Provision by
Time

You can provision to the start of any snapshot by selecting that snapshot card from the Timeflow view or by entering a value in
the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.

Provision by
SCN

You can use the Slide to Provision by SCN control to open the SCN entry field. Here, you can type or paste in the SCN to
which you want to provision. After entering a value, it will "snap" to the start of the closest appropriate snapshot.

When provisioning by LogSync information, you can provision to any point in time, or to any SCN, within a particular snapshot. The TimeFlow vie
w for a dSource shows multiple snapshots by default. To view the LogSync data for an individual snapshot, use the Slide to Open LogSync contr
ol at the top of an individual snapshot card.
Provisioning
By LogSync

Description

Provision by
Time

Use the Slide to Open LogSync control to view the time range within that snapshot. Drag the red triangle to the point in time
from which you want to provision. You can also enter a date and time directly.

Provision by
SCN

Use the Slide to Open LogSync and Slide to Provision by SCN controls to view the range of SCNs within that snapshot.
Drag the red triangle to the LSN from which you want to provision. You can also type or paste in the specific SCN to which you
want to provision. Note that if the SCN does not exist, you will see an error when you provision.

Adding or Removing RAC VDB Cluster Node After a VDB is Provisioned

Prerequisites
Disable the VDB before you edit the instance configuration.

Procedure
1. After provisioning, you can select the VDB card and flip it to the back to edit the RAC VDB instance configuration.

330

Delphix User Guide 2016 Delphix

2. Edit the following:

Number of instances
Name of instance
Check or uncheck the cluster node you want for this RAC VDB

3. Enable the VDB to take effect on the instance configuration change.

Related Links
Linking an Oracle Data Source
Requirements for Oracle Target Hosts and Databases
Using Pre- and Post-Scripts with dSources and SQL Server VDBs
Customizing Oracle VDB Configuration Settings
Customizing VDB File Mappings

331

Delphix User Guide 2016 Delphix

Provisioning an Oracle Virtual Pluggable Database

This topic describes how to provision a virtual pluggable database (VPDB) from an Oracle pluggable database source (dSource).

Prerequisites
You must have done one of the following:
linked a PDB dSource from a multitenant container database, as described in Linking an Oracle Pluggable Database
already created a VPDB from which you want to provision another VPDB
There must be a target environment that has a compatible multitenant container database to host the VPDB you are about to create
You will need to have the correct operating system (OS) user privileges on this target environment. For more information, refer
to Requirements for Oracle Target Hosts and Databases.
The multitenant container databases (CDBs) of the source PDB and the target that will host the VPDB must meet the following
requirements:
They must have the same endian format
They must be in ARCHIVELOG mode
They must have compatible character sets and national character sets, which means:
Every character in the source CDB character set is available in the target CDB character set
Every character in the source CDB character set has the same code point value in the target CDB character set
They must have the same set of database options installed. For example, if the source CDB is a real application cluster (RAC)
database, the target CDB must be a RAC database.

Procedure
1. Log into the Delphix Admin application.
2. Select Manage > Databases > My Databases.
3. Select a PDB dSource or a previously provisioned VPDB.
4. Select a snapshot.
For more information on provisioning options, see the Provisioning by Snapshot or LogSync section in Provisioning an Oracle VDB.

You can take a snapshot of the source database to provision from by clicking the Camera icon on the source card.

5. Optional: Slide the LogSync slider to open the snapshot timeline, and then move the arrow along the timeline to provision from a point
of time within a snapshot.

You can provision from the most recent log entry by opening the snapshot timeline and then clicking the red Arrow ic
on next to the LogSync Slider.

6. Click Provision.
The Provision VDB panel will open, and the provision target fields Installation Home, Container Database, Database Name, Mount
Base, and Environment User will auto-populate. Information from the selected target environment will be highlighted on the left hand
pane.
7. For each selected Installation Home, there can be more than one Container Database. Use the drop down box to further select which
Container Database you are about to provision to host your VPDB.
8.

Review the information for Installation Home, Container Database, and Database Name. Change or edit as
necessary.

9. Review the Mount Base and Environment User and edit as necessary.
The Environment User must have permissions to write to the specified Mount Base, as described in Requirements for Oracle Target
Environments and Databases. You may also want to create a new writeable directory in the target environment with the correct
permissions, and use that as the Mount Base for the VDB.
10. Select Provide Privileged Credentials if you want to use login credentials on the target environment other than those associated with
the Environment User.
11. Click Advanced to enter any file mappings setting for your VPDB.

332

Delphix User Guide 2016 Delphix

11.
See Customizing VDB File Mappings for more information.
12. Click Next.
13. Enter the VDB Name for the VPDB you are about to provision.
14. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
15. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
16. Click Next.
17. Enter any operations that should be run at Hooks during the provisioning process.
See Customizing Oracle Management with Hook Operations for more information.
18. Click Next.
19. Review the provision summary. Click Finish to proceed with provisioning the VPDB. When provisioning starts, you can review progress
of the job in the Databases panel, or in the Job History panel of the Dashboard. When provisioning is complete, the VPDB will be
included in the group you designated, and listed in the Databases panel. If you select the VPDB in the Databases panel and click the Op
en icon, you can view its card, which contains information about the database and its Data Management settings.

The container database of the VPDB will be automatically linked if it has not been linked already.

Temporary CDB Instance

During VPDB provisioning, a temporary CDB instance is created in the target environment to recover the VPDB to a consistent state.
This temporary CDB will be automatically deleted after the VPDB is provisioned successfully.

Related Links
Linking an Oracle Pluggable Database
Provision an Oracle VDB
Discovering Oracle Pluggable Databases in an Oracle Environment
Requirements for Oracle Target Hosts and Databases
Customizing VDB File Mappings
Migrate a vPDB
Customizing Oracle Management with Hook Operations

333

Delphix User Guide 2016 Delphix

Customizing Oracle VDB Configuration Settings

This topic describes how to customize Oracle and Oracle RAC virtual database (VDB) configuration settings, including settings that the Delphix
Engine reserves and those that it removes from the database configuration file during the provisioning process.
When you create a VDB, the Delphix Engine copies configuration settings from the dSource and uses them to create the VDB. Most settings are
copied directly, and you can see these settings by clicking the Advanced link in the Target Environment screen in the Provision VDB wizard.
When a VDB is provisioned in the browser, you can specify configuration parameters directly or copy them from a VDB Configuration Template.
Once set, the Delphix Engine will use these parameters whenever the VDB is refreshed, even if you change the original template. With the
command line interface (CLI), you can store a reference to the template with the VDB instead of copying the values. When using a template
reference, subsequent refreshes will use the configuration settings from the template. In this case, changes to a template will appear in any VDBs
when they are refreshed. If you delete a template while VDBs still refer to it, the template property will be unset for those VDBs and the current
settings will be used when refreshed in the future.
It is important to know, however, that some configuration parameters cannot be customized. In addition, some configuration parameters are
stripped out during the provisioning process but are customizable. The list of restricted and customizable parameters can be found below.

Creating a VDB Config Template

1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > VDB Config Templates to open the VDB Configuration Template Manager.
3. Click the green Plus icon to add a parameter.
4. Enter the name and value for the parameter.
5. Repeat steps 3 and 4 for each parameter you want to add to the template.
6. When you are done adding parameters, click Save Template.

Building Templates from Other Templates

If you have already created a VDB Config Template, you can use it as the basis for creating other templates.
1. Open the VDB Configuration Template Manager, and then select a template.
2. Click Create New Template.
3. Enter a name for the template.
4. Click OK.
A new template is created with the parameters from the selected template. You can now edit or add parameters as necessary.
5. Click Save Template.

Applying a VDB Config Template

You can apply a VDB Config Template to a VDB during the provisioning process. As described in the introduction, this copies the values from the
template. Any subsequent changes to the template will not appear in the VDB, even when that VDB is refreshed.
1. In the Target Environment screen of the Provision VDB wizard, click Advanced.
2. Select Use Template.
3. Select a template.
4. Click Next.

Dynamically Template Parameters on Refresh (CLI Only)

In the CLI, you can set a reference to the template instead of copying the parameters. Subsequent refreshes will use the values from the
template, even if those values have changed. Setting a template reference causes the Delphix Engine to ignore any manually-set parameters.
1. Select the target source.
delphix> source select vexample
2. Update the source.
delphix source "vexample"> update

3.
334

Delphix User Guide 2016 Delphix

3. Set the configTemplateproperty using the name of your desired template.

delphix source "vexample" update *> set configTemplate=ExampleTemplate
4. Commit the result.
delphix source "vexample" update *> commit

You can also set the template reference during provisioning. See the CLI Cookbook: Provisioning a Single Instance Oracle VDB topic for
more information.

Video

Restricted Parameters
These parameters are restricted for use by the Delphix Engine. Attempting to customize these parameters through the use of a VDB Config
Template will cause an error during the provisioning process.
active_instance_count
cluster_database
cluster_database_instances
cluster_interconnects
control_files
db_block_size
db_create_file_dest
db_create_online_log_dest_1
db_create_online_log_dest_2
db_create_online_log_dest_3
db_create_online_log_dest_4
db_create_online_log_dest_5
db_file_name_convert
db_name
db_recovery_file_dest
db_recovery_file_dest_size
db_unique_name
dg_broker_config_file1
dg_broker_config_file2
dg_broker_start
fal_client
fal_server
instance_name
instance_number
local_listener
log_archive_config
log_archive_dest
log_archive_duplex_dest
log_file_name_convert
spfile
standby_archive_dest
standby_file_management
thread
undo_tablespace
__db_cache_size
__java_pool_size
__large_pool_size
__oracle_base
__pga_aggregate
__sga_target

335

Delphix User Guide 2016 Delphix

__shared_io_pool_size
__shared_pool_size
__streams_pool_size

Customizable Parameters
The default value for these parameters is cleared during the provisioning process. They are removed from the VDB configuration file unless you
set values for them through a VDB Config Template.
audit_file_dest
audit_sys_operations
audit_trail
background_dump_dest
core_dump_dest
db_domain
diagnostic_dest
dispatchers
fast_start_mttr_target
log_archive_dest_1
log_archive_dest_2
log_archive_dest_3
log_archive_dest_4
log_archive_dest_5
log_archive_dest_6
log_archive_dest_7
log_archive_dest_8
log_archive_dest_9
log_archive_dest_10
log_archive_dest_11
log_archive_dest_12
log_archive_dest_13
log_archive_dest_14
log_archive_dest_15
log_archive_dest_16
log_archive_dest_17
log_archive_dest_18
log_archive_dest_19
log_archive_dest_20
log_archive_dest_21
log_archive_dest_22
log_archive_dest_23
log_archive_dest_24
log_archive_dest_25
log_archive_dest_26
log_archive_dest_27
log_archive_dest_28
log_archive_dest_29
log_archive_dest_30
log_archive_dest_31
log_archive_dest_state_1
log_archive_dest_state_2
log_archive_dest_state_3
log_archive_dest_state_4
log_archive_dest_state_5
log_archive_dest_state_6
log_archive_dest_state_7
log_archive_dest_state_8
log_archive_dest_state_9
log_archive_dest_state_10

336

Delphix User Guide 2016 Delphix

log_archive_dest_state_11
log_archive_dest_state_12
log_archive_dest_state_13
log_archive_dest_state_14
log_archive_dest_state_15
log_archive_dest_state_16
log_archive_dest_state_17
log_archive_dest_state_18
log_archive_dest_state_19
log_archive_dest_state_20
log_archive_dest_state_21
log_archive_dest_state_22
log_archive_dest_state_23
log_archive_dest_state_24
log_archive_dest_state_25
log_archive_dest_state_26
log_archive_dest_state_27
log_archive_dest_state_28
log_archive_dest_state_29
log_archive_dest_state_30
log_archive_dest_state_31
remote_listener
user_dump_dest

Customizing Oracle VDB Environment Variables

This topic describes how to customize the set of environment variables sourced prior to administering an Oracle virtual database (VDB).
Overview
Setting Custom Environment Variables
Prerequisites
Procedure
Environment Variable Blacklist
User-Input Sanitation For Environment Variables
Caveats

Overview
Certain Oracle database parameters are sensitive to the environment variables present when you start or administer the database. For this
reason, the Delphix Engine allows you to dictate custom environment variables that will be set prior to any administrative action, such as
provision, start, stop, rollback, or refresh.
You can specify environment variables by two different means:
Name-Value Pair A literal variable name and value to be set
Environment File An environment file to be sourced
Environment variables for Oracle RAC databases might vary in value between cluster nodes. Therefore, environment variable specifications for
an Oracle RAC database must specify the cluster node to which they apply.

Setting Custom Environment Variables

Prerequisites
If you are adding any environment variables that are environment files, these files must be accessible on the target environment.

Procedure
1. You can configure custom environment variables in the Provision Wizard.
a.
337

Delphix User Guide 2016 Delphix

1.
a. On the Target Environment tab, click Advanced.
or
b. You can also configure these variables on the back of an Oracle VDB card (on the Standard tab) when the VDB is disabled.
2. Click the Plus icon to add an environment variable.
3. Choose a format of environment variable.
a. Name-Value Pair
i. Enter a Name to identify the variable.
ii. Enter the variable's Value.
iii. For Oracle RAC databases, you must also specify the cluster node to which this environment variable applies.
b. Environment File
i. Enter an absolute path to an environment file on the target environment.
This path can be followed by parameters. Paths and parameters are separated by spaces.
Escaping Spaces
To specify literal spaces, escape them with a backslash ("hello\ world" -> "hello world").
To specify literal backslashes, escape them with a backslash ("foo\\" -> "foo\").
Any other character preceded by a backslash will retain both the backslash and the original character ("\b" ->
"\b").
Escaping is done in order from left to right ("part1\\ part2" -> "part1\" "part2" will be two parameters).

ii. For Oracle RAC databases, you must also specify the cluster node to which this environment variable applies.
4. Save the custom environment variables by completing provisioning, or clicking the Confirm icon below the widget on the VDB card.
These environment variables will take effect when you start the Oracle VDB.

Environment Variable Blacklist

The Delphix Engine blacklists the following environment variables; they cannot be set by the user.
ORACLE_SID
ORACLE_BASE
ORACLE_HOME
CRS_HOME
ORAENV_ASK
LOGON_STR
DLPX_SHELL
SQLPLUS_PLSQL_MODIFIERS
SQLPLUS_DML_MODIFIERS
SQLPLUS_DDL_MODIFIERS
If a Name-Value pair has any one of these blacklisted environment variables as the name, an error will be raised.
If an environment file sets one of these variables, the Delphix Engine will override this value when the Oracle VDB is started.

User-Input Sanitation For Environment Variables

For security purposes, user-input provided through the custom environment variables feature retains its literal value when interpreted, including ',
", and $.
Certain frequently-used environment variables are exempt from this rule and will be interpreted:
$ORACLE_HOME
$ORACLE_BASE
$ORACLE_SID
$CRS_HOME
$LD_LIBRARY_PATH
$PATH

Caveats

338

Delphix User Guide 2016 Delphix

Environment variables are sourced on provision, start, stop, rollback, and refresh. Custom environment variables are not applicable to
V2P.
Custom environment variables do not propagate to child VDBs and must be set again on provision.
Custom environment variables do not persist after migration.
On migration of a VDB with custom environment variables, an alert will be raised that the custom environment variables have been
removed from the VDB. In order to view the alert, go to System -> Event Viewer.

339

Delphix User Guide 2016 Delphix

Customizing Oracle VDB Environment Variables

This topic describes how to customize the set of environment variables sourced prior to administering an Oracle virtual database (VDB).
Overview
Setting Custom Environment Variables
Prerequisites
Procedure
Environment Variable Blacklist
User-Input Sanitation For Environment Variables
Caveats

Overview
Certain Oracle database parameters are sensitive to the environment variables present when you start or administer the database. For this
reason, the Delphix Engine allows you to dictate custom environment variables that will be set prior to any administrative action, such as
provision, start, stop, rollback, or refresh.
You can specify environment variables by two different means:
Name-Value Pair A literal variable name and value to be set
Environment File An environment file to be sourced
Environment variables for Oracle RAC databases might vary in value between cluster nodes. Therefore, environment variable specifications for
an Oracle RAC database must specify the cluster node to which they apply.

Setting Custom Environment Variables

Prerequisites
If you are adding any environment variables that are environment files, these files must be accessible on the target environment.

Procedure
1. You can configure custom environment variables in the Provision Wizard.
a. On the Target Environment tab, click Advanced.
or
b. You can also configure these variables on the back of an Oracle VDB card (on the Standard tab) when the VDB is disabled.
2. Click the Plus icon to add an environment variable.
3. Choose a format of environment variable.
a. Name-Value Pair
i. Enter a Name to identify the variable.
ii. Enter the variable's Value.
iii. For Oracle RAC databases, you must also specify the cluster node to which this environment variable applies.
b. Environment File
i. Enter an absolute path to an environment file on the target environment.
This path can be followed by parameters. Paths and parameters are separated by spaces.
Escaping Spaces
To specify literal spaces, escape them with a backslash ("hello\ world" -> "hello world").
To specify literal backslashes, escape them with a backslash ("foo\\" -> "foo\").
Any other character preceded by a backslash will retain both the backslash and the original character ("\b" ->
"\b").
Escaping is done in order from left to right ("part1\\ part2" -> "part1\" "part2" will be two parameters).

ii. For Oracle RAC databases, you must also specify the cluster node to which this environment variable applies.
4. Save the custom environment variables by completing provisioning, or clicking the Confirm icon below the widget on the VDB card.
These environment variables will take effect when you start the Oracle VDB.

340

Delphix User Guide 2016 Delphix

Environment Variable Blacklist

The Delphix Engine blacklists the following environment variables; they cannot be set by the user.
ORACLE_SID
ORACLE_BASE
ORACLE_HOME
CRS_HOME
ORAENV_ASK
LOGON_STR
DLPX_SHELL
SQLPLUS_PLSQL_MODIFIERS
SQLPLUS_DML_MODIFIERS
SQLPLUS_DDL_MODIFIERS
If a Name-Value pair has any one of these blacklisted environment variables as the name, an error will be raised.
If an environment file sets one of these variables, the Delphix Engine will override this value when the Oracle VDB is started.

User-Input Sanitation For Environment Variables

For security purposes, user-input provided through the custom environment variables feature retains its literal value when interpreted, including ',
", and $.
Certain frequently-used environment variables are exempt from this rule and will be interpreted:
$ORACLE_HOME
$ORACLE_BASE
$ORACLE_SID
$CRS_HOME
$LD_LIBRARY_PATH
$PATH

Caveats
Environment variables are sourced on provision, start, stop, rollback, and refresh. Custom environment variables are not applicable to
V2P.
Custom environment variables do not propagate to child VDBs and must be set again on provision.
Custom environment variables do not persist after migration.
On migration of a VDB with custom environment variables, an alert will be raised that the custom environment variables have been
removed from the VDB. In order to view the alert, go to System -> Event Viewer.

341

Delphix User Guide 2016 Delphix

Customizing VDB File Mappings

This topic describes how to customize file path mappings when provisioning a virtual database (VDB).
In the VDB provisioning process, it may be necessary to create mappings between files and directories that exist on the source, and files or file
directories that exist on the target. An example of this is creating a copy in the target environment of a wallet file for an encrypted database that
exists in the source environment.

Pattern Matching Example

You can use pattern matching rules to create full path names for data files and control files.
Pattern matching rules have the form source-regex-expression-KEY : target-replacement-VALUE. You can use multiple rules, which are
applied successively. Multiple rules with the same source key are allowed.
In this example, several rules are applied to the source file path /app/oracle/oradata/system01.dbf.
1. Applying the rule ora:foo results in: /app/foocle/foodata/system01.dbf
2. Applying the rule foo:bar results in: /app/barcle/bardata/system01.dbf
3. Applying the rule ora:no results in an error, because ora is no longer found in the pathname.
4. Applying the rule bar:oranew results in: /app/oranewcle/oranewdata/system01.dbf
5. Applying the rule ora:yes results in /app/yesnewcle/yesnewdata/system01.dbf
During the pattern matching process, two errors can be generated.
1. No match for specified mapping rules
This is the result when no rules match a source file
2. Invalid regex pattern specified for path mapping
This is the result of an invalid regex rule mapping
This topic on the java.regex.util class, hosted on docs.oracle.com, shows the regular expression syntax and constructs recognized by the
Delphix Engine pattern-matching operations.

Applying VDB File Mappings During the Provisioning Process

1. In the Target Environment screen of the Provision VDB wizard, click Advanced.
2. Click the green Plus icon to add a mapping rule.
3. Enter the mapping rule.
4. Click Validate to see the results of applying the rule.
If not matches are found, you will see an error message.
5. Click Next to continue with the provisioning process.

342

Delphix User Guide 2016 Delphix

Provisioning a VDB from an Encrypted Oracle Database

This topic describes how to provision a VDB from an encrypted database.
The Delphix Engine supports provisioning from a dSource linked to a physical database that has been encrypted with Oracle's Transparent
Database Encryption (TDE), which can be used to encrypt columns or tablespaces.
Provisioning a VDB from an encrypted dSource requires that you have an auto-open wallet set up in the target environment, because the
provisioning process requires the master key stored in the wallet file. You can either set up an auto-open wallet for the source database and copy
the auto-open wallet files (both ewallet.p12 and cwallet.sso) to the target environment, or first copy the encryption wallet file (ewallet.p1
2) to the target environment, and then generate an auto-open wallet from the encryption wallet file.
When provisioning a VDB from an encrypted dSource, if the target environment has other databases that also use TDE, each database should
use a different wallet. Please check Oracle documentation on how to set up different wallet locations for different databases. For example, you
can use $ORACLE_SID in the DIRECTORY clause of the ENCRYPTION_WALLET_LOCATION parameter in sqlnet.ora:

ENCRYPTION_WALLET_LOCATION=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=/opt/oracle/walle
ts/$ORACLE_SID)))
Procedure
1. Check for any encrypted columns or tablespaces on the source database by using these commands:

SELECT t.name name, e.encryptionalg algorithm FROM v$tablespace t,

v$encrypted_tablespaces e
WHERE t.ts# = e.ts# and upper(e.encryptedts) = 'YES';
2. Copy wallet files from the source database to the target environment, and then configure the sqlnet.ora file on the target to point to
the directory where the wallet is located.

$ more sqlnet.ora
ENCRYPTION_WALLET_LOCATION=(SOURCE(METHOD=file)
(METHOD_DATA=(DIRECTORY=/opt/oracle/oradata/nf/wallet)))
3. If the source database does not use auto-open wallet, create the auto-open wallet at the target environment.

$ orapki wallet create -wallet /opt/oracle/oradata/nf/wallet -auto_login

4. Proceed with provisioning the VDB as described in Provisioning an Oracle VDB.

343

Delphix User Guide 2016 Delphix

Time Flows for RAC Provisioning of VDBs

This topic describes special considerations when provisioning by time stamp from a RAC time flow.
Time stamps in Oracle RAC time flows can be imprecise because of time skew among the hosts in a RAC configuration. The time stamps will
generally track the host with the fastest clock. For this reason, provisioning by a time stamp may not leave the VDB provisioned at the exact time
desired. Provision by SCN should be used if more fine-grained control is required when provisioning.

344

Delphix User Guide 2016 Delphix

TimeFlow Patching
Introduction

The Delphix Engine provides the ability to link to an external database by creating a dSource within the Delphix
system. Once linked, the Delphix Engine maintains a complete history of the database as part of a t imeflow , limited
by the retention policies configured by the administrator. From any time within that timeflow, you can provision a
virtual database (VDB) from the Delphix Engine. This timeflow is maintained through the use of SnapSync and LogS
ync.
The SnapSync operation pulls over the complete data set of the external database during initial load. Subsequent SnapSync operations pull and
store only incremental changes. At the end of each SnapSync operation, a snapshot is created that serves as the base point for provisioning
operations. In

addition, LogSync periodically connects to the host(s) running the source database and pulls over any
log files associated with the database. These log files are stored separately from the SnapSync data and are used to
provision from points in between SnapSync snapshots. Usually SnapSync operates against a live database with
changes actively being made to it. Hence the data that it pulls over is fuzzy and logs must be applied to the data to
make it consistent and provisionable. If LogSync is enabled, SnapSync relies on it to copy the logs over. If LogSync
is not enabled, SnapSync copies the logs itself. Occasionally, LogSync or SnapSync is not able to retrieve one or
more log files from the database. This creates a break in the timeflow or can prevent a snapshot from being
provisioned. To remedy this situation, the Delphix Engine has tools to repair, or patch, a snapshot and the timeflow.
Snapshot Repair

Please note that the below steps do not apply if your archive logs are stored on ASM, if you are doing so the archived logs need to be
moved to a supported filesystem directory.

When missing log files prevent a snapshot from being provisioned, you can use the graphical user interface (GUI) to determine the missing logs
and repair the snapshot. The

Delphix Engine will generate a fault whenever missing logs prevent a snapshot from being
provisionable. The fault will likely have the title Cannot provision database from snapshot and will contain a
description of the cause. The most common causes are:
Logs were deleted/moved/archived from the database before the Delphix Engine could retrieve them. In this case, the archive log
retention policy on the source database may be too aggressive. Use the GUI snapshot repair tool to fetch the logs.
LogSync is still fetching the logs. SnapSync is relying on LogSync to fetch the logs needed to make the snapshot consistent. SnapSync
normally will wait up to 15 minutes for LogSync to fetch the logs. If LogSync has not fetched the logs by then, SnapSync will generate a
fault and finish. The best course of action in this case may be to wait for LogSync to fetch the logs.
The source database is a physical standby in real-time apply mode. The changes described in the current online log of the database are
needed to make the snapshot consistent. LogSync cannot retrieve the log until it is archived, and SnapSync cannot force the log to be
archived because the source database is a physical standby. Force a log switch on the primary database or wait until the log is naturally
archived.
Below is a screenshot of a snapshot with missing logs. Hovering the cursor over the (i) symbol on the snapshot card will cause the list of missing
log(s) to be shown. In this example, log sequences 18 and 19 are missing.

345

Delphix User Guide 2016 Delphix

Snapshot with missing logs, Version 4.2.0

If the snapshot can be repaired by fetching the logs from the source database, then you can use the GUI snapshot repair tool to fetch the logs.
Clicking on the tools symbol on the snapshot card causes the tool to be started.

Repair tool, Version 4.2.0

346

Delphix User Guide 2016 Delphix

To use the snapshot repair tool, as seen in the above illustration:

1. Enter a Hostname. This should be the host from which to retrieve the log(s).
2. Enter a Username and Password. These should be the credentials for a user who can read the archived log file(s).
3. Enter a File Path. This should be the name of the directory containing the missing log(s).
Note: If more than one file is missing, they should all exist in the directory specified by File Path. The tool will read every file in the File Path direc
tory so it is best that it only contains the files that are to be retrieved.

Timeflow Patching
When missing log files cause a break in the timeflow, you can use the command line interface (CLI) to determine the
missing logs and patch the timeflow. The Delphix Engine will generate a fault whenever there are missing logs on a portion of the
timeflow. The fault will likely have the title Cannot provision a database from a portion of TimeFlow and will contain a description of the cause.
The most common cause is an overly aggressive archive log retention policy on the source database causing a log to be deleted before LogSync
can fetch it. Other faults can also be generated describing the specific errors encountered when fetching the log(s).
You can use the CLI to list the missing logs and patch the timeflow. The following CLI Cookbook entry demonstrates how to do this: CLI
Cookbook: Repairing a Timeflow.

347

Delphix User Guide 2016 Delphix

Enabling and Disabling an Oracle VDB

This topic describes how to enable and disable a virtual database (VDB).
Disabling a VDB is a pre-requisite for procedures such as VDB migration or upgrade. Disabling a VDB removes all traces of it, including any
configuration files, from the target environment to which it was provisioned. When the VDB is later enabled again, these configuration files are
restored on the target environment.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the VDB you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the VDB again, move the slider control form Disabled to Enabled, and the VDB will continue to function as it did
previously.

348

Delphix User Guide 2016 Delphix

Provisioning from a Replicated Oracle VDB

This topic describes how to provision from a replicated dSource or virtual database (VDB). The process for provisioning from replicated objects is
the same as the typical VDB provisioning process, except that first you need to select the replica containing the replicated object.
Prerequisites
Procedure
Post-Requisites

Prerequisites
You must have replicated a dSource or a VDB to the target host, as described in Replication Overview.
You must have added a compatible target environment on the target host.

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB you want to provision.
6. The provisioning process is now identical to the process for provisioning standard objects.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

349

Delphix User Guide 2016 Delphix

Rewinding an Oracle VDB

This topic describes the procedure for rewinding a VDB.
Rewinding a VDB rolls it back to a previous point in its TimeFlow and re-provisions the VDB. The VDB will no longer contain changes after the
rewind point.
Although the VDB no longer contains changes after the rewind point, the rolled over Snapshots and TimeFlow still remain in Delphix
and are accessible through the Command Line Interface (CLI). See the topic CLI Cookbook: Rolling Forward a VDB for instructions
on how to use these snapshots to refresh a VDB to one of its later states after it has been rewound.
Prerequisites
Procedure

Prerequisites
To rewind a VDB, you must have the following permissions:
Auditor permissions on the dSource associated with the VDB
Owner permissions on the VDB itself
You do NOT need owner permissions for the group that contains the VDB. A user with Delphix Admin credentials can perform a VDB Rewind on
any VDB in the system.

Procedure
1. Login to the Delphix Admin application.
2. Under Databases, select the VDB you want to rewind.
3. Select the rewind point as a snapshot or a point in time.
4. Click Rewind.
5. If you want to use login credentials on the target environment other than those associated with the environment user, click Provide
Privileged Credentials.
6. Click Yes to confirm.
You can use TimeFlow bookmarks as the rewind point when using the CLI. Bookmarks can be useful to:
Mark where to rewind to - before starting a batch job on a VDB for example.
Provide a semantic point to revert back to in case the chosen rewind point turns out to be incorrect.
For a CLI example using a TimeFlow bookmark, see CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark.

350

Delphix User Guide 2016 Delphix

Refreshing an Oracle VDB

Prerequisites
Procedure
Related Links
This topic describes how to manually refresh a virtual database (VDB).
Refreshing a VDB will re-provision it from the dSource. As with the normal provisioning process, you can choose to refresh the VDB from a
snapshot or a specific point in time. However, you should be aware that refreshing a VDB will delete any changes that have been made to it over
time. When you refresh a VDB, you are essentially re-setting it to the state you select during the refresh process. You can refresh a VDB
manually, as described in this topic, or you can set a VDB refresh policy, as described in the topics Managing Policies: An Overview, Creating
Custom Policies, and Creating Policy Templates.
Although the VDB no longer contains the previous contents, the previous Snapshots and TimeFlow still remain in Delphix and are
accessible through the Command Line Interface (CLI).

Prerequisites
To refresh a VDB, you must have the following permissions:
Auditor permissions on the dSource associated with the VDB
Auditor permissions on the group that contains the VDB
Owner permissions on the VDB itself
A user with Delphix Admin credentials can perform a VDB Refresh on any VDB in the system.

Procedure
1. Login to the Delphix Admin application.
2. Under Databases, select the VDB you want to refresh.
3. Click the Open icon in the upper right hand corner of the VDB card.
4. On the back of the VDB card, click the Refresh VDB icon in the lower right-hand corner.
This will open the screen to re-provision the VDB.
5. Select desired refresh point snapshot or slide the display LogSync timeline to pick a point-in-time to refresh from.
6. Click Refresh VDB.
7. Click Yes to confirm.

Related Links
Managing Policies: An Overview
Creating Custom Policies
Creating Policy Templates

351

Delphix User Guide 2016 Delphix

Deleting an Oracle VDB

This topic describes how to delete a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Click My Databases.
4. Select the VDB you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

352

Delphix User Guide 2016 Delphix

Migrating an Oracle VDB

This topic describes how to migrate a Virtual Database (VDB) from one target environment to another.
There may be situations in which you want to migrate a virtual database to a new target environment, for example when upgrading the host on
which the VDB resides, or as part of a general data center migration. This is easily accomplished by first disabling the database, then using the
Migrate VDB feature to select a new target environment.

Prerequisites
You should have already set up a new target environment that is compatible with the VDB that you want to migrate.
A VDB from a Single Instance of Oracle cannot be migrated onto a RAC environment, the additional reconfiguration needed when
converting a single instance to RAC is only performed during a VDB provision. Provision a new VDB instead.

Procedure
1. Login to your Delphix Engine using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select the VDB you want to migrate.
6. Click the Open icon.
7. Slide the Enable/Disable control to Disabled, and click Yes to confirm.
When the VDB is disabled, its icon will turn grey.
8. On the bottom-right corner of the VDB card, click the VDB Migrate icon.
9. Select the new target environment for the VDB, the user for that environment, and the database installation where the VDB will reside.
10. Click the Check icon to confirm your selections.
11. Slide the Enable/Disable control to Enabled, and click Yes to confirm.
Within a few minutes your VDB will re-start in the new environment, and you can continue to work with it as you would any other VDB.

Video

353

Delphix User Guide 2016 Delphix

Upgrading an Oracle VDB

Prerequisites

Make a backup of the spfile for the old version of Oracle.

Follow Oracle documentation to upgrade the VDB's database on the target server.

Recreate the spfile using the new init.ora parameters as recommended by Oracle for the upgrade.
Procedure
Normally a PSU or Oracle upgrade will have both binary changes as well as some scripts to run on the database side as well.
Prior to applying to a VDB take a snapshot of the VDB just in case something goes wrong and you want to back it out.
There are 3 ways to apply a PSU/Oracle upgrade:
A) Apply to existing ORACLE_HOME. (Please be on Delphix version 4.1.x or higher.)
B) Create new ORACLE_HOME (could clone existing one) and then apply the PSU to the new ORACLE_HOME.
C) Using refresh on the back of a VDB card to upgrade the VDB after a dsource was upgraded.
Oracle documentation should be followed and the appropriate script(s) and or steps would be ran on the databases using those
ORACLE_HOMEs or in option B the instance would be stopped (using old ORALCE_HOME) and restarted with the new ORACLE_HOME from
the command line as normal.

For Delphix working with a VDB using option A:

1) Follow Oracle Documentation patch the ORACLE_HOME then the database for the VDB(s)
2) Refresh the environment the VDBs are on in the Delphix GUI.

For Delphix working with a VDB using option B:

1) Refresh the environment from the Delphix GUI we'll want to verify that the new ORACLE_HOME is picked up and in the databases tab as an
ORACLE Installation.
2) Stop the VDB from the command line (old ORACLE_HOME)
3) export ORACLE_HOME=(newORACLE_HOME) follow Oracle documentation patch the database.
4) Remember copy the init.ora for that VDB in this new $ORACLE_HOME/dbs directory. The delphix_os user will need write permissions to this
directory.
5) If there are any database parameter changes the spfile located on the delphix mount base would need to be updated with those values.
6) From the Delphix GUI flip the VDB card over and use the upgrade icon on the bottom to switch the ORACLE_INSTALLATION to the new one
you just used and we verified in step 1.

354

Delphix User Guide 2016 Delphix

For Delphix working with a VDB using option C:

1) Refresh the environment from the Delphix GUI, verify that the new ORACLE_HOME is picked up and in the databases tab as an
ORACLE Installation in the Manage Environments UI
2) Stop the VDB from GUI using the red stop button on the front of the VDB card.
3) Flip the VDB card over use the upgrade icon to switch the ORACLE_INSTALLATION to the new upgrade version same as the
dsource. Discovered in 1 above.
4) Flip the VDB card over and press the refresh button, select a new snapshot from the dsource that was taken after the dsource was
upgraded. (The database version is on the snapshot card.)

Updating the Oracle User after an Upgrade

There may be cases when you upgrade the Oracle home and the Oracle User (who owns the binary) is a different user than the
previous Oracle User. You will then need to update the Oracle User for each environment, and then re-connect each VDB to the
upgraded Oracle home using the new Oracle User.
The new Oracle User must be in the same OS group (for example, dba or oinstall) as the previous one.
1. Log into the Delphix Admin application using delphix_admin credentials.
2. Select Manage > Environments.
3. Select the environment where you want to add the user.
4. Next to Environment Users, click the Pencil icon to add the new user.
5. Set the new user as the default user.
6. Follow the procedure to upgrade VDBs described in this topic.

None

355

Delphix User Guide 2016 Delphix

Migrate a vPDB
There may be situations in which you want to migrate a virtual pluggable database (vPDB) to a new container database on the same or a different
target environment, for example when upgrading the host on which the vPDB resides, or as part of a general data center migration. This is easily
accomplished by first disabling the vPDB, then using the Migrate vPDB feature to select a new container database.

Pre-requisites
You should already set up and have Delphix discover a container database in the same environment as the vPDB currently is or from a different
environment to which the vPDB will be migrated to.

Procedure
Login to your Delphix Engine using Delphix Admin credentials.
1. Click Manage.
2.

Select Databases.

3.

Select My Databases.

4. Select the vPDB you want to migrate.

5. Flip the vPDB card.
6. Move the slider control to Disabled.
7. Click Yes to confirm.

When the vPDB is disabled, its icon will turn gray.

8. In the bottom right-hand corner of the vPDB card, click the vPDB Migrate icon.
9. Select the new container database for the vPDB, the user for that environment, and the database installation where the container
database of the vPDB will reside.
10. Click the Check icon to confirm your selections.
11. Move the slider control to Enabled.
12. Click Yes to confirm.
Within a few minutes, your vPDB will re-start in the new environment, and you can continue to work with it as you would any other vPDB.

Related Links
Linking an Oracle Pluggable Database
Provisioning an Oracle Virtual Pluggable Database
Provision an Oracle VDB
Discovering Oracle Pluggable Databases in an Oracle Environment
Requirements for Oracle Target Hosts and Databases
Customizing VDB File Mappings
Customizing Oracle Management with Hook Operations

356

Delphix User Guide 2016 Delphix

Customizing Oracle Management with Hook Operations

Hook operations allow you to execute an ordered list of custom operations at select hook points in linking, provisioning and virtual dataset
management. For details on the types of operations that are available, see children of this page.
dSource Hooks
Virtual Dataset Hooks
Setting Hook Operations
Setting Hook Operations through the Delphix Admin Application
Setting Hook Operations through the CLI
Example of Editing Hook Operations through the CLI
Hook Operation Templates
Creating a Hook Operation Template
Importing a Hook Operation Template
Exporting a Hook Operation Template

dSource Hooks
Hook

Description

Pre-Sync

Operations performed before a sync.

These operations can quiesce data to be captured during the sync, or stop processes that may interfere with the sync.

Post-Sync

Operations performed after a sync. This hook will run regardless of the success of the sync or Pre-Sync hook operations.
These operations can undo any changes made by the Pre-Sync hook.

Virtual Dataset Hooks

Hook

Description

Configure
Clone

Operations performed after initial provision or after a refresh. This hook will run after the virtual dataset has been started.
During a refresh, this hook will run before the Post-Refresh hook.

Pre-Refresh

Operations performed before a refresh.

These operations can cache data from the virtual dataset to be restored after the refresh completes.

Post-Refresh

Operations performed after a refresh. During a refresh, this hook will run after the Configure Clone hook. This hook will not run
if the refresh or Pre-Refresh hook operations fail.
These operations can restore cached data after the refresh completes.

Pre-Rewind

Operations performed before a rewind.

These operations can cache data from the virtual dataset to be restored after the rewind completes.

Post-Rewind

Operations performed after a rewind. This hook will not run if the rewind or Pre-Rewind hook operations fail.
These operations can restore cached data after the rewind completes.

Pre-Snapshot

Operations performed before a snapshot.

These operations can quiesce data to be captured during the snapshot, or stop processes that may interfere with the
snapshot.

Post-Snapshot

Operations performed after a snapshot. This hook will run regardless of the success of the snapshot or Pre-Snapshot hook
operations.
These operations can undo any changes made by the Pre-Snapshot hook.

Operation Failure
If a hook operation fails, it will fail the entire hook: no further operations within the failed hook will be run.

Setting Hook Operations

357

Delphix User Guide 2016 Delphix

You can construct hook operation lists through the Delphix Admin application or the command line interface (CLI). You can either define the
operation lists as part of the linking or provisioning process or edit them on dSources or virtual datasets that already exist.

Setting Hook Operations through the Delphix Admin Application

To specify hook operations during linking or provisioning, navigate to the Hooks tab of the Linking Wizard or Provision Wizard.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation or click Import to load a hook operation template.
4. Click the text area and edit the contents of the operation.
5. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
6. To remove an operation from the list, click the Trash icon on the operation.
7. When you have set all hook operations, click Next to continue with the provisioning process.
To edit hook operations on an already-existing dSource or virtual dataset, navigate to the Hooks tab on the back of the dSource card or virtual
dataset card.
1. Select the hook to edit.
2. The current operations at this hook will be displayed. To edit this list of operations, click the Pencil icon in the top right-hand corner of the
card.
3. Click the Plus icon to add a new operation.
4. Select the type of operation or click Import to load a hook operation template.
5. Click the text area and edit the contents of the operation.
6. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
7. To remove an operation from the list, click the Trash icon on the operation.
8. When you have set all hook operations, click Check to save the changes.

Setting Hook Operations through the CLI

To specify hook operations during linking, edit the relevant hook's array of operations defined on the LinkingParameters > Source >
Operations object.
To specify hook operations during provisioning, edit the relevant hook's array of operations defined on the ProvisionParameters > Source
> Operations object.
To edit hook operations on an already-created dSource, edit the relevant hook's array of operations defined on the Source > Operations obje
ct.
To edit hook operations on an already-created virtual dataset, edit the relevant hook's array of operations defined on the Source > Operation
s object.
For more information about these CLI objects, see the LinkedSourceOperations, VirtualSourceOperations, RunCommandOnSourceOp
eration, and RunExpectOnSourceOperation API documentation in the Help menu of the Delphix Admin application.

Example of Editing Hook Operations through the CLI

1. Navigate to the relevant source's VirtualSourceOperations object.
2. Select a hook to edit.
delphix> source
delphix source> select "pomme"
delphix source "pomme"> update
delphix source "pomme" update *> edit operations
delphix source "pomme" update operations *> edit postRefresh
3. Add an operation at index 0.
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
Properties
type: RunCommandOnSourceOperation (*)
command: echo Refresh completed. (*)
delphix source "pomme" update operations postRefresh

358

*> add
0 *> set type=RunCommandOnSourceOperation
0 *> set command="echo Refresh completed."
0 *> ls

0 *> commit

Delphix User Guide 2016 Delphix

4. Add another operation at index 1 and then delete it.

delphix
delphix
delphix
delphix
delphix
delphix

source
source
source
source
source
source

"pomme"
"pomme"
"pomme"
"pomme"
"pomme"
"pomme"

update
update
update
update
update
update

operations
operations
operations
operations
operations
operations

postRefresh
postRefresh
postRefresh
postRefresh
postRefresh
postRefresh

*> add
1 *> set type=RunCommandOnSourceOperation
1 *> set command="echo Refresh completed."
1 *> back
*> unset 1
*> commit

Hook Operation Templates

You can use templates to store commonly used operations, which allows you to avoid repeated work when an operation is applicable to more
than a single dSource or virtual dataset. You manage templates through the Delphix Admin application.
Hook Operations Templates Not Available via CLI
Hook operation templates cannot be fully utilized from the CLI. Manage and use hook operations through the Delphix Admin applicatio
n.

Creating a Hook Operation Template

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Operation Templates.
4. Click the Plus icon to add a new operation template.
5. Enter a Name for the template.
6. Select an operation Type.
7. Enter a Description detailing what the operation does or how to use it.
8. Enter operation Contents to implement the operation partially or fully.
9. Click Create.

Importing a Hook Operation Template

To import a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Click Import.
4. Select the template to import.
5. Click Import.
6. When you have set all hook operations, click Check to save the changes.

Exporting a Hook Operation Template

To export a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation.
4. Click the text area and edit the contents of the operation.
5. Click Export.
6. Enter a Name for the template.
7. Enter a Description detailing what the operation does or how to use it.
8. Click Create.

359

Delphix User Guide 2016 Delphix

Oracle Hook Operation Notes

Oracle RAC
Shell Operations
RunCommand Operation
RunBash Operation
Shell Operation Tips
Other Operations
RunExpect Operation
Oracle Environment Variables
dSource Environment Variables
VDB Environment Variables

Oracle RAC
When linking from, or provisioning to Oracle RAC environments, hook operations will not run once on each node in the cluster. Instead, the
Delphix Engine picks a node in the cluster at random and guarantees all operation within any single hook will execute serially on this node.
Note that the Delphix Engine does not guarantee the same node is chosen for the execution of every hook, but does guarantee that Pre-/Posthook pairs (such as Pre-Sync and Post-Sync) will execute on the same node.

Shell Operations
RunCommand Operation

The RunCommand operation runs a shell command on a Unix environment using whatever binary is available at /bin/sh. The environment user
runs this shell command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the shell command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Examples of RunCommand Operations

You can input the full command contents into the RunCommand operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
if test -d "$remove_dir"; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
If a script already exists on the remote environment and is executable by the environment user, the RunCommand operation can execute this
script directly.

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh "$ARG_ENVIRONMENT_VARIABLE" "second

argument in double quotes" 'third argument in single quotes'
RunBash Operation

The RunBash operation runs a Bash command on a Unix environment using a bash binary provided by the Delphix Engine.The environment user
runs this Bash command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the Bash command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of RunBash Operations

You can input the full command contents into the RunBash operation.

360

Delphix User Guide 2016 Delphix

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
# Bashisms are safe here!
if [[ -d "$remove_dir" ]]; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
Shell Operation Tips
Using nohup

You can use the nohup command and process backgrounding from resource in order to "detach" a process from the Delphix Engine. However, if
you use nohup and process backgrounding, you MUST redirect stdout and stderr.
Unless you explicitly tell the shell to redirect stdout and stderr in your command or script, the Delphix Engine will keep its connection to the
remote environment open while the process is writing to either stdout or stderr . Redirection ensures that the Delphix Engine will see no more
output and thus not block waiting for the process to finish.
For example, imagine having your RunCommand operation background a long-running Python process. Below are the bad and good ways to do
this.
Bad Examples
nohup
nohup
nohup
nohup

python
python
python
python

file.py
file.py
file.py
file.py

& # no redirection
2>&1 & # stdout is not redirected
1>/dev/null & # stderr is not redirected
2>/dev/null & # stdout is not redirected

Good Examples
nohup python file.py 1>/dev/null 2>&1 & # both stdout and stderr redirected, Delphix Engine will not
block

Other Operations
RunExpect Operation

The RunExpect operation executes an Expect script on a Unix environment. The Expect utility provides a scripting language that makes it easy to
automate interactions with programs which normally can only be used interactively, such as ssh. The Delphix Engine includes a
platform-independent implementation of a subset of the full Expect functionality.
The script is run on the remote environment as the environment user from their home directory. The Delphix Engine captures and logs all output
of the script. If the operation fails, the output is displayed in the Delphix Admin application and CLI to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunExpect Operation

Start an ssh session while interactively providing the user's password.

spawn ssh [email protected]

expect {
-re {Password: } {
send "${env(PASSWORD_ENVIRONMENT_VARIABLE)}\n"
}
timeout {
puts "Timed out waiting for password prompt."
exit 1
}
}
exit 0

361

Delphix User Guide 2016 Delphix

Oracle Environment Variables

Operations that run user-provided scripts have access to environment variables. For operations associated with specific dSources or virtual
databases (VDBs), the Delphix Engine will always set environment variables so that the user-provided operations can use them to access the
dSource or VDB.
dSource Environment Variables

Environment Variable

Description

ORACLE_SID

The SID of the dSource

ORACLE_BASE

The home directory of the Oracle software hosting the dSource

ORACLE_HOME

The Oracle Home for the dSource

CRS_HOME (only set for RAC dSources)

The home directory for cluster services hosting the dSource

ORAENV_ASK

Always set to NO

DELPHIX_DATABASE_NAME

The database name reported by Oracle

DELPHIX_DATABASE_UNIQUE_NAME

The database unique name reported by Oracle

DELPHIX_PDB_NAME (only set for PDBs)

The PDB name reported by Oracle

VDB Environment Variables

Environment Variable

Description

ORACLE_SID

The SID for the VDB

ORACLE_BASE

The home directory for the Oracle software hosting the VDB

ORACLE_HOME

The Oracle Home for the VDB

CRS_HOME (only set for RAC VDBs)

The home directory for cluster services hosting the RAC VDB

ORAENV_ASK

Always set to NO

DELPHIX_DATABASE_NAME

The database name reported by Oracle

DELPHIX_DATABASE_UNIQUE_NAME

The database unique name reported by Oracle

DELPHIX_PDB_NAME (only set for PDBs)

The PDB name reported by Oracle

DELPHIX_MOUNT_PATH

The root of the NFS mount hosting the VDB data

MASKING_CONNECTOR_HOST (only set for masked

provisioning)

The host that DMSuite will use for the connector

MASKING_CONNECTOR_PORT (only set for masked

provisioning)

The port that DMSuite will use for the connector

PATH and LD_LIBRARY_PATH configuration

PATH is configured by appending the bin directory in the Oracle home for the dSource or VDB.
LD_LIBRARY_PATH is configured by appending the lib directory in the Oracle home for the dSource or VDB.

362

Delphix User Guide 2016 Delphix

Listener and JDBC Verification

As with any database, a VDB needs to have a listener in order for external connections to be made. The Delphix Engine also uses a JDBC
connection string in order to connect to a source or target database. If the engine does not have the proper listener or JDBC connect string
defined, then connection errors can result.

Verifying the Listener Configuration

1. Verify that a listener is running on the source or target environment that you are investigating.
2. Login to the Delphix engine as delphix_admin or another user with administrative privileges.
3. Click Manage.
4. Select Environments.

5. Click on the environment which you are troubleshooting.

6. In the lower right-hand corner of the Environment Details tab, locate the Listeners section. Verify that the listener for the source or
target system is listed there.
7. If a listener is not listed, it may be due to insufficient privileges on the part of the environment user that the engine is using. Verify that the
proper sudo permissions have been granted for the user, or adjust them as necessary.
8. If you need to add another listener, you can do so manually.
a. Click the plus (+) sign.
b. Enter the appropriate values using the above image as a reference.

Verifying the JDBC Connection String

Each source database and VDB has a connection string defined. If any parameters have changed, you may need to adjust these connection
strings.
1. Verify that a listener is running on the source or target environment you are investigating.
2. Login to the Delphix engine as delphix_admin or another user with administrative privileges.
3. Click Manage.
4. Select Environments.

5. Click the environment which you are troubleshooting.

6. In the upper right-hand portion of the screen, click Databases.

Databases Icon
7. For the source database or VDB which you are investigating, click Show Details to the right of the database name. This will display the
JDBC connection string being used for the given database.
8. To verify that the connection string works, click the checkmark to the right of the connection string. You will then see username and
password text boxes.
9. Enter the oracle username and password used by the Delphix engine.

Database Username and Password

If no errors are encountered and the username/password dialogs simply go away, then a successful connection was made to the database.
If errors are encountered, you must investigate them on a case-by-case basis, just as you would do with any connection errors to an Oracle
database.

363

Delphix User Guide 2016 Delphix

Adding JDBC Connection String

If you need to define an additional JDBC connection string for any reason, take the following steps:
1. Follow the same steps as listed in Verifying the JDBC Connection String to reach the JDBC connection string definition(s).
2. Click the plus (+) sign to the right of Add Connection String to define an additional connection string.
In the screenshot below, the user is adding a connection string for the test2 service on port 1530 instead of the default 1521.

3. Click the checkmark (

) to save the changes.

4. Follow the remaining steps in Verifying the JDBC Connection String to validate your newly added connection string.

364

Delphix User Guide 2016 Delphix

Adding a New JDBC Connection String

If you need to define an additional JDBC connection string for any reason, take the following steps:
1. Follow the same steps as listed in Verifying the JDBC Connection String to reach the JDBC connection string definition(s).
2. Click the plus (+) sign to the right of Add Connection String to define an additional connection string.
In the screenshot below, the user is adding a connection string for the test2 service on port 1530 instead of the default 1521.

3. Click the checkmark (

) to save the changes.

4. Follow the remaining steps in Verifying the JDBC Connection String to validate your newly added connection string.

365

Delphix User Guide 2016 Delphix

Verifying the Listener Configuration

1. Verify that a listener is running on the source or target environment that you are investigating.
2. Login to the Delphix engine as delphix_admin or another user with administrative privileges.
3. Click Manage.
4. Select Environments.

5. Click on the environment which you are troubleshooting.

6. In the lower right-hand corner of the Environment Details tab, locate the Listeners section. Verify that the listener for the source or
target system is listed there.
7. If a listener is not listed, it may be due to insufficient privileges on the part of the environment user that the engine is using. Verify that the
proper sudo permissions have been granted for the user, or adjust them as necessary.
8. If you need to add another listener, you can do so manually.
a. Click the plus (+) sign.
b. Enter the appropriate values using the above image as a reference.

366

Delphix User Guide 2016 Delphix

Verifying the JDBC Connection String

Each source database and VDB has a connection string defined. If any parameters have changed, you may need to adjust these connection
strings.
1. Verify that a listener is running on the source or target environment you are investigating.
2. Login to the Delphix engine as delphix_admin or another user with administrative privileges.
3. Click Manage.
4. Select Environments.

5. Click the environment which you are troubleshooting.

6. In the upper right-hand portion of the screen, click Databases.

Databases Icon
7. For the source database or VDB which you are investigating, click Show Details to the right of the database name. This will display the
JDBC connection string being used for the given database.
8. To verify that the connection string works, click the checkmark to the right of the connection string. You will then see username and
password text boxes.
9. Enter the oracle username and password used by the Delphix engine.

Database Username and Password

If no errors are encountered and the username/password dialogs simply go away, then a successful connection was made to the database.
If errors are encountered, you must investigate them on a case-by-case basis, just as you would do with any connection errors to an Oracle
database.

367

Delphix User Guide 2016 Delphix

SQL Server Environments and Data Sources

368

Delphix User Guide 2016 Delphix

SQL Server Support and Requirements

These topics describe specific requirements for Windows environments, such as user privileges, as well as supported Microsoft SQL Server
versions and compatible operating systems.
Delphix as a Backup Solution to SQL Server
Network and Connectivity Requirements for SQL Server Environments
Requirements for SQL Server Source Hosts and Databases
Requirements for SQL Server Target Hosts and Databases
Requirements for SQL Server Validated Sync Targets
SQL Server Operating System Compatibility Matrices
SQL Server Target Host iSCSI Configuration Parameter Recommendations
Supported Operating Systems, Server Versions, and Backup Software for SQL Server

369

Delphix User Guide 2016 Delphix

Requirements for SQL Server Source Hosts and Databases

Source hosts are the servers that contain data sources to which the Delphix Engine links and from which it provisions virtual databases.
Collectively, the source host and its databases are referred to as the source environment. This topic describes the requirements for creating
connections between the Delphix Engine and SQL Server source hosts and databases.
Requirements for SQL Server Source Hosts and Databases
Windows Domain User Requirements
Database User Requirements
Related Links

Requirements for SQL Server Source Hosts and Databases

Each SQL Server source host must meet these requirements:
Either the source host must belong to the same Windows domain as the target environments, or the domain that the source environment
uses must have appropriate cross-domain trust relationships established with the target environments' domains
Source hosts can be running any supported Windows operating system version. For more information, see the topic Supported
Operating Systems, Server Versions, and Backup Software for SQL Server.
The SQL Server instance on the source host should run as either domain users or local service accounts. Delphix does not support
running SQL Server instances as local user accounts or Managed Service Accounts (MSA).
The validated sync environment that the Delphix Engine uses must have access to an existing full backup of the source database in order
to create the first full copy. Alternatively, the Windows Database User described below must have permissions to initiate a copy-only full
backup of the source database.
Backup images of the source database, including full, differential, and/or transaction logs, must be available over an SMB share to a
staging environment. For more information, see the topic Setting Up SQL Server Environments: An Overview.
You must enable TCP/IP access for each SQL Server instance that contains a database to which the Delphix Engine will link
To enable TCP/IP access, access the SQL Server Config Manager and select Network Configuration > Protocols > TCP/IP
If the source database is backed up with third-party backup software like LiteSpeed or Red Gate SQL Backup Pro, you must also install
the backup software on the validated sync environment. For backup software compatibility requirements, see the topic Supported
Operating Systems, Server Versions, and Backup Software for SQL Server.
Delphix regularly queries "msdb.dbo.backupset" to find out if a new backup image has been created and needs to be synchronized with
Delphix. Microsoft recommends maintaining this table with "sp_delete_backuphistory". Periodically deleting rows from this table
improves the performance of queries running against it and reduces the load on the source database.
Linking to Databases on Windows Server Failover Clusters
You can use databases on Windows Server Failover Clusters (WSFC) as data sources. Add the environment as described below,
based on which WSFC feature the source databases use:
Failover Cluster Instances
Add the environment as a standalone source using the cluster name or address.
AlwaysOn Availability Groups
Add the environment as a cluster source using the cluster name or address.

Windows Domain User Requirements

The source environment must have a Windows Domain user (for example, delphix_src) that the Delphix Engine can use. This is the user that
you provide when adding the source environment to the Delphix Engine. The user provides remote read-only access to the Windows Registry for
discovering SQL Server instances and databases. This user must meet these requirements:
Be a member of the Backup Operators or Administrators group on the source host
Be a member of the Backup Operators or Administrators group on the staging host that will be used to create staging copies of the
source databases on the source host
Be a login with Windows Authentication to each SQL Server instance with which the Delphix Engine will communicate
To create a new login, access the SQL Server Management Studio and select Security > Logins
Have the database role db_datareader for the master database on each SQL Server instance with which the Delphix Engine will
communicate
To edit the user properties and set this role, access the SQL Server Management Studio, select Security > Logins >
delphix_src > User Mapping
If the source host belongs to a cluster, the user must have these privileges on all hosts that comprise the cluster
If the source host belongs to a AlwaysOn Availability Groups then the user must be granted access to the following views:
VIEW ANY DEFINITION
VIEW SERVER STATE

370

Delphix User Guide 2016 Delphix

Database User Requirements

There must be a database user (for example, delphix_db) for each source database that will link to the Delphix Engine. This user must meet
these requirements:
Be able to login with a local database account using SQL Authentication over Java database connectivity (JDBC) to the database.
The database account can not use Windows Authentication. Note this user will not perform any action that could affect production
operations, only issuing queries for database names, database sizes, recovery mode and backup information.
For the master database, have the database role db_datareader
To set this role, access the SQL Server Management Studio and select Security > Logins > delphix_db > User Mappings
For the msdb database, have the database role db_datareader for reading backup history
To set this role, access the SQL Server Management Studio and select Security > Logins > delphix_db > User Mappings
If the Delphix Engine will initiate copy-only full backups of the database, the database user must have the database role db_backupope
rator for the database
To set this role, access SQL Server Management Studio and select Security > Logins > delphix_db > User Mappings
The database user should be able to "use" the desired database. Delphix will periodically run a query to find the size of the database ( "S
ELECT SUM(size) FROM sys.database_files;" ). The results of the query will be reflected on the back of the dSource card.

Related Links
Supported Operating Systems, Server Versions, and Backup Software for SQL Server
Setting Up SQL Server Environments: An Overview

371

Delphix User Guide 2016 Delphix

Requirements for SQL Server Target Hosts and Databases

This topic describes requirements for SQL Server target hosts, and Windows Domain or local users, for connecting with the Delphix Engine. The
target host server, and the databases it contains, are collectively referred to as target environments. Windows

target environments can

be used for staging and/or provisioning of virtual databases (VDBs), as well as proxies for discovery of database
instances on source environments. See the topic Setting Up SQL Server Environments: An Overview for more information.
The requirements described in this topic apply equally to target environments used as staging environments and for
provisioning VDBs.
Requirements for SQL Server Target Hosts
Each SQL Server target host must meet these requirements:
1. It must either belong to the same Windows domain as the source hosts, or the domain used by the target host must have appropriate two
way cross-domain trust relationships established with the source hosts' domains.
2. The SQL Server instance on the target host should run as either domain users or local service accounts. Delphix does not support
running SQL Server instances as local user accounts.
3. The SQL Server instance on the target host should be the same version or higher than the instance hosting the source database, with
one exception. If

a source database comes from a SQL Server 2005 instance, then the target hosts that will host
VDBs from that source must be running either a SQL Server 2005 instance or a SQL Server 2012 instance or
higher.
Upgrading VDBs from SQL Server 2005
You can first provision a VDB to SQL Server 2005 and then upgrade it to a higher version by following the steps described in
the topic Upgrading SQL Server VDBs. See the topic SQL Server Operating System Compatibility Matrices for more
information about compatibility between different versions of SQL Server.

4. The target host must have 64-bit Windows as the operating system. Delphix does not support 32-bit target systems.
5. To add a Windows cluster as a target environment see the topic Adding a SQL Server Failover Cluster Target Environment.
6. If the target host is a VMWare virtual machine, then the Windows Server operating system must be configured to use the VMXNET3 netw
ork driver.
7. The operating system version on a target host that will be used for the provisioning of VDBs should be equal to or higher than the
operating system on the target that is hosting the staging databases for the dSource from which the VDB is being provisioned. There is
no OS compatibility requirement between source and target hosts. See the topic SQL Server Operating System Compatibility
Matrices for more information.
8. Windows PowerShell 2.0 or higher must be installed.
9. Execution of Windows PowerShell scripts must be enabled on the target host.
While running Windows PowerShell as an Administrator, enter this command to enable script execution: Set-ExecutionPolicy
Unrestricted.
10. For Windows 2003 target hosts, the following should be installed:
a. WIndows Server iSCSI initiator (available for download).
b. Hotfix documented in Microsoft Knowledge Base article KB 943043.
11. The Windows iSCSI Initiator Service should have its Startup Type set to Automatic, and the service should be running. See the topic
SQL Server Target Host iSCSI Configuration Parameter Recommendations for configuring the Windows iSCSI Initiator Service.
12. The Delphix Connector must be installed, as described in the topics Setting Up SQL Server Environments: An Overview and Adding
a SQL Server Standalone Target Environment.
Flash Player Required for Connector Download
A Flash player must be available on the target host to download the Delphix Connector when using the Delphix GUI. If the
target host does not have a Flash player installed, you can download the connector directly from the Delphix Engine by
navigating to this URL: http://<name of your Delphix Engine>/connector/DelphixConnectorInstaller.msi

13. Shared Memory must be enabled as a Network Protocol for the SQL instances on the target.

In SQL Server Config Manager, navigate to Client Protocols > Shared Memory to enable this.
14. TCP/IP access must be enabled for each SQL Server instance on the target host to allow remote connections to instances.
In SQL Server Config Manager, navigate to Network Configuration > Protocols > TCP/IP to enable TCP/IP access.

372

Delphix User Guide 2016 Delphix

Windows User Requirements

There must be a Windows user (for example, delphix_trgt) for the target host that can be used by the Delphix Engine. This user can be a
Windows domain user or a local user. However, using a local user account will prevent the target host from being used as a staging target. This
user must meet these requirements:
1. Must be a member of the local Administrators group for access to discovery operations on source hosts, and for mounting iSCSI LUNs
presented by the Delphix Engine to the target host.
2. Must have the server role sysadmin for each SQL Server instance that the Delphix Engine will communicate with.
In SQL Server Management Studio, navigate to Security > Logins >delphix_trgt > Server Roles to set this role for the user.
3. Must have Log on as a batch job rights so the Delphix Engine can remotely execute commands via Powershell.
Using the secpol.msc security policy editor, navigate to Local Policies > User Rights Assignment > Log on as a batch job to set this
right.

Related Links
Setting Up SQL Server Environments: An Overview
SQL Server Operating System Compatibility Matrice
SQL Server Target Host iSCSI Configuration Parameter Recommendations

373

Delphix User Guide 2016 Delphix

Requirements for SQL Server Validated Sync Targets

This topic describes additional requirements for SQL Server environments that will be used as targets for validated sync. For more information,
see Setting Up SQL Server Environments: An Overview.
Requirements for SQL Server Validated Sync Target Environments
Windows Domain User Requirements
Related Links

Requirements for SQL Server Validated Sync Target Environments

Each SQL Server target environment used for validated sync must meet these requirements:
Only standalone target environments can be used as validated sync target environments. Windows Failover Cluster target environments
and SQL Server Failover Cluster instances cannot be used.
The SQL Server instance must be the same version as the instance hosting the source database. For more information about
compatibility between different versions of SQL Server, see SQL Server Operating System Compatibility Matrices.
The owner of the SQL Server instances on the target environment that are used for the staging databases must have SMB read access
to the location containing the backup images of the source databases
If the source database is backed up with third-party backup software like LiteSpeed or Red Gate SQL Backup Pro, you must install the
backup software on both the source and the validated sync environment. For backup software compatibility requirements, see Supporte
d Operating Systems, Server Versions, and Backup Software for SQL Server.

Windows Domain User Requirements

The Windows Domain user (for example, delphix_src) that the Delphix Engine uses on a source environment must also be enabled on the target
that hosts the staging databases for the source databases. This user must be a member of the Backup Operators or Administrators group on
the staging environment. This user must have Log on as a batch job rights on the Staging Server so the Delphix Engine can remotely execute
commands via Powershell.
Using the secpol.msc security policy editor, navigate to Local Policies > User Rights Assignment > Log on as a batch job to set this right
The Windows Domain user (for example, delphix_trgt) that the Delphix Engine uses on a validated sync environment must:
Meet all the requirements for the Windows user on a target host as outlined in Requirements for SQL Server Target Hosts and
Databases
Have SMB read access to the location holding the backup files of the source database

Related Links
Setting Up SQL Server Environments: An Overview
SQL Server Operating System Compatibility Matrices
Supported Operating Systems, Server Versions, and Backup Software for SQL Server
Requirements for SQL Server Target Hosts and Databases

374

Delphix User Guide 2016 Delphix

Supported Operating Systems, Server Versions, and Backup Software for SQL Server
This topic describes the versions of the Windows operating system and Microsoft SQL Server that Delphix supports.
Supported Versions of Windows OS
Supported Versions of SQL Server
Supported SQL Server Backup Software

Supported Versions of Windows OS

Windows Server 2003 SP2, 2003 R2
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012, 2012

R2

Delphix supports only 64-bit versions of Windows on target hosts and validated-sync-target hosts.
Target hosts and validated-sync-target hosts running Windows Server 2003 SP2 or 2003 R2 must install the hotfix documented in KB
943043.

For Windows 2008 R2

Updates NTFS.sys and uNTFS.dll

KB Article Number(s): 967351

Language: All (Global)

Platform: x64

Location: (http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix385766/7600/free/44135
1_intl_x64_zip.exe)

Updates MSISCI.sys

KB Article Number(s): 2277122

Language: All (Global)

Platform: x64

Location: (http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix388733/7600/free/44067
5_intl_x64_zip.exe)

375

Delphix User Guide 2016 Delphix

For Windows 2008 SP2

https://support.microsoft.com/en-us/kb/948275/
Ntfs.sys and untfs.dll for windows server 2008 SP2
In order to install NTFS.sys first go to c:\windows\system32\drivers, right click on ntfs.sys go to properties and check the tab
details In the details Tab check the file Version if the file version is less than 6.0.6002.22811 the one mentioned here
In order to install uNTFS.dll first go to c:\windows\system32, right click on untfs.dll go to properties and check the tab details In the
details Tab check the file Version if the file version is less than 6.0.6002.22811 the one mentioned here
Run the below mentioned commands.
Package: NTFS.sys and uNTFS.dll
--------------------------------------------------------------------------------------------------------------------KB Article Number(s): 967351
Language: All (Global)
Platform: x64
Location: (http://hotfixv4.microsoft.com/Windows%20Vista/sp3/Fix385798/6000/free/441782_intl_x64_zip.exe)

Download the file mentioned in the above link

Save the file in a folder named TEST under C drive.
Extract the zipped file.
Run the below mentioned command.

Expand -f:* c:\TEST\(write the complete details of the file with extension .msu).msu c:\TEST
Expand -f:* c:\TEST\(write the complete details of the file with extension .cab).cab c:\TEST
pkgmgr /ip /m:c:\Test\update-bf.mum

There are further restrictions on supported Windows and SQL Server versions for SQL Server Failover Cluster target environments.
See Adding a SQL Server Failover Cluster Target Environment for details.

Supported Versions of SQL Server

SQL Server Version

Delphix Version

SQL Server 2005 (9.0)

Delphix 3.x

SQL Server 2008 (10.0)

Delphix 3.x

SQL Server 2008 R2 (10.5)

Delphix 3.x

SQL Server 2012 (11.0)

Delphix 3.1.2 and beyond

SQL Server 2014 (12.0)

Delphix 4.1.3 and beyond

Delphix supports SQL Server AlwaysOn Availability Groups as a dSource but creation of a VDB on AlwaysOn Availability Groups is not
supported. Delphix

supports Windows Server Failover Cluster (WSFC) as a dSource and also as a target

(VDB).
Supported SQL Server Backup Software
The Delphix Engine interacts with source database backups in the following ways:

376

Delphix User Guide 2016 Delphix

When linking a new source database, the Delphix Engine can use an existing full backup to load the source database data
When performing a sync of an existing dSource, the Delphix Engine can use an existing full backup
After the dSource is created, the Delphix Engine picks up any new backups that are taken on the source database and applies them to
the copy of the source database on the Delphix Engine. This includes:
Transaction log backups for databases in Full or Bulk-Logged recovery models
Differential and full backups for databases in Simple recovery model
Delphix currently supports the following backup software for source database backups:
SQL Server native backups
Quest/NetVault LiteSpeed
If the source database is backed up with LiteSpeed, the source and the staging environments must have LiteSpeed installed on
them. The version of LiteSpeed on the staging environment must be the same or higher than that on the source. Delphix
currently supports LiteSpeed v5.0.0.0 to v8.x.
Red Gate SQL Backup Pro
If the source database is backed up with SQL Backup Pro, the source and the staging environments must have SQL Backup Pro
installed on them. The version of SQL Backup Pro on the staging environment must be the same as that on the source. Delphix
currently supports SQL Backup Pro v7.3 and onwards.

In versions 4.3.3.0 and newer Delphix supports encrypted backups; if you are running an older version of the Delphix Engine (v 4.3.2.x 3.0) encrypted backups are not supported.

377

Delphix User Guide 2016 Delphix

SQL Server Operating System Compatibility Matrices

The matrices in this topic illustrate the compatibility between various versions of SQL Server software used for source, staging target, and
provisioning target environments.

Source Environment OS Compatibility

Source environments can be running any supported Windows operating system version. There are no compatibility requirements between the
source environments operating system and that on the target environments.

Staging and Provisioning Target Environment OS Compatibility Matrix

The operating system version on the target environment that will contain the virtual databases should be equal to or higher than that on the
staging target. See Setting Up SQL Server Environments: An Overview for more information.

Provisioning Target Environment

Windows 2003 SP2/R2

Windows 2008 Windows 2008 R2

Windows 2012 Windows 2012 R2

Staging Target Environment

Windows 2003 SP2/R2

Windows 2008

Windows 2008 R2
Windows 2012
Windows 2012 R2

Source and Staging Environment SQL Server Compatibility Matrix

The SQL Server version on the staging environment should be equal to that on the source environment.

Staging Target Environment

SQL Server 2005

SQL Server 2008

SQL Server 2008 R2

SQL Server 2012

SQL Server 2014

Source Environment
SQL Server 2005

SQL Server 2008

SQL Server 2008 R2

SQL Server 2012

SQL Server 2014

Source and Provisioning Environment SQL Server Compatibility Matrix

When provisioning a VDB, the SQL Server version on the target can be equal to or higher than that on the source.

Provisioning Target Environment

SQL Server 2005

SQL Server 2008

SQL Server 2008 R2

SQL Server 2012

SQL Server 2014

Source Environment
SQL Server 2005
SQL Server 2008
SQL Server 2008 R2

X
X

378

Delphix User Guide 2016 Delphix

SQL Server 2012

SQL Server 2014

X
X

Provisioning to Higher SQL Versions When the Source is SQL Server 2005
For SQL Server 2005, direct provisioning to higher SQL Server versions is only supported for provisioning to SQL Server 2012 or
higher. You can first provision a VDB to SQL Server 2005 and then upgrade it to a higher version by following the steps outlined in the
topic Upgrading SQL Server VDBs.

379

Delphix User Guide 2016 Delphix

SQL Server Target Host iSCSI Configuration Parameter Recommendations

This topic describes Microsoft iSCSI Configuration Parameter Recommendations.
We recommend the following Microsoft iSCSI Initiator configuration parameters for target and staging hosts. See How to Modify the Windows
Registry on the Microsoft Support site for details about configuring registry settings.
A Windows Server reboot is required after changing iSCSI configuration parameters.

Registry Key

Registry Value

Type

Data

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\iSCSI\ MaxRequestHoldTime REG_DWORD 0x384 (900)

Discovery
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Disk

TimeoutValue

REG_DWORD 0x384 (900)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\

TcpAckFrequency

REG_DWORD 0x1 (1)

iSCSIDisableNagle

REG_DWORD 0x1 (1)

Interfaces\<Interface GUID>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\
{4D36E97B-E325-11CE-BFC1-08002BE10318}\<Instance Number>\Parameters

For systems running Windows 2003 see Microsoft Knowledge base article 815230 for hotfix information regarding changing
TcpAckFrequency.

380

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for SQL Server Environments

General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration
Connectivity Requirements for SQL Server Environments
Port Allocation for SQL Server Environments
Outbound from the Delphix Engine Port Allocation
Inbound to the Delphix Engine Port Allocation
Port Allocation Between Source and Staging Target Environments

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

381

Delphix User Guide 2016 Delphix

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

Connectivity Requirements for SQL Server Environments

For source environments, the Delphix Engine uses JDBC connections to the SQL Server instances on the source environment.
For target environments, Delphix uses a Delphix Connector connection to each target host from the Delphix Engine, and an iSCSI conn
ection from the target environment to Delphix Engine.
Between the source and target environments:
Delphix runs commands on a source environment through the Delphix Connector running on a target environment using SMB,
and SQL Server commands remotely over TCP from the target to the source environment.
During initial load, Delphix will take a full backup of the source database and direct the backup to go to a SMB share hosted on
the staging host from the source environment.
Delphix will attempt to access the source database's backups in the backup location from the staging target over SMB.

Port Allocation for SQL Server Environments

The following diagram describes the port allocations for SQL Server environments. It illustrates the ports that we recommend to be open from
Delphix to remote services, to the Delphix Engine, and to the Target Environments.

Refer to Setting Up SQL Server Environments: An Overview for information on SQL Server environments. The Delphix Engine makes use of
the following network ports for SQL Server dSources and VDBs:

Outbound from the Delphix Engine Port Allocation

Protocol

Port Numbers

Use

382

Delphix User Guide 2016 Delphix

TCP

9100

Delphix Connector connections to target environments

TCP

xxxx

JDBC Connections to the SQL Server instances on the source environments (typically port 1433)

Inbound to the Delphix Engine Port Allocation

Protocol

Port Number

Use

TCP

3260

iSCSI target daemon for connections from iSCSI initiators on the target environments to the Delphix Engine

Port Allocation Between Source and Staging Target Environments

Outgoing

Incoming

Protocol

Port
Number

Use

Source
Environment

Staging
Environment

SMB

445

Full backup of the source database during sync directed to the staging
environment

Staging
Environment

Source
Environment

SMB

445

1. Remote command execution on the source through Delphix Connector on

the target environment
2. Access to source database backups for restoring on the staging
environment

383

Delphix User Guide 2016 Delphix

Delphix as a Backup Solution to SQL Server

Using Delphix as a Backup Solution to SQL Server
Delphix provides you the option to automatically manage backups of your SQL Server source databases. Prior to this release, users could not link
source databases that were backed up by an unsupported backup software. In this release, we introduce a new feature that allows you to have
Delphix manage the backups for your databases. This is the first step in Delphix becoming a full-featured backup solution for MSSQL databases.
When the Delphix Engine manages the backups for a dSource, it takes regular, copy-only full backups of the source database, so activating the
feature will not interfere with existing backup management solutions. You can configure the schedule of when the Delphix Engine takes these
copy-only full backups by specifying a SnapSync policy for the dSource. You can change the SnapSync policy for a dSource at any time by
visiting the policy screen; there, you can either select a new SnapSync policy or modify the current one.
If you use a backup solution that is not supported by Delphix, you cannot use your existing backups to keep your dSources in sync. However,
enabling Delphix-managed backups will overcome this issue by using automatic copy-only full backups to keep dSources in sync. In the current
release, dSources linked when this feature is enabled will not support LogSync functionality, which means that you can only provision VDBs from
snapshots and not from any time between snapshots. Additionally, in the current release, the Delphix Engine cannot take differential or
transaction log backups of the source database.

Linking SQL Server dSources with Delphix Managed Backups

The Data Management tab of the link wizard for SQL Server dSources provides the option to enable Delphix
Managed Backups, as shown below:

It is only possible to enable this feature here at link time. Once a dSource has been linked, you cannot modify the use of this feature. If you enable
this feature, the dSource can only use Delphix-taken copy-only full backups to stay in sync with its source; the Delphix Engine will prohibit syncs
using existing backups. Checking the Enabled box results in the following changes to the Data Management page:
The initial load option is set to a Delphix-taken copy-only full backup
The ability to provide a backup path is removed
A SnapSync selection screen is added

You can select from the list of existing SnapSync policies, or click the green plus to create a new one. Proceeding through the remainder of the
link wizard will create a dSource with Delphix-managed backups enabled. You can confirm that a dSource has the feature by expanding its
dSource card and checking the Delphix Managed Backups section, as displayed below:

384

Delphix User Guide 2016 Delphix

Understanding SnapSync Policies

SnapSync policies provide you the ability to specify the frequency at which the Delphix Engine should take a copy-only full backup of a source
database. As shown in the section above, selecting an initial SnapSync policy is mandatory at dSource link time. However, you can change the
SnapSync policy applied on a dSource at any time by visiting the policy management screen:
1. Click Manage.
2. Click Policies.

For dSources that have Delphix-managed backups enabled, the current SnapSync policy will be displayed under the SnapSync column. The
rows corresponding to dSources that do not use Delphix-managed backups will be greyed out. Clicking the current SnapSync policy for a
dSource will display a drop-down menu of existing SnapSync policies along with the option to create a new SnapSync policy. Selecting a
SnapSync policy from this list will change the current SnapSync policy for the dSource. When creating a new policy, you will see the following
screen:

385

Delphix User Guide 2016 Delphix

Here, you can configure the frequency at which the Delphix Engine takes backups of your source database. You can modify these schedules at
any time by clicking the Modify Policy Templates button in the top right-hand corner of the policy management screen.
The Timeout field above specifies how long a SnapSync job is allowed to run before it is terminated. If a SnapSync job exceeds its timeout
window, the Delphix Engine discards the new backup and rolls back the dSource to the most recent snapshot.

386

Delphix User Guide 2016 Delphix

Managing SQL Server Environments

These topics describe special tasks and concepts for working with Windows environments containing SQL Server databases.
Setting Up SQL Server Environments: An Overview
Using HostChecker to Validate SQL Server Source and Target Environments
Adding a SQL Server Standalone Target Environment
Adding a SQL Server Source Environment
Changing the Host Name or IQN of a SQL Server Target or Staging Host
Editing SQL Server Environment Attributes
Managing SQL Server Environment Users
Deleting a SQL Server Environment
Refreshing a SQL Server Environment
Enabling Linking and Provisioning for SQL Server Environments
Adding a SQL Server Failover Cluster Target Environment

387

Delphix User Guide 2016 Delphix

Setting Up SQL Server Environments: An Overview

This topic describes the high-level process for adding SQL Server environments, linking SQL Server databases to the Delphix Engine, and
provisioning virtual databases.

Block Diagram of Linking Architecture between SQL Server Environments and the Delphix Engine

Block Diagram of SQL Server Provisioning Architecture

388

Delphix User Guide 2016 Delphix

The Delphix Connector and Environment Set Up

The Delphix Connector is a Windows service that enables communication between the Delphix Engine and the Windows target environment
where it is installed.
This target machine can serve three purposes in a Delphix Engine deployment. It can:
serve as a proxy for database discovery on source hosts
host a staging database for a linked dSource and run the validated sync process
host a target environment for the provisioning of Virtual Databases (VDBs)

389

Delphix User Guide 2016 Delphix

Database discovery is initiated during the environment set up process. When you specify a production source environment that contains the
databases you want to manage with the Delphix Engine, you must also specify a target environment where you have installed the Delphix
Connector to act as a proxy for communication with the source environment. This is necessary because Delphix does not require that you install
the Delphix Connector software on the production source environment. When you register the source environment with the Delphix Engine, the
Delphix Engine uses the Delphix Connector on the proxy environment to discover SQL Server instances and databases on the source. You can
then create dSources from the discovered databases. If you later refresh the source environment, the Delphix Engine will execute instance and
database re-discovery through the proxy host.
SQL Server dSources are backed by a staging database that runs on a target host, as shown in the diagram. There is no requirement for

At Delphix, we refer to the

creation and maintenance of this staging database on the staging host as "validated sync," because it prepares the
dSource data on the Delphix Engine for provisioning VDBs later on. After the Delphix Engine creates the staging
database, it continuously monitors the source database for new transaction log backups. When it detects a new
transaction log backup, it restores that backup to the staging database. The result is a TimeFlow with consistent
points from which you can provision a VDB, and a faster provisioning process, because there is no need for any
database recovery during provisioning.
additional local storage on this target host, as the storage is mounted over iSCSI from the Delphix Engine.

When you later provision a VDB, you can specify any environment as a target, including the environment that contains the staging database.
However, for best performance, Delphix recommends that you choose a different target environment. The only requirements for the target are:
it must have the Delphix Connector installed
it must have an operating system that is compatible with the one running on the validated host, as described in Requirements for SQL
Server Target Hosts and Databases

Workflow and Tasks for SQL Server Environments

1. Install the Delphix Connector on the standalone hosts that you will use as provisioning targets for VDBs and for the discovery and
validated sync processes, as described in Adding a SQL Server Standalone Target Environment.
2. Install the Delphix Connector on all cluster nodes of Windows Failover Clusters which you will use for provisioning targets for VDBs as
described in Adding a SQL Server Failover Cluster Target Environment.
3. Set up the Windows source environments using standalone target environments where you have installed the Delphix Connector as
proxies, as described in Adding a SQL Server Source Environment.
4. Link to the source database as described in Linking a SQL Server dSource.
5. Provision VDBs as described in Provisioning a SQL Server VDB.

Related Links
SQL Server Support and Requirements

390

Delphix User Guide 2016 Delphix

Using HostChecker to Validate SQL Server Source and Target Environments

What is HostChecker?
Prerequisites
Procedure to Validate Target Environments
Procedure to Validate Source Environments
Tests Run
Additional options
Related Links

What is HostChecker?
The HostChecker is a standalone program which validates that host machines are configured correctly before the Delphix Engine uses them as
data sources and provision targets.
Please note that HostChecker does not communicate changes made to hosts back to the Delphix Engine. If you reconfigure a host, you must
refresh the host in the Delphix Engine in order for it to detect your changes.
You can run the tests contained in the HostChecker individually, or all at once. You must run these tests on both the source and target hosts to
verify their configurations. As the tests run, you will either see validation messages that the test has completed successfully, or error messages
directing you to make changes to the host configuration.

Prerequisites
Make sure that your source and target environments meet the requirements specified in SQL Server Support and Requirements

Procedure to Validate Target Environments

1. Download and install the Delphix Connector as described in Adding a SQL Server Standalone Target Environment.
2. Login to the Windows target host using the Windows user account that will later be used to add the target.
3. Open Windows Powershell using the Run as Administrator option.
4. Execute the host checker script by running:
<Delphix Connector installation folder>\etc\dlpx-host-checker.ps1
5. Select a path where a report file will be saved, such as C:\temp\delphix-host-checker-report.txt.
6. Select the default option of Target Host.
7. Read the output of the checks.
8. The error or warning messages will explain any possible problems and how to address them. Resolve the issues that the HostChecker
describes. Do not be surprised or undo your work if more errors appear the next time you run HostChecker; the error you just fixed may
have been masking other problems.
9. Repeat steps 47 until all the checks return no errors or warnings.

Procedure to Validate Source Environments

1. Select the Windows target host which will be used as a proxy for discovering the source environment as described in Setting Up SQL
Server Environments: An Overview.
2. Login to the Windows target host using the Windows user account that will later be used to add the source environment.
3. Open Windows Powershell using the Run as Administrator option.
4. Execute the host checker script by running:
<Delphix Connector installation folder>\etc\dlpx-host-checker.ps1
5. Select a path where a report file will be saved, such as C:\temp\delphix-host-checker-report.txt.
6. Select the Source Host option.
7. Specify the host name or IP address of the source environment to verify.
8. Select ALL to discover all databases, or specify a single database to verify.
9. Specify the SQL Server database login and password that will later be used to add the source environment.
10. Read the output of the checks.
11. The error or warning messages will explain any possible problems and how to address them. Resolve the issues that the HostChecker
describes. Do not be surprised or undo your work if more errors appear the next time you run HostChecker; the error you just fixed may

391

Delphix User Guide 2016 Delphix

11.
have been masking other problems.
12. Repeat steps 49 until all the checks return no errors or warnings.

Tests Run
Test

MS SQL
Server
Source

MS
SQL Server
Target

Description

Check Powershell
Version

Verifies that Powershell 2.0 or greater is installed

Check OS User
Privileges

For target hosts, verifies that the the operating system (OS) user has administrative rights. For
source hosts, verifies that the OS user can successfully perform remote registry access from
the target host to the source host.

Check host
settings

Verifies that the Delphix Engine can discover host environment details from the Windows
registry

Check SQL Server

instance
discovery

Verifies that the Delphix Engine can discover SQL Server instances

Check SQL Server

instance login
permission

For target hosts, verifies that the Windows OS user can be used to log in to the SQL Server
instances. For source hosts, verifies that the supplied SQL Server login credentials can be
used to log in to the SQL Server instances.

Check database
discovery

Verifies that the Delphix Engine can discover SQL Server databases

Additional options
Run the following to view additional host checker options:
dlpx-host-checker.ps1 -?

Related Links
SQL Server Support and Requirements

392

Delphix User Guide 2016 Delphix

Adding a SQL Server Standalone Target Environment

This topic describes how to add a SQL Server standalone target environment to the Delphix Engine.
Prerequisites
Procedure
Post-Requisites
Related Links
As explained in Setting Up SQL Server Environments: An Overview, you can use SQL Server targets for three purposes in a Delphix Engine
deployment:
They can host a target environment for the provisioning of Virtual Databases (VDBs)
They can host a staging database for a linked dSource and run the validated sync process
They can serve as a proxy host for database discovery on source hosts
Regardless of the specific purpose, all Windows targets must have the Delphix Connector installed to enable communication between the host
and the Delphix Engine. The instructions in this topic cover initiating the Add Target process in the Delphix Engine interface, running the Delphix
Connector installer on the target machine, and then verifying that the target has been added in the Delphix Engine interface.

Prerequisites
Make sure that your target environment meets the requirements described in Requirements for SQL Server Target Hosts and
Databases.
On the Windows machine that you want to use as a target, you will need to download the Delphix Connector software through the
Delphix Engine interface, install it and then register that machine with the Delphix Engine.

Procedure
Flash Player Required for Connector Download
A Flash player must be available on the target host to download the Delphix Connector when using the Delphix GUI. If the target host
does not have a Flash player installed, you can download the connector directly from the Delphix Engine by navigating to this URL: ht
tp://<name of your Delphix Engine>/connector/DelphixConnectorInstaller.msi
1. From the machine that you want to use as a target, start a browser session and connect to the Delphix Engine GUI using the
delphix_admin login.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Windows in the operating system menu.
6. Select Target.
7. Select Standalone.
8. Click the download link for the Delphix Connector Installer.
The Delphix Connector will download to your local machine.
9. On the Windows machine that you want to want to use as a target, run the Delphix Connector installer. Click Next to advance through
each of the installation wizard screens.
The installer will only run on 64-bit Windows systems. 32-bit systems are not supported.

a. For Connector Configuration, make sure there is no firewall in your environment blocking traffic to the port on the target
environment that the Delphix Connector service will listen to.
b. For Select Installation Folder, either accept the default folder, or click Browse to select another.
c. Click Next on the installer final 'Confirm Installation' dialog to complete the installation process and then Close to exit the Delphix
Connector Install Program.
10. Return to the Delphix Engine interface.
11. Enter the Host Address, Username, and Password for the target environment.
12. Click Validate Credentials.
13. Click OK to complete the target environment addition request.

393

Delphix User Guide 2016 Delphix

13.
14. As the new environment is added, you will see two jobs running in the Delphix Admin Job History, one to Create and Discover an
environment, and another to Create an environment. When the jobs are complete, you will see the new environment added to the list in
the Environments panel.

Post-Requisites
1. On the target machine, in the Windows Start Menu, click Services.
2. Select Extended Services.
3. Ensure that the Delphix Connector service has a Status of Started.
4. Ensure that the Startup Type is Automatic.

Related Links
Setting Up SQL Server Environments: An Overview
Requirements for SQL Server Target Hosts and Databases

394

Delphix User Guide 2016 Delphix

Adding a SQL Server Source Environment

This topic describes how to add a SQL Server source environment.

Prerequisites
You must have already set up SQL Server target environments, as described in Adding a SQL Server Standalone Target
Environment
You will need to specify a target environment that will act as a proxy for running SQL Server instance and database discovery on
the source, as explained in Setting Up SQL Server Environments: An Overview
Make sure your source environment meets the requirements described in Requirements for SQL Server Target Hosts and Databases

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Windows in the operating system menu.
6. Select Source.
a. If you are adding a Windows Server Failover Cluster (WSFC), add the environment based on which WSFC feature the source
databases use:
i. Failover Cluster Instances
Add the environment as a standalone source using the cluster name or address.
ii. AlwaysOn Availability Groups
Add the environment as a cluster source using the cluster name or address.
b. Otherwise, add the environment as a standalone source.
7. Select a Connector Environment.
Connector environments are used as proxy for running discovery on the source. If no connector environments are available for selection,
you will need to set them up as described in Adding a SQL Server Standalone Target Environment. Connector environments must:
have the Delphix Connector installed
be registered with the Delphix Engine from the host machine where they are located.
8. Enter the Host Address, Username, and Password for the source environment.
9. Click Validate Credentials.
10. Click OK, and then click Yes to confirm the source environment addition request.
As the new environment is added, you will see multiple jobs running in the Delphix Admin Job History to Create and Discover an
environment. In addition, if you are adding a cluster environment, you will see jobs to Create and Discover each node in the cluster and
their corresponding hosts. When the jobs are complete, you will see the new environment added to the list in the Environments panel. If
you don't see it, click the Refresh icon.

Related Links
Setting Up SQL Server Environments: An Overview
Adding a SQL Server Standalone Target Environment
Adding a SQL Server Failover Cluster Target Environment
Requirements for SQL Server Target Hosts and Databases

395

Delphix User Guide 2016 Delphix

Changing the Host Name or IQN of a SQL Server Target or Staging Host
This topic describes how to change the host name or iSCSI Qualified Name (IQN) of a Windows target or staging host.
By default, Windows servers generate an IQN based on the host name assigned to the host. Changing the host name will change the host IQN as
well. Because the Delphix Engine exports storage for dSources and VDBs to Windows hosts using iSCSI, changes to the Windows host name
must be made according to the following procedure. If you have set a non-default IQN on a Windows target or staging host, and want to change
that IQN, you must follow these procedures when changing the IQN.
Changing the host name or IQN of a Windows target or staging server requires that you modify the iSCSI Initiator configuration on the
Windows host. Doing so incorrectly can cause failures in dSources, VDBs, or non-Delphix users of iSCSI on the Windows host.
The instructions in this topic describe how to change the IQN using the iscsicli command line utility. Because many people are less
familiar with the iscsicli utility, the instructions also include information for using the iSCSI Initiator graphical user interface.
Failing to carefully follow the steps below in order can cause availability issues for your dSources and VDBs. If you have questions
about the following instructions, please contact Delphix Support for help.

Procedure
1. Disable the dSources as described in Enabling and Disabling dSources.
2. Disable the VDBs as described in Enabling and Disabling Virtual Databases.
If your Windows server has dSources or VDBs from more than one Delphix Engine, you will need to disable the dSources and
VDBs on each Delphix Engine.

3. Remove any remaining persistent volumes from the Windows server.

In the iSCSI Initiator configuration tool, use the options available in the Volumes and Devices tab.
Follow these steps to use the iscsicli command line utility:
a. List the persistent volumes

PS C:\> iscsicli reportpersistentdevices

Microsoft iSCSI Initiator Version 6.1 Build 7601
Persistent Volumes
"\\?\storage#volume#{bb38add1-d03f-11e1-8767-005056b37fe6}#0000000008010000#{5
3f5630d-b6bf-11d0-94f2-00a0c91efb8b}"
"C:\Program
Files\Delphix\DelphixConnector\564d6fbb-df9d-e90b-00f1-da37b17011d3-staging-15
\ARCHIVE\"
[...]
The operation completed successfully.
b. Volumes with a "normal" path correspond to mounted volumes. For example, "C:\Program Files\Delphix is a normal path.
If you see any normal paths in the output, be sure you have disabled all of the VDBs and dSources.
c. Volumes with a path beginning "\\?\ correspond to unmounted persistent volumes. Remove each of them:

PS C:\> iscsicli RemovePersistentDevice

"\\?\storage#volume#{bb38add1-d03f-11e1-8767-005056b37fe6}#0000000008010000#{5
3f5630d-b6bf-11d0-94f2-00a0c91efb8b}"
d. Alternately, if all of the persistent devices are for unmounted volumes, you can remove them all at once with this command:

PS C:\> iscsicli clearpersistentdevices

4. Remove all of the persistent targets.
In the iSCSI Initiator configuration tool, use the options available in the Favorite Targets tab.
Follow these steps to use iscsicli command line utility:
a. List persistent targets:

396

Delphix User Guide 2016 Delphix

a.

PS C:\> iscsicli ListPersistentTargets

b. Remove the appropriate persistent targets. Below is sample output listing the persistent targets:

PS C:\> iscsicli ListPersistentTargets

[...]
Target Name
:
iqn.2008-07.com.delphix:02:02843619-12c4-e4d2-8041-f5c56a647bc2
Address and Socket
: 10.43.5.45 3260
Session Type
: Data
Initiator Name
: Root\ISCSIPRT\0000_0
Port Number
: <Any Port>
Security Flags
: 0x0
Version
: 0
Information Specified: 0x20
Login Flags
: 0x0
Username
:
[...]
Misleading Help for RemovePersistentTarget Command
The help for iscsicli RemovePersistentTarget is misleading:

iscsicli RemovePersistentTarget <Initiator Name> <TargetName>

<Port Number>
<Target Portal Address>
<Target Portal Socket>
<Initiator Name> and <Target Name> show up in the listing and should be taken directly from there.
<Port Number> can be taken from the listing output, but a * should be used if <Any Port> is listed.
<Target Portal Address> and <Target Portal Socket> are shortened to Address and Socket in the Li
stPersistentTargets output. The term Socket in both places is what is more typically referred to as a port.
Use the RemovePersistentTarget command to remove the target, as shown in this example:

PS C:\> iscsicli RemovePersistentTarget Root\ISCSIPRT\0000_0

iqn.2008-07.com.delphix:02:02843619-12c4-e4d2-8041-f5c56a647bc2 * 10.43.5.45
3260
5. Log out of any sessions.
In the iSCSI Initiator configuration tool, use the options available in the Targets tab to log out. Selected a connected session under Disco
vered Targets, and then click Disconnect.
Follow these steps to use the iscsicli command line utility :
a. List the sessions:

PS C:\> iscsicli sessionlist

Session Id : fffffa8003fb0018-4000013700000001
Initiator Node Name : iqn.1991-05.com.microsoft:10-43-1-200.ad.delphix.com
Target Node Name : (null)
Target Name : iqn.2008-07.com.delphix:02:02843619-12c4-e4d2-8041-f5c56a647bc2
[...]
b. Log out from the target:

PS C:\> iscsicli logouttarget fffffa8003fb0018-4000013700000001

6. Change the host name or IQN
a. If you are changing the host name, follow the instructions in the Microsoft TechNet article "Rename the Computer."
Note that if the computer is on a domain, you will need a domain administrator to perform the rename or re-add the

397

a.

Delphix User Guide 2016 Delphix

computer to the domain depending on the version of Windows it is running.

b. If you are changing the IQN only, change it through the Microsoft iSCSI Initiator GUI following the instructions in the Microsoft
iSCSI User Guide.
7. Wait for the computer to finish rebooting.
8. Verify the new IQN in the iSCSI initiator.
If you are using the default IQN and have changed the host name, the IQN should include the new host name.

9. Refresh the environment on the Delphix Engine.

10. Re-enable the dSources as described in Enabling and Disabling dSources.
11. Re-enable the VDBs as described in Enabling and Disabling Virtual Databases.
12. Using the iscsicli command line utility, verify that the sessions on the Windows server are using the new IQN:

PS C:\> iscsicli sessionlist

Microsoft iSCSI Initiator Version 6.1 Build 7601
Total of 1 sessions
Session Id : fffffa8003f77018-4000013700000004
Initiator Node Name : <NEW IQN>
[...]

Related Links
Enabling and Disabling dSources
Microsoft TechNet article "Renaming the Computer"
Microsoft iSCSI User Guide (download)

398

Delphix User Guide 2016 Delphix

Editing SQL Server Environment Attributes

Procedure
Common Editable Attributes
SQL Server Attributes
This topic describes how to edit attributes of an environment such as name, host address, ssh port, or toolkit path, as well as descriptions of more
advanced attributes for specific data platforms.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials or as the owner of an environment.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of an environment to view its attributes.
5. Under Attributes, click the Pencil icon to edit an attribute.
6. Click the Check icon to save your edits.

Common Editable Attributes

Attribute

Description

Environment
Users

The users for that environment. These are the users who have permission to ssh into an environment, or access the
environment through the Delphix Connector. See the Requirements topics for specific data platforms for more information on
the environment user requirements.

Host
Address

The IP address for the environment host.

Notes

Any other information you want to add about the environment.

SQL Server Attributes

Attribute

Description

Delphix
Connector Port

For target environments, the port used for communication with the Delphix Connector. See Setting Up SQL Server
Environments: An Overview for more information.

Connector
Host

The host where the Delphix Connector is installed. See Setting Up SQL Server Environments: An Overview and Adding a
SQL Server Target Environment for more information.

399

Delphix User Guide 2016 Delphix

Managing SQL Server Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure

Prerequisites
Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

400

Delphix User Guide 2016 Delphix

Deleting a SQL Server Environment

This topic describes how to delete an environment.

Prerequisites
You cannot delete an environment that has any dependencies, such as dSources or virtual databases (VDBs). These must be deleted before you
can delete the environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, select the environment you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

401

Delphix User Guide 2016 Delphix

Refreshing a SQL Server Environment

This topic describes how to refresh an environment.
After you make changes to an environment that you have already set up in the Delphix Admin application, such as installing a new database
home, creating a new database, or adding a new listener, you may need to refresh the environment to reflect these changes.
During environment discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the
toolkit are:
A JRE
Delphix jar files
The hostchecker utility
Scripts for managing the environment and/or VDBs
Delphix Connector log files
Delphix then executes some of these scripts to discover information about the objects in your environment (where the databases are installed,
the database names, information required to connect to these databases, etc.). In some environments (Windows in particular), the scripts are
customized to fit the customers environment.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of the environment to you want to refresh.
5. Click the Refresh icon.
To refresh all environments, click the Refresh icon next to Environments.

402

Delphix User Guide 2016 Delphix

Enabling Linking and Provisioning for SQL Server Environments

This topic describes how to enable and disable staging, provisioning, and linking for databases.
Before you can use a database as a dSource, you must first make sure that you have defined a staging environment and enabled linking to it.
Similarly, before you can provision a virtual database (VDB) to a target database, you must make sure that you have enabled provisioning to
it.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. To enable or disable staging, slide the button next to Use as Staging to Yes or No.
6. To enable or disable provisioning, slide the button next to Allow Provisioning to On or Off.

403

Delphix User Guide 2016 Delphix

Adding a SQL Server Failover Cluster Target Environment

This topic describes how to add a SQL Server Failover Cluster target environment to the Delphix Engine.
Adding a Failover Cluster target environment will discover SQL Server Failover Cluster instances that are running. You can then provision VDBs
to these Failover Cluster instances.

Prerequisites
You must add each node in the Window Failover Cluster individually as a standalone target environment using a non-cluster address.
See Adding a SQL Server Standalone Target Environment.

A cluster node added as a standalone environment will only have non-clustered SQL Server instances
discovered.
A cluster target environment will only have SQL Server Failover Cluster instances discovered.
Each clustered SQL Server instance must have at least one clustered disk added to the clustered instance resource group which can be
used for creating mount points to Delphix storage.
The clustered drive must have a drive letter assigned to it.
The clustered drive must be formatted using the "GUID Partition Table (GPT)" partition style.
Each node in the cluster must have the Failover Cluster Module for Windows Powershell feature installed.
An additional target environment that can be used as a Connector Environment must exist. This environment must NOT be a node in
the cluster. See Adding a SQL Server Standalone Target Environment.
Hotfix required for Windows 2008 R2 hosts
The following hotfix is required for Windows 2008 R2 Cluster nodes:
"0x80070490 Element Not found" error when you enumerate a cluster disk resource by using the WMI MSCluster_Disk class
query in a Windows Server 2008 R2-based failover cluster
http://support.microsoft.com/kb/2720218

Best Practices
SQL Server failover cluster instances that will be used with Delphix should not be used to host databases other than Delphix VDBs.

Cluster environment restrictions

Failover Cluster target environments cannot be used as staging environments.

Supported Operating System and SQL Server Versions for Cluster Target Environments
Supported Operating System Versions
Windows 2008 R2
Windows 2012
Windows 2012 R2
Supported SQL Server Versions
SQL Server 2008 (10.0)
SQL Server 2008 R2 (10.5)
SQL Server 2012 (11.0)
SQL Server 2014 (12.0)

Procedure
1. Click Manage.
2. Select Environments.
3.
404

Delphix User Guide 2016 Delphix

3. Next to Environments, click the green Plus icon.

4. In the Add Environment dialog, select Windows in the operating system menu.
5. Select Target.
6. Select Cluster.
7. Specify the cluster address of the Windows Failover Cluster.
8. Select a host which is NOT a node in the cluster as the Connector Environment.
9. Enter the Username and Password for the target environment.
10. Click Validate Credentials.
11. Click OK.
12. Click Yes to confirm the target environment addition request.
In the Delphix Engine interface, you will see a new icon for the Target environment, and two jobs running in the Delphix Admin Job
History, one to Create and Discover an environment, and another to Create an environment. When the jobs are complete, click the icon
for the new environment, and you will see the details for the environment.

Example Environment

In this example environment, the Delphix Connector was installed on Connector Environment, Cluster Node 1, and Cluster Node 2. Each host
was added to Delphix as standalone target environments. Next, the Windows Failover Cluster was added as a Windows Target Cluster
environment using the cluster address. Cluster Node 1 is currently the active node for the SQL Server Failover Cluster resource group. Delphix
has exported iSCSI LUs and has created the corresponding Cluster Disk resources for each VDB.

Related Links
Setting Up SQL Server Environments: An Overview
Adding a SQL Server Standalone Target Environment
Adding a SQL Server Source Environment
Requirements for SQL Server Target Hosts and Databases

405

Delphix User Guide 2016 Delphix

Managing SQL Server Data Sources

These topics describe special tasks and concepts for linking SQL Server dSources.
Linking a dSource from a SQL Server Database: An Overview
Linking a SQL Server dSource
Upgrading a dSource after a SQL Server Upgrade
Migrating a SQL Server Staging Database
Changing the Staging Target Environment for a SQL Server dSource
Advanced Data Management Settings for SQL Server dSources
Enabling and Disabling SQL Server dSources
Detaching and Re-Attaching SQL Server dSources
Deleting a SQL Server dSource
Provisioning from a Replicated SQL Server dSource
SQL Server dSource Icon Reference

406

Delphix User Guide 2016 Delphix

Linking a dSource from a SQL Server Database: An Overview

This topic describes basic concepts behind the creation of dSources from SQL Server databases.
When you create a dSource from a SQL Server database, the initial snapshot is derived from a full or differential database backup of the source
database. The database backup can be a new full database backup initiated by the Delphix Engine, the most recent existing database backup, or
a specific existing database backup as identified by its backup_set_uuid. When loading from an existing backup, the backup should be in a
location that is accessible over SMB by both the staging target's environment user and the Windows user running the SQL Server instance on the
staging host, as shown in the diagram in Setting Up SQL Server Environments: An Overview.
After obtaining the initial snapshot and linking the dSource, the Delphix Engine keeps the dSource and the source database in sync by monitoring
the source database for new backups, and then using those backups to perform a restore on the staging database, as described in Setting Up
SQL Server Environments: An Overview. If the source database is in full or bulk-logged recovery model, the Delphix Engine monitors and
applies new transaction log backups. If the source database is in simple recovery model, the Delphix Engine monitors and applies new full and
differential database backups.
After you have linked a database into the Delphix Engine, you can re-initialize it by performing a sync on the dSource. Performing a sync restores
a database backup, which can be a new full database backup taken by the Delphix Engine, the most recent full or differential database backup, or
a specific full or differential backup as identified by its backup_set_uuid.
Simple Recovery Model
If the source database is using simple recovery model, using a new full database backup taken through the Delphix Engine is not
supported for initial load and sync of a dSource.
The Delphix Engine supports source database backups that SQL Server creates natively, as well as backups created by Quest/Netvault
LiteSpeed and Red Gate SQL Backup Pro. For more information, see the topic Supported Operating Systems, Server Versions, and Backup
Software for SQL Server.

Related Topics
Setting Up SQL Server Environments: An Overview
Supported Operating Systems, Server Versions, and Backup Software for SQL Server

407

Delphix User Guide 2016 Delphix

Linking a SQL Server dSource

This topic describes how to link a dSource from a Microsoft SQL Server database.
Prerequisites
Procedure
Related Links

Prerequisites
Be sure that the source database meets the requirements described in Requirements for SQL Server Target Hosts and Databases
You must have already set up a staging target environment as described in Setting Up SQL Server Environments: An Overview and A
dding a Windows Target Environment
Maximum Size of a Database that Can Be Linked
If the staging environment uses the Windows 2003 operating system, the largest size of database that you can link to the
Delphix Engine is 2TB. This is also the largest size to which a virtual database (VDB) can grow.
For all other Windows versions, the maximum size for databases and VDBs is 32TB.
In both cases, the maximum size of the database and resulting VDBs is determined by the operating system on the staging target host.

Failover cluster environments cannot be used for staging

When linking a dSource, you cannot use SQL Server failover cluster instances as staging instances. When linking, select a standalone
SQL Server instance to use.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials or as the owner of the database from which you want to
provision the dSource.
2. Click Manage.
3. Select Databases.
4. Select Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing SQL Server Environment Users.

6. Enter your login credentials for the source database.

7. Click Verify Credentials.
8. Click Next.
9. Select a Database Group for the dSource.
10. Click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies .
If your data source name contains non-ASCII characters, you will need to change the default dSource name to something that
uses only ASCII characters.

11. Select the method for the Initial Load.

For details on initial load options, see Linking a dSource from a SQL Server Database: An Overview .
12. Enter a backup path from which the source database backups will be available for the Delphix Engine to restore. A backup path follows
a UNC naming convention as: \\hostname\sharename\possible additional directory
Alternatively, select Autodiscover to have the Delphix Engine automatically locate the backups by querying MSDB.
13. Select the target environment for creating the staging database for validated sync.
14.
408

Delphix User Guide 2016 Delphix

14. Select a standalone SQL Server instance on the target environment for hosting the staging database.
15. Select whether the data in the database is Masked.
16. Select whether you want LogSync enabled for the dSource. For more information, see Advanced Data Management Settings for SQL
Server dSources.
LogSync Disabled by Default
For SQL Server data sources, LogSync is disabled by default. For more information about how LogSync functions with SQL
Server data sources, see Managing SQL Server Data Sources.

17. Cl ick Advanced to edit retention policies and specify pre- and post-scripts. For details on pre- and post-scripts, refer to Customizing
SQL Server Management with Pre- and Post-Scripts. Additionally, if the source database's backups use LiteSpeed or RedGate
password protected encryption, you can supply the encryption key the Delphix Engine should use to restore those backups.
18. Click Next.
19. Review the dSource Configuration and Data Management information.
20. Click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync. You can monitor these jobs by clicking Active Jobs in
the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the database icon will change to a dSou
rce icon on the Environments > Databases screen, and the dSource will appear in the list of My Databases under its assigned group.
You can view the current state of Validated Sync for the dSource on the dSource card itself.
The dSource Card
After you have created a dSource, the dSource card allows you to view information about it and make modifications to its policies and
permissions. In the Databases panel, click the Open icon to view the front of the dSource card. You can then flip the card to see
information such as the Source Database and Data Management configuration. For more information, see the topic Advanced Data
Management Settings for SQL Server dSources.

Related Links
Users, Permissions, and Policies
Setting Up SQL Server Environments: An Overview
Linking a dSource from a SQL Server Database: An Overview
Advanced Data Management Settings for SQL Server dSources
Adding a SQL Server Standalone Target Environment
Requirements for SQL Server Target Hosts and Databases
Using Pre- and Post-Scripts with SQL Server dSources

409

Delphix User Guide 2016 Delphix

Upgrading a dSource after a SQL Server Upgrade

This topic describes how to upgrade dSources after an SQL Server database upgrade.

Prerequisites
The source SQL Server database has been upgraded by attaching to a higher version of SQL Server instance.

Procedure
1. Refresh all environments.
2. Log into the Delphix Admin application using delphix_admin credentials.
3. Select Manage > Databases > My Databases.
4. Disable the dSource to be upgraded.
5. Click the Expand icon to open its card.
6. Click the crown icon on the bottom of the dSource card.
The Upgrade Database screen will open. The new instance should appear in the dropdown list. If it does not, go to Manage->Environm
ents, select a card with the environment containing the new instance, and click Refresh Environment on that card.
7. Select the new SQL Server instance that the source database is attached to.
8. Select the appropriate staging environment and instance. The staging instance must be the same version as the new SQL Server
instance.
9. Click OK.
10. Enable the dSource.
11. Click Snapshot on the dSource card to run SnapSync for the dSource.

Related Links
Refreshing an Environment
Linking a SQL Server dSource
Enabling and Disabling dSources

410

Delphix User Guide 2016 Delphix

Migrating a SQL Server Staging Database

This topic describes how to migrate a SQL Server staging database to a different environment. For an overview of what a staging database is
used for, see Setting Up SQL Server Environments: An Overview .

Prerequisites
The dSource for the staging database has to be disabled first before the migration. Follow the steps in Enabling and Disabling
dSources to disable the dSource.
The target environment for the migrated staging database should already have been added to the Delphix Engine. Follow the steps in Ad
ding a SQL Server Standalone Target Environment to add the environment as a target environment. The environment should also
meet the requirements for hosting a staging database as described in Requirements for SQL Server Target Hosts and Databases.

Procedure
1. Go to Manage > Database > My Databases
2. Select the dSource for the staging source.
3. Modify the Staging Environment for the dSource by clicking the Pencil icon next to it.
4. Select the new target environment for the staging source.
5. Select the SQL Server instance on the new target environment.
6. Accept the change.

Post-Requisites
Enable the dSource following the steps outlined in Enabling and Disabling dSources.

Related Links
Setting Up SQL Server Environments: An Overview
Adding a SQL Server Standalone Target Environment
Enabling and Disabling dSources
Requirements for SQL Server Target Hosts and Databases

411

Delphix User Guide 2016 Delphix

Changing the Staging Target Environment for a SQL Server dSource

This topic describes how to change the staging target environment for a SQL Server dSource.

Prerequisites
The dSource for the staging database must be disabled before the staging target environment can be changed. Follow the steps in Enabling and
Disabling dSources to disable the dSource.

Procedure
1. In the Databases pane, select the dSource for which you want to change the staging target environment.
2. Click the Open icon for the dSource to view its information card.
3. On the front of the information card, click the Flip icon to view the Staging Environment on the back of the dSource card.
4. Click the Pencil icon next to Staging Environment to edit the target server and the SQL Server instance on the server to use for
staging.
5. Click the Check icon to save your changes.

412

Delphix User Guide 2016 Delphix

Advanced Data Management Settings for SQL Server dSources

Accessing Data Management Settings
During the dSource linking process
On the back of the dSource card
In the top menu bar
Retention Policies
Benefits of Longer Retention
LogSync for SQL Server dSources
Configuring Encryption Keys for SQL Server dSources
Related Links
This topic describes advanced data management settings for dSources.
When linking a dSource, you can use custom data management settings to improve overall performance and match the needs of your specific
server and data environment. If no specific settings are required, leverage default data management settings.

Accessing Data Management Settings

There are three ways to set or modify data management settings for dSources:
During the dSource linking process

1. In the Data Management panel of the Add dSource wizard, click Advanced.
On the back of the dSource card

1. Under Data Management, click the field next to Retention Policy

2. Click the Edit icon.
3. For SnapSync and Retention policies, click the policy name. This will open the Policy Management screen.
In the top menu bar

1. Click Manage.
2. Select Policies. This will open the Policy Management screen.
3. Select the policy for the dSource you want to modify.
4. Click Modify.
For more information, see Creating Custom Policies and Creating Policy Templates.

Retention Policies
Retention policies define the length of time that the Delphix Engine retains snapshots and log files to which you can rewind or provision objects
from past points in time. The retention time for snapshots must be equal to, or longer than, the retention time for logs.
To support longer retention times, you may need to allocate more storage to the Delphix Engine. The retention policy in combination with the
SnapSync policy can have a significant impact on the performance and storage consumption of the Delphix Engine.

Benefits of Longer Retention

With increased retention time for snapshots and logs, you allow a longer (older) rollback period for your data.
Common use cases for longer retention include:
SOX compliance
Frequent application changes and development
Caution and controlled progression of data
Reduction of project risk
Speed of rollback / restore to older points in time
With LogSync enabled, you can customize both the retention policy and the SnapSync policy to access logs for longer periods of time, enabling
point-in-time rollback and provisioning.

413

Delphix User Guide 2016 Delphix

LogSync for SQL Server dSources

LogSync is disabled by default for SQL Server dSources, because snapshots are triggered by transaction log backups of the source database
that you take, rather than by SnapSync policies. On average, the Delphix Engine takes transaction log backups every 30 minutes to an hour,
resulting in frequent snapshots.
You should enable LogSync if you need to be able to provision to a finer granularity than is possible using transaction log backups. LogSync adds
log files from the source database to the dSource, allowing you to provision a virtual database (VDB) from a specific point in time or LSN for SQL
Server databases. LogSync must be enabled for this provisioning functionality to work.
Enabling LogSync will increase the storage required for the dSource on the Delphix Engine, because the Delphix Engine will start storing the
transaction log backups according to the log retention policy.
LogSync settings are accessible during the Add dSource process and on the back of the dSource card.

Configuring Encryption Keys for SQL Server dSources

If the source database's backups use RedGate or LiteSpeed password-protected encryption, then the Delphix Engine requires the corresponding
encryption key in order to restore the backup.
Encryption key settings are accessible during the Add dSource process and on the back of the dSource card.
Encryption keys are only required to restore LiteSpeed or RedGate password protected backups
The Delphix Engine only requires an encryption key when restoring LiteSpeed or RedGate password-protected backups. If encryption is
configured using asymmetric keys or certificates, then you do not need to specify an encryption key.

Related Links
Managing SQL Server Data Sources

414

Delphix User Guide 2016 Delphix

Enabling and Disabling SQL Server dSources

This topic describes how to enable and disable dSources for operations such as backup and restore.
For certain processes, such as backing up and restoring the source database, you may want to temporarily disable your dSource. Disabling a
dSource turns off communication between the dSource and the source database, but does not tear down the configuration that enables
communication and data updating to take place. When a disabled dSource is later enabled, it will resume communication and incremental data
updates from the source database according to the original policies and data management configurations that you set.
Disabling a dSource is also a prerequisite for several other operations, like database migration and upgrading the dSource after upgrade of the
associated data source.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the dSource you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the dSource again, move the slider control from Disabled to Enabled, and the dSource will continue to function as
it did previously.

415

Delphix User Guide 2016 Delphix

Detaching and Re-Attaching SQL Server dSources

This topic describes how to detach dSources and re-attach them to a different source database.
Each dSource contains an association with the source database, as well as the data it has pulled from the source database up to that point. It is
possible to detach, or unlink, a dSource from its source database. This breaks the association with the source database without affecting the data
within the Delphix Engine. Detached dSources and their source databases have these properties:
You can use detached dSources as the source of virtual database (VDB) provisioning operations.
You can re-link the source database as a different dSource.

Detaching a dSource
1. Login to the Delphix Admin application as a user with OWNER privileges on the dSource, group, or domain.
2. Click Manage.
3. Select My Databases.
4. Select the database you want to unlink or delete.
5. Click the Unlink icon.
A warning message will appear.
6. Click Yes to confirm.

Attaching a dSource
Rebuilding Source Databases and Using VDBs
In situations where you want to rebuild a source database, you will need to detach the original dSource and create a new one
from the rebuilt data source. However, you can still provision VDBs from the detached dSource.
1. Detach the dSource as described above.
2. Rename the detached dSource by clicking the Edit icon in the upper left-hand corner of the dSource card, next to its
name.
This is necessary only if you intend give the new dSource the same name as the original one. Otherwise, you will see
an error message.
3. Create the new dSource from the rebuilt database.
You will now be able to provision VDBs from both the detached dSource and the newly created one, but the detached dSource
will only represent the state of the source database prior to being detached.

The attach operation is currently only supported from the command line interface (CLI). Full GUI support will be added in a future release. Only
databases that represent the same physical database can be re-attached
1. Login to the Delphix CLI as a user with OWNER privileges on the dSource, group, or domain.
2. Select the dSource by name using database select <dSource>.
3. Run the attachSource command.
4. Set the source config to which you want to attach using set source.config=<newSource>. Source configs are named by their
database unique name.
5. Set any other source configuration operations as you would for a normal link operation.
6. Run the commit command.

416

Delphix User Guide 2016 Delphix

Deleting a SQL Server dSource

This topic describes how to delete a dSource.

Prerequisites
You cannot delete a dSource that has dependent virtual databases (VDBs). Before deleting a dSource, make sure that you have deleted all
dependent VDBs as described in Deleting a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the Databases panel, select the dSource you want to delete.
6. Click the Trash Can icon.
7. Click Yes to confirm.

Deleting a dSource will also delete all snapshots, logs, and descendant VDB Refresh policies for that database. You cannot
undo the deletion.

417

Delphix User Guide 2016 Delphix

Provisioning from a Replicated SQL Server dSource

This topic describes how to provision from a replicated dSource or virtual database (VDB). The process for provisioning from replicated objects is
the same as the typical VDB provisioning process, except that first you need to select the replica containing the replicated object.
Prerequisites
Procedure
Post-Requisites

Prerequisites
You must have replicated a dSource or a VDB to the target host, as described in Replication Overview.
You must have added a compatible target environment on the target host.

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB you want to provision.
6. The provisioning process is now identical to the process for provisioning standard objects.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

418

Delphix User Guide 2016 Delphix

SQL Server dSource Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

419

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

420

Delphix User Guide 2016 Delphix

Provisioning VDBs from SQL Server dSources

These topics describe special tasks and concepts for provisioning VDBs from SQL Server dSources.
Provisioning SQL Server VDBs: An Overview
Provisioning a SQL Server VDB
File Permissions for SQL Server VDBs
Extended Properties for SQL Server VDBs
Upgrading SQL Server VDBs
Migrating a SQL Server VDB
Renaming a SQL Server VDB
Rewinding a SQL Server VDB

421

Delphix User Guide 2016 Delphix

Provisioning SQL Server VDBs: An Overview

This topic describes the basic concepts involved with provisioning VDBs from SQL Server dSources.
A dSource is a virtualized representation of a physical or logical source database. As a virtual representation, it cannot be accessed or
manipulated using database tools. Instead, you must create a Virtual Database (VDB) from a dSource snapshot. A VDB is an independent,
writeable copy of a dSource snapshot. You can also create VDBs from other VDBs. Once a VDB has been provisioned to a target environment,
you can also implement a snapshot policy for that VDB, to capture changes within it as if it were any other logical or physical database.
When provisioning a VDB, Delphix creates the database with the default SQL Server database options. If the database options have been altered
on the source database and you wish for the VDB to reflect these same options, they would need to be altered via a Post-Script.
For an overview of the high-level components involved in provisioning a SQL Server VDB refer to Setting Up SQL Server Environments: An
Overview.

Validated Sync and LogSync

When you link a source database into Delphix, you must also specify a target environment that will host a staging database for the validated sync
process, as described in Setting Up SQL Server Environments: An Overview. In this process, the Delphix Engine continuously monitors the
source database for new transaction log backups. When it detects one, it restores that backup to the staging database. The result is a TimeFlow
with consistent points from which you can provision a VDB, also known as snapshots.
Snapshots accumulate over time, and are available when you select the dSource in the My Databases panel of the Delphix Admin application.
Each snapshot is represented as a card that includes information about the source database, operating system, end stamp, and
snapshot database change number (SCN for Oracle and LSN for SQL Server). You can scroll through these cards to select the one you want, or
enter a date and time to search for a specific snapshot.
If LogSync is enabled, you will also see a LogSync slider control at the top of the snapshot card. If you slide this control to the right to open
LogSync, you will see a pointer that you can move along a timeline to select the exact time from which you want to provision a VDB.

Once a VDB has been provisioned, you can also take snapshots of it. As with the dSource snapshots, you can find
these when you select the VDB in the My Databases panel. You can then provision additional VDBs from these
VDB snapshots.
SQL Server and SAP ASE VDBs do not have LogSync support. You can only provision from VDB snapshots.

Dependencies
If there are dependencies on the SnapShot you will not be able to delete the SnapShot free space; the dependencies rely on the data
associated with the SnapShot.

Related Links
Setting Up SQL Server Environments: An Overview
Provisioning a SQL Server VDB

422

Delphix User Guide 2016 Delphix

Provisioning a SQL Server VDB

This topic describes how to provision a virtual database (VDB) from a SQL Server dSource.

Prerequisites
You will need to have linked a dSource from a source database, as described in Linking a SQL Server dSource, or have already
created a VDB from which you want to provision another VDB.
You should already have set up Windows target environments and installed the Delphix Connector on them, as described in Adding a
SQL Server Standalone Target Environment.
Make sure you have the required privileges on the target environment as described in Requirements for SQL Server Target Hosts and
Databases.
If you are provisioning to a different target environment than the one where the staging database has been set up, you need to make sure
that the two environments have compatible operating systems, as described in Requirements for SQL Server Target Hosts and
Databases. For more information on the staging database and the validated sync process, see Setting Up SQL Server Environments:
An Overview.

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource.
6. Select a means of provisioning.
See Provisioning by Snapshot and LogSync in this topic for more information.
7. Click Provision.
The Provision VDB panel will open, and the Database Name and Recovery Model will auto-populate with information from the
dSource.
8. Select a target environment from the left pane.
9. Select an Instance to use.
10. If the selected target environment is a Windows Failover Cluster environment, select a drive letter from Available Drives. This drive will
contain volume mount points to Delphix storage.
11. Specify any Pre or Post Scripts that should be used during the provisioning process.
For more information, see Using Pre- and Post-Scripts with SQL Server dSources.
12. Click Next.
13. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
14. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
15. Click Next.
16. If your Delphix Engine system administrator has configured the Delphix Engine to communicate with an SMTP server, you will be able to
specify one or more people to notify when the provisioning is done. You can choose other Delphix Engine users, or enter email
addresses.
17. Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the
VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database and its Data
Management settings.

You can select a SQL Server instance that has a higher version than the source database and the VDB will be automatically upgraded.
For more information about compatibility between different versions of SQL Server, see SQL Server Operating System Compatibility
Matrices.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any particular snapshot, either by time or LSN.

423

Delphix User Guide 2016 Delphix

You can take a new snapshot of the dSource and provision from it by clicking the Camera icon on the dSource card.

Provisioning
By
Snapshot

Description

Provision by
Time

You can provision to the start of any snapshot by selecting that snapshot card from the TimeFlow view, or by entering a value
in the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.

Provision by
LSN

You can use the Slide to Provision by LSN control to open the LSN entry field. Here, you can type or paste in the LSN you
want to provision to. After entering a value, it will "snap" to the start of the closest appropriate snapshot.

If LogSync is enabled on the dSource, you can provision by LogSync information. When provisioning by LogSync information, you can provision
to any point in time, or to any LSN, within a particular snapshot. The TimeFlow view for a dSource shows multiple snapshots by default. To view
the LogSync data for an individual snapshot, use the Slide to Open LogSync control at the top of an individual snapshot card.
Provisioning
By LogSync

Description

Provision by
Time

Use the Slide to Open LogSync control to view the time range within that snapshot. Drag the red triangle to the point in time
that you want to provision from. You can also enter a date and time directly.

Provision by
LSN

Use the Slide to Open LogSync and Slide to Provision by LSN controls to view the range of LSNs within that snapshot. You
must type or paste in the specific LSN you want to provision to. Note that if the LSN doesn't exist, you will see an error when
you provision.

Related Links
Linking a SQL Server dSource
Adding a SQL Server Standalone Target Environment
Adding a SQL Server Failover Cluster Target Environment
Requirements for SQL Server Target Hosts and Databases
Setting Up SQL Server Environments: An Overview
Using Pre- and Post-Scripts with dSources and SQL Server VDBs

424

Delphix User Guide 2016 Delphix

File Permissions for SQL Server VDBs

When provisioning a VDB the "access control lists" (ACLs) of database and log files are modified to help prevent
unintentional data loss through file deletion. This could happen if there is an attempt to DROP a VDB directly
through SQL Server management studio or other native SQL Server tools.
Each database and log file ACL is updated to include a deny delete "access control entry" (ACE) for the user account running the SQL Server
instance.
VDBs can still be dropped directly through SQL Server tools, however a warning message will be displayed and the files will remain on the
volume exported by Delphix. This file deletion prevention also applies to attempts to remove files from a database using the ALTER DATABASE
.. REMOVE FILE command.
If a VDB is inadvertently dropped, the database can be reattached using SQL Server tools.
If you attempt to delete a database or log file and then try to add a file of the same name this may fail because the original file was prevented from
being deleted by the deny delete ACE.
If it is your intention to delete the files from the volume provided by Delphix, the ACLs on the files can be changed using the icacls command.

icacls <file> /remove <SQL Server instance account>:deny(D)

Accounts other than the SQL Server instance account will not be prevented from deleting the VDB database and log files.

425

Delphix User Guide 2016 Delphix

Extended Properties for SQL Server VDBs

This topic describes extended properties on VDBs that can be used to track the origin of VDBs through SQL Server tools on target servers.
These are the extended properties:
Property

Description

dlpx_server_name

Address of the Delphix Engine hosting the VDB

dlpx_server_uuid

UUID of the Delphix Engine hosting the VDB

dlpx_source_id

Internal reference of the VDB

These properties can be found under the Extended Properties page of the Properties window for a VDB using the SQL Server Management
Studio tool. They can also be displayed by using the sp_dlpx_vdbinfo stored procedure. This stored procedure can be installed by running the
SQL code contained in <Delphix Connector install path>\etc\sp_dlpx_vdbinfo.sql.

426

Delphix User Guide 2016 Delphix

Upgrading SQL Server VDBs

This topic describes how to upgrade a SQL Server VDB to a higher version of SQL Server instance.

Procedure for VDB In-Place Upgrade

1. Remove any VDB Refresh Policy assigned to the VDB.
2. Upgrade the target SQL Server instance.
3. Refresh the target environment.

Procedure to Upgrade a VDB to a New SQL Instance

1. Refresh all environments.
2. Log into the Delphix Admin application using delphix_admin credentials pr as the owner of the VDB.
3. Select Manage > Databases > My Databases.
4. Disable the VDB to be upgraded.
5. Click the Expand icon to open the VDB card.
6. Click the crown icon on the bottom of the VDB card.
The Upgrade Database screen will open.
7. Select the new SQL Server instance your want the VDB to upgrade to.
8. Click OK.
9. Enable the VDB.
10. Repeat step 2 to 9 for each VDB you want to upgrade.

Notes
Upgrading a SQL Server 2005 VDB to SQL Server 2008 or 2008 R2 is not supported.

Related Links
Refreshing an Environment
Enabling and Disabling dSources

427

Delphix User Guide 2016 Delphix

Migrating a SQL Server VDB

This topic describes how to migrate a SQL Server VDB to a different environment.

Prerequisites
The VDB has to be disabled first before migrating it by following the steps outlined in Enabling and Disabling Virtual Databases.
The target environment where the VDB is to be migrated should already have been added to the Delphix Engine. Follow the steps
outlined in Adding a SQL Server Standalone Target Environment.

Procedure via GUI

1. Select the VDB you would like to migrate
2. Disable VDB
3. Select the Migrate VDB icon
4. Select the New Environment and Installation
5. Hit the Check Mark
6. After job finishes Enable VDB

Procedure via CLI

1. Select the source associated with the VDB.

delphix> source
delphix source > select "vexample"
2. Select the source config associated with the source.

delphix source "vexample"> get config

vexample
delphix source "vexample"> /sourceconfig
delphix sourceconfig > select "vexample"
delphix sourceconfig "vexample">
3. Update the repository to the repository on the target environment for the migration, and the environment user associated with the source
config.

delphix sourceconfig "vexample"> update

delphix sourceconfig "vexample" update *> set repository="new target
environment"/"MSSQL instance"
delphix sourceconfig "vexample" update *> set environmentUser="new target
environment"/"new target's user"
delphix sourceconfig "vexample" update *> commit
delphix sourceconfig "vexample">

Post-Requisites
Enable the VDB following the steps outlined in Enabling and Disabling Virtual Databases.

Related Links
Adding a SQL Server Standalone Target Environment

428

Delphix User Guide 2016 Delphix

Renaming a SQL Server VDB

This topic describes how to rename the database name on the SQL Server instance for a SQL Server VDB through Delphix.
Database name on SQL Server vs VDB name on Delphix
The database name that is changed in this procedure is what you would see under the SQL Server instance on the target environment
and is on the back of the VDB card. The name of the VDB object itself is a name internal to Delphix and is what you see on front of the
VDB card.

Prerequisites
The VDB should be running on the target environment.
The SQL Server instance on the target environment where the VDB is should be up and reachable.

Procedure
1. Select the source associated with the VDB.
delphix> source

"vexample"

2. Select the source configassociated with the source.

delphix source "vexample" > get config
vexample
delphix source "vexample" > /sourceconfig
delphix sourceconfig "vexample" >

"vexample"

3. Update the databaseNameto the new name.

delphix
delphix
delphix
delphix

sourceconfig
sourceconfig
sourceconfig
sourceconfig

"vexample" > update

"vexample" update *> set databaseName=newDBName
"vexample"
update *> commit
"vexample" >

429

Delphix User Guide 2016 Delphix

Rewinding a SQL Server VDB

This topic describes the procedure for rewinding a VDB.
Rewinding a VDB rolls it back to a previous point in its TimeFlow and re-provisions the VDB. The VDB will no longer contain changes after the
rewind point.
Although the VDB no longer contains changes after the rewind point, the rolled over Snapshots and TimeFlow still remain in Delphix
and are accessible through the Command Line Interface (CLI). See the topic CLI Cookbook: Rolling Forward a VDB for instructions
on how to use these snapshots to refresh a VDB to one of its later states after it has been rewound.

Prerequisites
To rewind a VDB, you must have the following permissions:
Auditor permissions on the dSource associated with the VDB
Owner permissions on the VDB itself
You do NOT need owner permissions for the group that contains the VDB. A user with Delphix Admin credentials can perform a VDB Rewind on
any VDB in the system.

Procedure
1. Login to the Delphix Admin application.
2. Under Databases, select the VDB you want to rewind.
3. Select the rewind point as a snapshot or a point in time.
4. Click Rewind.
5. If you want to use login credentials on the target environment other than those associated with the environment user, click Provide
Privileged Credentials.
6. Click Yes to confirm.

You can use TimeFlow bookmarks as the rewind point when using the CLI. Bookmarks can be useful to:
Mark where to rewind to - before starting a batch job on a VDB for example.
Provide a semantic point to revert back to in case the chosen rewind point turns out to be incorrect.
For a CLI example using a TimeFlow bookmark, see CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark.

Video

430

Delphix User Guide 2016 Delphix

Customizing SQL Server Management with Pre- and Post-Scripts

Using Scripts with SQL Server dSources and Virtual Databases (VDBs)
Execution Context for SQL Server Scripts
Available Variables for SQL Server dSource Scripts
Available Variables for SQL Server VDB Scripts
Error handling for SQL Server PowerShell Scripts
This topic describes the use of pre- and post-scripts with dSources.
For each script, you can add the script path and its arguments when linking a dSource in one of two ways. Either:
During the Add dSource wizard process, in the Data Management screen, click Advanced.
or
On the back of the dSource card, click the Pencil icon next to the Pre Script and Post Script fields.
To update pre- and post-script information:
1. Flip over the dSource card.
2. Click on the Pencil icon next to the Pre Script and Post Script fields.
3. When finished, click the check mark icon.
Note that pre-scripts are executed before the SnapSync policy, and if the script fails, SnapSync will fail as well. In the case of a post-script, the
script will execute after SnapSync is complete. If a post-script fails, you will see an error message.

Using Scripts with SQL Server dSources and Virtual Databases (VDBs)
For SQL Server dSources, pre- and post-scripts are incorporated into the validated sync process.
For SQL Server single instance environments, scripts must exist and be readable on the staging environment.
Scripts can also be run as part of the SQL Server VDB provisioning process, in which case they must exist and be readable on the target
environment.
For SQL Server, both dSource and VDB scripts can be either text or binary executables.

Execution Context for SQL Server Scripts

Pre- and Post-Scripts for dSources are executed in the context of the primary Windows user account of the staging environment for the dSource.
Pre- and Post-Scripts for VDBs are executed in the context of the primary Windows user account of the target environment.

Available Variables for SQL Server dSource Scripts

These environment variables are set by Delphix Engine for scripts running on a SQL Server dSource:
Environment Variables

Description

SOURCE_INSTANCE_HOST

Hostname of linked instance for the dSource

SOURCE_INSTANCE_PORT

Port of linked instance for the dSource

SOURCE_INSTANCE_NAME

Name of linked instance for the dSource

SOURCE_DATABASE_NAME

Name of database linked for the dSource

Available Variables for SQL Server VDB Scripts

These environment variables are set by Delphix Engine for scripts running on a SQL Server VDB:
Environment Variables

Description

VDB_INSTANCE_HOST

Hostname of linked instance for the VDB

VDB_INSTANCE_PORT

Port of linked instance for the VDB

431

Delphix User Guide 2016 Delphix

VDB_INSTANCE_NAME

Name of linked instance for the VDB

VDB_DATABASE_NAME

Name of database linked for the VDB

Error handling for SQL Server PowerShell Scripts

If the pre- or post-script execution results in an error, the Delphix Engine expects the script to return with a non-zero exit code. Otherwise, the
error will not be detected.
PowerShell gives you a few ways to handle errors in your scripts.
Set $ ErrorActionPreference. This only applies to PowerShell Cmdlets. For scripts or other executables such as sqlcmd,
PowerShell will return with exit code 0 even if there is an error, regardless of the value of $ErrorActionPreference. The allowable
values for $ErrorActionPreference are:
Continue (default) : Continue even if there is an error.
SilentlyContinue : SilentlyContinue acts like Continue with the exception that errors are not displayed.
Inquire : Prompts the user in case of error.
Stop : Stops execution after the first error.
Use exception handling by using traps and try/catch blocks to detect errors and return with non-zero exit codes
Custom error handling that can be invoked after each command execution to correctly detect errors:

function die {
Write-Error "Error: $($args[0])"
exit 1
}
function verifySuccess {
if (!$?) {
die "$($args[0])"
}
}
Write-Output "I'd rather be in Hawaii"
verifySuccess "WRITE_OUTPUT_FAILED"
& C:\Program Files\Delphix\scripts\myscript.ps1
verifySuccess "MY_SCRIPT_FAILED"

432

Delphix User Guide 2016 Delphix

Customizing SQL Server Management with Hook Operations

Hook Operations Not Supported by Default
By default, the Delphix Engine does not provided hook operations for SQL Server dSources or VDBs. This feature must be enabled by
Delphix.
If this feature has not been enabled, use the Pre- and Post- script functionality outlined in Customizing SQL Server Management with
Pre- and Post-Scripts.
Hook operations allow you to execute an ordered list of custom operations at select hook points in linking, provisioning and virtual dataset
management. For details on the types of operations that are available, see children of this page.
dSource Hooks
Virtual Dataset Hooks
Setting Hook Operations
Setting Hook Operations through the Delphix Admin Application
Setting Hook Operations through the CLI
Example of Editing Hook Operations through the CLI
Hook Operation Templates
Creating a Hook Operation Template
Importing a Hook Operation Template
Exporting a Hook Operation Template

dSource Hooks
Hook

Description

Pre-Sync

Operations performed before a sync.

These operations can quiesce data to be captured during the sync, or stop processes that may interfere with the sync.

Post-Sync

Operations performed after a sync. This hook will run regardless of the success of the sync or Pre-Sync hook operations.
These operations can undo any changes made by the Pre-Sync hook.

Virtual Dataset Hooks

Hook

Description

Configure
Clone

Operations performed after initial provision or after a refresh. This hook will run after the virtual dataset has been started.
During a refresh, this hook will run before the Post-Refresh hook.

Pre-Refresh

Operations performed before a refresh.

These operations can cache data from the virtual dataset to be restored after the refresh completes.

Post-Refresh

Operations performed after a refresh. During a refresh, this hook will run after the Configure Clone hook. This hook will not run
if the refresh or Pre-Refresh hook operations fail.
These operations can restore cached data after the refresh completes.

Pre-Rewind

Operations performed before a rewind.

These operations can cache data from the virtual dataset to be restored after the rewind completes.

Post-Rewind

Operations performed after a rewind. This hook will not run if the rewind or Pre-Rewind hook operations fail.
These operations can restore cached data after the rewind completes.

Pre-Snapshot

Operations performed before a snapshot.

These operations can quiesce data to be captured during the snapshot, or stop processes that may interfere with the
snapshot.

Post-Snapshot

Operations performed after a snapshot. This hook will run regardless of the success of the snapshot or Pre-Snapshot hook
operations.
These operations can undo any changes made by the Pre-Snapshot hook.

433

Delphix User Guide 2016 Delphix

Operation Failure
If a hook operation fails, it will fail the entire hook: no further operations within the failed hook will be run.

Setting Hook Operations

You can construct hook operation lists through the Delphix Admin application or the command line interface (CLI). You can either define the
operation lists as part of the linking or provisioning process or edit them on dSources or virtual datasets that already exist.

Setting Hook Operations through the Delphix Admin Application

To specify hook operations during linking or provisioning, navigate to the Hooks tab of the Linking Wizard or Provision Wizard.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation or click Import to load a hook operation template.
4. Click the text area and edit the contents of the operation.
5. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
6. To remove an operation from the list, click the Trash icon on the operation.
7. When you have set all hook operations, click Next to continue with the provisioning process.
To edit hook operations on an already-existing dSource or virtual dataset, navigate to the Hooks tab on the back of the dSource card or virtual
dataset card.
1. Select the hook to edit.
2. The current operations at this hook will be displayed. To edit this list of operations, click the Pencil icon in the top right-hand corner of the
card.
3. Click the Plus icon to add a new operation.
4. Select the type of operation or click Import to load a hook operation template.
5. Click the text area and edit the contents of the operation.
6. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
7. To remove an operation from the list, click the Trash icon on the operation.
8. When you have set all hook operations, click Check to save the changes.

Setting Hook Operations through the CLI

To specify hook operations during linking, edit the relevant hook's array of operations defined on the LinkingParameters > Source >
Operations object.
To specify hook operations during provisioning, edit the relevant hook's array of operations defined on the ProvisionParameters > Source
> Operations object.
To edit hook operations on an already-created dSource, edit the relevant hook's array of operations defined on the Source > Operations obje
ct.
To edit hook operations on an already-created virtual dataset, edit the relevant hook's array of operations defined on the Source > Operation
s object.
For more information about these CLI objects, see the LinkedSourceOperations, VirtualSourceOperations, RunCommandOnSourceOp
eration, and RunExpectOnSourceOperation API documentation in the Help menu of the Delphix Admin application.

Example of Editing Hook Operations through the CLI

1. Navigate to the relevant source's VirtualSourceOperations object.
2. Select a hook to edit.
delphix> source
delphix source> select "pomme"
delphix source "pomme"> update
delphix source "pomme" update *> edit operations
delphix source "pomme" update operations *> edit postRefresh
3. Add an operation at index 0.

434

Delphix User Guide 2016 Delphix

delphix source "pomme" update operations postRefresh

delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
Properties
type: RunCommandOnSourceOperation (*)
command: echo Refresh completed. (*)
delphix source "pomme" update operations postRefresh

*> add
0 *> set type=RunCommandOnSourceOperation
0 *> set command="echo Refresh completed."
0 *> ls

0 *> commit

4. Add another operation at index 1 and then delete it.

delphix
delphix
delphix
delphix
delphix
delphix

source
source
source
source
source
source

"pomme"
"pomme"
"pomme"
"pomme"
"pomme"
"pomme"

update
update
update
update
update
update

operations
operations
operations
operations
operations
operations

postRefresh
postRefresh
postRefresh
postRefresh
postRefresh
postRefresh

*> add
1 *> set type=RunCommandOnSourceOperation
1 *> set command="echo Refresh completed."
1 *> back
*> unset 1
*> commit

Hook Operation Templates

You can use templates to store commonly used operations, which allows you to avoid repeated work when an operation is applicable to more
than a single dSource or virtual dataset. You manage templates through the Delphix Admin application.
Hook Operations Templates Not Available via CLI
Hook operation templates cannot be fully utilized from the CLI. Manage and use hook operations through the Delphix Admin applicatio
n.

Creating a Hook Operation Template

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Operation Templates.
4. Click the Plus icon to add a new operation template.
5. Enter a Name for the template.
6. Select an operation Type.
7. Enter a Description detailing what the operation does or how to use it.
8. Enter operation Contents to implement the operation partially or fully.
9. Click Create.

Importing a Hook Operation Template

To import a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Click Import.
4. Select the template to import.
5. Click Import.
6. When you have set all hook operations, click Check to save the changes.

Exporting a Hook Operation Template

To export a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation.
4. Click the text area and edit the contents of the operation.
5. Click Export.
6. Enter a Name for the template.
7. Enter a Description detailing what the operation does or how to use it.

435

Delphix User Guide 2016 Delphix

7.
8. Click Create.

436

Delphix User Guide 2016 Delphix

SQL Server Hook Operation Notes

SQL Server Clusters
RunPowershell Operation
SQL Server Environment Variables
dSource Environment Variables
VDB Environment Variables

SQL Server Clusters

When linking from, or provisioning to cluster environments, hook operations will not run once on each node in the cluster. Instead, the Delphix
Engine always runs all hooks on the instance primary node.
RunPowershell Operation

The RunPowershell operation executes a Powershell script on a Windows environment. The environment user runs this shell command from their
home directory. The Delphix Engine captures and logs all output of the script. If the script fails, the output is displayed in the Delphix
Admin application and command line interface (CLI) to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunPowershell Operation

You can input the full command contents into the RunPowershell operation.

$removedir = $Env:DIRECTORY_TO_REMOVE
if ((Test-Path $removedir) -And (Get-Item $removedir) -is [System.IO.DirectoryInfo]) {
Remove-Item -Recurse -Force $removedir
} else {
exit 1
}
exit 0
SQL Server Environment Variables
Operations that run user-provided scripts have access to environment variables. For operations associated with specific dSources or virtual
databases (VDBs), the Delphix Engine will always set environment variables so that the user-provided operations can use them to access the
dSource or VDB.
dSource Environment Variables

Environment Variables

Description

SOURCE_INSTANCE_HOST

Hostname of linked instance for the dSource

SOURCE_INSTANCE_PORT

Port of linked instance for the dSource

SOURCE_INSTANCE_NAME

Name of linked instance for the dSource

SOURCE_DATABASE_NAME

Name of database linked for the dSource

VDB Environment Variables

Environment Variables

Description

VDB_INSTANCE_HOST

Hostname of the VDB

VDB_INSTANCE_PORT

Port of the VDB instance

VDB_INSTANCE_NAME

Name of the VDB instance

VDB_DATABASE_NAME

Name of the VDB

437

Delphix User Guide 2016 Delphix

438

Delphix User Guide 2016 Delphix

PostgreSQL Environments and Data Sources

439

Delphix User Guide 2016 Delphix

PostgreSQL Support and Requirements

These topics describe specific requirements for PostgreSQL environments, such as user privileges, as well as the supported operating systems
and database versions.
Requirements for PostgreSQL Source Hosts and Databases
Requirements for PostgreSQL Target Hosts and Databases
Supported Operating Systems and Database Versions for PostgreSQL Environments
Network and Connectivity Requirements for PostgreSQL Environments

440

Delphix User Guide 2016 Delphix

Requirements for PostgreSQL Source Hosts and Databases

Source hosts are servers which contain the source databases from which virtual database copies are made. Collectively, the source host and
database are referred to as the source environment. This topic describes the requirements for creating connections between PostgreSQL source
environments and the Delphix Engine.

Source Host Requirements

1. On 64-bit Linux environments, a 32-bit version of glibc must be installed.
2. There must be an operating system user with the following privileges:
a. The Delphix Engine must be able to make an SSH connection to the source environment using the operating system user.
b. The operating system user should have read and execute privileges on the PostgreSQL binaries installed on the source
environment.
c. The operating system user should have read access to the PostgreSQL data directories on the source environment.
3. There must be a directory on the source host where the Delphix Engine toolkit can be installed (e.g., /opt/delphix) with the following
properties:
a. The toolkit directory must be writable by the operating system user mentioned above.
b. The toolkit directory must have at least 256 MB of available storage.
4.

TCP/IP connectivity to and from the source environment must be configured as described in
and Connectivity Requirements.

General Network

Source Database Requirements

1. The database must accept read/write connections (in other words, it must not be in standby mode).
2. The Delphix Engine must have access to a PostgreSQL role that has superuser, replication and login privileges. This can be the built-in p
ostgres role or a newly-created role (for example, delphix).
Creating a Role for Use with the Delphix Engine
To create a new role for use with the Delphix Engine, use the following command:
SQL> CREATE ROLE delphix SUPERUSER LOGIN REPLICATION [ PASSWORD 'password']

3. The following changes must be made to postgresql.conf (for more information, see the Server Configuration chapter in the
PostgreSQL documentation):
a. TCP/IP connectivity must be configured to allow the role mentioned above to connect to the source database from the Delphix
Engine and from the standby DBMS instance set up by the Delphix Engine on the staging environment. This can be done by
modifying the listen_addresses parameter, which specifies the TCP/IP addresses on which the DBMS is to listen for
connections from client applications.
listen_addresses Configuration
The simplest way to configure Postgres is so that it listens on all available IP interfaces:
listen_addresses = '*'
# Default is 'localhost'

b. The value of max_wal_senders, which specifies the maximum number of concurrent connections from standby servers or
streaming base backup clients, must be increased from its desired value by four. That is, in addition to the allowance of
connections for consumers other than the Delphix Engine, there must be an allowance for four additional connections from
consumers set up by the Delphix Engine.
max_wal_senders Configuration
The default value of max_wal_senders is zero, meaning replication is disabled. In this configuration, the value of max
_wal_senders must be increased to two for the Delphix Engine:
max_wal_senders = 4
# Default is 0

c. The value of wal_level, which determines how much information is written to the write-ahead log (WAL), must be set to archi
ve or hot_standby to allow connections from standby servers. The logical wal_level value (introduced in PostgreSQL
9.4) is also supported.
wal_level Configuration
The default value of wal_level is minimal, which writes only the information needed to recover from a crash or

441

Delphix User Guide 2016 Delphix

immediate shutdown to the WAL archives. In this configuration, one must add the logging required for WAL archiving
as follows:
wal_level = archive
# Default is minimal

4. PostgreSQL must be configured to allow PostgreSQL client connections from the Delphix Engine and from the staging target
environment, as well as PostgreSQL replication client connections from the staging target environment by adding the following entries to
pg_hba.conf:

pg_hba.conf Configuration
host
host
host

all
all
replication

<role>
<role>
<role>

<ip-address_of_delphix_engine>/32
<ip-address_of_staging_target>/32
<ip-address_of_staging_target>/32

<auth-method>
<auth-method>
<auth-method>

<auth-method> must be md5 or trust to indicate if a password is required (md5) or not (trust). For more information on how to
configure pg_hba.conf, see the Client Authentication chapter in the PostgreSQL documentation.

Related Links
General Network and Connectivity Requirements
Server Configuration in the PostgreSQL documentation
Client Authentication in the PostgreSQL documentation

442

Delphix User Guide 2016 Delphix

Requirements for PostgreSQL Target Hosts and Databases

This topic describes user privileges and other requirements for PostgreSQL target hosts and databases, collectively referred to as the target
environment.

Target Environment Requirements

1. The operating system and architecture of the target environment must match those of the source environment.
2. There must be an installation of PostgreSQL on the target environment that is compatible with an installation of PostgreSQL on the
source environment. Two installations of PostgreSQL are compatible if and only if:
a. They share the same vendor (for example, PostgreSQL is incompatible with EnterpriseDB Postgres Plus Advanced Server).
b. They share the same major version number (for example, 8.4.2 is compatible with 8.4, 8.4.1 and 8.4.6; however, it is
incompatible with 8.3, 8.3.1, or 9.2).
c. They were compiled against the same architecture (in other words, 32-bit and 64-bit installations of Postgres are incompatible).
d. They were compiled with the same WAL segment size. The default WAL segment size of 16 MB is rarely changed in practice, so
almost all installations of PostgreSQL are compatible with each other in terms of WAL segment size.
3.

On 64-bit Linux environments, a 32-bit version of glibc must be installed.

4. The pg_xlogdump utility must be installed, this is typically included in the postgresql-contrib package. For postgres 9.2, the pg_xlo
gdump util was not included in the standard Postgres packages, so we include a copy in the toolkit dir installed by the DE.
5. There must be an operating system user with the following privileges:
a. The Delphix Engine must be able to make an SSH connection to the target environment using the operating system user.
b. The operating system user must have read and execute privileges on the PostgreSQL binaries installed on the
target environment.
c. The operating system user must have permission to run mount and umount as the superuser via sudo with neither a password
nor a TTY via the following entries in /etc/sudoers.conf:

/etc/sudoers Configuration
Defaults:<username> !requiretty
<username> ALL=NOPASSWD:/bin/mount, /bin/umount
6.

There must be a directory on the target environment where the Delphix Engine toolkit can be installed (for
example, /var/tmp ) with the following properties:
a. The toolkit directory must be writable by the operating system user mentioned above.
b. The toolkit directory must have at least 256 MB of available storage.

7.

There must be a mount point directory (for example, /mnt/provision) that will be used as the base for
mount points that are created when provisioning a VDB with the following properties:
a. The mount point directory must be writable by the operating system user mentioned above.
b. The mount point directory should be empty.

8.

TCP/IP connectivity to and from the source environment must be configured as described in
and Connectivity Requirements .

Related Links
Using HostChecker to Confirm Source and Target Environment Configuration
sudoers Manual Page

443

General Network

Delphix User Guide 2016 Delphix

Supported Operating Systems and Database Versions for PostgreSQL Environments

This topic describes supported operating systems and database versions for PostgreSQL.
Source and Target OS and DBMS Compatibility
The source and target environments must be running the same DBMS/Operating System combination (for example, PostgreSQL 9.2 on
RHEL 6.3) in order to successfully perform linking and provisioning.

Supported DBMS Versions

DBMS

Version

Processor Family

PostgreSQL

9.2, 9.3, 9.4

x86_64

EnterpriseDB Postgres Plus Advanced Server

9.2, 9.3, 9.4

x86_64

Supported Operating Systems

Operating System

Version

Processor Family

Red Hat Enterprise Linux 5

RHEL 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 5.10,5.11

x86_64

Red Hat Enterprise Linux 6

RHEL 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6

x86_64

444

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for PostgreSQL Environments

General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration
Connection Requirements for PostgreSQL Environments
Port Allocation for PostgreSQL Environments
Outbound from the Delphix Engine Port Allocation
Inbound to the Delphix Engine Port Allocation
Port Allocation Between Source and Staging Target Environments

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

445

Delphix User Guide 2016 Delphix

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

Connection Requirements for PostgreSQL Environments

The Delphix Engine uses an SSH connection to each source environment and PostgreSQL client connections to the
PostgreSQL instances on the source environment.
The Delphix Engine uses an SSH connection to each target environment, NFS connections from each target environment to the Delphix
Engine, and PostgreSQL client connections to the virtual databases on the target environment.
Once connected to a staging target environment through SSH, the Delphix Engine initiates a PostgreSQL replication client connection
from the target environment to the source environment.

Port Allocation for PostgreSQL Environments

The following diagram describes the port allocations for PostgreSQL environments. It illustrates the ports that we recommend to be open from
Delphix to remote services, to the Delphix Engine, and to the Target Environments.

Refer to Setting Up PostgreSQL Environments: An Overview for information on PostgreSQL environments. The Delphix Engine makes use of
the following network ports for PostgreSQL dSources and VDBs:

Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

22

SSH connections to source and target database environments

446

Delphix User Guide 2016 Delphix

TCP

xxx

PostgreSQL client connections to the PostgreSQL instances on the source and target environments (port 5432 by
default)

Inbound to the Delphix Engine Port Allocation

Protocol

Port Number

Use

TCP/UDP

111

Remote Procedure Call (RPC) port mapper used for NFS mounts

TCP

1110

Network Status Monitor (NSM) client from target hosts to the Delphix Engine

TCP/UDP

2049

NFS client from target hosts to the Delphix Engine

TCP

4045

Network Lock Manager (NLM) client from target hosts to the Delphix Engine

UDP

33434 - 33464

Traceroute from source and target database servers to the Delphix Engine (optional)

Port Allocation Between Source and Staging Target Environments

Outgoing

Incoming

Protocol

Port
Number

Use

Target
Environment

Source
Environment

PostgreSQL
replication client

xxx

PostgreSQL replication client connection to the PostgreSQL instances on the

source environment (port 5432 by default)

447

Delphix User Guide 2016 Delphix

Managing PostgreSQL Environments

These topics describe special tasks and concepts for working with PostgreSQL environments.
Setting Up PostgreSQL Environments: An Overview
Using HostChecker to Validate PostgreSQL Source and Target Environments
Adding a PostgreSQL Environment
Adding an Installation to a PostgreSQL Environment
Adding a Database Cluster to a PostgreSQL Environment
Editing PostgreSQL Environment Attributes
Managing PostgreSQL Environment Users
Deleting a PostgreSQL Environment
Refreshing a PostgreSQL Environment
Enabling Staging, Linking and Provisioning for PostgreSQL Environments
Changing the Host Name or IP Address for PostgreSQL Source and Target Environments

448

Delphix User Guide 2016 Delphix

Setting Up PostgreSQL Environments: An Overview

This topic describes the high-level process for adding PostgreSQL environments, linking PostgreSQL data sources to the Delphix Engine, and
provisioning virtual databases from PostgreSQL data sources.

Types of PostgreSQL Environments

At a high level, the Delphix Engine maintains an internal representation of a data source, from which one can provision virtual databases (VDBs).
In order to link a data source and provision a VDB, the following types of environments are required:
A source environment is where the unvirtualized source database runs. The Delphix Engine uses the backup, restore, and replication features of
the PostgreSQL DBMS to maintain its internal representation of the source database, to be used for provisioning VDBs. The Delphix Engine must
be able to connect to the source environment in order to discover running source databases and to orchestrate the backup, restore, and
replication functionality necessary to keep its representation synchronized with the source database. The Delphix Engine is designed to have a
minimal impact on the performance of the source database and the source environment.
A target environment is where virtualized databases run. PostgreSQL target environments serve two purposes:
1.

Since PostgreSQL does not provide a native incremental backup API, a warm standby server (in other words,
one in log-shipping mode) must be created with all database files stored on the Delphix Engine for each
source database. We refer to the creation and maintenance of this staging database as validated sync. During
validated sync, we retrieve data from the source and ensure that all the components necessary for provisioning a VDB have been
validated. The result of validated sync is both a TimeFlow with consistent points from which you can provision a VDB, and a faster
provisioning process, because there is no need for any database recovery when provisioning a VDB. In order to create a staging
database, you must designate a target environment for this task when linking a dSource. During the linking process, database files are
exported over the network to the target environment, where the staging database instance runs as a warm standby server. A target
environment that hosts one or more staging databases is referred to as a staging target for validated sync.

2.

Once a staging database has been set up, you can provision virtual databases from any point in time along
the TimeFlow mentioned above to any compatible target environment (for more information, see Requiremen
ts for PostgreSQL Target Hosts and Databases). Database files are exported over the network to the
target environment, where the virtual database instance runs.

Workflow for PostgreSQL Environments

Prior to linking a data source, you must add both a source environment and a compatible target environment (to be
used for the staging database mentioned above) to the Delphix Engine. Prior to provisioning a virtual database, you
must add a compatible target environment to the Delphix Engine. This may be the same target environment as that
used for the staging instance, or it may be a different target environment.
Once an environment is added to the Delphix Engine, environment discovery takes place. Environment discovery is the process of enumerating
PostgreSQL installations and configurations when a source or target environment is added to the Delphix Engine. We also repeat the discovery
process during environment refresh in order to detect new PostgreSQL installations and clusters. Environment objects can be added manually if
discovery is not possible due to non-standard setup.

449

Delphix User Guide 2016 Delphix

Using HostChecker to Validate PostgreSQL Source and Target Environments

This topic describes how to use HostChecker to configure PostgreSQL environments.
What is HostChecker?
Prerequisites
Procedure
Tests Run
Related Links

What is HostChecker?
The HostChecker is a standalone program which validates that host machines are configured correctly before the Delphix Engine uses them as
data sources and provision targets.
Please note that HostChecker does not communicate changes made to hosts back to the Delphix Engine. If you reconfigure a host, you must
refresh the host in the Delphix Engine in order for it to detect your changes.
You can run the tests contained in the HostChecker individually, or all at once. You must run these tests on both the source and target hosts to
verify their configurations. As the tests run, you will either see validation messages that the test has completed successfully, or error messages
directing you to make changes to the host configuration.

Prerequisites
Make sure that your source and target environments meet the requirements specified in PostgreSQL Support and Requirements.

Procedure
1. Download the HostChecker tarball from https://download.delphix.com/ (for
example: delphix_4.0.2.0_2014-04-29-08-38.hostchecker.tar).
2. Create a working directory and extract the HostChecker files from the HostChecker tarball.

mkdir dlpx-host-checker
cd dlpx-host-checker/
tar -xf delphix_4.0.2.0_2014-04-29-08-38.hostchecker.tar
3. Change to the working directory and enter this command. Note that for the target environments, you would change source to target.

$ ./chkHost.pl source postgresql

Don't Run as Root
Don't run the HostChecker as root; this will cause misleading or incorrect results from many of the checks.

4. Select which checks you want to run. We recommend you run all checks if you are running Hostchecker for the first time.
5. Pass in the arguments the checks ask for.
6. Read the output of the check.
7. The error or warning messages will explain any possible problems and how to address them. Resolve the issues that the HostChecker
describes. Don't be surprised or undo your work if more errors appear the next time you run HostChecker, because the error you just
fixed may have been masking other problems.
8. Repeat steps 37 until all the checks return no errors or warnings.

Tests Run
Test
Check Host
SSH
Connectivity

PostgreSQL
Source

PostgreSQL
Target

Description
Verifies that the environment is accessible via SSH

450

Delphix User Guide 2016 Delphix

Check Tool
Kit Path

Verifies that the toolkit installation location has the proper ownership, proper permissions, and
enough free space.

Check Home
Directory
Permissions

Verifies that the environment can be accessed via SSH using public key authentication. If you
don't need this feature, you can ignore the results of this check.

Verifies that the operating system user can execute certain commands with necessary privileges
via sudo. This only needs to be run on target environments. See the topic Requirements for
PostgreSQL Target Hosts and Databases for more information.

Check OS
User
Privileges
Check
PostgreSQL
OS
compatibility

Verifies that the environment is running a compatible operating system. See the topic Supporte
d Operating Systems and Database Versions for PostgreSQL Environments for more
information.

Check
PostgreSQL
installations

Attempts to discover existing PostgreSQL installations and validate that they are of a compatible
version and that each instance meets the requirements for PostgreSQL source databases. See
the topics Requirements for PostgreSQL Source Hosts and Databases and Supported
Operating Systems and Database Versions for PostgreSQL Environments for more
information.

Related Links
PostgreSQL Support and Requirements

451

Delphix User Guide 2016 Delphix

Adding a PostgreSQL Environment

This topic describes how to add a PostgreSQL source environment to the Delphix Engine.

Prerequisites
Make sure your environment meets the requirements described in the following topics:
Requirements for PostgreSQL Source Hosts and Databases
Requirements for PostgreSQL Target Hosts and Databases
Supported Operating Systems and Database Versions for PostgreSQL Environments

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Unix/Linux in the operating system menu.
6. Select Standalone Host.
7. Enter the Host IP address.
8. Enter an optional Name for the environment.
9. Enter the SSH port.
The default value is 22.
10. Enter a Username for the environment.
For more information about the environment user requirements, see Requirements for PostgreSQL Target Hosts and Databases and
Requirements for PostgreSQL Source Hosts and Databases.
11. Select a Login Type.
For Password, enter the password associated with the user in Step 9.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

12. For Password Login, click Verify Credentials to test the username and password.
13. Enter a Toolkit Path.
See Requirements for PostgreSQL Target Hosts and Databases and Requirements for PostgreSQL Source Hosts and Databases
for more information about the toolkit directory requirements.
14. Click OK.
As the new environment is added, you will see two jobs running in the Delphix Admin Job History, one to Create and Discover an
environment, and another to Create an environment. When the jobs are complete, you will see the new environment added to the list in
the Environments panel. If you don't see it, click the Refresh icon in your browser.

Post-Requisites
After you create the environment, you can view information about it by selecting Manage > Environments, and then select the
environment name.

452

Delphix User Guide 2016 Delphix

Related Links
Setting Up PostgreSQL Environments: An Overview
Requirements for PostgreSQL Source Hosts and Databases
Requirements for PostgreSQL Target Hosts and Databases
Supported Operating Systems and Database Versions for PostgreSQL Environments
Adding an Installation to a PostgreSQL Environment

453

Delphix User Guide 2016 Delphix

Adding an Installation to a PostgreSQL Environment

This topic describes how to add an installation to a PostgreSQL environment.
When you add an environment with the Delphix Admin application, all PostgreSQL installations on it are automatically discovered. However, if an
installation is not automatically discovered, you can add it manually to the environment.

Procedure
1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > Environments.
3. Click Databases.
4. Click the green Plus icon next to Add Dataset Home.
5. Under Dataset Home Type, select PostgreSQL.
6. Enter the path to the Installation.
7. Click the Check icon when finished.

Related Links
Adding a Database Cluster to a PostgreSQL Environment

454

Delphix User Guide 2016 Delphix

Adding a Database Cluster to a PostgreSQL Environment

This topic describes how to add a database cluster to a PostgreSQL environment.
When you add an environment with the Delphix Admin application, all database clusters on it are automatically discovered. However, if a
database cluster is not automatically discovered, you can add it manually to the environment.

Prerequisites
Make sure your source database meets the requirements described in Requirements for PostgreSQL Source Hosts and Databases a
nd Requirements for PostgreSQL Target Hosts and Databases.
Before adding a database, the installation of the database must exist in the environment. If the installation does not exist in the
environment, follow the steps in Adding an Installation to a PostgreSQL Environment.

Procedure
1. Log into the Delphix Admin application using Delphix Admin credentials.
2. Select Manage > Environments.
3. Click Databases.
4. Choose the installation which has been used to start the database cluster.
Click the Up icon next to the the installation path to show details if needed.
5. Click the green Plus icon next to Add DB Cluster.
6. Enter the Path of the data cluster directory.
7. Click the Check icon when finished.

Related Links
Requirements for PostgreSQL Source Hosts and Databases
Requirements for PostgreSQL Target Hosts and Databases
Adding an Installation to a PostgreSQL Environment

455

Delphix User Guide 2016 Delphix

Editing PostgreSQL Environment Attributes

Procedure
Common Editable Attributes
PostgreSQL Attributes
This topic describes how to edit attributes of an environment such as name, host address, ssh port, or toolkit path, as well as descriptions of more
advanced attributes for specific data platforms.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials or as the owner of an environment.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of an environment to view its attributes.
5. Under Attributes, click the Pencil icon to edit an attribute.
6. Click the Check icon to save your edits.

Common Editable Attributes

Attribute

Description

Environment
Users

The users for that environment. These are the users who have permission to ssh into an environment, or access the
environment through the Delphix Connector. See the Requirements topics for specific data platforms for more information on
the environment user requirements.

Host
Address

The IP address for the environment host.

Notes

Any other information you want to add about the environment.

PostgreSQL Attributes
Attribute

Description

SSH Port

The port used for secure shell connection to the host.

Toolkit Path

The directory used for storing Delphix toolkit files.

456

Delphix User Guide 2016 Delphix

Managing PostgreSQL Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure

Prerequisites
Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

457

Delphix User Guide 2016 Delphix

Deleting a PostgreSQL Environment

This topic describes how to delete an environment.

Prerequisites
You cannot delete an environment that has any dependencies, such as dSources or virtual databases (VDBs). These must be deleted before you
can delete the environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, select the environment you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

458

Delphix User Guide 2016 Delphix

Refreshing a PostgreSQL Environment

This topic describes how to refresh an environment.
After you make changes to an environment that you have already set up in the Delphix Admin application, such as installing a new database
home, creating a new database, or adding a new listener, you may need to refresh the environment to reflect these changes.
During environment discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the
toolkit are:
A JRE
Delphix jar files
The hostchecker utility
Scripts for managing the environment and/or VDBs
Delphix Connector log files
Delphix then executes some of these scripts to discover information about the objects in your environment (where the databases are installed,
the database names, information required to connect to these databases, etc.). In some environments (Windows in particular), the scripts are
customized to fit the customers environment.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of the environment to you want to refresh.
5. Click the Refresh icon.
To refresh all environments, click the Refresh icon next to Environments.

459

Delphix User Guide 2016 Delphix

Enabling Staging, Linking and Provisioning for PostgreSQL Environments

This topic describes how to enable and disable staging, provisioning, and linking for databases.
Before you can use a database as a dSource, you must first make sure that you have defined a staging environment and enabled linking to it.
Similarly, before you can provision a virtual database (VDB) to a target database, you must make sure that you have enabled provisioning to
it.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. To enable or disable staging, slide the button next to Use as Staging to Yes or No.
6. To enable or disable provisioning, slide the button next to Allow Provisioning to On or Off.

460

Delphix User Guide 2016 Delphix

Changing the Host Name or IP Address for PostgreSQL Source and Target Environments
This topic describes how to change the host name or IP address for source and target environments, and for the Delphix Engine.
Procedure
For Source Environments
For VDB Target Environments
For the Delphix Engine

Procedure
For Source Environments
1. Disable the dSource as described in Enabling and Disabling dSources.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the dSource.

For VDB Target Environments

1. Disable the VDB as described in Enabling and Disabling Virtual Databases.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the VDB.

For the Delphix Engine

1. Stop all running VDBs by clicking the red Stop button on the VDB card.
2. Disable all dSources as described in Enabling and Disabling dSources.
3. You can use either the command line interface or the Server Setup application to change the IP address of the Delphix Engine.
a. To use the command line interface, press F2 and follow the instructions described in Setting Up Network Access to the
Delphix Engine.
b. To use the Server Setup application, go to to the upper right hand corner to the user name and click for the drop down and
Select 'Engine Setup' in the Delphix Admin interface, or click Server Setup in the Delphix Engine login screen. Note: You must
have sysadmin credentials to be able to do this part
i. In the Network panel, click Modify.
ii. Under DNS Services, enter the new IP address.
iii. Click OK.
4. Refresh all Environments by clicking the Blue/Green Refresh Symbol on the Environments screen.
5. Enable all dSources as described in Enabling and Disabling dSources.
6. Start all VDBs by clicking the Start button on the VDB card.

461

Delphix User Guide 2016 Delphix

Managing PostgreSQL Data Sources

These topics describe concepts and tasks for linking PostgreSQL data sources to the Delphix Engine.
Linking PostgreSQL Data Sources: Overview
Linking a PostgreSQL dSource
Advanced Data Management Settings for PostgreSQL Data Sources
Using Pre- and Post-Scripts with PostgreSQL dSources
Enabling and Disabling PostgreSQL dSources
Detaching and Re-Attaching PostgreSQL dSources
Deleting a PostgreSQL dSource
PostgreSQL dSource Icon Reference

462

Delphix User Guide 2016 Delphix

Linking PostgreSQL Data Sources: Overview

This topic describes basic concepts behind the creation of dSources from PostgreSQL data sources.

Initial Linking and Staging Databases

A dSource is the copy of a physical database that is created when the Delphix Engine links to and loads the database. The Delphix Engine keeps
the dSource in sync with the source database in order to facilitate the provisioning of Virtual Databases (VDBs) from the dSource's TimeFlow.
Since PostgreSQL does not provide a native incremental backup API, a warm standby server (in other words, one in log-shipping mode) must be
created with all database files stored on the Delphix Engine for each source database, as described in Setting Up PostgreSQL Environments:
An Overview . We refer to the creation and maintenance of this staging database as validated sync, and a target environment that hosts one or
more staging databases is referred to as a staging target for validated sync.
When you create a dSource from a PostgreSQL database, the Delphix Engine initiates a full database backup of the source database by running
pg_basebackup(1) on the staging target. The initial snapshot of the dSource is derived from this backup.
After obtaining the initial snapshot and linking the dSource, the Delphix Engine keeps the dSource and the source database in sync by monitoring
the source database for new transaction logs on the staging target, and then applying those transaction logs on the staging database. Transaction
logs are fetched by running pg_receivexlog(1) on the staging target.

Target Environments for Staging and VDB Provisioning

It is possible to provision a VDB to the same source environment that contains the dSource, but performance and efficiency are improved if the
dSource is located in one environment, and the VDB in another. A target environment can be used both for staging databases and for VDBs. The
source and target environments must be running the same DBMS/Operating System combination (for example, PostgreSQL 9.2 on RHEL 6.3) in
order to successfully link a dSource, as described in Supported Operating Systems and Database Versions for PostgreSQL Environments.

Related Links
Setting Up PostgreSQL Environments: An Overview
PostgreSQL Support and Requirements

463

Delphix User Guide 2016 Delphix

Linking a PostgreSQL dSource

This topic describes the basic procedure for linking a dSource from a PostgreSQL database to the Delphix Engine.

Prerequisites
Make sure you have the correct user credentials for the source environment, as described in Requirements for PostgreSQL Source
Hosts and Databases
You may also want to read the topic Advanced Data Management Settings for PostgreSQL Data Sources.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Select Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing PostgreSQL Environment Users.

6. Enter your login credentials for DB Cluster User and DB Cluster Password.
7. Click Advanced to enter a Connection Database.
The Connection Database will be used when issuing SQL queries from the Delphix Engine to the linked database. It can be any existing
database that the DB Cluster User has permission to access.
8. Click Next.
9. Select a Database Group for the dSource, and then click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. See the topics under Users, Permissions, and Policies for more information.
10. Select a SnapSync Policy, and, if necessary, a Staging Installation for the dSource.
The Staging installation represents the PostgreSQL binaries that will be used on the staging target to backup and restore the linked
database to a warm standby.
11. Click Advanced to select whether the data in the data sources is Masked, to select a Retention Policy, and to indicate whether any pre
or post scripts should be executed during the dSource creation.
For more information, see Advanced Data Management Settings for PostgreSQL Data Sources and Using Pre- and Post-Scripts
with PostgreSQL dSources.
12. Click Next.
13. Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card, and also make modifications to its policies
and permissions. In the Databases panel, click on the Open icon to view the front of the dSource card. The card will then flip, showing
you information such as the Source Database and Data Management configuration. For more information, see Advanced Data
Management Settings for PostgreSQL Data Sources.

Related Links
Advanced Data Management Settings for PostgreSQL Data Sources
Requirements for PostgreSQL Target Hosts and Databases
Using Pre- and Post-Scripts with PostgreSQL dSources
Users, Permissions, and Policies

464

Delphix User Guide 2016 Delphix

465

Delphix User Guide 2016 Delphix

Advanced Data Management Settings for PostgreSQL Data Sources

Accessing Data Management Settings
During the dSource linking process
On the back of the dSource card
In the top menu bar
Retention Policies
Benefits of Longer Retention
PostgreSQL LogSync Settings
PostgreSQL SnapSync Policy Settings
Schedule By Settings
This topic describes advanced data management settings for dSources.
When linking a dSource, you can use custom data management settings to improve overall performance and match the needs of your specific
server and data environment. If no specific settings are required, leverage default data management settings.

Accessing Data Management Settings

There are three ways to set or modify data management settings for dSources:
During the dSource linking process

1. In the Data Management panel of the Add dSource wizard, click Advanced.
On the back of the dSource card

1. Under Data Management, click the field next to Retention Policy

2. Click the Edit icon.
3. For SnapSync and Retention policies, click the policy name. This will open the Policy Management screen.
In the top menu bar

1. Click Manage.
2. Select Policies. This will open the Policy Management screen.
3. Select the policy for the dSource you want to modify.
4. Click Modify.
For more information, see Creating Custom Policies and Creating Policy Templates.

Retention Policies
Retention policies define the length of time that the Delphix Engine retains snapshots and log files to which you can rewind or provision objects
from past points in time. The retention time for snapshots must be equal to, or longer than, the retention time for logs.
To support longer retention times, you may need to allocate more storage to the Delphix Engine. The retention policy in combination with the
SnapSync policy can have a significant impact on the performance and storage consumption of the Delphix Engine.

Benefits of Longer Retention

With increased retention time for snapshots and logs, you allow a longer (older) rollback period for your data.
Common use cases for longer retention include:
SOX compliance
Frequent application changes and development
Caution and controlled progression of data
Reduction of project risk
Speed of rollback / restore to older points in time
With LogSync enabled, you can customize both the retention policy and the SnapSync policy to access logs for longer periods of time, enabling
point-in-time rollback and provisioning.

466

Delphix User Guide 2016 Delphix

PostgreSQL LogSync Settings

LogSync is always enabled by default for PostgreSQL dSources.

PostgreSQL SnapSync Policy Settings

Schedule By Settings
In the default SnapSync policy setting, snapshots are taken daily at a set time, with a four hour period. You can modify the snapshot schedule and
frequency by changing the Schedule By setting.

467

Delphix User Guide 2016 Delphix

Using Pre- and Post-Scripts with PostgreSQL dSources

Using Pre- and Post-Scripts with PostgreSQL dSources
Specifying Arguments for PostgreSQL Scripts
An Example with Three Arguments
An Example with an Apostrophe
This topic describes the use of pre- and post-scripts with dSources.
For each script, you can add the script path and its arguments when linking a dSource in one of two ways. Either:
During the Add dSource wizard process, in the Data Management screen, click Advanced.
or
On the back of the dSource card, click the Pencil icon next to the Pre Script and Post Script fields.
To update pre- and post-script information:
1. Flip over the dSource card.
2. Click on the Pencil icon next to the Pre Script and Post Script fields.
3. When finished, click the check mark icon.
Note that pre-scripts are executed before the SnapSync policy, and if the script fails, SnapSync will fail as well. In the case of a post-script, the
script will execute after SnapSync is complete. If a post-script fails, you will see an error message.

Using Pre- and Post-Scripts with PostgreSQL dSources

For PostgreSQL dSources, pre- and post-scripts are run during initial sync and during redo-basebackup
For PostgreSQL environments, scripts must exist and be readable on the source environment for initial sync and redo-basebackup
PostgreSQL dSource scripts must be text scripts only

Specifying Arguments for PostgreSQL Scripts

You can specify multiple arguments for a script. In the Pre or Post Script field, enter the path to the script, and then list the arguments. If the
argument contains spaces, enclose it in single or double quotes. You can escape single quotes within the argument with a backslash.

An Example with Three Arguments

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh one "second argument in double
quotes" 'third argument in single quotes'
An Example with an Apostrophe
/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh 'I\'d rather be in Hawaii.'

468

Delphix User Guide 2016 Delphix

Enabling and Disabling PostgreSQL dSources

This topic describes how to enable and disable dSources for operations such as backup and restore.
For certain processes, such as backing up and restoring the source database, you may want to temporarily disable your dSource. Disabling a
dSource turns off communication between the dSource and the source database, but does not tear down the configuration that enables
communication and data updating to take place. When a disabled dSource is later enabled, it will resume communication and incremental data
updates from the source database according to the original policies and data management configurations that you set.
Disabling a dSource is also a prerequisite for several other operations, like database migration and upgrading the dSource after upgrade of the
associated data source.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the dSource you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the dSource again, move the slider control from Disabled to Enabled, and the dSource will continue to function as
it did previously.

469

Delphix User Guide 2016 Delphix

Detaching and Re-Attaching PostgreSQL dSources

Detaching a dSource
Attaching a dSource
This topic describes how to detach dSources and re-attach them to a different source database.
Each dSource contains an association with the source database, as well as the data it has pulled from the source database up to that point. It is
possible to detach, or unlink, a dSource from its source database. This breaks the association with the source database without affecting the data
within the Delphix Engine. Detached dSources and their source databases have these properties:
You can use detached dSources as the source of virtual database (VDB) provisioning operations.
You can re-link the source database as a different dSource.

Detaching a dSource
1. Login to the Delphix Admin application as a user with OWNER privileges on the dSource, group, or domain.
2. Click Manage.
3. Select My Databases.
4. Select the database you want to unlink or delete.
5. Click the Unlink icon.
A warning message will appear.
6. Click Yes to confirm.

Attaching a dSource
Rebuilding Source Databases and Using VDBs
In situations where you want to rebuild a source database, you will need to detach the original dSource and create a new one
from the rebuilt data source. However, you can still provision VDBs from the detached dSource.
1. Detach the dSource as described above.
2. Rename the detached dSource by clicking the Edit icon in the upper left-hand corner of the dSource card, next to its
name.
This is necessary only if you intend give the new dSource the same name as the original one. Otherwise, you will see
an error message.
3. Create the new dSource from the rebuilt database.
You will now be able to provision VDBs from both the detached dSource and the newly created one, but the detached dSource
will only represent the state of the source database prior to being detached.

The attach operation is currently only supported from the command line interface (CLI). Full GUI support will be added in a future release. Only
databases that represent the same physical database can be re-attached
1. Login to the Delphix CLI as a user with OWNER privileges on the dSource, group, or domain.
2. Select the dSource by name using database select <dSource>.
3. Run the attachSource command.
4. Set the source config to which you want to attach using set source.config=<newSource>. Source configs are named by their
database unique name.
5. Set any other source configuration operations as you would for a normal link operation.
6. Run the commit command.

Attaching PostgreSQL dSource

Attaching PostgreSQL dSource requires a staging instance. This is specified by the pptRepository parameter under the attachSou
rce command.

470

Delphix User Guide 2016 Delphix

Deleting a PostgreSQL dSource

This topic describes how to delete a dSource.

Prerequisites
You cannot delete a dSource that has dependent virtual databases (VDBs). Before deleting a dSource, make sure that you have deleted all
dependent VDBs as described in Deleting a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the Databases panel, select the dSource you want to delete.
6. Click the Trash Can icon.
7. Click Yes to confirm.

Deleting a dSource will also delete all snapshots, logs, and descendant VDB Refresh policies for that database. You cannot
undo the deletion.

471

Delphix User Guide 2016 Delphix

PostgreSQL dSource Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

472

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

473

Delphix User Guide 2016 Delphix

Provisioning VDBs from PostgreSQL dSources

These topics describe concepts and tasks for provisioning virtual databases (VDBs) from PostgreSQL dSources.
Provisioning PostgreSQL VDBs: Overview
Provisioning a PostgreSQL VDB
Enabling and Disabling PostgreSQL VDBs
Refreshing a PostgreSQL VDB
Deleting a PostgreSQL VDB
Migrating a PostgreSQL VDB
Provisioning a PostgreSQL VDB from a Replicated dSource or VDB
PostgreSQL VDB Icon Reference
Customizing PostgreSQL VDB Configuration Settings

474

Delphix User Guide 2016 Delphix

Provisioning PostgreSQL VDBs: Overview

This topic describes the basic concepts involved with provisioning a virtual database (VDB) from a PostgreSQL dSource.
A dSource is a virtualized representation of a physical or logical source database. As a virtual representation, it cannot be accessed or
manipulated using database tools. Instead, you must create a virtual database (VDB) from a dSource snapshot. A VDB is an independent,
writeable copy of a dSource snapshot. You can also create VDBs from other VDBs. Once a VDB has been provisioned to a target environment,
you can also implement a snapshot policy for that VDB, to capture changes within it as if it were any other logical or physical database.
For an overview of the high-level components involved in provisioning a PostgreSQL VDB, see to Setting Up PostgreSQL Environments: An
Overview.

Validated Sync and LogSync

When you link a source database into the Delphix Engine, you must also specify a target environment that will host a staging database for the
validated sync process, as described in Setting Up PostgreSQL Environments: An Overview. In this process, the Delphix Engine continuously
monitors the source database for new transaction logs. When it detects one, it applies that transaction log to the staging database. The result is a
TimeFlow.
Snapshots accumulate over time, and are available when you select the dSource in the My Databases panel of the Delphix Admin application.
Each snapshot is represented as a card that includes information about the source database, operating system, end stamp, and snapshot
database change number (LSN). You can scroll through these cards to select the one you want, or enter a date and time to search for a specific
snapshot.
If LogSync is enabled, you will also see a LogSync slider control at the top of the snapshot card. If you slide this control to the right to open
LogSync, you will see a pointer that you can move along a timeline to select the exact time from which you want to provision a VDB.
Once a VDB has been provisioned, you can also take snapshots of it. As with the dSource snapshots, you can find these when you select the
VDB in the My Databases panel. You can then provision additional VDBs from these VDB snapshots.

Target Environments for VDBs

It is possible to provision a VDB to the same source environment that contains the dSource, but performance and efficiency are improved if the
dSource is located in one environment, and the VDB in another. A target environment may be used both for staging databases and for VDBs. The
source and target environments must be running the same DBMS/Operating System combination (for example, PostgreSQL 9.2 on RHEL 6.3) in
order to successfully provision a VDB, as described in Supported Operating Systems and Database Versions for PostgreSQL Environments
.

Customizing VDB Configuration Settings and File Paths

When you provision a VDB, you have the option of customizing its configuration settings, and the file paths, that it will use on the target
environment. During the provisioning process, you can see the default configuration settings and file paths by clicking the Advanced link in the Ta
rget Environment screen of the VDB Provisioning Wizard.

Related Links
Setting Up PostgreSQL Environments: An Overview
Requirements for PostgreSQL Target Hosts and Databases
Supported Operating Systems and Database Versions for PostgreSQL Environments
Provisioning a PostgreSQL VDB

475

Delphix User Guide 2016 Delphix

Provisioning a PostgreSQL VDB

This topic describes how to provision a virtual database (VDB) from a PostgreSQL dSource.

Prerequisites
You will need to have linked a dSource from a source database, as described in Linking a PostgreSQL dSource, or have already
created a VDB from which you want to provision another VDB

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource.
6. Select a dSource snapshot.
See Provisioning by Snapshot and LogSync in this topic for more information on provisioning options.
You can take a snapshot of the dSource to provision from by clicking the Camera icon on the dSource card.

7. Optional: Slide the LogSync slider to the open the snapshot timeline, and then move the arrow along the timeline to provision from a
point in time within a snapshot.
8. Click Provision.
The VDB Provisioning Wizard will open, and the fields Installation, Mount Base, and Environment User will auto-populate with
information from the environment configuration.
9. Enter a Port Number.
The TCP port upon which the VDB will listen.
10. Click Advanced to enter any VDB configuration settings.
For more information, see Customizing PostgreSQL VDB Configuration Settings.
11. Click Next to continue to the VDB Configuration tab.
12. Modify the VDB Name if necessary.
13. Select a Target Group for the VDB.
14. Click the green Plus icon to add a new group, if necessary.
15. Select a Snapshot Policy for the VDB.
16. Click the green Plus icon to create a new policy, if necessary.
17. Click Next to continue to the Hooks tab.
18. Specify any Hooks to be used during the provisioning process.
For more information, see Customizing PostgreSQL Management with Hook Operations.
19.

Click Next to continue to the Summary tab.

20. Click Finish.

When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the
VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database and its Data
Management settings.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any snapshot by selecting that snapshot card from the Timeflow view, or by
entering a value in the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.
When provisioning by LogSync information, you can provision to any point in time within a particular snapshot. The TimeFlow view for a dSource
shows multiple snapshots by default. To view the LogSync data for an individual snapshot, use the Slide to Open LogSync control at the top of
an individual snapshot card to view the time range within that snapshot. Drag the red triangle to the point in time that you want to provision from.
You can also enter a date and time directly.

476

Delphix User Guide 2016 Delphix

Related Links
Linking a PostgreSQL dSource
Requirements for PostgreSQL Target Hosts and Databases
Using Pre- and Post-Scripts with dSources and VDBs
Customizing PostgreSQL VDB Configuration Settings

477

Delphix User Guide 2016 Delphix

Enabling and Disabling PostgreSQL VDBs

This topic describes how to enable and disable staging, provisioning, and linking for databases.
Before you can use a database as a dSource, you must first make sure that you have defined a staging environment and enabled linking to it.
Similarly, before you can provision a virtual database (VDB) to a target database, you must make sure that you have enabled provisioning to
it.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. To enable or disable staging, slide the button next to Use as Staging to Yes or No.
6. To enable or disable provisioning, slide the button next to Allow Provisioning to On or Off.

478

Delphix User Guide 2016 Delphix

Refreshing a PostgreSQL VDB

Unable to render {include}

The included page could not be found.

479

Delphix User Guide 2016 Delphix

Deleting a PostgreSQL VDB

This topic describes how to delete a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Click My Databases.
4. Select the VDB you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

480

Delphix User Guide 2016 Delphix

Migrating a PostgreSQL VDB

This topic describes how to migrate a virtual database (VDB) from one target environment to another.
There may be situations in which you want to migrate a virtual database to a new target environment for example, when upgrading the host on
which the VDB resides, or as part of a general data center migration. This is easily accomplished by first disabling the database, then using the
Migrate VDB feature to select a new target environment.
Prerequisites
Procedure
Video

Prerequisites
You must have already set up a new target environment that is compatible with the VDB that you want to migrate.

Procedure
1. Login to your Delphix Engine using Delphix Admin credentials.
2. Click Manage.
3. Click My Databases.
4. Select the VDB you want to migrate.
5. Click the Open icon.
6. Slide the Enable/Disable control to Disabled.
7. Click Yes to confirm.
When the VDB is disabled, its icon will turn gray.
8. In the lower right-hand corner of the VDB card, click the VDB Migrate icon.
9. Select the new target environment for the VDB, the user for that environment, and the database installation where the VDB will
reside.
10. Click the Check icon to confirm your selections.
11. Slide the Enable/Disable control to Enabled.
12. Click Yes to confirm.
Within a few minutes, your VDB will re-start in the new environment, and you can continue to work with it as you would with any other
VDBs.

Video

481

Delphix User Guide 2016 Delphix

Provisioning a PostgreSQL VDB from a Replicated dSource or VDB

This topic describes how to provision from a replicated dSource or virtual database (VDB). The process for provisioning from replicated objects is
the same as the typical VDB provisioning process, except that first you need to select the replica containing the replicated object.
Prerequisites
Procedure
Post-Requisites

Prerequisites
You must have replicated a dSource or a VDB to the target host, as described in Replication Overview.
You must have added a compatible target environment on the target host.

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB you want to provision.
6. The provisioning process is now identical to the process for provisioning standard objects.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

482

Delphix User Guide 2016 Delphix

PostgreSQL VDB Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

483

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

484

Delphix User Guide 2016 Delphix

Customizing PostgreSQL VDB Configuration Settings

This topic describes how to customize VDB configuration settings, including settings that are reserved by the Delphix Engine, those that are
removed from the database configuration file during the provisioning process, and those that can be customized.

VDB Configuration
When you create a VDB, configuration settings are copied from the dSource and used to create the VDB. Most settings are copied directly, and
you can see these settings by clicking the Advanced link in the Target Environment screen in the VDB Provisioning Wizard. When a VDB is
provisioned, you can specify configuration parameters directly. It is important to know, however, that some configuration parameters are not
customizable, and some are stripped out during the provisioning process but are customizable. The list of restricted and customizable parameters
can be found below.

VDB Access Control

By default, VDBs are provisioning with a pg_hba.conf file that only permits local connections to the VDB. To enable remote connections to
VDBs, customize the pg_hba.conf settings in the provisioning wizard.

Restricted Parameters
These parameters are restricted for use by the Delphix Engine. Attempting to customize these parameters will cause an error during the
provisioning process.
archive_command
archive_mode
wal_level
port
data_directory
config_file
hba_file
ident_file
max_stack_depth
wal_segment_size
block_size
lc_ctype
segment_size
wal_block_size
lc_collate
server_version
integer_datetimes
server_encoding
server_version_num
max_identifier_length
max_index_keys
max_function_args
include
include_if_exists

485

Delphix User Guide 2016 Delphix

Customizing PostgreSQL Management with Hook Operations

Hook operations allow you to execute an ordered list of custom operations at select hook points in linking, provisioning and virtual dataset
management. For details on the types of operations that are available, see children of this page.
dSource Hooks
Virtual Dataset Hooks
Setting Hook Operations
Setting Hook Operations through the Delphix Admin Application
Setting Hook Operations through the CLI
Example of Editing Hook Operations through the CLI
Hook Operation Templates
Creating a Hook Operation Template
Importing a Hook Operation Template
Exporting a Hook Operation Template

dSource Hooks
Hook

Description

Pre-Sync

Operations performed before a sync.

These operations can quiesce data to be captured during the sync, or stop processes that may interfere with the sync.

Post-Sync

Operations performed after a sync. This hook will run regardless of the success of the sync or Pre-Sync hook operations.
These operations can undo any changes made by the Pre-Sync hook.

Virtual Dataset Hooks

Hook

Description

Configure
Clone

Operations performed after initial provision or after a refresh. This hook will run after the virtual dataset has been started.
During a refresh, this hook will run before the Post-Refresh hook.

Pre-Refresh

Operations performed before a refresh.

These operations can cache data from the virtual dataset to be restored after the refresh completes.

Post-Refresh

Operations performed after a refresh. During a refresh, this hook will run after the Configure Clone hook. This hook will not run
if the refresh or Pre-Refresh hook operations fail.
These operations can restore cached data after the refresh completes.

Pre-Rewind

Operations performed before a rewind.

These operations can cache data from the virtual dataset to be restored after the rewind completes.

Post-Rewind

Operations performed after a rewind. This hook will not run if the rewind or Pre-Rewind hook operations fail.
These operations can restore cached data after the rewind completes.

Pre-Snapshot

Operations performed before a snapshot.

These operations can quiesce data to be captured during the snapshot, or stop processes that may interfere with the
snapshot.

Post-Snapshot

Operations performed after a snapshot. This hook will run regardless of the success of the snapshot or Pre-Snapshot hook
operations.
These operations can undo any changes made by the Pre-Snapshot hook.

Operation Failure
If a hook operation fails, it will fail the entire hook: no further operations within the failed hook will be run.

Setting Hook Operations

486

Delphix User Guide 2016 Delphix

You can construct hook operation lists through the Delphix Admin application or the command line interface (CLI). You can either define the
operation lists as part of the linking or provisioning process or edit them on dSources or virtual datasets that already exist.

Setting Hook Operations through the Delphix Admin Application

To specify hook operations during linking or provisioning, navigate to the Hooks tab of the Linking Wizard or Provision Wizard.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation or click Import to load a hook operation template.
4. Click the text area and edit the contents of the operation.
5. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
6. To remove an operation from the list, click the Trash icon on the operation.
7. When you have set all hook operations, click Next to continue with the provisioning process.
To edit hook operations on an already-existing dSource or virtual dataset, navigate to the Hooks tab on the back of the dSource card or virtual
dataset card.
1. Select the hook to edit.
2. The current operations at this hook will be displayed. To edit this list of operations, click the Pencil icon in the top right-hand corner of the
card.
3. Click the Plus icon to add a new operation.
4. Select the type of operation or click Import to load a hook operation template.
5. Click the text area and edit the contents of the operation.
6. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
7. To remove an operation from the list, click the Trash icon on the operation.
8. When you have set all hook operations, click Check to save the changes.

Setting Hook Operations through the CLI

To specify hook operations during linking, edit the relevant hook's array of operations defined on the LinkingParameters > Source >
Operations object.
To specify hook operations during provisioning, edit the relevant hook's array of operations defined on the ProvisionParameters > Source
> Operations object.
To edit hook operations on an already-created dSource, edit the relevant hook's array of operations defined on the Source > Operations obje
ct.
To edit hook operations on an already-created virtual dataset, edit the relevant hook's array of operations defined on the Source > Operation
s object.
For more information about these CLI objects, see the LinkedSourceOperations, VirtualSourceOperations, RunCommandOnSourceOp
eration, and RunExpectOnSourceOperation API documentation in the Help menu of the Delphix Admin application.

Example of Editing Hook Operations through the CLI

1. Navigate to the relevant source's VirtualSourceOperations object.
2. Select a hook to edit.
delphix> source
delphix source> select "pomme"
delphix source "pomme"> update
delphix source "pomme" update *> edit operations
delphix source "pomme" update operations *> edit postRefresh
3. Add an operation at index 0.
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
Properties
type: RunCommandOnSourceOperation (*)
command: echo Refresh completed. (*)
delphix source "pomme" update operations postRefresh

487

*> add
0 *> set type=RunCommandOnSourceOperation
0 *> set command="echo Refresh completed."
0 *> ls

0 *> commit

Delphix User Guide 2016 Delphix

4. Add another operation at index 1 and then delete it.

delphix
delphix
delphix
delphix
delphix
delphix

source
source
source
source
source
source

"pomme"
"pomme"
"pomme"
"pomme"
"pomme"
"pomme"

update
update
update
update
update
update

operations
operations
operations
operations
operations
operations

postRefresh
postRefresh
postRefresh
postRefresh
postRefresh
postRefresh

*> add
1 *> set type=RunCommandOnSourceOperation
1 *> set command="echo Refresh completed."
1 *> back
*> unset 1
*> commit

Hook Operation Templates

You can use templates to store commonly used operations, which allows you to avoid repeated work when an operation is applicable to more
than a single dSource or virtual dataset. You manage templates through the Delphix Admin application.
Hook Operations Templates Not Available via CLI
Hook operation templates cannot be fully utilized from the CLI. Manage and use hook operations through the Delphix Admin applicatio
n.

Creating a Hook Operation Template

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Operation Templates.
4. Click the Plus icon to add a new operation template.
5. Enter a Name for the template.
6. Select an operation Type.
7. Enter a Description detailing what the operation does or how to use it.
8. Enter operation Contents to implement the operation partially or fully.
9. Click Create.

Importing a Hook Operation Template

To import a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Click Import.
4. Select the template to import.
5. Click Import.
6. When you have set all hook operations, click Check to save the changes.

Exporting a Hook Operation Template

To export a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation.
4. Click the text area and edit the contents of the operation.
5. Click Export.
6. Enter a Name for the template.
7. Enter a Description detailing what the operation does or how to use it.
8. Click Create.

488

Delphix User Guide 2016 Delphix

PostgreSQL Hook Operation Notes

Shell Operations
RunCommand Operation
RunBash Operation
Shell Operation Tips
Other Operations
RunExpect Operation
PostgreSQL Environment Variables
dSource Environment Variables
VDB Environment Variables

Shell Operations
RunCommand Operation

The RunCommand operation runs a shell command on a Unix environment using whatever binary is available at /bin/sh. The environment user
runs this shell command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the shell command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Examples of RunCommand Operations

You can input the full command contents into the RunCommand operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
if test -d "$remove_dir"; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
If a script already exists on the remote environment and is executable by the environment user, the RunCommand operation can execute this
script directly.

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh "$ARG_ENVIRONMENT_VARIABLE" "second

argument in double quotes" 'third argument in single quotes'
RunBash Operation

The RunBash operation runs a Bash command on a Unix environment using a bash binary provided by the Delphix Engine.The environment user
runs this Bash command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the Bash command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of RunBash Operations

You can input the full command contents into the RunBash operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
# Bashisms are safe here!
if [[ -d "$remove_dir" ]]; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
Shell Operation Tips
Using nohup

489

Delphix User Guide 2016 Delphix

You can use the nohup command and process backgrounding from resource in order to "detach" a process from the Delphix Engine. However, if
you use nohup and process backgrounding, you MUST redirect stdout and stderr.
Unless you explicitly tell the shell to redirect stdout and stderr in your command or script, the Delphix Engine will keep its connection to the
remote environment open while the process is writing to either stdout or stderr . Redirection ensures that the Delphix Engine will see no more
output and thus not block waiting for the process to finish.
For example, imagine having your RunCommand operation background a long-running Python process. Below are the bad and good ways to do
this.
Bad Examples
nohup
nohup
nohup
nohup

python
python
python
python

file.py
file.py
file.py
file.py

& # no redirection
2>&1 & # stdout is not redirected
1>/dev/null & # stderr is not redirected
2>/dev/null & # stdout is not redirected

Good Examples
nohup python file.py 1>/dev/null 2>&1 & # both stdout and stderr redirected, Delphix Engine will not
block

Other Operations
RunExpect Operation

The RunExpect operation executes an Expect script on a Unix environment. The Expect utility provides a scripting language that makes it easy to
automate interactions with programs which normally can only be used interactively, such as ssh. The Delphix Engine includes a
platform-independent implementation of a subset of the full Expect functionality.
The script is run on the remote environment as the environment user from their home directory. The Delphix Engine captures and logs all output
of the script. If the operation fails, the output is displayed in the Delphix Admin application and CLI to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunExpect Operation

Start an ssh session while interactively providing the user's password.

spawn ssh [email protected]

expect {
-re {Password: } {
send "${env(PASSWORD_ENVIRONMENT_VARIABLE)}\n"
}
timeout {
puts "Timed out waiting for password prompt."
exit 1
}
}
exit 0
PostgreSQL Environment Variables
Operations that run user-provided scripts have access to environment variables. For operations associated with specific dSources or virtual
databases (VDBs), the Delphix Engine will always set certain environment variables so that the user-provided script can use them to access the
dSource or VDB.
dSource Environment Variables

No environment variables are set.

VDB Environment Variables

Environment Variable

Description

PGDATA

The path to the VDB data files mounted from the Delphix Engine

490

Delphix User Guide 2016 Delphix

PGPORT

The port on which the VDB is listening

PGUSER

The database user used to connect to the VDB

PGDATABASE

The VDB name within the PostgreSQL database cluster

491

Delphix User Guide 2016 Delphix

MySQL Environments and Data Sources

492

Delphix User Guide 2016 Delphix

MySQL Support and Requirements

These topics describe specific requirements for MySQL environments, such as user privileges, as well as the supported operating systems and
database versions.
Requirements for MySQL Source Hosts and Databases
Requirements for MySQL Target/Staging Hosts and Databases
Network and Connectivity Requirements for MySQL Environments
Supported Operating Systems and Database Versions for MySQL Environments

493

Delphix User Guide 2016 Delphix

Requirements for MySQL Source Hosts and Databases

Source hosts are servers which contain the source databases from which virtual database copies are made. Collectively, the source host and
source database are referred to as the "source environment." This topic describes the requirements for creating connections between MySQL
source environments and the Delphix Engine.

Source Host Requirements

On 64-bit Linux environments, a 32-bit version of glibc must be installed.
There must be an operating system user with the following privileges:
The Delphix Engine must be able to make an SSH connection to the source environment using the operating system user.
The operating system user must have read and execute privileges on the MySQL binaries installed on the source environment.
There must be a directory on the source host where the Delphix Engine toolkit can be installed (for example, /var/tmp) with the following
properties:
The toolkit directory must have 770 mode and be owned by the operating system user mentioned above to avoid creating a fault.
The toolkit directory must have at least 1.5 GB of available storage.

TCP/IP connectivity to and from the source environment must be configured as described in
and Connectivity Requirements.

General Network

Java version 6 or greater must be installed on the host.

Source Database Requirements

If you are providing the MySQL backup file, the operating system user must have read privilege on the MySQL backup file.
This can be an existing user or a newly created one for example, "delphix."
The MySQL user must be configured to have "replication slave" privilege from the Delphix Engine IP, as well as the staging host IP.
Allowing Replication Slave permissions from IPs
To grant the privilege for the user, use the following command:
SQL> GRANT REPLICATION SLAVE ON *.* TO '<delphix>'@'<staging_target_ip>';
SQL> GRANT REPLICATION SLAVE ON *.* TO '<delphix>'@'<delphix_engine_ip>';
If Delphix Engine has to take backup of the MySQL databases, additional privileges for the MySQL user are required.
The MySQL user must also have the following roles: SELECT, RELOAD, REPLICATION CLIENT, SHOW VIEW, EVENT, and
TRIGGER.
The operating system user must have read and execute privileges on the mysqldump binary installed on the source environment.
Binary logging must be enabled on MySQL source instance.
Server ID for the source must be greater than 0.

Related Links
General Network and Connectivity Requirements

494

Delphix User Guide 2016 Delphix

Requirements for MySQL Target/Staging Hosts and Databases

This topic describes user privileges and other requirements for MySQL target hosts and databases, collectively referred to as the "target
environment."

Target Environment Requirements

The operating system and architecture of the target environment must match those of the source environment.
There must be an installation of MySQL on the target environment that is compatible with an installation of MySQL on the source
environment. Two installations of MySQL are compatible if and only if:
They share the same vendor. For example, MySQL Community Edition is incompatible with MariaDB.
They share the same major and release number if the release is already GA. For example, 5.5.36 is compatible with 5.5.37, but
5.7.5 is not compatible with 5.7.6 because 5.7.5 and 5.7.6 are not GA versions. For non-GA versions, the major, release, and
version numbers should match. For example, 5.7.5 is compatible with 5.7.5.
They were compiled against the same architecture. In other words, 32-bit and 64-bit installations of MySQL are incompatible.
On 64-bit Linux environments, a 32-bit version of glibc must be installed.
There must be an operating system user with the following privileges:
The Delphix Engine must be able to make an SSH connection to the target environment using the operating system user.
The operating system user must have read and execute privileges on the MySQL binaries installed on the target environment.
The operating system user must have permission to run mount and umount as the superuser via sudo with neither a password
nor a TTY via the following entries in /etc/sudoers.conf:

/etc/sudoers Configuration
Defaults:<username> !requiretty
<username> ALL=NOPASSWD:/bin/mount, /bin/umount
There must be a directory on the target environment where the Delphix Engine toolkit can be installed (for example, /var/tmp) with the
following properties:
The toolkit directory must have 770 mode and be owned by the operating system user to avoid creating a fault.
The toolkit directory must have at least 1.5 GB of available storage.
NFS must be running on the host.
There must be a mount point directory (for example, /mnt/provision) that will be used as the base for mount points that are created when
provisioning a VDB. The mount point directory must:
be writable by the operating system user mentioned above.
be empty.
TCP/IP connectivity to and from the source environment must be configured as described in General Network and Connectivity
Requirements.
Java version 6 or greater must be installed on the host.

Related Links
Using HostChecker to Confirm Source and Target Environment Configuration
sudoers Manual Page

495

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for MySQL Environments

General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration
Connection Requirements for MySQL Environments
Port Allocation for MySQL Environments
Outbound from the Delphix Engine Port Allocation
Inbound to the Delphix Engine Port Allocation
Port Allocation Between Source and Staging Target Environments

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

496

Delphix User Guide 2016 Delphix

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

Connection Requirements for MySQL Environments

The Delphix Engine uses an SSH connection to each source environment and JDBC connections to the MySQL instances on the source
environment.
The Delphix Engine uses an SSH connection to each target environment, NFS connections from each target environment to the Delphix
Engine, JDBC and MySQL client connections to the virtual databases on the target environment.
Once connected to a staging target environment through SSH, the Delphix Engine initiates a MySQL replication client connection from
the staging target environment to the source environment.

Port Allocation for MySQL Environments

The following diagram describes the port allocations for MySQL environments. It illustrates the ports that we recommend to be open from Delphix
to remote services, to the Delphix Engine, and to the Target Environments.

The Delphix Engine makes use of the following network ports for MySQL dSources and VDBs:

Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

22

SSH connections to source and target database environments

TCP

xxx

MySQL client connections/JDBC connections to the MySQL instances on the source and target environments (port
3306 by default)

497

Delphix User Guide 2016 Delphix

Inbound to the Delphix Engine Port Allocation

Protocol

Port Number

Use

TCP/UDP

111

Remote Procedure Call (RPC) port mapper used for NFS mounts

TCP

1110

Network Status Monitor (NSM) client from target hosts to the Delphix Engine

TCP/UDP

2049

NFS client from target hosts to the Delphix Engine

TCP

4045

Network Lock Manager (NLM) client from target hosts to the Delphix Engine

UDP

33434 - 33464

Traceroute from source and target database servers to the Delphix Engine (optional)

Port Allocation Between Source and Staging Target Environments

Outgoing

Incoming

Protocol

Port
Number

Use

Target
Environment

Source
Environment

MySQL
replication client

xxx

MySQL replication client connection to the MySQL instances on the source

environment (port 3306 by default)

498

Delphix User Guide 2016 Delphix

Supported Operating Systems and Database Versions for MySQL Environments

This topic describes supported operating systems and database versions for MySQL.
Source and Target OS and DBMS Compatibility
The source and target environments must be running the same DBMS/Operating System combination (for example, MySQL 5.6 on
RHEL 6.3) in order to successfully perform linking and provisioning.

Supported DBMS Versions

DBMS Versions

Operating System Versions

Processor Family

MySQL Community Edition GA 5.5, 5.6

RHEL 6.2, 6.3, 6.4

x86_64

MySQL Community Edition >=5.7.7

RHEL 6.2, 6.3, 6.4

x86_64

MySQL Enterprise Edition GA 5.6

Solaris 11, RHEL 6.2, 6.3, 6.4

x86_64

MariaDB Server 10.0 GA Series (>=10.0.10)

RHEL 6.2, 6.3, 6.4

x86_64

MariaDB Enterprise 10.0 GA Series (>=10.0.10)

RHEL 6.2, 6.3, 6.4

x86_64

Supported MySQL Storage Engine

Storgage Engine
InnoDB

499

Delphix User Guide 2016 Delphix

Managing MySQL Environments

These topics describe special tasks and concepts for working with PostgreSQL environments.
Setting Up MySQL Environments: An Overview
Using HostChecker to Validate MySQL Source and Target Environments
Adding a MySQL Environment
Adding an Installation to a MySQL Environment
Adding a MySQL Server to a MySQL Environment
Editing MySQL Environment Attributes
Changing the Host Name or IP Address for MySQL Source and Target Environments
Deleting a MySQL Environment
Managing MySQL Environment Users
Refreshing a MySQL Environment
Enabling Staging, Linking, and Provisioning for MySQL Environments

500

Delphix User Guide 2016 Delphix

Setting Up MySQL Environments: An Overview

This topic describes the high-level process for adding MySQL environments, linking MySQL data sources to the Delphix Engine, and provisioning
virtual databases from MySQL data sources.

Types of MySQL Environments

At a high level, the Delphix Engine maintains an internal representation of a data source, from which you can provision virtual databases (VDBs).
In order to link a data source and provision a VDB, the following types of environments are required:
A source environment is where the unvirtualized source database runs. The Delphix Engine uses the backup, restore, and replication features of
the MySQL DBMS to maintain its internal representation of the source database, to be used for provisioning VDBs. The Delphix Engine must be
able to connect to the source environment in order to discover all running database instances on the source and to orchestrate backup, restore,
and replication functionality necessary to keep its internal representation synchronized with the source. The Delphix Engine is designed to have
minimal impact on the performance of the source database and the source environment.
A target environment is where virtualized databases run. MySQL target environments serve two purposes:
1. A replication slave must be created per source database instance with all database files stored on the Delphix Engine to allow the internal
representation of each source database instance to stay synchronized with the source. We refer to the creation and maintenance of this
staging database as "validated sync." During validated sync, the Delphix Engine retrieves data from the source and ensures that all the
components necessary for provisioning a VDB have been validated. The result of validated sync is a TimeFlow with consistent points
from which you can provision a VDB in a fast provisioning process where there is no need for database recovery. In order to create a
staging database, you must designate a target environment when linking a dSource. During the linking process, database files are
exported over the network to the target environment, where the staging database instance runs as a replication slave. A target
environment that hosts one or more staging databases is referred to as a "staging target" for validated sync.
2. Once a staging database has been set up, you can provision VDBs from any point in time along with the TimeFlow mentioned above to
any compatible target environment. Database files are exported over the network to the target environment, where the virtual databases
instance run. For more information, see Requirements for MySQL Target/Staging Hosts and Databases.

Workflow for MySQL Environments

Prior to linking a data source, you must add to the Delphix Engine both a source environment and a compatible target environment, to be used for
the staging database, or dSource, mentioned above. Prior to provisioning a virtual database, you must also add a compatible target environment
to the Delphix Engine. This can be either the same target environment as the one used for the staging instance, or a different target environment.
Once you have added an environment to the Delphix Engine, environment discovery takes place. "Environment discovery" is the process of
enumerating MySQL installations and running database server instances when a source or target environment is added to the Delphix
Engine. We also repeat the discovery process during environment refresh in order to detect any new MySQL installations or running database
server instances. MySQL installations and database instances can also be added manually if automated discovery was unsuccessful.

501

Delphix User Guide 2016 Delphix

Using HostChecker to Validate MySQL Source and Target Environments

This topic describes how to use HostChecker to configure MySQL environments.
What is HostChecker?
Prerequisites
Procedure
Tests Run
Related Links

What is HostChecker?
The HostChecker is a standalone program which validates that host machines are configured correctly before the Delphix Engine uses them as
data sources and provision targets.
Please note that HostChecker does not communicate changes made to hosts back to the Delphix Engine. If you reconfigure a host, you must
refresh the host in the Delphix Engine in order for it to detect your changes.
You can run the tests contained in the HostChecker individually, or all at once. You must run these tests on both the source and target hosts to
verify their configurations. As the tests run, you will either see validation messages that the test has completed successfully, or error messages
directing you to make changes to the host configuration.

Prerequisites
Ensure that your source and target environments meet the requirements specified in MySQL Support and Requirements.

Procedure
1. Download HostChecker tarball for the O/S version that runs on the source or target hosts.
a. For Linux, hostchecker_linux_x86.tar
b. For Solaris, hostchecker_sunos_sparc.tar
c. For HP-UX, hostchecker_hpux_ia64.tar
2. Create a working directory and extract the HostChecker files from the HostChecker tarball.

mkdir dlpx-host-checker
cd dlpx-host-checker/
tar -xf hostchecker_linux_x86.tar
3. Change to hostchecker sub-directory and enter this command:

$ ./hostchecker.sh
Do Not Run as Root
Do not run the HostChecker as root; this will cause misleading or incorrect results from many of the checks.

4. Select which host you want to check: source or target.

5. Select checks you want to run. If you are running Hostchecker for the first time, we recommend you run all checks.
6. Pass in the arguments for which the check asks.
7. Read the output of the check.
8. The error or warning messages will explain any possible problems and how to address them. Resolve the issues that the HostChecker
describes. Do not be surprised or undo your work if more errors appear the next time you run HostChecker; the error you just fixed may
have been masking other problems.
9. Repeat steps 57 until all the checks return no errors or warnings.

Tests Run
Test

MySQL
Source

MySQL
Target

Description

502

Delphix User Guide 2016 Delphix

Check Host
SSH
Connectivity

Verifies that the environment is accessible via SSH

Check Tool
Kit Path

Verifies that the toolkit installation location has the proper ownership, proper permissions, and enough free
space

Check
Home
Directory
Permissions

Verifies that the environment can be accessed via SSH using public key authentication. If you do not need
this feature, you can ignore the results of this check.

Verifies that the operating system user can execute certain commands with necessary privileges via sudo.
This only needs to be run on target environments. For more information, see Requirements for MySQL
Target/Staging Hosts and Databases.

Verifies that the appropriate MySQL binaries are executable by the current user for the specified
MySQLinstallation. For more information, see Requirements for MySQL Source Hosts and Databases a
nd Supported Operating Systems and Database Versions for MySQL Environments.

Check OS
User
Privileges
Check
MySQL
installation

Related Links
MySQL Support and Requirements
Managing MySQL Environments

503

Delphix User Guide 2016 Delphix

Adding a MySQL Environment

This topic describes how to add a MySQL source environment to the Delphix Engine.

Prerequisites
Make sure your environment meets the requirements described in the following topics:
Requirements for MySQL Source Hosts and Databases
Requirements for MySQL Target/Staging Hosts and Databases
Supported Operating Systems and Database Versions for MySQL Environments

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Unix/Linux in the operating system menu.
6. Select Standalone Host.
7. Enter the Host IP address.
8. Enter an optional Name for the environment.
9. Enter the SSH port.
The default value is 22.
10. Enter a Username for the environment.
For more information about the environment user requirements, see Requirements for MySQL Target/Staging Hosts and Databases a
nd Requirements for MySQL Source Hosts and Databases.
11. Select a Login Type.
For Password, enter the password associated with the user in step 9.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

12. For Password Login, click Verify Credentials to test the username and password.
13. Enter a Toolkit Path.
For more information about the toolkit directory requirements, see Requirements for MySQL Target/Staging Hosts and Databases an
d Requirements for MySQL Source Hosts and Databases.
14. Click OK.
As the new environment is added, you will see two jobs running in the Delphix Admin Job History, one to Create and Discover an
environment, and another to Create an environment. When the jobs are complete, you will see the new environment added to the list in
the Environments tab. If you do not see it, click the Refresh icon in your browser.

Post-Requisites
To view information about an environment after you have created it:
1. Click Manage.
2.
504

Delphix User Guide 2016 Delphix

2. Select Environments.
3. Select the environment name.

Related Links
Setting Up MySQL Environments: An Overview
Requirements for MySQL Source Hosts and Databases
Requirements for MySQL Target/Staging Hosts and Databases
Supported Operating Systems and Database Versions for MySQL Environments
Adding an Installation to a MySQL Environment

505

Delphix User Guide 2016 Delphix

Adding an Installation to a MySQL Environment

This topic describes how to add an installation to a MySQL environment.
When you add an environment with the Delphix Admin application, all MySQL installations on it are automatically discovered. However, if an
installation is not automatically discovered, you can add it manually to the environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. Click the green Plus icon next to Add Dataset Home.
6. Under Dataset Home Type, select MySQL.
7. Enter the path to the installation.
8. When finished, click the Check icon.

Related Links
Adding a MySQL Server to a MySQL Environment
Managing MySQL Environments

506

Delphix User Guide 2016 Delphix

Adding a MySQL Server to a MySQL Environment

This topic describes how to add a MySQL server to a MySQL environment.
When you add an environment with the Delphix Admin application, all MySQL servers on it are automatically discovered. However, if a server is
not automatically discovered, you can add it manually to the environment.

Prerequisites
Make sure your source database meets the requirements described in Requirements for MySQL Source Hosts and Databases and R
equirements for MySQL Target/Staging Hosts and Databases.
Before adding a database, the installation of the database must exist in the environment. If the installation does not exist in the
environment, follow the steps in Adding an Installation to a MySQL Environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. Choose the installation which has been used to start the database.
If needed, click the Up icon next to the the installation path to show details.
6. Click the green Plus icon next to Add Database.
7. Enter the data directory of the database as the Path.
8. Enter the port the server is running on as Port.
9. When finished, click the Check icon.

Related Links
Requirements for MySQL Source Hosts and Databases
Requirements for MySQL Target/Staging Hosts and Databases
Adding an Installation to a MySQL Environment

507

Delphix User Guide 2016 Delphix

Editing MySQL Environment Attributes

Procedure
Common Editable Attributes
MySQL Attributes
Related Links
This topic describes how to edit attributes of an environment such as name, host address, ssh port, or toolkit path, as well as descriptions of more
advanced attributes for specific data platforms.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials or as the owner of an environment.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of an environment to view its attributes.
5. Under Attributes, click the Pencil icon to edit an attribute.
6. Click the Check icon to save your edits.

Common Editable Attributes

Attribute

Description

Environment
Users

The users for that environment. These are the users who have permission to ssh into an environment, or access the
environment through the Delphix Connector. See the Requirements topics for specific data platforms for more information on
the environment user requirements.

Host
Address

The IP address for the environment host.

Notes

Any other information you want to add about the environment.

MySQL Attributes
Attribute

Description

SSH Port

The port used for secure shell connection to the host

Toolkit Path

The directory used for storing Delphix toolkit files

Related Links
Managing MySQL Environments

508

Delphix User Guide 2016 Delphix

Changing the Host Name or IP Address for MySQL Source and Target Environments
This topic describes how to change the host name or IP address for source and target environments, and for the Delphix Engine.
Procedure
For Source Environments
For VDB Target Environments
For the Delphix Engine

Procedure
For Source Environments
1. Disable the dSource as described in Enabling and Disabling MySQL dSources.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the dSource.

For virtual database (VDB) Target Environments

1. Disable the virtual database (VDB) as described in Enabling and Disabling MySQL VDBs.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the VDB.

For the Delphix Engine

1. Stop all running VDBs by clicking the red Stop button on each VDB card.
2. Disable all dSources as described in Enabling and Disabling MySQL dSources.
3. You can use either the command line interface or the Server Setup application to change the IP address of the Delphix Engine.
a. To use the command line interface, press F2 and follow the instructions described in Setting Up Network Access to the
Delphix Engine.
b. To use the Server Setup application, select System > Server Setup in the Delphix Admin interface, or click Server Setup in the
Delphix Engine login screen.
i. In the Network panel, click Modify.
ii. Under DNS Services, enter the new IP address.
iii. Click OK.
4. Refresh all environments by clicking the blue/green Refresh symbol on the Environments screen.
5. Enable all dSources as described in Enabling and Disabling MySQL dSources.
6. Start all VDBs by clicking the Start button on each VDB card.

Related Links
Enabling and Disabling MySQL dSources
Enabling and Disabling MySQL VDBs
Setting Up Network Access to the Delphix Engine
Managing MySQL Environments

509

Delphix User Guide 2016 Delphix

Deleting a MySQL Environment

This topic describes how to delete an environment.

Prerequisites
You cannot delete an environment that has any dependencies, such as dSources or virtual databases (VDBs). These must be deleted before you
can delete the environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, select the environment you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

Related Links
Managing MySQL Environments

510

Delphix User Guide 2016 Delphix

Managing MySQL Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure

Prerequisites
Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

Related Links
Managing MySQL Environments

511

Delphix User Guide 2016 Delphix

Refreshing a MySQL Environment

This topic describes how to refresh an environment.
After you make changes to an environment that you have already set up in the Delphix Admin application, such as installing a new database
home, creating a new database, or adding a new listener, you may need to refresh the environment to reflect these changes.
During environment discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the
toolkit are:
A JRE
Delphix jar files
The hostchecker utility
Scripts for managing the environment and/or VDBs
Delphix Connector log files
Delphix then executes some of these scripts to discover information about the objects in your environment (where the databases are installed,
the database names, information required to connect to these databases, etc.). In some environments (Windows in particular), the scripts are
customized to fit the customers environment.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of the environment to you want to refresh.
5. Click the Refresh icon.
To refresh all environments, click the Refresh icon next to Environments.

Related Links
Managing MySQL Environments

512

Delphix User Guide 2016 Delphix

Enabling Staging, Linking, and Provisioning for MySQL Environments

This topic describes how to enable and disable staging, provisioning, and linking for databases.
Before you can use a database as a dSource, you must first make sure that you have defined a staging environment and enabled linking to it.
Similarly, before you can provision a virtual database (VDB) to a target database, you must make sure that you have enabled provisioning to
it.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. To enable or disable staging, slide the button next to Use as Staging to Yes or No.
6. To enable or disable provisioning, slide the button next to Allow Provisioning to On or Off.

Related Links
Managing MySQL Environments

513

Delphix User Guide 2016 Delphix

MySQL Data Sources

These topics describe concepts and tasks for linking MySQL data sources to the Delphix Engine.
Linking MySQL Data Sources: Overview
Linking a MySQL dSource
Advanced Data Management Settings for MySQL Data Sources
Using Pre- and Post-Scripts with MySQL dSources
Deleting a MySQL dSource
Detaching and Re-Attaching MySQL dSources
Enabling and Disabling MySQL dSources
MySQL dSource Icon Reference

514

Delphix User Guide 2016 Delphix

Linking MySQL Data Sources: Overview

This topic describes basic concepts behind the creation of dSources from MySQL data sources.

Initial Linking and Staging Databases

A dSource is the copy of a physical database that is created when the Delphix Engine links to and loads the database. The Delphix Engine keeps
the dSource in sync with the source database in order to facilitate the provisioning of virtual databases (VDBs) from the dSource's TimeFlow. The
Delphix Engine will create a replication slave for each source database with all database files stored on the Delphix Engine, as described in Settin
g Up MySQL Environments: An Overview. We refer to the creation and maintenance of this staging database as "validated sync." A target
environment that hosts one or more staging databases is referred to as a "staging target" for validated sync.
When you create a dSource from a MySQL database, the Delphix Engine restores an existing database backup or initiates and restores a full
database backup of the source database on the staging target. The initial snapshot of the dSource is derived from this backup.
After obtaining the initial snapshot and linking the dSource, the Delphix Engine keeps the dSource and the source database synchronized by
setting up the staging database as a replication slave of the source database.

Target Environments for Staging and VDB Provisioning

It is possible to provision a VDB to the same source environment that contains the staging database, but performance and efficiency improve if
the staging database is located in one environment, and the VDB in another. A target environment can be used both for staging databases and for
VDBs. The source and target environments must be running the same DBMS/Operating System combination (for example, MySQL 5.6 on RHEL
6.4) in order to successfully link a dSource, as described in Supported Operating Systems and Database Versions for MySQL Environments
.

Related Links
Setting Up MySQL Environments: An Overview
MySQL Support and Requirements
Supported Operating Systems and Database Versions for MySQL Environments

515

Delphix User Guide 2016 Delphix

Linking a MySQL dSource

This topic describes the basic procedure for linking a dSource from a MySQL database to the Delphix Engine.

Prerequisites
Make sure you have the correct user credentials for the source environment, as described in Requirements for MySQL Source Hosts
and Databases
You may also want to read the topic Advanced Data Management Settings for MySQL Data Sources.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing MySQL Environment Users.

6. Enter your login credentials for DB Username and DB Password.

7. Click Next.
8. Select a Database Group for the dSource.
9. Click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies.
10. Select the Initial Load type.
a. If selecting Existing MySQL Backup, provide the Path to the backup and select the Dump Type.
11. Select a SnapSync Policy, a Staging Installation, and a Staging Port for the dSource.
The Staging installation represents the MySQL binaries that will be used on the staging target to backup and restore the linked
database to a replication slave.
12. If you want to enable LogSync, check the LogSync checkbox.
13. Click Advanced to select a Retention Policy and to manually specify replication coordinates.
For more information, see Advanced Data Management Settings for MySQL Data Sources.
14. Click Next.
15. Specify any operations to run before and after the initial sync.
For more information, see Using Pre- and Post-Scripts with MySQL dSources.
16. Click Next.
17. Review the dSource Configuration and Data Management information.
18. Click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active Jobs in
the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will change to a
dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card, and also make modifications to its policies
and permissions. In the Databases panel, click the Open icon to view the front of the dSource card. The card will then flip, showing you
information such as the Source Database and Data Management configuration. For more information, see Advanced Data
Management Settings for MySQL Data Sources.

Related Links

516

Delphix User Guide 2016 Delphix

Requirements for MySQL Source Hosts and Databases

Advanced Data Management Settings for MySQL Data Sources
Managing MySQL Environment Users
Requirements for MySQL Target/Staging Hosts and Databases
Using Pre- and Post-Scripts with MySQL dSources
Users, Permissions, and Policies

517

Delphix User Guide 2016 Delphix

Advanced Data Management Settings for MySQL Data Sources

Accessing Data Management Settings
During the dSource linking process
On the back of the dSource card
In the top menu bar
Retention Policies
Benefits of Longer Retention
MySQL LogSync Settings
MySQL SnapSync Policy Settings
Related Links
This topic describes advanced data management settings for dSources.
When linking a dSource, you can use custom data management settings to improve overall performance and match the needs of your specific
server and data environment. If no specific settings are required, leverage default data management settings.

Accessing Data Management Settings

There are three ways to set or modify data management settings for dSources:
During the dSource linking process

1. In the Data Management panel of the Add dSource wizard, click Advanced.
On the back of the dSource card

1. Under Data Management, click the field next to Retention Policy

2. Click the Edit icon.
3. For SnapSync and Retention policies, click the policy name. This will open the Policy Management screen.
In the top menu bar

1. Click Manage.
2. Select Policies. This will open the Policy Management screen.
3. Select the policy for the dSource you want to modify.
4. Click Modify.
For more information, see Creating Custom Policies and Creating Policy Templates.

Retention Policies
Retention policies define the length of time that the Delphix Engine retains snapshots and log files to which you can rewind or provision objects
from past points in time. The retention time for snapshots must be equal to, or longer than, the retention time for logs.
To support longer retention times, you may need to allocate more storage to the Delphix Engine. The retention policy in combination with the
SnapSync policy can have a significant impact on the performance and storage consumption of the Delphix Engine.

Benefits of Longer Retention

With increased retention time for snapshots and logs, you allow a longer (older) rollback period for your data.
Common use cases for longer retention include:
SOX compliance
Frequent application changes and development
Caution and controlled progression of data
Reduction of project risk
Speed of rollback / restore to older points in time
With LogSync enabled, you can customize both the retention policy and the SnapSync policy to access logs for longer periods of time, enabling
point-in-time rollback and provisioning.

518

Delphix User Guide 2016 Delphix

MySQL LogSync Settings

LogSync is disabled by default for MySQL dSources.
LogSync settings are accessible during the Add dSource process and on the back of the dSource card.
Enabled - LogSync generates log files which contain database changes from the source database to the dSource, and retains the logs
per policy, enabling the ability to provision a virtual database (VDB) from a specific point in time. LogSync must be enabled for this
functionality to work.

MySQL SnapSync Policy Settings

For default SnapSync policy setting, database snapshots are taken daily at a set time, with a four hour period timeout. You can modify the
snapshot schedule and the frequency by selecting Schedule By.

Related Links
Creating Custom Policies
Creating Policy Templates
MySQL Data Sources

519

Delphix User Guide 2016 Delphix

Using Pre- and Post-Scripts with MySQL dSources

Using Pre- and Post-Scripts with MySQL dSources
Specifying Arguments for MySQL Scripts
An Example with Three Arguments
An Example with an Apostrophe
Related Links
This topic describes the use of pre- and post-scripts with dSources.
For each script, you can add the script path and its arguments when linking a dSource in one of two ways. Either:
During the Add dSource wizard process, in the Data Management screen, click Advanced.
or
On the back of the dSource card, click the Pencil icon next to the Pre Script and Post Script fields.
To update pre- and post-script information:
1. Flip over the dSource card.
2. Click on the Pencil icon next to the Pre Script and Post Script fields.
3. When finished, click the check mark icon.
Note that pre-scripts are executed before the SnapSync policy, and if the script fails, SnapSync will fail as well. In the case of a post-script, the
script will execute after SnapSync is complete. If a post-script fails, you will see an error message.

Using Pre- and Post-Scripts with MySQL dSources

For MySQL dSources, pre- and post-scripts are run during initial sync and during later full syncs.
For MySQL environments, the scripts must exist and be executable on the source environment.
MySQL dSource scripts must be text scripts only.

Specifying Arguments for MySQL Scripts

You can specify multiple arguments for a script.
1. In the Pre or Post Script field, enter the path to the script.
2. List the arguments.
a. If the argument contains spaces, enclose it in single or double quotes. You can escape single quotes within the argument with a
backslash.

An Example with Three Arguments

/opt/mysql/scripts/myscript.sh one "second argument in double quotes" 'third argument in
single quotes'
An Example with an Apostrophe
/opt/mysql/scripts/myscript.sh 'I\'d rather be in Hawaii.'
Related Links
MySQL Data SourcesMySQL Data Sources

520

Delphix User Guide 2016 Delphix

Deleting a MySQL dSource

This topic describes how to delete a dSource.

Prerequisites
You cannot delete a dSource that has dependent virtual databases (VDBs). Before deleting a dSource, make sure that you have deleted all
dependent VDBs as described in Deleting a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the Databases panel, select the dSource you want to delete.
6. Click the Trash Can icon.
7. Click Yes to confirm.

Deleting a dSource will also delete all snapshots, logs, and descendant VDB Refresh policies for that database. You cannot
undo the deletion.

Related Links
MySQL Data Sources

521

Delphix User Guide 2016 Delphix

Detaching and Re-Attaching MySQL dSources

Detaching a dSource
Attaching a dSource
Related Links
This topic describes how to detach dSources and re-attach them to a different source database.
Each dSource contains an association with the source database, as well as the data it has pulled from the source database up to that point. It is
possible to detach, or unlink, a dSource from its source database. This breaks the association with the source database without affecting the data
within the Delphix Engine. Detached dSources and their source databases have these properties:
You can use detached dSources as the source of virtual database (VDB) provisioning operations.
You can re-link the source database as a different dSource.

Detaching a dSource
1. Login to the Delphix Admin application as a user with OWNER privileges on the dSource, group, or domain.
2. Click Manage.
3. Select My Databases.
4. Select the database you want to unlink or delete.
5. Click the Unlink icon.
A warning message will appear.
6. Click Yes to confirm.

Attaching a dSource
Rebuilding Source Databases and Using VDBs
In situations where you want to rebuild a source database, you will need to detach the original dSource and create a new one
from the rebuilt data source. However, you can still provision VDBs from the detached dSource.
1. Detach the dSource as described above.
2. Rename the detached dSource by clicking the Edit icon in the upper left-hand corner of the dSource card, next to its
name.
This is necessary only if you intend give the new dSource the same name as the original one. Otherwise, you will see
an error message.
3. Create the new dSource from the rebuilt database.
You will now be able to provision VDBs from both the detached dSource and the newly created one, but the detached dSource
will only represent the state of the source database prior to being detached.

The attach operation is currently only supported from the command line interface (CLI). Full GUI support will be added in a future release. Only
databases that represent the same physical database can be re-attached
1. Login to the Delphix CLI as a user with OWNER privileges on the dSource, group, or domain.
2. Select the dSource by name using database select <dSource>.
3. Run the attachSource command.
4. Set the source config to which you want to attach using set source.config=<newSource>. Source configs are named by their
database unique name.
5. Set any other source configuration operations as you would for a normal link operation.
6. Run the commit command.

Attaching MySQL dSource

Attaching a MySQL dSource requires a staging instance. This is specified by the pptRepository parameter under the attachSourc
e command.

Related Links

522

Delphix User Guide 2016 Delphix

MySQL Data Sources

523

Delphix User Guide 2016 Delphix

Enabling and Disabling MySQL dSources

This topic describes how to enable and disable dSources for operations such as backup and restore.
For certain processes, such as backing up and restoring the source database, you may want to temporarily disable your dSource. Disabling a
dSource turns off communication between the dSource and the source database, but does not tear down the configuration that enables
communication and data updating to take place. When a disabled dSource is later enabled, it will resume communication and incremental data
updates from the source database according to the original policies and data management configurations that you set.
Disabling a dSource is also a prerequisite for several other operations, like database migration and upgrading the dSource after upgrade of the
associated data source.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the dSource you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the dSource again, move the slider control from Disabled to Enabled, and the dSource will continue to function as
it did previously.

Related Links
MySQL Data Sources

524

Delphix User Guide 2016 Delphix

MySQL dSource Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

525

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

526

Delphix User Guide 2016 Delphix

Provisioning VDBs from MySQL dSources

These topics describe concepts and tasks for provisioning virtual databases (VDBs) from MySQL dSources.
Provisioning MySQL VDBs: Overview
Provisioning a MySQL VDB
Customizing MySQL VDB Configuration Settings
Provisioning a MySQL VDB from a Replicated dSource or VDB
Enabling and Disabling MySQL VDBs
Deleting a MySQL VDB
Migrating a MySQL VDB
Refreshing a MySQL VDB
MySQL VDB Icon Reference

527

Delphix User Guide 2016 Delphix

Provisioning MySQL VDBs: Overview

This topic describes the basic concepts involved with provisioning a virtual database (VDB) from a MySQL dSource.
A dSource is a virtualized representation of a physical or logical source database. As a virtual representation, it cannot be accessed or
manipulated using database tools. A VDB is an independent, and writeable copy of a dSource, which is provisioned from a snapshot of a
dSource. You can also create VDBs from other VDBs. Once you have provisioned a VDB on a target environment, you can implement snapshot
and retention policies for the VDB, which will determine how frequently Delphix engine will take db snapshot and how long the snapshots will be
retained for recovery and provisioning purpose.
For an overview of the high-level components involved in provisioning a MySQL VDB, see Setting Up MySQL Environments: An Overview.

Validated Sync and LogSync

When you link a source database into the Delphix Engine, you must also specify a target environment that will host a staging database for the
validated sync process, as described in Setting Up MySQL Environments: An Overview. In this process, the staging database is set up as a
replication slave of the source database so that it can replay changes as they occur on the source database. The result is a TimeFlow.
Snapshots accumulate over time and are available when you select the dSource in the My Databases panel of the Delphix Admin application.
Each snapshot is represented as a card that includes information about the source database, operating system, and end stamp. You can scroll
through these cards to select the one you want, or you can enter a date and time to search for a specific snapshot.
If LogSync is enabled, you will also see a LogSync slider control at the top of the snapshot card. If you slide this control to the right to open
LogSync, you will see a pointer that you can move along a timeline to select the exact time from which you want to provision a VDB.
Once you have provisioned a VDB, you can also take snapshots of it. As with the dSource snapshots, you can find these when you select the
VDB in the My Databases panel. You can then provision additional VDBs from these VDB snapshots.

Target Environments for VDBs

It is possible to provision a VDB in the same source environment that contains the dSource, but performance and throughput improve if the
dSource is located in one environment, and the VDB in another. You can use a target environment for both staging databases and VDBs. The
source and target environments must be running the same DBMS/Operating System combination (for example, MySQL 5.6 on RHEL 6.3) in order
to successfully provision a VDB, as described in Supported Operating Systems and Database Versions for MySQL Environments.

Customizing VDB Configuration Settings and File Paths

When you provision a VDB, you have the option to customize its configuration settings and the installation path it will use on the target
environment by clicking Advanced and the green Plus icon on the Target Environment screen of the VDB Provisioning Wizard.

Related Links
Setting Up MySQL Environments: An Overview
Requirements for MySQL Target/Staging Hosts and Databases
Supported Operating Systems and Database Versions for MySQL Environments
Provisioning a MySQL VDB

528

Delphix User Guide 2016 Delphix

Provisioning a MySQL VDB

This topic describes how to provision a virtual database (VDB) from a MySQL dSource.

Prerequisites
You must have already:
linked a dSource from a source database, as described in Linking a MySQL dSource
or,
created a VDB from which you want to provision another VDB

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Click My Databases.
4. Select a dSource.
5. Select a dSource snapshot.
For more information on provisioning options, see Provisioning by Snapshot or LogSync below.
6. Optional: Slide the LogSync slider to open the snapshot timeline, and then move the arrow along the timeline to provision from a point
in time within a snapshot.
7. Click Provision.
The VDB Provisioning Wizard will open, and the fields Installation, Mount Base, and Environment User will auto-populate with
information from the environment configuration.
8. Enter a Port Number. This is the TCP port upon which the VDB will listen.
9. Click Advanced followed by clicking the green Plus icon (Add Parameter) to add new or update existing VDB configuration settings on
the template provided.
For more information, see Customizing MySQL VDB Configuration Settings.
10. Click Next to continue to the VDB Configuration tab.
11. Modify the VDB Name if necessary.
12. Select a Target Group for the VDB.
13. If necessary, click the green Plus icon to add a new group.
14. Select a Snapshot Policy for the VDB.
15. If necessary, click the green Plus icon to create a new policy.
16. Click on LogSync option to enable LogSync process for point-in-time provisioning/refresh.
17. Click Next to continue to the Hooks tab.
18. Specify any Hooks to be used during the provisioning process.
For more information, see Customizing MySQL Management with Hook Operations.
19.

Click Next to continue to the Summary tab.

20. Verify all the information displayed for the VDB is correct.
21. Click Finish.
When provisioning starts, you can view progress of the job in the Databases panel or in the Job History panel of the Dashboard. When
provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the VDB in the Da
tabases panel and click the Open icon, you can view its card, which contains information about the database and its Data Management settings.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any snapshot by selecting that snapshot card from the Timeflow view, or by
entering a value in the time entry fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.
When provisioning by LogSync information, you can provision to any point in time within a particular snapshot. The TimeFlow view for a dSource
shows multiple snapshots by default. To view the LogSync data for an individual snapshot, use the Slide to Open LogSync control at the top of
an individual snapshot card to view the time range within that snapshot. Drag the red triangle to the point in time from which you want to provision.
You can also enter a date and time directly.

529

Delphix User Guide 2016 Delphix

Related Links
Linking a MySQL dSource
Requirements for MySQL Target/Staging Hosts and Databases
Using Pre- and Post-Scripts with dSources and VDBs
Customizing MySQL VDB Configuration Settings

530

Delphix User Guide 2016 Delphix

Customizing MySQL VDB Configuration Settings

This topic describes how to customize virtual database (VDB) configuration settings, including settings that are reserved by the Delphix Engine
during the provisioning process.

VDB Configuration
When you create a VDB, the Delphix Engine copies configuration settings from the dSource and uses them to create the VDB. Most settings are
copied directly, but you can add or update some of these settings by clicking the Advanced option in the Target Environment screen of the VDB
Provisioning Wizard. When you provision a VDB, it is important to know, however, that some configuration parameters are not customizable,
and some are stripped out during the provisioning process but are customizable. The list of restricted parameters can be found below.

Restricted Parameters
These parameters are restricted for use by the Delphix Engine. Attempting to customize these parameters will cause an unexpected behavior for
the VDB.
basedir
log_bin
datadir
log_error
gtid_mode
pid_file
port
relay_log
server_id
tmpdir
innodb_checksum_algorithm
innodb_checksums
innodb_data_file_path
innodb_log_file_size
innodb_log_files_in_group
innodb_page_size
innodb_undo_tablespaces
default_storage_engine
innodb_fast_shutdown
innodb_flush_log_at_trx_commit
innodb_flush_method
sync_binlog
sync_master_info
sync_relay_log
sync_relay_log_info

Related Links
Provisioning VDBs from MySQL dSources

531

Delphix User Guide 2016 Delphix

Provisioning a MySQL VDB from a Replicated dSource or VDB

This topic describes how to provision from a replicated dSource or virtual database (VDB). The process for provisioning from replicated objects is
the same as the typical VDB provisioning process, except that first you need to select the replica containing the replicated object.
Prerequisites
Procedure
Post-Requisites

Prerequisites
You must have replicated a dSource or a VDB to the target host, as described in Replication Overview.
You must have added a compatible target environment on the target host.

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB you want to provision.
6. The provisioning process is now identical to the process for provisioning standard objects.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

Related Links
Replication Overview
Provisioning VDBs from MySQL dSources

532

Delphix User Guide 2016 Delphix

Enabling and Disabling MySQL VDBs

This topic describes how to enable and disable a virtual database (VDB).
Disabling a VDB is a pre-requisite for procedures such as VDB migration or upgrade. Disabling a VDB removes all traces of it, including any
configuration files, from the target environment to which it was provisioned. When the VDB is later enabled again, these configuration files are
restored on the target environment.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the VDB you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the VDB again, move the slider control form Disabled to Enabled, and the VDB will continue to function as it did
previously.

Related Links
Provisioning VDBs from MySQL dSources

533

Delphix User Guide 2016 Delphix

Deleting a MySQL VDB

This topic describes how to delete a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Click My Databases.
4. Select the VDB you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

Related Link
Provisioning VDBs from MySQL dSources

534

Delphix User Guide 2016 Delphix

Migrating a MySQL VDB

This topic describes how to migrate a virtual database (VDB) from one target environment to another.
There may be situations in which you want to migrate a virtual database to a new target environment for example, when upgrading the host on
which the VDB resides, or as part of a general data center migration. This is easily accomplished by first disabling the database, then using the
Migrate VDB feature to select a new target environment.
Prerequisites
Procedure
Video

Prerequisites
You must have already set up a new target environment that is compatible with the VDB that you want to migrate.

Procedure
1. Login to your Delphix Engine using Delphix Admin credentials.
2. Click Manage.
3. Click My Databases.
4. Select the VDB you want to migrate.
5. Click the Open icon.
6. Slide the Enable/Disable control to Disabled.
7. Click Yes to confirm.
When the VDB is disabled, its icon will turn gray.
8. In the lower right-hand corner of the VDB card, click the VDB Migrate icon.
9. Select the new target environment for the VDB, the user for that environment, and the database installation where the VDB will
reside.
10. Click the Check icon to confirm your selections.
11. Slide the Enable/Disable control to Enabled.
12. Click Yes to confirm.
Within a few minutes, your VDB will re-start in the new environment, and you can continue to work with it as you would with any other
VDBs.

Video

Related Links
Provisioning VDBs from MySQL dSources

535

Delphix User Guide 2016 Delphix

Refreshing a MySQL VDB

Prerequisites
Procedure
Related Links
This topic describes how to manually refresh a virtual database (VDB).
Refreshing a VDB will re-provision it from the dSource. As with the normal provisioning process, you can choose to refresh the VDB from a
snapshot or a specific point in time. However, you should be aware that refreshing a VDB will delete any changes that have been made to it over
time. When you refresh a VDB, you are essentially re-setting it to the state you select during the refresh process. You can refresh a VDB
manually, as described in this topic, or you can set a VDB refresh policy, as described in the topics Managing Policies: An Overview, Creating
Custom Policies, and Creating Policy Templates.

Although the VDB no longer contains the previous contents, the previous Snapshots and TimeFlow still remain in Delphix and
are accessible through the Command Line Interface (CLI).

Prerequisites
To refresh a VDB, you must have the following permissions:
Auditor permissions on the dSource associated with the VDB
Auditor permissions on the group that contains the VDB
Owner permissions on the VDB itself
A user with Delphix Admin credentials can perform a VDB Refresh on any VDB in the system.

Procedure
1. Login to the Delphix Admin application.
2. Under Databases, select the VDB you want to refresh.
3. Click the Open icon in the upper right-hand corner of the VDB card.
4. On the back of the VDB card, click the Refresh VDB icon in the lower right-hand corner.
This will open the screen to re-provision the VDB.
5. Select desired refresh point snapshot or slide the display LogSync timeline to pick a point-in-time from which to refresh.
6. Click Refresh VDB.
7. Click Yes to confirm.

Related Links
Managing Policies: An Overview
Creating Custom Policies
Creating Policy Templates

536

Delphix User Guide 2016 Delphix

MySQL VDB Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

537

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

538

Delphix User Guide 2016 Delphix

Customizing MySQL Management with Hook Operations

Hook operations allow you to execute an ordered list of custom operations at select hook points in linking, provisioning and virtual dataset
management. For details on the types of operations that are available, see children of this page.
dSource Hooks
Virtual Dataset Hooks
Setting Hook Operations
Setting Hook Operations through the Delphix Admin Application
Setting Hook Operations through the CLI
Example of Editing Hook Operations through the CLI
Hook Operation Templates
Creating a Hook Operation Template
Importing a Hook Operation Template
Exporting a Hook Operation Template

dSource Hooks
Hook

Description

Pre-Sync

Operations performed before a sync.

These operations can quiesce data to be captured during the sync, or stop processes that may interfere with the sync.

Post-Sync

Operations performed after a sync. This hook will run regardless of the success of the sync or Pre-Sync hook operations.
These operations can undo any changes made by the Pre-Sync hook.

Virtual Dataset Hooks

Hook

Description

Configure
Clone

Operations performed after initial provision or after a refresh. This hook will run after the virtual dataset has been started.
During a refresh, this hook will run before the Post-Refresh hook.

Pre-Refresh

Operations performed before a refresh.

These operations can cache data from the virtual dataset to be restored after the refresh completes.

Post-Refresh

Operations performed after a refresh. During a refresh, this hook will run after the Configure Clone hook. This hook will not run
if the refresh or Pre-Refresh hook operations fail.
These operations can restore cached data after the refresh completes.

Pre-Rewind

Operations performed before a rewind.

These operations can cache data from the virtual dataset to be restored after the rewind completes.

Post-Rewind

Operations performed after a rewind. This hook will not run if the rewind or Pre-Rewind hook operations fail.
These operations can restore cached data after the rewind completes.

Pre-Snapshot

Operations performed before a snapshot.

These operations can quiesce data to be captured during the snapshot, or stop processes that may interfere with the
snapshot.

Post-Snapshot

Operations performed after a snapshot. This hook will run regardless of the success of the snapshot or Pre-Snapshot hook
operations.
These operations can undo any changes made by the Pre-Snapshot hook.

Operation Failure
If a hook operation fails, it will fail the entire hook: no further operations within the failed hook will be run.

Setting Hook Operations

539

Delphix User Guide 2016 Delphix

You can construct hook operation lists through the Delphix Admin application or the command line interface (CLI). You can either define the
operation lists as part of the linking or provisioning process or edit them on dSources or virtual datasets that already exist.

Setting Hook Operations through the Delphix Admin Application

To specify hook operations during linking or provisioning, navigate to the Hooks tab of the Linking Wizard or Provision Wizard.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation or click Import to load a hook operation template.
4. Click the text area and edit the contents of the operation.
5. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
6. To remove an operation from the list, click the Trash icon on the operation.
7. When you have set all hook operations, click Next to continue with the provisioning process.
To edit hook operations on an already-existing dSource or virtual dataset, navigate to the Hooks tab on the back of the dSource card or virtual
dataset card.
1. Select the hook to edit.
2. The current operations at this hook will be displayed. To edit this list of operations, click the Pencil icon in the top right-hand corner of the
card.
3. Click the Plus icon to add a new operation.
4. Select the type of operation or click Import to load a hook operation template.
5. Click the text area and edit the contents of the operation.
6. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
7. To remove an operation from the list, click the Trash icon on the operation.
8. When you have set all hook operations, click Check to save the changes.

Setting Hook Operations through the CLI

To specify hook operations during linking, edit the relevant hook's array of operations defined on the LinkingParameters > Source >
Operations object.
To specify hook operations during provisioning, edit the relevant hook's array of operations defined on the ProvisionParameters > Source
> Operations object.
To edit hook operations on an already-created dSource, edit the relevant hook's array of operations defined on the Source > Operations obje
ct.
To edit hook operations on an already-created virtual dataset, edit the relevant hook's array of operations defined on the Source > Operation
s object.
For more information about these CLI objects, see the LinkedSourceOperations, VirtualSourceOperations, RunCommandOnSourceOp
eration, and RunExpectOnSourceOperation API documentation in the Help menu of the Delphix Admin application.

Example of Editing Hook Operations through the CLI

1. Navigate to the relevant source's VirtualSourceOperations object.
2. Select a hook to edit.
delphix> source
delphix source> select "pomme"
delphix source "pomme"> update
delphix source "pomme" update *> edit operations
delphix source "pomme" update operations *> edit postRefresh
3. Add an operation at index 0.
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
Properties
type: RunCommandOnSourceOperation (*)
command: echo Refresh completed. (*)
delphix source "pomme" update operations postRefresh

540

*> add
0 *> set type=RunCommandOnSourceOperation
0 *> set command="echo Refresh completed."
0 *> ls

0 *> commit

Delphix User Guide 2016 Delphix

4. Add another operation at index 1 and then delete it.

delphix
delphix
delphix
delphix
delphix
delphix

source
source
source
source
source
source

"pomme"
"pomme"
"pomme"
"pomme"
"pomme"
"pomme"

update
update
update
update
update
update

operations
operations
operations
operations
operations
operations

postRefresh
postRefresh
postRefresh
postRefresh
postRefresh
postRefresh

*> add
1 *> set type=RunCommandOnSourceOperation
1 *> set command="echo Refresh completed."
1 *> back
*> unset 1
*> commit

Hook Operation Templates

You can use templates to store commonly used operations, which allows you to avoid repeated work when an operation is applicable to more
than a single dSource or virtual dataset. You manage templates through the Delphix Admin application.
Hook Operations Templates Not Available via CLI
Hook operation templates cannot be fully utilized from the CLI. Manage and use hook operations through the Delphix Admin applicatio
n.

Creating a Hook Operation Template

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Operation Templates.
4. Click the Plus icon to add a new operation template.
5. Enter a Name for the template.
6. Select an operation Type.
7. Enter a Description detailing what the operation does or how to use it.
8. Enter operation Contents to implement the operation partially or fully.
9. Click Create.

Importing a Hook Operation Template

To import a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Click Import.
4. Select the template to import.
5. Click Import.
6. When you have set all hook operations, click Check to save the changes.

Exporting a Hook Operation Template

To export a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation.
4. Click the text area and edit the contents of the operation.
5. Click Export.
6. Enter a Name for the template.
7. Enter a Description detailing what the operation does or how to use it.
8. Click Create.

541

Delphix User Guide 2016 Delphix

MySQL Hook Operation Notes

Shell Operations
RunCommand Operation
RunBash Operation
Shell Operation Tips
Other Operations
RunExpect Operation
MySQL Environment Variables
dSource Environment Variables
VDB Environment Variables

Shell Operations
RunCommand Operation

The RunCommand operation runs a shell command on a Unix environment using whatever binary is available at /bin/sh. The environment user
runs this shell command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the shell command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Examples of RunCommand Operations

You can input the full command contents into the RunCommand operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
if test -d "$remove_dir"; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
If a script already exists on the remote environment and is executable by the environment user, the RunCommand operation can execute this
script directly.

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh "$ARG_ENVIRONMENT_VARIABLE" "second

argument in double quotes" 'third argument in single quotes'
RunBash Operation

The RunBash operation runs a Bash command on a Unix environment using a bash binary provided by the Delphix Engine.The environment user
runs this Bash command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the Bash command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of RunBash Operations

You can input the full command contents into the RunBash operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
# Bashisms are safe here!
if [[ -d "$remove_dir" ]]; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
Shell Operation Tips
Using nohup

542

Delphix User Guide 2016 Delphix

You can use the nohup command and process backgrounding from resource in order to "detach" a process from the Delphix Engine. However, if
you use nohup and process backgrounding, you MUST redirect stdout and stderr.
Unless you explicitly tell the shell to redirect stdout and stderr in your command or script, the Delphix Engine will keep its connection to the
remote environment open while the process is writing to either stdout or stderr . Redirection ensures that the Delphix Engine will see no more
output and thus not block waiting for the process to finish.
For example, imagine having your RunCommand operation background a long-running Python process. Below are the bad and good ways to do
this.
Bad Examples
nohup
nohup
nohup
nohup

python
python
python
python

file.py
file.py
file.py
file.py

& # no redirection
2>&1 & # stdout is not redirected
1>/dev/null & # stderr is not redirected
2>/dev/null & # stdout is not redirected

Good Examples
nohup python file.py 1>/dev/null 2>&1 & # both stdout and stderr redirected, Delphix Engine will not
block

Other Operations
RunExpect Operation

The RunExpect operation executes an Expect script on a Unix environment. The Expect utility provides a scripting language that makes it easy to
automate interactions with programs which normally can only be used interactively, such as ssh. The Delphix Engine includes a
platform-independent implementation of a subset of the full Expect functionality.
The script is run on the remote environment as the environment user from their home directory. The Delphix Engine captures and logs all output
of the script. If the operation fails, the output is displayed in the Delphix Admin application and CLI to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunExpect Operation

Start an ssh session while interactively providing the user's password.

spawn ssh [email protected]

expect {
-re {Password: } {
send "${env(PASSWORD_ENVIRONMENT_VARIABLE)}\n"
}
timeout {
puts "Timed out waiting for password prompt."
exit 1
}
}
exit 0
MySQL Environment Variables
Operations that run user-provided scripts have access to environment variables. For operations associated with specific dSources or virtual
databases (VDBs), the Delphix Engine will always set environment variables so that the user-provided operations can use them to access the
dSource or VDB.
dSource Environment Variables

Environment Variable

Description

MYSQL_ENVUSER

The environment user used by Delphix Engine to connect to the environment

MYSQL_DATADIR

The data directory

MYSQL_INSTALL

The MySQL installation path

543

Delphix User Guide 2016 Delphix

MYSQL_PORT

The port number

MYSQL_DBUSER

The database user

VDB Environment Variables

Environment Variable

Description

MYSQL_ENVUSER

The environment user used by Delphix Engine to connect to the environment

MYSQL_DATADIR

The data directory

MYSQL_INSTALL

The MySQL installation path

MYSQL_PORT

The port number

MYSQL_DBUSER

The database user

MYSQL_SOCKET_FILE

The location of the socket file for the VDB

MYSQL_CNF_FILE

The location of the my.cnf file for the VDB

544

Delphix User Guide 2016 Delphix

SAP ASE Environments and Data Sources

545

Delphix User Guide 2016 Delphix

SAP ASE Support and Requirements

These topics describe specific requirements for SAP ASE environments, such as user privileges and the supported operating systems and
database versions.
Requirements for SAP ASE Source Hosts and Databases
Requirements for SAP ASE Target Hosts and Databases
Network and Connectivity Requirements for SAP ASE Environments
Supported Operating Systems and Database Versions for SAP ASE

546

Delphix User Guide 2016 Delphix

Requirements for SAP ASE Source Hosts and Databases

This topic describes the configuration and settings requirements for Sybase ASE source environments and databases.
Source environments are servers which contain the source databases from which virtual database copies are made.

Source Host Requirements

There must be an operating system user, such as delphix_os, that meets the following requirements:
The $PATH environment variable includes the location for the isql binary
The $SYBASE environment variable is set for non-interactive shells (such as via the .bashrc configuration file)
Can login to the source host via SSH
Has read access for the Sybase ASE Backup Server log files
A change was made in ASE 15.7.0 SP100 which made permissions on the backup server log file more restrictive: "rw-r-----"
(the permissions had previously been "rw-r--r--"). If the delphix_os user is not the backup server owner or in the same group,
the following workaround can be used: How to make the permission settings on ASE's errorlog less restrictive.

There must be a directory on the source host where you can install the Delphix Engine toolkit, for

example: /var/opt/delphix

/Toolkit
The delphix_os user must own the directory
The directory must have permissions 0770, for example, -rwxrwx---. However, you can also use more permissive settings.
The directory should have 256MB of available storage.
The Delphix Engine must be able to make an ssh connection (for example, TCP port 22) to the source host

Sample Script
Sample Script to create delphix_os on Linux

USER=delphix_os
GROUP=sybase
if [ ! `grep $USER /etc/passwd` ]
then
echo "Creating User $USER with no Password"
adduser --gid $GROUP --home-dir /home/$USER $USER
mkdir /home/$USER/.ssh
chmod 755 /home/$USER
echo "PATH=$PATH:/opt/sybase/ASE15_0/bin; export PATH" >> /home/$USER/.bashrc
echo "SYBASE=/opt/sybase; export SYBASE" >> /home/$USER/.bashrc
chown $USER:$GROUP /home/$USER/.ssh
else
echo "User $USER Already Exists"
fi
if [ ! -d /home/$USER/toolkit ]
then
echo "Creating Toolkit Directory"
mkdir /home/$USER/toolkit
chown $USER:$GROUP /home/$USER/toolkit
chmod 0770 /home/$USER/toolkit
else
echo "Toolkit Directory already Exists"
fi

547

Delphix User Guide 2016 Delphix

Source Database Requirements

There must be a database user, such as delphix_disc, that has SELECT privileges on sysdatabases, sysservers and syslisteners tab
les
The discovery database user must have these privileges for each instance on the source host
There must be a database user, such as delphix_link, that has SELECT privileges on the above tables.
If you will select New Full Backup when linking, this user must also have privileges to take a new full database dump of the
source database. For more information about linking options, see Linking an SAP ASE Data Source.
The link database user can be different for each instance and database on the source host
You can also use the delphix_link user for discovery, in which case only one user login is needed.

Sample Script
Sample script run as sa

sp_addlogin delphix_link, "StrongPassword"

go
sp_adduser delphix_link
go
grant select on sysdatabases to delphix_link
go
grant select on sysservers to delphix_link
go
grant select on syslisteners to delphix_link
go
use DatabaseToBeLinked
go
sp_adduser delphix_link
go
Delphix creates a minimum of 8 data devices and 8 log devices. As a result, a minimum of 16 devices per dSource is created and the
same is true for each VDB when provisioned.

Related Links
For more information about using the HostChecker bundle, see Using HostChecker to Validate SAP ASE Source and Target
Environments
Linking an SAP ASE Data Source
Sudo File Configurations

548

Delphix User Guide 2016 Delphix

Requirements for SAP ASE Target Hosts and Databases

This topic describes the configuration and settings requirements for SAP ASE target hosts and databases.
Target Host Requirements
Related Links

Target Host Requirements

The operating system on the target environment must be the same as, or binary compatible with, the operating system on the source
environment
The SAP ASE version on the target environment must be the same as the version on the source environment
There must be an operating system user, such as delphix_os, that meets the following requirements:
The $PATH environment variable includes the location for the isql binary
The $SYBASE environment variable is set for non-interactive shells (such as via the .bashrc configuration file)
Can login to the source host via Secure Shell (SSH)
Has write permission for the mount-point directory
Has permission to run mount/umount and mkdir/rmdir as the super-user, usually granted through sudo permissions. See Sudo
Privilege Requirements for further explanation of this requirement, and Sudo File Configurations for example file
configurations.
NOTE: The toolkit directory described in the bullet point below will be used as the base for mount points that are created
when you provision a virtual database (VDB) to the target host. Adjust the sudo file configurations to match this directory
accordingly.
Disable tty for the delphix_os user for mount/umount
There must be a database user, such as delphix_db, with SA role on each instance on the target environment
There must be a directory on the target environment where you can install the Delphix Engine toolkit, for example /var/opt/delphix/
Toolkit.
The delphix_os user must own the directory
The directory must have permissions 0770, for example, -rwxrwx--. However, you can also use more permissive settings.
The directory should have 1GB of available storage
Avoid using the home directory of the delphix_os user
If the target host will be used as a staging target environment (see Managing SAP ASE Environments: An Overview), at least one of
the following two options must be configured:
You must configure the ASE Backup Servers with sysservers on the source database ASE instance, or
Full and transaction dump files from the source database must be available over NFS on the target host
Staging and target ASE instances should have disk mirroring disabled.
sp_configure "disable disk mirroring" run value should be 1, which is the default. If it is 0, change it using
sp_configure "disable disk mirroring", 1 this parameter is static, and a rebbot of the target ASE instance is required for this
to take effect.
To support multiple VDBs, you may need to increase the parameter number of devices.
Delphix creates a minimum of 8 data devices and 8 log devices. As a result, Delphix creates a minimum of 16 devices for each
VDB.

To support multiple VDBs, you may need to increase the parameter number of alarms.
Delphix uses ASE operations which use alarm structures such as MOUNT and UNMOUNT. The number of alarms limit the
number of these operations which can be run concurrently. Various ASE instance failures can occur if the available alarm
structures are exhausted. The amount of memory consumed by increasing the number of alarm structures is small. Delphix
recommends that the number of alarms value is increased to 4096.

Related Links
Using HostChecker to Confirm Source and Target Environment Configuration
sudoers Manual Page

549

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for SAP ASE Environments

General Outbound from the Delphix Engine Port Allocation
Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries

550

Delphix User Guide 2016 Delphix

ClientAliveInterval
ClientAliveCountMax

Connection Requirements for SAP ASE Environments

The Delphix Engine uses an SSH connection to each source environment and SAP ASE client connections to the SAP ASE instances
on the source environment.
The Delphix Engine uses an SSH connection to each target environment, NFS connections from each target environment to the Delphix
Engine, and SAP ASE JDBC connections to the virtual databases on the target environment.

Port Allocation for SAP ASE Environments

The following diagram describes the port allocations for SAP ASE environments. It illustrates the ports that we recommend to be open from
Delphix to remote services, to the Delphix Engine, and to the Target Environments.

Refer to Managing SAP ASE Environments for information on SAP ASE environments. The Delphix Engine makes use of the following network
ports for SAP ASE dSources and VDBs:

Outbound from the Delphix Engine Port Allocation

Protocol

Port Numbers

Use

TCP

Configuration dependent

JDBC Connections to the SAP ASE instances on the source environments

Inbound to the Delphix Engine Port Allocation

Protocol

Port Number

Use

UDP

33434-33464

Traceroute from source and target database servers to the Delphix Engine (optional)

TCP/UDP

111

Remote Procedure Call (RPC) port mapper used for NFS mounts

TCP

2049

NFS client from target hosts to the Delphix Engine

TCP

1110

Network Status Monitor (NSM) client from target hosts to Delphix Engine

TCP

4045

Network Lock Manager (NLM) client from target hosts to Delphix Engine

551

Delphix User Guide 2016 Delphix

Port Allocation Between Source and Staging Target Environments

Protocol

Port Numbers

Use

TCP

Configuration
dependent

SAP ASE Remote Backup Server protocol. Applies if linking using the New Full Backup option, or if linking
with the Remote Backup Server option.

Port Allocation Between Staging Target Environments and Shared Backup Fileserver
Protocol

Port Numbers

Use

TCP/UDP

NFS and related port numbers:

NFS mount point exported by an NFS shared backup fileserver. Applies if linking using the Loc
al Backup Server option.

Portmap (111)
NFS (typically 2049)
Network Lock
Manager (NLM)
Network Status
Monitor (NSM)

552

Delphix User Guide 2016 Delphix

Supported Operating Systems and Database Versions for SAP ASE

This topic describes supported operating systems and database versions for SAP ASE.

Source and Target OS and DBMS Compatibility

The source and target must be running the same DBMS/Operating System combination, (although users can run different different
patch/sp levels) in order to successfully provision a VDB to the target. For example, if the source is running SAP ASE 16, the target can
be running ASE 16SP1. The Operating System platform must be the same between the source and target, even when the operating
system version may differ. For example, if the source is running Red Hat Enterprise Linux 6.2 x86_64 then the target could be running
Red Hat Enterprise Linux 6.4 x86_64, but not Solaris 10 SPARC.

DBMS Versions

Operating System Versions / Processor Family

SAP Adaptive Server Enterprise (ASE) 12.5

Red Hat Enterprise Linux 5.x / x86_64

Veritas Cluster Server

Solaris 10 / x86_64, SPARC

SAP Adaptive Server Enterprise (ASE) 15.03

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64

SuSE Linux Enterprise Server 11.x
Solaris 10 / x86_64, SPARC
AIX 5.3 / POWER

SAP Adaptive Server Enterprise (ASE) 15.5

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64

Solaris 10 / x86_64, SPARC
AIX 5.3 / POWER

SAP Adaptive Server Enterprise (ASE) 15.7

Red Hat Enterprise Linux 5.x / x86_64

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64
Solaris 10 / x86_64, SPARC
AIX 6.1, 7.1 / POWER

SAP Adaptive Server Enterprise (ASE) 16

Red Hat Enterprise Linux 6.2, 6.3, 6.4 / x86_64

Solaris 10 / x86_64, SPARC

553

VCS 5.1 on RHEL 5 & 6

Delphix User Guide 2016 Delphix

Managing SAP ASE Environments

These topics describe special tasks and concepts for working with SAP ASE environments.
Managing SAP ASE Environments: An Overview
Using HostChecker to Validate SAP ASE Source and Target Environments
Adding an SAP ASE Environment
Editing SAP ASE Environment Attributes
Changing the Host Name or IP Address of an SAP ASE Environment
Deleting an SAP ASE Environment
Managing SAP ASE Environment Users
Refreshing an SAP ASE Environment
Enabling Linking and Provisioning for SAP ASE Environments

554

Delphix User Guide 2016 Delphix

Managing SAP ASE Environments: An Overview

This topic describes the high-level process for adding SAP ASE environments, linking SAP ASE databases to the Delphix Engine, and
provisioning virtual databases.

Block Diagram of Linking Architecture between SAP ASE Environments and the Delphix Engine

Environment Setup
SAP ASE dSources are backed by a staging database that runs on a target host, as shown in the diagram. There is no requirement for additional
local storage on this host, as the storage is mounted over NFS from the Delphix Engine. At Delphix, we refer to the creation and maintenance of
this staging database on the staging host as "validated sync," because it prepares the dSource data on the Delphix Engine for provisioning VDBs
later on. After the Delphix Engine creates the staging database, it continuously monitors the source database for new transaction log dumps.
When it detects a new transaction log dump, it loads that dump to the staging database. The result is a TimeFlow with consistent points from
which you can provision a virtual database (VDB), and a faster provisioning process, because there is no need for any database recovery during
provisioning.
When you later provision a VDB, you can specify any environment as a target, including the environment that contains the staging database.
However, for best performance, Delphix recommends that you choose a different target environment. The target must have an operating system
that is compatible with the one running on the validated host, as described in Requirements for SAP ASE Target Hosts and Databases.

Workflow and Tasks for SAP ASE Environments

1. Add the desired source environments as described in Managing SAP ASE Environments.
2. Add the desired target environments as described in Managing SAP ASE Environments.
3. Link the source database as described in Linking an SAP ASE Data Source.

555

Delphix User Guide 2016 Delphix

3.
4. Provision VDBs as described in Provisioning an SAP ASE VDB.

Related Links
SAP ASE Support and Requirements

556

Delphix User Guide 2016 Delphix

Using HostChecker to Validate SAP ASE Source and Target Environments

This topic describes how to use HostChecker to configure SAP ASE environments.
What is HostChecker?
Prerequisites
Procedure
Tests Run
Related Links

What is HostChecker?
The HostChecker is a standalone program which validates that host machines are configured correctly before the Delphix Engine uses them as
data sources and provision targets.
Please note that HostChecker does not communicate changes made to hosts back to the Delphix Engine. If you reconfigure a host, you must
refresh the host in the Delphix Engine in order for it to detect your changes.
You can run the tests contained in the HostChecker individually, or all at once. You must run these tests on both the source and target hosts to
verify their configurations. As the tests run, you will either see validation messages that the test has completed successfully, or error messages
directing you to make changes to the host configuration.

Prerequisites
Make sure that your source and target environments meet the requirements specified in SAP ASE Support and Requirements.

Procedure
1. Download the HostChecker tarball from https://download.delphix.com/ (for example:
delphix_4.0.2.0_2014-04-29-08-38.hostchecker.tar).
2. Create a working directory and extract the HostChecker files from the HostChecker tarball.

mkdir dlpx-host-checker
cd dlpx-host-checker/
tar -xf delphix_4.0.2.0_2014-04-29-08-38.hostchecker.tar
3. Change to the working directory and enter this command. Note that for the target environments, you would change source to target.

$ ./chkHost.pl source ase

Don't Run as Root
Don't run the HostChecker as root; this will cause misleading or incorrect results from many of the checks.

4. Select which checks you want to run. We recommend you run all checks if you are running Hostchecker for the first time.
5. Pass in the arguments the checks ask for.
6. Read the output of the check.
7. The error or warning messages will explain any possible problems and how to address them. Resolve the issues that the HostChecker
describes. Don't be surprised or undo your work if more errors appear the next time you run HostChecker, because the error you just
fixed may have been masking other problems.
8. Repeat steps 37 until all the checks return no errors or warnings.

Tests Run
Test

ASE
Source

ASE
Target

Description

557

Delphix User Guide 2016 Delphix

Check Host
SSH
Connectivity

Verifies that the environment is accessible via SSH

Check Tool
Kit Path

Verifies that the toolkit installation location has the proper ownership, proper permissions, and enough free
space.

Verifies that the operating system user can execute certain commands with necessary privileges via sudo.
This only needs to be run on target environments. See the topic Requirements for SAP ASE Target Hosts
and Databases for more information.

Check OS
User
Privileges
Check OS
ASE
Environment

Checks that the proper ASE environment variables are defined and the isql executable can be found.

Check ASE
installations

Attempts to discover all ASE instances, backup servers, make sure backup server log files can be read and
that the user has proper database permissions. See the topic SAP ASE Support and Requirements for
more information.

Related Links
SAP ASE Support and Requirements

558

Delphix User Guide 2016 Delphix

Adding an SAP ASE Environment

Prerequisites
See Requirements for SAP ASE Source Hosts and Databases.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the Plus icon next to Environments.
5. In the Add Environment dialog, select Unix/Linux.
6. Select Standalone Host.
7. Enter the Host IP address.
8.

Enter an optional Name for the environment.

9. Enter the SSH port.

The default value is 22.
10. Enter a Username for the environment.
11.

Select a Login Type.

12. For Password, enter the password associated with the user in Step 10.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

13. For Password Login, click Verify Credentials to test the username and password.
14. Enter a Toolkit Path.
The toolkit directory stores scripts used for Delphix Engine operations. It must have a persistent working directory rather than a temporary
one. The toolkit directory will have a separate sub-directory for each database instance. The toolkit path must have 0770 permissions.
15. Click the Discover SAP ASE checkbox.
16. Enter a Username for an instance on the environment.
17. Enter the Password associated with the user in Step 15.
18. Click OK.

Post-Requisites
After you create the environment, you can view information about it by selecting Manage > Environments and then selecting the environment
name.

559

Delphix User Guide 2016 Delphix

Editing SAP ASE Environment Attributes

Procedure
Common Editable Attributes
SAP ASE Attributes
This topic describes how to edit attributes of an environment such as name, host address, ssh port, or toolkit path, as well as descriptions of more
advanced attributes for specific data platforms.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials or as the owner of an environment.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of an environment to view its attributes.
5. Under Attributes, click the Pencil icon to edit an attribute.
6. Click the Check icon to save your edits.

Common Editable Attributes

Attribute

Description

Environment
Users

The users for that environment. These are the users who have permission to ssh into an environment, or access the
environment through the Delphix Connector. See the Requirements topics for specific data platforms for more information on
the environment user requirements.

Host
Address

The IP address for the environment host.

Notes

Any other information you want to add about the environment.

SAP ASE Attributes

Attribute

Description

DB User

User for Delphix to use for ASE database operations

DB Password

Credentials to use for the DB User

560

Delphix User Guide 2016 Delphix

Changing the Host Name or IP Address of an SAP ASE Environment

This topic describes how to change the host name or IP address for source and target environments, and for the Delphix Engine.
Procedure
For Source Environments
For VDB Target Environments
For the Delphix Engine

Procedure
For Source Environments
1. Disable the dSource as described in Enabling and Disabling dSources.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the dSource.

For VDB Target Environments

1. Disable the VDB as described in Enabling and Disabling Virtual Databases.
2. If the Host Address field contains an IP address, edit the IP address.
3. If the Host Address field contains a host name, update your Domain Name Server to associate the new IP address to the host name.
The Delphix Engine will automatically detect the change within a few minutes.
4. In the Environments screen of the Delphix Engine, refresh the host.
5. Enable the VDB.

For the Delphix Engine

1. Stop all running VDBs by clicking the red Stop button on the VDB card.
2. Disable all dSources as described in Enabling and Disabling dSources.
3. You can use either the command line interface or the Server Setup application to change the IP address of the Delphix Engine.
a. To use the command line interface, press F2 and follow the instructions described in Setting Up Network Access to the
Delphix Engine.
b. To use the Server Setup application, go to to the upper right hand corner to the user name and click for the drop down and
Select 'Engine Setup' in the Delphix Admin interface, or click Server Setup in the Delphix Engine login screen. Note: You must
have sysadmin credentials to be able to do this part
i. In the Network panel, click Modify.
ii. Under DNS Services, enter the new IP address.
iii. Click OK.
4. Refresh all Environments by clicking the Blue/Green Refresh Symbol on the Environments screen.
5. Enable all dSources as described in Enabling and Disabling dSources.
6. Start all VDBs by clicking the Start button on the VDB card.

561

Delphix User Guide 2016 Delphix

Deleting an SAP ASE Environment

This topic describes how to delete an environment.

Prerequisites
You cannot delete an environment that has any dependencies, such as dSources or virtual databases (VDBs). These must be deleted before you
can delete the environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, select the environment you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

562

Delphix User Guide 2016 Delphix

Managing SAP ASE Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure

Prerequisites
Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

563

Delphix User Guide 2016 Delphix

Refreshing an SAP ASE Environment

This topic describes how to refresh an environment.
After you make changes to an environment that you have already set up in the Delphix Admin application, such as installing a new database
home, creating a new database, or adding a new listener, you may need to refresh the environment to reflect these changes.
During environment discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the
toolkit are:
A JRE
Delphix jar files
The hostchecker utility
Scripts for managing the environment and/or VDBs
Delphix Connector log files
Delphix then executes some of these scripts to discover information about the objects in your environment (where the databases are installed,
the database names, information required to connect to these databases, etc.). In some environments (Windows in particular), the scripts are
customized to fit the customers environment.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of the environment to you want to refresh.
5. Click the Refresh icon.
To refresh all environments, click the Refresh icon next to Environments.

564

Delphix User Guide 2016 Delphix

Enabling Linking and Provisioning for SAP ASE Environments

This topic describes how to enable and disable provisioning and linking for SAP ASE databases.
Before a database can be used as a dSource, you must first make sure that you have enabled linking to it. Similarly, before you can provision a
VDB to a target database, you must make sure that you have enabled provisioning to it.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click Databases.
5. Slide the button next to Allow Provisioning to On or Off to enable or disable provisioning for that instance.
6. Click show details for the database.
7. Slide the button next to Allow Linking to On or Off to enable or disable linking.

565

Delphix User Guide 2016 Delphix

Managing SAP ASE Data Sources

These topics describe special tasks and concepts for working with SAP ASE data sources.
Linking SAP ASE Data Sources: An Overview
Linking an SAP ASE Data Source
Advanced Data Management Settings for SAP ASE dSources
Using Pre- and Post-Scripts with SAP ASE Data Sources
Deleting an SAP ASE dSource
Detaching and Re-Attaching SAP ASE dSources
Enabling and Disabling SAP ASE dSources
SAP ASE dSource Icon Reference

566

Delphix User Guide 2016 Delphix

Linking SAP ASE Data Sources: An Overview

This topic describes basic concepts behind the creation of dSources from SAP ASE databases.

Initial Linking and Staging Databases

A dSource is the copy of a physical database that is created when the Delphix Engine links to and loads the database from a backup. The
database backup can be a new full database backup that the Delphix Engine initiates, the most recent existing database backup, or an existing
database backup specified by the user. When loading from an existing backup, the backup should be in a location that the source environment
user can access.
After obtaining the initial snapshot and linking the dSource, the Delphix Engine keeps the dSource and the source database in sync by monitoring
the source database for new transaction log dumps, and then applying those backups on a standby database. This database is called the "staging
database." A target environment that hosts one or more staging databases is referred to as a "staging target."
After you have linked a database into the Delphix Engine, you can re-initialize it by performing a sync on the dSource.

Related Links
Link an SAP ASE Data Source
Add an SAP ASE Environment

567

Delphix User Guide 2016 Delphix

Linking an SAP ASE Data Source

This topic describes the process of linking to a source database and creating a dSource.
Prerequisites
Procedure
Related Links

Prerequisites
1. Ensure a correct set up the source and target environment, as described in Managing SAP ASE Environments
2. Before you can link a data source in a Veritas Cluster Server (VCS) environment, the following static configuration parameter for Delphix
engine needs to be manually added by a support contact to avoid failure. This is because each node in a VCS environment typically
has more than one IP address for fail over purposes. By default, the Delphix engine will only interface with a single IP address from the
source host, unless the following configuration is added:
PRO.RESTRICT_TARGET_IP=false
3. The Delphix engine configuration must be modified and can be found with the following path name:
/var/delphix/server/etc/delphix_config_override.properties
4. Finally, the Delphix engine stack needs to be manually restarted in order for the new configuration to take effect.

Dump file requirements

Database and transaction log dumps which will be used by Delphix must be taken using native ASE format.
Dump devices are not supported, database and transaction dumps which will be used by Delphix must be taken to filesystem
files.
If ASE dump compression is being used the dumps must be generated using the compression = compress_level syntax. The
older compress::compress_level syntax is not supported.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click Add dSource.
Alternatively, on the Environment Management screen, you can click Link next to a database name to start the dSource creation
process.
5. In the Add dSource wizard, select the source database.
Changing the Environment User
If you need to change or add an environment user for the source database, see Managing SAP ASE Environment Users.

6. Enter your login credentials for the source database.

7. Click Verify Credentials.
8. Click Next.
9. Select a Database Group for the dSource.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies.
10. Click Next.
11. Select an Initial Load option and enter any additional settings needed. There are three different options for the initial load of the
dSource:
New Full Backup Let Delphix create a new full backup file and load it. Note that when Delphix creates the backup, it is
dumped to Delphix storage, not the Backup Location specified in the next step.
Most Recent Existing Full Backup Find the most recent existing full backup file in the Backup Location and load it.
Specific Existing Full Backup Specify which backup files in the Backup Location you want to load.

568

Delphix User Guide 2016 Delphix

12. Enter the Backup Location. This is the directory where the database backups are stored. Delphix recursively searches this location, so
the database backups or transaction logs can reside in any subdirectories below the path entered.
13. Optionally, enter the Load Backup Server Name. If you have multiple backup servers in your staging environment, you can specify the
name of the backup server here to load database dumps and transaction logs into the staging database. If you leave this parameter
empty, the server designated as "SYB_BACKUP" will be used.
14. Select environment and ASE instance name.

15. Enable or disable LogSync.

16. Select Backup Location Type.
17. Click Advanced to edit Retention policies and External Data Directory.
18. Click Next.
19. Specify any Pre and Post Scripts.
20. Review the dSource Configuration and Data Management information.
21. Click Finish.
The Delphix Engine will initiate two jobs, DB_Link and DB_Sync, to create the dSource. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

The dSource Card

After you have created a dSource, you can view information about it on the dSource card. You can also make modifications to its
policies and permissions. To view the front of the dSource card, click the Open icon in the Databases panel. The card will then flip,
showing you information such as the Source Database and Data Management configuration.

Related Links
Managing SAP ASE Environments
Requirements for SAP ASE Target Hosts and Databases
Managing SAP ASE Environment Users
Users, Permissions, and Policies

569

Delphix User Guide 2016 Delphix

Advanced Data Management Settings for SAP ASE dSources

Accessing Data Management Settings
During the dSource linking process
On the back of the dSource card
In the top menu bar
Retention Policies
Benefits of Longer Retention
SAP ASE Settings
This topic describes advanced data management settings for dSources.
When linking a dSource, you can use custom data management settings to improve overall performance and match the needs of your specific
server and data environment. If no specific settings are required, leverage default data management settings.

Accessing Data Management Settings

There are three ways to set or modify data management settings for dSources:
During the dSource linking process

1. In the Data Management panel of the Add dSource wizard, click Advanced.
On the back of the dSource card

1. Under Data Management, click the field next to Retention Policy

2. Click the Edit icon.
3. For SnapSync and Retention policies, click the policy name. This will open the Policy Management screen.
In the top menu bar

1. Click Manage.
2. Select Policies. This will open the Policy Management screen.
3. Select the policy for the dSource you want to modify.
4. Click Modify.
For more information, see Creating Custom Policies and Creating Policy Templates.

Retention Policies
Retention policies define the length of time that the Delphix Engine retains snapshots and log files to which you can rewind or provision objects
from past points in time. The retention time for snapshots must be equal to, or longer than, the retention time for logs.
To support longer retention times, you may need to allocate more storage to the Delphix Engine. The retention policy in combination with the
SnapSync policy can have a significant impact on the performance and storage consumption of the Delphix Engine.

Benefits of Longer Retention

With increased retention time for snapshots and logs, you allow a longer (older) rollback period for your data.
Common use cases for longer retention include:
SOX compliance
Frequent application changes and development
Caution and controlled progression of data
Reduction of project risk
Speed of rollback / restore to older points in time
With LogSync enabled, you can customize both the retention policy and the SnapSync policy to access logs for longer periods of time, enabling
point-in-time rollback and provisioning.

SAP ASE Settings

570

Delphix User Guide 2016 Delphix

Property

Usage

Staging environment

SAP ASE instance to use for validated sync

Backup path

Path to the directory, relative to the staging environment, where backups can be found

571

Delphix User Guide 2016 Delphix

Using Pre- and Post-Scripts with SAP ASE Data Sources

This topic describes the use of pre- and post-scripts with dSources.
For each script, you can add the script path and its arguments when linking a dSource in one of two ways. Either:
During the Add dSource wizard process, in the Data Management screen, click Advanced.
or
On the back of the dSource card, click the Pencil icon next to the Pre Script and Post Script fields.
To update pre- and post-script information:
1. Flip over the dSource card.
2. Click on the Pencil icon next to the Pre Script and Post Script fields.
3. When finished, click the check mark icon.
Note that pre-scripts are executed before the SnapSync policy, and if the script fails, SnapSync will fail as well. In the case of a post-script, the
script will execute after SnapSync is complete. If a post-script fails, you will see an error message.

Using Scripts with SAP ASE dSources

For SAP ASE dSources, linking pre- and post-scripts are run on the environment of the linked dSource.
Staging pre- and post-scripts are run on the staging environment

Available Variables for SAP ASE dSource Scripts

These environment variables are set by Delphix Engine for scripts running on a SAP ASE dSource or VDB:
Environment variable

Value

ASE_ENVUSER

Environment user executing the scripts

ASE_DBUSER

SAP ASE user name

ASE_DATABASE

SAP ASE database name

ASE_INSTANCE

SAP ASE instance name

ASE_PORT

SAP ASE instance port

Specifying Arguments for SAP ASE Scripts

You can specify multiple arguments for a script. In the Pre or Post Script field, enter the path to the script, and then list the arguments. If the
argument contains spaces, enclose it in single or double quotes. You can escape single quotes within the argument with a backslash.

An Example with Three Arguments

/opt/app/product/10.2.0.5/db_1/dbs/myscript.sh one "second argument in double quotes" 'third argument in single quotes

An Example with an Apostrophe

/opt/app/product/10.2.0.5/db_1/dbs/myscript.sh 'I\'d rather be in Hawaii.'

572

Delphix User Guide 2016 Delphix

Deleting an SAP ASE dSource

This topic describes how to delete an SAP ASE dSource.

Prerequisites
You cannot delete a dSource that has dependent VDBs. Before deleting a dSource, make sure all dependent VDBs have been deleted
as described in Deleting an SAP ASE VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the Databases panel, select the dSource you want to delete.
6. Click the Trash Can icon.
7. Click Yes to confirm.

573

Delphix User Guide 2016 Delphix

Detaching and Re-Attaching SAP ASE dSources

This topic describes how to detach dSources and re-attach them to a different source database.
Each dSource contains an association with the source database, as well as the data it has pulled from the source database up to that point. It is
possible to detach, or unlink, a dSource from its source database. This breaks the association with the source database without affecting the data
within the Delphix Engine. Detached dSources and their source databases have these properties:
You can use detached dSources as the source of virtual database (VDB) provisioning operations.
You can re-link the source database as a different dSource.

Detaching a dSource
1. Login to the Delphix Admin application as a user with OWNER privileges on the dSource, group, or domain.
2. Click Manage.
3. Select My Databases.
4. Select the database you want to unlink or delete.
5. Click the Unlink icon.
A warning message will appear.
6. Click Yes to confirm.

Attaching a dSource
Rebuilding Source Databases and Using VDBs
In situations where you want to rebuild a source database, you will need to detach the original dSource and create a new one
from the rebuilt data source. However, you can still provision VDBs from the detached dSource.
1. Detach the dSource as described above.
2. Rename the detached dSource by clicking the Edit icon in the upper left-hand corner of the dSource card, next to its
name.
This is necessary only if you intend give the new dSource the same name as the original one. Otherwise, you will see
an error message.
3. Create the new dSource from the rebuilt database.
You will now be able to provision VDBs from both the detached dSource and the newly created one, but the detached dSource
will only represent the state of the source database prior to being detached.

The attach operation is currently only supported from the command line interface (CLI). Full GUI support will be added in a future release. Only
databases that represent the same physical database can be re-attached
1. Login to the Delphix CLI as a user with OWNER privileges on the dSource, group, or domain.
2. Select the dSource by name using database select <dSource>.
3. Run the attachSource command.
4. Set the source config to which you want to attach using set source.config=<newSource>. Source configs are named by their
database unique name.
5. Set any other source configuration operations as you would for a normal link operation.
6. Run the commit command.

574

Delphix User Guide 2016 Delphix

Enabling and Disabling SAP ASE dSources

This topic describes how to enable and disable dSources for operations such as backup and restore.
For certain processes, such as backing up and restoring the source database, you may want to temporarily disable your dSource. Disabling a
dSource turns off communication between the dSource and the source database, but does not tear down the configuration that enables
communication and data updating to take place. When a disabled dSource is later enabled, it will resume communication and incremental data
updates from the source database according to the original policies and data management configurations that you set.
Disabling a dSource is also a prerequisite for several other operations, like database migration and upgrading the dSource after upgrade of the
associated data source.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the dSource you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the dSource again, move the slider control from Disabled to Enabled, and the dSource will continue to function as
it did previously.

575

Delphix User Guide 2016 Delphix

SAP ASE dSource Icon Reference

This topic illustrates the icons that appear on dSources and Virtual Databases (VDBs) in the Delphix Engine Graphic User Interface, and
describes the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See the error logs for more information.
There is a warning fault associated with the dSource or VDB. See the error logs for more information.
The Delphix Engine is checking the VDB status.
The dSource has been deleted or the Source status is UNKNOWN.
The state of the VDB is unknown. This is often associated with a connection error.
The VDB is inactive.
The dSource has been unlinked from the source database.
The VDB is disabled, is in the process of being created, or the creation process has been canceled or failed. For more information,
see Enabling and Disabling SAP ASE VDBs.
The VDB is running normally
The dSource is disabled. For more information, see Enabling and Disabling SAP ASE dSources.

The dSource or VDB is ready for Linux Transformation.

576

Delphix User Guide 2016 Delphix

Provisioning VDBs from SAP ASE dSources

These topics describe special tasks and concepts for provisioning VDBs from SAP ASE dSources.
Provisioning SAP ASE VDBs: An Overview
Provisioning an SAP ASE VDB
Provisioning an SAP ASE VDB from a Replicated VDB or dSource
Enabling and Disabling SAP ASE VDBs
Deleting an SAP ASE VDB
Migrating an SAP ASE VDB
Refreshing an SAP ASE VDB
Rewinding an SAP ASE VDB
SAP ASE VDB Icon Reference

577

Delphix User Guide 2016 Delphix

Provisioning SAP ASE VDBs: An Overview

Before you provision SAP ASE virtual databases (VDBs), you must:
Already have linked a dSource from a source database, as described in Linking an SAP ASE dSource, or have already created a VDB
from which you want to provision another VDB
Ensure that you have the required privileges on the target environment, as described in Requirements for SAP ASE Target Hosts and
Databases
If you are provisioning to a target environment that is different from the one in which you set up the staging database, you must ensure
that the two environments have compatible operating systems, as described in Requirements for SAP ASE Target Hosts and
Databases

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. Select a dSource.
6. Select a means of provisioning.
See Provisioning by Snapshot and LogSync in this topic for more information.
7. Click Provision.
The Provision VDB panel will open, and the Instance and Database Name fields will auto-populate with information from the dSource.
8. Specify any Pre or Post Scripts that should be used during the provisioning process.
9. Click Next.
10. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
11. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
12. Click Next.
13. If your Delphix Engine system administrator has configured the Delphix Engine to communicate with an SMTP server, you will be able to
specify one or more people to notify when the provisioning is done. You can choose other Delphix Engine users, or enter email
addresses.
14. Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and it will be listed in the Databases panel. If you
select the VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database
and its Data Management settings.

Provisioning by Snapshot or LogSync

When provisioning by snapshot, you can provision to the start of any particular snapshot.
If LogSync is enabled on the dSource, you can provision by LogSync information. When provisioning by LogSync information, you can provision
to any point in time, within a particular snapshot. The TimeFlow view for a dSource shows multiple snapshots by default. To view the LogSync
data for an individual snapshot, use the Slide to Open LogSync control at the top of an individual snapshot card.

578

Delphix User Guide 2016 Delphix

Provisioning an SAP ASE VDB

This topic describes how to provision a virtual database (VDB) from a SAP ASE dSource.

Prerequisites
Before you provision an SAP ASE VDB, you must:
Have linked a dSource from a source database, as described in Linking an SAP ASE Data Source, or have already created a VDB from
which you want to provision another VDB
Have set up target environments as described in Adding an SAP ASE Environment
Ensure that you have the required privileges on the target environment as described in Requirements for SAP ASE Target Hosts and
Databases
If you are provisioning to a target environment that is different from the one in which you set up the staging database, you must make
sure that the two environments have compatible operating systems, as described in Requirements for SAP ASE Target Hosts and
Databases. For more information on the staging database and the validated sync process, see Managing SAP ASE Environments: An
Overview.

Procedure
1. Login to the Delphix Admin application.
2. Click Manage
3. Select Databases.
4. Click My Databases.
5. Select a dSource.
6. Select a means of provisioning.
For more information, see Provisioning by Snapshot and LogSync.
7. Click Provision.
The Provision VDB panel will open, and the Instance and Database Name fields will auto-populate with information from the dSource.
8. Select whether to enable Truncate Log on Checkpoint database option for the VDB.
9. Click Next.
10. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
11. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
12. Click Next.
13. Specify any Hooks to be used during the provisioning process.
For more information, see Customizing SAP ASE Management with Hook Operations.
14. If your Delphix Engine system administrator has configured the Delphix Engine to communicate with an SMTP server, you will be able to
specify one or more people to notify when the provisioning is done. You can choose other Delphix Engine users or enter email
addresses.
15. Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and it will be listed in the Databases panel. If you
select the VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database
and its Data Management settings.

Provisioning by Snapshot
You can provision to the start of any snapshot by selecting that snapshot card from the TimeFlow view, or by entering a value in the time entry
fields below the snapshot cards. The values you enter will snap to the beginning of the nearest snapshot.

Provisioning by LogSync
If LogSync is enabled on the dSource, you can provision by LogSync information. When provisioning by LogSync information, you can provision
to any point in time within a particular snapshot. The TimeFlow view for a dSource shows multiple snapshots by default. To view the LogSync
data for an individual snapshot, use the Slide to Open LogSync control at the top of an individual snapshot card. Drag the red triangle to the
point in time from which you want to provision. You can also enter a date and time directly.

579

Delphix User Guide 2016 Delphix

Related Links
Linking an SAP ASE Data Source
Adding an SAP ASE Environment
Requirements for SAP ASE Target Hosts and Databases
Managing SAP ASE Environments: An Overview
Customizing SAP ASE Management with Hook Operations

580

Delphix User Guide 2016 Delphix

Provisioning an SAP ASE VDB from a Replicated VDB or dSource

This topic describes how to provision from a replicated dSource or virtual database (VDB). The process for provisioning from replicated objects is
the same as the typical VDB provisioning process, except that first you need to select the replica containing the replicated object.
Prerequisites
Procedure
Post-Requisites

Prerequisites
You must have replicated a dSource or a VDB to the target host, as described in Replication Overview
You must have added a compatible target environment on the target host

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB you want to provision.
6. The provisioning process is now identical to the process for provisioning standard objects.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

581

Delphix User Guide 2016 Delphix

Enabling and Disabling SAP ASE VDBs

This topic describes how to enable and disable a virtual database (VDB).
Disabling a VDB is a pre-requisite for procedures such as VDB migration or upgrade. Disabling a VDB removes all traces of it, including any
configuration files, from the target environment to which it was provisioned. When the VDB is later enabled again, these configuration files are
restored on the target environment.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the VDB you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the VDB again, move the slider control form Disabled to Enabled, and the VDB will continue to function as it did
previously.

582

Delphix User Guide 2016 Delphix

Deleting an SAP ASE VDB

This topic describes how to delete an SAP ASE virtual database (VDB).

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. Select the VDB you want to delete.
6. Click the Trash icon.
7. Click Yes to confirm.

583

Delphix User Guide 2016 Delphix

Migrating an SAP ASE VDB

This topic describes how to migrate a Virtual Database (VDB) from one target environment to another.
There may be situations in which you want to migrate a virtual database to a new target environment, for example when upgrading the host on
which the VDB resides, or as part of a general data center migration. This is easily accomplished by first disabling the database, then using the
Migrate VDB feature to select a new target environment.
Prerequisites
Procedure

Prerequisites
You should have already set up a new target environment that is compatible with the VDB that you want to migrate.

Procedure
1. Login to your Delphix Engine using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. Select the VDB you want to migrate.
6. Click the Open icon.
7. Slide the Enable/Disable control to Disabled.
8. Click Yes to confirm.
When the VDB is disabled, its icon will turn gray.
9. In the lower right-hand corner of the VDB card, click the VDB Migrate icon.
10. Select the new target environment for the VDB, the user for that environment, and the database instance where the VDB will reside.
11. Click the Check icon to confirm your selections.
12. Slide the Enable/Disable control to Enabled.
13. Click Yes to confirm.
Within a few minutes, your VDB will re-start in the new environment, and you can continue to work with it as you would any other VDB.

584

Delphix User Guide 2016 Delphix

Refreshing an SAP ASE VDB

Prerequisites
Procedure
This topic describes how to manually refresh a VDB.
Refreshing a VDB will re-provision the VDB from the dSource. As with the normal provisioning process, you can choose to refresh the VDB from a
snapshot or a specific point in time. However, you should be aware that refreshing a VDB will delete any changes that have been made to it over
time. When you refresh a VDB, you are essentially re-setting it to the state you select during the refresh process. You can refresh a VDB
manually, as described in this topic, or you can set a VDB refresh policy, as described in the topics Managing Policies: An Overview, Creating
Custom Policies, and Creating Policy Templates.

Although the VDB no longer contains the previous contents, the previous Snapshots and TimeFlow still remain in
Delphix and are accessible through the Command Line Interface (CLI).

Prerequisites
To refresh a VDB, you must have the following permissions:
Auditor permissions on the dSource associated with the VDB
Auditor permissions on the group that contains the VDB
Owner permissions on the VDB itself
A user with Delphix Admin credentials can perform a VDB Refresh on any VDB in the system.

Procedure
1. Login to the Delphix Admin application.
2. Under Databases, select the VDB you want to refresh.
3. Click the Open icon to open the VDB's card.
4. On the back of the VDB card, click the Refresh VDB icon in the lower right-hand corner.
This will open the screen to re-provision the VDB.
5. Select the refresh point as a snapshot or a point in time.
6. Click Refresh VDB.
7. If you want to use login credentials on the target environment other than those associated with the environment user, click Provide
Privileged Credentials.
8. Click Yes to confirm.

585

Delphix User Guide 2016 Delphix

Rewinding an SAP ASE VDB

This topic describes the procedure for rewinding an SAP ASE virtual database (VDB).
Rewinding a VDB rolls it back to a previous point in its TimeFlow and re-provisions the VDB. The VDB will no longer contain changes after the
rewind point.

Although the VDB no longer contains changes after the rewind point, the rolled over Snapshots and TimeFlow still remain in
Delphix and are accessible through the Command Line Interface (CLI). See the topic CLI Cookbook: Rolling Forward a VDB f
or instructions on how to use these snapshots to refresh a VDB to one of its later states after it has been rewound.
Prerequisites
Procedure

Prerequisites
To rewind a VDB, you must have the following permissions:
Auditor permissions on the dSource associated with the VDB
Owner permissions on the VDB itself
You do NOT need owner permissions for the group that contains the VDB. A user with Delphix Admin credentials can perform a VDB Rewind on
any VDB in the system.

Procedure
1. Login to the Delphix Admin application.
2. Under Databases, select the VDB you want to rewind.
3. Select the rewind point as a snapshot or a point in time.
4. Click Rewind.
5. If you want to use login credentials on the target environment other than those associated with the environment user, click Provide
Privileged Credentials.
6. Click Yes to confirm.

You can use TimeFlow bookmarks as the rewind point when using the CLI. Bookmarks can be useful to:
Mark where to rewind to - before starting a batch job on a VDB for example.
Provide a semantic point to revert back to in case the chosen rewind point turns out to be incorrect.
For a CLI example using a TimeFlow bookmark, see CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark.

586

Delphix User Guide 2016 Delphix

SAP ASE VDB Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

587

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

588

Delphix User Guide 2016 Delphix

Customizing SAP ASE Management with Hook Operations

Hook operations allow you to execute an ordered list of custom operations at select hook points in linking, provisioning and virtual dataset
management. For details on the types of operations that are available, see children of this page.
dSource Hooks
Virtual Dataset Hooks
Setting Hook Operations
Setting Hook Operations through the Delphix Admin Application
Setting Hook Operations through the CLI
Example of Editing Hook Operations through the CLI
Hook Operation Templates
Creating a Hook Operation Template
Importing a Hook Operation Template
Exporting a Hook Operation Template

dSource Hooks
Hook

Description

Pre-Sync

Operations performed before a sync.

These operations can quiesce data to be captured during the sync, or stop processes that may interfere with the sync.

Post-Sync

Operations performed after a sync. This hook will run regardless of the success of the sync or Pre-Sync hook operations.
These operations can undo any changes made by the Pre-Sync hook.

Virtual Dataset Hooks

Hook

Description

Configure
Clone

Operations performed after initial provision or after a refresh. This hook will run after the virtual dataset has been started.
During a refresh, this hook will run before the Post-Refresh hook.

Pre-Refresh

Operations performed before a refresh.

These operations can cache data from the virtual dataset to be restored after the refresh completes.

Post-Refresh

Operations performed after a refresh. During a refresh, this hook will run after the Configure Clone hook. This hook will not run
if the refresh or Pre-Refresh hook operations fail.
These operations can restore cached data after the refresh completes.

Pre-Rewind

Operations performed before a rewind.

These operations can cache data from the virtual dataset to be restored after the rewind completes.

Post-Rewind

Operations performed after a rewind. This hook will not run if the rewind or Pre-Rewind hook operations fail.
These operations can restore cached data after the rewind completes.

Pre-Snapshot

Operations performed before a snapshot.

These operations can quiesce data to be captured during the snapshot, or stop processes that may interfere with the
snapshot.

Post-Snapshot

Operations performed after a snapshot. This hook will run regardless of the success of the snapshot or Pre-Snapshot hook
operations.
These operations can undo any changes made by the Pre-Snapshot hook.

Operation Failure
If a hook operation fails, it will fail the entire hook: no further operations within the failed hook will be run.

Setting Hook Operations

589

Delphix User Guide 2016 Delphix

You can construct hook operation lists through the Delphix Admin application or the command line interface (CLI). You can either define the
operation lists as part of the linking or provisioning process or edit them on dSources or virtual datasets that already exist.

Setting Hook Operations through the Delphix Admin Application

To specify hook operations during linking or provisioning, navigate to the Hooks tab of the Linking Wizard or Provision Wizard.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation or click Import to load a hook operation template.
4. Click the text area and edit the contents of the operation.
5. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
6. To remove an operation from the list, click the Trash icon on the operation.
7. When you have set all hook operations, click Next to continue with the provisioning process.
To edit hook operations on an already-existing dSource or virtual dataset, navigate to the Hooks tab on the back of the dSource card or virtual
dataset card.
1. Select the hook to edit.
2. The current operations at this hook will be displayed. To edit this list of operations, click the Pencil icon in the top right-hand corner of the
card.
3. Click the Plus icon to add a new operation.
4. Select the type of operation or click Import to load a hook operation template.
5. Click the text area and edit the contents of the operation.
6. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
7. To remove an operation from the list, click the Trash icon on the operation.
8. When you have set all hook operations, click Check to save the changes.

Setting Hook Operations through the CLI

To specify hook operations during linking, edit the relevant hook's array of operations defined on the LinkingParameters > Source >
Operations object.
To specify hook operations during provisioning, edit the relevant hook's array of operations defined on the ProvisionParameters > Source
> Operations object.
To edit hook operations on an already-created dSource, edit the relevant hook's array of operations defined on the Source > Operations obje
ct.
To edit hook operations on an already-created virtual dataset, edit the relevant hook's array of operations defined on the Source > Operation
s object.
For more information about these CLI objects, see the LinkedSourceOperations, VirtualSourceOperations, RunCommandOnSourceOp
eration, and RunExpectOnSourceOperation API documentation in the Help menu of the Delphix Admin application.

Example of Editing Hook Operations through the CLI

1. Navigate to the relevant source's VirtualSourceOperations object.
2. Select a hook to edit.
delphix> source
delphix source> select "pomme"
delphix source "pomme"> update
delphix source "pomme" update *> edit operations
delphix source "pomme" update operations *> edit postRefresh
3. Add an operation at index 0.
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
Properties
type: RunCommandOnSourceOperation (*)
command: echo Refresh completed. (*)
delphix source "pomme" update operations postRefresh

590

*> add
0 *> set type=RunCommandOnSourceOperation
0 *> set command="echo Refresh completed."
0 *> ls

0 *> commit

Delphix User Guide 2016 Delphix

4. Add another operation at index 1 and then delete it.

delphix
delphix
delphix
delphix
delphix
delphix

source
source
source
source
source
source

"pomme"
"pomme"
"pomme"
"pomme"
"pomme"
"pomme"

update
update
update
update
update
update

operations
operations
operations
operations
operations
operations

postRefresh
postRefresh
postRefresh
postRefresh
postRefresh
postRefresh

*> add
1 *> set type=RunCommandOnSourceOperation
1 *> set command="echo Refresh completed."
1 *> back
*> unset 1
*> commit

Hook Operation Templates

You can use templates to store commonly used operations, which allows you to avoid repeated work when an operation is applicable to more
than a single dSource or virtual dataset. You manage templates through the Delphix Admin application.
Hook Operations Templates Not Available via CLI
Hook operation templates cannot be fully utilized from the CLI. Manage and use hook operations through the Delphix Admin applicatio
n.

Creating a Hook Operation Template

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Operation Templates.
4. Click the Plus icon to add a new operation template.
5. Enter a Name for the template.
6. Select an operation Type.
7. Enter a Description detailing what the operation does or how to use it.
8. Enter operation Contents to implement the operation partially or fully.
9. Click Create.

Importing a Hook Operation Template

To import a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Click Import.
4. Select the template to import.
5. Click Import.
6. When you have set all hook operations, click Check to save the changes.

Exporting a Hook Operation Template

To export a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation.
4. Click the text area and edit the contents of the operation.
5. Click Export.
6. Enter a Name for the template.
7. Enter a Description detailing what the operation does or how to use it.
8. Click Create.

591

Delphix User Guide 2016 Delphix

SAP ASE Hook Operation Notes

Shell Operations
RunCommand Operation
RunBash Operation
Shell Operation Tips
Other Operations
RunExpect Operation
SAP ASE Environment variables
dSource Environment Variables
VDB Environment Variables

Shell Operations
RunCommand Operation

The RunCommand operation runs a shell command on a Unix environment using whatever binary is available at /bin/sh. The environment user
runs this shell command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the shell command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Examples of RunCommand Operations

You can input the full command contents into the RunCommand operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
if test -d "$remove_dir"; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
If a script already exists on the remote environment and is executable by the environment user, the RunCommand operation can execute this
script directly.

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh "$ARG_ENVIRONMENT_VARIABLE" "second

argument in double quotes" 'third argument in single quotes'
RunBash Operation

The RunBash operation runs a Bash command on a Unix environment using a bash binary provided by the Delphix Engine.The environment user
runs this Bash command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the Bash command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of RunBash Operations

You can input the full command contents into the RunBash operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
# Bashisms are safe here!
if [[ -d "$remove_dir" ]]; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
Shell Operation Tips
Using nohup

592

Delphix User Guide 2016 Delphix

You can use the nohup command and process backgrounding from resource in order to "detach" a process from the Delphix Engine. However, if
you use nohup and process backgrounding, you MUST redirect stdout and stderr.
Unless you explicitly tell the shell to redirect stdout and stderr in your command or script, the Delphix Engine will keep its connection to the
remote environment open while the process is writing to either stdout or stderr . Redirection ensures that the Delphix Engine will see no more
output and thus not block waiting for the process to finish.
For example, imagine having your RunCommand operation background a long-running Python process. Below are the bad and good ways to do
this.
Bad Examples
nohup
nohup
nohup
nohup

python
python
python
python

file.py
file.py
file.py
file.py

& # no redirection
2>&1 & # stdout is not redirected
1>/dev/null & # stderr is not redirected
2>/dev/null & # stdout is not redirected

Good Examples
nohup python file.py 1>/dev/null 2>&1 & # both stdout and stderr redirected, Delphix Engine will not
block

Other Operations
RunExpect Operation

The RunExpect operation executes an Expect script on a Unix environment. The Expect utility provides a scripting language that makes it easy to
automate interactions with programs which normally can only be used interactively, such as ssh. The Delphix Engine includes a
platform-independent implementation of a subset of the full Expect functionality.
The script is run on the remote environment as the environment user from their home directory. The Delphix Engine captures and logs all output
of the script. If the operation fails, the output is displayed in the Delphix Admin application and CLI to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunExpect Operation

Start an ssh session while interactively providing the user's password.

spawn ssh [email protected]

expect {
-re {Password: } {
send "${env(PASSWORD_ENVIRONMENT_VARIABLE)}\n"
}
timeout {
puts "Timed out waiting for password prompt."
exit 1
}
}
exit 0
SAP ASE Environment variables
Operations that run user-provided scripts have access to environment variables. For operations associated with specific dSources or virtual
databases (VDBs), the Delphix Engine will always set environment variables so that the user-provided operations can use them to access the
dSource or VDB.
dSource Environment Variables

Environment Variables

Description

ASE_ENVUSER

Environment username for the dSource

ASE_DBUSER

Database username for the dSource

ASE_DATABASE

Database name for the dSource

593

Delphix User Guide 2016 Delphix

ASE_INSTANCE

SAP ASE Instance name for the dSource

ASE_PORT

SAP ASE Instance port for the dSource

VDB Environment Variables

Environment Variables

Description

ASE_ENVUSER

Environment username for the VDB

ASE_DBUSER

Database username for the VDB

ASE_DATABASE

Database name for the VDB

ASE_INSTANCE

SAP ASE Instance name for the VDB

ASE_PORT

SAP ASE Instance port for the VDB

594

Delphix User Guide 2016 Delphix

DB2 Environments and Data Sources

595

Delphix User Guide 2016 Delphix

DB2 on Delphix: An Overview

Introduction to DB2
DB2 Authentication
DB2 Instances
High Availability Disaster Recovery (HADR)
Log Transmitting
Multiple Standby
Delphix HADR Synchronization

Introduction to DB2
DB2 for Linux, UNIX and Windows is a database server product developed by IBM. Sometimes called DB2 LUW for brevity, it is part of the DB2
family of database products. DB2 LUW is the "Common Server" product member of the DB2 family, designed to run on most popular operating
systems. By contrast, all other DB2 products are specific to a single platform.
DB2 LUW was initially called DB2 Universal Database (UDB), but over time IBM marketing started to use the same term for other database
products, notably mainframe (z-Series) DB2. Thus the DB2 for Linux, UNIX and Windows moniker became necessary to distinguish the common
server DB2 LUW product from single-platform DB2 products.
The current DB2 LUW product runs on multiple Linux and UNIX distributions, such as Red Hat Linux, SUSE Linux, AIX, HP/UX, and Solaris, and
most Windows systems. Multiple editions are marketed for different sizes of organization and uses. The same code base is also marketed without
the DB2 name as IBM InfoSphere Warehouse edition.
The version numbers in DB2 are non-sequential with v10.1 and 10.5 being the two most recent releases. Specifics of DB2 versions and platforms
supported on Delphix are located in the DB2 Compatibility Matrix.

DB2 Authentication
Authentication is the process of validating a supplied user ID and password using a security mechanism. User and group authentication is
managed in a facility external to DB2 LUW, such as the operating system, a domain controller, or a Kerberos security system. This is different
from other database management systems (DBMSs), such as Oracle and SQL Server, where user accounts may be defined and authenticated in
the database itself, as well as in an external facility such as the operating system.
Any time a user ID and password is explicitly provided to DB2 LUW as part of an instance attachment or database connection request, DB2
attempts to authenticate that user ID and password using this external security facility. If no user ID or password is provided with the request, DB2
implicitly uses the user ID and password that were used to log in to the workstation where the request originated. More information of DB2
authentication and authorization is available via IBM documentation.
Delphix DB2 authentication
Delphix for DB2 requires that that the staging and target hosts must already have the necessary users and authentication systems
created/installed on them. Delphix will neither create users nor change database passwords as part of the provisioning process.

DB2 Instances
A DB2 instance is a logical database manager environment that can catalog databases and set configuration parameters. Depending on specific
needs, customers can create multiple instances on the same physical server to provide a unique database server environment for each instance.
Associated with an instance is the concept of an instance owner. This is the user that "owns" that instance and has SYSADM authority over the
instance and all databases inside that instance. SYSADM authority is the highest level of authority in DB2 and lets this user perform several
database management activities such upgrade, restore, edit configurations, etc... More information about intances can be found the IBM
knowledge center.
Delphix DB2 Instances
Delphix operates on the instance level and requires that the staging and target hosts must have the empty instances created a prior to
Delphix using them, and the instance owners added as environment users. It is important to note that our dSources and VDBs are
entire instances and NOT specific databases inside an instance.

High Availability Disaster Recovery (HADR)

The HADR feature of IBM DB2 provides a high availability solution for both partial and complete site failures. It protects against data loss by
replicating data changes from a source database, called the primary, to one or more target databases, called the standby.

596

Delphix User Guide 2016 Delphix

Delphix HADR
HADR replication takes place at a database level, not at the instance level. Therefore, a standby instance can have multiple databases
from multiple different primary servers/instances on it. If the instance ID on the Delphix standby is NOT the same as the instance ID on
the primary, the Delphix standby instance ID MUST have database permissions secadm and dbadm granted to it on the primary
database. These permissions, and all HADR settings, must be implemented on the primary database BEFORE you take the backup on
the primary database.

Log Transmitting
All changes that take place at the primary database server are written into log files. The individual log records within the log files are then
transmitted to the secondary database server, where the recorded changes are replayed to the local copy of the database. This procedure
ensures that the primary and the secondary database servers are in a synchronized state. Using two dedicated TCP/IP communication ports and
a heartbeat, the primary and the standby databases track where they are processing currently, the current state of replication, and whether the
standby database is up-to-date with the status of the primary database. When a log record is "closed" (still in memory, but has yet to be written to
disk on the primary), it is immediately transmitted to the HADR standby database(s). Transmission of the logs to the standbys may also be
time-delayed.

Multiple Standby
Beginning in DB2 v10.1,the HADR feature supports multiple standby databases. This enables an advanced topology where you can deploy HADR
in multiple standby mode with up to three standby databases for a single primary. One of the databases is designated as the principal HADR
standby database, with the others termed as auxiliary HADR standby databases. As with the standard HADR deployment, both types of HADR
standbys are synchronized with the HADR primary database through a direct TCP/IP connection. Furthermore, both types support the reads on
standby feature and can be configured for time-delayed log replay. It is possible to issue a forced or non-forced takeover on any standby,
including the delphix auxiliary standby. However, you should never use the Delphix auxiliary standby as a primary, because this will impact
Delphix performance.

Delphix HADR Synchronization

The Delphix for DB2 uses the HADR capability of DB2 to synchronize data from a production DB2 database into a Delphix-controlled DB2
"standby" server. By using this mature and existing DB2 capability, the Delphix Engine is able to ingest data and keep the standby server in sync
with only a minimal impact on production. The HADR connection is configured to Super-Asynchronous (SUPERASYNC) mode where log writes
are considered successfully transmitted when the log records are sent from the primary database. Because the primary database does not wait
for acknowledgements from the standby database, there is no delay on the primary and transactions are considered committed regardless of the
state of the replication of that transaction. For further information on Delphix synchronization, see Linking a dSource from a DB2 Database: An
Overview.

597

Delphix User Guide 2016 Delphix

DB2 Support and Requirements

DB2 Compatibility Matrix
Network and Connectivity Requirements for DB2 Environments
Requirements for DB2 Hosts and Databases

598

Delphix User Guide 2016 Delphix

DB2 Compatibility Matrix

This topic describes the DB2 (DBMS) versions that are supported by Delphix, as well as the compatible operating systems (OS), for use on target
and source environments.
Source, Staging and Target OS and DBMS Compatibility
The source, staging and target hosts must all be running the same DBMS/Operating System combination (for example, DB2 10.5.4 on
RHEL 6.5) in order to successfully provision a VDB to the target.

Supported DBMS Versions

DB2 Enterprise Server Edition 10.1
DB2 Advanced Enterprise Server Edition 10.1
DB2 Enterprise Server Edition 10.5
DB2 Advanced Enterprise Server Edition 10.5

Supported Operating Systems

Operating System

Version

Processor Family

Red Hat Enterprise Linux

6.5, 6.6

x86_64

AIX

7.1

Power

Unsupported DB2 Features

DB2 DPF
DB2 Purescale
DB2 BLU

599

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for DB2 Environments

This topic outlines the network and connectivity requirements for the Delphix Engine and DB2 standby and target environments.
Port Allocations Specific to DB2
Inbound to the Delphix Engine Port Allocation
Outbound from a Standby or Target Environment Port Allocation
Inbound to a Standby or Target Environment Port Allocation
HADR Service Ports
General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration

Port Allocations Specific to DB2

The Delphix Engine makes use of the following network ports for DB2 standby and target:
Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP/UDP

111

Remote Procedure Call (RPC) port mapper used for NFS mounts
Note: RPC calls in NFS are used to establish additional ports, in the high range 32768-65535, for supporting services.
Some firewalls interpret RPC traffic and open these ports automatically. Some do not.

TCP

1110

NFS Server daemon status and NFS server daemon keep-alive (client info)

TCP/UDP

2049

NFS Server daemon from vFiles to the Delphix Engine

TCP

4045

NFS lock daemon/manager

UDP

33434 33464

Traceroute from standby and target hosts to the Delphix Engine (optional)

UDP/TCP

32768 65535

NFS mountd and status services, which run on a random high port. Necessary when a firewall does not dynamically
open ports.

Outbound from a Standby or Target Environment Port Allocation

Protocol

Port Numbers

Use

TCP

873

Rsync connections used during V2P

TCP

xxxx

DSP connections used for monitoring and script management. Typically DSP runs on port 8415.

Inbound to a Standby or Target Environment Port Allocation

Protocol

Port Numbers

Use

TCP

22

SSH connections to target environment

HADR Service Ports

The HADR ports set for HADR_LOCAL_SVC and HADR_REMOTE_SVC on the DB2 Master and Standby hosts. The specific ports used at the
customers discretion and need to be specified during the linking process. It is highly recommended that this ports also be defined in the
/etc/services file to ensure that they are only used by DB2 for the specified databases.

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

600

Delphix User Guide 2016 Delphix

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

601

Delphix User Guide 2016 Delphix

Requirements for DB2 Hosts and Databases

DB2 hosts are servers that have DB2 binaries installed and have DB2 instances created on them. The hosts that contain the data that we wish to
ingest are referred to as the source environment. Hosts with empty instances (no dbs in instance) are used as either staging or target hosts. This
topic describes the requirements for creating connections between the Delphix Engine and DB2 hosts and instances.
Requirements for DB2 Source Hosts and Instances
Requirements for DB2 Staging and Target Hosts and Instances
Additional Environment Requirements
Instance User Requirements
Database Container Requirements
Related Links

Requirements for DB2 Source Hosts and Instances

Each DB2 Source host (master) must meet these requirements:
IBM DB2 installed and instance created on the machine
HADR settings for each database to be used with the standby server should be preset before the linking process begins as described in
Linking a DB2 dSource

Requirements for DB2 Staging and Target Hosts and Instances

The staging environment that the Delphix Engine uses must have access to an existing full backup of the source database on disk to
create the first full copy. We recommend using compressed backups as that will reduce storage needs and speed up ingest.
The staging and target DB2 instances that you wish to use must already exist on the host and contain no existing databases.
The available instances on each host can be verified by going to the databases tab for the environment in question.

Additional Environment Requirements

There must be an operating system user (delphix_os) with these privileges:
Ability to login to the target environment via SSH
The following permissions are usually granted via sudo authorization of the commands.
See Sudo Privilege Requirements for further explanation of the commands and for examples of the /etc/sudoers f
ile on different operating systems.
Permission to run mount, unmount, mkdir, and rmdir as a super-user
If the target host is an AIX system, permission to run the nfso command as a super-user
There must be a directory on the staging and target environment where you can install the Delphix Engine Toolkit for example, /var/
opt/delphix/toolkit .
The delphix_os user must own the directory.
The directory must have permissions -rwxrwx--- (0770), but you can also use more permissive settings.
The delphix_os user must have read and execute permissions on each directory in the path leading to the toolkit directory. For
example, when the toolkit is stored in /var/opt/delphix/toolkit, the permissions on /var, /var/opt, and /var/opt/d
elphix should allow read and execute for "others," such as -rwxr-xr-x.
The directory should have 1.5GB of available storage: 400MB for the toolkit and 400MB for the set of logs generated by each
DB2 instance that runs on the host.
The Delphix Engine must be able to initiate an SSH connection to the target environment
NFS client services must be running on the target environment

Instance User Requirements

The instance owner of each instance you wish to use within a staging or a target host must be added as an environment user within the
Delphix engine. See Managing DB2 Users and Instance Owners.
For HADR synced dSources the staging instance owner must be able to "read" the ingested database contents as Delphix will check the
validity of the database by querying tables before each dSource snapshot.

Database Container Requirements

All DB2 database containers types are fully supported with the exception of DB2 raw containers. NOTE: If a container is added or
deleted, the dSource will have to be resynced.

602

Delphix User Guide 2016 Delphix

Related Links
DB2 Compatibility Matrix
Setting Up DB2 Environments: An Overview

603

Delphix User Guide 2016 Delphix

Managing DB2 Environments

These topics describe special tasks and concepts for working with DB2 instances and databases
Setting Up DB2 Environments: An Overview
Adding a DB2 Environment
Editing DB2 Environment Attributes
Managing DB2 Instances
Managing DB2 Users and Instance Owners
Deleting a DB2 Environment
Refreshing a DB2 Environment

604

Delphix User Guide 2016 Delphix

Setting Up DB2 Environments: An Overview

This topic describes the high-level process for adding DB2 environments, linking DB2 instances to the Delphix Engine, and provisioning virtual
instances.

Delphix for DB2 Architecture

Delphix uses the a Standby server model along with DB2s High Availability Disaster Recovery feature to ingest data and stay in sync with the
source database. The standby server is then snapshotted by the Delphix engine and the snapshots can be provisioned out to one or more target
servers.
The snapshot and provision process occurs on the instance level, all databases that exist on the standby server will be provisioned out
to the target machines. Similarly actions such as bookmark, rewind and refresh will simultaneously apply to all the databases in the
instance.

Block Diagram of Linking Architecture Between DB2 Environments and the Delphix Engine

The linking process converts an empty DB2 instance on the standby server into an HADR standby for the primary database. In order to do this the
staging instance must have access to a recent backup copy of all the databases that you wish to add the dSource. Once the restoration process
is complete, Delphix will begin issue the HADR standby commands on each database and ensure that the health of the HADR connection stays
within the acceptable threshold values you set.

DB2 Staging Instance Set Up

This step of the process must be done carefully as the Delphix for DB2 operates on the instance level while HADR replication is done on the

605

Delphix User Guide 2016 Delphix

database level. If you have only one database to be replicated it is a direct 1-1 mapping betweeen instances and databases. However it may be
advantageous to collect multiple databases needed for an application into a single Delphix staging instance which can then be used to snapshot
and provision all the databases simultaneously. It is also possible to setup databases from multiple primary hosts to use the same
standby/dSource.
The choice of databases on the staging server should also take into account the expected network traffic that HADR will create between the
source and staging environments.

Related Links
DB2 Support and Requirements

606

Delphix User Guide 2016 Delphix

Adding a DB2 Environment

This topic describes how to add a DB2 Staging environment.

Prerequisites
Make sure that the staging environment in question meets the requirements described in Requirements for DB2 Hosts and Databases

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Unix/Linux in the operating system menu.
6. Select Standalone Host
7. Enter the Host IP address.
8. Enter an optional Name for the environment.
9. Enter the SSH port.
The default value is 22.
10. Enter a Username for the environment.
For more information about the environment user requirements, see Requirements for DB2 Hosts and Databases.
11. Select a Login Type.
For Password, enter the password associated with the user in step 9.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

12. For Password Login, click Verify Credentials to test the username and password.
13. Enter a Toolkit Path.
For more information about the toolkit directory requirements, see Requirements for DB2 Hosts and Databases.
14. Click OK.
As the new environment is added, you will see two jobs running in the Delphix Admin Job History, one to Create and Discover an
environment, and another to Create an environment. When the jobs are complete, you will see the new environment added to the list in
the Environments tab. If you do not see it, click the Refresh icon in your browser.

Post-Requisites
To view information about an environment after you have created it:
1. Click Manage.
2. Select Environments.
3. Select the environment name.

Related Links

607

Delphix User Guide 2016 Delphix

Setting Up DB2 Environments: An Overview

Requirements for DB2 Hosts and Databases

608

Delphix User Guide 2016 Delphix

Editing DB2 Environment Attributes

Procedure
Common Editable Attributes
This topic describes how to edit attributes of an environment such as name, host address, ssh port, or toolkit path, as well as descriptions of more
advanced attributes for specific data platforms.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials or as the owner of an environment.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of an environment to view its attributes.
5. Under Attributes, click the Pencil icon to edit an attribute.
6. Click the Check icon to save your edits.

Common Editable Attributes

Attribute

Description

Environment
Users

The users for that environment. These are the users who have permission to ssh into an environment, or access the
environment through the Delphix Connector. See the Requirements topics for specific data platforms for more information on
the environment user requirements.

Host
Address

The IP address for the environment host.

Notes

Any other information you want to add about the environment.

609

Delphix User Guide 2016 Delphix

Managing DB2 Instances

This topic explains how to manage DB2 instances on a host.
When you add an environment with the Delphix Admin application, all existing DB2 instances on the host are automatically discovered by Delphix.
This is an important step as Delphix requires that an empty instance be available on the host to be used as either staging or target. Delphix will
not create any instances if there are no empty available instances.
A list of all discovered instances is available inside Delphix.

View Instances
1. Login to the Delphix Admin application with Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of the environment to you want to refresh.
5. Click on Databases to see a list of all DB2 instances found in the environment.

Updating Instances on a Host

If you add or remove any DB2 instances from a host you must refresh the environment using the steps listed at Refreshing a DB2 Environment t
o update the list of instances available to Delphix. Additionally the environment users must be updated to match the DB2 instance owners as
detailed in Managing DB2 Users and Instance Owners.

610

Delphix User Guide 2016 Delphix

Managing DB2 Users and Instance Owners

All DB2 Delphix operations such as linking, snapshot and provisioning always occur on the instance level. As a result we require that any DB2
instance that you wish to use either as Staging or Target must have its associated instance owner added as an environment user to the host
within Delphix. Please perform the following steps to add each DB2 instance owner you to use on the host.
It is important to note that Delphix will not create new instances on the host and can only use existing DB2 instances that finds on the host
machine. For more information on instance management refer to Managing DB2 Instances.

Adding Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure

Prerequisites
Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

611

Delphix User Guide 2016 Delphix

Deleting a DB2 Environment

This topic describes how to delete an environment.

Prerequisites
You cannot delete an environment that has any dependencies, such as dSources or virtual databases (VDBs). These must be deleted before you
can delete the environment.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, select the environment you want to delete.
5. Click the Trash icon.
6. Click Yes to confirm.

612

Delphix User Guide 2016 Delphix

Refreshing a DB2 Environment

This topic describes how to refresh an environment.
After you make changes to an environment that you have already set up in the Delphix Admin application, such as installing a new database
home, creating a new database, or adding a new listener, you may need to refresh the environment to reflect these changes.
During environment discovery and environment refreshes, Delphix pushes a fresh copy of the toolkit to each host environment. Included in the
toolkit are:
A JRE
Delphix jar files
The hostchecker utility
Scripts for managing the environment and/or VDBs
Delphix Connector log files
Delphix then executes some of these scripts to discover information about the objects in your environment (where the databases are installed,
the database names, information required to connect to these databases, etc.). In some environments (Windows in particular), the scripts are
customized to fit the customers environment.

Procedure
1. Login to the Delphix Admin application with Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. In the Environments panel, click on the name of the environment to you want to refresh.
5. Click the Refresh icon.
To refresh all environments, click the Refresh icon next to Environments.

613

Delphix User Guide 2016 Delphix

Managing DB2 Data Sources

These topics describe special tasks and concepts for linking SQL Server dSources.
DB2 dSource Icon Reference
Linking a dSource from a DB2 Database: An Overview
Linking a DB2 dSource
Deleting a DB2 dSource
Enabling and Disabling DB2 dSources
Advanced Data Management Settings for DB2 dSources
Using Pre- and Post-Scripts with DB2 dSources
Provisioning from a Replicated DB2 dSource

614

Delphix User Guide 2016 Delphix

DB2 dSource Icon Reference

This topic illustrates the icons that appear on dSources and virtual databases (VDBs) in the Delphix Engine Graphic User Interface, and describes
the meaning of each, along with tips for clearing those that represent errors.
Icon

Description
There is a critical fault associated with the dSource or VDB. See
the error logs for more information.

There is a warning fault associated with the dSource or VDB.

See the error logs for more information.

The Delphix Engine is checking the VDB status.

The dSource has been deleted or the Source status is
UNKNOWN.
The state of the VDB is unknown. This is often associated with a
connection error.
The VDB is inactive.

615

Delphix User Guide 2016 Delphix

The dSource has been unlinked from the source database.

The VDB is disabled, is in the process of being created, or the
creation process has been canceled or failed. For more
information, see Enabling and Disabling VDBs.
The VDB is running normally.

The dSource is disabled. For more information, see Enabling

and Disabling dSources.
The dSource or VDB is ready for Linux Transformation.

616

Delphix User Guide 2016 Delphix

Linking a dSource from a DB2 Database: An Overview

This topic describes basic concepts behind the creation of dSources from DB2 instances.
Instance Level Operation
Data Ingest
Data Synchronization
Virtual Instance (VDB) Provisioning
Related Topics

Instance Level Operation

A DB2 instance is a logical database manager environment that can catalog databases and set configuration parameters. Depending on specific
needs, customers can create multiple instances on the same physical server to provide a unique database server environment for each instance.
Associated with an instance is the concept of an instance owner. This is the user that "owns" that instance and has SYSADM authority over the
instance and all databases inside that instance. SYSADM authority is the highest level of authority in DB2 and lets this user perform several
database management activities such upgrade, restore, edit configurations, etc... More information about intances can be found the IBM
knowledge center.
Delphix DB2 Instances
Delphix operates on the instance level and requires that the staging and target hosts must have the empty instances created a prior to
Delphix using them, and the instance owners added as environment users. It is important to note that our dSources and VDBs are
entire instances and NOT specific databases inside an instance.

Data Ingest
DB2 for Delphix ingests data by using a Standby instance of DB2 to create the necessary data files that represent the data. This Standby instance
is converted to a Delphix dSource by going through the linking process during which it is given access to a full backup of each of the databases
that are to be added to the dSource. Delphix then runs an automated redirected restore process on the backup file in order to convert the data
files to a format and structure that is compatible with Delphix. All of the data files and log files from this backup are stored on a single NFS mount
created by the Delphix engine which allows it to snapshot the dSource as necessary.
A single standby instance can contain data from multiple source databases.

Data Synchronization
During the linking process, you can optionally setup an HADR connection between the original source databases and copies on the Standby
instance. By doing this the Standby instance will always keep its databases in sync with the source databases using HADR for log shipping. It is
important to note that a single Standby instance (dSource) can contain multiple databases from multiple different servers and instances as long as
each database has a unique name.
Delphix HADR standby maintains a different structure from the production server and should never be used as a DR failover from
production.

Virtual Instance (VDB) Provisioning

The provisioning process in DB2 for Delphix converts an empty DB2 instance on the target host into a virtual instance (also known as VDB) that
contains the same databases as the dSource. After provisioning, the data in the Virtual instance will be an independent writeable copy of the
dSource snapshot. Once a VDB has been provisioned to a target environment, you can also implement a snapshot policy for that VDB, to capture
changes within it as if it were any other logical or physical database. It is also possible to provision a VDB from a snapshot of another VDB.
A single DB2 instance can only be used for a single VDB or dSource. If you wish to create multiple copies of a VDB on a single host
you will have to pre-create the empty DB2 instances to provision data into.

Related Topics
Requirements for DB2 Hosts and Databases

617

Delphix User Guide 2016 Delphix

DB2 Compatibility Matrix

Linking a DB2 dSource

618

Delphix User Guide 2016 Delphix

Linking a DB2 dSource

This topic describes how to link a DB2 staging dSource
Prerequisites
Source Database preparation
Instance Owner Permissions
Non-HADR Database
HADR Single Standby Database
HADR Multiple Standby Databases
Backup Source Database
Procedure
Related Links

Prerequisites
Be sure that the source and staging instances meets the host requirements and the databases meet the container requirements
described in Requirements for DB2 Hosts and Databases.

Source Database preparation

Instance Owner Permissions

Delphix uses the DB2 instance owner account on the dSource for many things, including verifying that data in the databases is
accessible. If the instance name on the dSource is different from the source instance name then you must explicitly grant DBADM and
SECADM to the dSource instance owner on the source instance using the following steps:
1. Connect to the source databases as the source instance owner.
a. connect to <DB_NAME> user <INSTANCE_OWNER>
2. Issue database grant command
a. grant DBADM, SECADM on database to user <DSOURCE_INSTANCE_OWNER>
3. Repeat step 2 for every database to be included in the dSource, on the corresponding source database.

Determine if your dSource will be a non-HADR instance, an HADR single standby instance, or an HADR multiple standby instance. Non-HADR
dSources can only be updated via a full dSource resync from a newer backup file
Non-HADR Database

1. See "Instance Owner Permissions" section above.

2.

Ensure that the source database has the necessary user permissions for the provisioned VDBs as
described in Database Permissions for Provisioned DB2 VDBs

HADR Single Standby Database

1. All items in Non-HADR Database section above.

2. The following database configuration settings must be set:
a. update db cfg for <DB_NAME> using HADR_LOCAL_HOST <PRIMARY_IP> HADR_LOCAL_SVC <PRIMARY_PORT
> immediate
b. update db cfg for <DB_NAME> using HADR_REMOTE_HOST <STANDBY_IP> HADR_REMOTE_SVC
<STANDBY_PORT> immediate
c. update db cfg for <DB_NAME> using HADR_REMOTE_INST <STANDBY_INSTANCE_NAME> immediate
d. update db cfg for <DB_NAME> using HADR_SYNCMODE SUPERASYNC immediate
3. If database configuration parameter LOGINDEXBUILD is set to OFF, do the following:
i. update db cfg for <DB_NAME> using LOGINDEXBUILD ON
ii. Force off all connections to the database and reactivate the database
4. If database configuration parameter LOGARCHMETH1 is set to OFF, do the following:
a. update db cfg for <DB_NAME> using LOGARCHMETH1 XXXX (must be a valid log archiving method)
b. Take an offline backup
5. If LOGARCHMETH1 points to a third-party backup server (i.e. TSM or Netbackup) define LOGARCHMETH2 to disk
a.
619

Delphix User Guide 2016 Delphix

5.
a. update db cfg for <DB_NAME> using LOGARCHMETH2 DISK:<full path to archive log directory>
i. Log files in the directory must be available from the time of the backup until the restore has successfully
completed on the dSource.
6. db2 start hadr on db <DB_NAME> as primary by force
7. Take a full online backup as defined in the "Backup Source Database" section below.
8. Record the following information, as it must be entered on the Delphix Engine while creating the dSource.
a. HADR Primary hostname
b. HADR Primary SVC
c. HADR Standby SVC (auxiliary standby port)

HADR Multiple Standby Databases

This assumes a single standby database HADR setup already exists. The existing standby will be referred to as the main standby.
The new delphix standby will be referred to as the auxiliary standby.
1. The following database configuration settings must be set on the primary database:
a. update db cfg for <DB_NAME> using HADR_SYNCMODE <SYNC MODE> immediate set whichever sync mode you
wish to use on your main standby.
b. update db cfg for <DB_NAME> using HADR_TARGET_LIST
"<MAIN_STANDBY_IP:MAIN_STANDBY_PORT|AUXILIARY_STANDBY_IP:AUXILIARY_STANDBY_PORT>"
immediate
i. You may have up to two auxiliary standbys defined separated by a '|'; one of which must be the delphix
dSource.
2. stop hadr on db <DB_NAME>
3. start hadr on db <DB_NAME> as primary by force
4. Take a full online backup as defined in the "Backup Source Database" section below. While this backup is running, you may
continue with step 5.
5. The following database configuration settings must be set on the existing main standby database:
a. update db cfg for <DB_NAME> using HADR_SYNCMODE <same mode as defined in 1.a above.> It must be the
same value used for primary database.
b. update db cfg for <DB_NAME> using HADR_TARGET_LIST
"<PRIMARY_IP:PRIMARY_PORT|MAIN_STANDBY_IP:MAIN_STANDBY_PORT>"
6. stop hadr on db <DB_NAME>
7. start hadr on db <DB_NAME> as standby
8. Record the following information, as it must be entered on the Delphix Engine while creating the dSource (the auxiliary standby
database):
a. HADR Primary hostname
b. HADR Primary SVC
c. HADR Standby SVC (auxiliary standby port)
d. HADR_TARGET_LIST <PRIMARY_IP:PRIMARY_PORT|MAIN_STANDBY_IP:MAIN_STANDBY_PORT>

Backup Source Database

Please ensure that the Source Database Preparation steps have been completed BEFORE taking the backup.

In order to complete the linking process, the Standby dSource must have access to a full backup of the source DB2 databases on disk. This
should be a compressed online DB2 backup and must be accessible to the dSource instance owner on disk. Delphix is currently not setup to
accept DB2 backups taken using third-party sources such as Netbackup or TSM. Both HADR and Non-HADR backups must also include logs.
Example backup command: db2 backup database <DB_NAME> online compress include logs

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials or as the owner of the database from which you want to
provision the dSource.
2. Click Manage.
3. Select My Databases.
4. Select the green + icon to Add dSource.
Alternatively, on the Databases tab of Environment Management screen, you can click Add dSource next to a instance name to start
the dSource creation process.
5. In the Add dSource wizard, select the source instance on the left of the screen.

620

Delphix User Guide 2016 Delphix

5.
6. If you are working with an HADR setup, please leave the HADR checkbox checked.

7. Hit the plus icon once per database you wish to restore into this instance. For every time you hit it, the following box will be added to the
screen:

8. The database name is mandatory and must be unique for a given instance. This is the name that the database was on the instance it was
restored from and it will be the same name in this instance.
9. Enter the complete Backup Path where the database backup file resides. If no value is entered, the default value used is the instance
home directory. If there are multiple backup files for a database on the backup path, the most current one will be used.
10. Enter the Log Archive Method1 you wish to use for the database. If no valued is entered, the default valued used is
DISK:/mountpoint/dbname/arch.
11. If the dSource is to use HADR please enter the following fields. If it will not use HADR skip ahead to step 13. For more information about
HADR please view Linking a dSource from a DB2 Database: An Overview.
a. Enter a fully qualified HADR Primary Hostname. This is a required field for HADR and must match the value set for
HADR_LOCAL_HOST on the master.
b. Enter the port or /etc/services name for the HADR Primary SVC. This is a required field for HADR and uses the value set for
HADR_LOCAL_SVC on the master.
c. Enter the port or /etc/services name for the HADR Standby SVC. This is a required field for HADR and uses the value set for
HADR_REMOTE_SVC on the master.
12. Enter the value for Max Heartbeat Misses. If any of the HADR connections exceed this number of missed heartbeats the Delphix engine
will throw a fault. This value will be used for all databases defined within this instance.
13. Click Next.
14. Select a dSource Name and Database Group for the dSource.
15. Click Next.
Adding a dSource to a database group lets you set Delphix Domain user permissions for that database and its objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies.
16. Set the Staging Environment to be the same as the dSource host.
17. Select the Staging Environment User to be the same as the instance owner of the dSource instance.

Changing the Environment User

621

Delphix User Guide 2016 Delphix

If you need to change or add an environment user for the dSource instance, see Managing DB2 Users and Instance Owners
.

18. Set the Staging Mount Base to be <DSOURCE_INSTANCE_HOME_DIR>/<DSOURCE_INSTANCE_NAME>. In the example below the
instance name is db2inst1 while the instance home is /home/db2instst1

19. Set the desired Snapsync Policy for the dSource. For more information on policies see Advanced Data Management Settings for DB2
dSources.
20. Click Next.
21. Specify any desired pre- and post-scripts. For details on pre- and post-scripts, refer to Customizing DB2 Management with Hook
Operations.
22. Click Next.
23. Review the dSource Configuration and Data Management information.
24. Click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync. You can monitor these jobs by clicking Active Jobs in
the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the database icon will change to a dSou
rce icon on the Environments > Databases screen, and the dSource will appear in the list of My Databases under its assigned group.

622

Delphix User Guide 2016 Delphix

The dSource Card

After you have created a dSource, the dSource card allows you to view information about it and make modifications to its policies and
permissions. In the Databases panel, click the Open icon to view the front of the dSource card. You can then flip the card to see
information such as the Source Database and Data Management configuration. For more information, see the topic Advanced Data
Management Settings for DB2 dSources

Related Links
Requirements for DB2 Hosts and Databases
Linking a dSource from a DB2 Database: An Overview
Users, Permissions, and Policies
Managing DB2 Users and Instance Owners
Advanced Data Management Settings for DB2 dSources
Customizing DB2 Management with Hook Operations

623

Delphix User Guide 2016 Delphix

Deleting a DB2 dSource

This topic describes how to delete a dSource.

Prerequisites
You cannot delete a dSource that has dependent virtual databases (VDBs). Before deleting a dSource, make sure that you have deleted all
dependent VDBs as described in Deleting a VDB.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the Databases panel, select the dSource you want to delete.
6. Click the Trash Can icon.
7. Click Yes to confirm.

Deleting a dSource will also delete all snapshots, logs, and descendant VDB Refresh policies for that database. You cannot
undo the deletion.

624

Delphix User Guide 2016 Delphix

Enabling and Disabling DB2 dSources

This topic describes how to enable and disable dSources for operations such as backup and restore.
For certain processes, such as backing up and restoring the source database, you may want to temporarily disable your dSource. Disabling a
dSource turns off communication between the dSource and the source database, but does not tear down the configuration that enables
communication and data updating to take place. When a disabled dSource is later enabled, it will resume communication and incremental data
updates from the source database according to the original policies and data management configurations that you set.
Disabling a dSource is also a prerequisite for several other operations, like database migration and upgrading the dSource after upgrade of the
associated data source.

Procedure
1. Click Manage.
2. Select Databases.
3. Click My Databases.
4. Select the dSource you want to disable.
5. On the back of the dSource card, move the slider control from Enabled to Disabled.
6. Click Yes to acknowledge the warning.
When you are ready to enable the dSource again, move the slider control from Disabled to Enabled, and the dSource will continue to function as
it did previously.

625

Delphix User Guide 2016 Delphix

Advanced Data Management Settings for DB2 dSources

Accessing Data Management Settings
Retention Policies
Benefits of Longer Retention
This topic describes advanced data management settings for dSources.
When linking a dSource, you can use custom data management settings to improve overall performance and match the needs of your specific
server and data environment. If no specific settings are required, leverage default data management settings.

Accessing Data Management Settings

There are three ways to set or modify data management settings for dSources:
1. During the dSource linking process, click Advanced in the Data Management panel of the Add dSource wizard.
2. On the back of the dSource card, click the field next to Retention Policy under Data Management. Click the Edit icon.
For SnapSync and Retention policies, click the policy name. This will open the Policy Management screen.
3. Select Manage > Policies in the top menu bar.
This will open the Policy Management screen. Select the policy for the dSource you want to modify, and click Modify.
For more information, see Creating Custom Policies and Creating Policy Templates.

Retention Policies
Retention policies define the length of time Delphix Engine retains snapshots within its storage. To support longer retention times, you may need
to allocate more storage to the Delphix Engine. The retention policy in combination with the SnapSync policy can have a significant impact on
the performance and storage consumption of the Delphix Engine.

Benefits of Longer Retention

With increased retention time for snapshots and logs, you allow a longer (older) rollback period for your data.
Common use cases for longer retention include:
SOX compliance
Frequent application changes and development
Caution and controlled progression of data
Reduction of project risk
Restore to older snapshots

626

Delphix User Guide 2016 Delphix

Using Pre- and Post-Scripts with DB2 dSources

Related Links
This topic describes the use of pre- and post-scripts with dSources.
For each script, you can add the script path and its arguments when linking a dSource in one of two ways. Either:
During the Add dSource wizard process, in the Data Management screen, click Advanced.
or
On the back of the dSource card, click the Pencil icon next to the Pre Script and Post Script fields.
To update pre- and post-script information:
1. Flip over the dSource card.
2. Click on the Pencil icon next to the Pre Script and Post Script fields.
3. When finished, click the check mark icon.
Note that pre-scripts are executed before the SnapSync policy, and if the script fails, SnapSync will fail as well. In the case of a post-script, the
script will execute after SnapSync is complete. If a post-script fails, you will see an error message.

Related Links
Customizing DB2 Management with Hook Operations

627

Delphix User Guide 2016 Delphix

Provisioning from a Replicated DB2 dSource

This topic describes how to provision from a replicated dSource or virtual database (VDB). The process for provisioning from replicated objects is
the same as the typical VDB provisioning process, except that first you need to select the replica containing the replicated object.
Prerequisites
Procedure
Post-Requisites

Prerequisites
You must have replicated a dSource or a VDB to the target host, as described in Replication Overview.
You must have added a compatible target environment on the target host.

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Click My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB you want to provision.
6. The provisioning process is now identical to the process for provisioning standard objects.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

628

Delphix User Guide 2016 Delphix

Provisioning VDBs from DB2 dSources

These topics describe special tasks and concepts for provisioning VDBs from SQL Server dSources.
Provisioning DB2 VDBs: An Overview
Provisioning a DB2 VDB
Database Permissions for Provisioned DB2 VDBs
Upgrading DB2 VDBs
Rewinding a DB2 VDB

629

Delphix User Guide 2016 Delphix

Provisioning DB2 VDBs: An Overview

This topic describes the basic concepts involved with provisioning VDBs from DB2.
A dSource is a virtualized representation of a physical or logical source database. As a virtual representation, it cannot be accessed or
manipulated using database tools. Instead, you must create a Virtual Database (VDB) from a dSource snapshot. A VDB is an independent,
writeable copy of a dSource snapshot. You can also create VDBs from other VDBs. Once a VDB has been provisioned to a target environment,
you can also implement a snapshot policy for that VDB, to capture changes within it as if it were any other logical or physical database.
For an overview of the high-level components involved in provisioning a DB2 VDB refer to Setting Up DB2 Environments: An Overview.
Snapshots accumulate over time, and are available when you select the dSource in the My Databases panel of the Delphix Admin application.
Each snapshot is represented as a card that includes information about the source instance, operating system and time stamp. You can scroll
through these cards to select the one you want, or enter a date and time to search for a specific snapshot.
Once a VDB has been provisioned, you can also take snapshots of it. As with the dSource snapshots, you can find these when you select the
VDB in the My Databases panel. You can then provision additional VDBs from these VDB snapshots.

Related Links
Setting Up DB2 Environments: An Overview
Provisioning a DB2 VDB
Database Permissions for Provisioned DB2 VDBs

630

Delphix User Guide 2016 Delphix

Provisioning a DB2 VDB

This topic describes how to provision a virtual database (VDB) from a SQL Server dSource.

Prerequisites
You will need to have linked a dSource from a staging instance, as described in Linking a DB2 dSource, or have created a VDB from
which you want to provision another VDB
You should have set up the DB2 target environment with necessary requirements as described in Requirements for DB2 Hosts and
Databases
Make sure you have the required Instance Owner permissions on the target instance and environment as described in Managing DB2
Users and Instance Owners
The method for Database Permissions for Provisioned DB2 VDBs is decided before the provisioning
You can take a new snapshot of the dSource by clicking the Camera icon on the dSource card. Once the snapshot is complete you can
provision a new VDB from it.

Procedure
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource.
6. Select a snapshot you wish to provision from.
7. Click Provision to open Provision VDB panel.
8. Select a target environment from the left pane.
9. Select an Installation to use from the dropdown list of available DB2 instances on that environment.
10. Set the Environment User to be the Instance Owner.
11. If the target machine has lower memory than the staging instance, set the BufferPool Override value in number of pages. If this is not
set and the target machine does not have enough memory the target server may crash. If the value is set to zero then the existing value
of that instance will not be overridden.

12. Click Next.

13. Select a Target Group for the VDB.
Click the green Plus icon to add a new group, if necessary.
14. Select a Snapshot Policy for the VDB.
Click the green Plus icon to create a new policy, if necessary.
15. Click Next.
16. Specify any desired hook operations. For details on hook operations, refer to Customizing DB2 Management with Hook Operations.
17. Click Next.
18.
631

Delphix User Guide 2016 Delphix

18. Review the Provisioning Configuration and Data Management information.

19. Click Finish.
When provisioning starts, you can review the progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the VDB will be included in the group you designated, and listed in the Databases panel. If you select the
VDB in the Databases panel and click the Open icon, you can view its card, which contains information about the database and its Data
Management settings.
20. Once the VDB provisioning has successfully completed, if the source and target instance ids are not the same, you may want to grant
secadm and dbadm on the database to the target instance id. Refer to Database Permissions for Provisioned DB2 VDBs for more
information.

Related Links
Linking a DB2 dSource
Provisioning DB2 VDBs: An Overview
Database Permissions for Provisioned DB2 VDBs
Customizing DB2 Management with Hook Operations

632

Delphix User Guide 2016 Delphix

Database Permissions for Provisioned DB2 VDBs

This topic describes the database permissions on provisioned DB2 virtual instances
DB2 Authentication
LDAP Authentication
OS Authentication
Generic Accounts
Instance Owner Usage
Related Topics

DB2 Authentication
Authentication is the process of validating a supplied user ID and password using a security mechanism. User and group authentication is
managed in a facility external to DB2 LUW, such as the operating system, a domain controller, or a Kerberos security system. This is different
from other database management systems (DBMSs), such as Oracle and SQL Server, where user accounts may be defined and authenticated in
the database itself, as well as in an external facility such as the operating system.
Any time a user ID and password is explicitly provided to DB2 LUW as part of an instance attachment or database connection request, DB2
attempts to authenticate that user ID and password using this external security facility. If no user ID or password is provided with the request, DB2
implicitly uses the user ID and password that were used to log in to the workstation where the request originated. More information of DB2
authentication and authorization is available via IBM documentation.
Delphix DB2 authentication
Delphix for DB2 requires that that the staging and target hosts must already have the necessary users and authentication systems
created/installed on them. Delphix will neither create users nor change database passwords as part of the provisioning process.
While the terminology used within the Delphix GUI refers to a VDB, the ingest, snapshot and provisioning process for DB2 on Delphix always
occurs on the instance level. Thus when a virtual DB2 instance is provisioned by Delphix, it contains all the DB2 databases that were in the
source instance with the identical user permissions as they had on the source. This means that if the target instance name is different from the
source instance name then that instance owner will NOT have DBADM or SECADM permissions unless they were specifically granted to that
instance owner on the source instance. The instance owner will however always have SYSADM permissions on all databases in the instance.

LDAP Authentication
If your DB2 instances and applications use LDAP authentication then they will work seamlessly as long as LDAP had been configured on the VDB
Target Instance.

OS Authentication
If your DB2 instances and applications are using OS authentication then it is important to ensure that the relevant OS accounts exist on the target
machine.

Generic Accounts
If the DB2 applications are using generic (non-instance owner) accounts, they will then be able to continue using them as long as those OS
accounts exist on the host machine. It is important to note that the passwords for the same account may be different on different hosts, or if they
use different LDAP servers (i.e. prod vs dev ldap servers).

Instance Owner Usage

If the DB2 applications typically use the instance owner accounts to access data then it is important to note that if the new instance name is
different from the source instance name then that instance owner will NOT have DBADM or SECADM permissions in the VDB instance and may
not be able to read and write data. In such a case there are three possible workarounds:
1. Connect to the databases as the source instance owner. This requires that the target host have a unix account with the same name as
the source instance.
2. Grant the necessary permissions to the VDB instance owner on the source instance before taking the snapshot that is to be provisioned.
3. Grant the permissions to a known "delphix" user on the source instance and then use that account to grant the permissions to the target
VDB instance after provisioning.

Related Topics

633

Delphix User Guide 2016 Delphix

Managing DB2 Instances

Managing DB2 Users and Instance Owners
Provisioning VDBs from DB2 dSources

634

Delphix User Guide 2016 Delphix

Upgrading DB2 VDBs

This topic describes how to upgrade a DB2 VDB to a higher version of DB2.

Procedure for VDB In-Place Upgrade

1. Remove any VDB Refresh Policy assigned to the VDB.
2. Upgrade the target DB2 instance.
3. Refresh the target environment.

635

Delphix User Guide 2016 Delphix

Rewinding a DB2 VDB

This topic describes the procedure for rewinding a VDB.
Rewinding a VDB rolls it back to a previous point in its TimeFlow and re-provisions the VDB. The VDB will no longer contain changes after the
rewind point.
Although the VDB no longer contains changes after the rewind point, the rolled over Snapshots and TimeFlow still remain in Delphix
and are accessible through the Command Line Interface (CLI). See the topic CLI Cookbook: Rolling Forward a VDB for instructions
on how to use these snapshots to refresh a VDB to one of its later states after it has been rewound.

Prerequisites
To rewind a VDB, you must have the following permissions:
Auditor permissions on the dSource associated with the VDB
Owner permissions on the VDB itself
You do NOT need owner permissions for the group that contains the VDB. A user with Delphix Admin credentials can perform a VDB Rewind on
any VDB in the system.

Procedure
1. Login to the Delphix Admin application.
2. Under Databases, select the VDB you want to rewind.
3. Select the rewind point as a snapshot or a point in time.
4. Click Rewind.
5. If you want to use login credentials on the target environment other than those associated with the environment user, click Provide
Privileged Credentials.
6. Click Yes to confirm.

You can use TimeFlow bookmarks as the rewind point when using the CLI. Bookmarks can be useful to:
Mark where to rewind to - before starting a batch job on a VDB for example.
Provide a semantic point to revert back to in case the chosen rewind point turns out to be incorrect.
For a CLI example using a TimeFlow bookmark, see CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark.

Video

636

Delphix User Guide 2016 Delphix

Customizing DB2 Management with Hook Operations

Hook operations allow you to execute an ordered list of custom operations at select hook points in linking, provisioning and virtual dataset
management. For details on the types of operations that are available, see children of this page.
dSource Hooks
Virtual Dataset Hooks
Setting Hook Operations
Setting Hook Operations through the Delphix Admin Application
Setting Hook Operations through the CLI
Example of Editing Hook Operations through the CLI
Hook Operation Templates
Creating a Hook Operation Template
Importing a Hook Operation Template
Exporting a Hook Operation Template

dSource Hooks
Hook

Description

Pre-Sync

Operations performed before a sync.

These operations can quiesce data to be captured during the sync, or stop processes that may interfere with the sync.

Post-Sync

Operations performed after a sync. This hook will run regardless of the success of the sync or Pre-Sync hook operations.
These operations can undo any changes made by the Pre-Sync hook.

Virtual Dataset Hooks

Hook

Description

Configure
Clone

Operations performed after initial provision or after a refresh. This hook will run after the virtual dataset has been started.
During a refresh, this hook will run before the Post-Refresh hook.

Pre-Refresh

Operations performed before a refresh.

These operations can cache data from the virtual dataset to be restored after the refresh completes.

Post-Refresh

Operations performed after a refresh. During a refresh, this hook will run after the Configure Clone hook. This hook will not run
if the refresh or Pre-Refresh hook operations fail.
These operations can restore cached data after the refresh completes.

Pre-Rewind

Operations performed before a rewind.

These operations can cache data from the virtual dataset to be restored after the rewind completes.

Post-Rewind

Operations performed after a rewind. This hook will not run if the rewind or Pre-Rewind hook operations fail.
These operations can restore cached data after the rewind completes.

Pre-Snapshot

Operations performed before a snapshot.

These operations can quiesce data to be captured during the snapshot, or stop processes that may interfere with the
snapshot.

Post-Snapshot

Operations performed after a snapshot. This hook will run regardless of the success of the snapshot or Pre-Snapshot hook
operations.
These operations can undo any changes made by the Pre-Snapshot hook.

Operation Failure
If a hook operation fails, it will fail the entire hook: no further operations within the failed hook will be run.

Setting Hook Operations

637

Delphix User Guide 2016 Delphix

You can construct hook operation lists through the Delphix Admin application or the command line interface (CLI). You can either define the
operation lists as part of the linking or provisioning process or edit them on dSources or virtual datasets that already exist.

Setting Hook Operations through the Delphix Admin Application

To specify hook operations during linking or provisioning, navigate to the Hooks tab of the Linking Wizard or Provision Wizard.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation or click Import to load a hook operation template.
4. Click the text area and edit the contents of the operation.
5. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
6. To remove an operation from the list, click the Trash icon on the operation.
7. When you have set all hook operations, click Next to continue with the provisioning process.
To edit hook operations on an already-existing dSource or virtual dataset, navigate to the Hooks tab on the back of the dSource card or virtual
dataset card.
1. Select the hook to edit.
2. The current operations at this hook will be displayed. To edit this list of operations, click the Pencil icon in the top right-hand corner of the
card.
3. Click the Plus icon to add a new operation.
4. Select the type of operation or click Import to load a hook operation template.
5. Click the text area and edit the contents of the operation.
6. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
7. To remove an operation from the list, click the Trash icon on the operation.
8. When you have set all hook operations, click Check to save the changes.

Setting Hook Operations through the CLI

To specify hook operations during linking, edit the relevant hook's array of operations defined on the LinkingParameters > Source >
Operations object.
To specify hook operations during provisioning, edit the relevant hook's array of operations defined on the ProvisionParameters > Source
> Operations object.
To edit hook operations on an already-created dSource, edit the relevant hook's array of operations defined on the Source > Operations obje
ct.
To edit hook operations on an already-created virtual dataset, edit the relevant hook's array of operations defined on the Source > Operation
s object.
For more information about these CLI objects, see the LinkedSourceOperations, VirtualSourceOperations, RunCommandOnSourceOp
eration, and RunExpectOnSourceOperation API documentation in the Help menu of the Delphix Admin application.

Example of Editing Hook Operations through the CLI

1. Navigate to the relevant source's VirtualSourceOperations object.
2. Select a hook to edit.
delphix> source
delphix source> select "pomme"
delphix source "pomme"> update
delphix source "pomme" update *> edit operations
delphix source "pomme" update operations *> edit postRefresh
3. Add an operation at index 0.
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
Properties
type: RunCommandOnSourceOperation (*)
command: echo Refresh completed. (*)
delphix source "pomme" update operations postRefresh

638

*> add
0 *> set type=RunCommandOnSourceOperation
0 *> set command="echo Refresh completed."
0 *> ls

0 *> commit

Delphix User Guide 2016 Delphix

4. Add another operation at index 1 and then delete it.

delphix
delphix
delphix
delphix
delphix
delphix

source
source
source
source
source
source

"pomme"
"pomme"
"pomme"
"pomme"
"pomme"
"pomme"

update
update
update
update
update
update

operations
operations
operations
operations
operations
operations

postRefresh
postRefresh
postRefresh
postRefresh
postRefresh
postRefresh

*> add
1 *> set type=RunCommandOnSourceOperation
1 *> set command="echo Refresh completed."
1 *> back
*> unset 1
*> commit

Hook Operation Templates

You can use templates to store commonly used operations, which allows you to avoid repeated work when an operation is applicable to more
than a single dSource or virtual dataset. You manage templates through the Delphix Admin application.
Hook Operations Templates Not Available via CLI
Hook operation templates cannot be fully utilized from the CLI. Manage and use hook operations through the Delphix Admin applicatio
n.

Creating a Hook Operation Template

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Operation Templates.
4. Click the Plus icon to add a new operation template.
5. Enter a Name for the template.
6. Select an operation Type.
7. Enter a Description detailing what the operation does or how to use it.
8. Enter operation Contents to implement the operation partially or fully.
9. Click Create.

Importing a Hook Operation Template

To import a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Click Import.
4. Select the template to import.
5. Click Import.
6. When you have set all hook operations, click Check to save the changes.

Exporting a Hook Operation Template

To export a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation.
4. Click the text area and edit the contents of the operation.
5. Click Export.
6. Enter a Name for the template.
7. Enter a Description detailing what the operation does or how to use it.
8. Click Create.

639

Delphix User Guide 2016 Delphix

DB2 Hook Operation Notes

Shell Operations
RunCommand Operation
RunBash Operation
Shell Operation Tips
Other Operations
RunExpect Operation
DB2 Environment Variables
dSource Environment Variables
VDB Environment Variables

Shell Operations
RunCommand Operation

The RunCommand operation runs a shell command on a Unix environment using whatever binary is available at /bin/sh. The environment user
runs this shell command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the shell command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Examples of RunCommand Operations

You can input the full command contents into the RunCommand operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
if test -d "$remove_dir"; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
If a script already exists on the remote environment and is executable by the environment user, the RunCommand operation can execute this
script directly.

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh "$ARG_ENVIRONMENT_VARIABLE" "second

argument in double quotes" 'third argument in single quotes'
RunBash Operation

The RunBash operation runs a Bash command on a Unix environment using a bash binary provided by the Delphix Engine.The environment user
runs this Bash command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the Bash command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of RunBash Operations

You can input the full command contents into the RunBash operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
# Bashisms are safe here!
if [[ -d "$remove_dir" ]]; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
Shell Operation Tips
Using nohup

640

Delphix User Guide 2016 Delphix

You can use the nohup command and process backgrounding from resource in order to "detach" a process from the Delphix Engine. However, if
you use nohup and process backgrounding, you MUST redirect stdout and stderr.
Unless you explicitly tell the shell to redirect stdout and stderr in your command or script, the Delphix Engine will keep its connection to the
remote environment open while the process is writing to either stdout or stderr . Redirection ensures that the Delphix Engine will see no more
output and thus not block waiting for the process to finish.
For example, imagine having your RunCommand operation background a long-running Python process. Below are the bad and good ways to do
this.
Bad Examples
nohup
nohup
nohup
nohup

python
python
python
python

file.py
file.py
file.py
file.py

& # no redirection
2>&1 & # stdout is not redirected
1>/dev/null & # stderr is not redirected
2>/dev/null & # stdout is not redirected

Good Examples
nohup python file.py 1>/dev/null 2>&1 & # both stdout and stderr redirected, Delphix Engine will not
block

Other Operations
RunExpect Operation

The RunExpect operation executes an Expect script on a Unix environment. The Expect utility provides a scripting language that makes it easy to
automate interactions with programs which normally can only be used interactively, such as ssh. The Delphix Engine includes a
platform-independent implementation of a subset of the full Expect functionality.
The script is run on the remote environment as the environment user from their home directory. The Delphix Engine captures and logs all output
of the script. If the operation fails, the output is displayed in the Delphix Admin application and CLI to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunExpect Operation

Start an ssh session while interactively providing the user's password.

spawn ssh [email protected]

expect {
-re {Password: } {
send "${env(PASSWORD_ENVIRONMENT_VARIABLE)}\n"
}
timeout {
puts "Timed out waiting for password prompt."
exit 1
}
}
exit 0
DB2 Environment Variables
Operations that run user-provided scripts have access to environment variables. For operations associated with specific dSources or virtual
databases (VDBs), the Delphix Engine will always set environment variables so that the user-provided operations can use them to access the
dSource or VDB.
dSource Environment Variables

Environment Variable

Description

DLPX_DATA_DIRECTORY

Path where staging database is mounted

VDB Environment Variables

641

Delphix User Guide 2016 Delphix

Environment Variable

Description

DLPX_DATA_DIRECTORY

Path where virtual database is mounted

642

Delphix User Guide 2016 Delphix

_Data Backup and Recovery

These topics describe how to use the Delphix Engine for data backup and recovery, including use of the Replication and Virtual to Physical (V2P)
features.
Backup and Recovery Strategies for the Delphix Engine
Backup and Recovery Requirements
Deployment Architecture
Mapping Requirements to Solutions
Backup Solution Implementation
Replication
Replication Overview
Replication Use Cases
Replication User Interface
Configuring Replication
Enabling Replicated Objects
Replicas and Failover
Failing Over a Replica
Updating Replication User Credentials from Previous Versions
Provisioning from Replicated Data Sources or VDBs
Selective Data Distribution
Selective Data Distribution Overview
Selective Data Distribution Use Cases
Selective Data Distribution User Interface
Configuring Selective Data Distribution
Selective Data Distribution and Failover
V2P: Virtual to Physical
Virtual to Physical: An Overview
V2P with an Oracle VDB
Move an Oracle VDB to a Physical ASM or Exadata Database
V2P with a SQL Server VDB
V2P with a PostgreSQL dSource or VDB
V2P with an SAP ASE dSource or VDB This topic describes the procedure for exporting a virtual database (VDB)

to a physical one, also known as V2P.

Manually Recovering a Database after V2P
Customizing Target Directory Structure for Database Export
V2P with Unstructured Files
V2P with a MySQL VDB

643

Delphix User Guide 2016 Delphix

Backup and Recovery Strategies for the Delphix Engine

These topics describe backup and recovery options for Delphix Engine.
As a software virtual appliance, Delphix leverages features of the storage, hypervisor, and appliance infrastructure to provide for recovery in the
event of failure. These topics walk through the process of evaluating requirements and defining a solution. This process depends on requirements
and features of the environment in which Delphix Engine is deployed.
Backup and Recovery Requirements
Deployment Architecture
Mapping Requirements to Solutions
Backup Solution Implementation

644

Delphix User Guide 2016 Delphix

Backup and Recovery Requirements

This topic describes determining requirements around infrastructure failure modes and recovery.
Before devising a strategy, you must first have a set of requirements to evaluate possible solutions. What failures are you trying to protect against,
and what are your recovery goals in the event of failure?

Failure Points
Before devising a strategy, you must first have a set of requirements by which the resulting solution can be evaluated. What failures are you trying
to protect against, and what are your recovery goals in the event of failure?

Physical Server Failure

The Delphix Engine runs within the VMware ESX hypervisor, which itself is running on a physical machine. Failure of that physical machine will
affect the Delphix Engine, as well as any other virtual machines running on that server. The failure is isolated to that particular server, and is not
the result of a larger, site-wide failure.
Recommendation: ESX Clustering

Storage Failure
The Delphix Engine uses LUNs from a storage array provided through the VMware hypervisor. The storage array may have redundant disks
and/or controllers to protect against single points of failure within the array. However, the Delphix Engine can still be affected by a failure of the
entire array, the SAN path between the Delphix Engine and the array, or by a failure of the LUNs in the array that are assigned to the Delphix
Engine.
Recommendation: Replication

Site Failure
When an entire site or datacenter goes down, all servers, storage, and infrastructure are lost. This will affect not only the Delphix Engine, but any
production databases and target servers in the datacenter.
Recommendation: Replication

Administrative Error
If an administrator mistakenly deletes a VDB or takes some other irreversible action, there is no method of recovery built into the Delphix Engine.
Recommendation: Snapshots

Recovery Objectives
Once infrastructure fails, some amount of work is required to restore the Delphix Engine to an operational state. Clients wont have access to the
Delphix Engine during this time, and the point to which the system is recovered is dependent on the mechanism being used. These qualitative
aspects of recovery can be captured by the following metrics. As these metrics are often directly associated with cost, it is important to think not
just about the desired metrics, but also the minimum viable goals.

Recovery Point Objective (RPO)

The RPO is the acceptable amount of data that can be lost in the event of a failure. For example, if backups are taken once a day, then at most
24 hours of data will be lost if the system fails immediately before a regularly scheduled backup.

Recovery Time Objective (RTO)

The RTO is the time required to restore the system to an operational state after a failure. For example, a recovery may require restoring data from
from a backup, followed by some number of manual steps to recreate the configuration in the new system. RTO is equivalent to the downtime
experienced by clients.

645

Delphix User Guide 2016 Delphix

Recovery Time Granularity (RTG)

The granularity of the recovery time is the specificity by which you can select a particular point in time from the past to restore the system. For
example, VM snapshots taken every hour provide no way to restore to a point in time between those snapshots.

646

Delphix User Guide 2016 Delphix

Deployment Architecture
This topic describes components of the Delphix deployment architecture.
Delphix operates in a virtual environment with several core systems working in concert, each with its own set of capabilities. Understanding this
architecture is critical in evaluating how solutions can be applied across the components, and the tradeoffs involved.

Architectural Components
This diagram illustrates Delphixs recommended best practices for deploying the Delphix Engine in a VMware environment:

This architecture is designed to isolate I/O traffic to individual LUNs while using the most commonly deployed VMware components. In this
example each VMDK file is placed in a separate VMFS volume. Each volume is exported to every node in the ESX cluster, allowing the Delphix
Engine to run on any physical host in the cluster.

Fault Recovery Features

Across the recommended deployment architecture there are three key components in play: Delphix Engine, VMware, and storage. Each of these
provides different failure handling capabilities, which can be roughly grouped into the following areas.

Server Clustering
Clustering provides a standby server that can take over in the event of failure. A given clustering solution may or may not provide high availability
guarantees, though all provide failover capabilities, provided that an identical passive system is available.

Snapshots
Snapshots preserve a point-in-time copy of data that can be used later for rollback or to create writable copies. Creating a snapshot is typically
low cost in terms of space and time. Because they use the storage allocated to the array, snapshots restore quickly, but they do not protect
against failures of the array.

647

Delphix User Guide 2016 Delphix

Replication
Data replication works by sending a series of updates from one system to another in order to recreate the same data remotely. This stream can
be synchronous, but due to performance considerations is typically asynchronous, where some data loss is acceptable. Replication has many of
the same benefits of backup, in that the data is transferred to a different fault domain, but has superior recovery time given that the data is
maintained within an online system. The main drawback of replication is that the data is always current - any logical data error in the primary
system is also propagated to the remote target. The impact of such a failure is less when replication is combined with snapshots, as is often the
case with continuous data protection (CDP) solutions.

Backup
Like snapshots, backup technologies preserve a point-in-time copy of a storage dataset, but then move that copy to offline storage. Depending on
the system, both full and incremental backups may be supported, and the backup images may or may not be consistent. Backup has the
advantage that the data itself is stored outside the original fault domain, but comes at high cost in terms of complexity, additional infrastructure,
and recovery time.

648

Delphix User Guide 2016 Delphix

Mapping Requirements to Solutions

This topic describes how to map from backup and recovery requirements to solutions.
With requirements and detailed knowledge of the deployment architecture, we can map to solutions tailored for the features provided by the
underlying infrastructure.

Feature Capabilities
Based on these failure points and recovery features, you can use the following table to map requirements to architectural components: VMware
(V), Delphix (D), or storage (S). This can drive implementation based on infrastructure capabilities and recovery objectives.
Fault Recovery Features
Failure Point

Clustering Snapshots Replication Backup

Server Failure

VSD

Storage Failure

VSD

VS

Site Failure

VSD

VS

Administrative Error

VS

VS

Recovery Point Objective (RPO)

Feature

Time

Description

Clustering

Zero

All changes committed to disk are automatically propagated to the new server. Any pending changes in
memory are lost.

Replication

Near zero

Most solutions offer scheduled replication, but many can offer continuous replication with near-zero data loss.

Snapshots

Snapshot period
(for example,
one hour)

Given their relatively low cost, snapshots tend to be taken at a higher frequency than a traditional backup
schedule.

Backup

Backup period
(for example,
one day)

Backup policies can be configured in a variety of ways, but even with incremental backups, most
deployments operate no more frequently than once a day because of the cost of full backups, and the impact
of incremental backups on recovery time.

Recovery Time Objective (RTO)

Feature

Time

Description

Clustering

Near
zero

VM clustering with the Delphix Engine provides near zero downtime in the event of failure, but clients may be briefly
paused or interrupted.

Replication

15
minutes

The target side environment is kept in hot standby mode, so it is relatively quick to switch over to the target
environment. Depending on the scope of the failure, however, some configuration information may need to be
changed on the target side prior to enabling operation.

Snapshots

15
minutes

The Delphix Engine can be rolled back to a previous state. Changes made to systems external to the Delphix Engine
(for example, deleting a VDB) can cause inconsistencies after rollback.

Backup

Hours
or days

Restoring a full backup can be very time consuming. In addition to having to read, transfer, and write all of the data,
the same process will need to be run for each incremental backup to reach the objective point.

Recovery Time Granularity

Feature

Granularity

Description

Clustering

None

Only the current system state can be recovered.

Replication

None

Only the nearest replicated state can be recovered, unless combined with snapshots.

649

Delphix User Guide 2016 Delphix

Snapshots

Snapshot period (for example, one hour)

Determined by the snapshot schedule.

Backup

Backup period (for example, one day)

Determined by the backup schedule.

650

Delphix User Guide 2016 Delphix

Backup Solution Implementation

This topic describes tradeoffs involved with backup and recovery solutions.
With the exception of clustering, solutions can be implemented using features at both the storage and hypervisor layer. Choosing the right
technology requires understanding both your requirements and what infrastructure is in use in your environment. The following sections outline
some basic choices and the tradeoffs involved.

Clustering
VMware vSphere high availability provides the ability to have a VM configuration shared between multiple physical ESX servers. Once the
storage has been configured on all physical servers, any server can run the Delphix Engine VM. This allows ESX clusters to survive physical
server failure. In the event of failure, the VM is started on a different server, and appears to clients as an unexpected reboot with non-zero but
minimal downtime. Depending on the length of the outage, this may cause a short pause in I/O and database activity, but longer outages can
trigger timeouts at the protocol and database layers that result in I/O and query errors. Such long outages are unlikely to occur in a properly
configured environment.
Automatic detection of failure in a HA environment does not work in all circumstances, and there are cases where the host, storage, or network
can hang such that clients are deprived access, but the systems continue to appear functional. In these cases, a manual failover of the systems
may be required.
When configuring a cluster, it is important to provide standby infrastructure with equivalent resources and performance characteristics.
Asymmetric performance capabilities can lead to poor performance in the event of a failover. In the worst case of an over-provisioned server, this
can cause widespread workload failure and inability to meet performance SLAs.

Snapshots
VMware provides storage-agnostic snapshots that are managed through the VMware Snapshot Manager. Use of VMware snapshots can,
however, cause debilitating performance problems for write-heavy workloads due to the need to manage snapshot redo-log metadata. In order to
provide an alternative snapshot implementation, while retaining the existing management infrastructure, VMware has created an API to allow
storage vendors to supply their own snapshot implementation. This is only supported in ESX 5.1. Furthermore, the array must support the the vSt
orage APIs. Consult the VMware documentation for supported storage solutions and the performance and management implications.
Storage-based snapshots, by virtue of being implemented natively in the storage array, typically do not suffer from such performance problems,
and are preferred over VMware snapshots when available. When managing storage-based snapshots, it is critical that all LUNs backing a single
VM be part of the same consistency group. Consistency groups provide write order consistency across multiple LUNs and allow snapshots to be
taken at the same point in time across the LUNs. This must include all VM configuration, system VMDKs, and VMDKs that hold the dSources and
VDBs. Each storage vendor presents consistency groups in a different fashion; consult your storage vendor documentation for information on how
to configure and manage snapshots across multiple LUNs.
In the event of a snapshot recovery becoming required, ensure that the Delphix Engine VM is powered off for the duration of the snapshot
recovery. Failure to do so can lead to filesystem corruption as you're changing blocks underneath a running system.

Replication
Site Recovery Manager (SRM) is a VMware product that provides replication and failover of virtual machines within a vSphere environment. It is
primarily an orchestration framework, with the actual data replication performed by a native VMware implementation, or by the storage array
through a storage replication adapter (SRA). A list of supported SRAs can be found in the VMware documentation. There is some performance
overhead in the native solution, but not of the same magnitude as the VMware snapshot impact. SRAs provide better performance, but require
that the same storage vendor be used as both source and target, and require resynchronization when migrating between storage vendors.
Storage-based replication can also be used in the absence of SRM, though this will require manual coordination when re-configuring and starting
up VMs after failover. The VM configuration, as well as the storage configuration within ESX, will have to be recreated using the replicated
storage.
The Delphix Engine also provides native replication within Delphix. This has the following benefits:
The target system is online and active
VDBs can be provisioned on the target from replicated objects
A subset of objects can be replicated
On failover, the objects are started in a disabled state. This allows configuration to be adjusted to reflect the target environment prior to
triggering policy-driven actions.
Multiple sources can be replicated to a single target
Note that the Delphix Engine currently only replicates data objects (dSources and VDBs) and environments (source and target services). It does
not replicate system configuration, such as users and policies. This provides more flexibility when mapping between disparate environments, but
requires additional work when instantiating an identical copy of a system after failover.

651

Delphix User Guide 2016 Delphix

Backup
There is a large ecosystem of storage and VM-based backup tools, each with its own particular advantages and limitations. VMware provides Dat
a Protector , but there are size limitations (linked to a maximum of 2TB of deduped data) that make it impractical for most Delphix Engine
deployments. Most third-party backup products, such as Symantec NetBackup, EMC Networker, and IBM Tivoli Storage Manager, have solutions
designed specifically for backup of virtual machines. Because the Delphx Engine is packaged as an appliance, it is not possible to install third
party backup agents. However, any existing solution that can back up virtual machines without the need for an agent on the system should be
applicable to Delphix as well. Check with your preferred backup vendor to understand what capabilities exist.
Some storage vendors also provide native backup of LUNs. Backup at the storage layer reduces overhead by avoiding data movement across the
network, but loses some flexibility by not operating within the VMware infrastructure. For example, recreating the VM storage configuration from
restored LUNs is a manual process when using storage based recovery.

652

Delphix User Guide 2016 Delphix

Replication
These topics describe concepts and procedures for replicating data from one Delphix Engine to another.
Replication Overview
Replication Use Cases
Replication User Interface
Configuring Replication
Enabling Replicated Objects
Replicas and Failover
Failing Over a Replica
Updating Replication User Credentials from Previous Versions
Provisioning from Replicated Data Sources or VDBs

653

Delphix User Guide 2016 Delphix

Replication Overview
Table of Contents

Replication Overview
Delphix allows data objects to be replicated between Delphix Engines. These engines must be running identical Delphix versions, but otherwise
they can be asymmetric in terms of engine configuration. In the event of a failure that destroys the source engine, you can bring up the target
engine in a state matching that of the source. In addition, you can provision VDBs from replicated objects, allowing for geographical distribution of
data and remote provisioning.
Replication can be run ad hoc, but it is typically run according to a predefined schedule. After the initial update, each subsequent update sends
only the changes incurred since the previous update. Replication does not provide synchronous semantics, which would otherwise guarantee that
all data is preserved on the target engine. When there is a failover to a replication target, some data is lost, equivalent to the last time a replication
update was sent.
Replication is not generally suited for high-availability configurations where rapid failover (and failback) is a requirement. Failing over a replication
target requires a non-trivial amount of time and is a one-way operation; to fail back requires replicating all data back to the original source. For
cases where high availability is necessary, it is best to leverage features of the underlying hypervisor or storage platform. See the topics under Ba
ckup and Recovery Strategies for the Delphix Engine for more information on how to evaluate the use of Delphix Engine replication for your
data recovery requirements.)

Replication Features
As virtual appliances, it is possible to backup, restore, replicate, and migrate data objects between Delphix Engines using features of VMWare
and the underlying storage infrastructure. Data objects include groups, dSources, VDBs, Jet Stream data templates and data containers, and
associated dependencies. In addition to the replication capabilities provided by this infrastructure, native Delphix Engine replication provides
further capabilities, such as the ability to replicate a subset of objects, replicate multiple sources to a single target, and provision VDBs from
replicated dSources and VDBs without affecting ongoing updates. The topics under Backup and Recovery Strategies for the Delphix Engine p
rovide more information on how to evaluate features of the Delphix Engine in relation to your backup and recovery requirements.
Replication is configured on the source Delphix Engine and copies a subset of dSources and VDBs to a target Delphix Engine. It then sends
incremental updates manually or according to a schedule. For more information on configuring replication, see Configuring Replication
You can use replicated dSources and VDBs to provision new VDBs on the target side. You can refresh these VDBs to data sent as part of an
incremental replication update, as long as you do not destroy the parent object on the replication source. For more information, see Provisioning
from a Replicated Data Sources or VDBs.
During replication, replicated dSources and VDBs are maintained in an alternate replica and are not active on the target side. In the event of a
disaster, a failover operation can break the replication relationship. For more information on how to activate replicated objects, see Replicas and
Failover.

Replication Details
When you select objects for replication, the engine will automatically include any dependencies, including parent objects, such as groups, and
data dependencies such as VDB sources. This means that replicating a VDB will automatically include its group, the parent dSource, and the
group of the dSource, as well as any environments associated with those databases. When replicating an entire engine, all environments will be
included. When replicating a database or group, only those environments with the replicated databases are included.
During replication, the Delphix Engine will negotiate an SSL connection with its server peer to use SSL_RSA_WITH_RC4_128_MD5 as the cipher
suite, and TLSv1 as the protocol.
Only database objects and their dependencies are copied as part of a backup or replication operation, including:
dSources
VDBs
Groups
Jetstream Data Templates and Data Containers
Environments
Environment configuration (users, database instances, and installations)
The following objects are not copied as part of a backup or replication operation:
Users and roles
Policies
VDB (init.ora) configuration templates
Events and faults

654

Delphix User Guide 2016 Delphix

Job history
System services settings, such as SMTP
After failover, these settings must be recreated on the target.

Resumable Replication
Resumable replication enhances the current replication feature by allowing you to restart large, time-consuming initial replication or incremental
updates from an intermediate point. A single replication instance can fail for a number of environmental and internal reasons. Previously, when
you restarted a failed replication instance, replication required a full resend of all data transmitted prior to the failure. With resumable replication,
no data is retransmitted. Replication is resumable across machine reboot, stack restart, and network partitions.
For example, suppose a replication profile has already been configured from a source to a target. A large, full send begins between the two that is
expected to take weeks to complete. Halfway through, a power outage at the datacenter that houses the source causes the source machine to go
down and only come back up after a few hours. On startup, the source will detect a replication was ongoing, automatically re-contact the target,
and resume the replication where it left off. In the user interface (UI) on the source, the same replication send job will appear as active and
continue to update its progress. However, in the UI of the target, a new replication receive job will appear but will track its progress as a
percentage of the entire replication.
In 4.1 and earlier releases, the replication component would always clean up after failed jobs to ensure that the Delphix Engine was kept in a
consistent state and that no storage was wasted on unused data. With the addition of resumability, the target and source can choose to retain
partial replication state following a failure to allow future replications to complete from that intermediate point. In the current release, the target and
source will only choose to retain partial replication state following failures that leave them out of network contact with each other for
example, source restart, target restart, or network partition. Once network contact is re-established, the ongoing replication will be automatically
detected and resumed. The resumable replication feature is fully automated and does not require or allow any user intervention.
Replication will not resume after failures that leave the source and target connected. For example, if a storage failure on the target, such as
out-of-space errors, causes a replication to fail, the source and target remain connected. As a result, will conservatively throw away all MDS and
ZFS data associated with the failed replication. Nonetheless, resumable replication would begin during a source reboot, a target reboot and a
network partition.
.

Related Topics
Backup and Recovery Strategies for the Delphix Engine
Replication User Interface
Configuring Replication
Provisioning from Replicated Data Sources or VDBs
Replicas and Failover New

655

Delphix User Guide 2016 Delphix

Replication Use Cases

Replication is a flexible tool that allows for dSources and virtual databases (VDBs) to be moved between Delphix Engines. These topics describe
the ways in which you can use replication to meet different use cases.

Disaster Recovery
Replication is traditionally used to provide recovery in the event of disaster, where a datacenter or site is completely destroyed. Delphix replication
may not be the only recovery solution in this scenario; consult the Backup and Recovery Strategies for the Delphix Engine topic to determine
if it meets your requirements.
In a disaster recovery scenario, the target is kept in a passive state until the source system is lost. At this point, a failover is performed that breaks
subsequent replication updates and activates objects so that they can be managed on the target side.

You can reconfigure environments on the target prior to failover if the infrastructure uses a different network topology or set of systems. Whether
or not this is required depends on the nature of the failure at the primary site. If only the Delphix Engine is affected, and all of the source
databases and target environments are unaffected, then the target can enable dSources and VDBs and reconnect to the original systems. If, on
the other hand, the failure also destroyed the source and target systems, then those environments will have to be adjusted to point to the new
systems on the target side. If there is not a 1:1 mapping, then you can migrate the VDBs to new systems on the target, and you can detach
dSources and attach them to the standby system in the target environment.
Follow the best practices below to simplify failover and meet performance expectations in the event of a disaster:
The environment should be as close to identical when it comes to available resources
Target hosts and systems should exist at the target that match those at the source
The Delphix Engine should be provisioned with identical resources
The network and storage topologies should be the same
A 1:1 relationship between source and targets should be maintained
The target should remain passive and not be actively used for other workloads
Configuration of non-replicated objects, such as policies and users, should be retrieved via the command line interface (CLI) and saved
so that they can be recreated after failover.

656

Delphix User Guide 2016 Delphix

Geographically Distributed Development

The Delphix Engine allows for VDBs to be provisioned from replicated dSources and VDBs, as described in Provisioning from Replicated Data
Sources or VDBs. This allows dSources to be linked in a single central location and geographically distributed so that developers can provision
VDBs remotely without having to sync from the source database in multiple locations.
In this environment, replication is never broken and failover never performed, unless the motivation for distribution is eliminated but remote VDBs
need to be preserved. You can refresh remote VDBs as long as the parent objects continue to exist on the source. If they are deleted, then
remote VDBs will continue to function but cannot be refreshed.

Because there is no failover, this topology can support more complex topologies such as 1-to-many and many-to-1. Chained replication
(replicating from Site A -> Site B -> Site C) is not supported.
For geographical distribution, follow these best practices:
Because each replication stream induces load on the source system:
Minimize the number of simultaneous replication updates
If possible, avoid heavy VDB workloads on the source
Provision only from sources that are effectively permanent. Otherwise, remote VDBs cannot be refreshed once the source is deleted.
Provision additional storage capacity on the target
Remotely provisioned VDBs can consume shared storage on the target even when the parent is deleted on the source

Migration
You can use replication to perform one-time migration of resources from one Delphix Engine to another. While the hypervisor provides tools to
move virtual appliances between physical systems, there are times when migration is necessary, such as:
Migrating between different physical storage
Consolidating or distributing workloads across Delphix Engines
In these cases, replication can be used to copy a subset of objects across asymmetric topologies.

657

Delphix User Guide 2016 Delphix

For migration, follow these best practices:

Send full updates, followed by incremental updates, until the time required for incremental updates meets your downtime window
Disable all objects to be migrated on the source, to ensure that they are not actively changing
Send a final incremental update before failing over the target
After failover, destroy any migrated objects on the source, or the entire engine

658

Delphix User Guide 2016 Delphix

Replication User Interface

Understanding Replication Functionality and User Interface
Understanding Sources for Replication
Understanding Targets for Replication
User Interface Replication Screen
Interacting with the Replication Profiles Section
Interacting with the Create New Replication Profile Section
Interacting with the Replica Section
Getting Started: Working in the Replication User Interface
Configuring Replication Profiles
Viewing and Editing an Existing Replication Profile
Viewing and Editing a Replica
Related Links

Understanding Replication Functionality and User Interface

The replication UI helps users manage replication on both the source and the target. Replication consists of a profile-replica pair. You can view
and edit the profile on the source engine, and view the replica on the target engine.

Understanding Sources for Replication

The Replication Profile section continues to handle the existing functionality but allows for the configuration of multiple replication profiles. This
makes it possible to replicate objects from a single source to multiple targets. Each profile defines the set of data objects and the associated
configuration between a single source and target.

Understanding Targets for Replication

The Replica section shows you the set of all objects in the replica and allows you to initiate failover. As in the old UI, one Delphix Engine can
have multiple received replicas. This means that the engine is the target of multiple sources of replication, or profiles.

User Interface Replication Screen

There are three interconnected sections that have been introduced to make the replication workflow easier. These three sections include the Repl
ication Profile, Create New Replication, and Replica.

Interacting with the Replication Profiles Section

The following screenshot and the descriptions below illustrate the capabilities in the Replication Profiles section. Click the screenshot for an
enlarged view.

659

Delphix User Guide 2016 Delphix

Create Profile Button

Allows you to configure a Replication Profile.
Replication Profiles List
Provides a list of existing replication profiles. Click a profile in this list to view its details.
Received Replicas List
Provides a list of all existing replicas on this Delphix Engine. Click a replica in this list to view its details.
Status Box
Shows the replication status of the selected profile, including:
The result of the most recent or current replication event
Statistics for the replication run such as data transferred, duration, and average throughput
In the top left-hand corner, an icon summarizes the replication status. There are four possible status icons:

Configuration Options
Configuration Options for the selected replication profile. These include:
Description Free text description of the profile
Target Engine The Delphix Engine on the receiving end of this replication pair
Automatic Replication If enabled, shows the frequency and time that regular replication will be run
Traffic options Summarizes the traffic options with which this profile has been configured
Object Selection Tree
Shows all of the objects, such as groups, dSources, VDBs, and Jet Stream data layouts, that you have selected for replication in this
replication profile. If you select Entire Delphix Engine, all objects on the engine will be replicated, and thus the tree is collapsed.
Replicate Now Button
Begins the replication process
Delete Button
Allows you to delete the current profile

Interacting with the Create New Replication Profile Section

1. In the left-hand navigation section, click Create Profile.
2. Enter the name of the replication profile and an optional description.
3. Select Replication Profile as the type.
4. For Target Engine, enter the hostname or IP address for the target Delphix Engine.
5. Enter the username and password of a user who has Delphix Admin-level credentials on the target Delphix Engine. If the username and
password change on the target Delphix Engine, you must update these settings on the source Delphix Engine.
6. By default, automatic replication is disabled, meaning that you must trigger replication updates manually. To enable automatic replication,
click the Enabled checkbox.
7. In the Automatic Replication field, enter the Frequency and Starting Time for replication updates to the target Delphix Engine. Once

660

Delphix User Guide 2016 Delphix

7.
you have entered and saved your replication settings, you will also see an option to trigger replication immediately with the Replicate
Now button.
a. Note : Automatic replication uses Quartz for scheduling. Starting with Delphix version 4.2, the Quartz-formatted string is editable
via the Advanced option. Please refer to the screenshot below:

8. Under Traffic Options, select whether you want to Encrypt traffic or Limit bandwidth during replication updates.
9. In the right-hand column, under Objects Being Replicated, click the boxes next to the objects you want to replicate.

Selected Objects
Some selected objects may have dependencies other objects that will be pulled into replication because they share data. For
more details, see what's copied. Objects that will be replicated are confirmed with a blue chain link icon.
Note that this is not guaranteed to be the full set of dependent objects, but rather is a best guess. The full set
of objects and their dependents will be calculated at the time of replication.
When selecting objects, you can select the entire server (Entire Delphix Engine) or a set of groups, dSources, VDBs, and Jet
Stream data layouts.
When replicating a group, all dSources and VDBs currently in the group, or added to the group at a later time, will be included.
If you select a Jet Stream data template, all data containers created from that template will be included. Likewise, if you select
a data container, its parent data template will be included.
If you select the entire server, all groups and Jet Stream objects will be included.
Regardless of whether you select a VDB individually or as part of a group, the parent dSource or VDB (and any parents in its
lineage) are automatically included. This is required because VDBs share data with their parent object. In addition, any
environments containing database instances used as part of a replicated dSource or VDB are included as well.
When replicating individual VDBs, only those database instances and repositories required to represent the replicated VDBs
are included. Other database instances that may be part of the environment, such as those for other VDBs, are not included.

10. Click Create Profile to submit the new profile. This saves the replication profile details. If you leave the Create page prior to submitting
the profile, the draft replication profile will be discarded.

Interacting with the Replica Section

Click the screenshot below for an enlarged view of the Replica section. The descriptions below provide more details of the functionality of this
section.

661

Delphix User Guide 2016 Delphix

Status Box
Similar to the Replication Profile status box, this shows the most up-to-date status information for the replica on the target
Replicated Environments
Replicating a dSource or VDB will automatically replicate any environments associated with those objects. For more information, see
Replication Overview.

Replicated Objects Tree

A read-only view of the objects in this replica
Failover Button
Initiates failover for this replica
Delete Button
Deletes this Replica on the target. This does not have an affect on the corresponding profile on the source engine.

Getting Started: Working in the Replication User Interface

To navigate to the Replication UI screen:
1. In the top navigation menu, click System.
2. Select Replication.

Configuring Replication Profiles

1.
662

Delphix User Guide 2016 Delphix

1. In the left-hand navigation section, click Create Profile.

2. Enter the name of the replication profile and an optional description.

3. Select Replication Profile as the type.
4. For Target Engine, enter the hostname or IP address for the target Delphix Engine.
5. Enter the username and password of a user who has Delphix Admin-level credentials on the target Delphix Engine. If the username and
password change on the target Delphix Engine, you must update these settings on the source Delphix Engine.
6. By default, automatic replication is disabled, meaning that you must trigger replication updates manually. To enable automatic replication,
click the Enabled checkbox.
7. In the Automatic Replication field, enter the Frequency and Starting Time for replication updates to the target Delphix Engine. Once
you have entered and saved your replication settings, you will also see an option to trigger replication immediately with the Replicate
Now button.
a. Note : Automatic replication uses Quartz for scheduling. Starting with Delphix version 4.2, the Quartz-formatted string is editable
via the Advanced option. Please refer to the screenshot below:

8. Under Traffic Options, select whether you want to Encrypt traffic or Limit bandwidth during replication updates.
9. In the right-hand column, under Objects Being Replicated, click the boxes next to the objects you want to replicate.

Selected Objects
Some selected objects may have dependencies other objects that will be pulled into replication because they share data. For
more details, see what's copied. Objects that will be replicated are confirmed with a blue chain link icon.
Note that this is not guaranteed to be the full set of dependent objects, but rather is a best guess. The full set
of objects and their dependents will be calculated at the time of replication.
When selecting objects, you can select the entire server (Entire Delphix Engine) or a set of groups, dSources, VDBs, and Jet
Stream data layouts.
When replicating a group, all dSources and VDBs currently in the group, or added to the group at a later time, will be included.
If you select a Jet Stream data template, all data containers created from that template will be included. Likewise, if you select
a data container, its parent data template will be included.
If you select the entire server, all groups and Jet Stream objects will be included.
Regardless of whether you select a VDB individually or as part of a group, the parent dSource or VDB (and any parents in its
lineage) are automatically included. This is required because VDBs share data with their parent object. In addition, any
environments containing database instances used as part of a replicated dSource or VDB are included as well.
When replicating individual VDBs, only those database instances and repositories required to represent the replicated VDBs
are included. Other database instances that may be part of the environment, such as those for other VDBs, are not included.

10. Click Create Profile to submit the new profile. This saves the replication profile details. If you leave the Create page prior to submitting
the profile, the draft replication profile will be discarded.

Viewing and Editing an Existing Replication Profile

To view and edit existing replicas:
1. From the left-hand navigation area, under the Received Replicas section, select a replica.
2. You can edit the Name and Description fields. All other fields are view-only.
To edit fields:

1. Click the edit icon

next to the corresponding field or group of fields.

663

Delphix User Guide 2016 Delphix

1.
2. You will also see
, which allow you to edit or cancel changes.
a. To commit to the edits and/or selections, click the Green Checkmark icon.
b. To cancel the edits and/or selections, click the Red X icon.

Viewing and Editing a Replica

To view and edit existing replicas:
1. From the left-hand navigation area, under the Received Replicas section, select a replica.
2. You can edit the Name and Description fields. All other fields are view-only.
To edit fields:

1. Click the edit icon

next to the corresponding field or group of fields.

2. You will also see

, which allow you to edit or cancel changes.
a. To commit to the edits and/or selections, click the Green Checkmark icon.
b. To cancel the edits and/or selections, click the Red X icon.

Related Links
CLI Cookbook: Replication
Configuring Replication
Replicas and Failover
Failing Over a Replica

664

Delphix User Guide 2016 Delphix

Configuring Replication
This topic describes how to configure data replication between Delphix Engines.
Prerequisites
Configuring the Network
Configuring the Replication Source Delphix Engine
Configuring the Target Delphix Engine
Related Links

Prerequisites
The replication source and the replication target must be running identical versions of the Delphix Engine (for example, Delphix Engine
version 5.0).
The target Delphix Engine must be reachable from the source engine.
The target Delphix Engine must have sufficient free storage to receive the replicated data.
The user must have administrative privileges on the source and the target engines.
See also: Replication Prerequisites

Configuring the Network

Replication operates using a private network protocol between two Delphix Engines. Apart from standard network considerations for performance,
no additional configuration is required for replication. Replication can run over dedicated networks by configuring routing to direct traffic destined
for the target IP address over a specific interface. The replication process can recover from transient network outages, but extended outages may
cause the process to start from the previous update.
The replication network protocol uses TCP port 8415. If there is a firewall between the source and target that is blocking this port, then there are
two possible solutions:
Enable port 8415 on the firewall in order to allow connections to this port from the source to the target.
Replication can connect through a SOCKS proxy if one exists. Configure the SOCKS proxy address and port by connecting to the
command line interface (CLI) as a system administrator user and navigating to "service proxy" to update the SOCKS configuration.
Example:

dlpx-engine> service proxy

dlpx-engine service proxy> update
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy> get
type: ProxyService
https:
type: ProxyConfiguration
enabled: false
host: (unset)
password: (unset)
port: 8080
username: (unset)
socks:
type: ProxyConfiguration
enabled: true
host: 10.2.3.4
password: ********
port: 1080
username: someuser

set socks.enabled=true
set socks.host=10.2.3.4
set socks.username=someuser
set socks.password=somepassword
commit

Note that SOCKS port 1080 is used by default, but can be overridden.

665

Delphix User Guide 2016 Delphix

Configuring the Replication Source Delphix Engine

1. On the source Delphix Engine, click System.
2. Select Replication.
3. In the left-hand navigation section, click Create Profile.
4. Enter the name of the replication profile and an optional description.
5. For Target Engine, enter the hostname or IP address for the target Delphix Engine.
6. Enter the username and password of a user who has Delphix Admin-level credentials on the target Delphix Engine. If the username and
password change on the target Delphix Engine, you must update these settings on the source Delphix Engine.
7. By default, automatic replication is disabled, meaning that you must trigger replication updates manually. To enable automatic replication,
click the Enabled checkbox.
8. In the Automatic Replication field, enter the Frequency and Starting Time for replication updates to the target Delphix Engine. Once
you have entered and saved your replication settings, you will also see an option to trigger replication immediately with the Replicate
Now button.
Encrypting Traffic
Automatic replication uses Quartz for scheduling. Starting with Delphix version 4.2, the Quartz-formatted string is editable via
the Advanced option.

9. Under Traffic Options, select whether you want to Encrypt traffic or Limit bandwidth during replication updates.
Encrypting Traffic
By default, replication streams are sent unencrypted. This provides maximum performance on a secure network. If the network
is insecure, you can enable encryption. Note that encrypting the replication stream will consume additional CPU resources and
may limit the maximum bandwidth that can be achieved.

Compressing Traffic
All replication streams are compressed via the same mechanism that compresses the data on disk. In environments where
network bandwidth is a constrained resource, compression has been shown to conserve bandwidth and optimize overall
throughput achieved by replication. Because the data is already stored compressed, there is no CPU overhead for
compressing replication streams.

Limiting Bandwidth
By default, replication will run at the maximum speed permitted by the underlying infrastructure. In some cases, particularly
when a shared network is being used, replication can increase resource contention and may impact the performance of other
operations. This option allows administrators to specify maximum bandwidth that replication can consume.

10. In the right-hand column, under Objects Being Replicated, click the checkboxes next to the objects you want to replicate.
Selected Objects
Some selected objects may have dependencies other objects that will be pulled into replication because they share
data. For more details, see Replication Overview. Objects that will be replicated are confirmed with a blue chain link
icon.
When selecting objects, you can select the entire server (Entire Delphix Engine) or a set of groups, dSources, VDBs,
and Jet Stream data layouts.
Note that this is not guaranteed to be the full set of dependent objects, but rather is a best guess. The
full set of objects and their dependants will be calculated at the time of replication.
When replicating a group, all dSources and VDBs currently in the group, or added to the group at a later time, will be
included.
If you select a Jet Stream data template, all data containers created from that template will be included. Likewise, if
you select a data container, its parent data template will be included.
If you select the entire server, all groups and Jet Stream objects will be included.
Regardless of whether you select a VDB individually or as part of a group, the parent dSource or VDB (and any
parents in its lineage) are automatically included. This is required because VDBs share data with their parent object. In
addition, any environments containing database instances used as part of a replicated dSource or VDB are included
as well.
When replicating individual VDBs, only those database instances and repositories required to represent the replicated
VDBs are included. Other database instances that may be part of the environment, such as those for other VDBs, are

666

Delphix User Guide 2016 Delphix

not included.

11. Click Create Profile to submit the new profile. This saves the replication profile details. If you leave the Create page prior to submitting
the profile, the draft replication profile will be discarded.

Configuring Replication and Multiple Target Engines through the CLI

You can also configure replication on the source Delphix Engine by using the replication spec in the command line interface. See the
topics under CLI Cookbook: Replication for more information.

Enabling Configuration of Multiple Replication Profiles

Learn how to configure and use functionality for multiple replication profiles on the source using the replication profiles in the Replicatio
n User Interface

Configuring the Target Delphix Engine

No additional configuration on the target is needed. Replicated objects will appear in an alternate replica that mirrors the original object layout.
These replicas can be viewed through the System > Replication screen under the Received Replicas section (or namespace in the CLI). All
replicated objects are read-only until the replica is failed over. For more information about managing replicas and how to activate a replica, see
the topics Replicas and Failover and Failing Over a Replica.
Objects can be created and managed on the target server without affecting subsequent updates, though this can cause conflicts on failover that
require additional time to resolve. For disaster recovery use cases, it is recommended to keep the target passive and not create any local objects.
This will avoid conflicts and guarantee a smooth failover operation.
Multiple sources can replicate to the same target, allowing for flexible geographical distribution of data. For disaster recovery this is not a
recommended practice, as it increases the probability of conflicts on failover, and may oversubscribe resources on the target if multiple replicas
are failed over and there is insufficient infrastructure to support the combined workloads.

Related Links
CLI Cookbook: Replication
Replication Overview
Replication User Interface
Replicas and Failover
Failing Over a Replica

667

Delphix User Guide 2016 Delphix

Enabling Replicated Objects

In order to complete the failover, you need to enable the objects on the now-primary Delphix Engine.
SSH Keys
If you were previously using password-less SSH key exchange on your source and/or target environments, you may need to publish the
now-primary engines public key for continued functionality.
1. Navigate to Manage/Environments
2. Select any environment
3. Under Environment Users, click the pencil icon (

) next to the defined user

4. Click View Public Key in order to display the public key for the Delphix Engine
5. Highlight the public key string (starts with ssh-rsa) and copy the key to your clipboard (Ctrl+C in Windows)
6. On each source and target host within your defined environments, paste the public key into the environment users authorized_keys file
(normally located in the users ~/.ssh/ directory)
Once the public key has been copied to the hosts making up your environments, you are ready to enable the remaining objects.
Enabling Environments
In order to begin using the environments and related dSources and VDBs, the environments must first be started.
1. Log into the Delphix Engine as delphix_admin or another user with administrative privileges
2. Navigate to Manage/Environments
3. Select an environment which you want to enable
4. Click or slide the slide bar, currently displaying Disabled (
initiate jobs that will refresh and enable the environment.

), to the right in order to enable the environment. This will

5. Repeat these steps for each environment which you want to enable
Enabling dSources
In order to again have actively syncing dSources, you must enable them.
1. Log onto the Delphix Engine administrative GUI as delphix_admin or another user with administrative privileges.
2. Click the Delphix logo in the upper-left corner, or navigate to Manage/Databases/My Databases
3. Hover over the dSource you wish to enable, and click the open arrow (
4. Click or slide the slide bar in the lower-left corner (

) to flip over the dSources card.

) to enable the dSource.

5. Confirm that you wish to enable the dSource.

Enabling VDBs
The final step in the failover would be to enable any needed VDBs.
1. Log into the Delphix Engine as delphix_admin or another user with administrative privileges.
2. Click on the VDB that needs to be enabled
3. To the right of the VDB name, click the open icon (

) to open the VDBs card

4. Click or slide the slide bar in the lower-left corner (

) to enable the VDB.

5. Confirm that you wish to enable the VDB.

668

Delphix User Guide 2016 Delphix

At this time the failover is complete. All objects previously running on the previous source Delphix Engine should now be running off of the
Delphix Engine to which was failed over.

669

Delphix User Guide 2016 Delphix

Replicas and Failover

This topic describes failover of replicated state.
Replication recreates objects on the target system in a replica that preserves object relationships and naming on the target server without
interfering with active objects on the system. Objects within a replica are read-only and disabled until a replica is failed over, at which point they
can be activated. VDBs and dSources within a replica can be used as the source for provisioning new VDBs.
Replicas
Failover and Conflict Resolution
Enabling Databases and Environments
Restoring Policies and Users

Replicas
A replica contains a set of replicated objects. These objects are read-only and disabled while replication is ongoing. To view replicated objects,
select the System > Replication menu item and select the replica under Received Replicas (or namespace in the CLI). On this screen you can
browse the contents of replicas, as well as fail over or delete individual replicas. As described in the Replication Overview NEW topic,
databases (dSouces and VDBs) and environments are included within the Replica.
Deleting or failing over a replica will sever any link with the replication source. Subsequent incremental updates will fail, requiring the
source to re-establish replication. Failover should only be triggered when no further updates from the source are possible (as in a
disaster scenario).
Multiple replicas can exist on the system at the same time. Active objects can exist in the system alongside replicas without interfering with
replication updates. VDBs and dSources within a replica can also be used as a source when provisioning. For more information, see Provisionin
g from Replicated Data Sources or VDBs.

Failover and Conflict Resolution

To activate the objects in a replica, you must first fail over the replica. This will sever replication and move the objects to the live system, where
they can be manipulated in the same fashion as other objects on the system. Any active objects with conflicting names will cause an error at the
time of failover. The error message will indicate which object(s) have conflicting names. The active objects must be renamed, since the replica
objects are read-only, before the failover operation can complete successfully.
Given that conflicting names prevent failover from succeeding, best practices in a disaster recovery situation are to leave the target
system completely passive with no active objects until the time that a failover is required.
Once a replica is failed over, the objects are active but will be automatically disabled.

Enabling Databases and Environments

Objects may refer to states (IP addresses, mount paths, etc) that differ between the source and target system. Because of this, all databases and
objects within a replica automatically start in the disabled state after a failover. This allows the administrator to alter configuration prior to enabling
databases and environments, without the system inadvertently connecting to invalid systems.
After failover is complete, all dSources, VDBs, and environments must be explicitly enabled. Should any configuration need to change for the
target environment, this can be done prior to enabling the objects.

Restoring Policies and Users

Policies and users are not replicated or backed up, requiring that they be recreated on the target after a failover. There is no built-in mechanism to
automate this within Delphix. It is recommended that all users and policies be backed up (using the CLI, web services or other manual means) so
that they can be recreated on the target system after failover.

670

Delphix User Guide 2016 Delphix

Failing Over a Replica

This topic describes the process of failing over a replica. Objects stored in a replica are read-only, and failing over a replica moves the replicated
objects to the live system. After a failover all of the objects will appear in the system as if they had been created locally.

Prerequisites
A Delphix system that contains a replica is required, see the Replicas and Failover topic for an overview of what replicas are and what failover
implies. For more information on configuring replication please refer to the Configuring Replication topics.

Procedure
1. Locate the replica to failover. The list of replicas can be accessed via the Received Replicas section of the System > Replication scree
n. Each replica has a default name that is the hostname of the source that sent the update. These names may be customized if desired.
Each replica will list the databases and environments it contains.
If this replica is the result of a replication update, check to see if the source Delphix appliance is still active. If so, then disable
any dsource or VDB that is part of the replica being failed over to ensure that only one instance is enabled. Dsources and
VDBs can be disabled by going to the Databases > My Databases screen, finding the appropriate database, and toggling the
enabled slider.

2. Click Failover and confirm the dialog that appears.

This will pause while the replica is failed over.
3. Apply any configuration changes that are required to customize the objects for the system. This might include updating object state such
as IP addresses, mount paths, or credentials. See the Replicas and Failover topic for more details.
4. Enable the environments that were failed over. The environments can be found by selecting Manage > Environments. The
environments will be disabled, toggle the disabled slider to enable them.
5. Enable the dsources and VDBs that were failed over. The databases can be found by selecting Databases > My Databases. Each
database will have a card, select the desired database card and toggle the disabled slider to enable them.
Policies and users are not replicated, be sure to recreate them after you fail over.

Related Topics
Replication User Interface
Replicas and Failover
Configuring Replication

671

Delphix User Guide 2016 Delphix

Updating Replication User Credentials from Previous Versions

This topic describes how to update the replication user credentials from previous versions of the Delphix Engine.
Previous versions of the Delphix Engine performed authentication through an NDMP user that was configured separately from the normal Delphix
users. With Delphix Engine 3.2, authentication is performed against native Delphix users.

Prerequisites
A source and target replication host that were configured with a release prior to 3.2 and subsequently upgraded.
On the target system, a Delphix user with domain privileges is required.

Procedure
1. On the source host, click System.
2. Select Replication.
3. Enter the name and password for a Delphix user on the target who has domain privileges.
4. Save the configuration.

Related Links
Configuring Replication

672

Delphix User Guide 2016 Delphix

Provisioning from Replicated Data Sources or VDBs

This topic describes how to provision from a replicated dSource or VDB. The process for provisioning from replicated objects is the same as the
typical VDB provisioning process except for the need to first select the namespace containing the replicated object.

Prerequisites
You will need to have replicated a dSource or a VDB to the target host, as described in Replication Overview
You will need to have added a compatible target environment on the target host as described in Provisioning VDBs: An Overview
You will need to install any toolkits the replicated objects depend on on the target host.

Procedure
1. Login to the Delphix Admin application for the target host.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. In the list of replicas, select the replica that contains the dSource or VDB to be provisioned.
6. The provisioning process is now identical to the process for provisioning standard objects. For the details of how to provision VDBs for
specific platforms, consult Provisioning VDBs: An Overview.

Post-Requisites
Once the provisioning job has started, the user interface will automatically display the new VDB in the live system.

Related Links
Replication Overview
Database Provisioning Overview
Provisioning VDBs: An Overview
Provisioning VDBs from Oracle and Oracle RAC dSources
Provisioning VDBs from SQL Server dSources
Provisioning VDBs from PostgreSQL dSources

673

Delphix User Guide 2016 Delphix

Selective Data Distribution

These topics describe concepts and procedures for replicating data from one Delphix Engine to another.
Selective Data Distribution Overview
Selective Data Distribution Use Cases
Selective Data Distribution User Interface
Configuring Selective Data Distribution
Selective Data Distribution and Failover

674

Delphix User Guide 2016 Delphix

Selective Data Distribution Overview

Selective Data Distribution Feature Flag
If you are interested in using the functionality enabled with Selective Data Distribution, please submit a support ticket request @ https://
support.delphix.com
The selective data distribution technology permits the distribution of masked data between Delphix Engines without bringing over the unmasked
parent source. These engines must be the identical versions of the Delphix Data as a Service Engine with the Delphix Masking Engine. Otherwi
se they can be asymmetric in terms of engine configuration. To learn more read the Delphix Masking Quick Start Guide. You can provision
VDBs from distributed masked objects, allowing for geographical distribution of data and remote provisioning.
You can run selective data distribution ad hoc, but it is typically run according to a predefined schedule. After the initial update, each subsequent
update sends only the changes incurred since the previous update. Selective data distribution does not provide synchronous semantics, meaning
that the data distributed to the target is only as current as the most recent update.

Selective Data Distribution Features

As virtual appliances, you can backup, restore, replicate, and migrate data objects between Delphix Engines using features of VMWare and the
underlying storage infrastructure. In addition to the replication capabilities provided by this infrastructure, selective data distribution permits the
distribution of masked data between Delphix Engines. The sources received on a target Delphix Engine do not include the original parent source,
thereby making the original source inaccessible from the target.
Selective data distribution is configured on the source Delphix Engine. It first copies a subset of masked VDBs to a target Delphix Engine, then
sends incremental updates either manually or according to a schedule.
You can use replicated masked VDBs to provision new VDBs on the target Delphix Engine. The provisioned VDBs contain the data in their
masked parent and are therefore also considered masked. You can refresh these VDBs to snapshots sent as part of an incremental replication
update, as long as you do not destroy the parent object on the replication source. For more information, see Provisioning from a Replicated
Data Sources or VDBs.
During replication, replicated masked VDBs are maintained in an alternate replica and are not active on the target side. Failover of a selective
data distribution replica is not supported.

Selective Data Distribution Details

When you select masked objects for selective data distribution, the engine will automatically include any dependencies, such as environments,
associated with the VDB. The parent dSource and any parent VDBs are not included automatically. The data associated with parent objects are
selectively included for disk space efficiency, but data in the parent dSource and VDBs that are not needed by the masked VDB are excluded.
During replication, the Delphix Engine will negotiate an SSL connection with its server peer to use SSL_RSA_WITH_RC4_128_MD5 as the cipher
suite, and TLSv1 as the protocol.
Only database objects and their dependencies are copied as part of a selective data distribution operation, including:
Masked VDBs
Environments
Environment configuration (users, database instances, and installations)
The following objects are not copied as part of a selective data distribution operation:
Parent dSources of masked VDBs
Groups of the parent dSources
Users and roles
Policies
VDB (init.ora) configuration templates
Events and faults
Job history
System services settings, such as SMTP

Resumable Selective Data Distribution

A single selective data distribution instance can fail for a number of environmental and internal reasons. However, using the Resume feature, you
can restart selective data distribution from an intermediate point; no data is retransmitted. Selective data distribution is resumable across machine
reboot, stack restart, and network partitions.

675

Delphix User Guide 2016 Delphix

For example, you can resume a large, time-consuming initial distribution or incremental update after it is interrupted. Suppose a selective data
distribution profile has already been configured from a source to a target. A large, full send from the source begins that is expected to take weeks
to complete. Halfway through, a power outage at the data center that houses the source causes the source machine to go down and only come
back up after a few hours. On startup, the source will detect that a selective data distribution was ongoing, automatically re-contact the target, and
resume the distribution where it left off. In the user interface (UI) on the source, the same selective data distribution send job will appear as active
and continue to update its progress. However, in the UI of the target, a new distribution receive job will appear, although it will track its progress
as a percentage of the entire replication.
Selective data distribution will not resume after failures that leave the source and target connected. For example, if a storage failure on the
target, such as an out-of-space error, causes a distribution to fail the source and target remain connected. As a result, the Delphix Engine will
conservatively throw away all MDS and ZFS data associated with the failed operation.

Selective Data Distribution Restrictions

Only masked VDBs can be added to a selective data distribution spec. You cannot add dSources, groups, or the entire domain.
Unmasked VDBs cannot be added to a selective data distribution spec.
VDBs that undergo selective data distribution and their children cannot be selectively redistributed to another target.
You cannot go to the target engine and create a selective data distribution spec that includes VDBs that are present because of a
selective data distribution. However, you can replicate this data using a traditional replication spec.

Related Links
Delphix Masking Overview
Selective Data Distribution Use Cases
Selective Data Distribution User Interface
Configuring Selective Data Distribution
Selective Data Distribution and Failover
Provisioning from a Replicated Data Sources or VDBs

676

Delphix User Guide 2016 Delphix

Selective Data Distribution Use Cases

Selective data distribution is a flexible tool that allows you to move dSources and virtual databases (VDBs) between Delphix Engines. Selective
data distribution relies on the replication infrastructure to transmit masked data, as such selectively distributed data has much of the same
capabilities and uses as replicated data. These topics describe several different use cases for selective data distribution.

Geographically Distributed Development

The Delphix Engine allows you to provision VDBs from distributed dSources and VDBs, as described in Provisioning from Replicated Data
Sources or VDBs. This allows dSources that are linked in a single central location to be geographically distributed so that developers can
provision VDBs remotely without having to sync from the source database in multiple locations. Selective distribution ensures that masked VDBs
are sent to the target without transmitting the original unmasked source. As such, the original unmasked source will not be accessible on the
target.
Selective data distribution does not support failover. In this environment, the link between the source and the target is never broken, except when
remote VDBs need to be preserved. You can refresh remote VDBs as long as the parent objects continue to exist on the source. If they are
deleted, then remote VDBs will continue to function but cannot be refreshed.

Because there is no failover, this technology can support more complex topologies such as 1-to-many and many-to-1. Chained distribution
(replicating from Site A -> Site B -> Site C) is not supported.

Best Practices
For geographical distribution, follow these best practices:
Because each replication stream induces load on the source system:
Minimize the number of simultaneous replication updates
If possible, avoid heavy VDB workloads on the source
On the target, provision only from sources that are effectively permanent. If a source is deleted remote VDBs can no longer be refreshed.
Provision additional storage capacity on the target
Remotely provisioned VDBs can consume shared storage on the target even when the parent is deleted on the source

Migration
You cannot use selective data distribution for data migration. A full replication is needed for data migration.

Related Links
Selective Data Distribution Overview
Selective Data Distribution User Interface

677

Delphix User Guide 2016 Delphix

Configuring Selective Data Distribution

Selective Data Distribution and Failover
Delphix Masking Overview
Provisioning from Replicated Data Sources or VDBs

678

Delphix User Guide 2016 Delphix

Selective Data Distribution User Interface

Understanding Selective Data Distribution Functionality and User Interface
Selective Data Distribution in the Delphix Engine in 5.0 release
Understanding Sources for Selective Data Distribution
Understanding Targets for Selective Data Distribution
User Interface Selective Data Distribution Screen
Interacting with the Selective Data Distribution Profiles Section
Interacting with the Create New Selective Data Distribution Profile Section
Interacting with the Selective Data Distribution Replica Section
Viewing and Editing an Existing Selective Data Distribution Profile
Viewing and Editing a Replica
Related Links

Understanding Selective Data Distribution Functionality and User Interface

Selective Data Distribution in the Delphix Engine in 5.0 release
In the 5.0 release, a new replication profile type Selective Data Distribution is added in the Replication section.

Understanding Sources for Selective Data Distribution

The Replication Profile section continues to handle the existing functionality but allows for the configuration of Selective Data Distribution profil
es. This makes it possible to distributes objects from a single source to multiple targets. Each profile defines the set of data objects and the
associated configuration between a single source and target.

Understanding Targets for Selective Data Distribution

The Replica section shows you the set of all objects in the Selective Data Distribution replica.

User Interface Selective Data Distribution Screen

There are three interconnected sections that have been introduced to make the selected data distribution workflow easier:
Selective Data Distribution Profiles
Create New Selective Data Distribution Profile
Selective Data Distribution Replica.

Interacting with the Selective Data Distribution Profiles Section

The following screenshot and the descriptions below illustrate the capabilities in the Selective Data Distribution Profiles section. Click the
screenshot for an enlarged view.

679

Delphix User Guide 2016 Delphix

Create Profile Button

is the icon that allows you to create a selective data distribution profile.
Replication Profiles List
Provides a list of existing replication profiles and selective data distribution profiles. Click a profile in this list to view its details.
To tell the types of the profiles in the list, you can give the profiles different names, or note the different icons.

is the icon for a replication profile.

is the icon for a selective data distribution profile.

Received Replicas List
Provides a list of all existing replicas on this Delphix Engine, including normal replication replicas and selective data distributions. Click
a replica in this list to view its details.
To distinguish between the types of the replicas in the list, you can give the replicas different names, or note the different icons.

is the icon for a replication replica.

is for a selective data distribution replica.

680

Delphix User Guide 2016 Delphix

Status Box
Shows the distribution status of the selected profile, including:
The result of the most recent or current distribution event
Statistics for the distribution run, such as data transferred, duration, and average throughput
In the upper left-hand corner, an icon summarizes the distribution status. There are four possible status icons:

Type
Shows the type of the selected profile or replica.
Configuration Options
Configuration options for the selective data distribution profile you have selected. These include:
Description Free text description of the profile
Target Engine The Delphix Engine on the receiving end of this data distribution pair
Automatic Replication If enabled, shows the frequency and time that regular distribution will be run
Traffic options Summarizes the traffic options with which this profile has been configured
Object Selection Tree
Shows all of the masked objects that you have selected for distribution in this selective data distribution profile.
Replicate Now Button
Begins the distribution process
Delete Button
Allows you to delete the current profile

Interacting with the Create New Selective Data Distribution Profile Section
1. In the left-hand navigation section, click the Create Profile icon

681

. It will show the Create New Profile page.

Delphix User Guide 2016 Delphix

2. Enter the name of the selective data distribution profile and an optional description.
3. Select type Selective Data Distribution.
4. For Target Engine, enter the hostname or IP address for the target Delphix Engine.
5. Enter the username and password of a user who has Delphix Admin-level credentials on the target Delphix Engine. If the username and
password change on the target Delphix Engine, you must update these settings on the source Delphix Engine.
6. By default, automatic replication is disabled, meaning that you must trigger distribution updates manually. To enable automatic
distribution, click the Enabled checkbox.
7. In the Automatic Replication field, enter the Frequency and Starting Time for distribution updates to the target Delphix Engine. Once
you have entered and saved your distribution settings, you will also see an option to trigger distribution immediately with the Replicate
Now button.
Automatic replication uses Quartz for scheduling. Starting with Delphix version 4.2, the Quartz-formatted string is editable via
the Advanced option. Refer to the screenshot below.

8. Under Traffic Options, select whether you want to Encrypt traffic or Limit bandwidth during distribution updates.
9. In the right-hand column, under Objects Being Replicated, click the boxes next to the objects you want to distribute.

Selected Objects

Only masked VDBs

can be used in a selective data distribution.
If there are no masked VDBs, you cannot create a selective data distribution profile.

10. Click Create Profile to submit the new profile. This saves the selective data distribution profile details. If you leave the Create page
prior to submitting the profile, the draft selective data distribution profile will be discarded.

Interacting with the Selective Data Distribution Replica Section

682

Delphix User Guide 2016 Delphix

Click the screenshot below for an enlarged view of the Replica section. The descriptions below provide more details of the functionality of this
section.

Status Box
Similar to the Replication Profile status box, this shows the most up-to-date status information for the replica on the target.
Type
A read-only field of the type of the replica, which is Selective Data Distribution.

Replicated Environments
Distributing a masked VDB will automatically distribute any environments associated with those objects. For more information, see Sel
ective Data Distribution Overview.
Replicated Objects Tree
A read-only view of the distributed objects in this replica
Delete Button
Deletes this replica on the target. This does not have an affect on the corresponding profile on the source engine.

Viewing and Editing an Existing Selective Data Distribution Profile

To view and edit existing replicas:
1. From the left-hand navigation area, under the Replication Profile section, select a Selective Data Distribution profile.
2. You can edit the Name and Description fields. All other fields are view-only.
To edit fields:

1. Click the edit icon

next to the corresponding field or group of fields.

2. You will also see

, which allow you to edit or cancel changes.
a. To commit to the edits and/or selections, click the Green Checkmark icon.
b. To cancel the edits and/or selections, click the Red X icon.

Viewing and Editing a Replica

683

Delphix User Guide 2016 Delphix

To view and edit existing replicas:

1. From the left-hand navigation area, under the Received Replicas section, select a replica.
2. You can edit the Name and Description fields. All other fields are view-only.
To edit fields:

1. Click the edit icon

next to the corresponding field or group of fields.

2. You will also see

, which allow you to edit or cancel changes.
a. To commit to the edits and/or selections, click the Green Checkmark icon.
b. To cancel the edits and/or selections, click the Red X icon.

Related Links
Selective Data Distribution Overview
Selective Data Distribution Use Cases
Configuring Selective Data Distribution
Selective Data Distribution and Failover
Delphix Masking Overview

684

Delphix User Guide 2016 Delphix

Configuring Selective Data Distribution

This topic describes how to configure Selective Data Distribution between Delphix Engines. Selective data distribution relies on the replication
infrastructure to transmit masked data, as such configuring selective data distribution is similar to configuring replication.
Prerequisites
Configuring the Network
Configuring the Source Delphix Engine
Configuring the Target Delphix Engine
Related Links

Prerequisites
The replication source and the replication target must be running identical versions of the Delphix Engine (for example, Delphix Engine
version 5.0).
The target Delphix Engine must be reachable from the source engine.
The target Delphix Engine must have sufficient free storage to receive the replicated data.
The user must have administrative privileges on the source and the target engines.
See also: Replication Prerequisites

Configuring the Network

Replication and selective data distribution operate using a private network protocol between two Delphix Engines. Apart from standard network
considerations for performance, no additional configuration is required for replication. Replication and selective data distribution can run over
dedicated networks by configuring routing to direct traffic destined for the target IP address over a specific interface. The selective data
distribution process can recover from transient network outages, but extended outages may cause the process to start from the previous update.
The selective data distribution network protocol uses TCP port 8415. If there is a firewall between the source and target that is blocking this port,
then there are two possible solutions:
Enable port 8415 on the firewall in order to allow connections to this port from the source to the target.
or
Selective data distribution can connect through a SOCKS proxy, if one exists. Configure the SOCKS proxy address and port by
connecting to the command line interface (CLI) as a system administrator and navigating to "service proxy" to update the socks
configuration. Example:

dlpx-engine> service proxy

dlpx-engine service proxy> update
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy update *>
dlpx-engine service proxy> get
type: ProxyService
https:
type: ProxyConfiguration
enabled: false
host: (unset)
password: (unset)
port: 8080
username: (unset)
socks:
type: ProxyConfiguration
enabled: true
host: 10.2.3.4
password: ********
port: 1080
username: someuser

set socks.enabled=true
set socks.host=10.2.3.4
set socks.username=someuser
set socks.password=somepassword
commit

685

Delphix User Guide 2016 Delphix

Note that SOCKS port 1080 is used by default, but you can override it.

Configuring the Source Delphix Engine

1. On the source Delphix Engine, click System.
2. Select Replication.
3. In the left-hand navigation section, click Create Profile.
4. Enter the name of the replication profile and an optional description.
5. Select type Selective Data Distribution.
6. For Target Engine, enter the hostname or IP address for the target Delphix Engine.
7. Enter the username and password of a user who has Delphix Admin-level credentials on the target Delphix Engine. If the username and
password change on the target Delphix Engine, you must update these settings on the source Delphix Engine.
8. By default, automatic replication is disabled, meaning that you must trigger replication updates manually. To enable automatic replication,
click the Enabled checkbox.
9. In the Automatic Replication field, enter the Frequency and Starting Time for replication updates to the target Delphix Engine. Once
you have entered and saved your replication settings, you will also see an option to trigger replication immediately with the Replicate
Now button.
Quartz scheduling
Automatic replication uses Quartz for scheduling. Starting with Delphix version 4.2, the Quartz-formatted string is editable via
the Advanced option.

10. Under Traffic Options, select whether you want to Encrypt traffic or Limit bandwidth during replication updates.
Encrypting Traffic
By default, replication streams are sent unencrypted. This provides maximum performance on a secure network. If the network
is insecure, encryption can be enabled. Note that encrypting the replication stream will consume additional CPU resources and
may limit the maximum bandwidth that can be achieved.

Limiting Bandwidth
By default, replication will run at the maximum speed permitted by the underlying infrastructure. In some cases, particularly
when a shared network is being used, replication can increase resource contention and may impact the performance of other
operations. This option allows you to specify the maximum bandwidth that replication can consume.

11. In the right-hand column, under Objects Being Replicated, click the checkboxes next to the objects you want to replicate.
Selected Objects
You can only select masked VDBs for selective data distribution.
The parent dSource or VDB (and any parents in its lineage) are NOT automatically included. Some of the data from
the parent may be included for disk space optimization. In addition, any environments containing database instances
used as part of a replicated VDB are included as well.
When replicating individual VDBs, only those database instances and repositories required to represent the replicated
VDBs are included. Other database instances that may be part of the environment, such as those for other VDBs, are
not included.

12. Click Create Profile to submit the new profile. This saves the replication profile details. If you leave the Create page prior to submitting
the profile, the draft replication profile will be discarded.

Configuring Replication and Multiple Target Engines through the CLI

You can also configure replication on the Source Delphix Engine by using the replication spec in the command line interface. For more
information, see the topics under CLI Cookbook: Replication.

Enabling Configuration of Multiple Replication Profiles

Learn how to configure and use functionality for multiple replication profiles on the source using the replication profiles in the Replicatio
n User Interface.

686

Delphix User Guide 2016 Delphix

Configuring the Target Delphix Engine

No additional configuration on the target is needed. Selectively distributed objects will appear in an alternate replica that mirrors the original object
layout. To view these replicas:
1. Click System.
2. Select Replication.
3. Review items listed under Received Replicas.
Alternatively, you can view replicas under namespace in the command line interface (CLI). All replicated objects are read-only. For more
information about managing replicas, see Selective Data Distribution and Failover.
Multiple sources can replicate to the same target, allowing for flexible geographical distribution of data. You can create and manage objects on
the target server without affecting subsequent updates. However, you cannot use selective data distribution for disaster recovery.

Related Links
Selective Data Distribution Overview
Selective Data Distribution Use Cases
Selective Data Distribution User Interface
Selective Data Distribution and Failover
Delphix Masking Overview
CLI Cookbook: Replication
Replication Prerequisites
Replication User Interface

687

Delphix User Guide 2016 Delphix

Selective Data Distribution and Failover

This topic describes failover of replicated state.
Replicas
Failover
Related Topics
Selective data distribution recreates objects on the target system in a replica that preserves the object relationships and naming on the target
server without interfering with active objects on the system. Objects within a replica are read-only and disabled. They cannot be failed over.
However, you can use virtual databases (VDBs) within a replica as the source for provisioning new VDBs.

Replicas
A replica contains a set of replicated objects. These objects are read-only and disabled while replication is ongoing. To view replicated objects:
1. Click the System.
2. Select Replication.
3. Under Received Replicas, select the replica. On this screen, you can browse the contents of replicas or delete individual replicas. As
described in the Selective Data Distribution Overview, VDBs and environments are included within the replica.
You can also view replicated objects under namespace in the command line interface (CLI).
Deleting a replica will sever the link with the replication source. Subsequent incremental updates will fail, requiring the source to
re-establish replication.
Multiple replicas can exist on the system at the same time. Active objects can exist in the system alongside replicas without interfering with
replication updates. VDBs within a replica can also be used as a source when provisioning. For more information, see Provisioning from
Replicated Data Sources or VDBs.

Failover
Selective data distribution does not support failover of replicas.

Related Topics
Selective Data Distribution Overview
Selective Data Distribution Use Cases
Selective Data Distribution User Interface
Configuring Selective Data Distribution
Selective Data Distribution and Failover
Provisioning from Replicated Data Sources or VDBs
Delphix Masking Overview

688

Delphix User Guide 2016 Delphix

V2P: Virtual to Physical

These topics describe the concepts and procedures for exporting a virtual database (VDB) to a physical one, otherwise known as V2P.
Virtual to Physical: An Overview
V2P with an Oracle VDB
Move an Oracle VDB to a Physical ASM or Exadata Database
V2P with a SQL Server VDB
V2P with a PostgreSQL dSource or VDB
V2P with an SAP ASE dSource or VDB This topic describes the procedure for exporting a virtual database (VDB) to a

physical one, also known as V2P.

Manually Recovering a Database after V2P
Customizing Target Directory Structure for Database Export
V2P with Unstructured Files
V2P with a MySQL VDB

689

Delphix User Guide 2016 Delphix

Virtual to Physical: An Overview

This topic describes the basic concepts behind exporting a virtual database to a physical one, also known as V2P.
After you have created a dSource or a VDB, you can export its contents and log files to a physical database. This process, referred to as V2P,
creates a set of directories in the target environment and populates them with the database data, log files, and scripts that are used to recover the
physical database. You can automatically start the physical database recovery process as part of the V2P export, or you can use the scripts for a
manual recovery. When the export process completes, the target environment will contain a copy of the database in its unvirtualized size, so
before you begin the process, make sure the target directories you specify in the V2P wizard have enough capacity to hold the unvirtualized
database.
V2P can be initiated by users with delphix_admin credentials, and object and group owners.

690

Delphix User Guide 2016 Delphix

V2P with an Oracle VDB

This topic describes the procedure for exporting a virtual database (VDB) to a physical one, also known as V2P.

Procedure
1. Login to the Delphix Admin application as a Delphix Admin user, or as a group or object owner.
2. Select the dSource or VDB you want to export.
3. Select the Snapshot of the dSource or VDB state you want to export.
4. If you want to export the state of the database from a specific point in time, slide the LogSync slider on the top of the snapshot card to
the right, and then select the point in time from which you want to create the export.
5. Click V2P or Deploy (If you have the Delphix Modernization Engine you will see "Deploy").
6. Select the target environment.
7. Enter the Target Directory for the export.
The target directory you enter here must exist in the target environment, and you must have permission to write to it. For more
information on user requirements for target environments, see Requirements for Oracle Target Hosts and Databases.
8. Select whether or not to Open Database After Recovery.
If you do not select this option, the Oracle database will not undergo open resetlogs, and the database will not be available for read/write
access. This can be useful if the files are to be used to restore an existing data file for recovery purposes. You can use the scripts that
are created in the target environment to complete the database open process at a later time. For more information, see Manually
Recovering a Database after V2P.
9. Click Advanced to customize data transfer settings, customize the target directory layout, enter any database configuration param
eters or enter file mappings from the source environment to the target. For more information, see Customizing Target Directory
Structure for Database Export, Customizing Oracle VDB Configuration Settings and Customizing VDB File Mappings. The data
transfer settings are described below:
Compression Enable compression of data sent over the network. Default is Off.
Encryption Enable encryption of data sent over the network. Default is Off.
Bandwidth Limit Select the network bandwidth limit in units of megabytes per second (MB/s) between the Delphix Engine and
the target environment. Default is 0, which means no bandwidth limit is enforced.
Number of Connections Select the number of transmission control protocol (TCP) connections to use between the Delphix
Engine and the target environment. Multiple connections may improve network throughput, especially over long-latency and
highly-congested networks. Default is 1.
Number of Files to Stream Concurrently Select the number of files that V2P should stream concurrently from the Delphix
Engine to the target environment. Default is 3.
10. Click Next.
11. Select whether you want to have an email sent to you when the export process completes.
12. Click Finish.

Post-Requisites
If you did not select for Open Database After Recovery, follow the instructions in Manually Recovering a Database after V2P to complete the
database open process.

Resumable V2P
Resumable V2P is a capability that allows you to suspend a V2P operation and then resume it at a later time, without redoing any of the work
already completed. For example, any portion of a file that has already been transferred to the target environment is not re-sent. For an entire file
that has already been transferred, no part is re-sent.
The image below presents a progress bar, a stop button and a pause button while a V2P is running. To manually suspend a V2P operation:
1. Click the pause button.

691

Delphix User Guide 2016 Delphix

The next image represents a message alert generated after a V2P job has been suspended. To manually resume the job:
1. Click the play button.

Recoverable Errors
Broadly speaking, a "recoverable error" is an error condition caused by a disruption in the environment or on the target host, not errors in the
actual V2P operation. Examples of recoverable errors include:
A timeout due to a network outage
Running out of disk space on the target environment
An inability to create directories or files on the target environment
You can often address recoverable errors by taking some action to fix the problem, such as freeing up space on the target environment.

Auto-Suspend
A V2P operation that encounters a recoverable error is auto-suspended: it appears as a suspended job in the user interface (UI), with a message
detailing the error condition. Once you have fixed the error, you can simply resume the job. Alternatively, you can cancel the job. Just as when
you manually suspend and resume a job, any portion of a file that has been transferred, including possibly the entire file itself, is not re-sent when
the job resumes.

Video

Related Links
Requirements for Oracle Target Hosts and Databases

692

Delphix User Guide 2016 Delphix

Manually Recovering a Database after V2P

Customizing Oracle VDB Configuration Settings
Customizing VDB File Mappings
Move an Oracle VDB to a Physical ASM or Exadata Database

693

Delphix User Guide 2016 Delphix

Move an Oracle VDB to a Physical ASM or Exadata Database

This topic describes how to move a virtual database (VDB) into a physical database stored on Oracle Automatic Storage Management (ASM) disk
groups. This is a scripted procedure that is assisted, but not fully automated, by Delphix. A full restore of the original source ASM database from a
Delphix dSource can be achieved using this procedure. No intermediate storage is needed; the database files are moved directly from Delphix
into the source database ASM diskgroups.
This procedure applies to stand-alone and RAC databases residing on ASM disk groups, including databases residing in an Oracle Exadata
machine.

Prerequisites
Provision a VDB on the target machine that is running Oracle ASM or Exadata
Create an ASM disk group that will contain all the database files. Optionally create a separate disk group for redo log files.
Where multiple disk groups are used for datafiles, the reference move-to-asm.sh script will need to be modified. Oracle best practices
recommend a single datafile disk group.
Oracle Versions
This procedure applies to all Oracle RDBMS Versions supported by Delphix.

Procedure
1. Download the reference shell script move-to-asm.sh on the target machine where the VDB instance and ASM instance are running.
2. Ensure that Oracle environment variables ORACLE_HOME ORACLE_SID and CRS_HOME (RAC only) are correctly set for the VDB that
needs to be moved.
3. Execute the script move-to-asm.sh as the Environment User who provisioned the single instance VDB.
For a RAC VDB, the Environment User selected to execute move-to-asm.sh must be the Oracle installation owner. This is due to an
Oracle restriction that only the installation owner can invoke srvctl to add or remove database configurations.
move-to-asm.sh [-noask] [-parallel #] [-dbunique db_unique_name] <data_diskgroup> [<redo_diskgroup>]
Parameters

Description

-noask [optional]

Do not prompt for confirmation before moving the VDB. Default is to prompt.

-parallel [optional]

Number of RMAN channels used to move the VDB to ASM. Default is 8.

-dbunique [optional]

Database unique name for the resulting physical database. Default is VDB unique name.

<data_diskgroup> [required]

Target ASM disk group for data, server parameter and control files.

<redo_diskgroup> [optional]

Target ASM disk group for redo log files. Default is data_diskgroup.

694

Delphix User Guide 2016 Delphix

$ /home/ora1120/scripts/delphix/move-to-asm.sh
Usage: move-to-asm.sh [-noask] [-parallel #] [-dbunique db_unique_name]
<data_diskgroup> [<redo_diskgroup>]
$ /home/ora1120/scripts/delphix/move-to-asm.sh -noask -dbunique davis +DATA +LOG
============================================================
Virtual-to-ASM script (move-to-asm.sh v1.5) for Delphix 3.x
Copyright (c) 2013 by Delphix.
============================================================
Moving database db52temp to ASM: started at Mon Jun 10 11:48:31 EDT 2013
db_unique_name => db52
ORACLE_SID => db52
ORACLE_HOME => /opt/app/oracle/product/11.2.0/dbhome_1
Datafile diskgroup => +VIIL
RMAN Channels => 8
Generate script to move tempfiles to ASM
Generate script to drop old tempfiles
Generate script to drop offline tablespaces
Generate script to make read-only tablespaces read-write
Make read-only tablespaces read-write
Remove offline tablespaces
Updating server parameter file with ASM locations
Move spfile to ASM
Move datafiles to ASM: started at Mon Jun 10 11:49:25 EDT 2013
Move datafiles to ASM: completed at Mon Jun 10 11:56:09 EDT 2013
Startup database with updated parameters
Move tempfiles into ASM
Move Online logs
Restore any read-only tablespaces
Remove old tempfiles
Database db52 moved to ASM: completed at Mon Jun 10 11:57:19 EDT 2013
Final Steps to complete the move to ASM:
1) Delete VDB on Delphix.
2) Copy new init.ora: cp
/home/ora1120/scripts/delphix/initdb52_run8396_moveasm.ora
/opt/app/oracle/product/11.2.0/dbhome_1/dbs/initdb52.ora
3) Startup database instance.
4) Modify initialization parameters to match source and restart.
Source parameters are restored at
/home/ora1120/scripts/delphix/source_initdb52.ora
4. Alternatively, enter move-to-asm.sh as a Post Script when provisioning the VDB. This will provision and move the VDB into ASM
diskgroups in a single flow.
You must specify the -noask option to execute in non-interactive mode. For example:
/delphix/scripts/move-to-asm.sh -noask -parallel 10 +DATA +REDO
See Using Pre- and Post-Scripts with dSources and SQL Server VDBs for more information.

CRS_HOME Environment Variable for Releases Prior to 3.1.4

For releases prior to 3.1.4, move-to-asm.sh must be modified to add the CRS_HOME environment variable for RAC VDB target
environments.

695

Delphix User Guide 2016 Delphix

Example: Restoring a RAC ASM Database from a dSource TimeFlow

Source Database: db_unique_name = proddb, db_name = proddb
4 RAC Instance ORACLE_SID = prod1, prod2, prod3, prod4.
All datafiles are contained in ASM diskgroup +DATA
Redo log files are in diskgroup +LOG.
1. Shut down all RAC instances for proddb. The entire database must be shut down before a full restore.
Issue srvctl stop database -d proddb
2. Remove all files in the +DATA and +LOG diskgroups using asmcmd.
3. Provision a VDB from the proddb dSource timeflow to RAC node 1 (SID prod1) with a Post Script to move into ASM:
a. In the Provision VDB wizard, set Database Unique Name to proddbtemp, set SID to prod1, set Database
Name to proddb.
b. Set Post Script to /delphix/scripts/move-to-asm.sh -noask -dbunique proddb +DATA +LOG
This method preserves the Database Unique Name, Database Name and SID of the original source database when restoring from a
dSource timeflow.
Script Output
The move-to-asm.sh script generates several output files. These files are all written to the working directory of the script:
1. move-to-asm.sh_<oracle_sid>_run<process-id>.log

the log file for the operation

2. init<oracle_sid>_run<process-id>_moveasm.ora the init.ora parameter file created for the

ASM DB instance
3. source_init<oracle_sid>.ora the init.ora for the source database (from which the VDB was
created)

Post-Requisites
Final steps to be manually executed are displayed when the script completes and are written to the execution output log.
1. Delete the Delphix VDB that was moved.
2. For Single Instance only: copy generated init.ora parameter file to the default $ORACLE_HOME/dbs/init<$ORACLE_SID>.ora
3. For Single Instance only: startup the physical database that will now run on ASM.
A RAC database is automatically started up by the move-to-asm.sh script using srvctl.
4. Modify initialization parameters to match the original source database parameters, if necessary.
As a convenience to assist with this step, the source database parameters are restored as source_init<$ORACLE_SID>.ora

Related Links
Requirements for Oracle Target Hosts and Databases

696

Delphix User Guide 2016 Delphix

V2P with a SQL Server VDB

This topic describes how to perform the Virtual to Physical (V2P) process with a SQL Server virtual database (VDB).

Procedure
1. Log into the Delphix Admin application as a Delphix Admin user, or group or object owner.
2. Select the dSource or VDB you want to export.
3. Select the snapshot of the dSource or VDB state you want to export.
4. If you want to export the state of the database from a specific point in time, slide the LogSync slider on the top of the snapshot card to
the right, and then select the point in time from which you want to create the export.
5. Click V2P or Deploy.
6. Select the target environment.
7. Enter the Target Directory for the export.
The target directory you enter here must exist in the target environment, and you must have permission to write to it. See Requirements
for SQL Server Target Hosts and Databases for more information on user requirements for target environments.
8. Select an option for Run recovery after V2P.
If you select No, you can use the scripts that are created in the target environment to manually recover the database at a later time. See
Manually Recovering a Database after V2P for more information.
9. Click Advanced to customize the target directory layout. See Customizing Target Directory Structure for Database Export for more
information.
10. Click Next.
11. Select whether you want to have an email sent to you when the export process completes, and then click Finish.

Post-Requisites
If you selected No for Run Recovery after V2P, follow the instructions in Manually Recovering a Database after V2P to complete the V2P
process.

Related Links
Requirements for SQL Server Target Hosts and Databases
Manually Recovering a Database after V2P

697

Delphix User Guide 2016 Delphix

V2P with a PostgreSQL dSource or VDB

This topic describes the procedure for performing virtual to physical (V2P) operations with a PostgreSQL VDB.

Procedure
1. Log into the Delphix Admin application as a Delphix Admin user, or as a group or object owner.
2. Select the dSource or VDB you want to export.
3. Select the snapshot of the dSource or VDB state you want to export.
4. Click V2P or Deploy.
5. Select the target environment.
6. Enter the Target Directory for the export.
The target directory you enter here must exist in the target environment, and you must have permission to write to it. See Requirements
for PostgreSQL Target Hosts and Databases for more information on user requirements for target environments.
7. Enter a Port Number.
This is the TCP port the exported database will listen on.
8. Click Advanced to customize the target directory layout, or enter any database configuration parameters.
See Customizing Target Directory Structure for Database Export, Customizing PostgreSQL VDB Configuration Settings for more
information.
9. Click Next.
10. Review the Target Environment configuration information, and then click Finish.

Related Links
Requirements for PostgreSQL Target Hosts and Databases
Customizing Target Directory Structure for Database Export
Customizing VDB Configuration Settings

698

Delphix User Guide 2016 Delphix

V2P with an SAP ASE dSource or VDB

This topic describes the procedure for exporting a virtual database (VDB) to a physical one, also known as V2P.
Requirements
Procedure
Related Links

Requirements
Before you perform the V2P operation, you must have created a database on the target instance into which you will load the exported data. It
must be sufficiently large, and you must have created it with the for load SAP ASE option.
The Delphix Engine will initiate a load command using the database specified. The V2P operation will overwrite any existing data in this
database.

Procedure
1. Login to the Delphix Admin application as a Delphix Admin user, or as a group or object owner.
2. Select the dSource or VDB you want to export.
3. Select the snapshot of the dSource or VDB state you want to export.
4. Click V2P.
5. Select the target environment.
6. Under Installation, select which instance that you want to export to.
7. Enter the Name of the database on the target instance into which you want to load the exported data.
8. Select whether or not to Run Recovery After V2P. When this option is set, the Delphix Engine will online the database when the export
is done.
9. Click Next.
10. Select whether you want to have an email sent to you when the export process completes.
11. Click Finish.

Related Links
Requirements for SAP ASE Environments

699

Delphix User Guide 2016 Delphix

Manually Recovering a Database after V2P

This topic describes how to manually recover a database after the V2P process.
If you select No as the option for Run recovery after V2P during the V2P export process, you can use the scripts that are created in the script
directory for your database instance in the target environment to manually recover the database.
V2P for PostgreSQL VDBs
This does not apply for PostgreSQL since after V2P PostgreSQL VDBs are automatically recovered by the Delphix Engine.

Procedure
1. In the V2P target environment, navigate to the scripts directory for your exported database instance.
You can find the scripts in a sub-directory named for that specific database instance. For Oracle databases, the path is <target_dire
ctory>/<db_unique_name>/script/<instance name> . For SQL Server databases, the path is <target_directory>\<db_n
ame>\scripts.
2. For Oracle databases, locate the scripts recover-vdb.sh and open-vdb.sh. Run them in that order.
For SQL Server databases, locate the script Provision.ps1 and run it.
3. For SQL Server databases, when the script completes, Refresh the target environment for it to discover the recovered database.
For Oracle databases, add the recovered database to /etc/oratab and Refresh the target environment for it to discover the recovered
database.

700

Delphix User Guide 2016 Delphix

Customizing Target Directory Structure for Database Export

This topic describes how to customize the target directory layout for database export.
In the V2P export process, it may be necessary to customize the target directory structure which the files will be exported to. The following is the
default directory structure:
Data files: <target directory>/data
Archive files: <target directory>/archive
Temp files: <target directory>/temp
External files: <target directory>/external
Script files: <target directory>/script
Note: The example on this page uses / for file separators which is relevant for Unix and Linux environments. If the target environment is
Windows, the file separator will be \.
The following procedure describes how to customize the directory layout.

Procedure
1. During the virtual to physical export process, click Advanced in the V2P Wizard to see the target directory options.
2. You can customize any of the following:
Data Directory
Archive Directory
Temp Directory
External Directory
Script Directory
3. Each directory will then be concatenated to the Target Directory separated by the appropriate separator.
Any one of Target Directory, Data Directory, Archive Directory, Temp Directory, External Directory, Script Directory ca
n be blank. However, the combination of the fields must form an absolute path.
Data files: <target directory>/<data directory>
Archive files: <target directory>/<archive directory>
Temp files: <target directory>/<archive directory>
External files: <target directory>/<external directory>
Script files: <target directory>/<script directory>

Examples
Target directory is not empty
This means all target directories have a common root.
Input

Final Directory Layout

Target Directory: /mytarget

Data files: /mytarget/mydata

Data Directory: /mydata

Archive files: /mytarget/myarchive

Archive Directory: /myarchive

Temp files: /mytarget/mytemp

Temp Directory: /mytemp

External files: /mytarget/myexternal

External Directory: /myexternal

Script files: /mytarget/myscript

Script Directory: /myscript

Target directory is empty

All target directories may not have a common root. Note that external files and temp files share the same common root.

701

Delphix User Guide 2016 Delphix

Input

Final Directory Layout

Target Directory:
Data Directory: /mydata

Data files: /mydata

Archive Directory: /myarchive

Temp files: /mytarget/temp

Temp Directory: /mytarget/temp

External files: /mytarget/external

External Directory: /mytarget/external

Script files: /myscript

Archive files: /myarchive

Script Directory: /myscript

Target directory is empty and data directory /

Combined with Customizing VDB File Mappings, exporting data files to separate file systems is possible. In this example, a.dbf and b.dbf c
an be exported to /filesystem1 and /filesystem2 resectively.
Input

Final Directory Layout

Target Directory:
Data Directory:
Archive Directory: /myarchive

Data files:/
/filesystem1/a.dbf
/filesystem2/b.dbf

Temp Directory: /mytarget/temp

Archive files: /myarchive

External Directory: /mytarget/myexternal

Temp files: /mytarget/mytemp

Script Directory: /myscript

External files: /mytarget/myexternal

File mappings:
a.dbf : /filesystem1/a.dbf
b.dbf : /filesystem2/b.dbf

Script files: /myscript

Target directory is empty and one of the sub directories is empty would result in error
Input
Target Directory:
Data Directory: /mydata

Final Directories
INVALID

Archive Directory:
Temp Directory: /mytarget/temp
External Directory: /mytarget/myexternal
Script Directory: /myscript

702

Delphix User Guide 2016 Delphix

V2P with Unstructured Files

This topic describes the procedure for performing virtual to physical (V2P) operations with unstructured files.
V2P Not Supported for Unstructured Files on Windows
V2P is not supported for unstructured files on Windows environments. Similar results to V2P may be achieved by provisioning a vFiles
and copying data out of the vFiles to the local machine.

Procedure
1. Log into the Delphix Admin application as a Delphix Admin user, or as a group or object owner.
2. Select the dataset you want to export.
3. Select the snapshot you want to export.
4. Click V2P or Deploy.
5. Select the target environment.
6. Enter the Mount Path for the export.
The directory you enter here must exist in the target environment, and you must have permission to write to it. See Managing Unix
Environments for more information on user requirements for target environments.
7. Click Next.
8. Review the Target Environment configuration information, and then click Finish.

Related Links
Managing Unix Environments
Virtual to Physical: An Overview

703

Delphix User Guide 2016 Delphix

V2P with a MySQL VDB

This topic describes how to perform the Virtual to Physical (V2P) process with a MySQL virtual database (VDB).

Procedure
1. Log into the Delphix Admin application as a Delphix Admin user, or as a group or object owner.
2. Select the dSource or VDB you want to export.
3. Select the snapshot of the dSource or VDB state you want to export.
4. Click V2P or Deploy.
5. Select the target environment.
6. Enter the Target Directory for the export.
The target directory you enter here must exist in the target environment, and you must have permission to write to it. See Requirements
for MySQL Server Target/Staging Hosts and Databases for more information on user requirements for target environments.
7. Enter a Port Number.
This is the TCP port the exported database will listen on.
8. ClickAdvanced to customize the target directory layout, or enter any database configuration parameters.
See Customizing Target Directory Structure for Database Export, Customizing MySQL VDB Configuration Settings for more
information.
9. Click Next.
10. Review the Target Environment configuration information, and then click Finish.

Related Links
Requirements for MySQL Server Target/Staging Hosts and Databases
Customizing Target Directory Structure for Database Export

704

Delphix User Guide 2016 Delphix

_Delphix Masking

705

Delphix User Guide 2016 Delphix

Delphix Masking Quick Start Guide - An Overview

Purpose of this Quick Guide
What Is Delphix Masking?
Common Use Cases
Masking Production Data for Non-Production Environments
Before You Begin
Delphix Masking Engine Workflows
Prepare Data for Masking
Create and Run a Simple Masking Job
Provision a Masked VDB
Advanced Integrated Masking Workflows
Related Links

Purpose of this Quick Guide

The Masking Engine Quick Start Guide is aimed at all users interested in using the Masking Engine in conjunction with Data as a Service Engine.
This guide serves as a brief overview and refresher of important Masking Engine concepts as well as a guide for the common masking workflows
when using either and or both the Masking Engine and Data as a Service Engine. The workflows below describe different options and
configurations available for masking virtualized data using both the Masking Engine along with the Data as a Service Engine.

What Is Delphix Masking?

Delphix Masking combines the Data as a Service Engine with the Masking Engine to provide the ability to provision, mask, and manage data in a
standardized and automated way. Masking technology works behind the scenes to replace sensitive data with fictitious data, which you can then
move out of your production environment and into non-prod environments.

Common Use Cases

Masking Production Data for Non-Production Environments
Developers commonly need access to data from the production environment when they are:
developing new applications
maintaining or enhancing existing applications
working in test environments to test the functionality of applications
Production data commonly includes sensitive information that by law needs to be protected. However, it is not uncommon in the app/dev life
cycle for the same sensitive data that is found in production to appear in non-production environments used for application development and
testing.
The masking features in the Masking Engine can be used to ensure that application/test environments do not transmit the sensitive information
contained in the parent source. The Masking Engine removes or alters sensitive information without changing the character of the production
data, allowing developers and testers to work with the highest quality test data for software development.

Before You Begin

Before getting started, familiarize yourself with the terminology in the Masking Engine Terms Overview. The Masking Engine introduces new
terms and concepts that may not be familiar to a Delphix administrator or user.
You will also need a fully installed Masking Engine prior to performing the workflows on this page. If your Masking Engine is not yet configured,
see the guide at: Masking Engine Install, System Configuration, and Network Setup.

Who is using this

deployment type?

Standalone Masking Engine

Combined Data as a Service Engine and Masking Engine

Masking installations on Delphix 4.x

Masking installations on Delphix 5.0 and above

706

Delphix User Guide 2016 Delphix

Installation and
deployment details

Masking Engine - see Masking Engine

Install, System Configuration, and
Network Setup

Data as a Service Engine - Includes the Masking Engine. See Installin

g the Delphix Engine.
Once the Delphix Engine is installed, a ticket may be filed with Delphix
Support to enable the Masking Engine.

Delphix Engine - see Installing the

Delphix Engine for your release version.
Where to Log In

http://<Masking Engine IP or DNS

name>:8282/dmsuite

Initial Requirements
for all Masking
Activities

In the Masking Engine interface:

http://<Delphix Engine IP or DNS name>:8282/dmsuite

1. Prepare data for masking.

2. Create a masking job.
For detailed instructions, see Prepare Data for Masking and Mask Data.

To mask data

Once a masking job has been created, you

can run it either:

Masking jobs can be created in the Masking Engine GUI and run via the
GUI or API just like Standalone Masking Engines.
You can also use the Data as a Service Engine GUI to provision
masked virtual databases (VDBs). See Provisioning Masked VDBs fo
r more details.

Via the GUI

Via the API

Post-Masking
Features

Secure replication with Selective Data Distribution.

Integrated management of Masked VDBs in Jet Stream

Delphix Masking Engine Workflows

Ultimately, the way you use the Delphix Masking Engine will depend on your business needs and security practices. However, there are several
common workflows that you will need to understand in order to perform various masking tasks.

Prepare Data for Masking

1. Link a dSource.
2. Provision a normal VDB in the Delphix Engine.
To learn more, visit Prepare Data for Masking

Create and Run a Simple Masking Job

To create and run a simple masking job in the Masking Engine:
1. Identify all sensitive data.
2. Select methods for securing data.
3. Validate that the methods will work for your needs.
4. Implement and create new masking jobs for your target environments.
To learn more, visit Masking Engine Activities. If you are interested in running jobs through the API for automation, you can learn more at Maski
ng API Calls to Run a Masking Job

Provision a Masked VDB

1. Associate masking jobs with a dSource in the Delphix Engine Admin console.
2. Use the dSource provision wizard to provision a VDB with a masking job.
3. Provision from a masked VDB to create a new masked VDB in the Delphix Engine.
To learn more, visit Provisioning Masked VDBs.

707

Delphix User Guide 2016 Delphix

Advanced Integrated Masking Workflows

Other advanced workflows include using masked VDBs for selective data distribution and Jet Stream.
To learn more, visit Advanced Integrated Delphix Masking Workflows.

Related Links
Masking Engine Terms Overview
Masking Engine Install, System Configuration, and Network Setup
Prepare Data for Masking
Masking Engine Activities
Provisioning Masked VDBs
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflows

708

Delphix User Guide 2016 Delphix

Masking Engine Terms Overview

Before getting started with the Masking Engine, an overview of universal terms and concepts will build and unify how different masking
components come together. The following provides a brief overview of eight key concepts for masking: provisioning, and working with
applications, environments, connections, rule sets, profiling, inventory, and algorithms while masking data in place.
Masking Engine Types
Provision Data
Understanding Environments and Applications
Understanding Connections
Understanding Rule Sets with Domains
Understanding Profiling
Understanding Inventory
Understanding Algorithms
Understanding Masked Data
Mask Data in Place
Related Links

Masking Engine Types

There are two primary Masking Engine types.
Standalone Masking Engine - This Engine is deployed as an OVA in a compatible hypervisor and contains the Masking Engine GUI.
From here you can create masking jobs, mask data, and administer your Masking Engine. This Engine type is suitable for Delphix
installations below Delphix 5.0.
Combined Delphix Engine and Masking Engine - This Engine is built into your Delphix 5.0 and above installation. It contains both the
Delphix Engine GUI and Masking Engine GUI, and allows tighter integration between Delphix's Data as a Service and Masking features.
For more information about these types of Masking Engine deployments, read the Before You Begin section in Delphix Masking Quick Start
Guide - An Overview.

Provision Data
Delphix allows you to provision data from a linked source to the target you choose. This flexibility empowers development and testing teams to
procure fresh, secure data from a source environment and move it to a non-production environment whenever they need it.

Understanding Environments and Applications

Environments define the scope of work in the Masking Engine. The masking environment is a collection of masking constructs (connectors, rule
sets / inventories, and jobs) that support masking for a given application environment. In order to mask databases and files within the Delphix
Engine, you first need to create an environment in which the Delphix Engine will store the connection information and masking rules for those data
stores. An environment can contain multiple database connections and multiple file connections. Environments are connected to applications for
informational purposes. For example, an integrated test environment can have multiple applications.
An application refers to the IT assets (programs, data, processes) that support a business function. For example, if a bank offers payroll services
to its clients, there would be an application in its IT division to support that business. If the bank develops code to support new functions for its
payroll application, the IT division would have environments where code is developed and tested. These environments contain test data used to
test the new code. The test data is masked to support data privacy requirements.

Understanding Connections
Delphix stores JDBC database connection information in an object called a "connector." You can discover a list of connectors within an
environment by going to Environment Overview and then clicking the Connector tab. The connection includes fields such as database name, h
ost, user id and password, and port. It is specific to the DBMS type you select. This builds a connector between the source database and the
masking interface.

Understanding Rule Sets with Domains

A "rule set" points to a collection of tables or flat files that the Masking Engine uses for masking data. The rule set allows you to identify, select,
and configure which tables you need to mask. For those tables that do not have a primary key defined, you can define a logical key with a
combination of columns (or ROWID for Oracle database).

709

Delphix User Guide 2016 Delphix

Understanding Profiling
Profiling is a major component of the Masking Engine. The objective of profiling is to identify the location of Non-Public Information (NPI) or
sensitive data if you are unsure of what data needs to be masked in the first place. Profiling data is not necessary when you have already
identified the sensitive data you need to mask.
The Delphix profiler uses two different methods to identify the location of sensitive data:
Searching through the column names in the target database by querying the database catalog (metadata)
Looking at the data itself, using a sampling algorithm, to see whether there is any sensitive data. This is especially useful for files and
comment and notes fields in a database.

Understanding Inventory
The Delphix Engine automatically stores the masking rules for each sensitive column in the Delphix repository database in the environment's
"inventory." When you select a table to mask, its columns will appear, and you can select them for masking. Afterwards, you can edit the columns
with an appropriate algorithm required for masking.

Understanding Algorithms
Algorithms are how the Masking Engine masks sensitive data. From the Settings tab, click Algorithm on the left-hand side, and the list of
algorithms appears for you to select. The following algorithms are the most commonly used methods for masking:
Secure Lookup Algorithm Uses a lookup file to assign masked values in a consistent manner
Segmented Mapping Algorithm Replaces data values based on segment definitions. For example, an ACCOUNT NUMBER algorithm
might keep the first segment of an account number but replace the remaining segments with a random number.
Secure Shuffle algorithm A user-defined algorithm assigned to a specific column. Secure shuffle automates the creation of a secure
lookup algorithm by building a list of replacement values based on the existing unique values in the target column and creating a secure
lookup using those values. In that respect, it is simply shuffling the values.

Understanding Masked Data

After you create a masking environment, connection, rule set, and inventory, you can mask data.
The Delphix Engine will maintain Referential Integrity (RI) by masking each field with the same algorithm. This repeatable masking automatically
maintains RI (for verbatim matches), even if it is between applications or platforms.
As a practical example, assume you have an Social Security Number (SSN) column in a Microsoft SQL Server database, an SSN column in a
DB2 database, and an SSN field in a tab-delimited file. If the SSN value was 111111111 across the two databases and the file, and you use the
same SSN algorithm for all three, the masked value (for example, 801-01-0838) will be the same for all three.
Note: When defining a masking job, select mask data in place.

Mask Data in Place

"Mask data in place" refers to updating a database with masked data. This includes reading data from the table defined in the rule set, masking
the data in the Masking Engine, and updating the tables with the masked data.

Related Links
Quick Start Masking Engine Overview
Masking Engine Install, System Configuration, and Network Setup
Prepare Data for Masking
Masking Engine Activities
Provisioning Masked VDBs
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflow

710

Delphix User Guide 2016 Delphix

Masking Engine Install, System Configuration, and Network Setup

Installation Overview
Delphix and Masking Engine Combined Installation
Standalone Masking Engine Installation
Next Steps
Related Links

Installation Overview
Installations of Delphix 5.0 and above include the Delphix Masking Engine. This combination of the Delphix Data as a Service Engine and
Masking Engine provides tight integration and enables additional features such as Selective Data Distribution.
Both installation types require:
A Delphix Support Account
The appropriate installation file for your supported hypervisor (e.g. VMWare) and installation type from Delphix Downloads
If you are installing Delphix 5.0 or above, start here: Delphix and Masking Engine Installation
If you are not running Delphix 5.0 or above, and want to install the latest Masking Engine, start here: Standalone Masking Engine Installation
If you are unsure of which Masking Engine is right for you, please contact your Professional Services team or Delphix Support.

Delphix and Masking Engine Combined Installation

Every Delphix 5.0 and above engine includes the Masking Engine. For this installation type:
1. Download Delphix 5.0 or above from Delphix Downloads using your Support credentials.
2. Install the Delphix Engine 5.0 or above. For requirements and details, see Installing the Delphix Engine.
3. Create a ticket through Delphix Support to enable masking functionality on your Delphix Engine.
4. Connect to the Masking Engine at: http://<Delphix Engine IP or DNS name>:8282/dmsuite as the user delphix_admin and password Del
phix_123.
Click here to proceed to next steps once your Masking Engine is installed and enabled.

Standalone Masking Engine Installation

If the Masking Engine is required but not included in your Delphix Engine (i.e. your Delphix Engine is below version 5.0), it is possible to install a
Standalone Masking Engine.
1. Download the Standalone Masking Engine 5.0 or above from Delphix Downloads using your Support credentials.
2. Deploy the downloaded OVA on a supported hypervisor using the following minimum requirements:
a. 16 GB RAM
b. 8 vCPU Cores
c. 50GB of disk will be automatically provisioned for Masking Engine metadata.
d. IP binding to a persistent address if DHCP will be used for the Masking Engine (the Masking Engine IP address should not
change).
3. If you are unable to use a persistent IP address for your Masking Engine guest, the Masking Engine must be configured to use a static IP
after deployment.
a. Contact Delphix Support or your Professional Services team. This operation requires root access to the Masking Engine, and a
member of these teams will need to enter the password via Webex to log in. Once they have logged you in, you can proceed
with the following steps.
b. Edit /etc/sysconfig/network-scripts/ifcfg-eth0.
c. Change BOOTPROTO=dhcp to BOOTPROTO=static.
d. Add a line IPADDR=<your IP address>.
e. Add a line NETMASK=<your netmask>.
f. Edit /etc/sysconfig/network.
g. Add a line GATEWAY=<your gateway IP>
h.
711

Delphix User Guide 2016 Delphix

h. /etc/init.d/network restart
i. Edit /etc/resolv.conf.
j. This may have been picked up correctly by dhcp, otherwise modify the nameserver to map to the correct DNS server(s)
k. If necessary, edit the firewall.
l. By default, the firewall is disabled, meaning that /etc/init.d/iptables status shows not running. If this needs to be
enabled, open the port 8282 for access to the UI as well as any ports needed to connect to their database servers.
m. Stop and start the Masking Engine from the root prompt with the following commands:
i. cd /opt/dmsuite
ii. ./stop_all.sh
iii. ./start_all.sh
4. Connect to the Masking Engine at: http://<IP or DNS name>:8282/dmsuite as the user delphix_admin and password Delphix_123.
Click here to proceed to next steps once your Masking Engine is installed and enabled.

Next Steps
Prepare Data for Masking
Masking Engine Activities

Related Links
Quick Start Masking Engine Overview
Prepare Data for Masking
Masking Engine Activities
Provisioning Masked VDBs
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflow
Installing the Delphix Engine

712

Delphix User Guide 2016 Delphix

Prepare Data for Masking

Link a dSource
Follow the detailed steps found in the documentation: Link an Oracle Data Source

Provision a VDB to Prepare to Configure a Masking Job

In order to prepare data for masking, you must first provision a virtual databases (VDBs) in the Delphix Engine. If you would like, a second may be
provisioned to validate against. To do so, repeat these steps.
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select a dSource and a dSource snapshot.
6. Click Provision.
7. Review the information for Installation Home, Database Unique Name, SID, and Database Name. Edit as necessary.
8. Review the Mount Base and Environment User. Edit as necessary.
9. If you want to use login credentials on the target environment that are different from the login credentials associated with the Environme
nt User, select Specify Privileged Credentials.
10. Click Next.
11. Select a Target Group for the VDB and a Snapshot Policy for the VDB.
12. Click Next.
13. Specify any Pre or Post Scripts that should be used during the provisioning process.
14. Click Advanced to select Oracle Node Listeners or enter any VDB configuration settings or file mappings.
15. Click Next.
16. Click Finish.

Next Steps
Masking Engine Activities
Create Data Masking Rule Sets, Algorithms, and Inventories
Mask Data

Related Links
Quick Start Masking Engine Overview
Prepare Data for Masking
Masking Engine Activities
Provisioning Masked VDBs
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflow
Link an Oracle Data Source

713

Delphix User Guide 2016 Delphix

Masking Engine Activities

Login to the Masking Engine
User Roles
Next Steps
Previous Steps
Related Links
Once you have provisioned a virtual database (VDB) for masking use in the Delphix Engine, you will need to complete the following activities in
the Masking Engine. The five primary tasks to be completed are:
adding a masking application
adding a masking environment
adding a connector to the newly provisioned VDB
defining the rules and profiles for masking
creating the masking job
Below is a visualization of this data masking user workflow:

Login to the Masking Engine

1. Login to a web browser that points to http://<server_or_IPAdress>:8282/dmsuite
2. Enter default username: delphix_admin.
3. Enter default user password: Delphix_123.
4. The auto default user role is the Administrator role.

User Roles
The Masking Engine has a built-in Administrator role, which gives you complete access to masking functions. As an administrator, you can
access, update, and delete all environments, and all objects within those environments. You can also add roles in the roles settings.
Note: Defining new environments and connections requires different privileges than building masking jobs.
Once logged into the Masking Engine, you can complete the activities needed for masking under the Environments tab, seen below:

714

Delphix User Guide 2016 Delphix

Next Steps
Add an Application and Create a New Environment and Connector
Create Data Masking Rule Sets, Algorithms, and Inventories
Mask Data

Previous Steps
Prepare Data for Masking

Related Links
Quick Start Masking Engine Overview
Provisioning Masked VDBs
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflow

715

Delphix User Guide 2016 Delphix

Add an Application and Create a New Environment and Connector

Add an Application
Select an Environment and Create a Connector
Next
Related Links

Add an Application
In order to mask, you first need to add an application and create an environment to store the connection information and the masking rules for the
data store.
1. Click Add Application.
2. Enter an Application Name.

3. In the upper right-hand side of the screen, click Add Environment. The screen prompts you for the following items:
a. From the Application Name drop-down menu, select the name of the application associated with this environment, for
informational purposes. An integrated test environment can have multiple applications.
b. Enter an Environment Name.
This will be the display name of the new environment.
c. From the Purpose drop-down menu, select Mask.

716

Delphix User Guide 2016 Delphix

4. Either:
Click Save to return to the Environments List/Summary screen,
or
Click Save & View to display the Environment Overview screen.

Select an Environment and Create a Connector

After you create a new environment, it will appear in the user interface (UI). You can then create connections by doing the following:
1. Click an Environment name.
2. From the Environment Overview screen, click the Connector tab.
The Connector List screen appears.
3. In the upper right-hand region of the Connectors Editor, click Create Connection.
The Create Connection window appears, prompting you for connection information for the database.
4. For Type, select the appropriate database type for example, Database Oracle.
5. Enter the required information such as the connection name, database name, host name or IP, port, and login credentials.
6. Click Save. You will be returned to the Connector List screen, where you can add additional connectors if necessary.

717

Delphix User Guide 2016 Delphix

After you create an environment and connectors, you need to define a rule set. See the following activity for how to do this.

Next
Create Data Masking Rule Sets, Algorithms, and Inventories

Related Links
Masking Engine Activities
Create Data Masking Rule Sets, Algorithms, and Inventories
Mask Data

718

Delphix User Guide 2016 Delphix

Create Data Masking Rule Sets, Algorithms, and Inventories

Create a Rule Set
Edit a Rule Set
Review Masking Inventory, Configure Columns with Domains and Algorithms
Optional Steps (Not required)
Create a New Profile of Data Using the Masking Inventory
Profiling Data
Next
Mask Data
Related Links
All rule sets need a name as well as the connector information you previously created. After you provide this information, you will see a list of
tables that is owned by the schema owner defined in the connector. This enables you to select the tables you want to mask. Below is a
step-by-step description for how to create a rule set.

Create a Rule Set

1. In the Environments tab, click the Rule Set tab.
2. In the upper right-hand corner of the Rule Set tab, click +Create Rule Set.
The Create Rule Set screen appears. This screen lets you specify which tables belong in the rule set.
Note: A similar screen appears when you edit a rule set.

Edit a Rule Set

1. Click the name of an environment.
2. Click the Rule Set tab.

719

Delphix User Guide 2016 Delphix

3. In the upper right-hand corner of the Rule Set tab, click the Edit (pencil) icon for the rule set you want to edit.
The Create Rule Set screen appears, allowing you to specify which tables belong in the Rule Set.
a. Enter a Name for your rule set.
b. Select a Connector name from the drop-down menu.
The list of tables for that connector appears.
c. To select individual tables, click their names in the list to the right. Alternatively, click Select All in the bottom left to select all the
tables.
d. Click Save.
You are returned to the Rule Set screen.
4. To see the list of tables that you selected, click the name of the newly-created rule set.
5. Optionally, for each table, if there is no primary key for that table, click Edit Table and define the logical key, as seen in the screenshot
below:

720

Delphix User Guide 2016 Delphix

The following section describes how to define the columns to mask for each table in the rule set.

Review Masking Inventory, Configure Columns with Domains and Algorithms

After selecting tables (connectors) and defining a rule set, which you did in the preceding section, you are ready to configure the columns in the
masking inventory. When you defined a rule set, an empty inventory was automatically created. Manually edit the columns with sensitive data to
assign a domain and algorithm by clicking the pencil icon at the end of the inventory row.
1. Click Inventory.
2. Select the rule set you want to mask.
3. Click Contents to list all the tables or files defined for the rule set.
4. Select a table. All the contents in the table will appear.
If a column is a primary key (PK), a Foreign Key (FK), or an index (IDX), an icon indicating this will appear to the left of the
column name. If there is a note for the column, a Note icon will appear. To read the note, click the icon.
If a table, metadata for the column appears: Data Type and Length (in parentheses). This information is read-only.
5. To mask or unmask a column, click Edit and choose the appropriate domain for the column.
6. The selected domain will open a corresponding algorithm. If needed, you can select a different algorithm from the drop-down list. Based
on the column you are masking, you may decide to choose one of the following three algorithms:
Secure Lookup Algorithm
Segmented Mapping Algorithm
Secure Shuffle Algorithm
7. Complete the presented form to the right that corresponds to your selected algorithm.
8. Click Save.
If you have already selected a column to be masked and you want to undo this:
1. Click the Edit (pencil) icon for that column.
2. In the Edit Properties dialogue box, reset the DOMAIN element to Choose Domain. You will exclude that column from being masked.
Please refer to the screenshot below:

Optional Steps (Not required)

Create a New Profile of Data Using the Masking Inventory
If you are unsure what data you want to mask, a good practice is to profile data by updating an inventory of your data with sensitive data elements
identified. You can then review and edit that inventory.
1. From your environment's Overview tab, click the Profile button.
The Create Profile Job screen will appear.
2. Enter a Job Name.
3.
721

Delphix User Guide 2016 Delphix

3. Select your rule set.

4. Select a profile set, which will be created when you set up your masking security policy or one of the provided profile sets.
5. Click Save. The job will appear on your overview screen.

Profiling Data
1. Create a profiling job using the steps above.
2. Run the profiling job you just created. When you run this profiling job, it updates/populates an inventory.

3. Click the Profile Job name to see the results.

4. Click the Results sub-tab. You should see the name columns appear as sensitive.
5. If you want to download a PDF report of the sensitive fields that have been profiled, click the profiling report.

722

Delphix User Guide 2016 Delphix

6. To view the inventory, click the Inventory tab while in an Environment Overview.
7. Examine the inventory to ensure that the profiling job has included everything you want to mask. For example, if you selected a First
Name field, you probably want the Last Name field as well. You can see which columns were selected for masking by selecting the
associated rule set. Make sure that you have included all sensitive data elements, such as personal identifying information, from the table
that you want to mask.
8. Modify the inventory, if necessary.
When a profiling job runs, it automatically updates the inventory for the given rule set. If you do not want the Profiler to automatically update the
inventory, change the ID Method to User.

Next
Mask Data
Related Links
Masking Activities
Add an Application and Create a New Environment and Connector
Mask Data

723

Delphix User Guide 2016 Delphix

Mask Data
Create a New Masking Job
Run a New Masking Job
Validate a New Masking Job
Next Steps
Related Links

Create a New Masking Job

Now that you have identified and prepared your data for masking, you can create a new masking job and confirm it.
1. Select Mask.
The Create Masking Job window appears.
2. Choose appropriate rule settings. You will be prompted for the following information:
Job Name A free-form name for the job you are creating. Must be unique across the entire application.
Masking Method Select In-Place.
Multi Tenant Check this box to allow this job to be used with multiple databases.
Provision Masked VDBs
A job must be Multi Tenant to use it when creating a masked virtual database (VDB).

Rule Set Select a rule set against which this job will execute.
2. When you are finished, click Save.

Run a New Masking Job

1. Under Action, click Run to run the masking job.
2. Click the job to view the progress of the masking job.

Validate a New Masking Job

If you want to validate the masking job, compare the VDB you have masked to another copy of the data, such as another VDB. Check the results
of the masking job by using a SQL tool such as SQL Developer to check that the fields were masked.
You can use the Certify button to create a masking certification job that will check for polluted columns for example, columns that contain a
value that is not in the secure lookup table. You can also use sqlplus on the target VDB machine to check the masked fields.

724

Delphix User Guide 2016 Delphix

Next Steps
Provisioning Masked VDBs

Related Links
Quick Start Masking Engine Overview
Masking Engine Activities
Add an Application and Create a New Environment and Connector
Create Data Masking Rule Sets, Algorithms, and Inventories
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflow

725

Delphix User Guide 2016 Delphix

Provisioning Masked VDBs

Prerequisites
Ways to Run a Masking Job on a VDB
Identifying and Navigating to Masked VDBs in the Delphix Engine
Restrictions
Workflow Overview to Provision Masked VDBs in the Delphix Admin Console
Associate a Masking Job with the dSource
Provisioning a Masked VDB using the dSource Provisioning Wizard
Refresh a Masked VDB
Disassociate a Masking Operation on a dSource
Masked VDB Data Operations
Continue to Next Steps
Related Links
Masked virtual databases (VDBs) function just like normal VDBs. The only distinction is that the data they contain has been masked by a masking
job. Masked VDBs can be selectively distributed to a separate Delphix Engine (in non-prod) without sending the original data that was obfuscated
during masking. This topic describes how to work with masked VDBs.

Prerequisites
Delphix Masking Pre-Configuration Activities
If you are configuring Delphix Masking for the first time, you must complete all of the activities below in order.
1. Install the Combined OVA.
2. Prepare Your Data.
3. Configure, Create, and Test a Simple Masking Job.
a. Add an Application.
b. Create Data Masking Rule Sets.
VDB Snapshot Required
Take a VDB snapshot before masking data. This is required to bring the changes into Delphix if you are going to be
provisioning masked VDBs.

c. Mask Data.
Mask Data for Provisioned Masked VDBs
A masking job must be Multi Tenant to use it when creating a masked virtual database (VDB).

726

Delphix User Guide 2016 Delphix

Ways to Run a Masking Job on a VDB

You will always need to configure and test new masking jobs in the Delphix Masking Engine as described in the Prerequisites. Once it has been
completely defined, you can run the masking job in the following ways:
Working in the Delphix Engine Admin Console using the dSource Provisioning Wizard
Working in the Delphix Masking Engine
Using the Masking API to Run a Masking Job Command

Identifying and Navigating to Masked VDBs in the Delphix Engine

Masked VDBs appear in the lef-handt sidebar, just like regular VDBs. They are most obviously identified by the different icon used to represent
them in the left-hand sidebar. A masked VDB will also contain information about the masking job that was applied to it on its database card.
Generally, anything you can do with an unmasked VDB is also possible with a masked VDB.
Masked VDB Icon on Left Sidebar

Masked VDB info in Database Card

Restrictions
Unique masking jobs cannot be selected and run on multiple VDBs simultaneously. The user interface
will allow you to assign the same masking job to multiple VDBs, but if you provision or refresh multiple
VDBs using the same selected masking job and ruleset, errors may occur with the masking jobs. To avoi
d any issues with provisioning or refreshing, and if you are using the same masking ruleset on multiple
VDBs, be sure to create a unique job for each VDB.
Provisioning masked VDBs through the Delphix Engine does not currently work with DB2. In order to mask DB2, you should use the
Masking Engine interface.
You cannot apply additional masking jobs to a masked VDB or its children.
If a masking job has been applied to a VDB, you cannot create an unmasked snapshot of that VDB.
If an existing VDB has not had a masking job applied to it, then you cannot mask that particular VDB at any point in the future. All the
data within the VDB and its parents will be accessible if it is replicated or distributed.

Workflow Overview to Provision Masked VDBs in the Delphix Admin Console

1. Associate masking jobs with a dSource in the Admin console.
2. Use dSource provision wizard to provision a VDB with a masking job.

Associate a Masking Job with the dSource

727

Delphix User Guide 2016 Delphix

To provision a masked VDB, you must first indicate that the masking job you are using is complete and applicable to a particular database. You
do this by associating the masking job with a dSource.
1. Open the database card for the dSource to which the masking job is applicable and with which it will be associated.
2. Click the Masking tab.

3. Click the pencil icon to edit. All masking jobs on this Delphix Engine that have not been associated with another dSource will be listed on
the right-hand side.

4. Select the job you want to associate with this dSource.

5. Click on the left-facing arrow.

6. Repeat for any other jobs that you want to associate with this dSource at this time.
7. Click the yellow checkmark to confirm.
The Delphix Engine now considers this masking job to be applicable to this dSource and ready for use. When provisioning from snapshots of this
dSource, this masking job will now be available.
Note: Masking jobs can also be associated with virtual sources in addition to dSources.

728

Delphix User Guide 2016 Delphix

Provisioning a Masked VDB using the dSource Provisioning Wizard

The steps required to provision a masked VDB are almost identical to the steps required to provision an unmasked VDB. Once you have created
a masked VDB, you cannot un-mask it, nor can you alter which masking job it uses. All snapshots in the VDBs timeflow will always be masked
using the masking job that you selected when you provisioned the masked VDB.
1. Select the dSource.
2. Click Provision.
3. Review the information for Installation Home, Database Unique Name, SID, and Database Name. Edit as necessary.
4. Review the Mount Base and Environment User. Edit as necessary.
a. If you want to use login credentials on the target environment that are different from the login credentials associated with the
Environment User, select Specify Privileged Credentials.
5. Click Next.
6. If necessary, edit the Target Group for the VDB and Snapshot Policy settings.
7. Select the masking job you want to use from the available drop-down menu. Only masking jobs that have been associated with the
parent dSource will be available.
Selecting Unique Masking Rulesets
If you are using the same masking ruleset on multiple VDBs, be sure to create a unique job for each VDB t o avoid any issues
when provisioning or refreshing.

8. Click Next.
9. Specify any Pre or Post Scripts that should be used during the provisioning process. If the VDB was configured before running the
masking job using scripts that impact either user access or the database schema, those same scripts should also be used here.
10. Click Next.
11. Click Finish.
In the Actions sidebar on the right-hand side of the window, there will be an action indicating that masking is running. You can verify this and
monitor progress by going to the Masking Engine page and clicking the Monitor tab.

Once you have created a masked VDB, you can provision its masked data to create additional VDBs, in the same way that you can
provision normal VDBs. Since the parent masked VDB contains masked data, descendent VDBs will only have masked data. This is a
great way to distribute multiple independent copies of masked data that is both time- and space-efficient.

Refresh a Masked VDB

You refresh a masked VDB in exactly the same way as you refresh a normal VDB. As with provisioning a masked VDB, the masking job will be
run during the refresh process.

729

Delphix User Guide 2016 Delphix

1. Login to the Delphix Admin application.

2. Under Databases, select the VDB you want to refresh.
3. From the database card, click the Refresh icon in the lower right-hand corner.

4. You will then be brought to the timeflow of the dSource from which the VDB was provisioned.
5. Select the snapshot or point in time to which you want to refresh.
6. Click Refresh.

Delphix will now update the masked VDB with the new data and mask it using the masking job with which this Masked VDB was provisioned.

Disassociate a Masking Operation on a dSource

If a masking job is found to be unsuitable or should be retired, you can disassociate it though the same database card that you used to associate
it.
1. Select the job on the left-hand side to disassociate.

730

Delphix User Guide 2016 Delphix

2. Click the right-facing arrow, as seen in the screenshot above.

Note that this will only prevent the creation of new masked VDBs with this job. It will not alter existing masked VDBs in any way. When
disassociating a job, review the existing masked VDBs and consider whether you need to delete or disable any of them.

Data Operations available to Masked VDBs are listed below:

Masked VDB Data Operations

Rewind

Alter the database to contain masked data from a previous point in time.

Procedure to Rewind an Oracle Masked VDB

Refresh

Get new data from the parent dSouce and mask it.

Procedure to Refresh an Oracle Masked VDB

Disable

Turn off the database and remove it from the host system.

Procedure to Disable an Oracle Masked VDB

Enable

Turn on the database and make it available on the host system.

Procedure to Enable an Oracle Masked VDB

Continue to Next Steps

Troubleshoot Provisioning Errors for Masked VDBs
Advanced Integrated Delphix Masking Workflows

Related Links
Troubleshoot Provisioning Errors for Masked VDBs
Quick Start Masking Engine Overview
Masking Engine Activities
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflow
Masking Engine Install, System Configuration, and Network Setup

731

Delphix User Guide 2016 Delphix

Prepare Data for Masking

Add an Application and Create a New Environment and Connector
Create Data Masking Rule Sets, Algorithms, and Inventories

732

Delphix User Guide 2016 Delphix

Troubleshoot Provisioning Errors for Masked VDBs

Avoiding and Handling Errors
It is possible that an error might occur when a masking job is run. This will cause the refresh or provision to fail, as can be seen by a failure in the
actions sidebar.

If the error message is insufficient to diagnose the problem, you can view the full Masking Engine logs.
1. From the Masking Engine page, click Admin.
2. On the left-hand side of the screen, click Logs.

Related Links
Provisioning Masked VDBs
Masking API Calls to Run a Masking Job

733

Delphix User Guide 2016 Delphix

Masking API Calls to Run a Masking Job

A limited REST API exists only to implement integration with the Delphix Engine and is not officially supported. The following procedure details
the single API to launch existing masking jobs.

Procedure
1. Login User GET dmsuite/apiV4/login?user={userID}&password={encrypted passwd}
a. Returns authorization token in HTTP header that should be used in subsequent operations
2. Get Application GET /dmsuite/apiV4/applications
a. Returns applications and environments associated to each application in response body for example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ApplicationsResponse>
<ResponseStatus>
<Status>SUCCESS</Status>
</ResponseStatus>
<Applications>
<Application>
<Name>demo</Name>
<Link href="applications/demo" rel="details"/>
<Environments>
<Link href="environments/1" rel="SAP"/>
</Environments>
<Environments>
<Link href="environments/37" rel="TEST"/>
</Environments>
</Application>
</Applications>
</ApplicationsResponse>
3. Get Job GET dmsuite/apiV4/applications/{applicationID}/jobs
a. Returns jobs in response body for example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<JobsResponse>
<ResponseStatus>
<Status>SUCCESS</Status>
</ResponseStatus>
<Jobs>
<Profiles>
<Profile>
<Name>OracleProfile</Name>
<Link rel="details" href="applications/demo/profilejobs/0"/>
<Status>Succeeded</Status>
</Profile>
</Profiles>
<Provisions/>
<Maskings>
<Masking>
<Name>OracleMasking</Name>
<Link rel="details" href="applications/demo/maskingjobs/1"/>
<Status>Succeeded</Status>
</Masking>
</Maskings>
<Certifys/>
</Jobs>
</JobsResponse>
4. Run Job POST dmsuite/apiV4/applications/{applicationID}/maskingjobs/{maskingjobID}/run
a. Returns job launch status in response body - for example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<MaskingsResponse>
<ResponseStatus>
<Status>SUCCESS</Status>
</ResponseStatus>
</MaskingsResponse>
b. For on-the-fly masking, pass the target connector in the request body environments/{environmentID}/connectors/{connectorId}?DataSource={Database,File,Mainframe}

734

Delphix User Guide 2016 Delphix

5. Get Job status - GET dmsuite/apiV4/applications/{applicationID}/maskingjobs/{maskingjobID}/results

a. Returns job run status in response body - for example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<MaskingsResponse>
<ResponseStatus>
<Status>SUCCESS</Status>
</ResponseStatus>
<Maskings>
<Masking>
<Name>OracleMasking</Name>
<Status>SUCCESS</Status>
<StartTime>16:04:00</StartTime>
<Duration>00:01:12</Duration>
<PreviousDuration>00:01:13</PreviousDuration>
<TablesTotal>1</TablesTotal>
<TablesProcessed>1</TablesProcessed>
<TablesRemaining>0</TablesRemaining>
<RowsProcessed>25</RowsProcessed>
<RowsRemaining>0</RowsRemaining>
<UpdatesRunning>4</UpdatesRunning>
<Respository>POSTGRESQL</Respository>
<Links>
<Link href="environments/1/connectors/1?DataSource=database" rel="SourceConnector"/>
<Link href="applications/demo/inventorys/Oracle?environmentId=1" rel="Inventory"/>
</Links>
</Masking>
</Maskings>
</MaskingsResponse>

Related Links
Quick Start Masking Engine Overview
Masking API Calls to Run a Masking Job
Masking Engine Activities
Provisioning Masked VDBs
Masking API Calls to Run a Masking Job
Advanced Integrated Delphix Masking Workflow

735

Delphix User Guide 2016 Delphix

Advanced Integrated Delphix Masking Workflows

Using Selective Data Distribution with Masked Data Sources
Using Jet Stream with Masked Data Sources
Related Links

Using Selective Data Distribution with Masked Data Sources

You can now replicate masked data in a VDB directly to a target Delphix engine without transmitting the
unmasked data in its parent source. To learn more or to get started, go to:
Selective Data Distribution Overview
Selective Data Distribution Use Cases
Selective Data Distribution User Interface
Configuring Selective Data Distribution
Selective Data Distribution and Failover

Using Jet Stream with Masked Data Sources

The workflows below detail both best practices and troubleshooting for how an admin user can select and use masked data sources within Jet
Stream. The figure below shows a dSource which has two masking jobs associated with it, two masked VDBs provisioned from the dSource each
masked with a different masking job, and two VDBs provisioned from the masked VDBs. With this set of objects, an admin user would place the
parent masked VDBs in a data template and use the child masked VDBs in data containers.
In order to create a data container with masked data as an admin user:
1. Provision a child masked VDB from the masked parent VDB.
2. Select the masked child VDB as a source for the container.

To learn more or to get started, go to the Jet Stream Admin Guide and follow the procedures for the following activities:

736

Delphix User Guide 2016 Delphix

Selecting Masked Data Sources in Data Templates

Selecting Masked Data Sources for Data Containers

Related Links
Selective Data Distribution Overview
Selective Data Distribution Use Cases
Selective Data Distribution User Interface
Configuring Selective Data Distribution
Selective Data Distribution and Failover
Jet Stream Admin Guide
Selecting Masked Data Sources in Data Templates
Selecting Masked Data Sources for Data Containers

737

Delphix User Guide 2016 Delphix

Masking Engine User Guide

Chapter 1: Delphix Data Masking

About Delphix and This Guide
Getting Started
Starting Delphix
Basic Tasks for a Database/File
Create or Import an Environment
Create/Define Connections
Create/Define a Rule Set
Profile Data/Define Inventory
Provision Data
Mask Data
Certify Data
Chapter 2: Delphix Components
Profiling Data
Provisioning and/or Subsetting Data
Practical Subset Example
Masking Data
Masking In-Place
On-The-Fly Masking
Masking a Primary Key Column
Certifying Data
Certification and Delta Masking
A Practical Certification Example
Chapter 3: Using Delphix
Managing Environments
The Environment List/Summary Screen
Creating or Importing an Environment
Exporting an Environment
Copying and Deleting Environments
The Environment Overview Screen

Managing Connectors
The Connector List
Creating or Editing a Connector

738

Delphix User Guide 2016 Delphix

Deleting Connectors
Database Connectors
File Connectors

Managing Rule Sets

The Rule Set Screen
Creating a Rule Set
Copying a Rule Set
Editing/Modifying a Rule Set
Deleting a Rule Set
Modifying Tables in a Rule Set

Managing the Masking Inventory

The Inventory Screen
Inventory Settings
Managing a Database Inventory
Managing a File Inventory
Importing and Exporting Inventory

Managing Jobs
Jobs on the Environment Overview Screen
Creating New Jobs
Creating a New Profiling Job
Creating a New Masking Job
Creating a New Certify Job
Creating a New Provisioning Job
Running and Stopping Jobs from the Environment Overview Screen

File Masking
Overview
File Formats
1. Mainframe and XML Files
2. Delimited, Excel, Fixed Files
Create a File Connector
Create a Ruleset
File Inventory

Tokenization
Creating a Tokenization Algorithm
Create a Domain
Create a Tokenization Environment
Create a Connection and Rule Set
Create the Rule Set and Apply File Format
Apply the Tokenization Algorithm
Create and Execute a Tokenization Job
Result Snapshot
Steps to Re-Identify
Result Snapshot

Monitor Jobs
Scheduler Tab
Scheduling Job(s) to Run
Job Completion E-mail Message

739

Delphix User Guide 2016 Delphix

Enabling and Disabling Database Constraints

Creating SQL Statements to Run Before and After Jobs

Settings Tab
Algorithms
Domains (Masking)
Profiler
Mapping
File Format
Remote Server

Admin Tab
Users
About

Risk Tab
Adhoc Reporting on the Delphix Repository
Index of Terms

740

Delphix User Guide 2016 Delphix

Chapter 1: Masking Engine Overview

Data Masking, sometimes called de-identification or redaction, is a technique used to secure your sensitive data in non-production environments
such as Development and QA by replacing sensitive data with fictitious but realistic data, eliminating the risk of exposing your sensitive data to
unauthorized parties. Delphix's unique approach to data masking involves breaking the logical association between unique identifying information
(for example, social security numbers) and personally identifiable data (for example, name and address). Delphix, uses this simple 5-step process
to protect your data and each step can be completed with a simple push of a button. Delphix processes for protecting sensitive data are
measurable, documented, and repeatable, providing clearly auditable results.
Delphix is a multi-user, browser based web application that provides complete, secure, and scalable software for your data masking and
tokenization needs, while meeting enterprise-class infrastructure requirements. There are several advantages to using the Delphix to mask your
data:
Risk reductionBy using masked data that is suitable for a large number of business activities, instead of copies of the real data, the
risk of a data breach is greatly reduced. Instead of having twenty (20) databases with sensitive data to be secured you can have just one
(1).
Profiling or Automated identification of sensitive dataThe Delphix Profiler identifies the location of sensitive data automatically
across all your databases, copybooks, and files, the time-consuming work associated with a data masking project is reduced
significantly.
Masking of sensitive dataDelphix is 10x faster in securing your data because of it's easy to use web browser interface and the fact
that there is no programming required! With Delphix, you create XML that is automatically imported.
Maintain referential integrity Delphix's patented, repeatable deterministic algorithms automatically maintain referential integrity,
not only within a database but across heterogeneous databases and file types.
Leverage investment The Delphix Engine can automatically create mappings based on the Sensitive Data inventory. This allows you
to use the powerful Extract-Transform-Load (ETL) engine within your existing infrastructure, without needing to code and maintain
hundreds or thousands of jobs. Another major advantage of the Delphix Engine is that you can use the masking algorithms deployed as
mapplets, use provided mapplets, or write your own mapplets to use with the Delphix Engine.
Enables data sharingBy sharing masked data safely and easily, relationships with partners, third parties, and outside vendors are
improved.
Lowers costsBy automating the entire masking process and securing only essential data (thereby reducing how much data to secure),
and provisioning only the data you need, costs to secure sensitive data are greatly reduced.

741

Delphix User Guide 2016 Delphix

Basic Tasks for a Database File

Whether you only plan to profile, provision and mask data, or just mask data, you need to perform certain tasks. Databases and files are dealt
with in a similar but slightly different way.
You need to perform the following tasks if you are working with a source. The sections following this list describe the tasks.
1. Create or Import an Environment
2. Define Connections
3. Define a Rule Set
4. Profile Data and Define Inventory
5. Provision Data (Databases only)
6. Mask Data
7. Certify Data (Databases only)

742

Delphix User Guide 2016 Delphix

Certify Data
After completing the other tasks and masking your data, you should create a job to certify your data on an ongoing basis. This alerts you if
unmasked data is introduced to a masked database.
You need to certify your data on a regular basis.

Certifying Data
1. Create a Certification job, as described in "Creating a New Certify Job" on page .
2. Run the Certify job.
3. Confirm that no unmasked data has been introduced.
For detailed information about certifying data, see "About Certifying Data."

743

Delphix User Guide 2016 Delphix

Create and Define a Rule Set

After you create an environment and connectors, you need to define a rule set.

Defining a Rule Set for a Database or File

1. Click on the name of an Environment, and then click the Rule Set tab.
The Rule Set screen appears.
2.

Click Create Rule Set to the upper right of the Rule Set screen.
The Create Rule Set screen appears (Figure 1.5 on next page). This screen lets you specify which tables belong in the Rule Set.
a. Enter a Name for your Rule Set.
b. Select a Connector name from the dropdown.
c. The list of tables/files for that connector appears.
d. Click individual tables/file names in the list to the right to select them, or click Select All in the bottom left to select all the tables.
Click Save.
e. You are returned to the Rule Set screen.

3.

When you are finished, click Save.

4.

You may then need to define the Rule Set by modifying the table settings as described in

For example:
For a table, you may want to filter data from the table.
For a file, you must select a File Format to use.

744

"Managing Rule Sets

".

Delphix User Guide 2016 Delphix

Create and Define Connections

After you create an environment, you need to create connections.
So, each connector you define in Delphix Masking must have a connection with the same name already defined in PowerCenter.
To define connectors:
1. Click an Environment name.
2. From the Environment Overview screen, click the Connector tab.

The Connector List Screen appears.

3.

Click Create Connection to the upper right of the Connectors Editor.

The Create Connection Window appears, prompting you for connection information for the database or file:
TypeSelect the appropriate database type (for example, Database - Oracle) or file type (for example, File
- Delimited).
For descriptions of the database connector fields, see "Database Connectors."
For descriptions of the file connector fields, see "File Connectors."
For descriptions of the mainframe connector fields, see "Mainframe Connectors."

4.

Enter the required information and click Save.

You are returned to the Connectors screen where you may add additional connectors if necessary.

For detailed information about connections, see "Managing Connectors" on page .

745

Delphix User Guide 2016 Delphix

Create or Import an Environment

The first task you need to perform is to create or import an application environment. Environments define the scope of work in Delphix Masking. In
order to mask or provision databases and files within Delphix Masking, you first need to create an environment in which Delphix Masking will store
the connection information and masking and provisioning rules for those data stores. An environment can contain multiple database connections
and multiple file connections.

Creating a New Environment

1. Click Add Environment at the upper right of the screen.

The screen prompts you for the following items:

Application Name: The name of the application associated with this environment, for informational purposes. (An integrated test
environment can have multiple applications.)
Environment Name: The display name of the new environment.
Purpose: The way the environment is used in the development process: Development, Gold Copy, QA, Training, and so on.
2.

Either click Save to return to the Environments List/Summary screen, or click Save & View to display the
Environment Overview screen (see "The Environment Overview Screen").

Importing an Environment
1. Click Import Environment at the upper right of the screen.

The screen prompts you for the following items:

Application Name: The name of the application associated with this environment, for informational purposes. (An integrated test
environment can have multiple applications.
Environment Name: The name of the environment that you want to import.
Purpose: The way the environment is used in the development process: Development, Gold Copy, QA, Training, and so on.
Select: Use to browse for the XML file that contains the information you want to import. (This file must be a previously
exported Delphix Agile Data Masking environment.)
Either click Save to return to the Environments List/Summary screen, or click Save & View to display the Environment Overview
screen (see "The Environment Overview Screen").

746

Delphix User Guide 2016 Delphix

Masking Your Data

You can mask data on-the-fly or you can provision it first and then mask it (in-place masking). If you plan to use Delphix Masking to provision your
data before masking it, you must first follow the procedure in the preceding section, "Provision Data".

Masking Your Data

1. Create a Masking job, as described in "Creating a New Masking Job."
2. Run the Masking job.
If you are using Informatica PowerCenter, this step generates XML that is automatically imported into your PowerCenter repository via
your Informatica Client (via the PMCMD interface). The XML files create your mappings and your workflow (how you apply the
mappings). If you chose Import as your Mask Method (rather than Import and Run), you need to log in to PowerCenter to execute the
workflow before you continue with this procedure.
3.

Confirm that you have masked data/generated the masking job:

a. Examine the data in the database columns or the fields in the file to determine whether the data is masked.
b. Run the application that uses the data to ensure that you do not see any unmasked data and that there are no issues in running
the application.

4. For detailed information about masking data, see "About Masking Data."

747

Delphix User Guide 2016 Delphix

Profile Data and Define Inventory

Before performing any profiling, be sure that your administrator has set up the site profiles according to Masking Administrator's Guide.
The purpose of profiling data is to determine what data you want to mask by updating an inventory of your data with sensitive data elements
identified. You can then review and edit that inventory.
If you are using a source file, instead of a source database, you have the choice to populate your inventory manually or use the Delphix Masking
Profiling module to profile your data. Because profiling assigns algorithm information to fields or columns, you might prefer not to profile your data
if you would rather manually assign these properties. If you choose not to profile your data, skip this section.
You can mask data on-the-fly or you can provision the data (using Delphix Masking or other tools) and then mask it (in-place masking). For a
mainframe environment, code is generated for provisioning and masking on the mainframe system. Whichever form of masking you choose, you
You need to profile your data first.
After selecting tables (connectors) and defining a rule set, which you did in the preceding sections, you create a profiling job. (When you defined a
rule set, an empty inventory was automatically created.) A profiling job updates or populates an inventory of your data and identifies potential
sensitive data elements based on the profiling set (rule sets) you use. (For information about the inventory, see "Managing Masking Inventory").
When you examine your inventory, you might determine that you only want to select certain columns to mask, to finalize your inventory.

Profiling Data
1. Create a profiling job as described in "Creating a New Profiling Job."
2.

Run the profiling job you just created.

When you run this profiling job, it updates/populates an Inventory.

3.

To view the inventory, click the Inventory tab while in an Environment Overview.

4.

Examine the inventory to ensure that the profiling job has included everything you want to mask. (For
example, if you selected a First Name field, you probably want the Last Name field as well.)
You can see which columns were selected for masking by selecting the associated rule set.
Make sure you have included all sensitive data elements (for example, personal identifying information) from
the table that you want to mask.

5.

Modify the inventory, if necessary.

When a profiling job runs, it automatically updates the inventory for the given rule set. If you do not want the Profiler to automatically update the
inventory, change the ID Method to User. For detailed information about profiling data, see "About Profiling Data."
What you do next depends on how you plan to mask your data. If you plan to mask your data in-place and you want to use Delphix Masking to
provision your data, proceed with "Provision Data" next. If you plan to mask data on-the-fly, or have already provisioned your data outside of
Delphix Masking, continue with "Mask Data.".

748

Delphix User Guide 2016 Delphix

Provision Data
If you are using a source file, instead of a source database, you do NOT provision your data. Skip this section.
Before you can provision or subset data, you must first create your source environment in Delphix Agile Data Masking (Create or Import an
Environment), define connections (Define Connections), define a rule set (Define a Rule Set), and create a target environment (Create or
Import an Environment).

Provisioning Data
1. Create a provisioning job as described in "Creating a New Provisioning Job."
2. Run the provisioning job.
3. Ensure you have the information you need.
For detailed information about provisioning data, see "About Provisioning (Subsetting Data)."

749

Delphix User Guide 2016 Delphix

Start Masking
Delphix Masking is a Web application that you use within a browser window.

Starting Delphix Masking

1. Enter your Delphix Masking URL into your client browser. This URL will be different depending on the type of installation you have
deployed. To better understand the types of Masking Engine deployments, read the section "Before You Begin" in Delphix Masking
Quick Start Guide - An Overview.
a. For the Standalone Masking Engine: http://<Masking Engine IP or DNS name>:8282/dmsuite
b. For the Combined Delphix Engine and Masking Engine: http://<Delphix Engine IP or DNS name>:8282/dmsuite
2.

Enter your User Id and Password. User Id is not case-sensitive; Password is case-sensitive. If this is your
first time logging in, the default Administrator is username delphix_admin, password Delphix_123

3.

Click Login.
The Environments List/Summary screen appears.For detailed information about the Environments
List/Summary screen, see "The Environment List/Summary Screen."
The username appears in the upper right corner of the screen.

4.

To log out of Delphix Masking, click Log Out to the right of the username.

750

Delphix User Guide 2016 Delphix

Chapter 2: Masking Engine Components

Delphix consists of the following major components:
1. Profiler
2. Provisioning
3. Masking
4. Certification

The following sections describe each component.

751

Delphix User Guide 2016 Delphix

Profiling Data
Profiling is one of the major components in Delphix. The objective of profiling is to identify the location of Non-Public Information (NPI) or sensitive
data.
The Delphix profiler uses two different methods to identify the location of sensitive data:
1. Search through the column names in the target database, by querying the database catalog (metadata).
2. Look at the data itself using a sampling algorithm, to see whether there is any sensitive data. This is especially useful for files, and
comment and notes fields in a database, for example.
After you have defined an environment and a connection for your data source, you can profile the data. To do so, you create a profiling job (see
Creating a New Profiling Job ).

752

Delphix User Guide 2016 Delphix

Provisioning and/or Subsetting Data

Delphix allows you to provision all or a subset of data to a target you choose. Delphix can create a target database for you on your existing
systems or in the cloud. While the target database will normally be the same type as the source, it can also be different for example, Oracle to
SQLServer. This power and flexibility will provide your development and testing teams with the ability to procure fresh secure data from a source
environment and move it to their nonproduction environment any time they need it. Provisioning jobs perform extract and load functions only.
Delphix does not transform data as part of this process.

Practical Subset Example

This section provides an example of when you might want to subset data. All the functionality for provisioning is done at the individual table level.
If you want to filter information based on customers, as part of the rule set you can filter as follows:
1. Columns Select a column or columns from a table when you don't want to load data to all the columns in a table.
2. Filter Specify a filter to run on the data before loading it to the target database.
3. Join Table Specify a SQL join condition so you can define primary key/foreign key relationships between tables.
4. List Select a list to use for filtering data in a table.
5. Custom SQL Use SQL statements to filter data for a table.
To change these filters, see Modifying Tables in a Rule Set.

753

Delphix User Guide 2016 Delphix

Masking Data
After you create an environment, connection, rule set, and inventory, you mask data.
To maintain Referential Integrity (RI), Delphix masks each field on itself. This repeatable masking automatically maintains RI (for verbatim
matches), even if it's between applications or platforms.
For example, if you want to match the values between a parent and children, simply select the same algorithm to mask them. This ensures that
referential integrity is maintained within the same database. Furthermore, Delphix creates the integrity across database platforms (between SQL
Server and DB2, for example) or across files (tab-delimited files) and relational data (a column in a SQL Server database)just select the same
masking algorithm.
As a practical example, assume you have an SSN column in a Microsoft SQL Server database, an SSN column in a DB2 database, and an SSN
field in a tab-delimited file. If the SSN value was 111111111 across the two databases and the file, and you use the same SSN algorithm for all
three, the masked value (for example, 801-01-0838) will be the same for all three.
There are two ways to mask data. You can mask data on-the-fly or you can provision it first and then mask it. The following sections explain these
two options.
Figure 6 Delphix In-Place Masking Option

Masking In-Place
With in-place masking, production data that already exists in a nonproduction environment is masked, in place.

Advantages/Disadvantages:
The main advantage to in-place masking is when you have provisioned data to a non-production environment that contains some production data.
Delphix can mask the data in those existing environments. In-place masking masks only the columns you flag in the inventory, leaving the other
columns alone.
The main disadvantage is that production data is copied potentially into a nonproduction environment while the masking takes place, so sensitive
data might exist in the nonproduction environment until the masking is complete.

On-The-Fly Masking

754

Delphix User Guide 2016 Delphix

Figure 7 Delphix On-the-Fly Masking Option

With on-the-fly masking, you specify the source of the information to be masked, and where the masked data will be loaded. On-the-fly masking is
an Extract Transform Load (ETL) process.
Delphix extracts the data from a source environment, such as a production copy, gold copy, or disaster recovery copy (only read from a database
not an archived file).
Delphix transforms, or masks, the data in the memory of the application server on which it resides, and then loads the masked data to the target
environment. Delphix does not modify the original source data; only the target data changes.

Advantages/Disadvantages:
One advantage to on-the-fly masking is that sensitive production data doesn't get persisted in any nonproduction environment. This method only
requires a production source and nonproduction target environment. Because on-the-fly masking uses all insert statements, it typically performs
better than in-place masking, which uses updates.
The main disadvantage to on-the-fly masking is that it requires an active connection to a source production environment or copy.

Masking a Primary Key Column

Because primary keys require unique values, you must mask those columns using a Delphix algorithm that can guarantee uniqueness. You apply
the same mapping algorithm to both the primary key column and the foreign key column so the values between the columns will match. For
information about creating algorithms, see Delphix Administrator's Guide.

755

Delphix User Guide 2016 Delphix

Certifying Data
After profiling and masking data, you want to monitor or audit the process (also known as certifying your data). This alerts you if unmasked data is
introduced to a masked database.
For example, if you mask your master customer database once a week, and an input file of unmasked is introduced by mistake, you want to be
able to detect that. The purpose of the Delphix certification module is to identify such a situation. To do so, you create a Certification job against
that database (see Creating a New Certify Job).
The Certifying job goes through every row in the tables in a rule set and verifies that every value designated for masking in the inventory is
masked. The Certification job output lists the fields designated for masking, along with the result of the certification: Clean, Polluted, or Not
Applicable. Polluted data indicates that Delphix encountered a value that could potentially be an unmasked production value. Not Applicable
indicates that Delphix was unable to determine whether the value is masked.

Certification and Delta Masking

As part of the certification process for databases, you can specify to mask rows that are not masked but are identified as part of the certification
process as polluted. In other words, if the certification process finds "polluted rows," Delta Masking instructs Delphix to mask the polluted records
to ensure that those polluted rows get masked.

A Practical Certification Example

When a certification job runs, it looks at the inventory defined for that database. If the inventory indicates to mask the Customer.First_Name
column with the First Name Secure Lookup algorithm, the certification job ensures that there are only masked values for that column.
The First Name Secure Lookup algorithm uses a look-up file that contains all the first names used to mask a column. When the certification job
runs, it compares the values in the Customer.First_Name column with the look-up file, which contains only the mask values.
If any names in the column do not match the names in the look-up file, Delphix indicates that it found polluted data in the Customer.First_Name
column.
You can use the Delphix Certification module to certify all data masked with Secure Lookup Algorithms.
You can also certify data masked with Segmented Mapping Algorithms, keeping in mind that the segmented mapping algorithm must specify a
range for each segment.
For example, if the SSN Segmented Mapping algorithm first segment has a range from 800-899, and there is SSN data in the Customer.SSN
column with the first three digits of 435, the certification job will tag the Customer.SSN column as containing polluted rows.
With the Telephone algorithm, the middle segment is the exchange. Because the exchange is always masked to an exchange of 555, any other
exchange will indicate polluted data.
We recommend that you run certification jobs at least once in between refreshes, when the refreshes for a database are scheduled 7 days or
more apart.

756

Delphix User Guide 2016 Delphix

Chapter 3: Understand and Manage the Masking Engine

The following sections detail the various tabs and functions in Delphix, presented in the order in which they appear in the Delphix application:
Managing Environments
Managing Connectors
Managing Rule Sets
Managing Masking Inventory
Managing Jobs
Tokenization

757

Delphix User Guide 2016 Delphix

Managing Environments
Environments define the scope of work in Delphix. In order to mask or provision databases and files within Delphix, you first need to create an
Environment in which Delphix will store the connection information and masking and provisioning rules for those data stores. An environment can
contain multiple database connections and multiple file connections.

The Environment List/Summary Screen

The Environment List/Summary screen provides a dashboard overview of what Delphix is doing. It is the first screen that appears when a user
logs in to Delphix. You can also reach it by clicking the Environments tab or by clicking the Environment List link elsewhere in the application.
To search for an environment, enter an environment name in the Search field and click Search.
The Environments List/Summary screen contains the following columns:
Application The name of the application.
Environment The name of the environment.
Purpose The purpose of this environment.
Jobs Running The number of running jobs.
Export Export the environment.
Copy Copy the environment.
Delete Delete the environment.

Creating or Importing an Environment

To create a new environment:
1. Click Add an Environment at the upper right of the (see Figure 2)
2. The screen prompts you for the following items:
a. Application Name: The name of the application associated with this environment, for informational purposes. (An integrated test
environment can have multiple applications.)
b. Environment Name: The display name of the new environment.
c. Purpose: The way the environment is used in the development process: Development, Gold Copy, QA, Training, and so on.
3. Either click Save to return to the Environments List/Summary screen, or click Save & View to display the Environment Overview screen
(see The Environment Overview Screen).
Import an environment:
1. Click Import an Environment at the upper right of the screen (see Figure 2)
a. The screen prompts you for the following items:
b. Application Name: The name of the application associated with this environment, for informational purposes. (An integrated test
environment can have multiple applications.)
c. Environment Name: The name of the environment that you want to import.
d. Purpose: The way the environment is used in the development process: Development, Gold Copy, QA, Training, and so on.
e. Select: Use to browse for the XML file that contains the information you want to import. (This file must be a previously
exported Delphix environment.)
2. Either click Save to return to the Environments List/Summary screen, or click Save & View to display the Environment Overview screen
(see The Environment Overview Screen).

Exporting an Environment
You can export an environment from the Environment List/Summary screen. You can later import that environment to a different instance of
Delphix, such as a development test instance or a production instance.
To export an environment:
1. Click the Export icon.
2. The popup fills in the following items:
a. Environment Name
b. File Name.
3. Click Export.

758

Delphix User Guide 2016 Delphix

All the information for the specified environment (connectors, rule sets, inventory, jobs, and so on) is exported to an XML file.
A status popup appears. When the export operation is complete, you can click on the Download file name to access the XML file.

Copying and Deleting Environments

You can copy and delete environments from the Environment List/Summary screen.
To copy an environment:
1. Click the Copy icon to the right of the environment status.
2. The popup prompts you for the following items:
a. Name
b. Purpose
c. Application Name
3. Click Save.
The environment definition is copied to a new name.
The copy feature is a very powerful tool. If you have multiple similar environments, you can create one, copy it multiple times, and make
necessary changes without having to start from scratch. Each environment will need its own connections, but you can update the
connections that get copied. However, you will need to create new jobs for each copied environment.
When you copy an environment, all of its connectors, rule sets, and inventory are copied with it. To avoid confusion when using copied
environments, we recommend that you change descriptive information to be different from the original.
To delete an environment:
Click the Delete icon to the right of the environment status and copy icon.
Clicking the Delete icon deletes everything for that environment: connections, inventory, rule sets, and so on.

The Environment Overview Screen

You can reach the Environment Overview screen by clicking an environment name from the Environments List/Summary screen.
Figure 9 Environment Overview Screen

This screen gives an overview of the Environment and the Environment Status. The left of the screen displays the environment Name, Purpose
(for example, DEV or QA), and the Application Name. The Environment Status lists the Current Status, and dates for Last Data Refresh, Last
Masked, Last Certified, and Last Profiled. The files listed on the right side of the window are pdfs of the last certification job (C) and the last
masking job inventory (M).
The body of the page displays all jobs currently defined for this environment, along with the status of the jobs (created, running, succeeded, or
failed). For information about Jobs and the icons on this screen, see Managing Jobs.
You can use the icons in the Jobs heading to create new jobs. See Monitor Jobs.

759

Delphix User Guide 2016 Delphix

Managing Connectors
Delphix stores database connection information in an object called a "Connector." When in an Environment Overview, click the Connector tab to
view the list of connectors within an environment.
For each connection, you must manually define a corresponding connector with the same name.

The Connector List

The Connector List screen shows the connectors that have been created within the environment.
Figure 10 Connector List Screen

Creating or Editing a Connector

To edit a connector:
1. Click the Edit icon to the right of the connector.
To create a new connector:
1. Click Create Connection to the upper right of the Connectors Editor.
The Create Connection window appears, prompting you for connection information for a database or file:
a. DB Type Select the appropriate database type (for example, Database - Oracle) or file type (for example, File - Delimited).
b. Each new connector uses the source system access credentials so appropriate access is granted when reading source data.

Deleting Connectors
To delete a connector:
Click the Delete icon to the far right of the connector name.
When you delete a connector, you also delete its rule sets and inventory data.

Database Connectors
The fields that appear are specific to the DBMS Type you select. If you need assistance determining these values, please contact your database
administrator. All required fields are marked with an asterisk on the screen.
You only can create connectors for the databases and/or files listed. If your database or file type is not listed here, you cannot create a
connector for it.
Kerberos Authentication (Sybase, Oracle, or DB2 only, optional) Whether to use a Kerberos connection to the database. This box is
clear by default. If this box is checked, the application code makes a Kerberos connection to the database instead of using a
login/password.
Connection Type (Oracle or MS SQL Server only) Choose a connection type:
Basic Basic connection information.
Advanced The full JDBC connect string.
Connection Name The name of the database connector (specific for your Delphix application).

760

Delphix User Guide 2016 Delphix

For each Connection Name, you must manually define a corresponding connector with the same name.
Schema Name The schema that contains the tables that this connector will access.
Database Name The name of the database to which you are connecting.
Host Name / IP or Hostname/IPThe network host name or IP address of the database server.
Username (Oracle only)
ODBC DNS Name (ODBC and Microsoft Access only)
Login ID The user login this connector will use to connect to the database.
Password The password associated with the Login ID or Username. (This password is stored encrypted.)
System Number (SAP only)
SAP Client (SAP only)
Language (SAP only)
Port The TCP port of the server.
SID (Oracle only) Oracle System ID (SID).
Instance Name (MS SQL Server only) The name of the instance. This is optional. If the instance name is specified, the connector
ignores the specified "Port" and attempts to connect to the "SQL Server Browser Service" on port 1434 to retrieve the connection
information for the SQL Server instance. If the instance name is provided, be sure to make exceptions in the firewall for port 1434 as well
as the particular port that the SQL Server instance listens to.
Server Name (Informix only) The name of the Informix server.
Custom Driver Name (Adabas and SQL Anywhere only) The name of the custom driver.
Custom JDBC URL (Adabas and SQL Anywhere only) The name of the custom JDBC URL.
All database types have a Test Connection button at the bottom left of the New Connector window. We highly recommend that you test your
connection before you save it. Do so before you leave this window. When you click Test Connection, Delphix uses the information in the form to
attempt a database connection. When finished, a status message appears indicating success or failure.

File Connectors
The values that appear correlate to the File Type you select. All required fields are marked with an asterisk on the screen.
Connector Name The name of the file connector (specific to your Delphix application and unrelated to the file itself).
Connection Mode Local Files, SFTP, FTP, HTTP & HTTPS.
Path The path to the directory where the file(s) are located.
Operating System Choose the operating system on which the file resides: Windows or Linux. (This value does not appear for
Mainframe Copybooks.)
If you select SFTP or FTP for Connection Mode, the following additional values appear:
Server Name The name of the server used to connect to the file.
User Name The User Name to connect to the server.
Public Key Authentication (Optional) (Only appears for SFTP.) Check this box to specify a public key.
When you check this box, the Available Keys dropdown appears. Choose a key from the dropdown. (The path on the server to the location that
contains the keys is configured in a Delphix property files.)
Password The associated Password for the server.
Port The Port used to connect to the server.

761

Delphix User Guide 2016 Delphix

Mainframe Connectors
The fields that appear are correlate to the File Type you select. If you need assistance determining these values, please contact your MVS
administrator. All required fields are marked with an asterisk on the screen.
Connection Name The name of the file connector (specific to your application and unrelated to the file itself).
Host Name / IP The network host name or IP address of the PDS server.
FileName The source file fully qualified data set name, including "(0)" for generation data group files.
FileType The source file type: normal, VSAM, or GDG.
UserID The user login this connector will use to connect to the mainframe host system to access the PDS copybook files. For VSAM
files, use the cluster name.
Password The password associated with the Login ID or Username. (This password is stored encrypted.)
File DCB RECFM The source file record format; possible values: F, FB, FBA, V, VB, VBA.
BLKSIZE The source file block size, from 1 to 32760.
File DCB LRECL The source file logical record length, from 1 to 32760. If record format is fixed, must be a divisor of block size.
Header/Trailer Code The number of records to skip (copy and not mask) at the beginning and end of the source file. The format is in
the form "H,x,T,y", "H,x", or "T,y" where:
H and T are constants.
x is the number of header rows to skip.
y is the number of trailer rows to skip.
Normal file types have a Test Connection button at the bottom left of the New Connector window. VSAM and GDG file types do not have a Test
Connection button.
We highly recommend that you test your connection. Do so before you leave this window. When you click the Test Connection button, DMsuite
uses the information in the form to attempt a mainframe connection. When finished, a status message appears indicating whether the attempt was
successful or failed.
VSAM files are treated sequentially as ordinary files. IDCAMS uses the cluster name to create an ordinary file. This GOLDCOPY is used to load
the target dataset later.
To allocate the new file, the process uses record format, record length, and block size, as follows:
If the VSAM source record is fixed length, use FB and record length, and make block size the largest multiple of record length less than
27,998 (half-track blocking).
If the VSAM record is variable length, use VB, and use the maximum record length +4 as the record length, and use block size of 27,990.
This information pertains to processing the source records and allocating the GOLDCOPY; it does not apply to system records about the original
source.

762

Delphix User Guide 2016 Delphix

Managing Rule Sets

A "Rule Set" points to a collection of tables or flat files that Delphix uses for profiling, provisioning, and masking, and certifying data. For
mainframe systems, the rule set represents a copybook definition for a file.

The Rule Set Screen

From anywhere within an Environment, click the Rule Set tab to display the Rule Sets associated with that environment. The Rule Set screen
appears (Figure 3.5).
If you have not yet created any rule sets, the Rule Set list is empty.
Figure 12 Rule Set Screen

Creating a Rule Set

Creating a Rule Set for a Mainframe Environment
To create a new rule set:
1. Click +Create Rule Set to the upper right of the Rule Set screen.
The Create Rule Set screen appears. This screen lets you specify which tables belong in the rule set. (Note: A similar screen appears
when you edit a Rule Set.)
a. The Edit rule set feature is disabled for a mainframe environment.
2. Enter a name for the new rule set.
3. Select a Connector name from the drop-down menu.
The list of tables for that connector appears. If you have not yet created any connectors, the list is empty.
4. Click individual table names to select them, or click Select All (bottom left) to select all the tables in the connector.
5. Click Save.
You are returned to the Rule Set screen.
6. Select a Connection name for this rule set.
7. Name and browse the PDS where copybooks are located.
The PDS connection must use the same host information as the file connection.
8. Select a copybook to add to the rule set.
9. Click Save.

Copying a Rule Set

This feature is disabled for a mainframe environment.
When you copy a rule set, you also copy the ' for that rule set.

763

Delphix User Guide 2016 Delphix

To copy a rule set:

1. Click the Copy icon to the right of the rule set on the Rule Set screen.
The Copy Rule Set window appears.
2. Specify a Name for the new rule set.
3. Click Save.
Modify the rule set as you want, using the preceding procedures.

Editing/Modifying a Rule Set

This feature is disabled for a mainframe environment.
To edit a rule set:
1. Click the Edit icon to the right of the rule set on the Rule Set screen.
2. Click the Edit Rule Set button towards the top.
The Create Rule Set screen appears. This screen lets you specify which tables belong in the rule set.
Modify the rule set as you want, using the preceding procedures.
If you have tables with names that change monthly, for example tables that are appended with the current date, you can set a table suffix for a
rule set.

Deleting a Rule Set

If you delete a Rule Set, any inventory associated with that Rule Set will also be deleted. Also, any filter conditions defined for that Rule Set will be
deleted.
To delete a rule set:
1. Click the Delete icon to the right of the rule set on the Rule Set screen.

Modifying Tables in a Rule Set (For Distributed Environment)

The features in this section are disabled for a mainframe environment.
For additional information about any of the features in this section, see About Provisioning (Subsetting Data).
You can modify tables in a rule set as follows:
Creating a Rule Set for a Mainframe Environment
Logical Key
Edit Filter
Custom SQL
Table Suffix
Add Column
Join Table
List

Logical Key
If your table has no primary keys defined in the database, and you are using an In-Place strategy, you must specify an existing column or columns
to be a logical key. This logical key does not change the target database; it only provides information to Delphix. For multiple columns, separate
each column using a comma. Note: If no primary key is defined and a logical key is not defined an identify column will be created.
To enter a logical key:
1. From the Rule Set screen, click the name of the desired rule set.
2. Click the green edit icon to the right of the table whose filter you wish to edit.
3. On the left, select Logical Key.
4. Edit the text for this property.
5. To remove any existing code, click Delete.
6.
764

Delphix User Guide 2016 Delphix

6. Click Save.

Edit Filter
Use this function to specify a filter to run on the data before loading it to the target database.
To add a filter to a database rule set table or edit a filter:
1. From the Rule Set screen, click the name of the desired rule set.
2. Click the green edit icon to the right of the table you want.
3. On the left, select Edit Filter.
4. Edit the properties of this filter by entering or changing values in the Where field.
Be sure to specify column name with table name prefix (for example, customer.cust_id <1000).
1. To remove an existing filter, click Delete.
2. Click Save.

Custom SQL
Use this function to use SQL statements to filter data for a table.
To add or edit SQL code:
1. From the Rule Set screen, click the name of the desired rule set.
2. Click the green edit icon to the right of the table you want.
3. On the left, select Custom SQL.
4. Enter custom SQL code for this table.
Delphix will run the query to subset the table based on the SQL you specify.
1. To remove any existing code, click Delete.
2. Click Save.

Table Suffix
To set a table suffix for a rule set:
1. In the Rule Set screen, click the name of the desired rule set.
2. Click the green edit icon to the right of the table for which you wish to set the suffix.
3. On the left, select Table Suffix.
4. The Original Table Name will already be filled in.
5. (Optional) Enter a Suffix date Pattern (for example, mmyy).
6. (Optional) Enter a Suffix Value, if you want to append a specific value.
7. (Optional) Enter a Separator (for example, _). This value will be inserted before the suffix value (for example, tablename_0131).
8. Click Save.

Add Column
Use this function to select a column or columns from a table when you don't want to load data to all the columns in a table.
To add a column to a database rule set table or edit a column:
1. From the Rule Set screen, click the name of the desired rule set.
2. Click the green edit icon to the right of the table you want.
3. On the left, select Add Column.
4. Select one or more column names to include in the table. To remove a column, deselect it.
You can also choose Select All or Select None.
5. Select Save.

Join Table
Use this function to specify a SQL join condition so you can define primary key/foreign key relationships between tables.
To define or edit the join condition for a table:
1.
765

Delphix User Guide 2016 Delphix

1. From the Rule Set screen, click the name of the desired rule set.
2. Click the green edit icon to the right of the table you want.
3. On the left, select Join Table.
4. Edit the properties for this join condition.
5. To remove an existing join condition, click Delete.
6. Click Save.

List
Use this function to select a list to use for filtering data in a table.
To add or edit a list:
1. From the Rule Set screen, click the name of the desired rule set.
2. Click the green edit icon to the right of the table you want.
3. On the left, select List.
4. Edit the text file properties for this list.
a. Select a column.
b. Enter or browse for a filename.
c. Files that have already been specified appear next to Existing File.
5. To remove an existing list file, click Delete.
6. Click Save.

Removing a Table
To remove a table from the rule set:
1. From the Rule Set screen, click the name of the desired rule set.
2. Click the red delete icon to the right of the table you want to remove.
If you remove a table from a rule set and that table has an inventory, that inventory will also be removed.

766

Delphix User Guide 2016 Delphix

Managing the Masking Inventory

The Inventory Screen
Inventory Settings
Managing a Database Inventory
Setting Column Criteria for a Table
Row Types and Creating New Row Types for Tables
Managing a File Inventory
Setting Field Criteria for a File
Defining Fields
Adding Record Types for Files
Masking XML Documents
Importing and Exporting an Inventory
Delphix stores the masking rules for each sensitive column in the Delphix repository database in the environment's inventory.

The Inventory Screen

From anywhere within an environment, click the Inventory tab to display the inventory for the rule sets for the environment and the Inventory
Screen appears (Figure 3.7).

Inventory Settings
To specify your inventory settings:
1. On the left-hand side of the screen, select a Rule Set from the drop-down menu.
2. Below this, Contents lists all the tables or files defined for the rule set.
Figure 14 Inventory Screen

3. Select a table or file for which you would like to create or edit the inventory of sensitive data.
The Columns or Fields for that specific table or file appear.
4. If a column is a primary key (PK), Foreign Key (FK) or an index (IDX), an icon indicating this will appear to the left of the column name. If
there is a Note for the column, a Note icon will appear. To read the note, click the icon.
5. If a table, metadata for the column appears: Data Type and Length (in parentheses). This information is read-only.
6. Choose how you would like to view the inventory:
a. All FieldsDisplays all columns in the table or all fields in the file (allowing you to mark new columns or fields to be masked).
b. Masked FieldsFilters the list to just those columns or fields that are already marked for masking.
7. Choose how to determine whether to mask/unmask a column:
a. AutoThe default value. The profiling job can determine or update the algorithm assigned to a column and whether to mask the
column.
b. UserThe user's choice overrides the profiling job. The user manually updates the algorithm assignment, mask/unmask option

767

7.
Delphix User Guide 2016 Delphix
b.
of the column. The Profiler will ignore the column, so it will not be updated as part of the Profiling job. In order to use the Secure
Shuffle algorithm the user would select it as a User defined algorithm and assign it to the specific column. Secure shuffle
automates the creation of a secure lookup algorithm by building a list of replacement values based on the existing unique values
in the target column and creating a secure lookup using those values. In that respect it is simply shuffling the values.

Managing a Database Inventory

The following sections apply to databases:
Setting Column Criteria for a Table
Row Types and Creating New Row Types for Tables

Setting Column Criteria for a Table

Note: a database must be selected from the Select Rule Set dropdown menu on the left, not a file system.
To set criteria for sensitive columns:
1. Click the green edit icon to the right of a name of a column.
2. To mask the selected column, check the Mask check box.
3. Clear this check box if you do not want to mask this column.
4. Choose the appropriate sensitive data element type for the column from the Domain dropdown.
5. Delphix defaults to a Masking Algorithm as specified in the Settings screen. If necessary, you can override the default algorithm for a
column.
6. To select a different masking algorithm, choose one from the Algorithm dropdown.
For detailed descriptions of these algorithms, see Algorithms. For information about how to create your own algorithms and how to add them to
domains, see Delphix Administrator's Guide.
If you select a DATESHIFT algorithm and you are not masking a datetime or timestamp column, you must specify a Date Format. (This field only
appears if you select a DATESHIFT algorithm from the Masking Algorithm dropdown.) For a list of acceptable formats, click the Help link for Date
Format. The default format is yyyy-MM-dd.
1. Select the Row Type according to its purpose, using "All Row" as a convention for all rows.
If you need to create a row type (for example, if filter conditions are required), see Row Types and Creating New Row Types for a
Table next.
2. Select an ID Method:
a. AutoThe default value. The profiling job can determine or update whether to mask a column.
b. UserThe user decides whether to mask/unmask a column. The user's choice overrides the profiling job. (The user masking is
done after the profiling job is finished.)
3. You can add/remove notes in the Notes text field.
4. Click Save when you are finished.
You must click Save for any edits to take effect.

Row Types and Creating New Row Types for Tables

Delphix provides a feature called Row Types that limits masking of a given column to a specific subset of rows.
Note: a database must be selected from the Select Rule Set dropdown menu on the left, not a file system.
To create a new row type:
1. From an Environment's Inventory tab, click +Row Types in the upper right.
The Row Type window appears, listing existing row types.
2. Click + Add a Row Type.
The Add Row Type window appears.
3. Name the Row Type according to its purpose. For example, if you want to subset the rows to only take rows with addresses, you can
name this row type "Address Rows".
4. To limit the masking to a subset of rows, specify an appropriate Where Clause.
5. Click Save.

Managing a File Inventory

The following sections apply to files:

768

Delphix User Guide 2016 Delphix

Setting Field Criteria for a File

Defining Fields
Adding Record Types for Files
File inventory is based on file format, not on file content. Therefore, if you make a change to a file inventory, that change applies to all files that
use that format.

Setting Field Criteria for a File

Note: a file system must be selected from the Select Rule Set dropdown menu on the left, not a database.
To set criteria for sensitive fields:
1. From an Environment's Inventory tab, click the green edit icon to the right of the field you want.
2. To mask this field, check the Mask check box (in the View Inventory pane).
3. Clear this check box if you do not want to mask this field.
4. Choose the appropriate sensitive data element type for the field from the Domain dropdown.
5. Delphix defaults to a masking Algorithm as specified in the Settings screen. If necessary, you may override the default algorithm for a
field.
6. To select a different masking algorithm, choose one from the Algorithm dropdown. For descriptions of these algorithms, see Algorithms
.
If you select a DATESHIFT algorithm, you must specify a Date Format. (This field only appears if you select a DATESHIFT algorithm
from the Masking Algorithm dropdown.) For a list of acceptable formats, click the Help link for Date Format. The default format is
yyyy-MM-dd.
7. Choose a Record Type from the dropdown.
8. If you are masking a delimited or fixed file, specify a Position: the field number (for delimited files) or the character position (for fixed
files) of the beginning of the field within the data record.
9. If you are masking a fixed file, specify a Length (the length of this field within the data record).
10. Notes can be added/removed in the Notes text field. (Fields with notes display a Note icon in the Notes column.)
11. Click Save when you are finished.

You must click Save for any edits to take effect.

Defining Fields
Note: A file system must be selected from the Select Rule Set dropdown menu on the left, not a database.
To create new fields:
1. From an Environment's Inventory tab, clickDefine fields to the far right.
The Edit Fields window appears.
Figure 15 Define Fields Window

769

Delphix User Guide 2016 Delphix

2. Edit the fields as described in Setting Field Criteria for a File.

3. When you are finished, click New to create a new field, or click Save to update an existing field.

Adding Record Types for Files

Note: You must select a file system from the Select Rule Set dropdown menu on the left, not a database.
To add a new Record Format:
1. In the upper right-hand corner of an environment's Inventory tab, click Record Types.
The Record Type window appears.
2. Click +Add a Record Type towards the bottom of the window.
The Add Record Type window appears.
3. Enter values for the following fields:
a. Record Type Name A free-form name for this record format.
b. Header/Body/Trailer If the file has header or trailer records, you will need to create file formats for them. Select the
appropriate type. Delphix allows for masking of multiple headers, multiple trailers, and multiple types of body records.
c. Record Type ID (optional) For body records, specify the value of the record type code or other identifier that allows Delphix to
identify records that qualify as this record type.
d. Position # (optional) Specify the field number (for delimited files) or the character position number (for fixed files) of the
beginning of the Record Type Identifier within the data record.
e. Length # (optional) For fixed files, specify the length of the Record Type Identifier within the data record.
4. Click Save when you are finished.

Masking XML Documents

In order to mask an XML file there are a few steps you must do.
1. First you have to import the XML file format under Settings > File Format. You can simply use the XML file itself to import the format. If
you have multiple xml files using this format you can use this format for all those files. If there are different xml formats you will have to
import a file format for each type of xml document.
2. Then you can go to the appropriate environment and create a connector for XML files. Once you create the connector you can create a
ruleset with the XML file(s) you need.
3. After you create the ruleset, you must go back and edit the ruleset and edit the file(s) in the ruleset. There you assign the file format that
you created and what the end_of_record terminator is for that file.
4. Then save this information.

770

Delphix User Guide 2016 Delphix

Once this is done you will see the XML fields show up on the inventory page so you can set up your masking. This is not a database.
To add a new Record Format:
1. From an Environment's Inventory tab, click Record Types towards the upper right.
The Record Type window appears.
2. Click +Add a Record Type towards the bottom of the window.
The Add Record Type window appears.

Importing and Exporting an Inventory

The format of an imported.csv file must exactly match the format of the exported inventory. If you plan to import an inventory, before
importing the inventory, you should export it and then update the exported file as needed before you import it.
To export an inventory:
1. Click the Export icon at the upper right.
The Export Inventory popup appears with the name of the currently selected Rule Set as the Inventory Name and a corresponding .csv
File Name.
2. Click Save.
A status popup appears. When the export operation is complete, you can click on the Download file name to access the inventory file.
To import an inventory:
1. Click the Import icon at the upper right.
The Import Inventory popup appears.
2. Click Select to browse for the name of a comma-separated (.csv) file.
3. Click Save.
The inventory you imported appears in the Rule Set list for this environment.

771

Delphix User Guide 2016 Delphix

Managing Jobs
Delphix creates "jobs" to profile, provision, and mask, and certify data.

Jobs on the Environment Overview Screen

The Environment Overview screen provides status of any jobs running or previously run within the environment. When you create jobs for an
environment, you must create them from the Environment Overview screen of the environment they mask or the environment they use as a
source for data provisioning.
The following columns appear in the Jobs section of the screen:
Name
Rule Set
Status
Action
Edit
Delete

Creating New Jobs

In the Environment Overview screen, select one of the jobs icons to create the corresponding job:
Profile
Mask
Certify
Provision
Figure 16 Environment Overview Screen Showing Create Job Buttons

Creating a New Profiling Job

You can create profiling jobs for databases, copybooks, delimited files, fixed-width, and Excel files.
A Profiling job for a mainframe system cannot assign groups because it does not have the heuristics needed to determine sensitive elements per
group. The Profiler assigns group-sensitive elements to a single group. Then, in inventory, groups are updated as needed to establish the
sensitive element field group sets.
To create a new profiling job:
1.
772

Delphix User Guide 2016 Delphix

1. Click Profile.
The Create Profiling Job window appears.
Figure 17 Create Profile Job

You will be prompted for the following information:

a. Job Name A free-form name for the job you are creating. Must be unique.
b. Multi Tenant Check box if the job is for a multi-tenant database.
c. Rule Set Select a rule set that this job will execute against.
d. Generator The default value is Delphix.
e. No. of Streams The number of parallel streams to use when running the jobs. For example, you can select two streams to
run two tables in the ruleset concurrently in the job instead of one table at a time.
f. Remote Server (optional) The remote server that will execute the jobs. This option lets you choose to execute jobs on a
remote server, rather than on the local Delphix instance. Note: This is an add-on feature for Delphix Standard Edition.
g. Min Memory (MB) (optional) Minimum amount of memory to allocate for the job, in megabytes.
h. Max Memory (MB) (optional) Maximum amount of memory to allocate for the job, in megabytes.
i. Feedback Size (optional) The number of rows to process before writing a message to the logs. Set this parameter to the
appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual
number of rows in a job, the progress for that job will only show 0 or 100%.
j. Profile Sets (Optional) The name of a profiler set, which is a subset of expressions (for example, a subset of financial
expressions). (See Delphix Administrator's Guide.)
Note: If you do not select a profile set, Delphix will use all defined expressions instead of just a subset.
k. Comments (optional) Add comments related to this job.
l. Email (optional) Add e-mail address(es) to which to send status messages. Separate addresses with a comma (,).
2. When you are finished, click Save.
For information about running jobs, see Running and Stopping Jobs from the Environment Overview Screen.

Creating a New Masking Job

To create a new masking job:
1. Click Mask.
The Create Masking Job window appears.
Figure 18 Create Masking Job

773

Delphix User Guide 2016 Delphix

You will be prompted for the following information:

a. Job Name A free-form name for the job you are creating. Must be unique across the entire application.
b. Masking Method Select either In-Place or On-The-Fly. For more information on masking type, see Mask Data.
c. Multi Tenant Check box if the job is for a multi-tenant database.
d. Rule Set Select a rule set that this job will execute against.
or:
e. Generator The default value is Delphix.
f. Repository Folder name The folder name in the repository where the objects should be imported.
g. Parameter File Path (optional) If checked, this tells Delphix to configure the sessions and workflows to use a parameter file
that contains the source and target connection information. If unchecked, the Delphix Engine will generate sessions/workflows
that use the connector names as defined within the Delphix Engine, which will require connections with the same names defined
within the repository.
h. Import Mapplet (optional) if checked, this tells the Delphix Engine to import mapplets that are assigned to columns in the
inventory along with the mappings/sessions/workflows. If unchecked, Delphix will not attempt to import any mapplets that are
assigned in the inventory.
i. Mask Method Choose either of the following:No. of StreamsThe number of parallel streams to use when running the jobs.
For example, you can select two streams to run two tables in the Rule Set concurrently in the job instead of one table at a time.
i. Import When you click the Run icon, creates the mappings but does not execute the workflow. You later run the job.
ii. Import and Run When you click the Run icon, creates the mappings and executes the workflow.
j. Remote Server (optional) The remote server that will execute the jobs. This option lets you choose to execute jobs on a
remote server, rather than on the local Delphix instance. Note: This is an optional feature for Delphix.
k. Min Memory (MB) (optional) Minimum amount of memory to allocate for the job, in megabytes.
l. Max Memory (MB) (optional) Maximum amount of memory to allocate for the job, in megabytes.
m. Update Threads The number of update threads to run in parallel to update the target database.
n. For databases using T-SQL, multiple update/insert threads can cause deadlocks. If you see this type of error, reduce the number
of threads that you specify in this box.
o. Commit Size (optional) The number of rows to process before issuing a commit to the database.
p.
774

Delphix User Guide 2016 Delphix

p. Feedback Size (optional) The number of rows to process before writing a message to the logs. Set this parameter to the
appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual
number of rows in a job, the progress for that job will only show 0 or 100%.
q. Bulk Data (optional) For In-Place masking only. The default is for this check box to be clear. If you are masking very large
tables in-place and require performance improvements, check this box. Delphix will mask data to a flat file, and then use inserts
instead of updates to bulk load the target table.
r. Disable Constraint (optional) Whether to automatically disable database constraints. The default is for this check box to be
clear and therefore not perform automatic disabling of constraints. For more information about database constraints, see Enabli
ng and Disabling Database Constraints.
s. Batch Update (optional) Enable or disable use of a batch for updates. A job's statements can either be executed individually,
or can be put in a batch file and executed at once, which is faster.
t. Disable Trigger (optional) Whether to automatically disable database triggers. The default is for this check box to be clear
and therefore not perform automatic disabling of triggers.
u. Drop Index (optional) Whether to automatically drop indexes on columns which are being masked and automatically re-create
the index when the masking job is completed. The default is for this check box to be clear and therefore not perform automatic
dropping of indexes.
v. Prescript (optional) Specify the full pathname of a file that contains SQL statements to be run before the job starts, or click Br
owse to specify a file. If you are editing the job and a prescript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a prescript file was already specified.) For information about creating your own
prescript files, see Creating SQL Statements to Run Before and After Jobs.
w. Postscript (optional) Specify the full pathname of a file that contains SQL statements to be run after the job finishes, or click
Browse to specify a file. If you are editing the job and a postscript file is already specified, you can click the Delete button to
remove the file. (The Delete button only appears if a postscript file was already specified.) For information about creating your
own postscript files, see Creating SQL Statements to Run Before and After Jobs.
x. Comments (optional) Add comments related to this masking job.
y. Email (optional) Add e-mail address(es) to which to send status messages.
2. When you are finished, click Save.
For information about running jobs, see Running and Stopping Jobs from the Environment Overview Screen.

Creating a New Certify Job

To create a new certify job:
1. Click Certify.
The Create Certify Job window appears.
Figure 19 Create Certify Job

You will be prompted for the following information:

a. Job Name A free-form name for the job you are creating. Must be unique.
b.
775

Delphix User Guide 2016 Delphix

b. Multi Tenant Check box if the job is for a multi-tenant database.

c. Rule Set Select a rule set that this job will execute against.
d. Generator The default value is Delphix.
e. No. of Streams The number of parallel streams to use when running the jobs. For example, you can select two streams to
run two tables in the ruleset concurrently in the job instead of one table at a time.
f. Remote Server (optional) The remote server that will execute the jobs. This option lets you choose to execute jobs on a
remote server, rather than on the local Delphix instance. Note: This is an add-on feature for Delphix Standard Edition.
g. Min Memory (MB) (optional) Minimum amount of memory to allocate for the job, in megabytes.
h. Max Memory (MB) (optional) Maximum amount of memory to allocate for the job, in megabytes.
i. Feedback Size (optional) The number of rows to process before writing a message to the logs. Set this parameter to the
appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual
number of rows in a job, the progress for that job will only show 0 or 100%.
j. Prescript (optional) Specify the full pathname of a file that contains SQL statements to be run before the job starts, or click Br
owse to specify a file. If you are editing the job and a prescript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a prescript file was already specified.) For information about creating your own
prescript files, see Creating SQL Statements to Run Before and After Jobs
k. Postscript (optional) Specify the full pathname of a file that contains SQL statements to be run after the job runs, or click Bro
wse to specify a file. If you are editing the job and a postscript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a postscript file was already specified.) For information about creating your own
postscript files, see Creating SQL Statements to Run Before and After Jobs.
l. Delta Masking Check this box to mask rows that are not masked and are identified as part of the certification process as
polluted.
m. Batch Update (optional) Enable or disable use of a batch for updates. A job's statements can either be executed individually,
or can be put in a batch file and executed at once, which is faster.
n. Disable Trigger (optional) Whether to automatically disable database triggers. The default is for this check box to be clear
and therefore not perform automatic disabling of triggers.
o. Comments (optional) Add comments related to this certification job.
p. Email (optional) Add e-mail address(es) to which to send status messages.
2. When you are finished, click Save.
For information about running a job, see Running and Stopping Jobs from the Environment Overview Screen.

Creating a New Provisioning Job

When you provision data, you define the provisioning job within the source environment (from source to target). On the other hand, a masking job
is defined from the target environment.
To create a new provisioning job:
1. Click Provision.
The Create Provisioning Job window appears.
Figure 20 Create Provisioning Job

776

Delphix User Guide 2016 Delphix

You will be prompted for the following information:

a. Job Name A free-form name for the job you are creating.
b. Target Environment The environment into which the data will be loaded.
c. Multi Tenant Check box if the job is for a multi-tenant database.
d. Rule Set Select a rule set that this job will execute against.
e. Target Connector The database connector into which the data will be loaded.
f. Generator
g. Repository Folder name The folder name in the repository where the objects should be imported.
h. No. of Streams The number of parallel streams to use when running the jobs. For example, you can select two streams to
run two tables in the ruleset concurrently in the job instead of one table at a time.
i. Remote Server (optional) The remote server that will execute the jobs. This option lets you choose to execute jobs on a
remote server, rather than on the local Delphix instance. Note: This is an add-on feature for Delphix Standard Edition.
j. Min Memory (MB) (optional) Minimum amount of memory to allocate for the job, in megabytes.
k.
777

Delphix User Guide 2016 Delphix

k. Max memory (MB) (optional) Maximum amount of memory to allocate for the job, in megabytes.
l. Commit Size (optional) The number of rows to process before issuing a commit to the database.
m. Feedback Size (optional) The number of rows to process before writing a message to the logs. Set this parameter to the
appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual
number of rows in a job, the progress for that job will only show 0 or 100%.
n. Disable Constraint (optional) Whether to automatically disable database constraints. The default is for this check box to be
clear and therefore not perform automatic disabling of constraints. For more information about database constraints, see Enablin
g and Disabling Database Constraints.
o. Batch Update (optional) Enable or disable use of a batch for updates. A job's statements can either be executed individually,
or can be put in a batch file and executed at once, which is faster.
p. Truncate (optional) Whether to truncate target tables before loading them with data. If this box is selected, the tables will be
"cleared" before the operation. If this box is clear, data is appended to tables, which potentially can cause primary key violations.
This box is clear by default.
q. Disable Trigger (optional) Whether to automatically disable database triggers. The default is for this check box to be clear
and therefore not perform automatic disabling of triggers.
r. Prescript (optional) Specify the full pathname of a file containing SQL statements to be run before the job starts, or click Bro
wse to specify a file. If you are editing the job and a prescript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a prescript file was already specified.) For information about creating your own
prescript files, see Creating SQL Statements to Run Before and After Jobs.
s. Postscript (optional) Specify the full pathname of a file containing SQL statements to be run after the job finishes, or click Bro
wse to specify a file. If you are editing the job and a postscript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a postscript file was already specified.) For information about creating your own
postscript files, see Creating SQL Statements to Run Before and After Jobs.
t. Comments (optional) Add comments related to this provisioning job.
u. Email (optional) Add e-mail address(es) to which to send status messages.
2. When you are finished, click Save.

Running and Stopping Jobs from the Environment Overview Screen

To run or rerun a job from the Environment Overview screen:
1. Click the Run icon (play icon) in the Action column for the desired job.
The Run icon changes to a Stop icon while the job is running.
When the job is complete, the Status changes.
To stop a running job from the Environment Overview screen:
1. Click the Stop icon in the Action column for the running job.
A popup appears asking Are you sure you want to stop job?
2. Click OK.
When complete, the Status changes.

778

Delphix User Guide 2016 Delphix

File Masking
Delphix will mask a number of different file types and formats. These include fixed, delimited, Excel, Mainframe/VSAM, XML, Word, and
Powerpoint. The purpose of this document is to provide an overview of general guidelines on how to successfully mask files using Delphix. This
document will not replace Delphix training or the Delphix manual set, it is in addition to these items.

Overview
Delphix supports 2 masking methodologies, In-Place and On-The-Fly. In-Place requires a single file connection and Delphix will read from that
file, mask data in memory, and update the file with the masked data. On-The-Fly requires 2 file connections. One connection for the source file,
and one connection to the target where the masked file will be placed. The target file name must exist. In this scenario, Delphix will read the file
from the source connection, mask in memory, and write the masked data to the target file.

File Formats
Unlike databases files for the most part do not have built in metadata to describe the format of the fields in the file. You must provide this to
Delphix so it can update the file appropriately. This is done through the settings tab where you will see a menu item on the left for File Format.
Select File Format and you will see options to create a file format or input a file format. This will depend on the type of file and how you want to let
Delphix know the format of the file.

Mainframe and XML Files

For Mainframe/VSAM files, you can input the file format via input format option which will import the copybook directly into Delphix. You can input
this file from SFTP, FTP, Local, or Hadoop-HDFS
For XML files you can also input the file format with the input format option. You can use the file you want to mask as the format. Delphix will input
the format of the file directly. You can input this file from SFTP, FTP, or Local.

Delimited, Excel, Fixed Files

For Delimited, Excel, and Fixed files you can either manually create the format of the file yourself, or you can input a text file which describes the
structure of the file to Delphix. To input the file format for delimited or Excel files create a text document with the column names each on its own
line. For example:
Name
Address
City
State
To input the file format for fixed files create a text document with the column names and the length of each column on its own line. For example:
Name,25
Address,40
City,20
State,2
Then input this file as the file format. The name of the text file will be the name of the file format. The file will need to be local to the Delphix
server.
To create a format manually, you can just click the create format button and give the format a name. We will input the details of the format a little
later in this document.

Create a File Connector

In your environment you will need to create a connector to access the files. Each file type will require a separate connector. When you create the
connector, scroll down to the particular file type you desire and select it. After you select this you will need to select the connection mode. For
Excel, Word, Powerpoint, and XML files there is only one connector mode and that is local. This can be either a directory on the Delphix server or
a share that is accessible as a local directory on the Delphix server. For Mainframe/VSAM, Delimited, or Fixed files the connector mode can be:
Local
SFTP
FTP
Hadoop HDFS.

779

Delphix User Guide 2016 Delphix

These connection modes (other than local) will require additional information. We provide a test connection button to test the validity of the
connection. If you are doing in-place masking the file(s) will be masked and updated in the directory pointed to by the connector. If you plan to do
on-the-fly masking then you will need to create a separate environment and connector to be the source for the files to be masked. The masked
files will get put into the directory pointed to by the connector you created previously (the target). However, the file name must exist in the target
directory. It does not have to be a copy of the file, just an entry in the directory with the same name. It will be replaced by the masked file.

Create a Ruleset
Once you create a connector, you can click on the ruleset tab and create a ruleset. Click on create ruleset, give it a name, and provide the file
connector you previously created. Once you do this you will see a list of files that the connector points to. You can select a single file, multiple
files, or all the files. Once you save this the ruleset with the file or files will be saved.
Once you create a ruleset with a file or set of files, you will need to assign those files to their appropriate file format. This is accomplished by
editing the ruleset. When you click on the edit button for the file a popup screen called edit file will appear with the file name. There will be a
dropdown for the format so you can select the proper format for the file. Select the end-of-record to let Delphix know whether the file is in
windows/dos format (CR+LF) or Linux format (LF). If the file is a delimited file you will have a space to put in the delimiter. If the file is a
Mainframe/VSAM file with a copybook you will see a checkbox to signify if the file is variable length. If there are multiple files in the ruleset you will
have to edit each one individually and assign it to the appropriate file format.

File Inventory
For XML or Copybook files, once you select the ruleset and the file you will see the inventory for the file and you can edit this inventory with the
appropriate masking settings like any Delphix data source by either using the profiler or setting this manually.
For Excel, Delimited, or Fixed files, if you created the file format by importing it then the format for the file will be set. When you go to the inventory
page and select the ruleset and file you will see a line which shows all the records which you can expand to see the inventory. If your file has a
header and/or footer you will need to click on Record Type, click on add record type and select Header and/or Footer from the dropdown box.
Then enter a name for this and the number of rows/lines. Now you can assign the appropriate masking algorithms either by running the profiler or
setting them manually on the all records section.
If you did not import a format and just created a file format with the create format button you will have to enter the actual layout of the file into
Delphix. This can be done for Excel, Delimited and Fixed files. This can be accomplished by:
Navigating to the inventory screen and selecting the appropriate ruleset and file
Click on the Record Type button and add the appropriate record types
You will have to add a body record type. Select body from the dropdown and give it a name (i.e. Body).
If you have a file with the columns defined you can import this using the import button. If not then just save.
If your file has a header or footer you can add those next.
If you did not import the format you will have to enter this in manually. To do this click on the Define Fields button, when the screen pops
up you enter in the field name, choose the record type (body) and position in the record.
If the file is a fixed length file you will also have to enter in the length of the field.
You can optionally set the masking here also as you enter this in, or you can do this with the profiler. Enter in all the fields and you will be
set.

780

Delphix User Guide 2016 Delphix

Tokenization
This section describes how to create and manage jobs. Tokenization uses reversible algorithms so that the data can be returned to it's original
state. Tokenization is a form of encryption where the actual data such as names and addresses are converted into tokens that have similar
properties to the original data (text, length, etc.) but no longer convey any meaning.

Creating a Tokenization Algorithm

1. From the Home page, click Settings.
2. Add Algorithm. You will see the popup below:

3. Select Tokenization Algorithm.

4. Enter a name and description.

Create a Domain
Once you have created an algorithm, you will need to associate it with a domain.
1. From the Home page, click Settings.
2. Select Domains.
3. Click Add Domain. You will see the popup below:

4. Enter a domain name and associate it with your algorithm.

Create a Tokenization Environment

1. From the Home page, click Environments.
2. Click Add Environment. You will see the popup below:

781

Delphix User Guide 2016 Delphix

3. Select Tokenize/Re-Identify as the purpose.

4. Click Save.

Note
This environment will be used to re-identify your data when required.

Create a Connection and Rule Set

At this point, you can proceed in the same fashion as if you were using Delphix to perform normal masking. You have made all the changes
needed to use Tokenization (reversible) algorithms instead of Masking (irreversible) algorithms. Note it is possible to create two different
environments for the same application one for Masking and one for Tokenization.
1. From the Home page, click Environments.
2. Click Connector.
3. Click Create Connection. You will see the popup below:

Create the Rule Set and Apply File Format

If you are masking a file you will need to create a Rule Set and the associated File Format.
1. From the Home page, click Environments.
2.
782

Delphix User Guide 2016 Delphix

2. Click Rule Set.

3. Click Edit Rule Set. You will see the popup below:

Apply the Tokenization Algorithm

In Step 1, you created a tokenization algorithm you can now apply to the field. You will see the popup below:

Create and Execute a Tokenization Job

1. From the Home page, click Environments.
2. Click Tokenize.
3. Set up a Tokenize job using tokenization method. Execute the job.

783

Delphix User Guide 2016 Delphix

4. You will be prompted for the following information:

a. Job Name A free-form name for the job you are creating.
b. Tokenization Method Select Tokenization Method.
c. Multi Tenant Check box if the job is for a multi-tenant database.
d. Rule Set Select a rule set that this job will execute against.
e. Generator
f. No. of Streams The number of parallel streams to use when running the jobs. For example, you can select two streams to
run two tables in the ruleset concurrently in the job instead of one table at a time. (This option only appears if you select DMsuite
as the Generator.)
g. Remote Server (optional) The remote server that will execute the jobs. This option lets you choose to execute jobs on a
remote server, rather than on the local Delphix instance. Note: This is an add-on feature for Delphix Standard Edition. (This
option only appears if you select DMsuite as the Generator.)
h. Min Memory (MB) (optional) Minimum amount of memory to allocate for the job, in megabytes. (This option only appears if
you select DMsuite as the Generator.)
i. Max memory (MB) (optional) Maximum amount of memory to allocate for the job, in megabytes. (This option only appears if
you select DMsuite as the Generator.)
j. Commit Size (optional) The number of rows to process before issuing a commit to the database.
k. Feedback Size (optional) The number of rows to process before writing a message to the logs. Set this parameter to the
appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual
number of rows in a job, the progress for that job will only show 0 or 100%.
l. Disable Constraint (optional) Whether to automatically disable database constraints. The default is for this check box to be

784

Delphix User Guide 2016 Delphix

l.
clear and therefore not perform automatic disabling of constraints. For more information about database constraints, see Enablin
g and Disabling Database Constraints.
m. Batch Update (optional) Enable or disable use of a batch for updates. A job's statements can either be executed individually,
or can be put in a batch file and executed at once, which is faster.
n. Truncate (optional) Whether to truncate target tables before loading them with data. If this box is selected, the tables will be
"cleared" before the operation. If this box is clear, data is appended to tables, which potentially can cause primary key violations.
This box is clear by default.
o. Disable Trigger (optional) Whether to automatically disable database triggers. The default is for this check box to be clear
and therefore not perform automatic disabling of triggers.
p. Drop Index (optional) Whether to automatically drop indexes on columns which are being masked and automatically re-create
the index when the masking job is completed. The default is for this check box to be clear and therefore not perform automatic
dropping of indexes.
q. Prescript (optional) Specify the full pathname of a file containing SQL statements to be run before the job starts, or click Bro
wse to specify a file. If you are editing the job and a prescript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a prescript file was already specified.) For information about creating your own
prescript files, see Creating SQL Statements to Run Before and After Jobs.
r. Postscript (optional) Specify the full pathname of a file containing SQL statements to be run after the job finishes, or click Bro
wse to specify a file. If you are editing the job and a postscript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a postscript file was already specified.) For information about creating your own
postscript files, see Creating SQL Statements to Run Before and After Jobs.
s. Comments (optional) Add comments related to this provisioning job.
t. Email (optional) Add e-mail address(es) to which to send status messages.
5. When you are finished, click Save.

Result Snapshot
Here is a snapshot of the data before and after Tokenization to give you an idea of what the it will look like.
Before Tokenization

After Tokenization

Steps to Re-Identify
Use the Tokenize/Re-Identify environment.
1. From the Home page, click Environments.
2. Click Re-Identify.
3. Create a re-Identify job and execute.

785

Delphix User Guide 2016 Delphix

You will be prompted for the following information:

a. Job Name A free-form name for the job you are creating.
b. Multi Tenant Check box if the job is for a multi-tenant database.
c. Rule Set Select a rule set that this job will execute against.
d. Generator The default value is Delphix.
e. No. of Streams The number of parallel streams to use when running the jobs. For example, you can select two streams to
run two tables in the ruleset concurrently in the job instead of one table at a time. (This option only appears if you select DMsuite
as the Generator.)
f. Remote Server(optional) The remote server that will execute the jobs. This option lets you choose to execute jobs on a
remote server, rather than on the local Delphix instance. Note: This is an add-on feature for Delphix Standard Edition. (This
option only appears if you select DMsuite as the Generator.)
g. Min Memory (MB) (optional) Minimum amount of memory to allocate for the job, in megabytes. (This option only appears if
you select DMsuite as the Generator.)
h. Max memory (MB) (optional) Maximum amount of memory to allocate for the job, in megabytes. (This option only appears if
you select DMsuite as the Generator.)
i. Commit Size (optional) The number of rows to process before issuing a commit to the database.
j. Feedback Size (optional) The number of rows to process before writing a message to the logs. Set this parameter to the
appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual
number of rows in a job, the progress for that job will only show 0 or 100%.
k. Bulk Data (optional) For In-Place masking only. The default is for this check box to be clear. If you are masking very large
tables in-place and require performance improvements, check this box. Delphix will mask data to a flat file, and then use inserts
instead of updates to bulk load the target table. (This option only appears if you select DMsuite as the Generator.)
l. Batch Update (optional) Enable or disable use of a batch for updates. A job's statements can either be executed individually,
or can be put in a batch file and executed at once, which is faster.
m. Drop Index (optional) Whether to automatically drop indexes on columns which are being masked and automatically re-create
the index when the masking job is completed. The default is for this check box to be clear and therefore not perform automatic
dropping of indexes.
n. Prescript (optional) Specify the full pathname of a file containing SQL statements to be run before the job starts, or click Bro

786

Delphix User Guide 2016 Delphix

n.
wse to specify a file. If you are editing the job and a prescript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a prescript file was already specified.) For information about creating your own
prescript files, see Creating SQL Statements to Run Before and After Jobs.
o. Postscript (optional) Specify the full pathname of a file containing SQL statements to be run after the job finishes, or click Bro
wse to specify a file. If you are editing the job and a postscript file is already specified, you can click the Delete button to remove
the file. (The Delete button only appears if a postscript file was already specified.) For information about creating your own
postscript files, see Creating SQL Statements to Run Before and After Jobs.
p. Comments (optional) Add comments related to this provisioning job.
q. Email (optional) Add e-mail address(es) to which to send status messages.
4. When you are finished, click Save.

Result Snapshot
Here is a snapshot of the data before and after re-identification to give you an idea of what to expect.
Before Re-Identification

After Re-Identification

787

Delphix User Guide 2016 Delphix

Monitor Jobs
Click the Monitor tab at the top of the screen to display all of the jobs defined to Delphix.
This screen provides an overview of job activity within the entire Delphix application, and also provides a mechanism to view execution results
and to run or rerun jobs. You will only see jobs associated with environments for which you have the appropriate role definition. If any job does not
succeed, you can correct the errors and then rerun the job.
Figure 21 Monitor Screen

The following columns appear in the Jobs Editor:

Environment
Job Name
Type
Progress
Status
To go to the Environment Overview screen for any environment, click the Environment name.
To see detailed information for any job, click the Job Name.
To search for a job, enter a job name in the SearchFilter field and press Enter.

788

Delphix User Guide 2016 Delphix

Scheduler Tab
Scheduling Job(s) to Run
To schedule new job(s)
To edit a schedule
To delete a schedule
Enabling and Disabling Database Constraints
Creating SQL Statements to Run Before and After Jobs (For Distributed Environment)
Click the Scheduler tab at the top of the screen to display the list of jobs scheduled to run. This screen provides an overview of scheduled jobs
and lets the user configure schedules for jobs to run.
The following columns appear on the Scheduler screen:
Groups
Status
Start
End
Frequency
Edit
Delete
To search for a job group:
1. Enter a job group name in the Search field.
2. Click Search.

Scheduling Job(s) to Run

To schedule new job(s)
1. In the upper right-hand corner of the screen, click Create Scheduler.
The Schedule Jobs screen appears.
Figure 22 Schedule Job Screen

You will be prompted for the following information:

a. Group Name A free-form name for this job schedule.
b. Scheduled Date Enter the date when you want to run the job group, in the form mm/dd/yyyy.
c. Scheduled Time Enter the time when you want to run the job group, in the form hh:mm.
d. Frequency (Optional) Select the frequency at which you want to run this job group: Daily, Weekly, Monthly, Yearly. Default is
daily if none is chosen.
e. Jobs Jobs are grouped by their Environment. Expand Environments and use the check boxes to add jobs to this group.
2.
789

Delphix User Guide 2016 Delphix

2. When you are finished, click Save.

All of the jobs you specified for this job group will be run, serially, beginning at the appointed time.
Jobs will run serially (one after the other). If you want to run jobs simultaneously, create two schedules with the same start time.

Upon completion of each job, an e-mail message that contains job start and end times, along with the completion status, is sent to the user whose
e-mail address is specified in the E mail field (in the Edit Job window).

To edit a schedule
1. From the Scheduler tab, click the Edit icon to the right of the schedule you want.

To delete a schedule
1. Click the Delete icon to the right of the schedule you want.

Enabling and Disabling Database Constraints

Depending on the type of target database you are using, the Delphix Engine can automatically enable and disable database constraints.
The ability to enable and disable constraints ensures that the Delphix Engine can update columns that have primary key or foreign key
relationships. You can set Delphix to handle constraints automatically.
Support for disabling constraints is dependent on your RDBMS. If your RDBMS does not support disabling of foreign keys, for example,
constraints must be added or dropped using prescript or postscript.

Creating SQL Statements to Run Before and After Jobs (For Distributed Environment)
When you create a masking job or a certification job, you can specify SQL statements to run before (prescript) you run a job and/or after
(postscript) the job has completed. For example, if you want to provision a schema from the source to a target, you would use a prescript (SQL
statements) to disable constraints and truncate data on the target.
You create prescript and postscript by creating a text document with the SQL statement(s) to execute. If the text file contains more than one SQL
statement, each statement must be separated by a semicolon [;] EXCEPT when variables are being used in the script. Any time variables are
used, a semicolon should not be used between statements until those variables are no longer needed. For example:

DECLARE @Path VARCHAR(250) [no semicolon after this statement]

Set @Path='C:\temp\file.bak' [no semicolon after this statement]
RESTORE DATABASE Delphix
FROM DISK = @Path WITH FILE = 1; [semicolon at the end]
For information about how and where to specify the pathname for prescript and postscript files, see Creating a New Masking Job , Creating a
New Certify Job , or Creating a New Provisioning Job.

790

Delphix User Guide 2016 Delphix

Settings Tab
This user guide only gives an overview of the Delphix settings. For more detailed information, see the Delphix Administrator's Guide.

Click the Settings tab at the top of the screen to view or change Delphix settings.
There are several areas to which settings are applied:
Algorithms
Types of Algorithms
Domains (Masking)
Profiler
Mapping
File Format
Remote Server

Algorithms
The main methods used by Delphix algorithms are secure lookup and segmented mapping. Delphix also includes some algorithms for specific
types of data, such as phone numbers and dates. These standard Delphix algorithms are available if you select Delphix as the generator.
From the Settings tab, if you click Algorithm to the left, the list of algorithms will be displayed.

Types of Algorithms
Secure Lookup Algorithm Uses a lookup file to assign masked values in a consistent manner. The design of the algorithm introduces
intentional collisions
Segmented Mapping Algorithm Replaces data values based on segment definitions. For example, an ACCOUNT NUMBER algorithm
might keep the first segment of an account number but replace the remainder or remaining segments with a random number.
Mapping Algorithm: Sequentially maps original data values to masked values that are pre-populated to a lookup table through the
Delphix user interface
Binary Lookup Algorithm Much like the Secure Lookup Algorithm, but used when entire files are stored in a specific column
Tokenization Algorithm Replaces the data value with an algorithmically generated token that can be reversed. These are only used
when you create a tokenization environment.
Min/Max Algorithm: This algorithm allows you to make sure all the values in the database are within a specified range. They prevent
unique identification of individuals by characteristics that are outside the normal range, such as age over 99.
Data Cleansing Algorithm If the target data needs to be put in a standard format prior to masking, you can use this algorithm. For
example, Ariz, Az, Arizona can all be cleansed to AZ.
Free Text Redaction Algorithm This algorithms masks or redacts free text columns of files. It uses either a Whitelist or Blacklist to
determine what words are masked or not masked. This algorithm may require additional configuration to work in the manner you desire.
These Delphix Algorithm Frameworks give you the ability to quickly and easily define the algorithms you want, directly on the Settings tab. Then,
you can immediately propagate them. Anyone in your organization who has Delphix can then access the info.

Domains (Masking)
Domains specify certain data to be masked with a certain algorithm.
From the Settings tab, if you click Domains to the left, the list of domains will be displayed. From here, you can add, edit, or delete domains. You
can set a domain's algorithm here; to change a domain's selection expressions or to group domains into sets, continue to the next section.

Profiler
The profiler is used to group domains into Profile Sets (aka Profiles) and assign expressions to domains. Profile Sets can be used in Profiling
Jobs.
From the Settings tab, if you click Profiler to the left, a list of expressions will be displayed. From here, you can work with:
Expressions Expressions are used to specify what data is sensitive. This can be done at either the column or data level. Each
expression is assigned to a domain, and domains can be grouped into profile sets. You can add, edit, or delete expressions from the Prof
iler Settings page.

791

Delphix User Guide 2016 Delphix

Profile Sets (Profiles) A profile set is a group of domains. Said another way, it is a group of certain data to be masked in certain ways.
You can add, edit, or delete profiles by clicking + Profiler Set at the top of the Profiler Settings page.

Mapping
From the Settings tab, if you click Mapping to the left, the list of mappings will be displayed. From here you can add, edit, or delete mappings.

File Format
File formats are a way of organizing the types of files to be masked. Before a file can be masked, it needs to have a file format assigned to it.
From the Settings tab, if you click File Format to the left, the list of file formats will be displayed. From here, you can add or delete file formats.
To assign a file format:
1. In the Rule Set screen, select a rule set.
2. Click the green edit icon to the right of a file.

Remote Server
The Delphix Engine typically executes jobs on a local instance. Remote servers are for executing jobs elsewhere.
From the Settings tab, if you click Remote Server to the left, the list of remote servers will be displayed. From here, you can add, edit, or delete
remote servers.

792

Delphix User Guide 2016 Delphix

Admin Tab
For more detailed Admin information, see the Delphix Administrator's Guide.

Click the Admin tab at the top of the screen for administrator settings and information.

Users
From the Admin tab, if you click Users to the left, the list of users will be displayed. From here you can add, edit, or delete users.
Along with regular user information (name, username, email etc.), users have permissions. You can set these permissions by the user's role and
what environments they can access.

About
From the Admin tab, if you click About to the left, the list of information about your current Delphix installation is shown:
Delphix Version
Operating System
Application Server
Database
Masking
Java Version
Expiration Date
Licensed Data Sources
The following figure shows a sample of the information displayed in the About section:
Figure 23 About Section

793

Delphix User Guide 2016 Delphix

Risk Tab
The screenshot below shows user entitlement information for Oracle databases.

The following columns will display on the Risk screen:

Owner
Table name
Column name
Grantee

Click Create PDF to generate a report.

Ad hoc Reporting on the Delphix Repository

Delphix comes with some sample Adhoc Reports developed using Pentaho Report Designer. The reports run against the Delphix repository and
can either be used as is or modified to create new reports to meet your needs.
The included list of reports are:
Masking Completed A report designed to show how much masking work has been completed in the given time period. It defaults to
the last month. This report only includes successful jobs.
Risk Mitigation Shows how many sensitive data elements have been masked over the last month
Utilization Shows how many jobs have been run and what sort of jobs they are. It also shows how many jobs have been run by the
various Delphix users.

794

Delphix User Guide 2016 Delphix

Restarting Delphix Masking

In case of a power outage or other failure, you will need to restart your Delphix Agile Data Masking application. The procedure below differs
depending on your application server.

Restarting Your Delphix Masking Application for Tomcat/JBoss

1. Go to this directory, where <tomcat_home> is the directory with the tomcat installation:
/<tomcat_home>/bin
For example:
Delphix Agile Data Masking/apache_tomcat_7.0.27/bin
2.

Run the startup.bat file.

Restarting Your Delphix Masking Application for WebLogic Server

1. Go to this directory, where <bea_server_root> is the location of your application server root folder:
<bea_server_root>/userprojects/domains/Delphix Agile Data Masking_domain/bin
For example:
bea_Delphix Agile Data Masking/apache_tomcat_6.0.18/userprojects/domains/Delphix Agile Data
Masking_domain/bin
2.

Run the startupWebLogic.cmd file.

Restarting Your Delphix Masking Application for IBM WebSphere

Select Programs > IBM WebSphere > Application Server ... > Profiles > newly created profile > Start the server.
For example, if the default profile created when you installed WebSphere was AppSrv01, your newly created profile might be AppSrv02:
Programs > IBM WebSphere > Application Server ... > Profiles > AppSrv02 > Start the server.

795

Delphix User Guide 2016 Delphix

Masking Engine Admin Guide

Managing Settings
The Settings Screen

Managing Algorithm Settings

Algorithm Settings Tab
Adding New Masking Engine Algorithms
Secure Lookup Algorithm
Segmented Mapping Algorithm
Segmented Mapping Example
Segmented Mapping Procedure
Mapping Algorithm
Binary Lookup Algorithm
Tokenization Algorithm
Min Max Algorithm
Data Cleansing Algorithm
Free Text Algorithm
Free Text Redaction Example

Managing Domain Settings

Adding New Domains

Managing Profiler Settings

Profiler Settings Tab
Adding New Expressions
Adding or Editing a Profiler Set
Practical Profiling Example

Managing Roles Settings

Roles Settings Tab
Adding Roles

Managing Mapping Settings

Adding Mappings

Managing File Formats

Managing Remote Servers
Managing Users
The Users Screen
Creating and Editing Users

Utilization Reports
The Utilization Screen

796

Delphix User Guide 2016 Delphix

Accessing Information About Your Software

The About Screen

Security
Storing Database Passwords
Authenticating Users
Authorizing Users (Roles)

Configuration
Configuring Masking Engine to use Active Directory
Configuring Log File Locations
Configuring the Default Port
Restarting Masking Engine

Troubleshooting
Memory Usage
Stack Traces
Application Server Down
Database Server Down
Backups and Recovery

797

Delphix User Guide 2016 Delphix

Administration
As a Masking Engine Administrator, you specify what information (data elements) to mask, how to mask the data (the algorithms to use), the
location of the data to mask (regular expressions and profiler settings), and the roles or privileges for Masking Engine users. You perform all this
within Masking Engine and you can then propagate it across all of your organization's departments.
A domain is a virtual representation of a data element. An integral part of the data masking process is to use algorithms to mask each data
element. The way you specify which algorithm to use on each individual data element is by creating a unique domain for each element. You do
this on the Domains tab. You define a unique domain for each element and then associate the classification and algorithm you want to use for
each domain.
In addition to using the Domain settings to determine your inventory of what to mask, a Profiling job uses expressions to identify the data you are
seeking. A regular expression is a special text string that defines a search pattern. You can also group expressions into profiler sets, which are
defined for a given target, such as financial services or health care.
Masking Engine has a built-in Administrator role, which gives a user complete access to Masking Engine functions. You can also add roles to the
Roles Settings. Perhaps you want to define an analyst or developer role, so someone can create masking jobs, or an operator role, to make sure
jobs are run consistently.

798

Delphix User Guide 2016 Delphix

Managing Settings
The Settings Screen
Display the Settings screen by clicking the Settings tab at the top of any Masking Engine screen.
You must have the appropriate user privileges to see this screen.
The Settings screen has the following tabs:
Algorithm Define the algorithms to use to mask your data
Domains Define domains and choose their classification and default masking algorithm
Profiler Define expressions and groupings of expressions used to create your inventory
Roles Define user roles and privileges, such as edit and delete
Mapping Define mapping rules
File Format Define the file format definitions and format types
Remote Server This is an add-on feature for Masking Engine Standard Edition. Define the remote server(s) that will execute jobs.

799

Delphix User Guide 2016 Delphix

The Settings Screen

Display the Settings screen by clicking the Settings tab at the top of any Masking Engine screen.
You must have the appropriate user privileges to see this screen.
The Settings screen has the following tabs:
Algorithm Define the algorithms to use to mask your data
Domains Define domains and choose their classification and default masking algorithm
Profiler Define expressions and groupings of expressions used to create your inventory
Roles Define user roles and privileges, such as edit and delete
Mapping Define mapping rules
File Format Define the file format definitions and format types
Remote Server This is an add-on feature for Masking Engine Standard Edition. Define the remote server(s) that will execute jobs.

800

Delphix User Guide 2016 Delphix

Managing Algorithm Settings

An integral part of the data masking process is to use algorithms to mask each data element. You specify which algorithm to use on each
individual data element (domain) on the Masking's tab. There, you define a unique domain for each element and then associate the classification
and algorithm you want to use for each domain. Use the Algorithm settings tab to create or delete algorithms.
Algorithm Settings Tab
Adding New Masking Engine Algorithms
To add an algorithm:
Secure Lookup Algorithm
Segmented Mapping Algorithm
Segmented Mapping Example
To define these segments:
Segmented Mapping Procedure
To add a segmented mapping algorithm:
Mapping Algorithm
To add a mapping algorithm:
Binary Lookup Algorithm
To add a binary lookup algorithm:
Tokenization Algorithm
Min Max Algorithm
Data Cleansing Algorithm
Free Text Algorithm
Free Text Redaction Example

Algorithm Settings Tab

The Algorithm tab displays algorithm Names along with Type and Description. This is where you add (or create) new algorithms. The default
Masking Engine algorithms and any algorithms you have defined appear on this tab.
All algorithm values are stored encrypted. These values are only decrypted during the masking process.
Figure 1 Algorithm Settings Tab

Adding New Masking Engine Algorithms

You might want to create a new algorithm if none of the default Masking Engine algorithms meet your needs.
Masking Engine Algorithm Frameworks give you the ability to quickly and easily define the algorithms you want, directly on the Settings page.
Then, you can immediately propagate them. Anyone in your organization who has Masking Engine can then access the info.
Note: Administrators can update system defined algorithms. User defined algorithms can be accessed by all users and updated by the
owner/user who created the algorithm.

801

Delphix User Guide 2016 Delphix

To add an algorithm:
1. Click Add Algorithm at the top right of the Algorithm tab.
Select Algorithm Type Popup

2. Choose one of the following:

Secure Lookup Algorithm
Segmented Mapping Algorithm
Mapping Algorithm
Binary Lookup Algorithm
Tokenization Algorithm
Min Max Algorithm
Data Cleansing Algorithm
Free Text Redaction Algorithm
3. Complete the form to the right (corresponding to your selected Algorithm)
4. Click Save.

Secure Lookup Algorithm

A secure lookup algorithm is a proprietary encrypt/hash/modulus algorithm that is repeatable but unbreakable. It lets you assign a realistic value
from a list of predefined values. Use a secure lookup algorithm when you do not need unique values.
To add a secure lookup algorithm:
1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Secure Lookup Algorithm. The Create SL Rule pane appears.
Create Secure Lookup Rule Pane

802

Delphix User Guide 2016 Delphix

3. Enter a Rule Name. (This name must be unique.)

4. Enter a Description.
5. Specify a Lookup File.
This file is a single list of values. It does not require a header. Make sure there are no spaces or returns at the end of the last line in the
file. The following is sample file content:

Example Lookup File

Smallville
Clarkville
Farmville
Townville
Cityname
Citytown
Towneaster

6, When you are finished, click Save.

7. Before you can use the algorithm (specify it in a profiling or masking job), you must add it to a domain.

Note
Masking Engine supports lookup files saved in ASCII or UTF-8 format only. If the lookup file contains foreign alphabet characters, the
file must be saved in UTF-8 format for Masking Engine to read the Unicode text correctly.

Segmented Mapping Algorithm

803

Delphix User Guide 2016 Delphix

Segmented mapping algorithms let you create unique asked values by dividing a target value into separate segments and masking each segment
individually. Optionally, you can preserve the semantically rich part of a value while providing an unique value for the remainder. This is especially
useful for primary keys or columns that need to be unique because they are part of a unique index.
When using segmented mapping algorithms for primary nd foreign keys, to make sure they match, you must use the same segmented mapping
algorithm for each.

Segmented Mapping Example

Perhaps you have an account number for which you need to create a segmented mapping algorithm. You can separate the account number into
segments, preserving the first two-character segment, replacing a segment with a specific value, and preserving a hyphen. The following is a
sample value for this account number:
NM831026-04
Where:
NM is a plan code number that you want to preserve, always a two-character alphanumeric code.
831026 is the uniquely identifiable account number. To ensure that you do not inadvertently create actual account numbers, you can replace the
first two digits with a sequence that never appears in your account numbers in that location. (For example, you can replace the first two digits with
98 because 98 is never used as the first two digits of an account number.) To do that, you want to split these six digits into two segments.
-04 is a location code. You want to preserve the hyphen and you can replace the two digits with a number within a range (in this case, a range of
1 to 77).

To define these segments:

1. Choose 3 for No. of Segment. (Remember, you do not count the segment(s) you want to preserve.)
2. Preserve the first two characters (NM in sample value). Under Preserve Original Values:
a. For Starting position, enter 1.
b. For length, enter 2.
3. Define the next two-digit segment (83 in sample value) to always be 98 or 99:
a. For Segment 1, choose Type > Numeric.
b. Choose Length > 2.
c. For Mask Values Range#, specify 98,99.
4. Define the next four-digit segment (1026 in sample value):
a. For Segment 2, choose Type > Numeric.
b. Choose Length > 4.
c. Leave range fields empty.
d. Click Add to the right of Preserve Original Values.
5. Preserve the hyphen:
a. For Starting position, enter 9.
b. For length, enter 1.
6. Define the last two-digit segment (04 in sample value):
a. For Segment 3, choose Type > Numeric.
b. Choose Length > 2.
c. For Mask Values Min#, specify 1.
d. For Mask Values Max#, specify 77.
The sample value NM831026-04 might be masked to NM98129177.

Segmented Mapping Procedure

To add a segmented mapping algorithm:
1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Segmented Mapping Algorithm.
The Segmented Mapping pane appears.
Segmented Mapping Pane

804

Delphix User Guide 2016 Delphix

3. Enter a Rule Name.

4. Enter a Description.
5. Select how many segments you want to mask (not counting the values you want to preserve) from the No. of Segment dropdown. (The
minimum number of segments is 2; the maximum is 9.)
A box appears for each segment.
6. For each segment, choose the Type of segment from the dropdown: Numeric or AlphaNumeric.
Numeric segments are masked as whole segments. Alphanumeric segments are masked by individual character.
7. For each segment, choose the Length of the segment (number of characters) from the dropdown (maximum is 4).
8. Optionally, for each segment, specify range values. (You might need to specify range values to satisfy particular application
requirements, for example.)
You can specify ranges for Real Values and Mask Values. With Real Values ranges, you can specify all the possible real values to map to the
ranges of masked values. Any values not listed in the Real Values ranges would then mask to themselves.
Specifying range values is optional. If you need unique values ( for example masking a unique key column) you must leave the range
values blank. If you plan to certify your data, you must specify range values.
Numeric segment type:
Min#A number; the first value in the range. (Value can be 1 digit or up to the length of the segment. For example, for a 3-digit
segment, you can specify 1, 2, or 3 digits. Acceptable characters: 0-9.)
Max#A number; the last value in the range. (Value should be the same length as the segment. For example, for a 3-digit
segment, you should specify 3 digits. Acceptable characters: 0-9.)
Range#A range of numbers; separate values in this field with a comma (,). (Value should be the same length as the segment.
For example, for a 3-digit segment, you should specify 3 digits. Acceptable characters: 0-9.)
If you do not specify a range, Masking Engine uses the full range. For example, for a 4-digit segment, Masking Engine uses 0-9999.
Alpha-Numeric segment type:
Min#A number from 0 to 9; the first value in the range.
Max#A number from 0 to 9; the last value in the range.
MinCharA letter from A to Z; the first value in the range.
MaxCharA letter from A to Z; the last value in the range.

805

Delphix User Guide 2016 Delphix

Range#A range of alphanumeric characters; separate values in this field with a comma (,). Individual values can be a number
from 0 to 9 or an uppercase letter from A to Z. (For example, B,C,J,K,Y,Z or AB,DE.)
If you do not specify a range, Masking Engine uses the full range (A-Z, 0-9). If you do not know the format of the input, leave the range fields
empty. If you know the format of the input (for example, always alphanumeric followed by numeric), you can enter range values such as A2 and
S9.
When determining a numeric or alphanumeric range, remember that a narrow range will likely generate duplicate values, which will cause
your job to fail.
To ignore specific characters, enter one or more characters in the Ignore Character List box. Separate values with a comma.
To ignore the comma character (,), select the Ignore comma (,) check box.
To ignore control characters, select Add Control Characters.
The Add Control Characters window appears.
Add Control Characters Window

Select the individual control characters that you would like to ignore, or choose Select All or Select None.
When you are finished, click Save.
You are returned to the Segmented Mapping pane.
9. Preserve Original Values by entering Starting position and length values. (Position starts at 1.)
For example, to preserve the second, third, and fourth values, enter Starting position 2 and length 3.
If you need additional value fields, click Add.
10. When you are finished, click Save.
11. Before you can use the algorithm (specify it in a profiling or masking job), you must add it to a domain. If you are not using the Masking
Engine Profiler to create your inventory, you do not need to associate the algorithm with a domain.

Mapping Algorithm
A mapping algorithm sequentially maps original data values to masked values that are pre-populated to a lookup table through the Masking
Engine user interface. With the mapping algorithm, you must supply at minimum, the same number of values as the number of unique values you
are masking, more is acceptable. For example if there are 10000 unique values in the column you are masking you must give the mapping
algorithm at least 10000 values.

To add a mapping algorithm:

1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Mapping Algorithm.
The MAPPING Rule pane appears.
Create Mapping Rule Pane

806

Delphix User Guide 2016 Delphix

3. Enter a Rule Name. (This name must be unique.)

4. Enter a Description.
5. Specify aLookup File (.txt){*}.
The value file must have NO header. Make sure there are no spaces or returns at the end of the last line in the file.
The following is sample file content (notice there's no header and only a list of values):
SmallvilleClarkvilleFarmvilleTownvilleCitynameCitytownTowneaster
6. To ignore specific characters, enter one or more characters in the Ignore Character List box. Separate values with a comma.
To ignore the comma character (,), select the Ignore comma (,) check box.
7. When you are finished, click Save.
Before you can use the algorithm (specify it in a profiling or masking job), you must add it to a domain. If you are not using the Masking
Engine Profiler to create your inventory, you do not need to associate the algorithm with a domain.
See Adding New Domains.

Binary Lookup Algorithm

A Binary Lookup Algorithm is much like the Secure Lookup Algorithm, but is used when entire files are stored in a specific column. This is useful
for masking binary columns (e.g. blob, image, varbinary, etc).

To add a binary lookup algorithm:

1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Binary Lookup Algorithm.
The Binary SL Rule pane appears.

807

Delphix User Guide 2016 Delphix

3. Enter a Rule Name.

4. Enter a Description.
5. Select a Binary Lookup File on your filesystem.
6. Click Save.

Tokenization Algorithm
Tokenization uses reversible algorithms so that the data can be returned to its original state. Tokenization is a form of encryption where the actual
data ( e.g. names and addresses) are converted into tokens that have similar properties to the original data (text, length, etc) but no longer convey
any meaning.

1. Enter Algorithm Name.

2. Enter a Description.
3. Click Save.
4. Once you have created an Algorithm you will need to associate it with a domain. Navigate to the Home>Settings>Domains page and
press the Add Domain button. You will see the popup below:

808

Delphix User Guide 2016 Delphix

Create a Domain

1. Enter a domain name and associate it with your algorithm.

Create a Tokenization Environment
2. Navigate to the Home>Environments page and press the Add Environment button. You will see the popup below:

3. Select Tokenize/Re-Identify as the purpose and Save. Note: This environment will be used to Re-Identify your data when required.
4. Set up a Tokenize job using tokenization method. Execute the job

809

Delphix User Guide 2016 Delphix

Result Snapshot
Here is a snapshot of the data before and after Tokenization to give you an idea of what the it will look like.
Before Tokenization

810

Delphix User Guide 2016 Delphix

After Tokenization

Min Max Algorithm

Masking Engine provides a "Min Max Algorithm" to Normalize data within a range e.g. 10 to 400. This algorithm allows you to make sure all the
values in the database are within a specified range. They prevent unique identification of individuals by characteristics that are outside the normal
range (i.e. age over 99).
If "Out of range Replacement value is checked a default value is used when the input cannot be evaluated

1. Enter Algorithm Name.

2. Enter a Description.
3. Enter Min value, Max value
4. Click Out of range Replacement Value
5. Click Save.
Example: Age less than 18 years - enter Min Value 0 and Max Value 18

Data Cleansing Algorithm

Data Cleansing Algorithm Masking Engine provides a data based lookup algorithm. If the target data needs to be put in a standard format prior
to masking these algorithms can be used ( i.e. Ariz, Az, Arizona can all be cleansed to AZ)

811

Delphix User Guide 2016 Delphix

1. Enter Algorithm Name.

2. Enter a Description.
3. Select Lookup file location
4. Enter default delimiter for Key and Value separator is =. User can change it to match lookup file
5. Click Save.
This is an example of a lookup input file. It does not require a header. Make sure there are no spaces or returns at the end of the last line in the
file.
The following is sample file content:
NYC=NYNY City =NYNew York=NYManhattan=NY

Free Text Algorithm

Masking Engine can perform masking of free text or comment fields for flat files and databases sources. These algorithms are to mask or redact
free text columns of files. It uses either a Whitelist or Blacklist to determine what words get masked or not masked. The blacklist feature will match
the data in the look up file to the input file. The Whitelist feature enables you to mask data using both the look up file and a profile set.

812

Delphix User Guide 2016 Delphix

You will be prompted for the following information:

a. Enter algorithm name
b. Enter description
c. Select the Black List or White List radio button
d. Select look up file and enter redaction value
OR/AND
a. Select Profiler Set from drop down and enter redaction value
b. Click Save

Free Text Redaction Example

1. Create Input File
2. Create input file using notepad. Enter the following text.
"The customer Bob Jones is satisfied with the terms of the sales agreement. Please call to confirm at 718-223-7896."
3. Save file as txt.
4. *Create look up file:*
a. Create a lookup file.
b. Use notepad to create a txt file and save the file as a TXT. Be sure to hit return after each field. The lookup flat file contains the
following data:
Bob
Jones
Agreement
Create Algorithm:
You will be prompted for the following information:
1. Enter algorithm name Blacklist_Test1
2. Enter description Blacklist Test
3.
813

Delphix User Guide 2016 Delphix

3. Select the Black List radio button

4. Select look up file and enter redaction value "XXXX"
5. Click save
Create Ruleset:
1. From the job page go to Rule Set and Click Create Rule Set.

You will be prompted for the following information:

Enter Rule Set Name i.e.; Free_ Text_RS
Choose Connector Mode from drop down Free Text
Select the Input File by clicking the box next to your input file
Click *Save*
Create Masking Job
1. Use Free_Texr Rule Set
2. Execute Masking job.
The results of the masking job will show the following:
Redacted Input File: The customer xxxx xxxx is satisfied with the terms of the sales xxxx. Please call to confirm at 718-223-7896.
Bob, Jones and agreement are redacted

814

Delphix User Guide 2016 Delphix

Algorithm Settings Tab

The Algorithm tab displays algorithm Names along with Type and Description. This is where you add (or create) new algorithms. The default
Masking Engine algorithms and any algorithms you have defined appear on this tab.
All algorithm values are stored encrypted. These values are only decrypted during the masking process.
Figure 1 Algorithm Settings Tab

815

Delphix User Guide 2016 Delphix

Adding New Masking Engine Algorithms

You might want to create a new algorithm if none of the default Masking Engine algorithms meet your needs.
Masking Engine Algorithm Frameworks give you the ability to quickly and easily define the algorithms you want, directly on the Settings page.
Then, you can immediately propagate them. Anyone in your organization who has Masking Engine can then access the info.
Note: Administrators can update system defined algorithms. User defined algorithms can be accessed by all users and updated by the
owner/user who created the algorithm.

To add an algorithm:
1. Click Add Algorithm at the top right of the Algorithm tab.
Select Algorithm Type Popup

2. Choose one of the following:

Secure Lookup Algorithm
Segmented Mapping Algorithm
Mapping Algorithm
Binary Lookup Algorithm
Tokenization Algorithm
Min Max Algorithm
Data Cleansing Algorithm
Free Text Redaction Algorithm
3. Complete the form to the right (corresponding to your selected Algorithm)
4. Click Save.

816

Delphix User Guide 2016 Delphix

Secure Lookup Algorithm

A secure lookup algorithm is a proprietary encrypt/hash/modulus algorithm that is repeatable but unbreakable. It lets you assign a realistic value
from a list of predefined values. Use a secure lookup algorithm when you do not need unique values.
To add a secure lookup algorithm:
1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Secure Lookup Algorithm. The Create SL Rule pane appears.
Create Secure Lookup Rule Pane

3. Enter a Rule Name. (This name must be unique.)

4. Enter a Description.
5. Specify a Lookup File.
This file is a single list of values. It does not require a header. Make sure there are no spaces or returns at the end of the last line in the
file. The following is sample file content:

Example Lookup File

Smallville
Clarkville
Farmville
Townville
Cityname
Citytown
Towneaster

6, When you are finished, click Save.

7. Before you can use the algorithm (specify it in a profiling or masking job), you must add it to a domain.

Note
Masking Engine supports lookup files saved in ASCII or UTF-8 format only. If the lookup file contains foreign alphabet characters, the
file must be saved in UTF-8 format for Masking Engine to read the Unicode text correctly.

817

Delphix User Guide 2016 Delphix

Segmented Mapping Example

Perhaps you have an account number for which you need to create a segmented mapping algorithm. You can separate the account number into
segments, preserving the first two-character segment, replacing a segment with a specific value, and preserving a hyphen. The following is a
sample value for this account number:
NM831026-04
Where:
NM is a plan code number that you want to preserve, always a two-character alphanumeric code.
831026 is the uniquely identifiable account number. To ensure that you do not inadvertently create actual account numbers, you can replace the
first two digits with a sequence that never appears in your account numbers in that location. (For example, you can replace the first two digits with
98 because 98 is never used as the first two digits of an account number.) To do that, you want to split these six digits into two segments.
-04 is a location code. You want to preserve the hyphen and you can replace the two digits with a number within a range (in this case, a range of
1 to 77).

To define these segments:

1. Choose 3 for No. of Segment. (Remember, you do not count the segment(s) you want to preserve.)
2. Preserve the first two characters (NM in sample value). Under Preserve Original Values:
a. For Starting position, enter 1.
b. For length, enter 2.
3. Define the next two-digit segment (83 in sample value) to always be 98 or 99:
a. For Segment 1, choose Type > Numeric.
b. Choose Length > 2.
c. For Mask Values Range#, specify 98,99.
4. Define the next four-digit segment (1026 in sample value):
a. For Segment 2, choose Type > Numeric.
b. Choose Length > 4.
c. Leave range fields empty.
d. Click Add to the right of Preserve Original Values.
5. Preserve the hyphen:
a. For Starting position, enter 9.
b. For length, enter 1.
6. Define the last two-digit segment (04 in sample value):
a. For Segment 3, choose Type > Numeric.
b. Choose Length > 2.
c. For Mask Values Min#, specify 1.
d. For Mask Values Max#, specify 77.
The sample value NM831026-04 might be masked to NM98129177.

818

Delphix User Guide 2016 Delphix

Segmented Mapping Procedure

To add a segmented mapping algorithm:
1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Segmented Mapping Algorithm.
The Segmented Mapping pane appears.
Segmented Mapping Pane

3. Enter a Rule Name.

4. Enter a Description.
5. Select how many segments you want to mask (not counting the values you want to preserve) from the No. of Segment dropdown. (The
minimum number of segments is 2; the maximum is 9.)
A box appears for each segment.
6. For each segment, choose the Type of segment from the dropdown: Numeric or AlphaNumeric.
Numeric segments are masked as whole segments. Alphanumeric segments are masked by individual character.
7. For each segment, choose the Length of the segment (number of characters) from the dropdown (maximum is 4).
8. Optionally, for each segment, specify range values. (You might need to specify range values to satisfy particular application
requirements, for example.)
You can specify ranges for Real Values and Mask Values. With Real Values ranges, you can specify all the possible real values to map to the
ranges of masked values. Any values not listed in the Real Values ranges would then mask to themselves.
Specifying range values is optional. If you need unique values ( for example masking a unique key column) you must leave the range
values blank. If you plan to certify your data, you must specify range values.
Numeric segment type:
Min#A number; the first value in the range. (Value can be 1 digit or up to the length of the segment. For example, for a 3-digit
segment, you can specify 1, 2, or 3 digits. Acceptable characters: 0-9.)
Max#A number; the last value in the range. (Value should be the same length as the segment. For example, for a 3-digit
segment, you should specify 3 digits. Acceptable characters: 0-9.)
Range#A range of numbers; separate values in this field with a comma (,). (Value should be the same length as the segment.
For example, for a 3-digit segment, you should specify 3 digits. Acceptable characters: 0-9.)

819

Delphix User Guide 2016 Delphix

If you do not specify a range, Masking Engine uses the full range. For example, for a 4-digit segment, Masking Engine uses 0-9999.
Alpha-Numeric segment type:
Min#A number from 0 to 9; the first value in the range.
Max#A number from 0 to 9; the last value in the range.
MinCharA letter from A to Z; the first value in the range.
MaxCharA letter from A to Z; the last value in the range.
Range#A range of alphanumeric characters; separate values in this field with a comma (,). Individual values can be a number
from 0 to 9 or an uppercase letter from A to Z. (For example, B,C,J,K,Y,Z or AB,DE.)
If you do not specify a range, Masking Engine uses the full range (A-Z, 0-9). If you do not know the format of the input, leave the range fields
empty. If you know the format of the input (for example, always alphanumeric followed by numeric), you can enter range values such as A2 and
S9.
When determining a numeric or alphanumeric range, remember that a narrow range will likely generate duplicate values, which will cause
your job to fail.
To ignore specific characters, enter one or more characters in the Ignore Character List box. Separate values with a comma.
To ignore the comma character (,), select the Ignore comma (,) check box.
To ignore control characters, select Add Control Characters.
The Add Control Characters window appears.
Add Control Characters Window

Select the individual control characters that you would like to ignore, or choose Select All or Select None.
When you are finished, click Save.
You are returned to the Segmented Mapping pane.
9. Preserve Original Values by entering Starting position and length values. (Position starts at 1.)
For example, to preserve the second, third, and fourth values, enter Starting position 2 and length 3.
If you need additional value fields, click Add.
10. When you are finished, click Save.
11. Before you can use the algorithm (specify it in a profiling or masking job), you must add it to a domain. If you are not using the Masking
Engine Profiler to create your inventory, you do not need to associate the algorithm with a domain.

820

Delphix User Guide 2016 Delphix

Mapping Algorithm
A mapping algorithm sequentially maps original data values to masked values that are pre-populated to a lookup table through the Masking
Engine user interface. With the mapping algorithm, you must supply at minimum, the same number of values as the number of unique values you
are masking, more is acceptable. For example if there are 10000 unique values in the column you are masking you must give the mapping
algorithm at least 10000 values.

To add a mapping algorithm:

1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Mapping Algorithm.
The MAPPING Rule pane appears.
Create Mapping Rule Pane

3. Enter a Rule Name. (This name must be unique.)

4. Enter a Description.
5. Specify aLookup File (.txt){*}.
The value file must have NO header. Make sure there are no spaces or returns at the end of the last line in the file.
The following is sample file content (notice there's no header and only a list of values):
SmallvilleClarkvilleFarmvilleTownvilleCitynameCitytownTowneaster
6. To ignore specific characters, enter one or more characters in the Ignore Character List box. Separate values with a comma.
To ignore the comma character (,), select the Ignore comma (,) check box.
7. When you are finished, click Save.
Before you can use the algorithm (specify it in a profiling or masking job), you must add it to a domain. If you are not using the Masking
Engine Profiler to create your inventory, you do not need to associate the algorithm with a domain.
See Adding New Domains.

821

Delphix User Guide 2016 Delphix

Binary Lookup Algorithm

A Binary Lookup Algorithm is much like the Secure Lookup Algorithm, but is used when entire files are stored in a specific column. This is useful
for masking binary columns (e.g. blob, image, varbinary, etc).

To add a binary lookup algorithm:

1. Click Add Algorithm at the top right of the Algorithm tab.
2. Choose Binary Lookup Algorithm.
The Binary SL Rule pane appears.

3. Enter a Rule Name.

4. Enter a Description.
5. Select a Binary Lookup File on your filesystem.
6. Click Save.

822

Delphix User Guide 2016 Delphix

Tokenization Algorithm
Tokenization uses reversible algorithms so that the data can be returned to its original state. Tokenization is a form of encryption where the actual
data ( e.g. names and addresses) are converted into tokens that have similar properties to the original data (text, length, etc) but no longer convey
any meaning.

1. Enter Algorithm Name.

2. Enter a Description.
3. Click Save.
4. Once you have created an Algorithm you will need to associate it with a domain. Navigate to the Home>Settings>Domains page and
press the Add Domain button. You will see the popup below:
Create a Domain

1. Enter a domain name and associate it with your algorithm.

Create a Tokenization Environment
2. Navigate to the Home>Environments page and press the Add Environment button. You will see the popup below:

823

Delphix User Guide 2016 Delphix

3. Select Tokenize/Re-Identify as the purpose and Save. Note: This environment will be used to Re-Identify your data when required.
4. Set up a Tokenize job using tokenization method. Execute the job

Result Snapshot
Here is a snapshot of the data before and after Tokenization to give you an idea of what the it will look like.
Before Tokenization

824

Delphix User Guide 2016 Delphix

After Tokenization

825

Delphix User Guide 2016 Delphix

Min Max Algorithm

Masking Engine provides a "Min Max Algorithm" to Normalize data within a range e.g. 10 to 400. This algorithm allows you to make sure all the
values in the database are within a specified range. They prevent unique identification of individuals by characteristics that are outside the normal
range (i.e. age over 99).
If "Out of range Replacement value is checked a default value is used when the input cannot be evaluated

1. Enter Algorithm Name.

2. Enter a Description.
3. Enter Min value, Max value
4. Click Out of range Replacement Value
5. Click Save.
Example: Age less than 18 years - enter Min Value 0 and Max Value 18

826

Delphix User Guide 2016 Delphix

Data Cleansing Algorithm

Data Cleansing Algorithm Masking Engine provides a data based lookup algorithm. If the target data needs to be put in a standard format prior
to masking these algorithms can be used ( i.e. Ariz, Az, Arizona can all be cleansed to AZ)

1. Enter Algorithm Name.

2. Enter a Description.
3. Select Lookup file location
4. Enter default delimiter for Key and Value separator is =. User can change it to match lookup file
5. Click Save.
This is an example of a lookup input file. It does not require a header. Make sure there are no spaces or returns at the end of the last line in the
file.
The following is sample file content:
NYC=NYNY City =NYNew York=NYManhattan=NY

827

Delphix User Guide 2016 Delphix

Free Text Algorithm

Masking Engine can perform masking of free text or comment fields for flat files and databases sources. These algorithms are to mask or redact
free text columns of files. It uses either a Whitelist or Blacklist to determine what words get masked or not masked. The blacklist feature will match
the data in the look up file to the input file. The Whitelist feature enables you to mask data using both the look up file and a profile set.

You will be prompted for the following information:

a. Enter algorithm name
b. Enter description
c. Select the Black List or White List radio button
d. Select look up file and enter redaction value
OR/AND
a. Select Profiler Set from drop down and enter redaction value
b. Click Save

828

Delphix User Guide 2016 Delphix

Free Text Redaction Example

1. Create Input File
2. Create input file using notepad. Enter the following text.
"The customer Bob Jones is satisfied with the terms of the sales agreement. Please call to confirm at 718-223-7896."
3. Save file as txt.
4. *Create look up file:*
a. Create a lookup file.
b. Use notepad to create a txt file and save the file as a TXT. Be sure to hit return after each field. The lookup flat file contains the
following data:
Bob
Jones
Agreement
Create Algorithm:
You will be prompted for the following information:
1. Enter algorithm name Blacklist_Test1
2. Enter description Blacklist Test
3. Select the Black List radio button
4. Select look up file and enter redaction value "XXXX"
5. Click save
Create Ruleset:
1. From the job page go to Rule Set and Click Create Rule Set.

You will be prompted for the following information:

Enter Rule Set Name i.e.; Free_ Text_RS
Choose Connector Mode from drop down Free Text
Select the Input File by clicking the box next to your input file
Click *Save*
Create Masking Job
1. Use Free_Texr Rule Set
2. Execute Masking job.
The results of the masking job will show the following:
Redacted Input File: The customer xxxx xxxx is satisfied with the terms of the sales xxxx. Please call to confirm at 718-223-7896.
Bob, Jones and agreement are redacted

829

Delphix User Guide 2016 Delphix

Managing Domain Settings

The Domains tab is where you define Domains along with their Classification and default Masking Algorithm.

Figure 7 Domains Tab

Masking Engine includes several default domains and algorithms. These appear the first time you display the Masking Settings tab. Each
domain has a classification and masking method assigned to it. You might choose to assign a different algorithm to a domain, but each domain
name is unique and can only be associated with one algorithm.
If you create additional algorithms, they will appear in the Algorithms dropdown. Because each algorithm used must have a unique domain, you
need to add a domain or reassign an existing domain in order to use any other algorithms. If you create mapplets, you need to follow the
instructions in Error! Reference source not found to integrate them and add them to the Algorithms dropdown list.

To add a Domain:
1. Click Add Domain at the Top of the Domains tab.
A new domain will be created in-line.
Add Domain Window

2. Name the new Domain Name.

The domain name you specify will appear as a menu option on the Inventory screen elsewhere in Masking Engine. Domain names must
be unique.
3. Specify the Classification (informational only); for example, customer-facing data, employee data, or company data.
4. Select a default Masking Algorithm for the new domain.
For information about algorithm settings, see Managing Algorithm Settings.

830

Delphix User Guide 2016 Delphix

5. Click Save.

To delete any Domain:

1. Click the Delete icon to the far right of the domain name.

831

Delphix User Guide 2016 Delphix

Adding New Domains

To add a Domain:
1. Click Add Domain at the Top of the Domains tab.
A new domain will be created in-line.
Add Domain Window

2. Name the new Domain Name.

The domain name you specify will appear as a menu option on the Inventory screen elsewhere in Masking Engine. Domain names must
be unique.
3. Specify the Classification (informational only); for example, customer-facing data, employee data, or company data.
4. Select a default Masking Algorithm for the new domain.
For information about algorithm settings, see Managing Algorithm Settings.
5. Click Save.

To delete any Domain:

1. Click the Delete icon to the far right of the domain name.

832

Delphix User Guide 2016 Delphix

Managing Profiler Settings

The Masking Engine profiler uses two different methods to identify the location of sensitive data:
At the metadata levelsearches through the column names in the target database, by querying the database catalog, looking for
specific words in column names (for example, column names with "name" in them).
At the data levellooks at the data itself using a sampling algorithm, to see whether there is any sensitive data.
Masking Engine then uses that profile information to generate the appropriate jobs that will mask the target database. The user defines the
connections to the databases to profile and then uses the Masking Engine software to perform the Profiling. When the profiling is complete, the
information is stored as profile metadata for Masking Engine processing in the locally hosted or network Masking Engine database.

Profiler Settings Tab

You can add regular expressions and profiler sets to the Profiler Settings. In addition to using the Masking settings to determine your inventory of
what to mask, a Profiling job uses expressions to identify the data you are seeking. For more information about profiling, see "About Profiling
Data" in Masking Engine User's Guide.
The Profiler displays Domains along with their Expression Text, Expression Name, and Expression Level.
Profiler Settings Tab

Adding New Expressions

Expressions let you specify how you want to profile data by letting you determine the data to profile based on the criteria you enter in the
expressions. For example, you can define an expression that looks for a name or partial name for a column and only profiles data in columns that
match that name or partial name. The following table shows some sample expressions.
Sample Expressions
Expression

Column
Description

Data Description

(i:ad(d

dress)_line1

ad(d

dress)1

city_ad(d

dress)

(.[\s]+b(ou)?l(e)?v(ar)?d[\
s].*)

(.[\s]+st[.]?(reet)?[\
s].*)

(.[\s]+ave[.]?(nue)?[\
s].*)

(.[\s]+r(oa)?d[\
s].*)

(.[\s]+l(a)?n(e)?[\
s].*)

(.[\s]+cir(cle)?[\
s].*)

(?i)(.[\s]*ap(ar)?t(ment)?[\
s]+.)

(.[\s]*s(ui)?te[\s]+.)

(c(are)?[\s][\\\\\]?[/]?o
(f)?[\s]+.)

833

Looks for address

line 2 information
in the data

ad(d

Delphix User Guide 2016 Delphix

For sample expressions and tools, see http://www.regular-expressions.info/ or perform an Internet search for "regular expressions".
(Disclaimer: We have provided this resource as a suggestion. Axis Technology does not endorse this or any other related site.)

To add an expression:
1. Click Add Expression at the top of the Profiler tab.
A new expression will be created in-line.
2. Select a domain from the Domain dropdown.
Note: Only the default Masking Engine domains and the domains you have defined appear in this dropdown. If you need to add a domain, see
page 28.
1. Enter the following information for that domain:
Expression NameThe field name used to select this expression as part of a profiler set.
Expression TextThe regular expression used to identify the location of the sensitive data.
2. Select an Expression Level for the domain:
Column LevelTo identify sensitive data based on column names.
Data LevelTo identify sensitive data based on data values, not column names.
3. When you are finished, click Save.
Add Expression Window

To delete an expression:
Click the Delete icon to the far right of the name.

Adding or Editing a Profiler Set

You can define Profiler Sets in Masking Engine. A profiler set is a grouping of expressions for a particular purpose. For instance, First Name, Last
Name, Address, Credit Card, SSN, and Bank Account Number could constitute a Financial Profiler Set. For information about creating a profiling
job, see "Creating a New Profiling Job" in Masking Engine User's Guide.
Masking Engine comes with two predefined profiler sets: Financial and Healthcare vertical. A Masking Engine administrator (a user with the
appropriate role privileges) can create/add/update/delete these profiler sets.
If you don't choose a profiler set as part of the Profiler job, Masking Engine profiles data based on all the expressions defined on the Profiler
Settings page.
If you want to edit or add a profiler set, click Profiler Set at the top of the Profiler tab. The Profiler Set screen appears, listing the profiler sets
along with their Purpose and Date Created.

To edit a profiler set:

Click the Edit icon to the right of the Profiler Set name.

To delete a profiler set:

Click the Delete icon to the right of the Profiler Set name.
Profiler Set Window

834

Delphix User Guide 2016 Delphix

To add a profiler set:

1. Click Add Set. The Create Profile Set window appears.
2. Enter a profile Set Name.
3. Optionally, enter a Purpose for this profile set.
4. Enter/select which Domains to include in this set.
5. When you are finished, click Submit.
Add Set Window

Practical Profiling Example

This section provides an example of how you might define the data you want to profile.
Starting on the Profiler Settings page, you might want to look for First Name. Specify a regular expression to specify how to look for it. If the
expression is column-name specific, Masking Engine will identify which column names match the pattern specified in the expression. If Masking
Engine finds a match, it will tag it as a sensitive column. If an expression matches multiple columns in a table, Masking Engine tags all the
columns for which it finds a match, not just the first column in the table. However, if multiple expressions match one column, Masking Engine tags
the first match in that column.
Profiling data takes a sample against the column. (Data sampling does not apply to mainframe processing.) Masking Engine does not look at all
rows, but the first n (n being 10,000 rows, 100,000 rows, and so on). (The value of n is set in the kettle-profiling.properties file by the
NO_OF_ROWS property.)
So, if you want to look for First Names across all of your databases, specify the following expression on the Profiler Settings page:
[Nn][Aa][Mm][Ee]

835

Delphix User Guide 2016 Delphix

If the expression is at a data level, you can look for common names such as John and Mary:
(([Jj][Oo][Hh][Nn])|[Mm][Aa][Rr][Yy]))
This expression looks for the names John and Mary in the database. If Masking Engine finds any, it identifies that as a First Name column.
You can also search based on format. For instance you can look for a social security number by looking for nine digits of data, with two hyphens
(at positions 4,1 and 7,1): ^\d{3}\d{2}\d{4}$

836

Delphix User Guide 2016 Delphix

Profiler Settings Tab

You can add regular expressions and profiler sets to the Profiler Settings. In addition to using the Masking settings to determine your inventory of
what to mask, a Profiling job uses expressions to identify the data you are seeking. For more information about profiling, see "About Profiling
Data" in Masking Engine User's Guide.
The Profiler displays Domains along with their Expression Text, Expression Name, and Expression Level.
Profiler Settings Tab

837

Delphix User Guide 2016 Delphix

Adding New Expressions

Expressions let you specify how you want to profile data by letting you determine the data to profile based on the criteria you enter in the
expressions. For example, you can define an expression that looks for a name or partial name for a column and only profiles data in columns that
match that name or partial name. The following table shows some sample expressions.
Sample Expressions
Expression

Column
Description

Data Description

(i:ad(d

dress)_line1

ad(d

dress)1

city_ad(d

dress)

(.[\s]+b(ou)?l(e)?v(ar)?d[\
s].*)

(.[\s]+st[.]?(reet)?[\
s].*)

(.[\s]+ave[.]?(nue)?[\
s].*)

(.[\s]+r(oa)?d[\
s].*)

(.[\s]+l(a)?n(e)?[\
s].*)

(.[\s]+cir(cle)?[\
s].*)

(?i)(.[\s]*ap(ar)?t(ment)?[\
s]+.)

(.[\s]*s(ui)?te[\s]+.)

(c(are)?[\s][\\\\\]?[/]?o
(f)?[\s]+.)

Looks for address

line 2 information
in the data

For sample expressions and tools, see http://www.regular-expressions.info/ or perform an Internet search for "regular expressions".
(Disclaimer: We have provided this resource as a suggestion. Axis Technology does not endorse this or any other related site.)

To add an expression:
1. Click Add Expression at the top of the Profiler tab.
A new expression will be created in-line.
2. Select a domain from the Domain dropdown.
Note: Only the default Masking Engine domains and the domains you have defined appear in this dropdown. If you need to add a domain, see
page 28.
1. Enter the following information for that domain:
Expression NameThe field name used to select this expression as part of a profiler set.
Expression TextThe regular expression used to identify the location of the sensitive data.
2. Select an Expression Level for the domain:
Column LevelTo identify sensitive data based on column names.
Data LevelTo identify sensitive data based on data values, not column names.
3. When you are finished, click Save.
Add Expression Window

To delete an expression:

838

ad(d

Delphix User Guide 2016 Delphix

Click the Delete icon to the far right of the name.

839

Delphix User Guide 2016 Delphix

Adding or Editing a Profiler Set

You can define Profiler Sets in Masking Engine. A profiler set is a grouping of expressions for a particular purpose. For instance, First Name, Last
Name, Address, Credit Card, SSN, and Bank Account Number could constitute a Financial Profiler Set. For information about creating a profiling
job, see "Creating a New Profiling Job" in Masking Engine User's Guide.
Masking Engine comes with two predefined profiler sets: Financial and Healthcare vertical. A Masking Engine administrator (a user with the
appropriate role privileges) can create/add/update/delete these profiler sets.
If you don't choose a profiler set as part of the Profiler job, Masking Engine profiles data based on all the expressions defined on the Profiler
Settings page.
If you want to edit or add a profiler set, click Profiler Set at the top of the Profiler tab. The Profiler Set screen appears, listing the profiler sets
along with their Purpose and Date Created.

To edit a profiler set:

Click the Edit icon to the right of the Profiler Set name.

To delete a profiler set:

Click the Delete icon to the right of the Profiler Set name.
Profiler Set Window

To add a profiler set:

1. Click Add Set. The Create Profile Set window appears.
2. Enter a profile Set Name.
3. Optionally, enter a Purpose for this profile set.
4. Enter/select which Domains to include in this set.
5. When you are finished, click Submit.
Add Set Window

840

Delphix User Guide 2016 Delphix

841

Delphix User Guide 2016 Delphix

Practical Profiling Example

This section provides an example of how you might define the data you want to profile.
Starting on the Profiler Settings page, you might want to look for First Name. Specify a regular expression to specify how to look for it. If the
expression is column-name specific, Masking Engine will identify which column names match the pattern specified in the expression. If Masking
Engine finds a match, it will tag it as a sensitive column. If an expression matches multiple columns in a table, Masking Engine tags all the
columns for which it finds a match, not just the first column in the table. However, if multiple expressions match one column, Masking Engine tags
the first match in that column.
Profiling data takes a sample against the column. (Data sampling does not apply to mainframe processing.) Masking Engine does not look at all
rows, but the first n (n being 10,000 rows, 100,000 rows, and so on). (The value of n is set in the kettle-profiling.properties file by the
NO_OF_ROWS property.)
So, if you want to look for First Names across all of your databases, specify the following expression on the Profiler Settings page:
[Nn][Aa][Mm][Ee]
If the expression is at a data level, you can look for common names such as John and Mary:
(([Jj][Oo][Hh][Nn])|[Mm][Aa][Rr][Yy]))
This expression looks for the names John and Mary in the database. If Masking Engine finds any, it identifies that as a First Name column.
You can also search based on format. For instance you can look for a social security number by looking for nine digits of data, with two hyphens
(at positions 4,1 and 7,1): ^\d{3}\d{2}\d{4}$

842

Delphix User Guide 2016 Delphix

Managing Roles Settings

Masking Engine has a built-in Administrator role, which gives a user complete access to Masking Engine functions. This is similar to a superuser
role. The administrator can access, update, and delete all environments, and all objects within those environments. The administrator can also
add roles to the Roles Settings. The following are some sample roles and associated tasks:
Analyst roleCan profile data and update inventories (but not create environments or connections)
Developer roleCan create masking jobs and view reports
Operator roleCan execute jobs (but cannot update inventories)
Application owner roleCan define connections
Each username can only have one role assigned to it.

Roles Settings Tab

The Roles tab displays the Roles that you have created. (If you have not created any roles, the list will be empty.) If you do not have the
appropriate privileges, the Roles tab will not appear. When you click on a Roles Name or Add Roles, a screen similar to the following appears:
Roles

Adding Roles
To add a role:
1. Click Add Roles near the top of the Roles tab.
2. Enter a Role Name. The types of privileges appear across the top of the table, corresponding to the columns of check boxes:
View
Add
Update
Delete
Copy
Import
Export
The far-left column lists the items for which you can set privileges.
3. Select the check boxes for the corresponding privileges that you want to apply. If there is no check box, that privilege is not available.
For example, if you want this Role to have View, Add, Update, and Run privileges for Masking jobs, select the corresponding check boxes
in the Masking Job row.
4. When you are finished assigning privileges for this Role, click Submit.
Add Role Window

843

Delphix User Guide 2016 Delphix

844

Delphix User Guide 2016 Delphix

Roles Settings Tab

The Roles tab displays the Roles that you have created. (If you have not created any roles, the list will be empty.) If you do not have the
appropriate privileges, the Roles tab will not appear. When you click on a Roles Name or Add Roles, a screen similar to the following appears:
Roles

845

Delphix User Guide 2016 Delphix

Adding Roles
To add a role:
1. Click Add Roles near the top of the Roles tab.
2. Enter a Role Name. The types of privileges appear across the top of the table, corresponding to the columns of check boxes:
View
Add
Update
Delete
Copy
Import
Export
The far-left column lists the items for which you can set privileges.
3. Select the check boxes for the corresponding privileges that you want to apply. If there is no check box, that privilege is not available.
For example, if you want this Role to have View, Add, Update, and Run privileges for Masking jobs, select the corresponding check boxes
in the Masking Job row.
4. When you are finished assigning privileges for this Role, click Submit.
Add Role Window

846

Delphix User Guide 2016 Delphix

Managing Mapping Settings

Mapping Tab

Adding Mappings
To add a new mapping:
1. Click Add Mapping at the upper right. The Add Mapping Rule window appears
2. Select a Mapping Type.
3. Enter a Mapping Name.
4. Enter values for Input and Output.
5. Select a Mapping File from the filesystem.
6. Click Submit.
Add Mapping Rule Window

847

Delphix User Guide 2016 Delphix

Adding Mappings
To add a new mapping:
1. Click Add Mapping at the upper right. The Add Mapping Rule window appears
2. Select a Mapping Type.
3. Enter a Mapping Name.
4. Enter values for Input and Output.
5. Select a Mapping File from the filesystem.
6. Click Submit.
Add Mapping Rule Window

848

Delphix User Guide 2016 Delphix

Managing File Formats

A file format is a template that you can use again and again. This saves you time when creating an inventory for files of the same type. Instead of
recreating an inventory for each file, you can create a file format to associate with the files.
The File Format tab displays the file formats that you have created. (If you have not created any file formats, the list will be empty.)
File Format Tab

To create a new file format

1. Click Create Format at the upper right. The Create File Format window appears.
2. Enter a File Format Name.
3. Choose a File Format Type:
Delimited File
Excel Sheet
Fixed Width File
Type 19
4. Optionally enter a Description.
5. Click Submit.
Create File Format

To import a new file format

1. Click Import Format at the upper right. The Import File Format window appears
2. Select an Import File Type
For a Format Type of Copybook or XML:
1. Select a Connection Mode
2.
849

Delphix User Guide 2016 Delphix

2. Fill out the required fields of the selected Connection Mode

3. Click Browse
4. Click the Select button to the right of the desired import file format
5. Enter a Logical Name
6. Click Submit
For a Format Type of Delimited File, Excel sheet, or Fixed Width File:
1. Click the Select button
2. Browse for the file to import fields from
3. Click Save
The file must have NO header. Make sure there are no spaces or returns at the end of the last line in the file. The field names must be in the
same order they are in the file to be masked.
The following is sample file content for Delimited or Excel file formats. With these formats just the field name is provided.(notice there's no header
and only a list of values):
First_NameLast_NameDOBSSNAddress
CityState
Zip_Code
The following is sample file content for Fixed Width format. In this format the field name is followed by the length of the field, separated by a
comma. (notice there's no header and only a list of values):
First_Name,20Last_Name,30DOB,10SSN,11Address,30
City,20State,2
Zip_Code,10

To delete a file format

Click the Delete icon to the right of the File Format name.
File inventory is based on file format. Therefore, if you make a change to a file inventory, that change applies to all files that use that
format.
You can only add or delete a file format, you cannot edit one.

850

Delphix User Guide 2016 Delphix

To create a new file format

1. Click Create Format at the upper right. The Create File Format window appears.
2. Enter a File Format Name.
3. Choose a File Format Type:
Delimited File
Excel Sheet
Fixed Width File
Type 19
4. Optionally enter a Description.
5. Click Submit.
Create File Format

851

Delphix User Guide 2016 Delphix

To Import a New File Format

1. Click Import Format at the upper right. The Import File Format window appears
2. Select an Import File Type
For a Format Type of Copybook or XML:
1. Select a Connection Mode
2. Fill out the required fields of the selected Connection Mode
3. Click Browse
4. Click the Select button to the right of the desired import file format
5. Enter a Logical Name
6. Click Submit
For a Format Type of Delimited File, Excel sheet, or Fixed Width File:
1. Click the Select button
2. Browse for the file to import fields from
3. Click Save
The file must have NO header. Make sure there are no spaces or returns at the end of the last line in the file. The field names must be in the
same order they are in the file to be masked.
The following is sample file content for Delimited or Excel file formats. With these formats just the field name is provided.(notice there's no header
and only a list of values):
First_NameLast_NameDOBSSNAddress
CityState
Zip_Code
The following is sample file content for Fixed Width format. In this format the field name is followed by the length of the field, separated by a
comma. (notice there's no header and only a list of values):
First_Name,20Last_Name,30DOB,10SSN,11Address,30
City,20State,2
Zip_Code,10

852

Delphix User Guide 2016 Delphix

To delete a file format

Click the Delete icon to the right of the File Format name.
File inventory is based on file format. Therefore, if you make a change to a file inventory, that change applies to all files that use that
format.
You can only add or delete a file format, you cannot edit one.

853

Delphix User Guide 2016 Delphix

Managing Remote Servers

This feature is an add-on for Masking Engine Standard Edition.
Masking Engine typically executes jobs on a local instance.To execute jobs on a remote server, use this tab to define the server(s).
If you have already defined remote server(s), they appear on the Remote Server tab, in the Remote Server Name column.
Defined remote servers also appear in a dropdown on the Create Job window when you create any new job.
Remote Server Screen

To define a remote server

1. Click Create Remote Server to the upper right, below the tabs. The New Remote Server window appears.
Add Remote Server

2. Enter a name for the remote server in the Remote Server Name field.
3. In the Host Name/IP field, enter the name of the remote server host or the IP address of the remote server.
4. Enter the Port on which the remote client is listening for job requests.
5. Enter a User Name to access the remote server.
6. Enter the Password for the specified User Name.
7. In the Remote Application Home field, enter the path on the remote server to the home directory for the Masking Engine client.
8. Click Submit.

To edit a remote server

854

Delphix User Guide 2016 Delphix

Click the Edit icon to the right of the Remote Server Name.

To delete a remote server

Click the Delete icon to the right of the Remote Server Name.

855

Delphix User Guide 2016 Delphix

To define a remote server

1. Click Create Remote Server to the upper right, below the tabs. The New Remote Server window appears.
Add Remote Server

2. Enter a name for the remote server in the Remote Server Name field.
3. In the Host Name/IP field, enter the name of the remote server host or the IP address of the remote server.
4. Enter the Port on which the remote client is listening for job requests.
5. Enter a User Name to access the remote server.
6. Enter the Password for the specified User Name.
7. In the Remote Application Home field, enter the path on the remote server to the home directory for the Masking Engine client.
8. Click Submit.

856

Delphix User Guide 2016 Delphix

To edit a remote server

Click the Edit icon to the right of the Remote Server Name.

857

Delphix User Guide 2016 Delphix

To delete a remote server

Click the Delete icon to the right of the Remote Server Name.

858

Delphix User Guide 2016 Delphix

Managing Users
The Users Screen
Click the Admin tab at the top and the then the Users tab on the left of the screen to display the list of users defined in the Masking Engine
installation.
Users Tab

Creating and Editing Users

To create a new user
1.

Click Add User at the upper right of the Users screen.

2. You will be prompted for the following information:

First NameThe user's given name.
Last NameThe user's surname.
User NameThe login name for the user.
EmailThe user's e-mail address (mailable from the Masking Engine server for purposes of job completion e-mail messages).
PasswordThe password Masking Engine uses to authenticate the user on the login page. The password must be at least six
characters long, and contain a minimum of one uppercase character, one wild character (!@#$%^&*), and one number.
Confirm PasswordConfirm the password with double-entry to avoid data entry error.
Administrator(Optionally) Select the Administrator check box if you want to give this user Administrator privileges.
(Administrator privileges allow the user to perform all Masking Engine tasks, including creating and editing users in Masking
Engine.)
If you select the Administrator check box, the Roles and Environments fields disappear because Administrator privileges include
all roles and environments.
RoleSelect the role to grant to this user. The choices here depend on the custom roles that you have created. (For information
about creating custom roles, see Managing Roles Settings on page .)
You can assign one role per user name.
EnvironmentEnter as many environments that this user will be able to access
Granting a user access to a given environment does not give them unlimited access to that environment. The user's access is
still limited to their assigned role.
3. When you are finished, click Save.
Add User Window

859

Delphix User Guide 2016 Delphix

To edit a user
1. Click on the User Name in the user list. The User Profile pane appears.
2. Modify the settings as you would for a new user.
3. Click Save.

To delete any user

Click the Delete icon.

860

Delphix User Guide 2016 Delphix

The Users Screen

Click the Admin tab at the top and the then the Users tab on the left of the screen to display the list of users defined in the Masking Engine
installation.
Users Tab

861

Delphix User Guide 2016 Delphix

Creating and Editing Users

To create a new user

1.

Click Add User at the upper right of the Users screen.

2. You will be prompted for the following information:

First NameThe user's given name.
Last NameThe user's surname.
User NameThe login name for the user.
EmailThe user's e-mail address (mailable from the Masking Engine server for purposes of job completion e-mail messages).
PasswordThe password Masking Engine uses to authenticate the user on the login page. The password must be at least six
characters long, and contain a minimum of one uppercase character, one wild character (!@#$%^&*), and one number.
Confirm PasswordConfirm the password with double-entry to avoid data entry error.
Administrator(Optionally) Select the Administrator check box if you want to give this user Administrator privileges.
(Administrator privileges allow the user to perform all Masking Engine tasks, including creating and editing users in Masking
Engine.)
If you select the Administrator check box, the Roles and Environments fields disappear because Administrator privileges include
all roles and environments.
RoleSelect the role to grant to this user. The choices here depend on the custom roles that you have created. (For information
about creating custom roles, see Managing Roles Settings on page .)
You can assign one role per user name.
EnvironmentEnter as many environments that this user will be able to access
Granting a user access to a given environment does not give them unlimited access to that environment. The user's access is
still limited to their assigned role.
3. When you are finished, click Save.
Add User Window

To edit a user

1. Click on the User Name in the user list. The User Profile pane appears.
2. Modify the settings as you would for a new user.
3. Click Save.
To delete any user

Click the Delete icon.

862

Delphix User Guide 2016 Delphix

Utilization Reports
The Utilization Screen
Click the Admin tab at the top and then the Utilization tab on the left to bring up the utilization screen.
Utilization Screen

To generate a new utilization report:

1. Select the Environment you want a utilization report for.
2. Select the Start Date of the report.
3. Select the End Date of the report.
4. Click Create at the top right.

863

Delphix User Guide 2016 Delphix

The Utilization Screen

Click the Admin tab at the top and then the Utilization tab on the left to bring up the utilization screen.
Utilization Screen

To generate a new utilization report:

1. Select the Environment you want a utilization report for.

2. Select the Start Date of the report.
3. Select the End Date of the report.
4. Click Create at the top right.

864

Delphix User Guide 2016 Delphix

Accessing Information About Your Software

The About Screen
To access the about screen first click the Admin tab at the top of the screen and then the About tab on the left of the screen.
From the About screen you can access information such as:
The Masking Engine Version number
The server's Operating System
The Application Server
The installed Database type
The installed Masking library
The installed Java version
The license Expiration Date
The list of all the Licensed Data Sources

865

Delphix User Guide 2016 Delphix

The About Screen

To access the about screen first click the Admin tab at the top of the screen and then the About tab on the left of the screen.
From the About screen you can access information such as:
The Masking Engine Version number
The server's Operating System
The Application Server
The installed Database type
The installed Masking library
The installed Java version
The license Expiration Date
The list of all the Licensed Data Sources

866

Delphix User Guide 2016 Delphix

Security
The following sections describe security actions:
Storing Database Passwords
Authenticating Users
Authorizing Users (Roles)
Configuring a Boot Password
Configuring a Security Banner

Storing Database Passwords

Masking Engine uses encryption and stores all passwords encrypted in the application's repository database.

Authenticating Users
If you choose to use Masking Engine internal authentication, Masking Engine uses encryption and stores passwords for each user encrypted in
the Masking Engine relational repository.
When a user logs in to Masking Engine and enters their username and password, Masking Engine verifies that the user is an active user with
Masking Engine, and then authenticates their password.
Optionally, Masking Engine can integrate with external authentication software (Microsoft Active Directory, CA SiteMinder, or LDAP) to
authenticate users. If you integrate with external authentication software, Masking Engine will validate that the user has rights to access the
application and will log in the user automatically. (No additional Masking Engine password will be required.)

Authorizing Users (Roles)

With the built-in Masking Engine Administrator role, which is similar to a superuser role, the administrator can add roles (Managing Roles
Settings on page ) and assign the roles to users (Managing Users on page ). By creating specific roles and assigning them, the administrator
can control which users are authorized to perform various tasks (privileges).

Configuring a Boot Password

Delphix Engine uses a boot loader to select the

underlying system image to run, along with associated options. Access to the console is controlled through the
virtualization framework, which should be sufficient to secure the Delphix Engine. System users can configure a boot
password if additional compliance regulations require a boot loader password on top of the access control provided
by the virtualization framework.
This topic describes how to configure a boot password on the Delphix Engine. The

Procedure

1. Log into the CLI as a system user.

The boot password is not currently configurable through the browser UI.

2. Switch to the service security context and execute the update command.

delphix> service security

delphix service security> update
3. Set the bootPassword property. The password can be entered on a separate line to avoid echoing the contents.

delphix service security update *> set bootPassword

Enter bootPassword: ******
To clear an existing boot password, run unset bootPassword.

4. Commit the change.

delphix service security update *> commit

867

Delphix User Guide 2016 Delphix

Configuring a Security Banner

This topic describes how the system administrator can configure a security banner on the Delphix Engine. All users will see the security banner
prior to login, over Secure Shell (SSH) and in the browser.
Procedure

1. Log into the command line interface (CLI) as a system user.

Currently, you cannot configure the security banner through the browser user interface (UI).

2. Switch to the service security context and execute the update command.

delphix> service security

delphix service security> update
3. Set the banner property, using quotation marks if you require spaces.

delphix service security update *> set banner="Use is subject to license terms."
The banner is in plain text. HTML or other markup is not supported.

To clear an existing banner, run unset banner.

4. Commit the change.

delphix service security update *> commit

868

Delphix User Guide 2016 Delphix

Configuring a Boot Password

Delphix Engine uses a boot loader to select the
underlying system image to run, along with associated options. Access to the console is controlled through the
virtualization framework, which should be sufficient to secure the Delphix Engine. System users can configure a boot
password if additional compliance regulations require a boot loader password on top of the access control provided
by the virtualization framework.
This topic describes how to configure a boot password on the Delphix Engine. The

Procedure

1. Log into the CLI as a system user.

The boot password is not currently configurable through the browser UI.

2. Switch to the service security context and execute the update command.

delphix> service security

delphix service security> update
3. Set the bootPassword property. The password can be entered on a separate line to avoid echoing the contents.

delphix service security update *> set bootPassword

Enter bootPassword: ******
To clear an existing boot password, run unset bootPassword.

4. Commit the change.

delphix service security update *> commit

869

Delphix User Guide 2016 Delphix

Configuring a Security Banner

This topic describes how the system administrator can configure a security banner on the Delphix Engine. All users will see the security banner
prior to login, over Secure Shell (SSH) and in the browser.
Procedure

1. Log into the command line interface (CLI) as a system user.

Currently, you cannot configure the security banner through the browser user interface (UI).

2. Switch to the service security context and execute the update command.

delphix> service security

delphix service security> update
3. Set the banner property, using quotation marks if you require spaces.

delphix service security update *> set banner="Use is subject to license terms."
The banner is in plain text. HTML or other markup is not supported.

To clear an existing banner, run unset banner.

4. Commit the change.

delphix service security update *> commit

870

Delphix User Guide 2016 Delphix

User Security
The following sections describe security actions:
Storing Database Passwords
Authenticating Users
Authorizing Users (Roles)

Storing Database Passwords

Masking Engine uses encryption and stores all passwords encrypted in the application's repository database.

Authenticating Users
If you choose to use Masking Engine internal authentication, Masking Engine uses encryption and stores passwords for each user encrypted in
the Masking Engine relational repository.
When a user logs in to Masking Engine and enters their username and password, Masking Engine verifies that the user is an active user with
Masking Engine, and then authenticates their password.
Optionally, Masking Engine can integrate with external authentication software (Microsoft Active Directory, CA SiteMinder, or LDAP) to
authenticate users. If you integrate with external authentication software, Masking Engine will validate that the user has rights to access the
application and will log in the user automatically. (No additional Masking Engine password will be required.)

Authorizing Users (Roles)

With the built-in Masking Engine Administrator role, which is similar to a superuser role, the administrator can add roles (Managing Roles
Settings on page ) and assign the roles to users (Managing Users on page ). By creating specific roles and assigning them, the administrator
can control which users are authorized to perform various tasks (privileges).

871

Delphix User Guide 2016 Delphix

Storing Database Passwords

Masking Engine uses encryption and stores all passwords encrypted in the application's repository database.

872

Delphix User Guide 2016 Delphix

Authenticating Users
If you choose to use Masking Engine internal authentication, Masking Engine uses encryption and stores passwords for each user encrypted in
the Masking Engine relational repository.
When a user logs in to Masking Engine and enters their username and password, Masking Engine verifies that the user is an active user with
Masking Engine, and then authenticates their password.
Optionally, Masking Engine can integrate with external authentication software (Microsoft Active Directory, CA SiteMinder, or LDAP) to
authenticate users. If you integrate with external authentication software, Masking Engine will validate that the user has rights to access the
application and will log in the user automatically. (No additional Masking Engine password will be required.)

873

Delphix User Guide 2016 Delphix

Authorizing Users (Roles)

With the built-in Masking Engine Administrator role, which is similar to a superuser role, the administrator can add roles (Managing Roles
Settings on page ) and assign the roles to users (Managing Users on page ). By creating specific roles and assigning them, the administrator
can control which users are authorized to perform various tasks (privileges).

874

Delphix User Guide 2016 Delphix

Configuration
Configuring Masking Engine to use Active Directory
Masking Engine can be configured to use the Active Directory environment to manage the login process. This is accomplished by modifying one
of the Masking Engine property files with the appropriate information to communicate with the Active Directory infrastructure.

Configuration Steps
1. The first step, before you configure Masking Engine to use AD is to create a user in Masking Engine using your AD username. The
Masking Engine username must match exactly your AD username as this is what we will be sending to AD for validation. You will have to
put in a password, but this will not be used once AD is turned on. This user should be an administrator in Masking Engine as this will be
the only valid user until more AD users are created.
2. Once this user is created, bring down Masking Engine.
3. Once Masking Engine is stopped, you need to edit the dm-util.properties file. This is located in the <Masking Engine_home>\conf dire
ctory.
4. Scroll down in the file until you come to the following section:
#LDAP CONFIGURATION.
LDAP_ENABLE=0
LDAP_HOST=10.10.10.31
LDAP_PORT=389
LDAP_BASEDN=DC=tbspune,DC=com
LDAP_FILTER=(&(objectClass=person)(sAMAccountName=?))
LDAP_ANONYMOUS=false
MSAD_DOMAIN=AD
LDAP_KERBEROS_AUTH=true
LDAP_USERID_ATTR=msfwid
5. Set the following entries:
LDAP_ENABLE=1
LDAP_HOST=xxx.xxx.xxx.xxx (your AD host IP address)
LDAP_PORT=389 (your AD host port, this is normally 389)
LDAP_BASEDN=xxx (your AD environment's base DN)
LDAP_KERBEROS_AUTH=false (disable Kerberos if your environment does not use it)
6. Save the file
7. Restart Masking Engine
8. Once Masking Engine comes up you should be able to login to Masking Engine using your AD login and password. If this does not work,
a few things are the possible cause:
a) You did not enter in you username in Masking Engine exactly the way AD expects it. In order to fix this, you will have to bring
Masking Engine down. Edit the dm-util.properties file and change LDAP_ENABLE=0, and save the file. Restart Masking Engine and
login as axistech, correct the AD user. Edit the property file again setting LDAP_ENABLE=1, and save the file. Bring Masking Engine
down, and restart Masking Engine and then try the login again.
b) It is possible that your Active Directory environment is customized, we have run into this before and then you will need to open a
support ticket and have your Active Directory support people available for consultation.

Setting Notes:
Multiple AD domains can be supported by specifying the MSAD_DOMAIN property as a comma separated list of AD domains. For
example: MSAD_DOMAIN=AD,TEST,DEMO
LDAP_USERID_ATTR is only used when LDAP_KERBEROS_AUTH=true

Configuring Log File Locations

Application log files and masking log files and reports are copied to a location determined by a path in a properties file. Over time, these locations
might become full so, at some point, you might want to change the default locations.
You MUST restart your application server after making changes to any properties file for the changes to take effect.

To change the application log file location

1. Open the following properties file:

875

Delphix User Guide 2016 Delphix

/conf/log4j.properties
2. Modify the following key in the file:
log4j.appender.R.File =
For example:
log4j.appender.R.File = C:/Tomcat 6.0/logs/Masking Engine/Masking Engine.log
3. Save and close the properties file.
4. Restart your application server.

To change the masking log file and report locations

1. Open the following properties file:
/conf/dm-util.properties
2. Modify the following keys in the file:
MASKING_LOG_PATH =
REPORT_PATH =
For example:
MASKING_LOG_PATH = D:/logs
REPORT_PATH = D:/reports
3. Save and close the properties file.
4. Restart your application server.

Configuring the Default Port

The default port for application servers is 8080. Follow this procedure if you want to change this default. The example in this procedure is specific
to Tomcat. Substitute values as appropriate for your application server.

To change the default port for application servers:

1. Go to the following location, where <tomcat_home> is the directory with the tomcat installation:
/<tomcat_home>/conf
For example:
Masking Engine/apache_tomcat_6.0.18/conf
2. The conf folder is at the same level as the bin folder.
3. Modify the following line in the server.xml file:
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />
In this example, the default port is changed to 8443.
4. Save and close the file.
5. Restart your application server.

Restarting Masking Engine

In case of a power outage or other failure, you will need to restart your Masking Engine application. The procedure you follow differs depending
on your application server.

To restart your Masking Engine application for Tomcat/JBoss:

1. Go to the following location, where <tomcat_home> is the directory with the tomcat installation:
/<tomcat_home>/bin
For example:
Masking Engine/apache_tomcat_7.0.27/bin
2. Execute the startup.bat file.

To restart your Masking Engine application for WebLogic Server:

876

Delphix User Guide 2016 Delphix

1. Go to the following location, where <bea_server_root> is the location of your application server root folder:
<bea_server_root>/userprojects/domains/Masking Engine_domain/bin
For example:
bea_Masking Engine/apache_tomcat_6.0.18/userprojects/domains/Masking Engine_domain/bin
2. Execute the startupWebLogic.cmd file.

To restart your Masking Engine application for IBM WebSphere:

1. Select Programs > IBM WebSphere > Application Server ... > Profiles > newly created profile > Start the server.
For example, if the default profile created when you installed WebSphere was AppSrv01, your newly created profile might be
AppSrv02:
Programs > IBM WebSphere > Application Server ... > Profiles > AppSrv02 > Start the server.

877

Delphix User Guide 2016 Delphix

Configuring Masking Engine to use Active Directory

Masking Engine can be configured to use the Active Directory environment to manage the login process. This is accomplished by modifying one
of the Masking Engine property files with the appropriate information to communicate with the Active Directory infrastructure.
Configuration Steps

1. The first step, before you configure Masking Engine to use AD is to create a user in Masking Engine using your AD username. The
Masking Engine username must match exactly your AD username as this is what we will be sending to AD for validation. You will have to
put in a password, but this will not be used once AD is turned on. This user should be an administrator in Masking Engine as this will be
the only valid user until more AD users are created.
2. Once this user is created, bring down Masking Engine.
3. Once Masking Engine is stopped, you need to edit the dm-util.properties file. This is located in the <Masking Engine_home>\conf dire
ctory.
4. Scroll down in the file until you come to the following section:
#LDAP CONFIGURATION.
LDAP_ENABLE=0
LDAP_HOST=10.10.10.31
LDAP_PORT=389
LDAP_BASEDN=DC=tbspune,DC=com
LDAP_FILTER=(&(objectClass=person)(sAMAccountName=?))
LDAP_ANONYMOUS=false
MSAD_DOMAIN=AD
LDAP_KERBEROS_AUTH=true
LDAP_USERID_ATTR=msfwid
5. Set the following entries:
LDAP_ENABLE=1
LDAP_HOST=xxx.xxx.xxx.xxx (your AD host IP address)
LDAP_PORT=389 (your AD host port, this is normally 389)
LDAP_BASEDN=xxx (your AD environment's base DN)
LDAP_KERBEROS_AUTH=false (disable Kerberos if your environment does not use it)
6. Save the file
7. Restart Masking Engine
8. Once Masking Engine comes up you should be able to login to Masking Engine using your AD login and password. If this does not work,
a few things are the possible cause:
a) You did not enter in you username in Masking Engine exactly the way AD expects it. In order to fix this, you will have to bring
Masking Engine down. Edit the dm-util.properties file and change LDAP_ENABLE=0, and save the file. Restart Masking Engine and
login as axistech, correct the AD user. Edit the property file again setting LDAP_ENABLE=1, and save the file. Bring Masking Engine
down, and restart Masking Engine and then try the login again.
b) It is possible that your Active Directory environment is customized, we have run into this before and then you will need to open a
support ticket and have your Active Directory support people available for consultation.

Setting Notes:
Multiple AD domains can be supported by specifying the MSAD_DOMAIN property as a comma separated list of AD domains. For
example: MSAD_DOMAIN=AD,TEST,DEMO
LDAP_USERID_ATTR is only used when LDAP_KERBEROS_AUTH=true

878

Delphix User Guide 2016 Delphix

Configuring Log File Locations

Application log files and masking log files and reports are copied to a location determined by a path in a properties file. Over time, these locations
might become full so, at some point, you might want to change the default locations.
You MUST restart your application server after making changes to any properties file for the changes to take effect.
To change the application log file location

1. Open the following properties file:

/conf/log4j.properties
2. Modify the following key in the file:
log4j.appender.R.File =
For example:
log4j.appender.R.File = C:/Tomcat 6.0/logs/Masking Engine/Masking Engine.log
3. Save and close the properties file.
4. Restart your application server.
To change the masking log file and report locations

1. Open the following properties file:

/conf/dm-util.properties
2. Modify the following keys in the file:
MASKING_LOG_PATH =
REPORT_PATH =
For example:
MASKING_LOG_PATH = D:/logs
REPORT_PATH = D:/reports
3. Save and close the properties file.
4. Restart your application server.

879

Delphix User Guide 2016 Delphix

Configuring the Default Port

The default port for application servers is 8080. Follow this procedure if you want to change this default. The example in this procedure is specific
to Tomcat. Substitute values as appropriate for your application server.
To change the default port for application servers:

1. Go to the following location, where <tomcat_home> is the directory with the tomcat installation:
/<tomcat_home>/conf
For example:
Masking Engine/apache_tomcat_6.0.18/conf
2. The conf folder is at the same level as the bin folder.
3. Modify the following line in the server.xml file:
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />
In this example, the default port is changed to 8443.
4. Save and close the file.
5. Restart your application server.

880

Delphix User Guide 2016 Delphix

Restarting Masking Engine

In case of a power outage or other failure, you will need to restart your Masking Engine application. The procedure you follow differs depending
on your application server.
To restart your Masking Engine application for Tomcat/JBoss:

1. Go to the following location, where <tomcat_home> is the directory with the tomcat installation:
/<tomcat_home>/bin
For example:
Masking Engine/apache_tomcat_7.0.27/bin
2. Execute the startup.bat file.
To restart your Masking Engine application for WebLogic Server:

1. Go to the following location, where <bea_server_root> is the location of your application server root folder:
<bea_server_root>/userprojects/domains/Masking Engine_domain/bin
For example:
bea_Masking Engine/apache_tomcat_6.0.18/userprojects/domains/Masking Engine_domain/bin
2. Execute the startupWebLogic.cmd file.
To restart your Masking Engine application for IBM WebSphere:

1. Select Programs > IBM WebSphere > Application Server ... > Profiles > newly created profile > Start the server.
For example, if the default profile created when you installed WebSphere was AppSrv01, your newly created profile might be
AppSrv02:
Programs > IBM WebSphere > Application Server ... > Profiles > AppSrv02 > Start the server.

881

Delphix User Guide 2016 Delphix

Troubleshooting
Memory Usage
Masking Engine masking operations can be memory- and processor-intensive. Therefore, the number of jobs that can run in parallel and the
speed with which they run varies depending on processor and RAM.
Initially, we recommend that you allocate at least 1 GB for the Tomcat application server instance. Other application servers might require more
memory; follow the suggested guidelines for your server. If you encounter memory issues, you might need to increase your memory allocation.
32-bit Java Virtual Machines (JVMs) have a maximum memory setting (1.5 GB) that you cannot exceed. 64-bit JVMs do not have this
restriction.
If you do not allocate enough memory initially, you could have issues if you try to allocate memory as needed. To avoid this problem, we suggest
that you set your Java Xms and Xmx values to the same number. This ensures that all necessary memory is reserved and available for the job at
the beginning. Otherwise, your operating system might attempt to terminate some lower priority processes to free up memory, which could halt
your higher priority processes. We recommend allocating 1 GB per job.
For information on system requirements, see Masking Engine System Requirements.

Stack Traces
If an unhandled exception occurs in code, you might get a stack trace. If this happens, do the following:
1. Restart the server.
2. Ensure that the database is up.
3. If the problem persists, contact Customer Support.

Application Server Down

If the application server is down, the application is also down. The repository might still be available, if the database server is still up. If the server
is down, do the following:
1. Restart the database server, if necessary.
2. Restart the application server.
3. Ensure that both servers are up and running.
4. If the problem persists, contact Customer Support.

Database Server Down

If the database server is down, do the following:
1. Restart the database server.
2. Restart the application server, if necessary.
3. Ensure that both servers are up and running.
4. If the problem persists, contact Customer Support.

Backups and Recovery

Refer to the Masking Engine Disaster Recovery guide.

882

Delphix User Guide 2016 Delphix

Memory Usage
Masking Engine masking operations can be memory- and processor-intensive. Therefore, the number of jobs that can run in parallel and the
speed with which they run varies depending on processor and RAM.
Initially, we recommend that you allocate at least 1 GB for the Tomcat application server instance. Other application servers might require more
memory; follow the suggested guidelines for your server. If you encounter memory issues, you might need to increase your memory allocation.
32-bit Java Virtual Machines (JVMs) have a maximum memory setting (1.5 GB) that you cannot exceed. 64-bit JVMs do not have this
restriction.
If you do not allocate enough memory initially, you could have issues if you try to allocate memory as needed. To avoid this problem, we suggest
that you set your Java Xms and Xmx values to the same number. This ensures that all necessary memory is reserved and available for the job at
the beginning. Otherwise, your operating system might attempt to terminate some lower priority processes to free up memory, which could halt
your higher priority processes. We recommend allocating 1 GB per job.
For information on system requirements, see Masking Engine System Requirements.

883

Delphix User Guide 2016 Delphix

Stack Traces
If an unhandled exception occurs in code, you might get a stack trace. If this happens, do the following:
1. Restart the server.
2. Ensure that the database is up.
3. If the problem persists, contact Customer Support.

884

Delphix User Guide 2016 Delphix

Application Server Down

If the application server is down, the application is also down. The repository might still be available, if the database server is still up. If the server
is down, do the following:
1. Restart the database server, if necessary.
2. Restart the application server.
3. Ensure that both servers are up and running.
4. If the problem persists, contact Customer Support.

885

Delphix User Guide 2016 Delphix

Database Server Down

If the database server is down, do the following:
1. Restart the database server.
2. Restart the application server, if necessary.
3. Ensure that both servers are up and running.
4. If the problem persists, contact Customer Support.

886

Delphix User Guide 2016 Delphix

Backups and Recovery

Refer to the Masking Engine Disaster Recovery guide.

887

Delphix User Guide 2016 Delphix

Release Notes for Delphix Masking 4.7.1

New Features/Enhancements in 4.7.1
Bug Fixes/Improvements in 4.7.1
Known Issues
Notes
DMSuite Repository
Basic Install Instructions

New Features/Enhancements in 4.7.1

General
Added Support for Multiple Active Directory domains.
The email field on the Job Creation screen now defaults to the user's email address instead of blank.
Masking
File Masking - Added support to determine row/record type using multiple fields which is requirement of certain files [Healthcare/Financial
EDI file formats].
File Masking - Added support to custom end of record character to the existing system specific default like LF and CRLF.
DB Masking - Added support for masking columns with not well-formed embedded XML i.e. missing root element
API
Added support to POST method for runJob operation for backward compatibility.
Configuration
The dao properties file is now preconfigured with POSTGRES as default.
The Minor Version #002 assigned to this Major version # 4.7.1

Bug Fixes/Improvements in 4.7.1

General
Fixed the issue with Monitor tab hanging during the execution of large size jobs.
Masking
DB Masking - Fixed SQL statements for DB2 Mainframe version that are different from DB2 LUW [Linux/Unix/Windows] version.
DB Masking - Optimized [2x rows/min throughtput] the In-Place Masking of binary columns with embedded XMLs.
Replaced current Last Name secure lookup [All Caps] with Mixed case version.
DB Masking - Fix the drop index query[resulting in Job failure] for custom identity column which is added when no primary key exists or
logical key supplied for the table to be masked.
File Masking - Fix the data truncation issue when a Header record type is defined for a file format.
API
Service API bug fixes
Appended the DataSource in connector response location
Added the functionality to support Encrypted password for add connector REST API
Configuration
Change the default dm-util.properties reference from incorrect apache-tomcat-7.0.57 to Apache-tomcat-7.0.42 version which is shipped
with DMSuite.
Fix the certification mapplet configuration to reflect correct postgres port information.

Known Issues

888

Delphix User Guide 2016 Delphix

While updating Keys the screen is hung for a few moments.

While trying to establish ODBC connection on LINUX machine, application hangs until the underlying connection responds.
Some older browser version do not show page layout properly, use compatibility mode. Some incorrect Alert messages appear.
User must specify the "Id" column as the first column in a custom SQL query when using a Salesforce connector/ruleset.

Notes
License
License installation is required separately. The license file goes under the dm_license directory under <DMSUITEHOME> (e.g.,
/opt/dmsuite/dm_license or C:/dmsuite/dm_license).
License is valid for installation only for the date specified and cannot be used on a different date.
License is bound to the MAC address provided for installation.
Ports
Port 5432 (Linux & windows) should be available on the machine, if using the bundled PostgreSQL repository.
Port 8282 should be available on the machine, if using default port of apache tomcat.
Port 8443 should be available if tomcat is to be used in https mode.
Extraction of fast-stack [DMSuite-4.7.1-2.tar.bz2] is done in <Current folder>/dmsuite.
For Linux, user should move/copy the extracted subfolder dmsuite and its contents to /opt/ for default paths to work (absolute path should
be /opt/dmsuite).
For Windows, user should move/copy the extract subfolder dmsuite and its contents to C:\ for default paths to work (absolute path should
be C:\dmsuite).
Configuration updates may be needed as per your environment to the /opt/dmsuite/conf/dm-util.properties file or
C:/dmsuite/conf/dm-util.properties (see Step 3 under Basic Install Instructions below for more information):
OUTPUT_FOLDER_PATH property should be:
OUTPUT_FOLDER_PATH=/opt/ or OUTPUT_FOLDER_PATH=C:
APPLICATOR_HOME property should be:
APPLICATOR_HOME=/opt/dmsuite/DMSApplicator/ or APPLICATOR_HOME=C:/dmsuite/DMSApplicator/
Bundled Mappings will be functional if the installation paths are /opt/dmsuite in current minor release

DMSuite Repository
DMSuite includes PostgreSQL as its database repository. To use another database as the DMSuite repository, one must comment/uncomment
the sections in the <DMSUITEHOME>/conf/dmsuite-dao.properties file applicable to the repository type being used (do not forget to comment
out/modify the PostgreSQL section).
The dmsuite-dao.properties for PostgreSQL appears as shipped:

/opt/conf/dmsuite-dao.properties or C:/dmsuite/conf/dmsuite-dao.properties
Entry:
## ------------ DATABASE: PostgreSQL -----------## ---- FIXED ITEMS
database.dialect=org.hibernate.dialect.PostgreSQLDialect
database.driver=org.postgresql.Driver
database.instancename=POSTGRESQL
database.Prefix=
## ---- VARIABLE ITEMS
database.ownername=dmsuite
database.username=dmsuite
database.password=ENC(LRFCy6TouiWKGkE0VL5WJlc41biWuGCf)
database.url=jdbc:postgresql://127.0.0.1:5432/dmsuite

889

Delphix User Guide 2016 Delphix

Basic Install Instructions

1. Extract the fast-stack using the UserID for the owner of the DMSuite server (the UserID used to run the DMSuite server)
a. For Linux, use tar xvjf DMSuite-4.7.1-2.tar.bz2
b.For Windows, use tool such as 7zip
2. Verify that the permissions are right - ensure the owner (UserID) of the DMSuite installation directory has read, write and execute
permisson on all of its contents. e.g.
a. For Linux, pgsql sub-directory contents should have 700 permission for PostgreSQL repository to run properly
3. Edit file paths. DMSuite file paths are defaulted to /opt/. If the user extracts the DMSuite fast-stack to /opt/, continue to Step 4.

Install
If your install directory (<DMSUITEHOME>) is not /opt/, you must edit the following 2 files:
a.

<DMSUITEHOME>/conf/dmsuite-log4j.properties

E.g. :
/opt/conf/dmsuite-log4j.properties or
C:/dmsuite/conf/dmsuite-log4j.properties
Entry:

log4j.appender.R.File=C:/dmsuite/logs/AppLogs/dmsuite.log (or appropriate

local path
b.

<DMSUITEHOME>/conf/dm-util.properties
File :

/opt/conf/dm-util.properties or C:/dmsuite/conf/dm-util.properties

Entry: Change the appropriate paths (e.g., /opt/ to c:/dmsuite) - ~49 changes, so
use replace all
Entry: PROCESS_WAIT_FOR_VALUE=137#143 (default for Linux) change
value to PROCESS_WAIT_FOR_VALUE=1#-1073741510 for windows

4. Create an environment variable DMSUITEHOMEDIR with corresponding local value e.g. DMSUITEHOMEDIR=C:/dmsuite or
DMSUITEHOMEDIR=/opt/dmsuite
5. Execute Start_all.bat or Start_all.sh from the <DMSUITEHOME> directory to startup the bundled PostgreSQL repository and tomcat
server.
Install
If you get an error message indicating "The program can't start because MSVCR120.dll is missing from your computer. Try
reinstalling the program to fix this problem.", download and run vcredist_x64.exe to load the Visual C++ Redistributable
Package for Visual Studio 2013 (see http://www.microsoft.com/en-us/download/details.aspx?id=40784).

6. On a browser navigate to http://<localhost_or_hostname>:8282/dmsuite

For advanced installs/customizations steps refer to https://support.delphix.com/

890

Delphix User Guide 2016 Delphix

_XPP

891

Delphix User Guide 2016 Delphix

Cross-Platform Provisioning of Oracle Data Sources

These topics describe how to use the cross-platform provisioning feature of the Delphix Engine to enable agile data migration of Oracle data
sources.
Cross-Platform Provisioning of Oracle dSources: Overview
Enabling Oracle dSources for Cross-Platform Provisioning
Provisioning an Oracle dSource across Platforms
Creating Scripts for Cross-Platform Provisioning

892

Delphix User Guide 2016 Delphix

Cross-Platform Provisioning of Oracle dSources: Overview

This topic describes basic concepts behind migrating Oracle databases from Unix to Linux platforms. This feature is available in the Delphix Agile
Migration Package. Contact [email protected] for more information about obtaining this package.
Delphix Engine cross-platform provisioning automates existing Oracle best practices to create a Linux Oracle database with the same structure
and data as an existing Unix Oracle database. The process uses the underlying Oracle Transportable Tablespaces and RMAN CONVERT
DATAFILES technologies to efficiently convert Oracle datafiles to the Linux format. In addition, the Delphix

Engine cross-platform
provisioning functionality utilizes algorithms that are unique to the Delphix File System (DxFS) to detect similarities
between the Unix datafiles and converted Linux datafiles, allowing the converted database to be stored in less than
5/100 of the space that would normally be required.

Requirements
The underlying Oracle technology used to transform to Linux imposes several requirements, including:
Encryption can not be used
Tablespace Transport Set must be self-contained
Tablespaces with XML types can not be used before Oracle version 11.2
Advanced queues versions 8 or later
Spatial indexes can not be used before Oracle version 11.2
These requirements are checked by Transformation Validation, as described in Enabling Oracle dSources for Cross-Platform Provisioning. C
reating Scripts for Cross-Platform Provisioning describes how to modify the database to meet these requirements.

Related Links
Enabling Oracle dSources for Cross-Platform Provisioning
Creating Scripts for Cross-Platform Provisioning

893

Delphix User Guide 2016 Delphix

Enabling Oracle dSources for Cross-Platform Provisioning

This topic describes how to enable a Unix Oracle database for conversion to Linux.
Prerequisites
Procedure
Related Links

Prerequisites
A source Unix Oracle database
This can be a dSource or a VDB.
A Unix staging environment
This environment must be the same platform and Oracle version as the source database. See Enabling Validated Sync for Oracle for
information on designating a staging environment.
The default OS user for the staging host must have access to the Oracle installation that will be used as the staging
environment.

A Linux provisioning environment

This environment must be the same Oracle version as the source database. We recommend that this environment have a fast network
link to the Delphix Engine, because it needs to process all blocks in the database when converting a database to Linux. See General
Network and Connectivity Requirements and Network Performance Configuration Options for general information about network
requirements and configuration for the Delphix Engine.

Procedure
1. Log into the Delphix Admin application using delphix_admin credentials
2. In the Manage menu, select Databases > My Databases.
3. Select the Oracle dSource that you want to use for cross-platform provisioning.
4. Click the dSource's Expand icon to open the dSource card, then click the Flip icon on the card to view the back.
5. On the back of the dSource card, click the Linux tab.
6. In the lower right corner of the dSource card, click the green Validate Transformation button.
The validation process will create a temporary VDB on the Unix staging environment, and run SQL commands against it to verify that the
database structure meets the requirements of the underlying Oracle platform conversion technology. Depending on the size of the
dSource, this may take several minutes. See Cross-Platform Provisioning of Oracle dSources: Overview for more information about
the specific database requirements that will checked during this process.
7. If the validation process is successful, green check marks will appear next to each validation requirement, and a gold database icon will
appear next to the dSource name in the Databases panel. If the dSource does not pass the validation process, a red X will appear next
to the requirement. See Creating Scripts for Cross-Platform Provisioning for more information on how to correct these violations of
the cross-platform provisioning requirements.

Related Links
Enabling Validated Sync for Oracle
General Network and Connectivity Requirements
Network Performance Configuration Options
Creating Scripts for Cross-Platform Provisioning

894

Delphix User Guide 2016 Delphix

Provisioning an Oracle dSource across Platforms

This topic describes how to provision a Unix Oracle virtual database (VDB) to a Linux environment.

Prerequisites
A Unix Oracle dSource or VDB that has passed the validation checks for cross-platform provisioning as described in Enabling Oracle
dSources for Cross-Platform Provisioning
A Unix staging environment
This environment must be the same platform and Oracle version as the source database. See Enabling Validated Sync for Oracle for
information on designating a staging environment.
A Linux provisioning environment
This environment must be the same Oracle version as the source database. We recommend that this environment have a fast network
link to the Delphix Engine, because it needs to process all blocks in the database when converting a database to Linux. See Network
and Connectivity Requirements and Network Performance Configuration Options for general information about network requirements
and configuration for the Delphix Engine.

Procedure
1. Log into the Delphix Admin application using delphix_admin credentials.
2. In the Manage menu, select Databases > My Databases if the Databases panel is not visible.
3. In the Databases panel, select an Oracle dSource that has passed the validation checks for cross-platform provisioning.
Eligible dSources will have a gold database icon next to the dSource name, as shown in the dSource Icon Reference.
4. Select a provision point for the virtual database.
See Provisioning an Oracle VDB for information on using Snapshots, LogSync, and SCN Numbers as provision points.
5. Click Transform to Linux.
6. In the Linux Transformation VDB wizard, select a Linux environment where you want to provision the VDB, and follow the steps for
configuring the new VDB as described in Provisioning an Oracle VDB.
When the Linux transformation process completes, a VDB will be created with the transformed database running on Linux. You should be
aware that the transformation process can be time and resource intensive, because Oracle must read and convert all blocks in the
database

Related Links
Enabling Oracle dSources for Cross-Platform Provisioning
Enabling Oracle Pre-Provisioning
Network and Connectivity Requirements
Network Performance Configuration Options
dSource Icon Reference
Provisioning an Oracle VDB

895

Delphix User Guide 2016 Delphix

Creating Scripts for Cross-Platform Provisioning

This topic describes the process for using scripts to correct violations that occur when a dSource does not pass validation checks for
cross-platform provisioning.
As described in Enabling Oracle dSources for Cross-Platform Provisioning, a dSource may not pass all the validation checks that are
necessary for it to be eligible for cross-platform provisioning. Failure to pass these checks is usually the result of an issue with objects in the
database itself. For example, there cannot be any user objects in system tablespaces, and other requirements as described in Cross-Platform
Provisioning of Oracle dSources: Overview. These validation violations must be corrected by modifying the database objects, which can be
accomplished by uploading a Transformation Script. This script is a series of SQL commands that will be run against the temporary virtual
database (VDB) before the validation process executes. For example, the Transformation Script might move user objects from the system
tablespace to a user tablespace. The Delphix Customer Services group can help you with the initial creation of these scripts.
Procedure
Related Links

Procedure
1. Log into the Delphix Admin application using delphix_admin credentials.
2. If the Databases panel is not visible, select Manage > Databases > My Databases.
3. In the Databases panel, select the dSource that did not pass the cross-platform provisioning validation checks.
4. Click the Expand icon for the dSource to view its card.
5. Click the Flip icon to view the back of the card.
6. Click the Linux tab.
7. Click the Upload Transformation Script icon in the lower-right corner of the card.
8. Click Choose a File to Upload and navigate to the location of the script, then click Choose.
The file will automatically upload when you click Choose.
The Transformation Script must be an SQL or plain text file otherwise the upload will fail.

9. Click the Validate Transformation icon to execute the script against the temporary virtual database.

Related Links
Enabling Oracle dSources for Cross-Platform Provisioning

896

Delphix User Guide 2016 Delphix

_Unstructured Files

897

Delphix User Guide 2016 Delphix

Unstructured Files: Getting Started

This topic describes basic concepts for creating and managing unstructured files sources.
The term unstructured files" refers to data stored in a filesystem that is NOT usually accessed by a DBMS or similar software. Unstructured files
can consist of anything from a simple directory to the root of a complex application like Oracle Enterprise Business Suite.

Like with other data types, you can configure a dSource to sync periodically with a set of unstructured files external
to the Delphix Engine. The dSource is a copy of these physical files stored on the Delphix Engine. On Unix
platforms, dSources are created and periodically synced by an implementation of the rsync utility. On Windows,
files are synced using the robocopy utility, which is distributed with Windows.
From dSources, you can provision vFiles, which are virtual copies of data that are fully functional read write copies
of the original files source.You can mount vFiles across one target environment or many.

898

Delphix User Guide 2016 Delphix

Unstructured Files Environment Requirements

This section describes the environment requirements that must be satisfied before you can link, virtualize, or provision unstructured files. These
requirements include expectations for operating system and network configuration.
Unstructured Files on Unix Environments
Requirements for Unix Environments
Network and Connectivity Requirements for Unix Environments
Sudo Privilege Requirements and File Configurations
Managing Unix Environments
Adding a Unix Environment
Managing Unix Environment Users
Unstructured Files on Windows Environments
Requirements for Windows Environments
Network and Connectivity Requirements for Windows Environments
Managing Windows Environments
Adding a Windows Environment
Managing Windows Environment Users
Options for Linking Unstructured Files on Windows Environments
Network and Connectivity Requirements for Windows Environment

899

Delphix User Guide 2016 Delphix

Unstructured Files on Unix Environments

These topics describe requirements for Unix source and target environments hosting unstructured files.
Requirements for Unix Environments
Network and Connectivity Requirements for Unix Environments
Sudo Privilege Requirements and File Configurations
Managing Unix Environments
Adding a Unix Environment
Managing Unix Environment Users

900

Delphix User Guide 2016 Delphix

Requirements for Unix Environments

This topic outlines the supported operating systems (OSs) for use on Unix source and target environments.

Supported Operating Systems

Operating System

Version

Processor Family

Solaris

9, 10, 11

SPARC

Solaris

10, 11

x86_64

Red Hat Enterprise Linux

4.7, 4.8, 4.9

5.3 - 5.10
6.0 - 6.5

x86, x86_64

Oracle Enterprise Linux

5.3 - 5.10
6.0 - 6.5

x86_64

Novell SUSE Linux Enterprise Server

10, 10SP1, 10SP2, 10SP3

11, 11SP1

x86_64

AIX

5.3, 6.1, 7.1

Power

HP-UX

11i v2 (11.23)

IA64

11i v3 (11.31)
Delphix supports all 64-bit OS environments for source and target, though 64-bit Linux environments also require that a 32-bit version of glibc is
installed.
Required HP-UX patch for Target Servers

PHNE_37851 - resolves a known bug in HP-UX NFS client prior to HP-UX 11.31.
Additional Source Environment Requirements

There must be an operating system user (delphix_os) with these privileges:

Ability to login to the source environment via SSH
There must be a directory on the source environment where you can install the Delphix Engine Toolkit for example, /var/opt/delph
ix/toolkit.
The delphix_os user must own the directory
The directory must have permissions -rwxrwx--- (0770), but you can also use more permissive settings
The delphix_os user must have read and execute permissions on each directory in the path leading to the toolkit directory. For
example, when the toolkit is stored in /var/opt/delphix/toolkit, the permissions on /var, /var/opt, and /var/opt/d
elphix should allow read and execute for "others," such as -rwxr-xr-x.
The directory should have 1.5GB of available storage: 400MB for the toolkit and 400MB for the set of logs generated by each
client that runs out of the toolkit
On a Solaris host, gtar must be installed. Delphix uses gtar to handle long file names when extracting the toolkit files into the toolkit
directory on a Solaris host. The gtar binary should be installed in one of the following directories:
/bin:/usr
/bin:/sbin:/usr
/sbin:/usr/contrib
/bin:/usr/sf
/bin:/opt/sfw
/bin:/opt/csw/bin
The Delphix Engine must be able to initiate an SSH connection to the source environment
Additional Target Environment Requirements

There must be an operating system user (delphix_os) with these privileges:

Ability to login to the target environment via SSH

The following permissions are usually granted via sudo authorization of the commands.
See Sudo Privilege Requirements for further explanation of the commands and for examples of the
/etc/sudoers file on different operating systems.

901

Delphix User Guide 2016 Delphix

Permission to run mount, unmount, mkdir, and rmdir as a super-user

If the target host is an AIX system, permission to run the

nfso command

as a super-user

There must be a directory on the source environment where you can install the Delphix Engine
Toolkit for example, /var/opt/delphix/toolkit .
The delphix_os user must own the directory
The directory must have permissions -rwxrwx--- (0770), but you can also use more permissive settings
The delphix_os user must have read and execute permissions on each directory in the path leading to the toolkit directory. For
example, when the toolkit is stored in /var/opt/delphix/toolkit, the permissions on /var, /var/opt, and /var/opt/d
elphix should allow read and execute for "others," such as -rwxr-xr-x.
The directory should have a total of at least 800MB of storage, plus 1MB of storage per vFile that will be provisioned to the target
On a Solaris host, gtar must be installed. Delphix uses gtar to handle long file names when extracting the toolkit files into the toolkit
directory on a Solaris host. The gtar binary should be installed in one of the following directories:
/bin:/usr
/bin:/sbin:/usr
/sbin:/usr/contrib
/bin:/usr/sf
/bin:/opt/sfw
/bin:/opt/csw/bin

There must be an empty directory (/delphix) that will be used as a container for the mount points that are
created when provisioning a vFile to the target environment. The group associated with the directory must be
the primary group of the delphix_os user. Group permissions for the directory should allow read, write, and
execute by members of the group.
The Delphix Engine must be able to initiate an SSH connection to the target environment
NFS client services must be running on the target environment

902

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for Unix Environments

This topic outlines the network and connectivity requirements for the Delphix Engine and Unix source and target environments.
Port Allocations Specific to Unstructured Files
Inbound to the Delphix Engine Port Allocation
Outbound from a Source Environment Port Allocation
Inbound to a Source Environment Port Allocation
Outbound from a Target Environment Port Allocation
Inbound to a Target Environment Port Allocation
General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration
Port Allocations Specific to Unstructured Files

The Delphix Engine makes use of the following network ports for unstructured files dSources and vFiles:
Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

873

Rsync connections used for communication to rsyncd during SnapSync

TCP/UDP

111

Remote Procedure Call (RPC) port mapper used for NFS mounts
Note: RPC calls in NFS are used to establish additional ports, in the high range 32768-65535, for supporting services.
Some firewalls interpret RPC traffic and open these ports automatically. Some do not.

TCP

1110

NFS Server daemon status and NFS server daemon keep-alive (client info)

TCP/UDP

2049

NFS Server daemon from vFiles to the Delphix Engine

TCP

4045

NFS lock daemon/manager

UDP

33434 33464

Traceroute from source and target database servers to the Delphix Engine (optional)

UDP/TCP

32768 65535

NFS mountd and status services, which run on a random high port. Necessary when a firewall does not dynamically
open ports.

Outbound from a Source Environment Port Allocation

Protocol

Port Numbers

Use

TCP

873

Rsync connections used during SnapSync

TCP

xxxx

DSP connections used for monitoring and script management during SnapSync. Typically DSP runs on port 8415.

Inbound to a Source Environment Port Allocation

Protocol

Port Numbers

Use

TCP

22

SSH connections to source environment

Outbound from a Target Environment Port Allocation

Protocol

Port Numbers

Use

TCP

873

Rsync connections used during V2P

TCP

xxxx

DSP connections used for monitoring and script management. Typically DSP runs on port 8415.

Inbound to a Target Environment Port Allocation

903

Delphix User Guide 2016 Delphix

Protocol

Port Numbers

Use

TCP

22

SSH connections to target environment

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:

904

Delphix User Guide 2016 Delphix

Disallowed sshd Configuration Entries

ClientAliveInterval
ClientAliveCountMax

905

Delphix User Guide 2016 Delphix

Sudo Privilege Requirements and File Configurations

This topic describes sudo file privilege configurations necessary for interacting with the Delphix Engine.
Sudo Privilege Rationale

Privilege

Sources

Targets

mkdir/rmdir

Not
Optional
Required

Rationale
Delphix dynamically makes and removes directories under the provisioning directory during vFiles
operations. This privilege is optional, provided the provisioning directory permissions allow the delphi
x_os user to make and remove directories.

mount/umount Not
Required Delphix dynamically mounts and unmounts directories under the provisioning directory during vFiles
Required
operations. This privilege is required because mount and umount are typically reserved for a
super-user.
nfso (AIX only)

Not
Required Delphix monitors NFS read and write sizes on an AIX target host. It uses the nfso command to
Required
query the sizes in order to optimize NFS performance for vFiles running on the target host. Only a
super-user can issue the nfso command.

Configuring sudo Access on Solaris SPARC Target Environments

On a Solaris target, sudo access to mount, umount, mkdir, and rmdir is required. In this customer example, super-user privilege is
restricted to the virtual dataset mount directory

/delphix.

Example: Solaris /etc/sudoers entries for a Delphix Target

User_Alias DELPHIX_USER=delphix_os
Cmnd_Alias DELPHIX_CMDS= \
/usr/sbin/mount
/delphix/*, \
/usr/sbin/mount
100.245.235.12\:* /delphix/*, \
/usr/sbin/mount -o* 100.245.235.12\:* /delphix/*, \
/usr/sbin/umount
/delphix/*, \
/usr/sbin/umount -f /delphix/*, \
/usr/bin/mkdir
/delphix/*, \
/usr/bin/mkdir -p
/delphix/*, \
/usr/bin/rmdir
/delphix/*
DELPHIX_USER ALL=(ALL) NOPASSWD: DELPHIX_CMDS
Configuring sudo Access on Linux for Target Environments

On a Linux target, sudo access to mount, umount, mkdir, and rmdir is required. In this customer example, super-user privilege is restricted to
the virtual database mount directory /delphix.

Example: Linux /etc/sudoers file for a Delphix Target

Defaults:delphix_os !requiretty
Cmnd_Alias DELPHIX_ADMIN_CMDS= \
/bin/mount
/delphix/*,
/bin/mount
*
/delphix/*,
/bin/umount
/delphix/*,
/bin/umount *
/delphix/*,
/bin/mkdir -p -m 755 /delphix/*,
/bin/mkdir -p
/delphix/*,
/bin/mkdir
/delphix/*,
/bin/rmdir
/delphix/*

\
\
\
\
\
\
\

Host_Alias DELPHIX_HOSTS=delphix001, delphix002

delphix_os DELPHIX_HOSTS=NOPASSWD:DELPHIX_ADMIN_CMDS

906

Delphix User Guide 2016 Delphix

Configuring sudo Access on AIX for Target Environments

In addition to sudo access to the mount, umount, mkdir, and rmdir commands on AIX target hosts, Delphix also
requires sudo access to nfso. This is required on target hosts for Delphix to monitor the NFS read / write sizes
configured on the AIX system. Super-user access level is needed to run the nfso command.
Example: AIX /etc/sudoers File for a Delphix Target
Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD: \
/bin/mount, \
/bin/umount, \
/bin/mkdir, \
/bin/rmdir, \
/usr/sbin/nfso
Configuring sudo Access on HP-UX for Target Environments

On the HP-UX target, as with other operating systems, sudo access to mount, umount, mkdir, and rmdir is required.

Example: HP-UX /etc/sudoers file for a Delphix Target

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD:/sbin/mount, /sbin/umount, /bin/mkdir, /bin/rmdir

Considerations for sudo access and account locking

The Delphix Engine tests its ability to run the mount command using sudo on the target environment by issuing the sudo mount com
mand with no arguments. Many of the examples shown in this topic do not allow that, and in those cases the attempt will be blocked. In
most situations, this does not cause a problem.
However, some users configure the security on the target environments to monitor sudo failures and lock out the offending account
after some threshold. In those situations, the delphix_os account can become locked. One work-around for this situation is to increase
the threshold for locking out the user account. Another option is to modify /etc/sudoers to permit the delphix_os user to run mkdir,
rmdir, and mount commands without parameters.

907

Delphix User Guide 2016 Delphix

Managing Unix Environments

These topics describe special tasks and concepts for working with Unix environments containing unstructured files.
Adding a Unix Environment
Managing Unix Environment Users

908

Delphix User Guide 2016 Delphix

Adding a Unix Environment

This topic describes how to add a new Unix environment.
Prerequisites

See the topic Requirements for Unix Environments.

Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Environments.
4. Click the Plus icon next to Environments.
5. In the Add Environment dialog, select Unix/Linux.
6. Select Standalone Host.
7. Enter the Host IP address.
8. Enter an optional Name for the environment.
9. Enter the SSH port. The

default value is 22.

10. Enter a Username for the environment.

11. Select a Login Type.
For Password, enter the password associated with the user in Step 10.
Using Public Key Authentication
If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file
does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as explained
in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

12. For Password Login, click Verify Credentials to test the username and password.
13. Enter a Toolkit Path.
The toolkit directory stores scripts used for Delphix Engine operations. It should have a persistent working directory rather than a
temporary one.
14. Click OK.
Post-Requisites

After you create the environment, you can view information about it by doing the following:
1. Click Manage.
2. Select Environments.
3. Select the environment name.
Related Links

Requirements for Unix Environments

909

Delphix User Guide 2016 Delphix

Managing Unix Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure
Prerequisites

Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.
Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

910

Delphix User Guide 2016 Delphix

Unstructured Files on Windows Environments

These topics describe requirements for Windows source and target environments hosting unstructured files.
Requirements for Windows Environments
Network and Connectivity Requirements for Windows Environments
Managing Windows Environments
Adding a Windows Environment
Managing Windows Environment Users
Options for Linking Unstructured Files on Windows Environments
Network and Connectivity Requirements for Windows Environment

911

Delphix User Guide 2016 Delphix

Requirements for Windows Environments

This topic outlines the supported operating systems (OSs) for use on Windows source and target environments.

Supported Operating Systems

Windows Server 2003 SP2, 2003 R2
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012, 2012 R2
Requires 64-Bit Windows
Delphix must install the Delphix Connector on all Windows hosts that Delphix will directly communicate with. This means all target
hosts, and source or staging hosts. The Delphix Connector only supports 64-bit versions of Windows.
See Options for Linking Unstructured Files on Windows Environments for more information about source vs. staging hosts.

Additional Source or Staging Environment Requirements

The Delphix Connector must be installed on the source or staging environment. You must have used the Delphix Connector to register
this environment with the Delphix Engine.
The robocopy utility must be installed on the source or staging Windows environment.
robocopy is installed by default on Windows Server 2008, Windows Vista, Windows 7, and Windows 8. For other versions of Windows,
it is available by downloading a resource kit from Microsoft.
If using a staging environment, the source's files must be made available and readable to the environment user from the staging
environment via a UNC path. For example, use Windows Sharing.

Additional Target Environment Requirements

The Delphix Connector must be installed on the target environment. You must have used the Delphix Connector to register this
environment with the Delphix Engine.

Procedure for Adding and Installing the Delphix Connector for Windows
All Windows environments that will communicate with Delphix must have the Delphix Connector installed. The instructions in this topic cover
downloading Delphix Connector, running the Delphix Connector installer on the Windows machine, and then registering the environment with the
Delphix Engine.

Procedure
Downloading the Delphix Connector

Delphix Connector software supplied by Delphix Engine versions before 4.2.4.0 required that the Windows machine had SQL Server
installed. If you are using a Windows machine that does not have SQL Server installed, you must download the Delphix Connector from
a Delphix Engine of version 4.2.4.0 or higher.
The Delphix Connector can be downloaded through the Delphix Engine Interface, or by directly accessing its URL.
Using the Delphix Engine Interface

A Flash player must be available on the Windows host in order to download Delphix Connector using the Delphix GUI.

1. From the Windows machine that you want to use, start a browser session and connect to the Delphix Engine GUI using the
delphix_admin login.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the Add Environment dialog, select Windows in the operating system menu.
6. Select Target.
7. Select Standalone.

912

Delphix User Guide 2016 Delphix

7.
8. Click the download link for the Delphix Connector Installer.
The Delphix Connector will download to your local machine.
Direct Download

1. You can download the Delphix Connector directly by navigating to this URL: http://<name of your Delphix
Engine>/connector/DelphixConnectorInstaller.msi
Installing Delphix Connector

On the Windows machine that you want to want to use, run the Delphix Connector installer. Click Next to advance through each of the installation
wizard screens.
The installer will only run on 64-bit Windows systems. 32-bit systems are not supported.

1. For Connector Configuration, make sure there is no firewall in your environment blocking traffic to the port on the Windows
environment that the Delphix Connector service will listen to.
2. For Select Installation Folder, either accept the default folder, or click Browse to select another.
3. Click Next on the installer final Confirm Installation dialog to complete the installation process and then Close to exit the Delphix
Connector Install Program.
4. Note: At this point, you can close the Delphix GUI dialog by clicking Cancel.
Registering Environment With Delphix Engine

1. On the Windows machine, navigate to the folder where the Delphix Connector was installed for example, C:\Program
Files\Delphix\DelphixConnector.
2. Run this batch script as Administrator: <Delphix Connector installation
folder>\Delphix\DelphixConnector\connector\addhostgui.cmd.
3. When the Add Windows Environment Wizard launches, provide the Host IP Address, Delphix Engine IP Address, your login
credentials, and the environment user on the Windows host.
4. After providing this information, click Submit.
5. Click Yes to confirm the environment addition request.
6. In the Delphix Engine interface, you will see a new icon for the environment, and two jobs running in the Delphix Admin Job History,
one to Create and Discover an environment, and another to Create an environment. When the jobs are complete, click on the icon for
the new environment, and you will see the details for the environment.

Post-Requisites
On the Windows machine, in the Windows Start Menu, go to Services > Extended Services, and make sure that the Delphix
Connector service has a Status of Started, and that the Startup Type is Automatic.

913

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for Windows Environments

This topic outlines the network and connectivity requirements for the Delphix Engine and Windows source and target environments.
Port Allocations Specific to Unstructured Files
Outbound from the Delphix Engine
Inbound to the Delphix Engine
Outbound from a Source, Staging, or Target Environment
Inbound to a Source, Staging, or Target Environment
General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration
Port Allocations Specific to Unstructured Files

The Delphix Engine makes use of the following network ports for unstructured files dSources and VDBs:
Outbound from the Delphix Engine

Protocol

Port
Numbers

Use

TCP

xxxx

Delphix Connector connections to source and target environments. Typically the Delphix Connector runs on port
9100.

Inbound to the Delphix Engine

Protocol

Port Number

Use

TCP

3260

iSCSI target daemon for connections from iSCSI initiators on the target environments to the Delphix Engine

Outbound from a Source, Staging, or Target Environment

Protocol

Port Numbers

Use

TCP

80

The Delphix Connector registers environments over HTTP

TCP

xxxx

DSP connections used for monitoring and script management. Typically DSP runs on port 8415.

Inbound to a Source, Staging, or Target Environment

Protocol

Port Numbers

Use

TCP

xxxx

Delphix Connector connections to source environments. Typically the Delphix Connector runs on port 9100.

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

914

Delphix User Guide 2016 Delphix

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

915

Delphix User Guide 2016 Delphix

Managing Windows Environments

These topics describe special tasks and concepts for working with Windows environments containing unstructured files.
Adding a Windows Environment
Managing Windows Environment Users

916

Delphix User Guide 2016 Delphix

Adding a Windows Environment

This topic describes how to add a Windows environment to the Delphix Engine for use with unstructured files.

All Windows source and target environments containing unstructured files must have the Delphix Connector
installed to enable communication between the environment and the Delphix Engine. The instructions in this topic
cover initiating the Add Target process in the Delphix Engine interface, running the Delphix Connector installer on
the environment, and verifying that the environment has been added in the Delphix Engine interface.
Prerequisites

Make sure your source and target environment meets the requirements described in Requirements for Windows Environments.
Procedure

1. From the machine that you want to use, login to the Delphix Admin application.
2. Click Manage.
3. Select Environments.
4. Next to Environments, click the green Plus icon.
5. In the operating system menu, select Windows.
6. Select Target.
7. Select Standalone.
8. Click the download link for the Delphix Connector Installer.
The Delphix Connector will download to your local machine.
9. On the Windows machine that you want to use, run the Delphix Connector installer. Click Next to advance through each of the installation
wizard screens.
The installer will only run on 64-bit Windows systems. 32-bit systems are not supported.

a. For Connector Configuration, make sure there is no firewall in your environment blocking traffic to the port on the target
environment to which the Delphix Connector service will listen.
b. For Select Installation Folder, either accept the default folder or click Browse to select another.
c. Click Close to complete the installation process.
d. Run this batch script as Administrator: <Delphix Connector installation
folder>\Delphix\DelphixConnector\connector\addhostgui.cmd.
When the Add Windows Target Environment Wizard launches, enter the Target Host IP Address, Delphix Engine IP
Address, your login credentials, and the environment user on the Windows host.
e. After providing this information, click Submit.
f. Click Yes to confirm the target environment addition request.
10. In the Delphix Engine interface, you will see a new icon for the environment and two jobs running in the Delphix Admin Job History,
one to Create and Discover an environment, and another to Create an environment. When the jobs are complete, click the icon for the
new environment, and you will see the details for the environment.
Post-Requisites

1. On the Windows environment, in the Windows Start Menu, select Services.

2. Select Extended Services.
3. Make sure that the Delphix Connector service has a Status of Started.
4. Make sure that the Startup Type is Automatic.
Related Links

Requirements for Windows Environments

917

Delphix User Guide 2016 Delphix

Managing Windows Environment Users

This topic describes how to manage the users associated with an environment. For information on providing Delphix users with privileges for
groups and database objects, see the topics under Managing Users and Managing Policies.
Prerequisites
Procedure
Prerequisites

Users that you add to an environment must meet the requirements for that environment as described in the platform-specific Requirements topics.
Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Environments.
4. Click the name of an environment to open the environment information screen.
5. Under Basic Information, click the green Plus icon to add a user.
6. Enter the Username and Password for the OS user in that environment.

Using Public Key Encryption

If you want to use public key encryption for logging into your environment:
a. Select Public Key for the Login Type.
b. Click View Public Key.
c. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If
this file does not exist, you will need to create it.
i. Run chmod 600 authorized_keys to enable read and write privileges for your user.
ii. Run chmod 755 ~ to make your home directory writable only by your user.
The public key needs to be added only once per user and per environment.
You can also add public key authentication to an environment user's profile by using the command line interface, as
explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users.

7. Click the Check icon to save the new user.

8. To change the primary user for this environment, click the Pencil icon next to Environment Users.
9. To delete a user, click the Trash icon next to their username.

918

Delphix User Guide 2016 Delphix

Options for Linking Unstructured Files on Windows Environments

There are two techniques for linking a new dSource from files on a Windows source.

Direct Communication With The Source Environment

The simplest technique is to have the Delphix Engine communicate directly with the source environment. This requires installing the Delphix
Connector on the source machine. When linking, specify a local path on the source machine, such as C:\Files\MyData.

Using a Staging Environment

In some cases, it is not possible or desirable to install the Delphix Connector on the source environment. In those cases, you can install the
Delphix Connector on a "staging environment." This is another Windows machine that will act as an intermediary between the Delphix Engine and
the source environment. Files on the source must be accessible by the environment user from the staging environment via a UNC path. For
example, use Windows Sharing on the source machine. When linking, specify the UNC path to the files on the source for example,
\\MySource\MyData\

919

Delphix User Guide 2016 Delphix

Network and Connectivity Requirements for Windows Environment

This topic outlines the network and connectivity requirements for the Delphix Engine and Windows source and target environments.
Port Allocations Specific to Unstructured Files
Outbound from the Delphix Engine
Inbound to the Delphix Engine
Outbound from a Source, Staging, or Target Environment
Inbound to a Source, Staging, or Target Environment
General Outbound from the Delphix Engine Port Allocation
General Inbound to the Delphix Engine Port Allocation
Firewalls and Intrusion Detection Systems (IDS)
SSHD Configuration

Port Allocations Specific to Unstructured Files

The Delphix Engine makes use of the following network ports for unstructured files dSources and VDBs:
Outbound from the Delphix Engine

Protocol

Port
Numbers

Use

TCP

xxxx

Delphix Connector connections to source and target environments. Typically, the Delphix Connector runs on port
9100.

Inbound to the Delphix Engine

Protocol

Port Number

Use

TCP

3260

iSCSI target daemon for connections from iSCSI initiators on the target environments to the Delphix Engine

Outbound from a Source, Staging, or Target Environment

Protocol

Port Numbers

Use

TCP

80

The Delphix Connector registers environments over HTTP

TCP

xxxx

DSP connections used for monitoring and script management. Typically, DSP runs on port 8415.

Inbound to a Source, Staging, or Target Environment

Protocol

Port Numbers

Use

TCP

xxxx

Delphix Connector connections to source environments. Typically, the Delphix Connector runs on port 9100.

General Outbound from the Delphix Engine Port Allocation

Protocol

Port
Numbers

Use

TCP

25

Connection to a local SMTP server for sending email

TCP/UDP

53

Connections to local DNS servers

UDP

123

Connection to an NTP server

UDP

162

Sending SNMP TRAP messages to an SNMP Manager

HTTPS

443

SSL connections from the Delphix Engine to the Delphix Support upload server

TCP/UDP

636

Secure connections to an LDAP server

920

Delphix User Guide 2016 Delphix

TCP

8415

Connections to a Delphix replication target. See Configuring Replication.

TCP

50001

Connections to source and target environments for network performance tests via the Delphix command line interface
(CLI). See Network Performance Tool.

General Inbound to the Delphix Engine Port Allocation

Protocol

Port
Number

Use

TCP

22

SSH connections to the Delphix Engine

TCP

80

HTTP connections to the Delphix GUI

UDP

161

Messages from an SNMP Manager to the Delphix Engine

TCP

443

HTTPS connections to the Delphix GUI

TCP

8415

Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for
Oracle, V2P, and the Delphix Connector.

TCP

50001

Connections from source and target environments for network performance tests via the Delphix CLI. See Network
Performance Tool.

TCP/UDP

32768 65535

Required for NFS mountd and status services from target environment only if the firewall between Delphix and the
target environment does not dynamically open ports.
Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens
ports, this port range is not explicitly required.

Firewalls and Intrusion Detection Systems (IDS)

Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can
add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and
the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be
configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed
above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the
anticipated high volumes of data transfer between dSources and the Delphix Engine.

SSHD Configuration
Both source and target Unix environments are required to have sshd running and configured such that the Delphix Engine can connect over ssh.
The Delphix Engine expects to maintain long-running, highly performant ssh connections with remote Unix environments. The following sshd con
figuration entries can interfere with these ssh connections and are therefore disallowed:
Disallowed sshd Configuration Entries
ClientAliveInterval
ClientAliveCountMax

921

Delphix User Guide 2016 Delphix

Linking Unstructured Files

This topic describes the process of linking to a set of unstructured files and creating a dSource.

Prerequisites
The source environment must meet the requirements outlined in Unstructured Files Environment Requirements.
The Delphix Engine must have access to an environment user. This user should should have read permissions on all files to be cloned.
Unstructured Files on Cluster Environments
Unstructured files cannot be linked from, or provisioned to, any form of cluster environment, such as an Oracle RAC environment. To
link or provision unstructured files from a host that is part of a cluster, add the host as a standalone environment. Then, link from or
provision to this standalone host.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Select the environment containing the unstructured files you want to link.
If you have not already added the environment, see the Managing Unix Environments and Managing Windows Environments topics
for more information about adding environments.
5. Click the Environment Details tab.
6. If the environment user described in the Prerequisites section is not already added to the Delphix Engine, add the user.
See the Managing Unix Environments and Managing Windows Environments topics for more information about adding environment
users.
7. Click the Databases tab.
8. Click the Plus icon next to Add Dataset Home.
Adding the files as a dataset home will register the type and location of the files with the Delphix Engine.
9. Select Unstructured Files as the Dataset Home Type.
10. Enter a Name to help identify the files.
11. Enter the Path to the root directory of the files. On Windows, this may be a local path or an UNC name.
12. Click the Check icon to save your dataset home. Scroll down the list of dataset homes to view and edit this dataset home if necessary.
13. Click Manage.
14. Select Databases.
15. Select Add

dSource.
Alternatively, on the Environment Management screen, you can click Link next to a dataset name to start
the dSource creation process.

16. In the Add dSource wizard, select the files source.

17. Select the Environment User outlined in the Prerequisites section.
18. Click Advanced.
19. Enter Paths to Exclude.
These paths are relative to the root path of the dataset home path and will not be linked by the Delphix Engine. This feature is most
commonly used to exclude directories containing log files. Wildcard (*) pattern matching is supported to exclude all the contents of a
directory, without excluding the directory itself. For example, specifying /dir/* will exclude all contents of /dir but still link /dir as an
empty directory.

Retroactive Edits to Exclude Paths on Windows

After creating a dSource, you can edit the set of Paths to Exclude from syncing at any time on the back of the dSource card.
For Unix environments, retroactively adding a path to exclude will result in the next SnapSync deleting the newly-excluded files.
However, for Windows environments, retroactively adding a path to exclude will result in the next SnapSync ignoring
newly-excluded files. Stale versions of these files will still exist in all future snapshots.

20. If you are linking files from a Unix environment, enter Paths of Symlinks to Follow.

922

Delphix User Guide 2016 Delphix

20.
These paths are relative to the root path of the dataset home path and will be followed to gather additional files to copy.
Paths of Symlinks to Follow - Caveats
This feature can only be used to follow symlinks to directories. Symlinks to files will be ignored.
This feature is not available for files on Windows environments

21. Click Next.

22. Enter a dSource Name.
23. Select a Database Group for the dSource.
24. Click Next.
Adding a dSource to a database group enables you to set Delphix Domain user permissions for that dSource's objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies .
25. Select a SnapSync policy.
26. Click Advanced to edit Retention policies.
27. Click Next.
28. Enter any operations that should be run at Hooks during the sync process (or any future sync processes).
For more information, see Customizing vFiles Management with Hook Operations.
29. Click Next.
30. Review the dSource Configuration and Data Management information.
31. Click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync. You can monitor these jobs by clicking Active Jobs in
the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the files icon will change to a dSource ic
on on the Environments > Databases screen, and the dSource will be added to the list of My Databases under its assigned group.
The dSource Card
After you have created a dSource, you can view information about it and make modifications to its policies and permissions on the dSo
urce card. In the Databases panel, click the Open icon to view the front of the dSource card. The card will then flip, showing you
information such as the Source and Data Management configuration.

Related Links
Unstructured Files - Getting Started
Provisioning Unstructured Files as vFiles
Customizing vFiles with Hook Operations

923

Delphix User Guide 2016 Delphix

Provisioning Unstructured Files as vFiles

This topic describes the process of provisioning to a set of unstructured files as vFiles.

Prerequisites
You will need an unstructured files dSource, as described in Linking Unstructured Files, or an existing vFiles from which you want to
provision another.
The target environment must meet the requirements outlined in Unstructured Files Environment Requirements.
Unstructured Files on Cluster Environments
Unstructured files cannot be linked from, or provisioned to, any form of cluster environment, such as an Oracle RAC environment. To
link or provision unstructured files from a host that is part of a cluster, add the host as a standalone environment. Then, link from or
provision to this standalone host.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Databases.
4. Select My

Databases.

5.

Select a dSource or vFiles.

6.

Select a snapshot.

7.

Click Provision.
The Provision vFiles panel will open, and the field Mount Path will auto-populate with the path to the files on
the source environment.

8.

Select a target environment.

If you need to add a new target environment for the vFiles, click the green Plus icon next to Filter Target to
add the environment.
Environment Compatibility
You can only target a Unix environment when provisioning from a Unix dSources or vFiles. You can only target a Windows
environment when provisioning from a Windows dSources and vFiles.

9.

If necessary, modify the Mount Path.

10.

Click Advanced.

11.

Enter Additional Mount Points.

When it is mounted to the target environment, the vFiles will be mounted to any additional mount points you
provide.
Shared Path
The Shared Path is a relative path dictating which portion of the vFiles should be available on the additional environments. To
share the entirety of the vFiles, specify a Shared Path of /.

12.

Select an Environment User to own the mounted files.

If the files are being mounted to multiple environments, ensure this user is available across all environments.

13.

Click Next.

14.

Enter a vFiles Name.

15.

Select a Target Group for the vFiles.

If necessary, click the green Plus icon to add a new group.

16.
924

Delphix User Guide 2016 Delphix

16.

Select a Snapshot Policy for the vFiles.

If necessary, click the green Plus icon to create a new policy.

17.

Click Next.

18.

Enter any operations that should be run at Hooks during the lifetime of the vFiles.
See Customizing Oracle VDB Configuration Settings for more information.

19.

Click Next.

20.

Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History p
anel of the Dashboard. When provisioning is complete, the vFiles will be included in the group you
designated and listed in the Databases panel. If you select the vFiles in the Databases panel and click the O
pen icon, you can view its card, which contains information about the vFiles and its Data Management
settings.

Related Links
Linking Unstructured Files
Managing Data Operations for vFiles
Creating Empty vFiles from the Delphix Engine

925

Delphix User Guide 2016 Delphix

Customizing Unstructured Files with Hook Operations

Hook operations allow you to execute an ordered list of custom operations at select hook points in linking, provisioning and virtual dataset
management. For details on the types of operations that are available, see children of this page.
dSource Hooks
Virtual Dataset Hooks
Setting Hook Operations
Setting Hook Operations through the Delphix Admin Application
Setting Hook Operations through the CLI
Example of Editing Hook Operations through the CLI
Hook Operation Templates
Creating a Hook Operation Template
Importing a Hook Operation Template
Exporting a Hook Operation Template

dSource Hooks
Hook

Description

Pre-Sync

Operations performed before a sync.

These operations can quiesce data to be captured during the sync, or stop processes that may interfere with the sync.

Post-Sync

Operations performed after a sync. This hook will run regardless of the success of the sync or Pre-Sync hook operations.
These operations can undo any changes made by the Pre-Sync hook.

Virtual Dataset Hooks

Hook

Description

Configure
Clone

Operations performed after initial provision or after a refresh. This hook will run after the virtual dataset has been started.
During a refresh, this hook will run before the Post-Refresh hook.

Pre-Refresh

Operations performed before a refresh.

These operations can cache data from the virtual dataset to be restored after the refresh completes.

Post-Refresh

Operations performed after a refresh. During a refresh, this hook will run after the Configure Clone hook. This hook will not run
if the refresh or Pre-Refresh hook operations fail.
These operations can restore cached data after the refresh completes.

Pre-Rewind

Operations performed before a rewind.

These operations can cache data from the virtual dataset to be restored after the rewind completes.

Post-Rewind

Operations performed after a rewind. This hook will not run if the rewind or Pre-Rewind hook operations fail.
These operations can restore cached data after the rewind completes.

Pre-Snapshot

Operations performed before a snapshot.

These operations can quiesce data to be captured during the snapshot, or stop processes that may interfere with the
snapshot.

Post-Snapshot

Operations performed after a snapshot. This hook will run regardless of the success of the snapshot or Pre-Snapshot hook
operations.
These operations can undo any changes made by the Pre-Snapshot hook.

Operation Failure
If a hook operation fails, it will fail the entire hook: no further operations within the failed hook will be run.

Setting Hook Operations

926

Delphix User Guide 2016 Delphix

You can construct hook operation lists through the Delphix Admin application or the command line interface (CLI). You can either define the
operation lists as part of the linking or provisioning process or edit them on dSources or virtual datasets that already exist.

Setting Hook Operations through the Delphix Admin Application

To specify hook operations during linking or provisioning, navigate to the Hooks tab of the Linking Wizard or Provision Wizard.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation or click Import to load a hook operation template.
4. Click the text area and edit the contents of the operation.
5. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
6. To remove an operation from the list, click the Trash icon on the operation.
7. When you have set all hook operations, click Next to continue with the provisioning process.
To edit hook operations on an already-existing dSource or virtual dataset, navigate to the Hooks tab on the back of the dSource card or virtual
dataset card.
1. Select the hook to edit.
2. The current operations at this hook will be displayed. To edit this list of operations, click the Pencil icon in the top right-hand corner of the
card.
3. Click the Plus icon to add a new operation.
4. Select the type of operation or click Import to load a hook operation template.
5. Click the text area and edit the contents of the operation.
6. You can reorder operations either through drag-and-drop or by clicking the arrow icons.
7. To remove an operation from the list, click the Trash icon on the operation.
8. When you have set all hook operations, click Check to save the changes.

Setting Hook Operations through the CLI

To specify hook operations during linking, edit the relevant hook's array of operations defined on the LinkingParameters > Source >
Operations object.
To specify hook operations during provisioning, edit the relevant hook's array of operations defined on the ProvisionParameters > Source
> Operations object.
To edit hook operations on an already-created dSource, edit the relevant hook's array of operations defined on the Source > Operations obje
ct.
To edit hook operations on an already-created virtual dataset, edit the relevant hook's array of operations defined on the Source > Operation
s object.
For more information about these CLI objects, see the LinkedSourceOperations, VirtualSourceOperations, RunCommandOnSourceOp
eration, and RunExpectOnSourceOperation API documentation in the Help menu of the Delphix Admin application.

Example of Editing Hook Operations through the CLI

1. Navigate to the relevant source's VirtualSourceOperations object.
2. Select a hook to edit.
delphix> source
delphix source> select "pomme"
delphix source "pomme"> update
delphix source "pomme" update *> edit operations
delphix source "pomme" update operations *> edit postRefresh
3. Add an operation at index 0.
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
delphix source "pomme" update operations postRefresh
Properties
type: RunCommandOnSourceOperation (*)
command: echo Refresh completed. (*)
delphix source "pomme" update operations postRefresh

927

*> add
0 *> set type=RunCommandOnSourceOperation
0 *> set command="echo Refresh completed."
0 *> ls

0 *> commit

Delphix User Guide 2016 Delphix

4. Add another operation at index 1 and then delete it.

delphix
delphix
delphix
delphix
delphix
delphix

source
source
source
source
source
source

"pomme"
"pomme"
"pomme"
"pomme"
"pomme"
"pomme"

update
update
update
update
update
update

operations
operations
operations
operations
operations
operations

postRefresh
postRefresh
postRefresh
postRefresh
postRefresh
postRefresh

*> add
1 *> set type=RunCommandOnSourceOperation
1 *> set command="echo Refresh completed."
1 *> back
*> unset 1
*> commit

Hook Operation Templates

You can use templates to store commonly used operations, which allows you to avoid repeated work when an operation is applicable to more
than a single dSource or virtual dataset. You manage templates through the Delphix Admin application.
Hook Operations Templates Not Available via CLI
Hook operation templates cannot be fully utilized from the CLI. Manage and use hook operations through the Delphix Admin applicatio
n.

Creating a Hook Operation Template

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Operation Templates.
4. Click the Plus icon to add a new operation template.
5. Enter a Name for the template.
6. Select an operation Type.
7. Enter a Description detailing what the operation does or how to use it.
8. Enter operation Contents to implement the operation partially or fully.
9. Click Create.

Importing a Hook Operation Template

To import a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Click Import.
4. Select the template to import.
5. Click Import.
6. When you have set all hook operations, click Check to save the changes.

Exporting a Hook Operation Template

To export a hook operation template, navigate to the Hooks tab on the back of the dSource or virtual dataset card.
1. Select the hook to edit.
2. Click the Plus icon to add a new operation.
3. Select the type of operation.
4. Click the text area and edit the contents of the operation.
5. Click Export.
6. Enter a Name for the template.
7. Enter a Description detailing what the operation does or how to use it.
8. Click Create.

928

Delphix User Guide 2016 Delphix

Unstructured Files Hook Operation Notes

Shell Operations
RunCommand Operation
RunBash Operation
Shell Operation Tips
Other Operations
RunExpect Operation
RunPowershell Operation
Unstructured Files Environment Variables
dSource Environment Variables
VDB Environment Variables

Shell Operations
RunCommand Operation

The RunCommand operation runs a shell command on a Unix environment using whatever binary is available at /bin/sh. The environment user
runs this shell command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the shell command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Examples of RunCommand Operations

You can input the full command contents into the RunCommand operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
if test -d "$remove_dir"; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
If a script already exists on the remote environment and is executable by the environment user, the RunCommand operation can execute this
script directly.

/opt/app/oracle/product/10.2.0.5/db_1/dbs/myscript.sh "$ARG_ENVIRONMENT_VARIABLE" "second

argument in double quotes" 'third argument in single quotes'
RunBash Operation

The RunBash operation runs a Bash command on a Unix environment using a bash binary provided by the Delphix Engine.The environment user
runs this Bash command from their home directory. The Delphix Engine captures and logs all output from this command. If the script fails, the
output is displayed in the Delphix Admin application and command line interface (CLI) to aid in debugging.
If successful, the Bash command must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of RunBash Operations

You can input the full command contents into the RunBash operation.

remove_dir="$DIRECTORY_TO_REMOVE_ENVIRONMENT_VARIABLE"
# Bashisms are safe here!
if [[ -d "$remove_dir" ]]; then
rm -rf "$remove_dir" || exit 1
fi
exit 0
Shell Operation Tips

929

Delphix User Guide 2016 Delphix

Using nohup

You can use the nohup command and process backgrounding from resource in order to "detach" a process from the Delphix Engine. However, if
you use nohup and process backgrounding, you MUST redirect stdout and stderr.
Unless you explicitly tell the shell to redirect stdout and stderr in your command or script, the Delphix Engine will keep its connection to the
remote environment open while the process is writing to either stdout or stderr . Redirection ensures that the Delphix Engine will see no more
output and thus not block waiting for the process to finish.
For example, imagine having your RunCommand operation background a long-running Python process. Below are the bad and good ways to do
this.
Bad Examples
nohup
nohup
nohup
nohup

python
python
python
python

file.py
file.py
file.py
file.py

& # no redirection
2>&1 & # stdout is not redirected
1>/dev/null & # stderr is not redirected
2>/dev/null & # stdout is not redirected

Good Examples
nohup python file.py 1>/dev/null 2>&1 & # both stdout and stderr redirected, Delphix Engine will not
block

Other Operations
RunExpect Operation

The RunExpect operation executes an Expect script on a Unix environment. The Expect utility provides a scripting language that makes it easy to
automate interactions with programs which normally can only be used interactively, such as ssh. The Delphix Engine includes a
platform-independent implementation of a subset of the full Expect functionality.
The script is run on the remote environment as the environment user from their home directory. The Delphix Engine captures and logs all output
of the script. If the operation fails, the output is displayed in the Delphix Admin application and CLI to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunExpect Operation

Start an ssh session while interactively providing the user's password.

spawn ssh [email protected]

expect {
-re {Password: } {
send "${env(PASSWORD_ENVIRONMENT_VARIABLE)}\n"
}
timeout {
puts "Timed out waiting for password prompt."
exit 1
}
}
exit 0
RunPowershell Operation

The RunPowershell operation executes a Powershell script on a Windows environment. The environment user runs this shell command from their
home directory. The Delphix Engine captures and logs all output of the script. If the script fails, the output is displayed in the Delphix
Admin application and command line interface (CLI) to aid in debugging.
If successful, the script must exit with an exit code of 0. All other exit codes will be treated as an operation failure.
Example of a RunPowershell Operation

You can input the full command contents into the RunPowershell operation.

930

Delphix User Guide 2016 Delphix

$removedir = $Env:DIRECTORY_TO_REMOVE
if ((Test-Path $removedir) -And (Get-Item $removedir) -is [System.IO.DirectoryInfo]) {
Remove-Item -Recurse -Force $removedir
} else {
exit 1
}
exit 0
Unstructured Files Environment Variables
Operations that run user-provided scripts have access to environment variables. For operations associated with specific dSources or virtual
databases (VDBs), the Delphix Engine will always set environment variables so that the user-provided operations can use them to access the
dSource or VDB.
dSource Environment Variables

Environment Variable

Description

DLPX_DATA_DIRECTORY

Path where linked-staged database is mounted

VDB Environment Variables

Environment Variable

Description

DLPX_DATA_DIRECTORY

Path where virtual database is mounted

931

Delphix User Guide 2016 Delphix

Managing Data Operations for vFiles

These topics describes how to run and manage various data operations for vFiles once they have been provisioned.
Enabling and Disabling vFiles
Rewinding vFiles
Refreshing vFiles
Deleting vFiles
Migrating vFiles

932

Delphix User Guide 2016 Delphix

Enabling and Disabling vFiles

This topic describes the process of enabling and disabling a vFiles.
Prerequisites

You must have already provisioned a vFiles. For more information, see Provisioning Unstructured Files as vFiles.
Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2.

Click Manage.

3.

Select Databases.

4.

Select My Databases.

5.

Select the vFiles to disable.

6. On the back of the card, move the slider control from Enabled to Disabled.
When you are ready to enable the vFiles again, move the slider control form Disabled to Enabled, and the vFiles will continue to function as it did
previously.
Disabling the vFiles will unmount it from target environments. This unmount will fail if there are processes still accessing the vFiles.

Related Links

Managing Data Operations for vFiles

Provisioning Unstructured Files as vFiles

933

Delphix User Guide 2016 Delphix

Rewinding vFiles
This topic describes how to rewind a vFiles.
Prerequisites

You must have already provisioned a vFiles. For more information, see Provisioning Unstructured Files as vFiles.
Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select the vFiles to rewind.
6. Select a past snapshot.
7. Click Rewind below the snapshots.

Related Links
Managing Data Operations for vFiles
Provisioning Unstructured Files as vFiles

934

Delphix User Guide 2016 Delphix

Refreshing vFiles
This topic describes how to manually refresh a vFiles.
Refreshing a vFiles will re-provision the vFiles from its parent. As with the normal provisioning process, you can choose to refresh the vFiles from
any snapshot available in its parent. However, you should be aware that refreshing a vFiles will delete any changes that have been made to it
over time. When you refresh a vFiles, you are essentially resetting it to the state you select during the Refresh process. You can refresh a vFiles
manually, as described in this topic, or you can set a vFiles refresh policy, as described in the topics Managing Policies: An Overview, Creating
Custom Policies, and Creating Policy Templates.
Although the VDB no longer contains the previous contents, the previous Snapshots and TimeFlow still remain in the Delphix Engine
and are accessible through the Command Line Interface (CLI).

Prerequisites

You must have already provisioned a vFiles. For more information, see Provisioning Unstructured Files as vFiles.
Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select the vFiles to refresh.
6.

On the back of the vFiles card, click the Refresh icon in the lower right-hand corner.

7. Select a snapshot from which to refresh.

Related Links
Managing Data Operations for vFiles
Provisioning Unstructured Files as vFiles

935

Delphix User Guide 2016 Delphix

Deleting vFiles
This topic describes how to delete a vFiles.
Prerequisites

You must have already provisioned a vFiles. For more information, see Provisioning Unstructured Files as vFiles.
Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select the vFiles you want to delete.
6. Click the Trash icon.
7. Click Yes to confirm.

Deleting a vFiles may fail if it cannot be unmounted successfully from all target environments. You can use the Force Delete option to
ignore all failures during unmount.

Related Links

Managing Data Operations for vFiles

Provisioning Unstructured Files as vFiles

936

Delphix User Guide 2016 Delphix

Migrating vFiles
This topic describes how to migrate a vFiles from one target environment to another.
Prerequisites

You must have already provisioned a vFiles. For more information, see Provisioning Unstructured Files as vFiles.
Procedure

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Databases.
4. Select My Databases.
5. Select the vFiles you want to migrate.
6. Click the Open icon.
7. Move the slider control from Enabled to Disabled to unmount the files.
For more information, see Enabling and Disabling vFiles.
8. In the bottom right-hand corner of the vFiles card, click the vFiles Migrate icon.
9. Select a new target environment.
10. Click the Check icon to confirm your selection.
11. Move the slider control to Enabled.
12. Click Yes to confirm.
Within a few minutes, your vFiles will re-start in the new environment, and you can continue to work with it as you would any other vFiles.

Related Links

Enabling and Disabling vFiles

Rewinding vFiles
Refreshing vFiles
Deleting vFiles

937

Delphix User Guide 2016 Delphix

Creating Empty vFiles from the Delphix Engine

This topic describes the procedure for creating empty vFiles. This feature is available for unstructured files. Unstructured files are a dataset that
is treated as simply a directory tree full of files. It is not a database, and it does not receive any special treatment or processing by Delphix. It is
just a set of files. You can create vFiles

in two ways: by provisioning from an existing dataset that is, from a dSource or
from another vFiles or by creating an empty vFiles and filling it with data.
Creating an empty vFiles places an initially-empty mount on target environments, hence the term "empty vFiles." This mount is useful when you
have no existing files to copy into the Delphix Engine, but you do have files which you will generate, track, and copy with vFiles.
vFiles created without dSources are almost identical to those created by provisioning. The only thing you cannot do with them is refresh. Refreshi
ng a dataset means overwriting the datasets content with new data that is pulled in from the datasets parent. If you create new vFiles from
scratch, that newly-created dataset will not have a parent. Therefore, it cannot be refreshed. All other functionality is identical you can provision
from such a dataset, rewind, take snapshots, and so forth.

Prerequisites
The target environment must meet the requirements outlined in Unstructured Files Environment Requirements.
Unstructured Files on Cluster Environments
You cannot create vFiles on any form of cluster environment, such as an Oracle RAC environment. To create a vFiles on a host that is
part of a cluster, add the host as a standalone environment. Then, create the vFiles on this standalone host.

Procedure
To create new vFiles without provisioning:
1. Login to the Delphix Admin application.
2. Click Manage.
3. Select Database.
4. Select Create vFiles as seen below.

Related Links
Managing Data Operations for vFiles
Provisioning Unstructured Files as vFiles

938

Delphix User Guide 2016 Delphix

Restoring Data from Unstructured Files

This topic describes the process of restoring data on a source system from a copy stored in the Delphix Engine.
When creating a dSource, the Delphix Engine takes a backup of your data from the source system. To recover this data from the Delphix Engine,
you can create a restoration dataset. Creating a restoration dataset will mount the Delphix-copy of this data to the source environment at a
specified location. This data can then be copied out of the mount or accessed by a data restoration tool.
Because this data is meant only for restoration purposes, you cannot use the Delphix Engine to snapshot changes made to the mount or to
provision from data in the mount.

Prerequisites
You will need an unstructured files dSource, as described in Linking Unstructured Files, or an existing vFiles from which you want to
provision another.
The target environment must meet the requirements outlined in Unstructured Files Environment Requirements.

Procedure
1. Login to the command line interface (CLI) using Delphix Admin credentials.
2. Navigate to database and select createRestorationDataset.

delphix> database
delphix database> createRestorationDataset
3. View parameter information using list.

delphix database createRestorationDataset> list

Properties
---------type: AppDataRestorationDatasetCreationParameters
container:
type: AppDataContainer
name: (required)
description: (unset)
group: (required)
sourcingPolicy: (unset)
source:
type: AppDataRestorationSource
name: (unset)
additionalMountPoints: (unset)
config: (unset)
sourceConfig:
type: AppDataDirectSourceConfig
name: (required)
environmentUser: (unset)
linkingEnabled: true
path: (required)
repository: (required)
timeflowPointParameters:
type: TimeflowPointSemantic
container: (required)
location: LATEST_POINT
Operations
---------defaults
4. Fill in the required parameter fields, or select defaults.

939

Delphix User Guide 2016 Delphix

delphix database createRestorationDataset> set

delphix database createRestorationDataset> set
delphix database createRestorationDataset> set
delphix database createRestorationDataset> set
sourceConfig.path=/home/delphix/restoration
delphix database createRestorationDataset> set
delphix database createRestorationDataset> set
delphix
delphix
delphix
delphix

database
database
database
database

name=restoration
group=Untitled
sourceConfig.name=restoration

sourceConfig.repository=builtin:files
timeflowPointParameters.container=source

createRestorationDataset> defaults
createRestorationDataset defaults> set container=source
createRestorationDataset defaults> commit
createRestorationDataset> set sourceConfig.repository=builtin:files

5. Create a restoration dataset using commit.

delphix database createRestorationDataset> commit

You now have a restored dSource copy on your source machine mounted to the specified path.
7. Use select to select and manage the restoration dataset. Most source and database operations are not supported for restoration
datasets.

delphix database> select restoration

8. When it is time to delete, select the restoration dataset and select delete.

delphix database restoration> delete

delphix database restoration delete *> commit

Supported Operations
Because restoration datasets are not fully provisioned like normal virtual datasets, they do not support the full set of management features
available through the Delphix Engine. Restoration datasets support the following operations:
delete
refresh
switchTimeflow
undo
enable
disable
All other source and database operations will result in errors when executed against a restoration dataset.

Related Links
Unstructured Files - Getting Started
Provisioning Unstructured Files as vFiles
Customizing vFiles with Hook Operations

940

Delphix User Guide 2016 Delphix

_Virtualizing Oracle Enterprise Business Suite

941

Delphix User Guide 2016 Delphix

Virtualizing Oracle Enterprise Business Suite

942

Delphix User Guide 2016 Delphix

Oracle EBS + Delphix: Conceptual Overview

This topic provides a conceptual overview of the integration between the Delphix Engine and Oracle Enterprise Business Suite (EBS).
Why Use the Delphix Engine with EBS?
Overview of Linking and Provisioning EBS
dbTechStack Dataset
Database Dataset
appsTier Dataset
How Does It Work?
Related Links

Why Use the Delphix Engine with EBS?

Oracle Enterprise Business Suite offers a multitude of enterprise resource planning (ERP), supply chain management (SCM) and customer
relationship management (CRM) applications useful for running a business. Typical EBS instances are consumed horizontally across an
organization, but managed on-premise by an IT organization. Most businesses hire consultants or in-house developers to customize these
instances to fit business needs.
Production EBS instances are critical to many business processes; EBS is expected to always be available and functioning correctly. An IT
organization's EBS team is responsible for maintaining this production instance: this team monitors the instance and manages how software
modifications are integrated. Common EBS software modifications include patches provided by Oracle or new application logic provided by
consultants or in-house developers.
However, before making a software modification to their production EBS instance, most EBS teams vet the modification. These teams typically
maintain a series of non-production copies of their production EBS instance to use for the vetting process. To vet a modification, the EBS team
will modify a non-production instance in an attempt to identify bugs in the modification that might lead to incorrect functionality, performance
regressions, or downtime. Once a modification has been installed and tested successfully, it is considered vetted and the same modification is
made to the production instance.
Maintaining non-production copies of EBS is costly. EBS teams not only need to provision and maintain resources for each copy, they also must
update each copy to match production every time production itself is modified. This process takes a couple hours at a minimum and can take up
to a week or more.
The Delphix Engine can alleviate much of the pain around managing non-production copies of Oracle Enterprise Business Suite. You can link a
production EBS instance to the Delphix Engine and use it to provision virtual copies. These virtual copies lower storage costs associated with
non-production. They also drastically reduce the amount of active attention required from the EBS team. When a change is made to the
production EBS instance, the Delphix Engine can synchronize its copy; all virtual EBS instances can then be refreshed to match this new version
of production. The process of refreshing a virtual EBS instance is fully automated, so an EBS team no longer needs to invest copious amounts of
time refreshing non-production instances manually.
In addition, virtual EBS instances can be snapshotted in known healthy states so that risky modifications can easily be rolled back while being
vetted. This functionality provides modern version control semantics for a process which previously had none.

Overview of Linking and Provisioning EBS

Oracle Enterprise Business Suite is primarily comprised of a database service and a plethora of application services. The Delphix Engine
supports the linking and provisioning of all EBS datasets, including the database technology stack (dbTechStack), database, and application files
(appsTier). Note that the Delphix Engine can also manage custom extensions and plug-ins.
The process of linking EBS data involves creating multiple dSources:
a dSource for the dbTechStack
a dSource for the Oracle database used by EBS
a dSource for the appsTier
These dSources are collectively referred to as EBS dSources. They are also the source datasets from which you can provision virtual EBS
instances.
The process of provisioning a virtual EBS instance involves provisioning from each of these dSource separately to the proper environments in
sequence. You can add custom configuration logic to the Delphix Engine for each EBS instance such that the linking, provisioning, and refresh
processes are fully automated.

dbTechStack Dataset
The source dbTechStack is linked using the Delphix Engine's EBS support: the linking process automatically runs pre-clone logic to ensure EBS

943

Delphix User Guide 2016 Delphix

configuration is always appropriately staged at the time of data capture. When you provision EBS, the Delphix Engine automates post-clone
configuration such that a copy of the dbTechStack is available for use on the target dbTier server with no additional effort. You can add this copy
of the dbTechStack to the Delphix Engine as an Oracle installation home and use it to host an EBS virtual database (VDB).

Database Dataset
The database dSource is linked using the Delphix Engine's support for Oracle databases. This dSource contains database data files that EBS is
currently using. For more information about managing Oracle databases, see Managing Oracle, Oracle RAC, and Oracle PDB Data Sources.
When you provision EBS, you will use the Delphix Engine to set up a copy of the EBS database on the target dbTier server. This copy of the
database will be used to back virtual EBS instances appsTier.

appsTier Dataset
The appsTier is linked using the Delphix Engine's EBS support: the linking process automatically runs pre-clone logic to ensure EBS configuration
is always appropriately staged at the time of data capture. When you provision EBS, the Delphix Engine will automate post-clone configuration
such that a copy of the appsTier is available for use on the target appsTier server. This virtual copy of the appsTier will connect to the provisioned
EBS virtual database (VDB).

How Does It Work?

The Delphix Engine's linking and provisioning logic follows the Oracle-recommended cloning procedures outlined in the following Oracle Support
documents found at http://docs.oracle.com:
Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)
Cloning Oracle Applications Release 12 with Rapid Clone (Doc ID 406982.1)
Cloning Oracle Applications Release 11i with Rapid Clone (Doc ID 230672.1)

Related Links
Managing Oracle, Oracle RAC, and Oracle PDB Data Sources
Oracle EBS R12.2
Oracle EBS R12.1
Virtual EBS Instance Recipes

944

Delphix User Guide 2016 Delphix

Oracle EBS R12.2

This section describes linking and provisioning Oracle Enterprise Business Suite R12.2.
Source EBS R12.2 Instance Requirements
Virtual EBS R12.2 Instance Requirements
Preparing a Source EBS R12.2 Instance for Linking
Linking a Source EBS R12.2 Instance
Preparing Target EBS R12.2 Environments for Provisioning
Provisioning a Virtual EBS R12.2 Instance
Monitoring EBS R12.2 dbTechStack Provisioning Progress
Monitoring EBS R12.2 appsTier Provisioning Progress

945

Delphix User Guide 2016 Delphix

Source EBS R12.2 Instance Requirements

Operating Systems
dbTier Requirements
Supported Topologies
appsTier Requirements
Supported Topologies
Caveats
Related Links
The Delphix Engine supports linking a variety of versions and configurations of Oracle Enterprise Business Suite R12.2. Below, detailed
compatibility notes are outlined.
Note that minor releases of EBS are not certified for Delphix Engine compatibility individually: major release support implies support for any minor
release.
To review the requirements for provisioning a virtual EBS R12.2 instance from the Delphix Engine, see Virtual EBS R12.2 Instance
Requirements.

Operating Systems
Linux
Solaris
AIX and HP-UX Not Supported
The Delphix Engine does not support linking EBS instances running on AIX or HP-UX.

dbTier Requirements
Supported Topologies
Oracle SI dbTechStack and Database
Oracle RAC dbTechStack and Database

appsTier Requirements
Supported Topologies
Single-node appsTier
Multi-node appsTier with a shared APPL_TOP
Non-shared APPL_TOP Not Supported
The Delphix Engine does not provide support for linking a multi-node appsTier where the APPL_TOP is not shared between nodes.

Caveats
The Delphix Engine does not provide support for linking an EBS R12.2 instance utilizing custom context variables maintained in the EBS context
file.

Related Links
Virtual EBS R12.2 Instance Requirements

946

Delphix User Guide 2016 Delphix

Virtual EBS R12.2 Instance Requirements

Operating Systems
dbTier Requirements
Supported Topologies
appsTier Requirements
Supported Topologies
Caveats
Related Links
The Delphix Engine supports provisioning a variety of versions and configurations of Oracle Enterprise Business Suite R12.2. Below, detailed
compatibility notes are outlined.
Note that minor releases of EBS are not certified for Delphix Engine compatibility individually: major release support implies support for any minor
release.
To review the requirements for linking an EBS R12.2 instance to the Delphix Engine, see Source EBS R12.2 Instance Requirements.

Operating Systems
Linux
Solaris
AIX and HP-UX Not Supported
The Delphix Engine does not support provisioning EBS instances to AIX or HP-UX.

dbTier Requirements
Supported Topologies
Oracle SI dbTechStack and Database
Oracle RAC Not Supported
The Delphix Engine does not support provisioning Oracle RAC dbTechStack for use with Oracle Enterprise Business Suite.
However, you may provision an Oracle SI dbTier from a linked EBS RAC dbTier instance. During the provisioning process, the Delphix
Engine will relink the dbTechStack for use with an Oracle SI database and scale down the Oracle RAC database to an Oracle SI
database.

appsTier Requirements
Supported Topologies
Single-node appsTier
Multi-node appsTier with a shared APPL_TOP
Non-shared APPL_TOP Not Supported
The Delphix Engine does not provide support for provisioning a multi-node appsTier where the APPL_TOP is not shared between
nodes.

appsTier Topology Is Configurable

The appsTier topology of the virtual EBS instance does NOT need to match the appsTier topology of the source EBS instance. The
Delphix Engine will automate scale up or scale down logic as required during provisioning.

Caveats

947

Delphix User Guide 2016 Delphix

The Delphix Engine will only register the default WLS-managed server for each server type during multi-node appsTier provisioning. Additional
WLS managed servers need to be registered manually or as a Configure Clone hook.

Related Links
Source EBS R12.2 Instance Requirements

948

Delphix User Guide 2016 Delphix

Preparing a Source EBS R12.2 Instance for Linking

This topic outlines the prerequisites for linking an EBS R12.2 instance to the Delphix Engine.
Ensure your EBS R12.2 instance is supported
Prepare the dbTier for linking
Delphix Engine's Unix Environment Requirements
oracle User
dbTechStack Binary Permissions
Clean Up Before Provisioning Option
The Delphix Engine's Oracle Database Requirements
Prepare the appsTier for Linking
Delphix Engine's Unix Environment Requirements
applmgr User
Clean Up Before Provisioning Option
Related Links

Ensure your EBS R12.2 instance is supported

See Source EBS R12.2 Instance Requirements to ensure you can link your EBS R12.2 instance to the Delphix Engine.

Prepare the dbTier for linking

Delphix Engine's Unix Environment Requirements
The dbTier must meet the source requirements outlined in Requirements for Unix Environments. These requirements are generic to all source
Unix environments added to the Delphix Engine.

oracle User
The Delphix Engine must have access to an oracle user on the dbTier.
This user should be a member of both the EBS dba and oinstall groups.
The user should have read permissions on all dbTechStack and database files that will be cloned.

dbTechStack Binary Permissions

Verify that the oracle user described above has read permissions at the group level for:
$ORACLE_HOME/bin/nmb
$ORACLE_HOME/bin/nmhs
$ORACLE_HOME/bin/nmo

Clean Up Before Provisioning Option

If you plan to utilize the Cleanup Before Provision option available during dbTechStack provisioning, the Delphix Engine requires the Database
Oracle Home to be patched with Oracle Universal Installer (OUI) version 10.2 or above. You can read more about the Clean Up Provisioning
option in Provisioning a Virtual EBS R12.2 Instance.
Note that provisioning is still possible without this option specified, but you will need to manage the target dbTier's Oracle Inventory manually to
ensure that conflicting entries do not cause provisions to fail.

The Delphix Engine's Oracle Database Requirements

The dbTier must meet the source requirements outlined in Oracle Support and Requirements. These requirements are generic to all Unix
environments containing an Oracle database to be linked.

949

Delphix User Guide 2016 Delphix

Prepare the appsTier for Linking

Delphix Engine's Unix Environment Requirements
The appsTier must meet the source requirements outlined in Requirements for Unix Environments. These requirements are generic to all
source Unix environments added to the Delphix Engine.

applmgr User
The Delphix Engine must have access to an applmgr user on the appsTier.
This user should be a member of the EBS oinstall group.
The user should have read permissions on all appsTier files to be cloned.

Clean Up Before Provisioning Option

If you plan to utilize the Cleanup Before Provision option available during appsTier provisioning, the Delphix Engine requires the Tools Oracle
Home to be patched with Oracle Universal Installer (OUI) version 10.2 or above. You can read more about this provisioning option in Provisionin
g a Virtual EBS R12.2 Instance.
Note that provisioning is still possible without this option specified, but you will need to manage the target appTier's Oracle Inventory manually to
ensure that conflicting entries do not cause provisions to fail.

Related Links
Source EBS R12.2 Instance Requirements
Provisioning a Virtual EBS R12.2 Instance
Oracle Support and Requirements
Requirements for Unix Environments

950

Delphix User Guide 2016 Delphix

Linking a Source EBS R12.2 Instance

This topic describes the process of linking an EBS R12.2 instance and creating the necessary dSources.

Prerequisites
Prepare your source EBS R12.2 instance for linking by following the outline in Preparing a Source EBS R12.2 Instance for Linking.

Procedure
Link the Oracle Database
1.

Link the Oracle database used by EBS, as outlined in Linking an Oracle Data Source.

Link the EBS dbTechStack

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4.

Select the source dbTier environment containing the source dbTechStack.

If you have not already added the environment, see the Managing Unix Environments topics for more
information about adding environments.
Linking from RAC dbTier
If you are linking from a RAC dbTier, select the environment for a single running node of the RAC cluster.

5.

Click the Environment Details tab.

6.

If the oracle environment user described in Preparing a Source EBS R12.2 Instance for Linking is not
already added to the Delphix Engine, add the user.
For more information about adding environment users, see the Managing Unix Environment Users topics .

7.

Click the Databases tab.

8.

Click the Plus icon next to Add Dataset Home.

Adding the files as a dataset home will register the type and location of the files with the Delphix Engine.

9.

For your Dataset Home Type , select E-Business Suite R12.2 dbTechStack.
When you select this type of dataset home, the Delphix Engine will know to automate pre-clone logic.
Specifically, the Delphix Engine will run adpreclone.pl dbTier prior to every SnapSync of the
dbTechStack. During dSource creation, you will be able to enter additional pre-clone steps as Pre-Sync hook
operations.

10.

Enter an Installation Home.

This path should be the Oracle base install directory. For example, if the value of $ORACLE_HOME on your source environment is /u01/
oracle/VIS/11.2.0 , the Oracle base install directory is /u01/oracle/VIS .

11.

Click the Confirm icon to save your dataset home.

If necessary, scroll down the list of dataset homes to view and edit this dataset home.

12. Click Manage.

13. Select Add dSource.
14.

In the Add dSource wizard, select the dbTechStack files source you just created.

15.

Enter the EBS-specific parameters for your dbTechStack.

These parameter values will be used when adpreclone.pl is run.
Ensure that the DB Tier Context Name uses the short hostname.

16.
951

Delphix User Guide 2016 Delphix

16.

Click Advanced.

17.

Exclude the EBS database's data files if they are stored underneath the Oracle base install directory.
These data files will be linked with the database instead of with the dbTechStack. Add the relative path to the
data files to the Paths to Exclude list.

18.

Click Next.

19.

Enter a dSource Name.

20. Select a Database Group for the dSource.

21. Click Next.

Adding a dSource to a database group enables you to set Delphix Domain user permissions for that
dSource's objects, such as snapshots. For more information, see the topics under Users, Permissions, and
Policies Users, Permissions, and Policies.
22. Select a SnapSync policy.
23. Click Next.
24.

Enter any custom pre or post sync logic as Pre-Sync or Post-Sync hook operations.
Remember that adpreclone.pl dbTier is already run prior to every Snapshot of the dbTechStack.
The Pre-Sync hook operations will be run prior to running the adpreclone.pl tool.
For more information, see Customizing Unstructured Files with Hook Operations.

25.

Click Next.

26.

Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync . You can monitor
these jobs by clicking Active Jobs in the top menu bar, or by selecting System > Event Viewer. When the
jobs have completed successfully, the files icon will change to a dSource icon on the Environments > Data
bases screen, and the dSource will be added to the list of My Databases under its assigned group.

Link the EBS appsTier

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Select the source appsTier environment.
If you have not already added the environment, see the Managing Unix Environments topics for more information about adding
environments.
Linking from multi-node appsTier
If you are linking from a multi-node appsTier, select the environment for the node on which EBS admin services reside.

5. Click the Environment Details tab.

6. If the applmgr environment user described in Preparing a Source EBS R12.2 Instance for Linking is not already added to the
Delphix Engine, add the user.
For more information about adding environment users, s ee the Managing Unix Environment Users topics.
7. Click the Databases tab.
8. Click the Plus icon next to Add Dataset Home.
Adding the files as a dataset home will register the type and location of the files with the Delphix Engine.
9. For your Dataset Home Type , select E-Business Suite R12.2 appsTier.
When you select this type of dataset home, the Delphix Engine will know to automate pre-clone logic. Specifically the Delphix Engine will
run adpreclone.pl appsTier prior to every SnapSync of the appsTier. During dSource creation, you will be able to enter additional
pre-clone steps as Pre-Sync hook operations.
10. Enter an Installation Home.
This path should be the one level above Run/Patch edition file system base directory. For example, if the value of $RUN_BASE on your
source environment is /u01/oracle/VIS/fs1, the install directory is /u01/oracle/VIS.
11. Click the Confirm icon to save your dataset home.
If necessary, scroll down the list of dataset homes to view and edit this dataset home.
12. Click Manage.
13.
952

Delphix User Guide 2016 Delphix

13. Select Databases.

14. Select Add dSource.
15. In the Add dSource wizard, select the appsTier files source you just created.
16. Enter the EBS-specific parameters for your appsTier.
These parameter values will be used when adpreclone.pl is run.
17. Click Advanced .
18. Add the relative paths of files to exclude to the Paths to Exclude list.
Exclude the non-edition file system, instance directories, and FMW home directories which will be recreated when provisioning a virtual
EBS appsTier.
These paths should typically include:
fs_ne
fs1/inst
fs2/inst
fs1/FMW_Home
fs2/FMW_Home
19. Click Next.
20. Enter a dSource Name.
21. Select a Database Group for the dSource.
22. Click Next.
Adding a dSource to a database group enables you to set Delphix Domain user permissions for that dSource's objects, such as
snapshots. For more information, s ee the topics under Users, Permissions, and Policies .
23. Click Next.
24. Select a SnapSync policy.
25. Click Next.
26. Enter any custom pre- or post-sync logic as Pre-Sync or Post-Sync hook operations.
Remember that adpreclone.pl appsTier is already run prior to every SnapSync of the appsTier.
The Pre-Sync hook operations will be run prior to running the adpreclone.pl tool.
For more information, see Customizing Unstructured Files with Hook Operations .
27. Click Next.
28. Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the files icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

Related Links
Preparing a Source EBS R12.2 Instance for Linking
Linking an Oracle Data Source
Preparing a Source EBS R12.2 Instance for Linking
Managing Unix Environment Users
Users, Permissions, and Policies
Customizing Unstructured Files with Hook Operations
Managing Unix Environments

953

Delphix User Guide 2016 Delphix

Preparing Target EBS R12.2 Environments for Provisioning

This topic outlines the prerequisites for provisioning a virtual EBS R12.2 instance to target environments.
Ensure your target EBS R12.2 instance is supported
Prepare the dbTier for provisioning
Delphix Engine's Unix Environment Requirements
oracle User
oraInst.loc
The Delphix Engine's Oracle Database Requirements
Prepare the appsTier for Provisioning
Delphix Engine's Unix Environment Requirements
applmgr User
oraInst.loc
Related Links

Ensure your target EBS R12.2 instance is supported

See Virtual EBS R12.2 Instance Requirements to ensure you can provision your EBS R12.2 instance.

Prepare the dbTier for provisioning

Delphix Engine's Unix Environment Requirements
The dbTier must meet the target requirements outlined in Requirements for Unix Environments. These requirements are generic to all target
Unix environments you add to the Delphix Engine.

oracle User
The Delphix Engine must have access to an oracle user on the dbTier.
This user should be a member of both the EBS dba and oinstall groups.
This user will be given proper permissions to manage the dbTechStack and database.

oraInst.loc
An oraInst.loc file must exist on the dbTier prior to provisioning. This file will specify where the oraInventory directories live or where they should
be created if they do not already exist.
The oraInst.loc file is typically located at /etc/oraInst.loc on Linux or /var/opt/oracle/oraInst.loc on Solaris. Ensure that the
oraInventory to which this file points is writeable by the oracle user.
Consult Oracle EBS documentation for more information about where to place this file on your dbTier and what this file should contain.

The Delphix Engine's Oracle Database Requirements

The dbTier must meet the target requirements outlined in Oracle Support and Requirements. These requirements are generic to all target Unix
environments expected to host a virtual Oracle database.

Prepare the appsTier for Provisioning

Delphix Engine's Unix Environment Requirements
The appsTier must meet the target requirements outlined in Requirements for Unix Environments. These requirements are generic to all target
Unix environments added to the Delphix Engine.

applmgr User

954

Delphix User Guide 2016 Delphix

The Delphix Engine must have access to an applmgr user on the appsTier.
This user should be a member of the EBS oinstall group.
This user will be given proper permissions to manage the appsTier.

oraInst.loc
An oraInst.loc file must exist on every appsTier node prior to provisioning. This file will specify where the oraInventory directories live or where
they should be created if they do not already exist.
The oraInst.loc file is typically located at /etc/oraInst.loc on Linux or /var/opt/oracle/oraInst.loc on Solaris. Ensure that the
oraInventory to which this file points is writeable by the applmgr user.
Delphix recommends that this file specify an oraInventory location under the virtual appsTier mount path.
If you are provisioning a single-node appsTier, this recommendation is OPTIONAL; putting the oraInventory directories on
Delphix-provided storage merely eases administration of the virtual EBS instance.
If you are provisioning a multi-node appsTier, this recommendation is REQUIRED; the Delphix Engine's automation requires that all
nodes in the appsTier have access to the oraInventory directories via Delphix-provided storage.
Consult Oracle EBS documentation for more information about where to place this file on your appsTier and what this file should contain.

Related Links
Virtual EBS R12.2 Instance Requirements
Requirements for Unix Environments
Oracle Support and Requirements

955

Delphix User Guide 2016 Delphix

Provisioning a Virtual EBS R12.2 Instance

This topic describes the process of provisioning a virtual EBS R12.2 instance.

Prerequisites
You must have already linked a source instance of EBS R12.2. For more information, see Linking a Source EBS R12.2 Instance.
Prepare your target EBS R12.2 environments for provisioning by following the outline in Preparing Target EBS R12.2 Environments for
Provisioning.
Snapshot Coordination
Changes applied to EBS and picked up only in certain dSource snapshots may make certain combinations of snapshots across the
appsTier and dbTier incompatible. When provisioning, refreshing, or rewinding a virtual EBS instance, be sure the points in time you
select for each dataset are compatible with each other.

Procedure
Provision the EBS dbTechStack
1.

Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select My Databases.
4.

Select the dbTechStack dSource.

5.

Select a dSource snapshot.

All snapshots will have staged configuration prepared by adpreclone.pl and any hook operations placed
on the dSource.

6. Click Provision.
The Provision vFiles wizard will open.
7. Select an Environment.
This environment will host the virtual dbTechStack and be used to execute hook operations specified in step 16.
8. Select an Environment User.
This user should be the oracle user outlined in Preparing Target EBS R12.2 Environments for Provisioning.
9. Enter a Mount Path for the virtual dbTechStack files.
10. Enter the EBS-specific parameters for the virtual dbTechStack. A subset of these parameters are discussed in more detail below.
a. Ensure that the Target DB Hostname value is the short hostname, not the fully-qualified hostname.
b. The APPS Password is required to configure the virtual dbTechStack.
This password is encrypted when stored within the Delphix Engine and is available as an environment variable to the adcfgclo
ne process.
c. Enable the Disable RAC option if you want to permit the Delphix Engine to automatically disable the RAC option for the binaries
when applicable.
This option is necessary if provisioning from a dSource with RAC dbTier, because the binaries are relinked with the rac_on opti
on even after running adcfgclone. If the source binaries already have the RAC option disabled (also the case for SI dbTier),
the Delphix Engine ignores this option.
d. Enable the Cleanup Before Provision option if you want to permit the Delphix Engine to automatically cleanup stale EBS
configuration during a refresh. This option is recommended, but only available if your Oracle Home is patched with Oracle
Universal Installer (OUI) version 10.2 or above.
i. With this option enabled, the Delphix Engine will inspect the target environment's oraInventory prior to refreshing this
virtual dbTechStack. If any Oracle Homes are already registered within the specified Mount Path, the Delphix Engine
will detach them from the inventory prior to running adcfgclone. These homes must be detached prior to running
post-clone configuration, or else adcfgclone will fail, citing conflicting oraInventory entries as an issue.
ii. Without this option enabled, Oracle Homes found to conflict with the specified Mount Path will be reported in an error
instead of automatically detached. For refresh to succeed, conflicting Oracle Homes must be manually detached prior to
refresh.
11. Click Next.
12. Enter a vFiles Name.
13.

Select a Target Group for the vFiles.

956

Delphix User Guide 2016 Delphix

13.

If necessary, click the green Plus icon to add a new group.

14.

Select a Snapshot Policy for the vFiles.

If necessary, click the green Plus icon to create a new policy.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

15.

Click Next.

16.

Enter any custom hook operations that are needed to help correctly manage the virtual dbTechStack files.
For more information about these hooks, when they are run, and how operations are written, see Customizin
g Unstructured Files with Hook Operations.
The Configure Clone hook will be run after the adcfgclone.pl tool has both mounted and configured the
dbTechStack.

17. Click Next.

18. Click Finish.

When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History p
anel of the Dashboard. When provisioning is complete, the dbTechStack vFiles will be included in the group
you designated and listed in the Databases panel. If you select the dbTechStack vFiles in the Databases pa
nel and click the Open icon, you can view its card, which contains information about the virtual files and its
Data Management settings.
19.

For tips on monitoring the progress of dbTechStack provisioning, see Monitoring EBS R12.2 dbTechStack
Provisioning Progress.

Register the EBS dbTechStack

Register the freshly-provisioned dbTechStack with the Delphix Engine.
1.

Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Environments.
4.

Select the target dbTier environment.

5.

Click the Databases tab.

6.

Click the Plus icon next to Add Dataset Home.

7.

Select Oracle as your Dataset Home Type.

8.

Enter an Installation Home.

This path should be the value of $ORACLE_HOME on your target dbTier; this path will live under the mount
path specified when you provisioned the virtual dbTechStack.
Commonly, this path looks like /u01/oracle/VIS/11.2.0.

9. Click the Confirm icon to save your dataset home.

Scroll down the list of dataset homes to view and edit this dataset home if necessary.
10.

Refresh the dbTier environment.

Refreshing the environment will discover EBS database listener and ensure it is available for selection when
provisioning the EBS database.
a.

Click the Refresh button in the bottom right-hand corner of the environment card.

957

Delphix User Guide 2016 Delphix

Provision the Oracle Database

1. Provision the EBS database to the target dbTier environment by following the steps outlined in Provisioning an Oracle VDB.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

2.

Select the correct Installation Home.

This should be the virtual dbTechStack you just added to the Delphix Engine.

3.

Enter the SID same as whats provided to the virtual dbTechStack you just added to the Delphix Engine.

4. Click Advanced.
5. Select the correct Oracle Node Listeners value.
This should be the listener corresponding to the virtual dbTechStack you just added to the Delphix Engine.
6. Add the EBS R12.2 dbTier environment file as a Custom Environment Variables entry.
This file can be specified as an Environment File with Path Parameters of $ORACLE_HOME/<CONTEXT_NAME>.env .
Replace <CONTEXT_NAME> with the virtual EBS instance's context name. The Delphix Engine will exapnd the $ORACLE_HOME variable
at runtime.
For more information, see Customizing Oracle VDB Environment Variables.
7.

Add a Run Bash Shell Command operation to the Configure Clone hook to ensure that adcfgclone is run
against the newly provisioned database. Typically, this operation will look similar to the script below.
# NOTE: Ensure the below environment variables will be set up correctly by the
shell. If not, hardcode or generate the values below.
# CONTEXT_NAME=${ORACLE_SID}_$(hostname -s)
# APPS_PASSWD=<passwd>
. ${ORACLE_HOME}/${CONTEXT_NAME}.env
sqlplus "/ as sysdba" <<EOF
@${ORACLE_HOME}/appsutil/install/${CONTEXT_NAME}/adupdlib.sql so
EOF
perl ${ORACLE_HOME}/appsutil/clone/bin/adcfgclone.pl dbconfig
${ORACLE_HOME}/appsutil/${CONTEXT_NAME}.xml <<EOF
${APPS_PASSWD}
EOF

8. Set up a Pre-Snapshot hook Run Bash Shell Command operation to run any pre-clone steps necessary and specific to your EBS
database. Normally, these steps will include running Oracle's adpreclone tool. Below is an example of a simple Run Bash Shell
Command hook operation:

# NOTE: Ensure the below environment variables will be set up correctly by the
shell. If not, hardcode or generate the values below.
# CONTEXT_NAME=${ORACLE_SID}_$(hostname -s)
# APPS_PASSWD=<passwd>
. ${ORACLE_HOME}/${CONTEXT_NAME}.env
perl ${ORACLE_HOME}/appsutil/scripts/${CONTEXT_NAME}/adpreclone.pl database <<-EOF
${APPS_PASSWD}
EOF

Provision the EBS appsTier

958

Delphix User Guide 2016 Delphix

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select My Databases.
4.

Select the appsTier dSource.

5.

Select a dSource snapshot.

All snapshots will have staged configuration prepared by adpreclone.pl and any hook operations placed
on the dSource.

6. Click Provision.
The Provision vFiles wizard will open.
7. Select an Environment.
This environment will host the virtual appsTier and be used to execute hook operations specified in a few steps. This environment will
also run the WebLogic Admin server (Web Administration service) for the virtual appsTier.
If you are provisioning a multi-node appsTier, you will be able to specify additional environments to host the virtual appsTier in a few
steps.
8. Select an Environment User.
This user should be the applmgr user outlined in Preparing Target EBS R12.2 Environments for Provisioning.
9. Enter a Mount Path for the virtual appsTier files.
If you are provisioning a multi-node appsTier, this mount path will be used across all target environments.
10. Enter the EBS-specific parameters for the virtual appsTier. A subset of these parameters are discussed in more detail below.
a. Ensure that the Target Application Hostname and Target DB Server Node values are the short hostnames, not the
fully-qualified hostnames.
b. The APPS Password is required to configure and manage the virtual appsTier.
This password is encrypted when stored within the Delphix Engine and is available as an environment variable to the adcfgclo
ne, adstrtal, and adstpall processes.
c. Enable the Cleanup Before Provision option if you want to permit the Delphix Engine to automatically cleanup stale EBS
configuration during a refresh. This option is recommended, but only available if your Oracle Home is patched with Oracle
Universal Installer (OUI) version 10.2 or above.
i. With this option enabled, the Delphix Engine will inspect the target environment's oraInventory prior to refreshing this
virtual appsTier. If any Oracle Homes are already registered within the specified Mount Path, the Delphix Engine will
detach them from the inventory prior to running adcfgclone. These homes must be detached prior to running
post-clone configuration, or else adcfgclone will fail, citing conflicting oraInventory entries as an issue. The Delphix
Engine will also remove any conflicting INST_TOP directories left on the environment. Non-conflicting INST_TOP
directories will not be modified.
ii. Without this option enabled, Oracle Homes or INST_TOP directories found to conflict with the specified Mount Path or
desired INST_TOP location will be reported in errors instead of automatically cleaned up. For refresh to succeed,
conflicting Oracle Homes must be manually detached and conflicting INST_TOP directories must be manually removed
prior to refresh.
d. Delphix recommends specifying an Instance Home Directory under the Mount Path so that instance-specific EBS files live on
Delphix-provided storage.
For example, if the provided Mount Path is /u01/oracle/VIS, then providing an Instance Home Directory of /u01/oracle
/VIS would allow EBS to generate virtual application INST_TOP in /u01/oracle/VIS/fs1/inst/apps/<CONTEXT_NAME >
and /u01/oracle/VIS/fs2/inst/apps/<CONTEXT_NAME > .
i. If you are provisioning a single-node appsTier, this recommendation is OPTIONAL; putting instance-specific EBS files
on Delphix-provided storage merely eases administration of the virtual EBS instance.
ii. If you are provisioning a multi-node appsTier, this recommendation is REQUIRED; the Delphix Engine's automation
requires that all nodes in the appsTier have access to instance-specific files via Delphix-provided storage.
e. If you are provisioning a multi-node appsTier, enter additional appsTier nodes as Additional Nodes.
i. The Environment User for each node should be the applmgr user outlined in Preparing Target EBS R12.2
Environments for Provisioning.
ii. Ensure that the Hostname value for each node is the short hostname, not the fully-qualified hostname.
iii. The Mount Path is not configurable for each node individually. The Mount Path provided for the primary environment
will be used for each additional node.
11. Click Next.
12.

Enter a vFiles Name.

13.

Select a Target Group for the vFiles.

If necessary, click the green Plus icon to add a new group.

14.

Select a Snapshot Policy for the vFiles.

If necessary, click the green Plus icon to create a new policy.

959

Delphix User Guide 2016 Delphix

14.

EBS SnapSync Conflicts

When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

15.

Click Next.

16.

Enter any custom hook operations that are needed to help correctly manage the virtual appsTier.
For more information about these hooks, when they are run, and how operations are written, see Customizin
g Unstructured Files with Hook Operations.
The Configure Clone hook will be run after the adcfgclone.pl tool has both mounted and configured the
appsTier.
All hook operations run against the environment specified for provision. For a multi-node appsTier, hook
operations never run against additional nodes specified.

17. Click Next.

18. Click Finish.
dbTier Must Be Accessible During appsTier Provisioning
Post-clone configuration will fail if the appsTier cannot connect to the database. Ensure the target dbTier is accessible to the
appsTier during the provisioning process. Ensure both the virtual database and database listener are running.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the appsTier vFiles will be included in the group you designated and listed in the Databases panel. If you
select the appsTier vFiles in the Databases panel and click the Open icon, you can view its card, which contains information about the
virtual files and its Data Management settings.
19. For tips on monitoring the progress of appsTier provisioning, see Monitoring EBS R12.2 appsTier Provisioning Progress.
Once all three EBS virtual datasets have been provisioned successfully, your virtual EBS instance should be running and accessible.

Related Links
Linking a Source EBS R12.2 Instance
Preparing Target EBS R12.2 Environments for Provisioning
Customizing Unstructured Files with Hook Operations
Monitoring EBS R12.2 dbTechStack Provisioning Progress
Provisioning an Oracle VDB
Customizing Oracle VDB Environment Variables
Customizing Unstructured Files with Hook Operations
Monitoring EBS R12.2 appsTier Provisioning Progress

960

Delphix User Guide 2016 Delphix

Monitoring EBS R12.2 dbTechStack Provisioning Progress

This topic describes how to monitor the progress of EBS R12.2 dbTechStack provisioning.
The Delphix Engine automates the configuration of the dbTechStack during provisioning. It spends the majority of provisioning time running
RapidClone utilities such as adcfgclone. The Delphix Engine does not report the progress of RapidClone utilities through the progress of the D
B_Provision job. To track provisioning progress more accurately, Delphix recommends monitoring EBS log files generated on the target dbTier
environment.

Procedure
1. Connect to the target dbTier environment using SSH or an alternative utility.
2. Change directories to the <ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/.
Replace <ORACLE_HOME> with the path to the dbTechStack's Oracle Home. This path will be under the mount path specified
during provisioning.
Replace <CONTEXT_NAME> with the virtual EBS instance's context name.
3. After adcfgclone has begun running, a file matching ApplyDBTechStack_*.log will exist. Identify this log file and use tail or an
equivalent utility to monitor it.

Leave the Mount Point Prior to Refresh

If provisioning fails, you will need to fix the cause of the failure and perform a refresh of the dataset before you can attempt
configuration again. Prior to refreshing or disabling the dataset, be sure to change directories to a location outside of the mount path on
the target environment. If you leave a shell session with a current working directory inside the mount path, the dataset will fail to
unmount cleanly during refresh or disable.

Related Links
Monitoring EBS R12.2 appsTier Provisioning Progress

961

Delphix User Guide 2016 Delphix

Monitoring EBS R12.2 appsTier Provisioning Progress

This topic describes how to monitor the progress of EBS R12.2 appsTier provisioning.
The Delphix Engine automates the configuration of the appsTier during provisioning. It spends the majority of provisioning time running
RapidClone utilities such as adcfgclone. The Delphix Engine does not report the progress of RapidClone utilities through the progress of the D
B_Provision job. To track provisioning progress more accurately, Delphix recommends monitoring EBS log files generated on the target appsTier
environment.

Procedure
1. Connect to the target appsTier environment using SSH or an alternative utility.
2. Change directories to the <INST_TOP>/admin/log/.
Replace <INST_TOP> with the value of INST_TOP on the virtual EBS instance.
3. After adcfgclone has begun running, a file matching ApplyAppsTier_*.log will exist. Identify this log file and use tail or an
equivalent utility to monitor it.

Leave the Mount Point Prior to Refresh

If provisioning fails, you will need to fix the cause of the failure and perform a refresh of the dataset before you can attempt
configuration again. Prior to refreshing or disabling the dataset, be sure to change directories to a location outside of the mount path on
the target environment. If you leave a shell session with a current working directory inside the mount path, the dataset will fail to
unmount cleanly during refresh or disable.

Related Links
Monitoring EBS R12.2 dbTechStack Provisioning Progress

962

Delphix User Guide 2016 Delphix

Oracle EBS R12.1

This section describes linking and provisioning Oracle Enterprise Business Suite R12.1.
Source EBS R12.1 Instance Requirements
Virtual EBS R12.1 Instance Requirements
Preparing a Source EBS R12.1 Instance for Linking
Linking a Source EBS R12.1 Instance
Preparing Target EBS R12.1 Environments for Provisioning
Provisioning a Virtual EBS R12.1 Instance
Monitoring EBS R12.1 dbTechStack Provisioning Progress
Monitoring EBS R12.1 appsTier Provisioning Progress

963

Delphix User Guide 2016 Delphix

Source EBS R12.1 Instance Requirements

Operating Systems
dbTier Requirements
Supported Topologies
appsTier Requirements
Supported Topologies
Caveats
Related Links
The Delphix Engine supports linking a variety of versions and configurations of Oracle Enterprise Business Suite R12.1. Below, detailed
compatibility notes are outlined.
Note that minor releases of EBS are not certified for Delphix Engine compatibility individually; major release support implies support for any minor
release.
To review the requirements for provisioning a virtual EBS R12.1 instance from the Delphix Engine, see Virtual EBS R12.1 Instance
Requirements.

Operating Systems
Linux
Solaris
AIX and HP-UX Not Supported
The Delphix Engine does not support linking EBS instances running on AIX or HP-UX.

dbTier Requirements
Supported Topologies
Oracle SI dbTechStack and Database
Oracle RAC dbTechStack and Database

appsTier Requirements
Supported Topologies
Single-node appsTier
Multi-node appsTier with a shared APPL_TOP
Non-shared APPL_TOP Not Supported
The Delphix Engine does not provide support for linking a multi-node appsTier where the APPL_TOP is not shared between nodes.

Caveats
The Delphix Engine does not provide support for linking an EBS R12.1 instance utilizing custom context variables that is, custom variables
maintained in the EBS context file.

Related Links
Virtual EBS R12.1 Instance Requirements

964

Delphix User Guide 2016 Delphix

Virtual EBS R12.1 Instance Requirements

Operating Systems
dbTier Requirements
Supported Topologies
appsTier Requirements
Supported Topologies
Related Links
The Delphix Engine supports provisioning a variety of versions and configurations of Oracle Enterprise Business Suite R12.1. Below, detailed
compatibility notes are outlined.
Note that minor releases of EBS are not certified for Delphix Engine compatibility individually: major release support implies support for any minor
release.
To review the requirements for linking an EBS R12.1 instance to the Delphix Engine, see Source EBS R12.1 Instance Requirements.

Operating Systems
Linux
Solaris
AIX and HP-UX Not Supported
The Delphix Engine does not support provisioning EBS instances to AIX or HP-UX.

dbTier Requirements
Supported Topologies
Oracle SI dbTechStack and Database
Oracle RAC Not Supported
The Delphix Engine does not support provisioning Oracle RAC dbTechStack for use with Oracle Enterprise Business Suite.
However, you can provision an Oracle SI dbTier from a linked EBS instance with an Oracle RAC dbTier. During the provisioning
process, the Delphix Engine will relink the dbTechStack for use with an Oracle SI database and scale down the Oracle RAC database
to an Oracle SI database.

appsTier Requirements
Supported Topologies
Single-node appsTier
Multi-node appsTier with a shared APPL_TOP
Non-shared APPL_TOP Not Supported
The Delphix Engine does not provide support for provisioning a multi-node appsTier where the APPL_TOP is not shared between
nodes.

appsTier Topology Is Configurable

The appsTier topology of the virtual EBS instance does NOT need to match the appsTier topology of the source EBS instance. The
Delphix Engine will automate scale up or scale down logic as required during provisioning.

Related Links
Preparing a Source EBS R12.1 Instance for Linking

965

Delphix User Guide 2016 Delphix

Preparing a Source EBS R12.1 Instance for Linking

This topic outlines the prerequisites for linking an EBS R12.1 instance to the Delphix Engine.
Ensure your EBS R12.1 instance is supported
Prepare the dbTier for linking
Delphix Engine's Unix Environment Requirements
oracle User
dbTechStack Binary Permissions
Cleanup Before Provisioning Option
Special Considerations for Upgraded 11gR2 Database
Delphix Engine's Oracle Database Requirements
Prepare the appsTier for Linking
Delphix Engine's Unix Environment Requirements
applmgr User
Clean Up Before Provisioning Option
Related Links

Ensure your EBS R12.1 instance is supported

See Source EBS R12.1 Instance Requirements to ensure you can link your EBS R12.1 instance to the Delphix Engine.

Prepare the dbTier for linking

Delphix Engine's Unix Environment Requirements
The dbTier must meet the source requirements outlined in Requirements for Unix Environments. These requirements are generic to all source
Unix environments added to the Delphix Engine.

oracle User
The Delphix Engine must have access to an oracle user on the dbTier.
This user should be a member of both the EBS dba and oinstall groups.
The user should have read permissions on all dbTechStack and database files that will be cloned.

dbTechStack Binary Permissions

Verify that the oracle user described above has read permissions at the group level for:
$ORACLE_HOME/bin/nmb
$ORACLE_HOME/bin/nmhs
$ORACLE_HOME/bin/nmo

Cleanup Before Provisioning Option

If you plan to utilize the Cleanup Before Provision option available during dbTechStack provisioning, the Delphix Engine requires the Database
Oracle Home to be patched with Oracle Universal Installer (OUI) version 10.2 or above. You can read more about this provisioning option in Provi
sioning a Virtual EBS R12.1 Instance.
Note that provisioning is still possible without this option enabled, but you will need to manage the target dbTier's Oracle Inventory manually to
ensure that conflicting entries do not cause provisions to fail.

Special Considerations for Upgraded 11gR2 Database

If the database for the EBS R12.1 instance has been upgraded to 11gR2 from previous versions, please follow the workaround procedures in
Oracle Support document Doc ID 1333997.1 to update PERL5LIB variable in database context file if applicable. Failure to follow these
workaround procedures may result in errors during the dbTier linking and provisioning process.

966

Delphix User Guide 2016 Delphix

Delphix Engine's Oracle Database Requirements

The dbTier must meet the source requirements outlined in Oracle Support and Requirements. These requirements are generic to all Unix
environments containing an Oracle database to be linked.

Prepare the appsTier for Linking

Delphix Engine's Unix Environment Requirements
The appsTier must meet the source requirements outlined in Requirements for Unix Environments. These requirements are generic to all
source Unix environments added to the Delphix Engine.

applmgr User
The Delphix Engine must have access to an applmgr user on the appsTier.
This user should be a member of the EBS oinstall group.
The user should have read permissions on all appsTier files that will be cloned.

Clean Up Before Provisioning Option

If you plan to utilize the Cleanup Before Provision option available during appsTier provisioning, the Delphix Engine requires the Web Oracle
Home to be patched with Oracle Universal Installer (OUI) version 10.2 or above. You can read more about this provisioning option in Provisionin
g a Virtual EBS R12.1 Instance.
Note that provisioning is still possible without this option enabled, but you will need to manage the target appTier's Oracle Inventory manually to
ensure that conflicting entries do not cause provisions to fail.

Related Links
Source EBS R12.1 Instance Requirements
Requirements for Unix Environments
Provisioning a Virtual EBS R12.1 Instance
Oracle Support and Requirements

967

Delphix User Guide 2016 Delphix

Linking a Source EBS R12.1 Instance

This topic describes the process of linking an EBS R12.1 instance and creating the necessary dSources.

Prerequisites
Prepare your source EBS R12.1 instance for linking by following the outline in Preparing a Source EBS R12.1 Instance for Linking.

Procedure
Link the Oracle Database
1.

Link the Oracle database used by EBS as outlined in Linking an Oracle Data Source.

Link the EBS dbTechStack

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4.

Select the source dbTier environment containing the source dbTechStack.

If you have not already added the environment, see the Managing Unix Environments topics for more
information about adding environments.
Linking from RAC dbTier
If you are linking from a RAC dbTier, select the environment for a single running node of the RAC cluster.

5.

Click the Environment Details tab.

6.

If the oracle environment user described in Preparing a Source EBS R12.1 Instance for Linking is not
already added to the Delphix Engine, add the user.
For more information about adding environment users, see the Managing Unix Environment Users topics.

7.

Click the Databases tab.

8.

Click the Plus icon next to Add Dataset Home.

Adding the files as a dataset home will register the type and location of the files with the Delphix Engine.

9.

For your Dataset Home Type , select E-Business Suite R12.1 dbTechStack.
When you select this type of dataset home, the Delphix Engine will know to automate pre-clone logic.
Specifically, adpreclone.pl dbTier will be run prior to every SnapSync of the dbTechStack. During
dSource creation, you will be able to enter additional pre-clone steps as Pre-Sync hook operations.

10.

Enter an Installation Home.

This path should be the Oracle base install directory. For example, if the value of $ORACLE_HOME on your
source environment is /u01/oracle/VIS/db/tech_st/11.1.0, the Oracle base install directory is /u01
/oracle/VIS.

11. Click the Confirm icon to save your dataset home.

If necessary, scroll down the list of dataset homes to view and edit this dataset home.
12.

Click Manage.

13.

Select Add dSource.

14.

In the Add dSource wizard, select the dbTechStack files source you just created.

15.

Enter the EBS-specific parameters for your dbTechStack.

These parameter values will be used when adpreclone.pl is run.
Ensure that the DB Tier Context Name uses the short hostname.

16.
968

Delphix User Guide 2016 Delphix

16.

Click Advanced.

17.

Exclude the EBS database's data files if they are stored underneath the Oracle base install directory.
These data files will be linked with the database i nstead of with the dbTechStack . Add the relative path to the data files to the Paths to
Exclude list.

18.

Click Next.

19.

Enter a dSource Name.

20.

Select a Database Group for the dSource.

21.

Click Next.
Adding a dSource to a database group enables the ability for you to set Delphix Domain user permissions for
that dSource's objects, such as snapshots. For more information, see the topics under Users, Permissions,
and Policies.

22.

Select a SnapSync policy.

23.

Click Next.

24.

Enter any custom pre- or post-sync logic as Pre-Sync or Post-Sync hook operations.
Remember that adpreclone.pl dbTier is already run prior to every SnapSync of the dbTechStack.
The Pre-Sync hook operations will be run prior to running the adpreclone.pl tool.
For more information, see Customizing Unstructured Files with Hook Operations.

25.

Click Next.

26.

Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync . You can monitor these
jobs by clicking Active Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs
have completed successfully, the files icon will change to a dSource icon on the Environments > Database
s screen, and the dSource will be added to the list of My Databases under its assigned group.

Link the EBS appsTier

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select Environments.
4. Select the source appsTier environment.
If you have not already added the environment, see the Managing Unix Environments topics for more information how to do so.
Linking from multi-node appsTier
If you are linking from a multi-node appsTier, select the environment for the node on which EBS admin services reside.

5. Click the Environment Details tab.

6. If the applmgr environment user described in Preparing a Source EBS R12.1 Instance for Linking is not already added to the
Delphix Engine, add the user.
For more information about adding environment users, see the Managing Unix Environment Users topics.
7. Click the Databases tab.
8. Click the Plus icon next to Add Dataset Home.
Adding the files as a dataset home will register the type and location of the files with the Delphix Engine.
9. For your Dataset Home Type, select E-Business Suite R12.1 appsTier.
When you select this type of dataset home, the Delphix Engine will know to automate pre-clone logic. Specifically, the Delphix Engine will
run adpreclone.pl appsTier prior to every SnapSync of the appsTier. During dSource creation, you will be able to enter additional
pre-clone steps as Pre-Sync hook operations.
10. Enter an Installation Home.
This path should be the Oracle base install directory. For example, if the value of $APPL_TOP on your source environment is /u01/orac
le/VIS/apps/apps_st/appl, the Oracle base install directory is /u01/oracle/VIS.
11. Click the Confirm icon to save your dataset home.
If necessary, scroll down the list of dataset homes to view and edit this dataset home.
12. Click Manage.
13.
969

Delphix User Guide 2016 Delphix

13. Select Databases.

14. Select Add dSource.
15. In the Add dSource wizard, select the appsTier files source you just created.
16. Enter the EBS-specific parameters for your appsTier.
These parameter values will be used when adpreclone.pl is run.
Ensure that the Instance Home Directory specifies an absolute path.
17. Click Next.
18. Enter a dSource Name.
19. Select a Database Group for the dSource.
20. Click Next.
Adding a dSource to a database group enables you to set Delphix Domain user permissions for that dSource's objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies.
21. Click Next.
22. Select a SnapSync policy.
23. Click Next.
24. Enter any custom pre- or post-sync logic as Pre-Sync or Post-Sync hook operations.
Remember that adpreclone.pl appsTier is already run prior to every SnapSync of the appsTier.
The Pre-Sync hook operations will be run prior to running the adpreclone.pl tool.
For more information, see Customizing Unstructured Files with Hook Operations.
25. Click Next.
26. Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the files icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

Related Links
Preparing a Source EBS R12.1 Instance for Linking
Linking an Oracle Data Source
Managing Unix Environments
Preparing a Source EBS R12.1 Instance for Linking
Managing Unix Environment Users
Users, Permissions, and Policies
Customizing Unstructured Files with Hook Operations

970

Delphix User Guide 2016 Delphix

Preparing Target EBS R12.1 Environments for Provisioning

This topic outlines the prerequisites for provisioning a virtual EBS R12.1 instance to target environments.
Ensure your target EBS R12.1 instance is supported
Prepare the dbTier for provisioning
Delphix Engine's Unix Environment Requirements
oracle User
oraInst.loc
Delphix Engine's Oracle Database Requirements
Prepare the appsTier for Provisioning
Delphix Engine's Unix Environment Requirements
applmgr User
oraInst.loc
Related Links

Ensure your target EBS R12.1 instance is supported

See Virtual EBS R12.1 Instance Requirements to ensure that you can provision your EBS R12.1 instance.

Prepare the dbTier for provisioning

Delphix Engine's Unix Environment Requirements
The dbTier must meet the target requirements outlined in Requirements for Unix Environments. These requirements are generic to all target
Unix environments added to the Delphix Engine.

oracle User
The Delphix Engine must have access to an oracle user on the dbTier.
This user should be a member of both the EBS dba and oinstall groups.
This user will be given proper permissions to manage the dbTechStack and database.

oraInst.loc
An oraInst.loc file must exist on the dbTier prior to provisioning. This file will specify where the oraInventory directories live or where they should
be created if they do not already exist.
The oraInst.loc file is typically located at /etc/oraInst.loc on Linux or /var/opt/oracle/oraInst.loc on Solaris. Ensure that the
oraInventory to which this file points is writeable by the oracle user.
Consult Oracle EBS documentation for more information about where to place this file on your dbTier and what this file should contain.

Delphix Engine's Oracle Database Requirements

The dbTier must meet the target requirements outlined in Oracle Support and Requirements. These requirements are generic to all target Unix
environments expected to host a virtual Oracle database.

Prepare the appsTier for Provisioning

Delphix Engine's Unix Environment Requirements
The appsTier must meet the target requirements outlined in Requirements for Unix Environments. These requirements are generic to all target
Unix environments added to the Delphix Engine.

applmgr User

971

Delphix User Guide 2016 Delphix

The Delphix Engine must have access to an applmgr user on the appsTier.
This user should be a member of the EBS oinstall group.
This user will be given proper permissions to manage the appsTier.

oraInst.loc
An oraInst.loc file must exist on every appsTier node prior to provisioning. This file will specify where the oraInventory directories live or where
they should be created if they do not already exist.
The oraInst.loc file is typically located at /etc/oraInst.loc on Linux or /var/opt/oracle/oraInst.loc on Solaris. Ensure the
oraInventory to which this file points is writeable by the applmgr user.
Delphix recommends that this file specify an oraInventory location under the virtual appsTier mount path.
If you are provisioning a single-node appsTier, this recommendation is OPTIONAL; putting the oraInventory directories on
Delphix-provided storage merely eases administration of the virtual EBS instance.
If you are provisioning a multi-node appsTier, this recommendation is REQUIRED; the Delphix Engine's automation requires that all
nodes in the appsTier have access to the oraInventory directories via Delphix-provided storage.
Consult Oracle EBS documentation for more information about where to place this file on your appsTier and what this file should contain.

Related Links
Virtual EBS R12.1 Instance Requirements
Requirements for Unix Environments
Oracle Support and Requirements
Requirements for Unix Environments

972

Delphix User Guide 2016 Delphix

Provisioning a Virtual EBS R12.1 Instance

This topic describes the process of provisioning a virtual EBS R12.1 instance.

Prerequisites
You must have already linked a source instance of EBS R12.1. For more information, see Linking a Source EBS R12.1 Instance.
Prepare your target EBS R12.1 environments for provisioning by following the outline in Preparing Target EBS R12.1 Environments for
Provisioning.
Snapshot Coordination
Changes applied to EBS and picked up only in certain dSource snapshots may make certain combinations of snapshots across the
appsTier and dbTier incompatible. When provisioning, refreshing, or rewinding a virtual EBS instance, be sure the points in time you
select for each dataset are compatible with each other.

Procedure
Provision the EBS dbTechStack
1.

Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select My Databases.
4.

Select the dbTechStack dSource.

5.

Select a dSource snapshot.

All snapshots will have staged configuration prepared by adpreclone.pl and any hook operations placed
on the dSource.

6.

Click Provision.
The Provision vFiles wizard will open.

7.

Select an Environment.
This environment will host the virtual dbTechStack and be used to execute hook operations specified in a few
steps.

8.

Select an Environment User.

This user should be the oracle user outlined in Preparing Target EBS R12.1 Environments for
Provisioning.

9.

Enter a Mount Path for the virtual dbTechStack files.

10.

Enter the EBS-specific parameters for the virtual dbTechStack. A subset of these parameters are discussed
in more detail below.
a. Ensure that the Target DB Hostname value is the short hostname, not the fully-qualified hostname.
b. The APPS Password is required to configure the virtual dbTechStack.
This password is encrypted when stored within the Delphix Engine and is available as an environment variable to the adcfgclo
ne process.
c. Enable the Disable RAC option if you want to permit the Delphix Engine to automatically disable the RAC option for the binaries
when applicable.
This option is necessary if provisioning from a dSource with a RAC dbTier, because the binaries are relinked with the rac_on op
tion even after running adcfgclone. If the source binaries already have the RAC option disabled (also the case for SI dbTier),
the Delphix Engine ignores this option.
d. Enable the Cleanup Before Provision option if you want to permit the Delphix Engine to automatically cleanup stale EBS
configuration during a refresh. This option is recommended, but only available if your Oracle Home is patched with Oracle
Universal Installer (OUI) version 10.2 or above.
i. With this option enabled, the Delphix Engine will inspect the target environment's oraInventory prior to refreshing this
virtual dbTechStack. If any Oracle Homes are already registered within the specified Mount Path, the Delphix Engine
will detach them from the inventory prior to running adcfgclone. These homes must be detached prior to running
post-clone configuration, or else adcfgclone will fail, citing conflicting oraInventory entries as an issue.
ii. Without this option specified, Oracle Homes found to conflict with the specified Mount Path will be reported in an error

973

Delphix User Guide 2016 Delphix

ii.
instead of automatically detached. For refresh to succeed, conflicting Oracle Homes must be manually detached prior to
refresh.
11. Click Next.
12. Enter a vFiles Name.
13.

Select a Target Group for the vFiles.

If necessary, click the green Plus icon to add a new group.

14.

Select a Snapshot Policy for the vFiles.

If necessary, click the green Plus icon to create a new policy.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

15.

Click Next.

16.

Enter any custom hook operations that are needed to help correctly manage the virtual dbTechStack files.
For more information about these hooks, when they are run, and how operations are written, see Customizin
g Unstructured Files with Hook Operations.
The Configure Clone hook will be run after the adcfgclone.pl tool has both mounted and configured the
dbTechStack.

17. Click Next.

18. Click Finish.

When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History p
anel of the Dashboard. When provisioning is complete, the dbTechStack vFiles will be included in the group
you designated and listed in the Databases panel. If you select the dbTechStack vFiles in the Databases pa
nel and click the Open icon, you can view its card, which contains information about the virtual files and its
Data Management settings.
19. See Monitoring EBS R12.1 dbTechStack Provisioning Progress for tips for monitoring the progress of dbTechStack provisioning.

Register the EBS dbTechStack

Register the freshly-provisioned dbTechStack with the Delphix Engine.
1.

Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Environments.
4.

Select the target dbTier environment.

5.

Click the Databases tab.

6.

Click the Plus icon next to Add Dataset Home.

7.

For your Dataset Home Type, select Oracle.

8.

Enter an Installation Home.

This path should be the value of $ORACLE_HOME on your target dbTier; this path will live under the mount
path specified when you provisioned the virtual dbTechStack.
Commonly, this path looks like /u01/oracle/VIS/db/tech_st/11.1.0.

9. Click the Confirm icon to save your dataset home.

If necessary, scroll down the list of dataset homes to view and edit this dataset home.
10.

Refresh the target dbTier environment.

Refreshing the environment will discover the EBS database listener and ensure that it is available for

974

Delphix User Guide 2016 Delphix

10.

selection when provisioning the EBS database.

a.

Click the Refresh button in the bottom right-hand corner of the environment card.

Provision the Oracle Database

1. Provision the EBS database to the target dbTier environment by following the steps outlined in Provisioning an Oracle VDB.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

2.

Select the correct Installation Home.

This selection should be the virtual dbTechStack you just added to the Delphix Engine.

3.

Enter the SID. This should be the same as what is provided to the virtual dbTechStack you just added to the
Delphix Engine.

4.

Click Advanced.

5.

Select the correct Oracle Node Listeners value.

This selection should be the listener corresponding to the virtual dbTechStack you just added to the Delphix
Engine.

6. Add the EBS R12.1 dbTier environment file as a Custom

Environment Variables entry.

$ORACLE_HOME/<CONTEXT_NAME>.env .
Replace <CONTEXT_NAME> with the virtual EBS instance's context name. The Delphix Engine will expand the $ORACLE_HOME v
This file can be specified as an Environment File with Path Parameters of
ariable at runtime.
For more information, see Customizing Oracle VDB Environment Variables .

7.

Add a Run Bash Shell Command operation to the Configure Clone hook to ensure that adcfgclone is run
against the newly provisioned database. Typically, this operation will look similar to the script below.
# NOTE: Ensure the below environment variables will be set up correctly by the
shell. If not, hardcode or generate the values below.
# CONTEXT_NAME=${ORACLE_SID}_$(hostname -s)
# APPS_PASSWD=<passwd>
. ${ORACLE_HOME}/${CONTEXT_NAME}.env
sqlplus "/ as sysdba" <<EOF
@${ORACLE_HOME}/appsutil/install/${CONTEXT_NAME}/adupdlib.sql so
EOF
perl ${ORACLE_HOME}/appsutil/clone/bin/adcfgclone.pl dbconfig
${ORACLE_HOME}/appsutil/${CONTEXT_NAME}.xml <<EOF
${APPS_PASSWD}
EOF

8. Set up a Pre-Snapshot hook Run Bash Shell Command operation to run any pre-clone steps necessary and specific to the virtual EBS
database. Normally, these steps will include running Oracle's adpreclone tool. Below is an example of a simple Run Bash Shell
Command hook operation:

975

Delphix User Guide 2016 Delphix

# NOTE: Ensure the below environment variables will be set up correctly by the
shell. If not, hardcode or generate the values below.
# CONTEXT_NAME=${ORACLE_SID}_$(hostname -s)
# APPS_PASSWD=<passwd>
. ${ORACLE_HOME}/${CONTEXT_NAME}.env
perl ${ORACLE_HOME}/appsutil/scripts/${CONTEXT_NAME}/adpreclone.pl database <<-EOF
${APPS_PASSWD}
EOF

Provision the EBS appsTier

1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3.

Select My Databases.

4.

Select the appsTier dSource.

5.

Select a dSource snapshot.

All snapshots will have staged configuration prepared by adpreclone.pl and any hook operations placed
on the dSource.

6.

Click Provision.
The Provision vFiles wizard will open.

7.

Select an Environment.
This environment will host the virtual appsTier and be used to execute hook operations specified in a few
steps.
If you are provisioning a multi-node appsTier, you will be able to specify additional environments to host the
virtual appsTier in a few steps.

8. Select an Environment

User.

9. Enter a Mount Path for the virtual appsTier files.

If you are provisioning a multi-node appsTier, this mount path will be used across all target environments.
10.

This user should be the applmgr user outlined in Preparing Target EBS R12.1 Environments for
Provisioning.

11.

Enter the EBS-specific parameters for the virtual appsTier. A subset of these parameters is discussed in
more detail below.
a. Ensure that the Target Application Hostname and Target DB Server Node values are the short
hostnames, not the fully-qualified hostnames.
b. The APPS Password is required to configure and manage the virtual appsTier.
This password is encrypted when stored within the Delphix Engine and is available as an environment variable to the adcfgclo
ne, adstrtal, and adstpall processes.
c. Enable the Cleanup Before Provision option if you want to permit the Delphix Engine to automatically cleanup stale EBS
configuration during a refresh. This option is recommended, but only available if your Oracle Home is patched with Oracle
Universal Installer (OUI) version 10.2 or above.
i. With this option enabled, the Delphix Engine will inspect the target environment's oraInventory prior to refreshing this
virtual appsTier. If any Oracle Homes are already registered within the specified Mount Path, the Delphix Engine will
detach them from the inventory prior to running adcfgclone. These homes must be detached prior to running
post-clone configuration, or else adcfgclone will fail, citing conflicting oraInventory entries as an issue. The Delphix
Engine will also remove any conflicting INST_TOP directories left on the environment. Non-conflicting INST_TOP
directories will not be modified.
ii. Without this option enabled, Oracle Homes or INST_TOP directories found to conflict with the specified Mount Path or
desired INST_TOP location will be reported in errors instead of being automatically cleaned up. For refresh to succeed,
conflicting Oracle Homes must be manually detached and conflicting INST_TOP directories must be manually removed
prior to refresh.
d. Delphix recommends specifying an Instance Home Directory under the Mount Path so that instance-specific EBS files live on
Delphix-provided storage.

976

Delphix User Guide 2016 Delphix

d.

For example, if the provided Mount Path is /u01/oracle/VIS, then providing an Instance Home Directory of /u01/oracle
/VIS/inst would allow EBS to generate virtual application INST_TOP in /u01/oracle/VIS/inst/apps/<CONTEXT_NAME>
.
i. If you are provisioning a single-node appsTier, this recommendation is OPTIONAL; putting instance-specific EBS files
on Delphix-provided storage merely eases administration of the virtual EBS instance.
ii. If you are provisioning a multi-node appsTier, this recommendation is REQUIRED; the Delphix Engine's automation
requires that all nodes in the appsTier have access to instance-specific files via Delphix-provided storage.
e. If you are provisioning a multi-node appsTier, enter additional appsTier nodes as Additional Nodes.
i. The Environment User for each node should be the applmgr user outlined in Preparing Target EBS R12.1
Environments for Provisioning.
ii. Ensure that the Hostname value for each node is the short hostname, not the fully-qualified hostname.
iii. The Mount Path is not configurable for each node individually. The Mount Path provided for the primary environment
will be used for each additional node.
12. Click Next.
13.

Enter a vFiles Name.

14.

Select a Target Group for the vFiles.

If necessary, click the green Plus icon to add a new group.

15.

Select a Snapshot Policy for the vFiles.

If necessary, click the green Plus icon to create a new policy.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

16.

Click Next.

17.

Enter any custom hook operations that are needed to help correctly manage the virtual appsTier.
For more information about these hooks, when they are run, and how operations are written, see Customizin
g Unstructured Files with Hook Operations.
The Configure Clone hook will be run after the adcfgclone.pl tool has both mounted and configured the
appsTier.
All hook operations run against the environment specified for provision. For a multi-node appsTier, hook
operations never run against additional nodes specified.

18. Click Next.

19. Click Finish.
dbTier Must Be Accessible During appsTier Provisioning
Post-clone configuration will fail if the appsTier cannot connect to the database. Ensure that the target dbTier is accessible to
the appsTier during the provisioning process. Ensure that both the database and the database listener are running.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard. Wh
en provisioning is complete, the appsTier vFiles will be included in the group you designated and listed in the Databases panel. If you
select the appsTier vFiles in the Databases panel and click the Open icon, you can view its card, which contains information about the
virtual files and its Data Management settings.
20. For tips on monitoring the progress of appsTier provisioning, see Monitoring EBS R12.1 appsTier Provisioning Progress .
Once all three EBS virtual datasets have been provisioned successfully, your virtual EBS instance should be running and accessible.

Related Links
Linking a Source EBS R12.1 Instance
Preparing Target EBS R12.1 Environments for Provisioning

977

Delphix User Guide 2016 Delphix

Customizing Unstructured Files with Hook Operations

Monitoring EBS R12.1 dbTechStack Provisioning Progress
Provisioning an Oracle VDB
Customizing Oracle VDB Environment Variables
Monitoring EBS R12.1 appsTier Provisioning Progress

978

Delphix User Guide 2016 Delphix

Monitoring EBS R12.1 dbTechStack Provisioning Progress

This topic describes how to monitor the progress of EBS R12.1 dbTechStack provisioning.
The Delphix Engine automates the configuration of the dbTechStack during provisioning. It spends the majority of provisioning time running
RapidClone utilities such as adcfgclone. The Delphix Engine does not report the progress of RapidClone utilities through the progress of the D
B_Provision job. To track provisioning progress more accurately, Delphix recommends monitoring EBS log files generated on the target dbTier
environment.

Procedure
1. Connect to the target dbTier environment using SSH or an alternative utility.
2. Change directories to the <ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/.
Replace <ORACLE_HOME> with the path to the dbTechStack's Oracle Home: this path will be under the mount path specified
during provisioning.
Replace <CONTEXT_NAME> with the virtual EBS instance's context name.
3. After adcfgclone has begun running, a file matching ApplyDBTechStack_*.log will exist. Identify this log file and use tail or an
equivalent utility to monitor it.

Leave the Mount Point Prior to Refresh

If provisioning fails, you will need to fix the cause of the failure and perform a refresh of the dataset before you can attempt
configuration again. Prior to refreshing or disabling the dataset, be sure to change directories to a location outside of the mount path on
the target environment. If you leave a shell session with a current working directory inside the mount path, the dataset will fail to
unmount cleanly during refresh or disable.

Related Links
Monitoring EBS R12.1 appsTier Provisioning Progress

979

Delphix User Guide 2016 Delphix

Monitoring EBS R12.1 appsTier Provisioning Progress

This topic describes how to monitor the progress of EBS R12.1 appsTier provisioning.
The Delphix Engine automates the configuration of the appsTier during provisioning. It spends the majority of provisioning time running
RapidClone utilities such as adcfgclone. The Delphix Engine does not report the progress of RapidClone utilities through the progress of the D
B_Provision job. To track provisioning progress more accurately, Delphix recommends monitoring EBS log files generated on the target appsTier
environment.

Procedure
1. Connect to the target appsTier environment using SSH or an alternative utility.
2. Change directories to the <INST_TOP>/admin/log/.
Replace <INST_TOP> with the value of INST_TOP on the virtual EBS instance.
3. After adcfgclone has begun running, a file matching ApplyAppsTier_*.log will exist. Identify this log file and use tail or an
equivalent utility to monitor it.

Leave the Mount Point Prior to Refresh

If provisioning fails, you will need to fix the cause of the failure and perform a refresh of the dataset before you can attempt
configuration again. Prior to refreshing or disabling the dataset, be sure to change directories to a location outside of the mount path on
the target environment. If you leave a shell session with a current working directory inside the mount path, the dataset will fail to
unmount cleanly during refresh or disable.

Related Links
Monitoring EBS R12.1 dbTechStack Provisioning Progress

980

Delphix User Guide 2016 Delphix

Oracle EBS 11i

This section describes linking and provisioning Oracle Enterprise Business Suite 11i.
Source EBS 11i Instance Requirements
Virtual EBS 11i Instance Requirements
Preparing a Source EBS 11i Instance for Linking
Linking a Source EBS 11i Instance
Preparing Target EBS 11i Environments for Provisioning
Provisioning a Virtual EBS 11i Instance
Monitoring EBS 11i dbTechStack Provisioning Progress
Monitoring EBS 11i appsTier Provisioning Progress

981

Delphix User Guide 2016 Delphix

Source EBS 11i Instance Requirements

The Delphix Engine supports linking a variety of versions and configurations of Oracle Enterprise Business Suite 11i. Below, detailed compatibility
notes are outlined.
Note that minor releases of EBS are not certified for Delphix Engine compatibility individually: major release support implies support for any minor
release.
See Virtual EBS 11i Instance Requirements for the requirements for provisioning a virtual EBS 11i instance from the Delphix Engine.
Oracle Enterprise Business Suite 11i
Operating Systems
dbTier Requirements
Supported Topologies
Supported Oracle Database Versions
appsTier Requirements
Supported Topologies
Caveats

Oracle Enterprise Business Suite 11i

Operating Systems
Linux (32-bit or 64-bit)
Solaris (32-bit or 64-bit)
AIX and HP-UX Not Supported
The Delphix Engine does not support linking EBS instances running on AIX or HP-UX.

dbTier Requirements
Supported Topologies
Oracle SI dbTechStack and Database
Oracle RAC Not Supported
The Delphix Engine does not support linking EBS 11i instances with an Oracle RAC database.

Supported Oracle Database Versions

The EBS database must be patched to version 9.2.0.8 or greater. The Delphix Engine does not support Oracle databases patched below
this version.

appsTier Requirements
Supported Topologies
Single-node appsTier
Multi-node appsTier Not Supported
The Delphix Engine does not support linking EBS 11i instances with a multi-node appsTier.

Caveats
The Delphix Engine does not provide support for linking an EBS 11i instance utilizing custom context variables (custom variables
maintained in the EBS context file).

982

Delphix User Guide 2016 Delphix

Virtual EBS 11i Instance Requirements

The Delphix Engine supports provisioning a variety of versions and configurations of Oracle Enterprise Business Suite 11i. Below, detailed
compatibility notes are outlined.
Note that minor releases of EBS are not certified for Delphix Engine compatibility individually: major release support implies support for any minor
release.
See Source EBS 11i Instance Requirements for the requirements for linking an EBS 11i instance to the Delphix Engine.
Oracle Enterprise Business Suite 11i
Operating Systems
dbTier Requirements
Supported Topologies
appsTier Requirements
Supported Topologies

Oracle Enterprise Business Suite 11i

Operating Systems
Linux (32-bit or 64-bit)
Solaris (32-bit or 64-bit)
AIX and HP-UX Not Supported
The Delphix Engine does not support provisioning EBS instances to AIX or HP-UX.

dbTier Requirements
Supported Topologies
Oracle SI dbTechStack and Database
Oracle RAC Not Supported
The Delphix Engine does not support provisioning Oracle RAC dbTechStack for use with Oracle Enterprise Business Suite.

appsTier Requirements
Supported Topologies
Single-node appsTier
Multi-node appsTier Not Supported
The Delphix Engine does not support provisioning EBS 11i instances with a multi-node appsTier.

983

Delphix User Guide 2016 Delphix

Preparing a Source EBS 11i Instance for Linking

This topic outlines the prerequisites for linking an EBS 11i instance to the Delphix Engine.
Ensure your EBS 11i instance is supported
Prepare the dbTier for linking
Delphix Engine's Unix Environment Requirements
oracle User
Clean Up Before Provisioning Option
Delphix Engine's Oracle Database Requirements
Prepare the appsTier for Linking
Delphix Engine's Unix Environment Requirements
applmgr User
Clean Up Before Provisioning Option

Ensure your EBS 11i instance is supported

See Source EBS 11i Instance Requirements to ensure you can link your EBS 11i instance to the Delphix Engine.

Prepare the dbTier for linking

Delphix Engine's Unix Environment Requirements
The dbTier must meet the source requirements outlined in Requirements for Unix Environments. These requirements are generic to all source
Unix environments added to the Delphix Engine.

oracle User
The Delphix Engine must have access to an oracle user on the dbTier. This user should be a member of both the EBS dba and oinstall grou
ps. The user should have read permissions on all dbTechStack and database files to be cloned.

Clean Up Before Provisioning Option

If you plan to utilize the Cleanup Before Provision option available during dbTechStack provisioning, the Delphix Engine requires the Database
Oracle Home be patched with Oracle Universal Installer (OUI) version 10.2 or above. You can read more about this provisioning option in Provisi
oning a Virtual EBS 11i Instance.
Note that provisioning is still possible without this option specified, but you will need to manage the target dbTier's Oracle Inventory manually to
ensure conflicting entries do not cause provisions to fail.

Delphix Engine's Oracle Database Requirements

The dbTier must meet the source requirements outlined in Oracle Support and Requirements. These requirements are generic to all Unix
environments containing an Oracle database to be linked.

Prepare the appsTier for Linking

Delphix Engine's Unix Environment Requirements
The appsTier must meet the source requirements outlined in Requirements for Unix Environments. These requirements are generic to all
source Unix environments added to the Delphix Engine.

applmgr User
The Delphix Engine must have access to an applmgr user on the appsTier. This user should be a member of the EBS oinstall group. The
user should have read permissions on all appsTier files to be cloned.

Clean Up Before Provisioning Option

984

Delphix User Guide 2016 Delphix

If you plan to utilize the Cleanup Before Provision option available during appsTier provisioning, the Delphix Engine requires the iAS Oracle
Home be patched with Oracle Universal Installer (OUI) version 10.2 or above. You can read more about this provisioning option in Provisioning a
Virtual EBS 11i Instance.
Note that provisioning is still possible without this option specified, but you will need to manage the target appTier's Oracle Inventory manually to
ensure conflicting entries do not cause provisions to fail.

985

Delphix User Guide 2016 Delphix

Linking a Source EBS 11i Instance

This topic describes the process of linking an EBS 11i instance and creating the necessary dSources.

Prerequisites
Prepare your source EBS 11i instance for linking by following the outline in Preparing a Source EBS 11i Instance for Linking.

Procedure
Link the Oracle Database

1.

Link the Oracle database used by EBS, as outlined in Linking an Oracle Data Source.

Link the EBS dbTechStack

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3.

Select Environments.

4.

Select the source dbTier environment containing the source dbTechStack.

If you have not already added the environment, see the Managing Unix Environments topics for more
information about adding environments.

5.

Click the Environment Details tab.

6.

If the oracle environment user described in Preparing a Source EBS 11i Instance for Linking is not
already added to the Delphix Engine, add the user.
For more information about adding environment users, see the Managing Unix Environment Users topics.

7.

Click the Databases tab.

8.

Click the Plus icon next to Add Dataset Home.

Adding the files as a dataset home will register the type and location of the files with the Delphix Engine.

9.

Select E-Business Suite 11i dbTechStack as your Dataset Home Type.

When you select this type of dataset home, the Delphix Engine will know to automate pre-clone logic.
Specifically, adpreclone.pl dbTier will be run prior to every SnapSync of the dbTechStack. During
dSource creation, you will be able to enter additional pre-clone steps as Pre-Sync hook operations.

10.

Enter an Installation Home.

This path should be the directory above $ORACLE_HOME on your source environment. Commonly, this path
looks like /u01/oracle/VIS.

11.

Click the Confirm icon to save your dataset home.

Scroll down the list of dataset homes to view and edit this dataset home if necessary.

12.

Click Manage.

13. Select Add

dSource.

14.

In the Add dSource wizard, select the dbTechStack files source you just created.

15.

Enter the EBS-specific parameters for your dbTechStack.

These parameter values will be used when adpreclone.pl is run.
Ensure the DB Tier Context Name uses the short hostname.

16.

Click Advanced.

17.

Exclude the EBS database's data files if they are stored underneath the Oracle base install directory.
These data files will be linked with the database instead of with the dbTechStack. Add the relative path to the data files to the Paths to
Exclude list.

18.

Click Next.

19.

Enter a dSource Name.

20.
986

Delphix User Guide 2016 Delphix

20. Select a Database Group for the dSource.

21. Click Next.

Adding a dSource to a database group enables you to set Delphix Domain user permissions for that
dSource's objects, such as snapshots. For more information, see the topics under Users, Permissions, and
Policies.
22. Select a SnapSync policy.
23. Click Next.
24.

Enter any custom pre or post sync logic as Pre-Sync or Post-Sync hook operations.
Remember that adpreclone.pl dbTier is already run prior to every SnapSync of the dbTechStack.
The Pre-Sync hook operations will be run prior to running the adpreclone.pl tool.
For more information, see Customizing Unstructured Files with Hook Operations.

25.

Click Next.

26.

Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync . You can monitor
these jobs by clicking Active Jobs in the top menu bar, or by selecting System > Event Viewer. When the
jobs have completed successfully, the files icon will change to a dSource icon on the Environments > Data
bases screen, and the dSource will be added to the list of My Databases under its assigned group.

Link the EBS appsTier

1. Login to the Delphix Admin application using Delphix Admin credentials.

2. Click Manage.
3. Select Environments.
4. Select the source appsTier environment.
If you have not already added the environment, see the Managing Unix Environments topics for more information about adding
environments.
5. Click the Environment Details tab.
6. If the applmgr environment user described in Preparing a Source EBS 11i Instance for Linking has not already been added to the
Delphix Engine, add the user.
For more information about adding environment users, see the Managing Unix Environment Users topics.
7. Click the Databases tab.
8. Click the Plus icon next to Add Dataset Home.
Adding the files as a dataset home will register the type and location of the files with the Delphix Engine.
9. Select E-Business Suite 11i appsTier as your Dataset Home Type.
When you select this type of dataset home, the Delphix Engine will know to automate pre-clone logic. Specifically, adpreclone.pl
appsTier will be run prior to every SnapSync of the appsTier. During dSource creation, you will be able to enter additional pre-clone
steps as Pre-Sync hook operations.
10. Enter an Installation Home.
This path should be the directory above $APPL_TOP on your source EBS environment. Commonly, this path looks like /u01/oracle/V
IS/.
11. Click the Confirm icon to save your dataset home.
Scroll down the list of dataset homes to view and edit this dataset home if necessary.
12. Click Manage.
13. Select Databases.
14. Select Add dSource.
15. In the Add dSource wizard, select the appsTier files source you just created.
16. Enter the EBS-specific parameters for your appsTier.
These parameter values will be used when adpreclone.pl is run.
Ensure the Apps Tier Context Name uses the short hostname.
17. Click Next.
18. Enter a dSource Name.
19. Select a Database Group for the dSource.
20. Click Next.
Adding a dSource to a database group enables you to set Delphix Domain user permissions for that dSource's objects, such as
snapshots. For more information, see the topics under Users, Permissions, and Policies.
21. Click Next.

987

Delphix User Guide 2016 Delphix

21.
22. Select a SnapSync policy.
23. Click Next.
24. Enter any custom pre or post sync logic as Pre-Sync or Post-Sync hook operations.
Remember that adpreclone.pl appsTier is already run prior to every SnapSync of the appsTier.
The Pre-Sync hook operations will be run prior to running the adpreclone.pl tool.
For more information, see Customizing Unstructured Files with Hook Operations.
25. Click Next.
26. Review the dSource Configuration and Data Management information, and then click Finish.
The Delphix Engine will initiate two jobs to create the dSource, DB_Link and DB_Sync. You can monitor these jobs by clicking Active
Jobs in the top menu bar, or by selecting System > Event Viewer. When the jobs have completed successfully, the files icon will
change to a dSource icon on the Environments > Databases screen, and the dSource will be added to the list of My Databases under
its assigned group.

988

Delphix User Guide 2016 Delphix

Preparing Target EBS 11i Environments for Provisioning

This topic outlines the prerequisites for provisioning a virtual EBS 11i instance to target environments.
Ensure your target EBS 11i instance is supported
Prepare the dbTier for provisioning
Delphix Engine's Unix Environment Requirements
oracle User
oraInst.loc
oratab
Delphix Engine's Oracle Database Requirements
Prepare the appsTier for Provisioning
Delphix Engine's Unix Environment Requirements
applmgr User
oraInst.loc
oratab

Ensure your target EBS 11i instance is supported

See Virtual EBS 11i Instance Requirements to ensure you can provision your EBS 11i instance.

Prepare the dbTier for provisioning

Delphix Engine's Unix Environment Requirements
The dbTier must meet the target requirements outlined in Requirements for Unix Environments. These requirements are generic to all target
Unix environments added to the Delphix Engine.

oracle User
The Delphix Engine must have access to an oracle user on the dbTier. This user should be a member of both the EBS dba and oinstall grou
ps. This user will be given proper permissions to manage the dbTechStack and database.

oraInst.loc
An oraInst.loc file must exist on the dbTier prior to provisioning. This file will specify where the oraInventory directories live or should be created if
they do not already exist.
The oraInst.loc file is typically located at /etc/oraInst.loc or /var/opt/oracle/oraInst.loc on Linux and Solaris respectively. Ensure
the oraInventory pointed to by this file is writable by the oracle user.
Consult Oracle EBS documentation for more information about where to place this file on your dbTier and what this file should contain.

oratab
An oratab file must exist on the dbTier prior to provisioning. This file must be writable by the oracle user.
The oratab file is typically located at /etc/oratab or /var/opt/oracle/oratab on Linux and Solaris respectively,
Consult Oracle EBS documentation for more information about where to place this file on your dbTier and what this file should contain.

Delphix Engine's Oracle Database Requirements

The dbTier must meet the target requirements outlined in Oracle Support and Requirements. These requirements are generic to all target Unix
environments expected to host a virtual Oracle database.

Prepare the appsTier for Provisioning

Delphix Engine's Unix Environment Requirements

989

Delphix User Guide 2016 Delphix

The appsTier must meet the target requirements outlined in Requirements for Unix Environments. These requirements are generic to all target
Unix environments added to the Delphix Engine.

applmgr User
The Delphix Engine must have access to an applmgr user on the appsTier. This user should be a member of the EBS oinstall group. This
user will be given proper permissions to manage the appsTier.

oraInst.loc
An oraInst.loc file must exist on the appsTier prior to provisioning. This file will specify where the oraInventory directories live or should be created
if they do not already exist.
The oraInst.loc file is typically located at /etc/oraInst.loc or /var/opt/oracle/oraInst.loc on Linux and Solaris respectively. Ensure
the oraInventory pointed to by this file is writable by the applmgr user.
Consult Oracle EBS documentation for more information about where to place this file on your appsTier and what this file should contain.

oratab
An oratab file must exist on the appsTier prior to provisioning. This file must be writable by the applmgr user.
The oratab file is typically located at /etc/oratab or /var/opt/oracle/oratab on Linux and Solaris respectively,
Consult Oracle EBS documentation for more information about where to place this file on your appsTier and what this file should contain.

990

Delphix User Guide 2016 Delphix

Provisioning a Virtual EBS 11i Instance

This topic describes the process of provisioning a virtual EBS 11i instance.

Prerequisites
You must have already linked a source instance of EBS 11i. For more information, see Linking a Source EBS 11i Instance .
Prepare your target EBS 11i environments for provisioning by following the outline in Preparing Target EBS 11i Environments for
Provisioning.
Snapshot Coordination
Changes applied to EBS and picked up only in certain dSource snapshots may make certain combinations of snapshots across the
appsTier and dbTier incompatible. When provisioning, refreshing or rewinding a virtual EBS instance, be sure the points in time you
select for each dataset are compatible with each other.

Procedure
Provision the EBS dbTechStack

1.

Login to the Delphix Admin application using Delphix Admin credentials.

2.

Click Manage.

3.

Select My Databases.

4.

Select the dbTechStack dSource.

5.

Select a dSource snapshot.

All snapshots will have staged configuration prepared by adpreclone.pl and any hook operations placed
on the dSource.

6.

Click Provision.
The Provision vFiles wizard will open.

7.

Select an Environment.
This environment will host the virtual dbTechStack and be used to execute hook operations specified in a
few steps.

8.

Select an Environment User.

This user should be the oracle user outlined in Preparing Target EBS 11i Environments for
Provisioning.

9.

Enter a Mount Path for the virtual dbTechStack files.

10. Enter the EBS-specific parameters for the virtual dbTechStack. A subset of these parameters are discussed in more detail below.
a. Ensure that the Target DB Hostname value is the short hostname, not the fully-qualified hostname.
b. The APPS Password is required to configure the virtual dbTechStack.
This password is encrypted when stored within the Delphix Engine and is available as an environment variable to the adcfgclo
ne process.
c. Enable the Cleanup Before Provision option to permit the Delphix Engine to automatically cleanup stale EBS configuration
during a refresh. This option is recommended, but only available if your Oracle Home is patched with Oracle Universal Installer
(OUI) version 10.2 or above.
i. With this option specified, the Delphix Engine will inspect the target environment's oraInventory prior to refreshing this
virtual Oracle Home. If any Oracle Homes are already registered within the specified Mount Path, the Delphix Engine
will detach them from the inventory prior to running adcfgclone. These homes must be detached prior to running
post-clone configuration, or else adcfgclone will fail citing conflicting oraInventory entries as an issue. The Delphix
Engine will also inspect the target environment's oratab file, and cleanup any conflicting entries registered within the
specified Mount Path.
ii. Without this option specified, Oracle Homes found to conflict with the specified Mount Path will be reported in an error
instead of automatically detached. For refresh to succeed, these Oracle Homes must be manually detached prior to
refresh.
11. Click Next.
12. Enter a vFiles Name.
13.

Select a Target Group for the vFiles.

991

Delphix User Guide 2016 Delphix

13.

If necessary, click the green Plus icon to add a new group.

14.

Select a Snapshot Policy for the vFiles.

If necessary, click the green Plus icon to create a new policy.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

15.

Click Next.

16.

Enter any custom hook operations that are needed to help correctly manage the virtual dbTechStack files.
For more information about these hooks, when they are run, and how operations are written, see Customizin
g Unstructured Files with Hook Operations.
The Configure Clone hook will be run after the adcfgclone.pl tool has both mounted and configured the
dbTechStack.

17.

Click Next.

18.

Click Finish.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History p
anel of the Dashboard. When provisioning is complete, the dbTechStack vFiles will be included in the group
you designated and listed in the Databases panel. If you select the dbTechStack vFiles in the Databases pa
nel and click the Open icon, you can view its card, which contains information about the virtual files and its
Data Management settings.

19.

See Monitoring EBS 11i dbTechStack Provisioning Progress for tips for monitoring the progress of
dbTechStack provisioning.

Register the EBS dbTechStack

Register the freshly-provisioned dbTechStack with the Delphix Engine.

1.

Login to the Delphix Admin application using Delphix Admin credentials.

2.

Click Manage.

3.

Select Environments.

4.

Select the target dbTier environment.

5.

Click the Databases tab.

6.

Click the Plus icon next to Add Dataset Home.

7.

Select Oracle as your Dataset Home Type.

8.

Enter an Installation Home.

This path should be the value of $ORACLE_HOME on your target dbTier; this path will live under the mount
path specified when you provisioned the virtual dbTechStack.
Commonly, this path looks like /u01/oracle/VIS/visdb/9.2.0.

9.

Click the Confirm icon to save your dataset home.

Scroll down the list of dataset homes to view and edit this dataset home if necessary.

10.

Refresh the target dbTier environment.

Refreshing the environment will discover EBS database listener and ensure it is available for selection when
provisioning the EBS database.
a.

Click the Refresh button in the bottom right-hand corner of the environment card.

992

Delphix User Guide 2016 Delphix

Provision the Oracle Database

1. Provision the EBS database to the target dbTier environment by following the steps outlined in Provisioning an Oracle VDB.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

2.

Select the correct Installation Home.

This selection should be the virtual dbTechStack you just added to the Delphix Engine.

3.

Enter the SID same as whats provided to the virtual dbTechStack you just added to the Delphix Engine.

4.

Click Advanced .

5.

Select the correct Oracle Node Listeners value.

This selection should be the listener corresponding to the virtual dbTechStack you just added to the Delphix
Engine.

6. Add the EBS 11i dbTier environment file as a Custom

Environment Variables entry.

This file can be specified as an Environment File with Path Parameters of $ORACLE_HOME/<CONTEXT_NAME>.env.
See Customizing Oracle VDB Environment Variables for more information.
Replace <CONTEXT_NAME> with the virtual EBS instance's context name. The $ORACLE_HOME variable will be expanded by the
Delphix Engine at runtime.
7. Add a Run Bash Shell Command operation to the Configure Clone hook to ensure adcfgclone is run against the newly provisioned
database. Typically, this operation will look similar to the below script.

# NOTE: Ensure the below environment variables will be set up correctly by the
shell. If not, hardcode or generate the values below.
# CONTEXT_NAME=${ORACLE_SID}_$(hostname -s)
# APPS_PASSWD=<passwd>
. ${ORACLE_HOME}/${CONTEXT_NAME}.env
sqlplus "/ as sysdba" <<EOF
@${ORACLE_HOME}/appsutil/install/${CONTEXT_NAME}/adupdlib.sql so
EOF
perl ${ORACLE_HOME}/appsutil/clone/bin/adcfgclone.pl dbconfig
${ORACLE_HOME}/appsutil/${CONTEXT_NAME}.xml <<EOF
${APPS_PASSWD}
EOF
8.

Set up a Pre-Snapshot hook Run Bash Shell Command operation to run any pre-clone steps necessary and
specific to the target EBS database. Normally, these steps will include running Oracle's adpreclone tool.
Below is an example of a simple Run Bash Shell Command hook operation:
# NOTE: Ensure the below environment variables will be set up correctly by the
shell. If not, hardcode or generate the values below.
# CONTEXT_NAME=${ORACLE_SID}_$(hostname -s)
# APPS_PASSWD=<passwd>
. ${ORACLE_HOME}/${CONTEXT_NAME}.env
perl ${ORACLE_HOME}/appsutil/scripts/${CONTEXT_NAME}/adpreclone.pl database <<-EOF
${APPS_PASSWD}
EOF

993

Delphix User Guide 2016 Delphix

Provision the EBS appsTier

1. Login to the Delphix Admin application using Delphix Admin credentials.

2.

Click Manage.

3. Select My

Databases.

4.

Select the appsTier dSource.

5.

Select a dSource snapshot.

All snapshots will have staged configuration prepared by adpreclone.pl and any hook operations placed
on the dSource.

6. Click Provision.
The Provision vFiles wizard will open.
7. Select an Environment.
This environment will host the virtual appsTier and be used to execute hook operations specified in a few steps.
8.

Select an Environment User.

This user should be the applmgr user outlined in Preparing Target EBS 11i Environments for
Provisioning.

9.

Enter a Mount Path for the virtual appsTier files.

10. Enter the EBS-specific parameters for your target appsTier. A subset of these parameters are discussed in more detail below.
a. Ensure the Target Application Hostname and Target DB Server Node values are the short hostnames, not the fully-qualified
hostnames.
b. The APPS Password is required to configure and manage the virtual appsTier.
This password is encrypted when stored within the Delphix Engine and is available as an environment variable to the adcfgclo
ne, adstrtal, and adstpall processes.
c. Enable the Cleanup Before Provision option to permit the Delphix Engine to automatically cleanup stale EBS configuration
during a refresh. This option is recommended, but only available if your Oracle Home is patched with Oracle Universal Installer
(OUI) version 10.2 or above.
i. With this option specified, the Delphix Engine will inspect the target environment's oraInventory prior to refreshing this
virtual appsTier. If any Oracle Homes are already registered within the specified Mount Path, the Delphix Engine will
detach them from the inventory prior to running adcfgclone. These homes must be detached prior to running
post-clone configuration, or else adcfgclone will fail citing conflicting oraInventory entries as an issue. The Delphix
Engine will also inspect the target environment's oratab file, and cleanup any conflicting entries registered within the
specified Mount Path.
ii. Without this option specified, Oracle Homes found to conflict with the specified Mount Path will be reported in an error
instead of automatically cleaned up. For refresh to succeed, conflicting Oracle Homes must be manually detached and
removed from oratab prior to refresh.
11. Click Next.
12.

Enter a vFiles Name.

13.

Select a Target Group for the vFiles.

If necessary, click the green Plus icon to add a new group.

14.

Select a Snapshot Policy for the vFiles.

If necessary, click the green Plus icon to create a new policy.
EBS SnapSync Conflicts
When Snapshot is running against the dbTechStack, database, or appsTier, the Delphix Engine also executes pre-clone logic
to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against
the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

15.

Click Next.

16.

Enter any custom hook operations that are needed to help correctly manage the virtual appsTier.
For more information about these hooks, when they are run, and how operations are written, see Customizin
g Unstructured Files with Hook Operations.

994

16.
Delphix User Guide 2016 Delphix

The Configure Clone hook will be run after the adcfgclone.pl tool has both mounted and configured the
appsTier.
17. Click Next.
18. Click Finish.
dbTier Must Be Accessible During appsTier Provisioning
Post-clone configuration will fail if the appsTier cannot connect to the database. Ensure that the target dbTier is accessible to
the appsTier during the provisioning process. Ensure that both the target database and database listener are running.
When provisioning starts, you can review progress of the job in the Databases panel, or in the Job History panel of the Dashboard.
When provisioning is complete, the appsTier vFiles will be included in the group you designated and listed in the Databases panel. If you
select the appsTier vFiles in the Databases panel and click the Open icon, you can view its card, which contains information about the
virtual files and its Data Management settings.
19. See Monitoring EBS 11i appsTier Provisioning Progress for tips for monitoring the progress of appsTier provisioning.
Once all three EBS virtual datasets have been provisioned successfully, your virtual EBS instance should be running and accessible.

995

Delphix User Guide 2016 Delphix

Monitoring EBS 11i dbTechStack Provisioning Progress

This topic describes how to monitor the progress of EBS 11i dbTechStack provisioning.
The Delphix Engine automates the configuration of the dbTechStack during provisioning. It spends a majority of provisioning time running
RapidClone utilities such as adcfgclone. The Delphix Engine does not report the progress of RapidClone utilities through the progress of the D
B_Provision job. To more accurately track provisioning progress, Delphix recommends monitoring EBS log files generated on the target dbTier
environment.
Procedure

1. Connect to the target dbTier environment using SSH or an alternative utility.

2. Change directories to the <ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/.
Replace <ORACLE_HOME> with the path to the dbTechStack's Oracle Home: this path will be under the mount path specified during
provisioning.
Replace <CONTEXT_NAME> with the virtual EBS instance's context name.
3. After adcfgclone has begun running, a file matching ApplyDBTechStack_*.log will exist. Identify this log file and use tail or an
equivalent utility to monitor it.

Leave the Mount Point Prior to Refresh

If provisioning fails, you will need to fix the cause of the failure and perform a refresh of the dataset to attempt configuration again. Prior
to refreshing or disabling the dataset, be sure to change directories to a location outside of the mount path on the target environment. If
you leave a shell session with a current working directory inside the mount path, the dataset will fail to unmount cleanly during refresh
or disable.

996

Delphix User Guide 2016 Delphix

Monitoring EBS 11i appsTier Provisioning Progress

This topic describes how to monitor the progress of EBS 11i appsTier provisioning.
The Delphix Engine automates the configuration of the appsTier during provisioning. It spends a majority of provisioning time running RapidClone
utilities such as adcfgclone. The Delphix Engine does not report the progress of RapidClone utilities through the progress of the DB_Provision
job. To more accurately track provisioning progress, Delphix recommends monitoring EBS log files generated on the target appsTier environment.
Procedure

1. Connect to the target appsTier environment using SSH or an alternative utility.

2. Change directories to the <APPL_TOP>/admin/<CONTEXT_NAME>/log/.
Replace <APPL_TOP> with the value of APPL_TOP on the virtual EBS instance: this value will contain the mount path specified during
provisioning.
Replace <CONTEXT_NAME> with the virtual EBS instance's context name.
3. After adcfgclone has begun running, a file matching ApplyAppsTier_*.log will exist. Identify this log file and use tail or an
equivalent utility to monitor it.

Leave the Mount Point Prior to Refresh

If provisioning fails, you will need to fix the cause of the failure and perform a refresh of the dataset to attempt configuration again. Prior
to refreshing or disabling the dataset, be sure to change directories to a location outside of the mount path on the target environment. If
you leave a shell session with a current working directory inside the mount path, the dataset will fail to unmount cleanly during refresh
or disable.

997

Delphix User Guide 2016 Delphix

Managing Data Operations of Virtual EBS Instances

This section describes how to perform various data operations for virtual Oracle Enterprise Business Suite (EBS) instances once they have been
provisioned.
Starting and Stopping a Virtual EBS Instance
Rewinding a Virtual EBS Instance
Refreshing a Virtual EBS Instance
Enabling and Disabling a Virtual EBS Instance
Deleting a Virtual EBS Instance
Modifying the appsTier Topology
Replicating a Virtual EBS Instance
Upgrading a Delphix Engine hosting a Virtual EBS Instance

998

Delphix User Guide 2016 Delphix

Starting and Stopping a Virtual EBS Instance

This topic describes the process of starting and stopping a virtual Oracle Enterprise Business Suite (EBS) instance.
Stopping
Starting
You can start and stop virtual EBS instances through the Delphix Admin application or through the standard Oracle command line interface (CLI)
utilities, adstrtal and adstpall. The Delphix Engine will show the dbTechStack and appsTier as running as long as there are processes using
the dbTechStack and appsTier filesystem mounts on the target environments.
Be careful! Services running on the appsTier depend on the availability of services on the dbTier. The steps below are explicitly ordered
with these dependencies in mind. Executing steps out of order may lead to errors in accessing the virtual EBS instance.

Stopping
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select My Databases.
4.

Select the appsTier vFiles for your EBS instance.

5. In the bottom right-hand corner, click Stop.

Stopping the appsTier will run Oracles adstpall.sh utility.
For multi-node appsTier, secondary nodes will be stopped sequentially, followed by the primary node.
Stopping the appsTier may take a long time. The Delphix Engine will wait for all Oracle application processes to exit before
declaring the appsTier as stopped.

6. Select the VDB utilized by your EBS instance.

7. In the lower right-hand corner, click Stop.
This action will shut down the database instance.
8. Select the dbTechStack vFiles hosting your virtual EBS database.
9. In the lower right-hand corner, click Stop.
Stopping the dbTechStack will shut down the database listener.

Starting
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select My Databases.
4. Select the dbTechStack vFiles hosting your virtual EBS database.
5. In the lower right-hand corner, click Start.
Starting the dbTechStack will start the database listener.
6. Select the VDB utilized by your EBS instance.
7. In the lower right-hand corner, click Start.
Starting the database will open the database.
8. Select the appsTier vFiles for your EBS instance.
9. In the lower right-hand corner, click Start.
Starting the appsTier will run Oracles adstrtal.sh utility.
For multi-node appsTier, the primary node will be started first, followed by secondary nodes sequentially.

999

Delphix User Guide 2016 Delphix

Rewinding a Virtual EBS Instance

This topic describes the process of rewinding a virtual Oracle Enterprise Business Suite (EBS) instance.
Prerequisites
Procedure
Changes applied to EBS and picked up only in some dSource snapshots may make certain combinations of snapshots across the
appsTier and dbTier incompatible. When provisioning, refreshing, or rewinding a virtual EBS instance, be sure the points in time you
select for each dataset are compatible with each other.

Be careful! Services running on the appsTier depend on the availability of services on the dbTier. The steps below are explicitly ordered
with these dependencies in mind. Executing steps out of order may lead to errors in accessing the virtual EBS instance.

Prerequisites
The appsTier Instance Home Directory of the virtual EBS instance must reside under the specified Mount Path.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select My Databases.
4. Select the appsTier vFiles for your EBS instance.
5. Click the Stop icon to shut down the appsTier services.
6. Select the VDB utilized by your EBS instance.
7. Click the Stop icon to shut down the database.
8. Select the dbTechStack vFiles hosting your virtual EBS database.
9. Click the Stop icon to shut down the database listener.
10. Rewind the dbTechStack vFiles.
a. Select a snapshot.
b. Click the Rewind button below the snapshots.
11. Rewind the EBS VDB.
a. Select a snapshot.
b. Click the Rewind button below the snapshots.
12. Rewind the appsTier vFiles.
a. Select a snapshot.
b. Click the Rewind button below the snapshots.
Once you have rewound all three EBS virtual datasets successfully, your virtual EBS instance should be running and accessible.

1000

Delphix User Guide 2016 Delphix

Refreshing a Virtual EBS Instance

This topic describes the process of refreshing a virtual Oracle Enterprise Business Suite (EBS) instance.
Changes applied to EBS and picked up only in some dSource snapshots may make certain combinations of snapshots across the
appsTier and dbTier incompatible. When provisioning, refreshing, or rewinding a virtual EBS instance, be sure the points in time you
choose for each dataset are compatible with each other.

Be careful! Services running on the appsTier depend on the availability of services on the dbTier. The steps below are explicitly ordered
with these dependencies in mind. Executing steps out of order may lead to errors in accessing the virtual EBS instance.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select My Databases.
4. Select the appsTier vFiles for your EBS instance.
5. Click the Stop icon to shut down the appsTier services.
6. Select the VDB utilized by your EBS instance.
7. Click the Stop icon to shut down the database.
8. Select the dbTechStack vFiles hosting your virtual EBS database.
9. Click the Stop icon to shut down the database listener.
Clean Up Might Be Required
If you did NOT specify the Cleanup Before Provision option for either your virtual dbTechStack or appsTier, you must
manually clean up your target environments prior to refresh. If you have specified this option for both datasets, no manual work
is required.

instance-specific directories and oraInventory

entries that will conflict with files and entries recreated during a refresh. If you are refreshing a virtual
EBS 11i instance, you must also clean up stale entries in the oraTab file before performing a refresh.
Without this clean up, post-clone configuration performed during a refresh will fail with an error
claiming that a conflicting EBS instance is already installed.
To manually clean up a target environment prior to refresh, remove

10. Refresh the dbTechStack vFiles.

a. On the back of the vFiles card, click the Refresh icon in the lower right-hand corner.
b. Select a snapshot from which to refresh.
11. Refresh the EBS VDB.
a. On the back of the VDB card, click the Refresh icon in the lower right-hand corner.
b. Select a snapshot from which to refresh.
12. Refresh the appsTier vFiles.
a. On the back of the vFiles card, click the Refresh icon in the lower right-hand corner.
b. Select a snapshot from which to refresh.
Once you have refreshed all three EBS virtual datasets successfully, your virtual EBS instance should be running and accessible.

1001

Delphix User Guide 2016 Delphix

Enabling and Disabling a Virtual EBS Instance

This topic describes the process of enabling and disabling a virtual Oracle Enterprise Business Suite (EBS) instance.
Disabling
Enabling
An enabled virtual EBS instance will be running and fully available to end users. A disabled virtual EBS instance will be neither running nor
mounted to the target environments.
Be careful! Services running on the appsTier depend on the availability of services on the dbTier. The steps below are explicitly ordered
with these dependencies in mind. Executing steps out of order may lead to errors in accessing the virtual EBS instance.

Disabling
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select My Databases.
4.

Select the appsTier vFiles for your EBS instance.

5. On the back of the card, move the slider control from Enabled to Disabled.

Disabling the appsTier vFiles will stop the appsTier services and unmount the appsTier files.
Stopping the appsTier may take a long time. The Delphix Engine will wait for all Oracle application processes to exit before
declaring the appsTier as stopped.

6. Select the VDB utilized by your EBS instance.

7. On the back of the card, move the slider control from Enabled to Disabled.
Disabling the VDB will stop the database instance and unmount the data files.
8. Select the dbTechStack vFiles hosting your virtual EBS database.
9. On the back of the card, move the slider control from Enabled to Disabled.
Disabling the dbTechStack vFiles will stop the database listener and unmount the dbTechStack files.
Once you have disabled all three EBS virtual datasets successfully, your virtual EBS instance should be fully removed from the target
environment.

Enabling
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select My Databases.
4. Select the dbTechStack vFiles hosting your virtual EBS database.
5. On the back of the card, move the slider control from Disabled to Enabled.
Enabling the dbTechStack vFiles will mount the dbTechStack files and start the database listener.
6. Select the VDB utilized by your EBS instance.
7. On the back of the card, move the slider control from Disabled to Enabled.
Enabling the VDB will mount the data files and start the database instance.
8. Select the appsTier vFiles hosting your virtual EBS database.
9. On the back of the card, move the slider control from Disabled to Enabled.
Enabling the dbTechStack vFiles will mount the appsTier files and start the application services.
Once you have enabled all three EBS virtual datasets successfully, your virtual EBS instance should be running and accessible.

1002

Delphix User Guide 2016 Delphix

Deleting a Virtual EBS Instance

This topic describes the process of deleting a virtual Oracle Enterprise Business Suite (EBS) instance.
Be careful! Services running on the appsTier depend on the availability of services on the dbTier. The steps below are explicitly ordered
with these dependencies in mind. Executing steps out of order may lead to errors in accessing the virtual EBS instance.

Procedure
1. Login to the Delphix Admin application using Delphix Admin credentials.
2. Click Manage.
3. Select My Databases.
4. Select the appsTier vFiles for your EBS instance.
5. Delete the appsTier vFiles by clicking the Trash Can icon in the lower left-hand corner.
6. Select the VDB utilized by your EBS instance.
7. Delete the VDB by clicking the Trash Can icon in the lower left-hand corner.
8. Click Manage.
9. Select Environments.
10. Select the target dbTier environment.
11. Click the Databases tab.
12. In the list of Installation Homes on the environment, click the Trash Can icon next to the dbTechStack Oracle Home you want to delete.
13. Click Manage.
14. Select My Databases.
15. Select the dbTechStack vFiles for your EBS instance.
16. Delete the dbTechStack vFiles by clicking the Trash Can icon in the lower left-hand corner.
17. Clean up any files that the virtual EBS instance might have created outside of the Delphix mount points on the target
environments. These typically include the instance-specific directories, oraInventory files, and oraTab entries.
Once you have deleted all three EBS virtual datasets successfully, your virtual EBS instance should be fully removed from the target
environments.

1003

Delphix User Guide 2016 Delphix

Modifying the appsTier Topology

This topic describes the process of modifying the appsTier topology of a virtual EBS instance.
EBS R12.1 and EBS R12.2 Only
This topic is only relevant to EBS R12.1 and EBS R12.2; the Delphix Engine only supports single-node appsTier for EBS 11i.

appsTier Topology Changes Invalidate Rewind

If you modify the appsTier topology of a virtual EBS instance, all snapshots in existence prior to the modification will no longer be valid
for rewind. The appsTier topology in the snapshots will no longer match the Delphix Engine's configuration and rewind targeting these
snapshots will fail if attempted.

Procedure
1. Disable the virtual EBS instance by following the procedure outlined in Enabling and Disabling a Virtual EBS Instance.
2. Select the appsTier vFiles for your EBS instance.
3. On the back of the card, modify the EBS-specific parameters for the virtual appsTier.
This process will normally entail adding or deleting Additional Nodes and configuring its corresponding Services.
4. Apply the configuration changes by refreshing the entire virtual EBS instance.
Follow the procedure outlined in Refreshing a Virtual EBS Instance.

Related Links
Enabling and Disabling a Virtual EBS Instance
Refreshing a Virtual EBS Instance

1004

Delphix User Guide 2016 Delphix

Replicating a Virtual EBS Instance

This topic describes the process of replicating a virtual Oracle Enterprise Business Suite (EBS) instance.

Replication
1. Login to the source Delphix Engine's Delphix Admin application using Delphix Admin credentials.
2. Configure replication between the source Delphix Engine and a target Delphix Engine.
For a detailed outline of the replication process, see Configuring Replication.
3. Select the dbTechStack vFiles , VDB , and appsTier vFiles objects to be replicated.
These objects have dependencies on all other Delphix Engine objects relevant to the virtual EBS instance: you do not need to specify
any additional objects for EBS replication.
4. Schedule or perform the replication.

Failover
1. Login to the target Delphix Engine's Delphix Admin application using Delphix Admin credentials.
2. Failover the replica dbTechStack vFiles , VDB , and appsTier vFiles. Failing over these object will sever future replication, but will
not enable the datasets.
For a detailed outline of the failover process, see Failing Over a Replica.
3. Enable the dbTier and appsTier environments.
a. Click Manage.
b. Select Environments.
c. For each environment, move the slider control from Disabled to Enabled .
4. Enable the virtual EBS instance by following the procedure outlined in Enabling and Disabling a Virtual EBS Instance.

Provisioning from a Replicated EBS Instance

You can provision new virtual EBS instances from replicated datasets regardless of whether these datasets have been failed over. The
provisioning process for each version of EBS is outlined in Virtualizing Oracle Enterprise Business Suite. For more information about
provisioning from replicated datasets, see Provisioning from Replicated Data Sources or VDBs.

Related Links
Configuring Replication
Failing Over a Replica
Enabling and Disabling a Virtual EBS Instance
Virtualizing Oracle Enterprise Business Suite
Provisioning from Replicated Data Sources or VDBs

1005

Delphix User Guide 2016 Delphix

Upgrading a Delphix Engine hosting a Virtual EBS Instance

This topic describes the process of upgrading a Delphix Engine hosting a virtual Oracle Enterprise Business Suite (EBS) instance.

Procedure
1. Disable the virtual EBS instance by following the procedure outlined in Enabling and Disabling a Virtual EBS Instance.
2. Once you have safely disabled the virtual EBS instance , upgrade the Delphix Engine by following the procedure outlined in Upgrading
the Delphix Engine.
3. Enable the virtual EBS instance by following the procedure outlined in Enabling and Disabling a Virtual EBS Instance.

Related Links
Enabling and Disabling a Virtual EBS Instance
Upgrading the Delphix Engine

1006

Delphix User Guide 2016 Delphix

Virtual EBS Instance Recipes

This section describes recipes for accomplishing common tasks with virtual EBS instances.
Configuring a Jet Stream Data Template for EBS
Managing the APPS Password
Refreshing a Target dbTier Environment

1007

Delphix User Guide 2016 Delphix

Configuring a Jet Stream Data Template for EBS

This topic describes the process of configuring a Jet Stream data template for Oracle Enterprise Business Suite (EBS).
By configuring a Jet Stream data template for EBS, you eliminate the need to order operations applied across the EBS datasets.
The ordering of operations is a result of the dataset dependencies discussed in topics under Managing Data Operations of Virtual EBS
Instances, such as Refreshing a Virtual EBS Instance.

Procedure
1. Create a Jet Stream data template by following the procedure outlined in Understanding Jet Stream Data Templates.
a. For EBS, the data template will have three data sources: the dbTechStack, database and appsTier.
2. Be sure to set the following ordering of the data sources when creating the data template. This ordering will ensure that Jet Stream
operations do not violate the EBS dataset dependencies.
Order

Dataset

dbTechStack

Database

appsTier

Once you have created a Jet Stream data template, you can configure Jet Stream data containers to manage virtual EBS instances. Jet Stream
data containers will follow the ordering of data sources configured in the template. All Jet Stream operations should works as expected for virtual
EBS instances.

Related Links
Managing Data Operations of Virtual EBS Instances
Refreshing a Virtual EBS Instance
Understanding Jet Stream Data Templates

1008

Delphix User Guide 2016 Delphix

Managing the APPS Password

This topic outlines how to manage the APPS password on a virtual EBS instance.
Changing the APPS Password
Refreshing or Rewinding
Related Links
The Delphix Engine requires a virtual EBS instance's APPS password in order to manage its dbTechStack and appsTier. This password is
encrypted when stored within the Delphix Engine and is exposed as an environment variable to RapidClone tools.
When a virtual EBS instance is being provisioned, the Delphix Engine's copy of the APPS password should match the source EBS instance's
APPS password during its time of snapshot. After provisioning, you can change the APPS password of the virtual instance in both EBS and the
Delphix Engine.

Changing the APPS Password

1. Provision a virtual EBS instance.
2. Change the APPS password in the virtual EBS instance.
You can perform the password change using Oracle's FNDCPASS utility.
3. Stop the virtual appsTier manually using adstpall.
You cannot stop the virtual appsTier through the Delphix Engine, because the APPS password being stored is now out of sync.
4. Disable the entire virtual EBS instance.
For an outline of this process, see Enabling and Disabling a Virtual EBS Instance.
5. Change the APPS password on the dbTechStack.
a. Select the dbTechStack vFiles hosting your virtual EBS database.
b. On the back of the card, click the Custom tab.
c. Edit the APPS Password field.
6. Change the APPS password in any hook operations defined on the EBS virtual database.
a. Select the VDB utilized by your EBS instance.
b. On the back of the card, click the Hooks tab.
c. Edit the relevant hook operations.
Typically, you will need to edit the Pre-Snapshot hook operation running adpreclone.
7. Change the APPS password on the appsTier.
a. Select the appsTier vFiles hosting your virtual EBS database.
b. On the back of the card, click the Custom tab.
c. Edit the APPS Password field.
8. Enable the entire virtual EBS instance.
For an outline of this process, see Enabling and Disabling a Virtual EBS Instance.

Refreshing or Rewinding
The APPS password stored across individual snapshots of a virtual EBS instance will not be consistent after a password change. Old snapshots
of EBS data will refer to a different APPS password than new snapshots of EBS data. To perform a refresh or rewind, you must explicitly
manipulate the Delphix Engine's copy of the APPS password to ensure that the virtual EBS instance is being accessed with the correct APPS
password at every step.
Recipe Not Needed If Password Not Changed
These steps are only necessary if the virtual EBS instance has a different APPS password than the snapshots being targeted by the
refresh or rewind.
If the APPS password has not been changed, follow the instructions in Refreshing a Virtual EBS Instance or Rewinding a Virtual
EBS Instance.
1. Before refreshing or rewinding the virtual EBS instance, disable the entire virtual EBS instance.
For an outline of this process, see Enabling and Disabling a Virtual EBS Instance.
2. Identify the APPS password for the snapshots being targeted by the refresh or rewind. Modify the virtual EBS instance to refer to this
password.
a. Change the APPS password on the dbTechStack.
i. Select the dbTechStack vFiles hosting your virtual EBS database.

1009

2.

Delphix User Guide 2016 Delphix

a.
i.
ii. On the back of the card, click the Custom tab.
iii. Edit the APPS Password field.
b. Change the APPS password in any hook operations defined on the EBS virtual database.
i. Select the VDB utilized by your EBS instance.
ii. On the back of the card, click the Hooks tab.
iii. Edit the relevant hook operations.
Typically, you will need to edit the Pre-Snapshot hook operation running adpreclone and the Configure Clone
operation running adcfgclone.
c. Change the APPS password on the appsTier.
i. Select the appsTier vFiles hosting your virtual EBS database.
ii. On the back of the card, click the Custom tab.
iii. Edit the APPS Password field.

3. Perform the refresh or rewind while the EBS instance is disabled.

See Refreshing a Virtual EBS Instance or Rewinding a Virtual EBS Instance for an outline of these processes.

Related Links
Enabling and Disabling a Virtual EBS Instance
Refreshing a Virtual EBS Instance
Rewinding a Virtual EBS Instance

1010

Delphix User Guide 2016 Delphix

Refreshing a Target dbTier Environment

This topic describes how to properly refresh a target dbTier environment hosting an EBS VDB.
Procedure
Related Links
When an environment is initially registered with the Delphix Engine, a discovery process is responsible for registering resources such as Oracle
Homes, listeners, and databases. When an environment is modified for example, when an Oracle Home is upgraded or removed you must
run the discovery process again in order to register new resources and unregister removed ones.
The virtual dbTechStack plays a unique role in the Delphix Engine because it acts both as a virtual dataset AND a discovered resource on the
target dbTier environment. Because of this unique role, you must mount and start this dataset (hosting the EBS database listener) before you
refresh the target dbTier environment.
If you unmount or stop the virtual dbTechStack, the discovery process will assume that the EBS Oracle Home and database listener have been
removed from the environment. Further interactions with the EBS VDB will result in error, because neither the database listener nor Oracle Home
appear available to the database.

Procedure
1. Prior to refreshing a target dbTier environment, ensure that the virtual dbTechStack is both enabled and started.
For more information, see Enabling and Disabling a Virtual EBS Instance and Starting and Stopping a Virtual EBS Instance.
2. Refresh the target dbTier environment.
For more information, see Refreshing an Oracle Environment.

Related Links
Enabling and Disabling a Virtual EBS Instance
Starting and Stopping a Virtual EBS Instance
Refreshing an Oracle Environment

1011

Delphix User Guide 2016 Delphix

_Mission Control Delphix Admin User Guide (2015)

ADMIN USER GUIDE

Mission Control
V.1.1

Getting Started
Welcome to Delphix Mission Control
User Roles and Permissions
System Requirements
Supported Browsers
Delphix Engine Configuration
Activity One: Install Mission Control
Logging In
Mission Control Toolbar
Activity Two: Add Delphix Engines to Mission Control
Adding Users
Change a User Password
Search and Run Reports
Activity Three: Access a List of Reports
Filter, Organize, and Extract Reports
Tagging
Activity Four: Apply Tags
Filtering
Activity Five: Extracting Data from Reports
Understanding the Graphs Interface
Activity Six: Viewing Graphs in the Breakdown Tab
Working with Total Storage Graphs
Working with Source Usage Graphs
Activity Seven: Working with Graphs in the Historical Tab
Mission Control Maintenance
Managing the Operating System
Upgrading Mission Control
Activity Eight: Self-Service Upgrade of Mission Control
Activity Nine: Generate and Upload MC Support Bundles
Resources
Support

1012

Delphix User Guide 2016 Delphix

Getting Started with Mission Control

Welcome to Delphix Mission Control
User Roles and Permissions
System Requirements
Supported Browsers

Welcome to Delphix Mission Control

Mission Control is a centralized reporting and auditing tool for overseeing multiple Delphix Engine deployments. Mission Control allows
administrators to combine, sort, and audit data from multiple Delphix Engines. A centralized view of data from many Delphix Engines allows
administrators to identify promptly any issues with the deployment, determine where resources are allocated, quickly locate deployed databases,
and properly size future additions.

User Roles and Permissions

Mission Control has two types of users:
Admin User
Admin users have full access to all report data and can configure the Mission Control appliance. For example, they can add/delete Delphix
Engines, add/delete reports, add/delete users, change tunable settings, and add/delete tags.

Auditor User
Auditor users can only view report data. Admin users can also assign auditor users a set of tags (arbitrary text strings) to restrict which report data
they can view. There is no default auditor account. The first Delphix Administrator will need to create the auditor users and will be responsible for
creating their User IDs and Passwords.

System Requirements
The VM guest where you install Mission Control has the following requirements:
VMware ESX: 4.x or greater
Two Virtual CPUs
4 GB of Memory
50 GB of Storage
Mission Control supports Delphix Engine 4.0 or later.

Supported Browsers
The following are the minimum supported browser versions for accessing the Mission Control console:
Chrome 37
Safari 7
Firefox 32
Internet Explorer 11

1013

Delphix User Guide 2016 Delphix

Delphix Engine Configuration

Activity One: Import the OVA file for Mission Control into a VM guest
Add Mission Control to the Network
Logging In
Navigating the Mission Control Toolbar and User Interface
Viewing Reports
Configure Mission Control
Configure Reports
Report Scripts
Script Configuration
Email Reports
Activity Two: Configure, Automate, and Email Mission Control Reports
Configure Engines
Configure Users
Activity Three: Add Delphix Engines to Mission Control
Activity Four: Adding Users
Activity Five: Change a User Password

Activity One: Import the OVA file for Mission Control into a VM guest
1. Using the vSphere client, login to the vSphere server where you want to install Mission Control.
2. Click File.
3. Select Deploy OVA Template.
4. Select the Mission Control OVA file.

Add Mission Control to the Network

By default, Mission Control is configured to use DHCP to acquire an IP address. If this is acceptable within your organization, then Mission
Control should be immediately accessible at the IP hostname assigned to the VM guest within vSphere.
However, many organizations do not support the use of DHCP by servers on their network. In that case, it will become necessary to log in as
"root" into Mission Control via the console provide by vSphere, and work with your network administrator to perform the following actions to set up
a static IP address on the VM guest.
1. Connect to the VM guest (running a stripped-down version of Linux) as "root", initial default password is "delphix."
a. Change this password as soon as possible.
2. Run the Linux command ifconfig -a | grep -i hwaddr.
a. Record the "HwAddr" output for later use. This should be six hexadecimal numbers delimited by colons, such as 0A:1B:2C:
4D:5E:6F.
3. Change to the directory /etc/sysconfig/network-scripts
4. Edit the ifcfg-eth0 file to make the following changes:
a. Copy the existing ifcfg-eth0 file to another name like ifcfg-eth0.save.
b. Change bootproto=dhcp to bootproto=static.
c. Using the "HwAddr" value saved from step #2 above, add a line reading HWADDR=<hwaddr-value-captured-above> .
d. Using an available IP address value obtained from your network administrator, add a line reading IPADDR=<available-IP
-address> .
e. Using an IP netmask value obtained from your network administrator, add a line reading NETMASK=<netmask-spec> .
f. Save the changes.
5. Make sure that output from the hostname command matches the value set within vSphere.
a. If the output does not match, use the Linux command hostname <short-IP-hostname-value> to set it.
6. Create a default gateway route for the static IP address assigned above.
a. Typically, the default gateway address has the fourth digit of ".1" for the IP address of the server
i. The server at IP address 192.168.7.10 might have a gateway of 192.168.7.1.
ii.
1014

6.

Delphix User Guide 2016 Delphix

a.

ii. Obtain the gateway IP address from your network administrator.

b. Use the Linux command route add default gw <gateway-IP-address> .
c. To ensure that the default gateway persisted after a reboot, add GATEWAY<DNS-nameserver-IP-address>=<gateway-IP-ad
dress> to /etcsysconfig/network-scripts/ifcfg-eth0.
7. Make sure that the contents of the /etc/resolv.conf file is set appropriately to permit DNS name resolution.
a. Ensure the line that specifies the IP domain name is correct for your network.
i. For example, the line reads domain delphix.com for servers within Delphix.
b. Ensure that at least one (and preferably two or more) DNS nameserver IP addresses are specified and that they are
reachable via "ping."
i. For example, each line should read nameserver <DNS-nameserver-IP-address> . Running the Linux
command "ping <DNS-nameserver-IP-address>" should complete successfully.
8. Once all of these changes have been made, restart network services on the Linux OS.
a. Run the Linux command service network restart and ensure that it completes successfully.
To ensure the default gateway is persisted after a reboot, add GATEWAY=<gateway-IP-address> to
/etc/sysconfig/network-scripts/ifcfg-eth0

Logging In
1. Access Mission Control by opening a web browser using the IP address or DNS qualified host name. Mission Control does not currently
support SSL connections, so you should use http, not https.
2. Mission Control ships with one generic Delphix Admin User. The User ID is delphix_admin and the password is delphix.
Once logged in as the Delphix Admin User, change your password. You can find instructions to do this in the Change a User Password section
found below.

Navigating the Mission Control Toolbar and User Interface

The Mission Control Toolbar appears after logging into Mission Control. The navigation bar enables you to analyze, manage, and configure data
reporting for a Delphix deployment. The View Report functionality appears on the left-hand side of the toolbar. The configuration, help, and login
buttons appear on the right-hand side of the toolbar. Below is a screenshot of the toolbar key functionality as well as a brief summary of the
functionality available.

Mission Control Toolbar - Version 1.3

Viewing Reports

1015

Delphix User Guide 2016 Delphix

The View Report s tab provides aggregated data across all connected Delphix Engines and presents it as a set of different reports. You can
select these reports from the drop-down menu. Mission Control has automated features that check for updates across all Delphix Engines and
sync these updates into reports every 10 minutes. To refresh the currently displayed report manually, click Refresh.

Reports Tab - Version 1.3.

Interactive reports such as Storage Breakdown and History display interactive graphical representations of historical and current storage usage
across all Delphix Engines you are monitoring. These visualizations of storage and disk capacity enable you to analyze and mediate storage
across Delphix Engines from multiple perspectives.

Graphs tab Version 1.3.

Configure Mission Control

Clicking the configuration icon in the upper right-hand corner of the screen navigates you to four configuration tabs: Reports, Engines, Users,
and System. Read below for more details.

1016

Delphix User Guide 2016 Delphix

Configure Reports
The Reports tab is the central place to configure settings, create scripts, and email reports in Mission Control. There are three sections that
include Report scripts, Script configuration (tunables), and Email reports. To learn more about how to navigate and work in each of these
sections, please continue reading.
To navigate to the Report configuration tab:
1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Reports.

Report Scripts
Enable/disable individual reports to determine which ones are available in the reports drop-down menu
Delete reports
Deleted reports are no longer generated in Mission Control
Upload new reports
This is an experimental feature. Please contact Delphix if you are interested in customizing existing reports or creating new ones.

Script Configuration
Configure tunable parameters for specific reports
Click the field in the value column to make it editable

Report Scripts Section - Version 1.3

Email Reports
Configure email reports which automatically send tabular data to any number of email addresses
Send emails on daily, weekly, or monthly schedules
Customize the way the data is presented in emails by choosing the sort column and limiting the number of rows.

1017

Delphix User Guide 2016 Delphix

To access the Email Reports section, follow the instructions below:

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Reports.
3. Scroll down to Email Reports.

Email Reports Configuration - Version 1.3

Activity Two: Configure, Automate, and Email Mission Control Reports

This activity will walk you through the system and report configuration and automation features that facilitate emailing Mission Control reports in
the Email Reports configuration section. To begin, you will need to navigate the the configuration icon and select system configurations first in
order to enable system connections such as the SMTP server.
1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click System .
3. Scroll down to Email and click Edit Settings .

1018

Delphix User Guide 2016 Delphix

1019

Delphix User Guide 2016 Delphix

Mission Control Configuring Email System - Version 1.3

4. Populate all the fields in the Edit Email Settings as seen below and click Save changes:

Mission Control Email Settings - Version 1.3

5. Now that SMTP has been configured, navigate to the Reports Configuration page and scroll down to Email reports. Follow and complete the
three-step process as illustrated below to begin automating and emailing Mission Control reports.

Mission Control Email Reports Configuration Window - Version 1.3

Required: Click Add Email Report. A series of fields will appear to help guide the configuration and automation of emailing selected Mission
Control reports. The following is a description of each of these fields.
1.

a. The Report field provides a selection of the specific Mission Control report you would like to use for the Email Report function.
Note: Only tabular reports are available for email.
b. Sort by Selection provides a drop down of the column you wish to sort by , which varies based on the report you have selected
above, and whether the results should be ascending or descending.
c. In the Limit the Report To fields, a selection choice appears allowing you to run and email a report with all data rows or to enter
the number of data rows you would like included in the report.
d.

In the Schedule field, fields are provided to select the scheduled day and time that you want the report to be sent.

e. In the Send to field, enter the email addresses to which you want to send the report. Note: Use a comma to separate email
addresses.
Once you have configured all of the fields above, save the information by clicking Add Email Report . The newly added report will appear. You
will then have access to additional features to edit, send a report now, or click the X button to delete the report.
Optional: Click the Edit button when you need to change or enter new information into any of the configuration fields found in the Add Email
Report functionality.
Optional : Click the Send Now button to either:
1. Send a test email report during the process of configuring an email report in order to verify the report settings, or design.
Or
2. Send a one-off email outside of an automated and scheduled email report.

1020

Delphix User Guide 2016 Delphix

2.

Configure Engines
To navigate to the Engines screen, as seen below:
1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Engines .
The Engines tab lists all Delphix Engines that you have added to Mission Control. The Status column shows whether Mission Control is
connected to each Engine; it will prompt a specific error message if it is unable to connect. To remove an engine from Mission Control:
1. Click the X icon next to the engine you wish to delete.

2. In the confirmation dialog, click OK.

Configure Engines Tab - Version 1.3.

Configure Users
To navigate to the Users screen, as seen below.
1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Users .
The Users tab displays the set of user accounts that have permission to access Mission Control. You can assign tags to auditor users to restrict
which Delphix Engines and containers they can see. For more information, refer to the How to Assign Tags activity in a later section.

1021

Delphix User Guide 2016 Delphix

Users Tab - Version 1.3.

Activity Three: Add Delphix Engines to Mission Control

1. Access Mission Control with a supported web browser using its I P address or DNS qualified host name. Supported web browsers
include Chrome 37, IE 11, Safari 7, and Firefox 32.
2. Click the Engines tab in the Mission Control Toolbar.
3. Click Add Engine.
4. In the Hostname field, enter the Delphix Engines IP address or hostname.
5. Enter a username and password. The user must have at least an auditor role on the target Delphix Engine.

1022

Delphix User Guide 2016 Delphix

Adding a Delphix Engine Version 1.3.

Activity Four: Adding Users

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Users.
3. Click Add user.
4. Enter a username and password.
5. Select auditor or admin.
6. Inform the newly-created user of their user ID and password login credentials.

Activity Five: Change a User Password

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Users.
3. Click the name in the upper right-hand corner.
4. Click change password.

1023

Delphix User Guide 2016 Delphix

Search and Run Reports

Activity Six: Search and View a Report
Engine Activity Reports
Health Reports
Source Reports
Storage Reports
VDB Reports
Reports are the heart of Mission Control. Reports gather data that spans all connected Delphix Engines and presents the data in a single location.

Activity Six: Search and View a Report

1. Click View Report.

2. Click the report drop-down menu to reveal a selection of report options, as seen below.
Five new category sections appear to help you quickly locate the report of your choice. These include Engine Activity, Health, Source, Storage,
and VDB.
Reports of interest may include the Storage Summary report found under Storage, allowing you to view, compare, and analyze storage usage
across Delphix Engines. Other useful reports include Active Faults, SnapSync, and Replication Summary. Below is a summary list of all
reporting categories found under View Reports and a description of the reports found under each category.

Running a Report - Version 1.3.

Engine Activity Reports

Audit Log: Provides a view of all actions that have been performed on all Delphix Engines. This includes both user- and system-executed
actions.

1024

Delphix User Guide 2016 Delphix

Audit Log Report Version 1.3.

Bookmarks: Tracks Jet Stream bookmark usage across a jet stream deployment, particularly in relation to storage/capacity, as bookmarks pin
storage on the delphix engine.
Recent Jobs: Covers all jobs across all engines, such as provisioning or refreshing a VDB.
Replication Status: Allows you to validate that replication is running successfully across all Delphix Engines where it has been configured. If
replication is not running successfully, it allows you to determine the cause.

Health Reports
Active Faults: Presents a consolidated view of faults across all Delphix Engines, along with suggested actions (in the Action column) to resolve
the fault. When you have identified and fixed a fault, an administrator can go to the affected engine and mark the fault as resolved through the

1025

Delphix User Guide 2016 Delphix

GUI or CLI.

Active Faults Report Version 1.3.

Engine Summary: A high-level overview report of all Delphix Engines. It contains version and platform information, the number of faults and
recent jobs, and critical alerts for each engine.
Recent Alerts: Alerts are events that have occurred, their severity, and the point in time at which they occurred. The Recent Alerts report
combines the alerts and their associated information across engines.
Replication Status: If you work with multiple Delphix Engines, it can be difficult to keep track of the various replication jobs. This report helps you
determine quickly whether everything is running smoothly or whether a certain replication job is failing.

Replication Status Report Version 1.3

Source Reports
dSource Usage: Shows a list of dSources with the following information for each:
Actual disk capacity the dSource uses
Unvirtualized capacity that is, the disk space that would be required if not using Delphix Engines
Percentage storage saved
Number of VDBs that are currently provisioned from the dSource
SnapSync Summary: Allows you to validate that SnapSync is occurring as expected and to compare the current and average duration of
SnapSync operations. The duration of SnapSync operations may vary based on the size of the database, available network bandwidth, and
database configuration for example, whether change block tracking (CBT) is enabled. You can use this report to easily find the dSources for
which SnapSyncs take the longest.

1026

Delphix User Guide 2016 Delphix

SnapSync Summary Report Version 1.3.

Storage Reports
Storage Breakdown
Using the information displayed with the Total button, you can:
Determine which engines have the most free space and identify good candidates for new dSources/VDBs
Determine which engines have the least free space, identify which engines need additional storage or require storage to be freed, and
identify which engines may require different retention policies
Determine which engines have the most space used by VDBs and take actions such as refreshing VDBs or removing unneeded VDBs
and/or VDB snapshots
Determine which engines have the most space used by dSources and identify source breakdown to see how capacity is used for dSource
data. If needed, you can make appropriate changes to free up space.

1027

Delphix User Guide 2016 Delphix

Using the information displayed with the Source button, you can determine which engines have the most space used for logs and snapshots and
modify retention policies or refresh VDBs to release old snapshots.

Storage Breakdown Report Version 1.3.

Storage History: Clicking the Historical tab summarizes total storage usage of all monitored engines for the past 30 days.
Storage Summary: Shows the total, used, and available storage for each engine, which allows you to identify when you are approaching a
low-storage availability state.

Storage Summary Report Version 1.3.

VDB Reports
VDB Inventory: Shows a consolidated list of all virtual datasets (VDBs and vFiles) that have been provisioned from a data source using the
Delphix Engine. This report contains the same data as the top-level Containers tab. You can use this report to easily identify where each virtual
database is located.

1028

Delphix User Guide 2016 Delphix

VDB Inventory Report Version 1.3.

VDB Refresh Summary: Allows you to verify that refreshes are happening as expected and to compare the current and average duration of
refresh operations.
VDB Usage: Shows a list of VDBs with the following information for each:
Actual disk capacity the VDB uses
Unvirtualized capacity
Percentage of storage saved
Date of most recent refresh operation or, if never refreshed, date when VDB was provisioned

1029

Delphix User Guide 2016 Delphix

1030

Delphix User Guide 2016 Delphix

Filter, Organize, and Extract Reports

Tagging
Activity Seven: Apply Tags
Filtering
Activity Eight: Extracting Data from Reports

Tagging
You can tag Delphix Engines in Mission Control with a set of arbitrary text strings. You can then filter reports to show only data from Delphix
Engines with a certain tag. You can also use tags to restrict auditor users so that they can only view data from Delphix Engines with that tag.

Activity Seven: Apply Tags

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Users.
3. Click the space under the Tag headline.
4. Enter any text string.
5. Click OK.

Applying Tags Version 1.3.

The screenshot below illustrates how to use a tag to filter the kinds of data and reports an Auditor User can access.

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click Users.
3. Click in space under the Tag headline.
4. Enter the tag category configured for the Auditor User.
5. Click OK.

1031

Delphix User Guide 2016 Delphix

Applying Tags to Users - Version 1.3.

Once you apply the tag filter, the Auditor User will only have access to reports and data associated with that tag.

Filtering
Each report contains a free text filter field. Using this filter allows you to search all displayed columns and returns all rows that have at least one
match. Examples of report filtering include:
Identifying certain types of faults
Identifying all assets related to an engine
Locating a virtual database by name

Activity Eight: Extracting Data from Reports

Once you have selected the report you are interested in viewing, you will be able to extract the report data with a variety of options. Extract and
save the report data by clicking Copy, CSV, PDF, or Print on the right-hand side. Click the option of your choice to extract and save the report.
The screenshot below highlights the sequence of steps to extract reports.

Extracting Data From Reports - Version 1.3.

1032

Delphix User Guide 2016 Delphix

Understanding the Graphs Interface

Activity Nine: Viewing Storage Breakdown Reports
Working with Total Storage Graphs
Working with Source Usage Graphs
Activity Ten: Viewing Storage History Reports
The View Report drop-down menu on the Mission Control Toolbar includes interactive graphical representations of historical and current
storage usage across all Delphix Engines you are monitoring.
These include visualizations of Storage Breakdown and Storage History. Storage Breakdown provides different ways of viewing data,
including Total to interact with graphs containing the current total storage on all engines and Source to view the breakdown of disk capacity
currently used for dSource data. Storage History provides a graphical interface to analyze all historical storage data collected by monitored
engines in the past 30 days.
The following activities provide more detail for how to interact with the graphs.

The View Report Drop-Down Menu in the Mission Control Toolbar Version 1.3.

Activity Nine: Viewing Storage Breakdown Reports

Selecting Storage Breakdown allows you to analyze current storage usage by Total and Source.

Working with Total Storage Graphs

Clicking the Total button presents an interactive data visualization of total storage on each Delphix Engine. The bar graphs show the breakdown
of all disk capacity between:
Source The capacity used for dSource data
Virtual The capacity used for VDBs
Free space The amount of available free space on the engine
The Category Legend Key on the right-hand side, shown in the screenshot below, helps you see how your current storage is distributed.

1033

Delphix User Guide 2016 Delphix

Graphical Visualization of Storage Capacity Breakdown for All Delphix Engines - Version 1.3.

To display engines according to a particular category:

1. Click a category in the Category Legend Key.
The engines will appear in order according to the category you chose to prioritize. In the screenshot above, Total has been prioritized.

Using the information displayed with the Total button, you can:
Determine which engines have the most free space and identify good candidates for new dSources/VDBs
Determine which engines have the least free space, identify which engines need additional storage or require storage to be freed, and
identify which engines may require different retention policies
Determine which engines have the most space used by VDBs and take actions such as refreshing VDBs or removing unneeded VDBs
and/or VDB snapshots
Determine which engines have the most space used by dSources and identify source breakdown to see how capacity is used for dSource
data. If needed, you can make appropriate changes to free up space.

Working with Source Usage Graphs

Selecting the Source button presents an interactive data visualization from a source perspective. The bar graphs show how much of each
engines storage space is used by:
Active Source Data The capacity used for current active copy of dSources
Manually Retained Snapshots The capacity held exclusively due to manually retained snapshots
Snapshot Retention The capacity held due to snapshot retention policy, either exclusively or in combination with manual settings
Snapshots for Dependent VDBs The capacity of snapshots held due to VDBs that have been provisioned from them, either
exclusively or in combination with policy or manual settings
Log Retention The capacity held due to LogSync retention policy.
The Category Legend Key on the right-hand side helps you see how your current storage is distributed.

Graphical Visualization of Storage Capacity Breakdown for All Engines by Source, Mission Control Version 1.3.
To display engines according to a particular category:
1. Click a category in the Category Legend Key.
The engines will appear in order according to the category you chose to prioritize. In the screenshot above, Active Source Data has been
prioritized.
Using the information displayed with the Source button, you can determine which engines have the most space used for logs and snapshots and
modify retention policies or refresh VDBs to release old snapshots.

Activity Ten: Viewing Storage History Reports

Clicking the Storage History Report visually summarizes total storage usage of all monitored engines for the past 30 days. In this tab, a line
graph appears with the historical storage data for the selected Delphix Engine(s) and a drop-down list of Delphix Engines from which to choose,
as seen in the screenshot below.

1034

Delphix User Guide 2016 Delphix

Storage History for Top Five Engines, Mission Control Version 1.3.

By default, the above graph shows historical details of the top five engines, based on the most recent data point. However, you can choose which
engines details to display by selecting it from the drop-down menu.
The screenshot below illustrates using the scroll bar at the bottom to hone in on a particular time and date of capacity use. Use your mouse and
hover over interesting points on the graph for specific storage information. A rollover box will appear with specific information.

Specific Historical Storage Capacity Details, Mission Control Version 1.3.

1035

Delphix User Guide 2016 Delphix

Mission Control Maintenance

Managing the Operating System
Activity Eleven: Self-Service Upgrade of Mission Control
Activity Twelve: Generate and Upload MC Support Bundles

Managing the Operating System

Mission Control runs as an open virtual appliance. The underlying operating system, CentOS, can be modified or patched as needed. For best
practices, please refer to the official documentation: https://www.centos.org/docs/
Note: Any changes to files related to Delphix may result in an unusable system. These files are stored in the following locations:
/opt/delphix
/var/delphix
/var/log/delphix
To manage the appliance or the Operation System or to upgrade, you must have root access. The default root password is delphix. You should
change this as soon as possible.
To navigate to the System screen, as seen below:

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click System.
Here you can view the current version of Mission Control.

System Tab - Version 1.3

Activity Eleven: Self-Service Upgrade of Mission Control

When a new version of Mission Control is available, download the upgrade script from Delphix.

1036
1.

Delphix User Guide 2016 Delphix

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click System.
3. Scroll down to the Upgrade section.
4. Click Choose file.
5. Select the upgrade script.
6. Click Upload & Install.

Upgrading Mission Control

Activity Twelve: Generate and Upload MC Support Bundles

You only need to do this when Delphix support requests that you send a Mission Control support bundle.

1. Click the configuration icon

on the right-hand side of the toolbar.

2. Click System.
3. Scroll down to the Support section.
4. Enter the case number if provided by Delphix support.
5. Click Submit.

1037

Delphix User Guide 2016 Delphix

Support for Mission Control

To file support requests from the support portal please go to https://support.delphix.com.
Additional support is available with the Delphix community@ https://community.delphix.com/delphix under the Mission Control category.

1038

Delphix User Guide 2016 Delphix

_JetStream

1039

Delphix User Guide 2016 Delphix

Jet Stream Admin Guide

Table of Contents
Getting Started with Jet Stream
Welcome to Jet Stream
User Roles and Permissions
Login

Jet Stream Concepts

Data Sources
Data Templates
Data Containers
Jet Stream Data Flow

Navigating the Jet Stream Admin Interface

Jet Stream Administrator Home Page
Jet Stream Data Template Management
Jet Stream User Roles and Permissions in Admin App
Jet Stream Data Management User Interface for Delphix Administrators

Understanding Jet Stream User Management

Jet Stream User Management Activities
Creating a Jet Stream User
Assigning a Jet Stream User to a Data Container
User Details Page

Understanding Jet Stream Data Templates

Jet Stream Data Templates: An Overview
Jet Stream Data Template Activities
Creating a Data Template
Setting the Ordering of Data Sources
Managing Data Template Notes
Editing a Data Template's Name
Deleting a Data Template

Understanding How to Manage Data Template Details

Summary
Containers
Sources
Properties

1040

Delphix User Guide 2016 Delphix

Bookmarks
Capacity

Understanding Jet Stream Data Containers

Jet Stream Data Container Overview
Refresh
Restore
Reset
Branch
Activate
Bookmark
Share

Jet Stream Data Container Activities

Configuring Jet Stream Data Containers
Delete a Data Container
Data Management Operations
Start a Data Container
Stop a Data Container

Understanding Bookmarks
Bookmarks Overview
Using Bookmarks in Data Templates

Understanding Jet Stream Usage Management

Jet Stream Usage Management Dashboard Overview
Template Usage Overview
Template Usage Details
User Usage Overview
Template Usage (Containers) Overview
Template Usage (Bookmarks) Overview
Container Usage (Branches) Overview

Resources
Support

1041

Delphix User Guide 2016 Delphix

Getting Started with Jet Stream

Welcome to Jet Stream
The Delphix agile data platform has greatly improved the speed at which end users can get the data that they need. While end users reap the
benefits, they do not typically interact with the Delphix Engine directly, nor are they necessarily even aware that they are using it. End users most
commonly file tickets for data management operations and wait for the tickets to be serviced by their IT organization. Delphix data management
workflows allow database administrators (DBAs) to respond to these tickets much more quickly and reliably, but DBAs are often overloaded, and
resolving high-priority issues takes precedence over requests from users. Requiring interactions between users and IT for every data operation is
inefficient and can lead to unwanted delays.
The goal of Jet Stream is to create a clear separation of IT infrastructure and data management. As with the current Delphix platform, IT
administrators and DBAs continue to control decisions about how resources such as virtual databases (VDBs) and vFiles are allocated. However,
with Jet Stream, administrators can also assign these resources directly to a user. A Jet Stream user has the ability to control what data these
resources should make available, even though the details of the physical resources are hidden from them. This separation of roles empowers Jet
Stream users to get the data they need, when they need it, while providing administrators with the controls to ensure resources are accounted for
appropriately.

User Roles and Permissions

Jet Stream has two types of users:

Admin User
Admin users have full access to all report data and can configure Jet Stream. Additionally, they can use the Delphix data platform to add/delete
Delphix Engines, add/delete reports, add/delete users, change tunable settings, add/delete tags, and create and assign data templates and
containers.

Jet Stream Data User

Jet Stream data users have access to production data provided in a data container. The data container provides these users with a playground in
which to work with data using the Self-Service Toolbar.

Login
1. Access Jet Stream by opening a web browser and using the IP address or DNS qualified host name.
2. Login with the Delphix Admin User ID and Password provided for you.

Jet Stream Admin User Log In, Version 1.0.0

1042

Delphix User Guide 2016 Delphix

Jet Stream Concepts

Data Sources
Data Templates
Data Containers
Jet Stream Data Flow

Data Sources
A data source in Delphix can represent a database, an application, or a set of unstructured files. Delphix administrators configure the Delphix
Engine to link to data sources, which pulls the data of these sources into Delphix. The Delphix Engine will periodically pull in new changes to the
data, based on a specific policy. This, in turn, begins building a custom timeline for each data source. Additionally, the Delphix Engine can rapidly
provision new data sources that are space-efficient copies, allowing users to work in parallel without impacting each other.

Data Templates
Data templates are the backbone of the Jet Stream data container. They are created by you, the Delphix administrator, and consist of the data
sources users need in order to manage their data playground and their testing and/or development environments. Data templates serve as the
parent for a set of data containers that the administrator assigns to Jet Stream users. Additionally, data templates enforce the boundaries for how
data is shared. Data can only be shared directly with other users whose containers were created from the same parent data template.

Data Containers
A Jet Stream data container allows data users to access and manage their data in powerful ways. Their data can consist of application binaries,
supporting information, and even the entire database(s) that underlie it.
A Jet Stream data container allows users to:
Undo any changes to their application data in seconds or minutes
Have immediate access to any version of their data over the course of their project
Share their data with other people on their team, without needing to relinquish control of their own container
Refresh their data from production data without waiting for an overworked DBA
A Jet Stream data container consists of one or more data sources, such as databases, application binaries, or other application data. The user
controls the data made available by these data sources. Just like data sources in a template, changes that the user makes will be tracked,
providing the user with their own data history.
The Jet Stream Data Container Interface lets users view the details and status of their data container and its associated data sources, as well
as manipulating which data is in those sources. The Data Container Interface includes a section called the Data Container Report Panel, which
displays details about each source, including the connection information needed to access it - for example, the java database connectivity (JDBC)
string for a database. This connection of information is persistent and stable for the life of the data container, regardless of what data the
resources are hosting.

Jet Stream Data Flow

The Jet Stream data flow diagram below demonstrates how a Jet Stream data user accesses data sources. Data sources are connected to a
Delphix Engine, which is controlled by the Delphix administrator. The Delphix administrator will connect all data sources that developers and
quality assurance (QA) teams need to a Jet Stream data template. This data template acts as a parent source to create the data containers that
the administrator will assign to Jet Stream data users. Data sources flow from the Delphix Engine into a data template and downstream into a
data container, where a Jet Stream data user or users will use the data sources to complete tasks. The data container acts as a self-contained
testing environment and playground for the Jet Stream data user. Additionally, Jet Stream data users are able to set, bookmark, and share data

1043

Delphix User Guide 2016 Delphix

points in their container with other Jet Stream data users of other data containers, as long as all the data containers were created from the same
parent data template.

JetStream Data Flow, Version 1.0.0

1044

Delphix User Guide 2016 Delphix

Navigating the Jet Stream Admin Interface

The following screenshots provide a roadmap for how to navigate the primary screens and places a user will go within the Jet Stream Admin
Interface. The interface includes screens such as the Jet Stream Administrator Home Page, Jet Stream Data Platform Management, Jet Stream
Users and Permissions, and the Data User Management Interface.

JetStream Delphix Admin User Interface Drop Down Menu, Version 1.0.0

Jet Stream Administrator Home Page

The Jet Stream Administrator Home Page is the home page of Jet Stream once an admin user has selected Jet Stream in the Admin App user
log in dropdown menu. On this page you can add and view existing data templates and data containers. You can also view users, whom you can
then assign to data containers that you create from existing data templates.

JetStream Administrator Home Page, Version 1.0.0

Jet Stream Data Template Management

The Jet Stream Data Template Management page contains a view panel of 6 tiles on the left-hand side of the screen. Each tile reports on a
variety of useful information, such as user activity, data sources, data capacity, specific details about data containers, and data templates. They

1045

Delphix User Guide 2016 Delphix

also help you navigate to areas where you can complete specific tasks, such as creating a new template or container, working with data
timeflows, assigning users to containers, and bookmarking important points in time.

Jet Stream Data Template Management, Version 1.0.0

Jet Stream User Roles and Permissions in Admin App

The Jet Stream User Roles and Permissions Page is found under Manage-Users in the Admin App. Here you can add new Jet Stream users
by selecting the Jet Stream users only in the user details box, as seen in the screenshot below.

JetStream User Roles and Permissions, Version 1.0.0

Jet Stream Data Management User Interface for Delphix Administrators

The Jet Stream Data Management User Interface is the only interface to which Jet Stream data users have access and with which they interact.
The user interface is the environment in which a data user works with data in an assigned data container, using data sources from a data
template.
The user interface is divided into two work areas. The upper half allows the user a workspace to complete tasks using self-service operations. The
lower half provides users with a summary of important details about the data container and offers bookmark management.

1046

Delphix User Guide 2016 Delphix

For more details about how to use this interface, please refer to the Jet Stream Data User Guide. The screenshot below illustrates the data user
interface.

JetStream Data Management User Interface, Version 1.0.0

1047

Delphix User Guide 2016 Delphix

Understanding Jet Stream User Management

Jet Stream User Management Activities
Creating a Jet Stream User
Assigning a Jet Stream User to a Data Container
Case 1: Data Container Creation
Case 2: Changing the Owner of an Existing Data Container
User Details Page

Jet Stream User Management Activities

This document describes the process of creating a Jet Stream user and assigning that user to a data container. It also provides an overview of
the Jet Stream User Details page.

Creating a Jet Stream User

Follow the same process when creating a new user or modifying an existing Delphix user. Jet Stream users do not have access to the existing
admin UI, and they can only access the Jet Stream Data Container page for containers they own.
1. From the Admin App, select Manage.
2. Select Users.

User Manager, Version 1.0.0

3. Click Add User.
a. To make an existing user a Jet Stream user, select the user from the list.
4. Enter the appropriate information.
5. Select theJS-Only User checkbox.

User Creation, Version 1.0.0

6. Press Save.

1048

Delphix User Guide 2016 Delphix

The user is now a Jet Stream user! This means that the user can now login to the Jet Stream user interface, and you can make the user the
owner of a data container.
Notes
Jet Stream users will only be able to access the Jet Stream Data Management page. They will not be able to access the other portions
of the Jet Stream interface, nor the Admin App.
A Delphix admin user cannot be made a JS-Only User. However, admins can still use Jet Stream and own a data container. Admins are
also able to manage all data containers.
A user who owns one or more data containers cannot be deleted.
For the list of data containers that a given user owns, see Jet Stream User Details.
You cannot revoke a user's JS-Only role if they own any data containers.
For the list of data containers that a given user owns, see Jet Stream User Details.

Assigning a Jet Stream User to a Data Container

This section describes how to assign a Jet Stream user (created in the previous section) to a data container. Making a Jet Stream user the owner
of a data container allows them to perform operations such as Refresh on that data container. Jet Stream users cannot see or manipulate data
containers that they do not own. You can either assign a user when creating a new data container, or modify the owner of an existing data
container.

Case 1: Data Container Creation

Case 2: Changing the Owner of an Existing Data Container

1. On the Management Overview page, select the data template from which the data container was provisioned.
2. Click the Containers tile in the left-hand panel.
3. Click the Edit icon next to the name of the data container's owner.

Data Container Editing, Version 1.0.0

4. Select the desired ownerfrom the drop-down list.
a. To remove the current owner, select <None> from the list.
5. When you are finished editing, click the checkmark to the right.
The user you selected is now the owner of the data container and can perform operations on that data container.
Note
A data container can only have a single owner at a time

1049

Delphix User Guide 2016 Delphix

Data Container Editing, Version 1.0.0

User Details Page

This section provides an overview of the Jet Stream User Details page. This page displays graphs related to the user's Jet Stream activity, as
well as a list of all of the data containers that the user owns.
1. On the Management Overview page, click the Users tab.

Management Overview, Version 1.0.0

2. Select the name of the desired user to go to their User Details page.
3. The Operation Counts By Week graph shows the aggregate of all Jet Stream operations performed by this user on all of their
containers. The Container Age Distribution graph shows the average time since a data operation was performed on all of the user's
containers. Each container that the user owns will appear in the Containers section. The user details page looks like this:

1050

Delphix User Guide 2016 Delphix

Jet Stream User Details, version 1.0.0

1051

Delphix User Guide 2016 Delphix

Understanding Jet Stream Data Templates

Jet Stream Data Templates: An Overview
Jet Stream Data Template Activities
Creating a Data Template and Adding Data Sources
Setting the Ordering of Data Sources
Selecting Masked Data Sources
Viewing Data Templates
Managing Data Template Notes
Notes
Editing a Data Template's Name
Deleting a Data Template

Jet Stream Data Templates: An Overview

A Jet Stream data template represents a collection of data sources that you can provision to a Jet Stream user. A data source can be a dSource,
a VDB, or vFiles. These sources can be used in multiple data templates. Once you have created a data template, the set of data sources
associated with it is fixed; you cannot add data sources to an existing template, nor can you remove data sources from it. In addition to data
sources, you can define the set of metadata that is relevant for a given template for example, notes, descriptions, names for sources that are
relevant to an end user, and other configuration details. Once you have created the template, it provides a stencil for provisioning data containers.
This, in turn, enables Jet Stream users to have self-service access to a space-efficient copy of the data sources defined in the data template.

Jet Stream Data Template Activities

Data templates are managed by a Delphix admin. The admin can provision data containers from the data template and assign a data container to
an end user. The admin can also create bookmarks on the data template timeline in order to mark meaningful points in time.
When creating a data template, it is important to consider the set of users who will own data containers provisioned from it. In Jet Stream,
templates effectively define the boundaries of the data that users can share directly with each other. Only owners of data containers created from
the same data template are able to share data using bookmarks.

Creating a Data Template and Adding Data Sources

A data template consists of an arbitrary set of dSources, virtual databases (VDBs), and vFiles. These are created and managed in the Delphix
Admin interface, and can be used in Jet Stream as data sources. You can use any data type supported by the Delphix Engine as a data source in
Jet Stream. For more information, refer to the Linking/Provisioning documentation for the standard Delphix Engine. The following is an example of
the many kinds of data sources you can use to create a data template.

Data Sources, version 1.0.0

When adding data sources to the data template, it is important to consider whether there are any dependencies between them. For example, do
data operations need to begin with a VDB (database) source before the same operation occurs on vFiles (application binary)? Or can data
operations be performed in parallel on each of the data sources? The Jet Stream data source dependencies are by default synced together in
parallel during any data operation, including starting the data container and its sources. When working with specific ordering constraints, such as
with Oracle EBS, you can set up and configure the ordering sequence for each data source.
To create a data template:
1.
1052

Delphix User Guide 2016 Delphix

1. From the drop-down menu in the upper right-hand corner of the Delphix UI, select Jet Stream.

Jet Stream Drop Down, version 1.0.0

2. On the Mgmt Overview page, click Add Template.

Jet Stream Add Data Template, version 1.0.0

This will send you to the Create Data Template page.

3. Enter a Name for the data template.
4. Optionally, enter a description for the data template.
5. Click Add Data Source to add data sources to the template.

Jet Stream Data Template Creation, version 1.0.0

Default vs. Setting the Ordering of Data Sources to a Data Template

1053

Delphix User Guide 2016 Delphix

You have the option of setting the ordering of data sources to a data template. This option minimizes the time needed to complete Jet
Stream operations by running them in parallel on each data source. You cannot change this setting after the data template has been
created. If you want default behavior, do NOT select the box highlighted in the image above.
When your template has ordering constraints, as with Oracle EBS, you must set the startup order for each data source. Check the Set
startup order of data sources box. The Delphix Engine will select the data source with order 1 as the first source started and the last
one to be stopped. The data source with order 2 will be selected as the second source started, and this sequence will continue until the
last data source is selected and ordered. Note that it is not possible to have operations performed in parallel on a subset of data
sources and sequentially on a different subset of data sources.

Setting the Ordering of Data Sources

1. Use the drop-down menu to select the source you want to include. The drop-down menu will display all dSources in the system and all
VDBs and vFiles that are not already assigned to a Jet Stream data container.
2. Enter a Jet Stream-specific name for the data source.
3. Optionally, enter a description in the Notes section. Jet Stream users see a copy of these notes in the data containers they own.
4. Click Add Data Source to continue to add and configure more data sources to the data template. You can remove data sources using
the Delete icon.
5. Click Create to finish creating the data template.

Setting Ordered Data Sources to a Data Template

For Oracle EBS, the vFiles dbTechStack will have order 1, the Oracle database order 2, and the vFiles appsTier order 3. For more
information about EBS, see the EBS documentation.
Once you have created a template, you cannot change the set of data sources in it. Any VDBs or dSources being used as data sources
in Jet Stream will appear with a special badge in the Admin App.

Selecting Masked Data Sources

Prerequisites
Using Jet Stream with Masked Data Sources
Procedure

1054

Delphix User Guide 2016 Delphix

When creating a data template with masked data sources, select the parent masked VDBs as sources to use in the data template.

Viewing Data Templates

As the Delphix Admin user, you can view what sources have been included in a data template. You can distinguish the masked sources from the
unmasked sources by referring to the corresponding data icons, as seen below.

1055

Delphix User Guide 2016 Delphix

1056

Delphix User Guide 2016 Delphix

Example of a template containing both masked and unmasked VDBs

Managing Data Template Notes

After you have created the data template, it will be visible from the Management Overview page under the Data Templates tab, which is the
default tab.

Data Template Details in Jet Stream Management Overview

Notes
Each tile corresponds to a data template and contains high-level information about that data template. For example, the number of child
data containers is visible under the name of the container.
You can search, sort, and filter the data template tiles, making it easy to manage a large number of data templates in Jet Stream.

Jet Stream Search

Editing a Data Template's Name

1. Click the Edit icon next to the data template name.

Data Template Editing, version 1.0.0

2. Enter the new name.
3. Click the checkmark icon to confirm changes.

1057

Delphix User Guide 2016 Delphix

Data Template Editing2, version 1.0.0

Deleting a Data Template

1. Select the data template you want to delete.
2. Click the Delete icon in the lower right-hand corner of the tile.

Data Template Details

Note: If there are any data containers provisioned from the data template, you must remove them before you can delete the data template. See
instructions in the Managing Data Containers section of this guide.

1058

Delphix User Guide 2016 Delphix

Understanding How to Manage Data Template Details

Viewing and Working with the Data Template Details Page
In the Data Management Page, under the Templates Tab, Select and click the data template's name.
This will direct you to the Data Template Details page. You can use this page to view and configure details of an individual data template. It
consists of a number of tiles:
Summary
Containers
Sources
Properties
Bookmarks
Capacity

Summary
Use this tile to get an overview of the data template and its child data containers.

Jet Stream Summary Details, Version 1.0.0

Notes
The graphs labeled Operation Counts By Week and Container Data Age Distribution give a sense of the amount of activity in the data
template over time
Top Checkouts shows at a glance which bookmarks have been used most frequently as part of a Restore or Branch operation
Top Users by Data Operations shows at a glance which users are the most active in Jet Stream

Containers
Use this tile to create, view, and delete child data containers from this data template.

1059

Delphix User Guide 2016 Delphix

Jet Stream Container Details, Version 1.0.0

Sources
In this tile, you can view the data sources that this data template uses. Each data source has a Jet Stream user-visible name, a description, and a
set of properties that consist of arbitrary key/value pairs. This information will be included in the data containers provisioned from this template.

Jet Stream Sources Details, Version 1.0.0

1060

Delphix User Guide 2016 Delphix

Properties
Use this tile to edit the data template's properties. Properties are arbitrary key/value pairs associated with the data template. These values will be
propagated to all data containers provisioned from this template. This provides a way for you to annotate data templates and data containers with
whatever information is relevant to their use case.

Jet Stream Properties Details, Version 1.0.0

Bookmarks
Use this tile to create and manage bookmarks on the data template. A bookmark represents a given point in time that is protected against
retention. Bookmarks created on a data template are visible to all of the data containers provisioned from it. For more details, refer to the
Bookmarks section in the Jet Stream Data User Guide.

Jet Stream Bookmarks Details, Version 1.0.0

1061

Delphix User Guide 2016 Delphix

Capacity
Use this tile to get information about the storage associated with the data template and its child containers.

Jet Stream Capacity Details, Version 1.0.0

1062

Delphix User Guide 2016 Delphix

Understanding Jet Stream Data Containers

Jet Stream Data Container Overview
Refresh
Restore
Reset
Branch
Activate
Bookmark
Share
Jet Stream Data Container Activities
Configuring Jet Stream Data Containers
Add a Data Container
Selecting Masked Data Sources for Data Containers
Prerequisites
Procedure
Delete a Data Container
Data Management Operations
Start a Data Container
Stop a Data Container
Working with Multiple Container Owners
Coordinating Users
What operations could disrupt others using a container?
What processes should I put in place?
Where can I see which user has performed what operation?

Jet Stream Data Container Overview

Data containers are provisioned from data templates by administrators and assigned to a Jet Stream user. A data container represents a socket
that is capable of making any data within the data template accessible. The Jet Stream user controls what data they want to access. Jet Stream
users have effectively been provisioned a set of "physical" resources, such as a database on a host that consumes some set of resources. A data
container is comprised of a VDB or vFiles provisioned from each source in the data template from which it is created. The data container
manages these VDBs, and the data operations performed on a data container will only impact these VDBs. Data containers represent the
separation between IT infrastructure and end users. IT determines the set of VDBs or vFiles to allocate to a data container, and Jet Stream users
determine the data that they want accessible in the containers allocated to them.
Data containers can be used to access any data within a single data template, but not across templates. Jet Stream users have the ability to
populate the data within their data container from any point in time on the data template, the data container's history, or shared bookmarks from
other data containers. Although operations are all accomplished by performing timeflow operations on the underlying VDBs, the data containers
hide the VDBs and their underlying properties from Jet Stream users. None of the data container operations require provisioning additional VDBs;
everything is accomplished using the resources assigned when the data container is created.

Refresh
This is the same basic concept as Refresh in VDBs. In Jet Stream, Refresh will update the data on the active branch of a user's data container.
The user will then have the latest data in the sources of the data template from which the container was provisioned.

Restore
Restore allows a Jet Stream user to update the data on the active branch of their data container to any point in time on the data container, the
data template from which the container was provisioned, or a bookmark. This operation effectively means, "Take me to the data at this time."

Reset
Reset is a simplified version of Restore built to support the notion of "undo." It allows a user to reset the state of their application container to the
latest operation. This can be useful for testing workflows where, after each test, users want to reset the state of their environment.

1063

Delphix User Guide 2016 Delphix

Branch
A Jet Stream branch represents a logical timeline, effectively a task on which a user is working. Only one branch can be active at a time, but a
user can use multiple branches to track logically separate tasks. Jet Stream branches do not require the allocation of a new VDB; instead, they
are comprised of a collection of timeflows within a VDB.

Activate
This allows the user to select which branch they want to be active. Only a single branch within a data container can be active at a time.

Bookmark
This creates a semantic name for a point in time and prevents this data from being removed by the retention policy. Bookmarks can be annotated
with tags to make them easier to search for. In addition to tags, bookmarks allow a user to enter a description of what the bookmark represents.

Share
Bookmarks can be shared, which allows them to be seen by users who own data containers that have been provisioned from the same data
template. This allows users to share data, providing a way for other users to either restore their existing timeline or create a new branch from
these shared points.

Jet Stream Data Container Activities

Configuring Jet Stream Data Containers
A Jet Stream data container is comprised of a set of virtual databases (VDBs), where each VDB is a direct child of the dSource, VDB, or vFiles in
the data template's data sources. Jet Stream does not automatically provision VDBs when creating a data container; a Delphix admin must create
the required VDBs via the existing Admin App. Once the data container has been created, these VDBs are managed exclusively through Jet
Stream.
1.Select the Management Overview page, select a template from which you want to create the data container.This will take you to the Data
Template Page seen below.

Jet Stream Management Overview for Templates

Add a Data Container

1. Click Add Container in the upper right-hand corner of the screen.

1064

Delphix User Guide 2016 Delphix

Jet Stream Details Panel and Dashboard.

This will take you the Create Data Container page.

Jet Stream Data Container Page

2. Enter information about the data container, such as the Name and Description (optional).

1065

Delphix User Guide 2016 Delphix

Data Container Creation, Version 1.0.0

3.. Select the Owners for the data container from the search box. Note: Any Delphix administrator is able to manage all containers, so the
owners should be end users. Refer to the User Management section in this guide for details.

4. It is acceptable to have multiple Owners per each data container. Select the VDBs to use for this container's data sources. The available VDBs
have the following constraints:
They have been provisioned from the dSources/VDBs belonging to the parent data template
They are not already part of another Jet Stream data template or container

Note: If there are no VDBs that meet these constraints, you may see a message informing you that you do not have any compatible VDBs. Click
Create.

1066

Delphix User Guide 2016 Delphix

Jet Stream VDB Warning Alert

Selecting Masked Data Sources for Data Containers

Prerequisites
Using Jet Stream with Masked Data Sources
Selecting Masked Data Sources in Data Templates

Procedure
Once a child masked VDB is selected for the data container, the admin user can see the parent-child relationship as a masked source under data
sources.

Masked Data Sources Parent/Child Relationship

1067

Delphix User Guide 2016 Delphix

Additionally, an admin user can select both masked and unmasked data sources in both Jet Stream templates and data containers.

Selecting Masked and Unmasked Data Sources in a Data Container

Jet Stream users will not know whether the data in their containers and branches is masked or unmasked. All Jet Stream functionality remains the
same regardless of whether a data source is masked or unmasked.

The figure above is an example of a data container with masked data.

Delete a Data Container

By default, all data sources (VDBs and vFiles) in a Jet Stream Data Container are deleted as part of the Jet Stream Data Container deletion

1068

Delphix User Guide 2016 Delphix

process.

When performing the Delete Container operation, you can uncheck the Delete associated VDBs and vFiles box in the dialog window to keep
these data sources intact after the Data Container is deleted.

Data Management Operations

Start a Data Container
Starting a Data Container does the following:
Starts the data sources, This means that each data source listed in the Source Details section of the Data Container page will start
using CPU and network resources on the host system it is running.
Puts a copy of the data from the active branch into those data sources.
On the Self-Service Toolbar, click Start.

Stop a Data Container

Stopping a data container does the following:
If not already done, copies the current data in the data sources into the active branch of the data container
Shuts down the data sources. This means each data source listed in the Source Details section of the Data Container page will stop
using CPU and network resources on the host system.
On the Self-Service Toolbar, click Stop.

Jet Stream Self-Service Toolbar, Version 1.0.0

Jet Stream Self Service Toolbar, Version 1.0.0
Other operations on the data container, such as Stop, Reset, and Refresh, must be performed from the Data Management page:

1069

Delphix User Guide 2016 Delphix

Jet Stream Data Management Interface Shortcut in Jet Stream Data Template, Version 1.0.0

Working with Multiple Container Owners

Administrators may designate multiple Jet Stream users as owners of a single data container. These users all share access to the same data
container; actions taken by one user will impact all users. This means that if User A makes Banch X the active branch, User B will also see
Branch X as the active branch. Because of this, Jet Stream Admins should take steps to avoid confusion when Jet Stream Users are sharing the
same container.

Coordinating Users
Opportunity for disruption increases as more owners are sharing a single container. Sharing a container works best when users can communicate
with each other, such as when they are part of a team, or when they are working with the container at different times. Jet Stream users cannot
see the other users with whom they share the container. Work with Jet Stream users to ensure they know who they are sharing with.

What operations could disrupt others using a container?

Potentially disruptive operations include:
Refresh
Switching active branches
Deleting bookmarks
Creating Branches
Un-sharing bookmarks
Restore
Reset
Staring/ stopping your container

What processes should I put in place?

The more owners you have for a single container, the more processes you should put into place in order to coordinate usage between users.
Each team is different, but strategies include
designating a person to perform certain data operations
saving your work with a bookmark or a creating/ working on a personal branch
being aware of who is using your data container / data before performing operations

Where can I see which user has performed what operation?

1070

Delphix User Guide 2016 Delphix

Which user has performed which action can be seen in the history tab of the data-mgmt page in Jet Stream. Be aware that operations counts in
the template view are are currently counted based on the container, not the user performing the operation.

1071

Delphix User Guide 2016 Delphix

Understanding Bookmarks
Bookmarks Overview
Bookmarks are a way to mark and name a particular moment of data on a timeline. You can restore the active branch's timeline to the moment of
data marked with a bookmark. You can also share bookmarks with other Jet Stream users, which allows them to restore their own active
branches to the moment of data in your container. The data represented by a bookmark is protected and will not be deleted until the bookmark is
deleted. To help manage the space used by this data, users can set an optional expiration date for a bookmark. At the end of the set date, the
bookmark will automatically be deleted. Once created, you can easily locate a bookmark through one of the bookmark viewers in the interface. To
understand how to use bookmarks in Jet Stream, please refer to the Jet Stream Data User Guide.
Using Bookmarks in Data Templates
An admin user can create a bookmark on a template that will then be automatically shared to all containers created from that template.
Additionally, an admin user can create a bookmark on the master template timeline with the point of time you are interested in. The bookmark will
always be saved from retention policies and a new branch can be created from this bookmark.

1072

Delphix User Guide 2016 Delphix

Understanding Jet Stream Usage Management

Jet Stream Usage Management Dashboard Overview
Template Usage Overview
Template Usage Details
Template Usage (Containers) Overview
Template Usage (Bookmarks) Overview
Container Usage (Branches) Overview

Jet Stream Usage Management Dashboard Overview

Jet Stream data templates are comprised of dSources, virtual databases (VDBs), and vFiles. These data sources are controlled by the standard
policies configured in the Admin App of the Delphix Engine. As with existing containers, space will be reclaimed by the retention policy over time.
As retention cleans up historical data, users will no longer be able to use those points in time to restore or branch. In Jet Stream, an admin can
create a bookmark on the data template timeline, which will prevent retention from cleaning up the data that a bookmark references.
Jet Stream data containers are comprised of VDBs provisioned from the sources defined in the data template. Similar to VDBs in the existing
Admin App, data containers' VDBs will share blocks with the source from which they are provisioned. This prevents the referenced data on the
source from being cleaned up by retention. Retention for these VDBs is controlled by the standard Delphix retention policies. As on templates,
bookmarks in data containers will prevent storage from being reclaimed by retention. In addition, Jet Stream will ensure that the latest data on
each Jet Stream branch is never removed.
The Usage pages of the data templates and data containers provide information that can help you understand how storage is being used, how to
reclaim space, and how much space you are able to reclaim.
Usage Overview is a top-level page, along with the Data Mgmt and Mgmt Overview pages. It contains the space usage breakdowns by data
templates and users.

Jet Stream Usage Overview, version 1.0.0

Template Usage Overview

The Template Usage Overview page, seen in the image below, contains the usage breakdowns for data templates and users. The interface is
interactive and allows you to visualize data by interacting with pie charts, bar graphs and tables. The pie chart contains information about the top
10 space consumers; the table at the bottom contains information about all of the templates and/or users.
The table below the charts includes category fields. You can find corresponding descriptions by hovering over the names of the fields in the table:

1073

Delphix User Guide 2016 Delphix

The Template Usage Overview page, Version 4.2

Additionally, the table allows you to sort, navigate, and interact by clicking the field category of interest. For example, to sort the table, click a colu
mn header such as Unvirtualized and the table will sort by that category. To navigate to a particular data template or user, you can click either
the pie slice or the name of the template/user in the table.

Table of templates/users, Version 4.2

The field categories display the following information:
Total The sum of the space used by the data containers provisioned from this data template and by the bookmarks created on this
template. This is the space that will be freed if you delete the template.
Containers The amount of space used by the data containers provisioned from this data template. This is the space that will be freed if
you delete or purge all of the data containers.

1074

Delphix User Guide 2016 Delphix

Bookmarks The amount of space used by the bookmarks on this data template. This is the space that will be freed if you delete all
bookmarks on the template.
Unvirtualized The amount of space that would be used by the data in this template and its child data containers without Delphix
virtualization.
The pie chart and table graphs can help you analyze storage usage information.

Template Usage Details

You can locate the Usage tile at the bottom of the Jet Stream navigation sidebar, as seen in the image below. Usage summaries are available for
templates, containers, and users. For example, when you click the Usage tile on the Template Details page, the usage details you interact with
will be in the context of the selected data template. The same is true when you are navigating the Data Management page for the data
containers, and the User Details page for users.

The Usage tile in the Jet Stream navigation sidebar, Version 4.2

User Usage Overview

The User Usage Overview page provides graphical visualizations of space used by the Jet Stream users assigned to data containers. The two
category fields include the number of containers owned and the amount of space being referenced by a user.

1075

Delphix User Guide 2016 Delphix

The User Usage Overview page, Version 4.2

The field categories display the following information:
Referenced The amount of space used by data containers that are owned by this user. This excludes the space that this user is
sharing with other users.
Containers Owned The number of data containers owned by this user.

Template Usage (Containers) Overview

The Template Usage Details page, as seen below, shows the space used by data containers provisioned from the template and the bookmarks
created on the template.

1076

Delphix User Guide 2016 Delphix

Container Usage, Version 4.2

The stacked bar graph shows information about the top 10 space users. You can re-sort the graph based on the fields in the Sort by legend on
the top right-hand corner of the screen as seen in the image above. For example, if you want to know which data containers are sharing the most
data with others, you can un-select Shared (others data) and Unique by clicking them in the legend.

The Sort by legend, Version 4.2

Note: When the legend items are not selected, their corresponding colored boxes turn gray and the data is removed from the chart. The data and
name will reappear when you re-select by clicking the grayed-out category you want.
The field categories display the following information:
Unique The amount of space that will be freed if you delete this data container. This assumes that also delete underlying data sources.
Shared (others data) The amount of space that cannot be freed on the parent data template (or sibling data containers) because it is
also being referenced by this data container due to Restore or Create Branch operations. The snapshots on the template or sibling
container are what use up the space.

1077

Delphix User Guide 2016 Delphix

Shared (self data) The amount of space that cannot be freed on this data container because it is also being referenced by sibling data
containers due to Restore or Create Branch operations, via shared bookmarks
Unvirtualized The amount of space that would be used by the data in this container without Delphix virtualization

Template Usage (Bookmarks) Overview

As shown in the image below, the Template Usage Details page provides the usage information about bookmarks created on a template. The
primary categories of information include Unique, Shared (others data) and Shared (self data).

Template Usage (Bookmarks), Version 4.2

The field categories display the following information:
Unique The amount of space that will be freed if you delete this bookmark
Shared The amount of space referenced by this bookmark that cannot be freed by deleting this bookmark because it is also referenced
by neighboring bookmarks or branches that have been created or restored from this bookmark
Externally Referenced The amount of space referenced by this bookmark that cannot be freed by deleting this bookmark because it
is also being referenced outside of Jet Stream for example, by a retention policy.

Container Usage (Branches) Overview

The Container Usage Details page shows the usage information about the branches and bookmarks created on a container. The primary
categories of information include Unique, Shared (others data), and Shared (self data).

1078

Delphix User Guide 2016 Delphix

The Container Usage Details page, Version 4.2

The field categories display the following information:
Unique The amount of space that will be freed if you delete this branch
Shared (others data) The amount of space that cannot be freed on the parent data template or sibling branches because it is also
being referenced by this branch due to Restore or Create Branch operations. The snapshots on the template or sibling container are what
use up the space.
Shared (self data) The amount of space that cannot be freed on this branch because it is also being referenced by sibling data
containers due to Restore or Create Branch operations, via shared bookmarks.

1079

Delphix User Guide 2016 Delphix

Resources
Access more resources at http://docs.delphix.com/display/DOCS50/Delphix+Engine+4.1+Documentation

1080

Delphix User Guide 2016 Delphix

Support
Ask the community for support at[ +https://community.delphix.com/delphix+|https://community.delphix.com/delphix]. If you are seeing an issue
that cannot be resolved with help from the community, file a support case as appropriate.

1081

Delphix User Guide 2016 Delphix

Jet Stream Data User Guide

Getting Started
Welcome to Delphix Jet Stream
User Roles and Permissions
Admin User
Jet Stream Data User
Login

Jet Stream User Interface

Data Container Workspace (Top Half of the Jet Stream Interface)
Data Container Workspace
Jet Stream User Login and Settings Drop-Down Menu
Data Container Drop-Down Menu
Data Container View Panel
Data Container Self-Service Toolbar
Branch Timeline
Data Container Report Panel (Bottom Half of the Jet Stream Interface)
Data Container Report Panel
Summary
Sources
History
Bookmarks
Usage

Jet Stream Data Concepts

Understanding Data Sources
Understanding Data Templates
Understanding Data Containers
Jet Stream Data Flow
Understanding Branches
Understanding Timelines
Branch Timeline
Container Timeline
Selecting a Point in Time with the Time Selector
Selecting a Point in Time with the Time Selector Calendar
Understanding the Self-Service Toolbar
Branch Timeline Segments
Working with Multiple Branches and Timelines
Understanding How to Preserve Data in a Point of Time
Understanding Bookmarks
Bookmarks Tab in the Data Container View Panel
Bookmarks Tile in the Data Container Report Panel
Bookmark Sharing Permissions
Bookmark Appearance
Data Container Storage and Retention for Branches and Timelines

Working with Data Operations and Sources in a Container

Getting Started
Activity One: How to Start and Stop a Data Container
Working with a Branch, a Branch Timeline, and the Self-Service Toolbar

1082

Delphix User Guide 2016 Delphix

Activity Two: Using Reset from a Bookmark to Facilitate Destructive Testing

Create a Bookmark
Reset to Data from a Bookmark
Activity Three: Using Refresh to Get the Latest Data From a Data Template
Activity Four: Using Restore to Return Data Back to a Point in Time
Activity Five: Create a New Branch and Switch Between Branches
Active Branch
Activity Six: Rename and/or Delete a Branch
Rename the Default Branch
Delete a Newly-Created Branch
Working with Bookmarks
Activity Seven: Share a Bookmark with Other Jet Stream Users
Share a Bookmark
Un-share a Bookmark
Delete a Bookmark
Activity Eight: Editing Bookmarks
Rename a Bookmark
Edit the Description of a Bookmark
Activity Nine: Filter and View Bookmarks
View Only Your Created Bookmarks
View Bookmarks You Have Shared with Others
View Bookmarks That Others Have Shared with You
Adding Tags To Your Bookmark
Finding Bookmarks

Understanding Jet Stream Usage

Jet Stream Usage Management Dashboard Overview
Container Usage Overview
Bookmarks Usage Overview
Branches Usage Overview

Resources
Support

1083

Delphix User Guide 2016 Delphix

Getting Started
Welcome to Delphix Jet Stream
Jet Stream grants access to the data that users need, whenever they need it. Once users have been assigned a Jet Stream data container, they
can control the data available within it. This means they can refresh to the latest production data, roll back to a previous point in the data
container's timeline, and share data with another Jet Stream user without requiring any involvement from Information Technology or database
administrators (DBAs). Self-service data management allows developers to be more productive while using fewer resources, dramatically
improving operational efficiency.

User Roles and Permissions

Jet Stream has two types of users:

Admin User
Admin users have full access to all report data and can configure Jet Stream. Additionally, they can use the Delphix data platform to add/delete
Delphix Engines, add/delete reports, add/delete users, change tunable settings, add/delete tags, and create and assign data templates and
containers.

Jet Stream Data User

Jet Stream data users have access to production data provided in a data container. The data container provides these users with a playground in
which to work with data using the self-service toolbar.

Login
1. Access Jet Stream by opening a web browser using the IP address or DNS qualified host name.
2. Login with the User ID and Password the Delphix Administrator has provided for you.

1084

Delphix User Guide 2016 Delphix

Jet Stream User Interface

Data Container Workspace (Top Half of the Jet Stream Interface)
Data Container Workspace
Jet Stream User Log In and Settings Drop Down Menu
Data Container Drop Down Menu
Data Container View Panel
Data Container Self-Service Toolbar
Branch Timeline
Data Container Report Panel (Bottom Half of the Jet Stream Interface)
Data Container Report Panel
Summary
Sources
History
Bookmarks
Usage
The Jet Stream User Interface is organized within a single web browser page. The upper half of the screen represents an interactive data
container workspace, and the bottom half of the screen serves as a data container report and management panel. The diagram below provides a
visual orientation along with descriptive narratives to navigate a user to Jet Stream activities and viewing panels.

1085

Delphix User Guide 2016 Delphix

Jet Stream User Interface Glossary, Version 1.0.0

Data Container Workspace (Top Half of the Jet Stream Interface)

1086

Delphix User Guide 2016 Delphix

Jet Stream Data Container Workspace (Top Half), version 1.0.0

Data Container Workspace

The Data Container Workspace contains all the tools, actions, and view panels needed to begin using Jet Stream features. For example,
the workspace allows a user to view the history of their data on a branch, and to refresh, reset, and restore that data.

Jet Stream User Log In and Settings Drop Down Menu

The user login icon in the upper right-hand corner of the screen provides a drop-down menu with options to change your password
and/or log out.

Data Container Drop Down Menu

The Container drop-down menu in the upper right-hand region of the screen allows you to change which data container (or data
template) is shown in the page. Users can own multiple data containers and can select whichever data containers they want to browse.

1087

Delphix User Guide 2016 Delphix

Data Container View Panel

The Data Container View Panel, found on the left-hand side of the screen, is divided into three tabular sections: time, branches, and bo
okmarks. These tabs allow you to find and select data that you are interested in. Based on user selections made in the view panel, the
corresponding branch timeline can change.

Data Container Self-Service Toolbar

The Data Container Self-Service Toolbar allows you to perform tasks and activities with data in the current container, by clicking on the
following user action icons:
Activate will make a branch active
Bookmark will mark an interesting point of data on a branch timeline
Branch will create a branch that supports one task. A branch is a group of data time segments called a "timeline."
Share will share a bookmark with users of other data containers from the same template
Refresh will refresh each source in the data container on a branch timeline to the latest data in the corresponding source of the data
template.
Restore will restore the data to a point in time from the template, the container, or a shared bookmark.
Reset will reset to the last interesting moment of data time on the current data timeline
Stop will stop a data container
Start will start a data container

Branch Timeline

Use this to view the timeline associated with a branch. Note that this only shows the timeline for a single branch. The branch timeline is
how a user interacts with data in the container to mark, stamp, and perform tasks that occur at various points in time.

Data Container Report Panel (Bottom Half of the Jet Stream Interface)

1088

Delphix User Guide 2016 Delphix

Jet Stream Data Container Workspace (Bottom Half), version 1.0.0

Data Container Report Panel

The Data Container Report Panel consists of a series of tile buttons to help report on activities being completed in the Data Container.
They are summarized below as Summary, Sources, History, Bookmarks, and Capacity.

Summary

The Summary tile allows you to see an overview identifying what data sources are in the data container, properties associated with the
data container, and information about operations performed in the data container.

Sources

The Sources tile in the upper left-hand panel bar provides information about each data source, such as the description, name, and
properties that the administrator has placed inside the data container. In particular, you can get the connection information to access them from
here.

History

The History tile reveals a list of actions performed in this data container. Using the filter control on the upper right-hand side of the
page is an easy way to find specific activities completed over time.

Bookmarks

The Bookmarks tile allows you to view and edit details about bookmarks within this data container and bookmarks accessible from it.

Usage

The Usage tile allows you to view information about how much storage capacity this container has used.

1089

Delphix User Guide 2016 Delphix

Jet Stream Data Concepts

Understanding Data Sources
Understanding Data Templates
Understanding Data Containers
Jet Stream Data Flow
Understanding Branches
Understanding Timelines
Branch Timeline
Container Timeline
Selecting a Point in Time with the Time Selector
Selecting a Point in Time with the Time Selector Calendar
Understanding the Self-Service Toolbar
Branch Timeline Segments
Working with Multiple Branches and Timelines
Understanding How to Preserve Data in a Point of Time
Understanding Bookmarks
Bookmarks Tab in the Data Container View Panel
Bookmarks Tile in the Data Container Report Panel
Bookmark Sharing Permissions
Bookmark Appearance
Data Container Storage and Retention for Branches and Timelines

Understanding Data Sources

A data source in Delphix can represent a database, an application, or a set of unstructured files. Delphix administrators configure the Delphix
Engine to link to data sources, which pulls the data of these sources into Delphix. The Delphix Engine will periodically pull in new changes to the
data, based on a specific policy. This, in turn, begins building a custom timeline for each data source. Additionally, the Delphix Engine can rapidly
provision new data sources that are space-efficient copies, allowing users to work in parallel without impacting each other.

Understanding Data Templates

Data templates are the backbone of the Jet Stream data container. They are created by you, the Delphix administrator, and consist of the data
sources users need in order to manage their data playground and their testing and/or development environments. Data templates serve as the
parent for a set of data containers that the administrator assigns to Jet Stream users. Additionally, data templates enforce the boundaries for how
data is shared. Data can only be shared directly with other users whose containers were created from the same parent data template.

Understanding Data Containers

A Jet Stream data container allows data users to access and manage their data in powerful ways. Their data can consist of application binaries,
supporting information, and even the entire database(s) that underlie it.
A Jet Stream data container allows users to:
Undo any changes to their application data in seconds or minutes
Have immediate access to any version of their data over the course of their project
Share their data with other people on their team, without needing to relinquish control of their own container
Refresh their data from production data without waiting for an overworked DBA
A Jet Stream data container consists of one or more data sources, such as databases, application binaries, or other application data. The user
controls the data made available by these data sources. Just like data sources in a template, changes that the user makes will be tracked,
providing the user with their own data history.
The Jet Stream Data Container Interface lets users view the details and status of their data container and its associated data sources, as well
as manipulating which data is in those sources. The Data Container Interface includes a section called the Data Container Report Panel, which
displays details about each source, including the connection information needed to access it - for example, the java database connectivity (JDBC)
string for a database. This connection of information is persistent and stable for the life of the data container, regardless of what data the
resources are hosting.

Jet Stream Data Flow

The Jet Stream data flow diagram below demonstrates how a Jet Stream data user accesses data sources. Data sources are connected to a
Delphix Engine, which is controlled by the Delphix administrator. The Delphix administrator will connect all data sources that developers and

1090

Delphix User Guide 2016 Delphix

quality assurance (QA) teams need to a Jet Stream data template. This data template acts as a parent source to create the data containers that
the administrator will assign to Jet Stream data users. Data sources flow from the Delphix Engine into a data template and downstream into a
data container, where a Jet Stream data user or users will use the data sources to complete tasks. The data container acts as a self-contained
testing environment and playground for the Jet Stream data user. Additionally, Jet Stream data users are able to set, bookmark, and share data
points in their container with other Jet Stream data users of other data containers, as long as all the data containers were created from the same
parent data template.

JetStream Data Flow, Version 1.0.0

Understanding Branches
You can organize data in the data container into task-specific groupings, called "branches." For example, you can use a branch to group all the
data you have used while addressing a particular bug, testing a new feature in an application, or exploring a business analytics scenario. By
default, Jet Stream automatically creates the first branch of source data for you when you login to Jet Stream for the first time. You can view the
default branch and any additional branches that you create over time by clicking the Branch tab. Additionally, to the right of the default branch,
you will see an interconnected branch timeline unique to whichever branch is currently active. The illustration below displays both the default
branch in the Branch tab of the Data Container View Panel and the default branch timeline.

Jet Stream Branch Tab, version 1.0.0

1091

Delphix User Guide 2016 Delphix

Jet Stream Branch View Panel and Branch Timeline, Version 1.0.0
A branch is used to track a logical task, and contains a timeline of the historical data for that task. One branch is the "active" branch, which means
that it is the branch that is currently being updated with new data from the data sources. At any time, you can change which branch is active and
thus change which data is in the associated data sources.

Understanding Timelines
Branch Timeline
A branch timeline acts as a dynamic point-in-time interface for user actions within the branch. You can interact with the source data in the active
branch by using both the branch timeline and icons along the Self-Service Toolbar at specific points in time. Common activities include re-setting
data sources to run a test, refreshing the data container with the most current source data, and bookmarking data to share or track interesting
moments of time along the branch timeline. Users work with one branch at a time to perform a series of actions related to a particular testing or
debugging task such as data updates or starting and stopping data. As you work within your data container, you can create more branches over
time to run or complete separate tasks. Additionally, the data container tracks each branch and the corresponding actions you perform on the
branches. To view the actions completed over the life of a branch, see the container timeline in the Time tab of the Data Container View Panel.

Jet Stream Branch with Timeline Segments Over the Life of the Branch, Version 1.0.0

Container Timeline
The Time tab displays the data container's timeline, which acts as a wall clock of time. It shows continuous real time across all branches and
timeline segments. You can scroll up and down in the container timeline to find the point of time that interests you.

1092

Delphix User Guide 2016 Delphix

Jet Stream Time Tab Timeline, Version 1.0.0

Jet Stream Time Tab Timeline Continued, and Version 1.0.0

Clicking on a point in time in the container timeline will display the corresponding branch timeline capturing any actions performed on the branch.
Additionally, should you need to select a time between tic-marks, you can use the time input field in the time selector on the left side of the
screen.

1093

Delphix User Guide 2016 Delphix

Jet Stream Container Timeline, version 1.0.0

Selecting a Point in Time with the Time Selector

1. In the time selector, type in a date and time with the following format:
Month/Day/Year Hour:Minute:Second{am|pm}. For example: 1/26/2015 1:14:13pm.
2. Press Enter.
The time input field will show the selected time. Now that you have entered the specific time you want, you can use the toolbar to select the data
operation that you want performed at this point in time. Data operations can include Create Bookmark, Create Branch, and Restore.
Note: If you type in an invalid time value, or a time that is out of range, the value you typed in will revert to the previous default that existed before.

Selecting a Point in Time with the Time Selector Calendar

1. Locate and Click on the calendar icon on the left of the input field in the time selector.
2. From the flyout that appears, click the date and select a time that you wish to use.

3. Click on the data operation button on the toolbar that you want to perform at this point in time. Data operations can include Reset, Create
Branch, and Create a Bookmark.

Note: The flyout will not let you pick a date that is before the first point of data time in the container, or after the present moment.

Understanding the Self-Service Toolbar

The Jet Stream Self-Service Toolbar contains self-service action icons that represent available actions a Jet Stream data user can perform. You
can distinguish between available and unavailable icon actions by the use of color on the toolbar. Actions available to you will be red, and actions
that are unavailable will be grey. All actions are dynamic, and availability will change based on how you use and work with data in both the
branches and data container(s) that are assigned to you.

Jet Stream Self-Service Toolbar, Version 1.0.0

For example, your options for actions on the Self-Service Toolbar can change if the branch of the branch timeline you are working with is
activated. In the illustration below, the screen shows a user working in an active branch. Notice the bright red star at the end of the timeline. This
indicates that the branch is active. Also notice which actions are and are not available to the user on the Self-Service Toolbar.

1094

Delphix User Guide 2016 Delphix

Jet Stream Self Service Toolbar with a Point In Time selected on an Active Branch Timeline, Version 1.0.0
The Self-Service Toolbar is dynamic and will change based on tasks a user performs in Jet Stream. These workflows will influence how and
when self service actions become available on the self-service toolbar.

Branch Timeline Segments

A branch timeline with segments is a visual representation of actions taken on a branch timeline over a time span. The timeline segments
represents data in time that is no longer contiguous once a user clicks Create Branch, Refresh, Reset, or Restore on the Self-Service Toolbar.
A vertical bar between each of the segments appears to remind a Jet Stream user that the data in one timeline segment is a completely new data
start. In other words, while the data within one segment is logically contiguous, the data is never contiguous across segments. For example, the
following image above shows a timeline with multiple segments.

Segmented Branch Timeline, Version 1.0.0

As mentioned above, the branch timeline becomes segmented after you have performed a specific action or task, such as Refresh. Based on the
action, two red bubbles will appear in the time segment. The top bubble indicates where the data used for this action came from, for example the
data template, a different branch, or a shared bookmark. The second red bubble appears on the timeline as the actual data stream in a point of
time from the parent data. It appears because of actions such as Refresh, Reset, Restore, Create Branch, and Bookmark. Clicking the second
bubble will show you specific details of the action, such as the specifics of the action including its name, the time the action occurred, and the data
sources used at a point in time. This is illustrated below:

1095

Delphix User Guide 2016 Delphix

Parent Data Sources and Child Data Sources, Version 1.0.0

Working with Multiple Branches and Timelines

As you work in your data container, you can switch between branches at various times to work on resolving a bug or to test a new application
feature. For example, consider what occurs on two different branches in a container:
Branch 1:

Branch 1 Timeline, Version 1.0.0

Branch 2:

Branch 2 Timeline, Version 1.0.0

The Jet Stream user may have actually worked with these branches in the following order over time:
Branch 1: Create a branch and use

1096

Delphix User Guide 2016 Delphix

Branch 2: Create another branch and use

Branch 1: Activate branch, Restore the data source and use

Branch 2: Activate branch and create bookmarks

Branch 2: Refresh the data source from a particular point in time

Branch 2: Reset a branch to the last action (e.g., refresh) on the timeline, and use

In the above illustrations, an individual branch's timeline shows all actions performed on the branch while the branch was active. The active
branch timeline can be interrupted and deactivated when a user chooses to perform actions such as switching to another branch, Create Branch,
Activate, or Stop a data container. Additionally, a user will only be able to view actions on a single branch at a time. A better way to manage
multiple branches is to go to the Time tab in the Data Container View Panel. The Time tab allows you to access the container timeline, which
becomes useful as you toggle back and forth between branches to complete different tasks. The container timeline allows you to view all the
continuous data points of time, with all actions taken on all branches in a single data container.

1097

Delphix User Guide 2016 Delphix

Jet Stream Container Timeline, version 1.0.0

Understanding How to Preserve Data in a Point of Time

The following illustration shows that on 8/27/14, at 9:33:09am, data was reset to the parent data branch (master) at 9:28:48am, capturing data
points from 9:33:06am.

Jet Stream Preserve Data in a Point of Time, version 1.0.0

The black arrows above point to a tick, (representing a point in time) clicked on the branch timeline. This represents the time the Reset action was
performed on the data container. The red arrows point to when time was captured in a data source using the Reset action on the branch timeline.
When clicked, the reset bubble provides more details with a flyout, indicating where the data comes from and the time that the data represents.
Additionally, the reset bubble detail flip card provides additional information about each data source. Specifically, the blue arrows point to the time
used for each data source at this point in the data container. NOTE: This does not show the time that was used for each source that pulled the
data.
Time represented on the branch timeline varies based on many factors. For example, after selecting a specific point in time on the branch
timeline, the Delphix Engine will map that point in time to the closest usable point in time for each data source. Based on the properties of the

1098

Delphix User Guide 2016 Delphix

underlying data sources, these times may be different.Not all data sources track changes at the same granularity, as illustrated below.

Jet Stream Point In Time, version 1.0.0

While a branch timeline can follow a continuous time flow, the data sources being selected for each time segment may not be continuous.

Understanding Bookmarks
Bookmarks are a way to mark and name a particular moment of data on a timeline. Once created, you can easily locate a bookmark through one
of the bookmark viewers in the interface. You can restore the active branch's timeline to the point of data marked with a bookmark. You can also
share bookmarks with other Jet Stream users, which allows them to restore their own active branches to the point of data in your container.

Bookmarks Tab in the Data Container View Panel

The Bookmarks tab is the third tab in the Data Container View Panel within the data container workspace of the Jet Stream interface. It allows
you to find a bookmark that is within your data container and view the branch where the bookmark has been placed.

Jet Stream Bookmark Tab, version 1.0.0

Bookmarks Tile in the Data Container Report Panel

The Bookmarks tile in the Data Container Report Panel allows you to see all bookmarks within your container and all bookmarks that other
users have made available to you. Here you can also edit details about bookmarks, create new branches, and restore the active branch to the
bookmark's point of data time.

1099

Delphix User Guide 2016 Delphix

Jet Stream Bookmark Tile, version 1.0.0

Bookmark Sharing Permissions

When you first create them, bookmarks are private to your data container, but you can share a bookmark with other Jet Stream data users.
Bookmarks that other users have shared with you are called "available" bookmarks.
Your bookmarks will only be shared with Jet Stream data users in data containers created from the same data template. This is because all data
containers created from the same data template have a compatible set of data sources.

Bookmark Appearance
A bookmark that is private

1100

Delphix User Guide 2016 Delphix

A bookmark you have shared

A bookmark that has been shared with you

Data Container Storage and Retention for Branches and Timelines

Bookmarks mark a moment of data. Jet Stream will never automatically delete the data marked by a bookmark. However, Jet Stream will
automatically delete a bookmark with an expiration date set after it has expired. For more information on setting or removing an expiration date
see Working with Data Operations and Sources in a Container. Jet Stream may delete data from any time in the past on your branches,
depending on the retention policies configured by your administrator. If you select a moment of data that has been deleted, the flyout will indicate
that retention has removed data for this point in time.

1101

Delphix User Guide 2016 Delphix

Jet Stream Data Container and Retention, version 1.0.0

1102

Delphix User Guide 2016 Delphix

Working with Data Operations and Sources in a Container

Getting Started
Activity One: How to Start and Stop a Data Container
Working with a Branch, a Branch Timeline, and the Self-Service Toolbar
Activity Two: Using Reset from a Bookmark to Facilitate Destructive Testing
Create a Bookmark
Reset to Data from a Bookmark
Activity Three: Using Refresh to Get the Latest Data From a Data Template
Activity Four: Using Restore to Return Data Back to a Point in Time
Activity Five: Restoring to a Point on the Parent Template
Activity Six: Create a New Branch and Switch Between Branches
Active Branch
Activity Seven: Rename and/or Delete a Branch
Rename the Default Branch
Delete a Created Branch
Working with Bookmarks
Activity Eight: Share a Bookmark with Other Jet Stream Users
Share a Bookmark
Un-share a Bookmark
Delete a Bookmark
Activity Nine: Editing Bookmarks
Rename a Bookmark
Edit the Description of a Bookmark
Remove the expiration date of a Bookmark
Set or update the expiration date of a Bookmark
Activity Ten: Filter and View Bookmarks
View Only Your Created Bookmarks
View Bookmarks You Have Shared with Others
View Bookmarks That Others Have Shared with You
Adding Tags To Your Bookmark
Finding Bookmarks
Working with Multiple Container Owners
Know the Other Owners
What operations could disrupt others using my container?
What should I do?

Getting Started
Data Containers can be shared between multiple Jet Stream users. In this situation, Jet Stream users should coordinate with their co-owners
when performing data operations that could disrupt other user's workflow such as stopping or refreshing the Data Container.

Activity One: How to Start and Stop a Data Container

Starting a Data Container does the following:
Starts the data sources
This means that each data source listed in the Source Details section of the Data Container page will start using CPU and
network resources on the target system it is running on
Makes the data in the active branch available
Once the container has been started, the data represented by the active branch is available
Stopping a Data Container does the following:
Shuts down the data sources
This means each data source listed in the Source Details section of the Data Container page will stop using CPU and network
resources on the target system.
1. To start a Data Container, click Start on the Self-Service Toolbar.
2. To stop a Data Container, click Stop on the Self-Service Toolbar.

1103

Delphix User Guide 2016 Delphix

Working with a Branch, a Branch Timeline, and the Self-Service Toolbar

Activity Two: Using Reset from a Bookmark to Facilitate Destructive Testing
Reset is a Jet Stream data user workflow that is optimized to enable destructive testing. Reset automatically restores the data to the last
operation conducted in the data container, which can include creating a bookmark, resetting, or restoring data. As an example, you can do a
refresh and then get your data into a state required for testing. Once you are satisfied with the state of your data, you can create a bookmark,
which will preserve the data at this point in time.
Afterwards, you can then run destructive tests on the data. When you are done, you can click the Reset icon, which will automatically restore the
state of the container to the last operation in this case, the bookmark. This workflow ensures that each test has a clean copy of the data and is
not impacted by the results of other tests. You only need to create a bookmark and click Reset on the Self-Service Toolbar.

Create a Bookmark
1. Select a Data Point on a branch's timeline.
2. Click the Bookmark icon on the Self-Service Toolbar

3. Type a new name in the Bookmark Window.

Name a Created Bookmark, Version 1.0.0

4. Optionally, fill in a description.
5. Optionally, set an expiration date. The bookmark will be automatically deleted at the end of this day.
6. Optionally, add one or more tags.
These can be used to help filter a set of bookmarks.
7. Click Create.
After the bookmark has been created, you will see the bookmark icon appear on the timeline. When you click the Reset button, all data will be
reset to that point of time.

Reset to Data from a Bookmark

1104

Delphix User Guide 2016 Delphix

1. Click the Reset icon.

This action reflects the moment of data marked by the closest operation bubble (Refresh, Restore, Reset, or Bookmark) into a new
timeline segment on the active branch. It also copies the moment of data into the data sources.

Update Data with Reset, Version 1.0.0

Activity Three: Using Refresh to Get the Latest Data From a Data Template
Start a new timeline segment with the most recent point of data from the Data Container's Data Template.
1. Click the Refresh icon.
Refresh creates a new timeline segment on the active branch. This refreshes each source in the data container to the latest data in the
corresponding source of the data template.

Update Data with Refresh, Version 1.0.0

Activity Four: Using Restore to Return Data Back to a Point in Time

This starts a new timeline segment on the active branch with the selected point of data.
1. Select one of the following:
a. A point of data on a timeline.
b. A bookmark on a timeline.
c. A bookmark under the Bookmarks tile in the Data Container Report Panel.
2. Click the Restore icon.

1105

Delphix User Guide 2016 Delphix

If you restore data back to a point in time on the data template master timeline, Jet Stream will ask you which data container to restore into. It will
then:
Reflect the selected point of data into a new timeline segment on the active branch
Copy the moment of data into the data sources
If the timeline segment on a branch timeline was created by a Restore operation, then the segment starts with the moment of data from the
branch that was selected when the Restore operation was done. This is illustrated below.
Note: The parent branch for this segment can be the same branch of which this segment is a part. It is possible to restore the active branch from
a point in time on the same branch.

Update Data with Restore, Version 1.0.0

Note: The source branch for this segment can be the same branch of which this segment is a part. It is possible to restore the active branch from
a point in time on the same branch.

Activity Five: Restoring to a Point on the Parent Template

Data templates serve as the parent for a set of data containers, and as a Jet stream data user, you have the flexibility to restore your container to
any point on the template.
1. Choose the container tab and select the template above the currently selected container.

1106

Delphix User Guide 2016 Delphix

The branch timeline will now show the timeline for the parent template.
2. Select one of the following:
A point of data on the timeline
A bookmark on the timeline
A bookmark under the Bookmarks tile in the Data Container Report Panel

3. Click the restore icon

4. A dialog will pop up. Use it to select the container you'd like to restore.

1107

Delphix User Guide 2016 Delphix

Activity Six: Create a New Branch and Switch Between Branches

Developers and QA teams can have multiple branches that can represent data from different points in time or different sources. You have many
options for how you create a new branch. These include:
A point of data time on a data timeline within the Jet Stream data container, or
A bookmark bubble on the timeline, or
A bookmark in the Bookmarks tile in the Data Container Report Panel
1. Click the Branch

icon to create a new branch.

2. Enter a name for the new branch.

3. Click OK.
4. Click the Activate icon

in the Self-Service Toolbar.

If the inactive branch is not showing in the data container workspace:

1. Find the branch in the Branch tab.

Selection of Branches in Branch Tab, Version 1.0.0

2. Click the Activate

icon.

3. After a moment, the branch will become active.

Active Branch
Within a single data container, only one branch is active at any given time. The data located at the red star of the active branch's timeline is the

1108

Delphix User Guide 2016 Delphix

newest copy of the data from the data container's data sources.
The active branch is distinguished by a red star, which appears at the far right of the timeline, alongside its name in the Branch Name area, and
in the Branch tab.

Active Branch

Inactive Branch

Activity Seven: Rename and/or Delete a Branch

Rename the Default Branch
1. Select the Default Branch in the Branch tab.
2. Click the Pencil icon to the right of the name.
3. Enter the new name.
4. Click the Checkmark icon.

Delete a Created Branch

1. Select the branch in the Branch tab.

2. Click the Delete icon to the right of the name.

3. Click Delete in the confirmation window that appears.

Working with Bookmarks

Working with bookmarks is an easy way to share data with other Jet Stream users of any container created from the same template. By sharing
with others, you can integrate testing, development and QA needs. For example, in the past if someone found a bug they would have to wait until
it was fixed. But with bookmarks they can simply say "the problem is at this bookmark", they do not have to stop their work while someone tries to
fix the problem. Sharing a bookmark allows users to work with data as they see fit. Bookmarks mark a moment of data. Jet Stream will never
automatically delete the data marked by that bookmark. However, Jet Stream will automatically delete a bookmark with an expiration date set at
the end of that day.

Bookmarks Management in the Data Report View Panel, version 1.0.0

Activity Eight: Share a Bookmark with Other Jet Stream Users

1109

Delphix User Guide 2016 Delphix

Share a Bookmark
1. Select a bookmark by clicking one of the following:
a. The bookmark's bubble on the branch timeline.
b. The Bookmarks tab in the data container workspace.
c. The Bookmarks tile in the Data Container Report Panel.

2. Click the Share

icon

Note: You cannot share a bookmark that you or another user have already shared.

Un-share a Bookmark
1. Select a bookmark by clicking one of the following:
a. The bookmark's bubble on the branch timeline.
b. The Bookmarks tab in the data container workspace.
c. The Bookmarks tile in the Data Container Report Panel.

2. Click the Unshare

icon.

Note: You cannot unshare a bookmark that is already private or a bookmark which someone else has shared.

Delete a Bookmark
1. Select a bookmark by clicking one of the following:
a. The bookmark's bubble on the branch timeline.
b. The Bookmarks tile in the Data Container Report Panel.

2. Click the Delete

icon.

Activity Nine: Editing Bookmarks

Rename a Bookmark
1. Click the Bookmarks tile found in the Data Container Report Panel. A selection of bookmarks will appear based on whether you have
chosen to view private, shared, and/or available bookmarks. Whichever bookmark tile you click, a bookmark tile will appear in the Data
Container Report Panel.
2. In the detail bookmarks window, click the Edit icon to the right of its name.
3. Enter the new name in the edit field and click the checkmark to the right of the field to accept and save the new name.

Edit the Description of a Bookmark

1. Select a bookmark by clicking the Bookmarks tile in the Data Container Report Panel.
2. Click the Edit icon to the right of its name.

Remove the expiration date of a Bookmark

1. Select a bookmark by clicking the Bookmarks tile in the Data Container Report Panel.
2. Click the Edit icon to the right of its name.
3. Uncheck the "Will be deleted after" checkbox and click the checkmark to the right of the date selector.

Set or update the expiration date of a Bookmark

1.
1110

Delphix User Guide 2016 Delphix

1. Select a bookmark by clicking the Bookmarks tile in the Data Container Report Panel.
2. Click the Edit icon to the right of its name.
3. Check the "Will be deleted after" checkbox
4. Pick a new date using the date selector and click the checkmark to the right of the date selector.

Activity Ten: Filter and View Bookmarks

View Only Your Created Bookmarks
In the Bookmarks tile in the Data Container Report Panel, bookmarks that belong to you are shown. To see only your own bookmarks:
1. Click the Bookmarks tile in the Data Container Report Panel.
2. De-select Available.

View Bookmarks You Have Shared with Others

1. Click the Bookmarks tile in the Data Container Report Panel.
2. De-select Private.
3. De-select Available.
4. Only your shared bookmarks will be shown.

View Bookmarks That Others Have Shared with You

1. Click the Bookmarks tile in the Data Container Report Panel.
2. De-select Private.
3. De-select Shared.
4. Select Available.
5. These are the bookmarks that have been shared with you.

Adding Tags To Your Bookmark

1. Click the Bookmarks tile in the Data Container Report Panel.
2. Select the bookmark to which you want to add tags.
3. Click Add a Tag.
4. Enter the tag name.
5. Click the Accept icon.
Your tags will be shown at the bottom of the Bookmarks tile in the Data Container Report Panel.
Note: You can only add tags to bookmarks that you have created.

Finding Bookmarks
In either the Bookmarks tab in the data container workspace or the Bookmarks tile in the Data Container Report Panel:
1. Type into the Filter field.
This will only show bookmarks that have names or tags that match the text you have entered.

Working with Multiple Container Owners

Multiple Jet Stream users can be assigned to be an owner of a single Jet Stream data container. With this comes the ability to share a single Jet
Stream data container amongst a group of people, such as a team. These users all share access to the same data container; actions taken by
one user will impact all users. This means that if User A makes Banch X the active branch, User B will also see Branch X as the active branch.
Here are some tips to help minimize disruptions when sharing a container.

1111

Delphix User Guide 2016 Delphix

Know the Other Owners

Jet Stream users cannot see the other users with whom they share the container. Work with the Jet Stream Administrator to find out who is
sharing your data container.

What operations could disrupt others using my container?

Potentially disruptive operations include:
Refresh
Switching active branches
Deleting bookmarks
Creating Branches
Un-sharing bookmarks
Restore
Reset
Staring/ stopping your container

What should I do?

The more owners you have for a single container, the more processes you should put into place in order to coordinate usage between users.
Each team is different, but strategies include
designating a person to perform certain data operations
saving your work with a bookmark or a creating/ working on a personal branch
being aware of who is using your data container / data before performing operations

1112

Delphix User Guide 2016 Delphix

Understanding Jet Stream Usage

Jet Stream Usage Management Dashboard Overview
Container Usage Overview
Bookmarks Usage Overview
Branches Usage Overview

Jet Stream Usage Management Dashboard Overview

Jet Stream data templates are comprised of dSources, virtual databases (VDBs), and vFiles. These data sources are controlled by the standard
policies configured in the Admin App of the Delphix Engine. As with existing containers, space will be reclaimed by the retention policy over time.
As retention cleans up historical data, users will no longer be able to use those points in time to restore or branch. In Jet Stream, an admin can
create a bookmark on the data template timeline, which will prevent retention from cleaning up the data that a bookmark references.
Jet Stream data containers are comprised of VDBs provisioned from the sources defined in the data template. Similar to VDBs in the existing
Admin App, data containers' VDBs will share blocks with the source from which they are provisioned. This prevents the referenced data on the
source from being cleaned up by retention. Retention for these VDBs is controlled by the standard Delphix retention policies. As on templates,
bookmarks in data containers will prevent storage from being reclaimed by retention. In addition, Jet Stream will ensure that the latest data on
each Jet Stream branch is never removed.
The Usage pages of the data templates and data containers provide information that can help you understand how storage is being used, how to
reclaim space, and how much space you are able to reclaim.
Usage Overview is a top-level page, along with the Data Mgmt and Mgmt Overview pages. It contains the space usage breakdowns by data
templates and users.

Container Usage Overview

The Usage Details page, shows the space used by data containers provisioned from the template and the bookmarks created on the template.

Container Usage, Version 4.2

1113

Delphix User Guide 2016 Delphix

The stacked bar graph shows information about the top 10 space users. You can re-sort the graph based on the fields in the Sort by legend on
the top right-hand corner of the screen as seen in the image above. For example, if you want to know which data containers are sharing the most
data with others, you can un-select Shared (others data) and Unique by clicking them in the legend.

Note: When the legend items are not selected, their corresponding colored boxes turn gray and the data is removed from the chart. The data and
name will reappear when you re-select by click on the preferred grayed-out category.
The field categories display the following information:
Unique The amount of space that will be freed if you delete this data container. This assumes that also delete underlying data
sources.
Shared (others data) The amount of space that cannot be freed on the parent data template (or sibling data containers) because it is
also being referenced by this data container due to Restore or Create Branch operations. The snapshots on the template or sibling
container are what use up the space.
Shared (self data) The amount of space that cannot be freed on this data container because it is also being referenced by sibling data
containers due to Restore or Create Branch operations, via shared bookmarks
Unvirtualized The amount of space that would be used by the data in this container without Delphix virtualization

Bookmarks Usage Overview

As shown in the image above, the Container Usage page provides the usage information about bookmarks created on a template. The primary
categories of information include Unique, Shared (others data), and Shared (self data).

Template Usage (Bookmarks), Version 4.2

The field categories display the following information:
Unique The amount of space that will be freed if you delete this bookmark
Shared The amount of space referenced by this bookmark that cannot be freed by deleting this bookmark because it is also referenced

1114

Delphix User Guide 2016 Delphix

by neighboring bookmarks or branches that have been created or restored from this bookmark
Externally Referenced The amount of space referenced by this bookmark that cannot be freed by deleting this bookmark because it
is also being referenced outside of Jet Stream for example, by a retention policy.

Branches Usage Overview

As detailed in the image above, the Container Usage Details page shows the usage information about the branches and bookmarks created on
a container. The primary categories of information include Unique, Shared (others data), and Shared (self data).

The Container Usage Details page, Version 4.2

The field categories display the following information:
Unique The amount of space that will be freed if you delete this branch
Shared (others data) The amount of space that cannot be freed on the parent data template or sibling branches because it is also
being referenced by this branch due to Restore or Create Branch operations. The snapshots on the template or sibling container are what
use up the space.
Shared (self data) The amount of space that cannot be freed on this branch because it is also being referenced by sibling data
containers due to Restore or Create Branch operations, via shared bookmarks.

1115

Delphix User Guide 2016 Delphix

Jet Stream Resources

Access more resources at http://docs.delphix.com/display/DOCS50/Delphix+Engine+4.1+Documentation

1116

Delphix User Guide 2016 Delphix

Jet Stream Support

Ask the community for support @ {+}https://community.delphix.com/delphix+. If you are seeing an issue that cannot be resolved with help
from the community, contact your in-house Delphix administrator and have them file a support case as appropriate.

1117

Delphix User Guide 2016 Delphix

_Reference

1118

Delphix User Guide 2016 Delphix

Command Line Interface Guide

Command Line Interface Overview
Connecting to the CLI
CLI Contexts
Managing Objects
Managing Properties
Array Properties
Untyped Object Properties
CLI Automation
Delphix Objects
Object Type Hierarchy
Object Names and References
Databases and Environments
Asynchronous Jobs
Command Reference
CLI Help and Display Commands
CLI Context Commands
CLI Object Commands
CLI Property Commands
CLI Miscellaneous Commands
CLI Cookbook: Common Workflows, Tasks, and Examples
CLI Cookbook: Authentication and Users
CLI Cookbook: Configuring Key-Based SSH Authentication for Automation
Third Party SSH Key Generation Example
CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users
CLI Cookbook: System Administration
CLI Cookbook: Configuring A Second Network Interface
CLI Cookbook: Adding A Static Route
CLI Cookbook: Changing the Default Group Name
CLI Cookbook: How to Change a Delphix User Password
CLI Cookbook: Creating Alert Profiles
CLI Cookbook: Retrieve Capacity Information
CLI Cookbook: Hosts and Environments
CLI Cookbook: Adding a UNIX Host
CLI Cookbook: Adding a SQL Server Source Environment
CLI Cookbook: Setting Multiple Addresses for a Target Host
CLI Cookbook: How to Change Environment User
CLI Cookbook: Source Databases and dSources
CLI Cookbook: Detaching and Attaching an Oracle dSource
CLI Cookbook: Disabling LogSync for a dSource
CLI Cookbook: Enabling Oracle Validated Sync
CLI Cookbook: Linking a Microsoft SQL Server Database Loading from a Specific Full Backup of the Source
Database
CLI Cookbook: Linking a Microsoft SQL Server Database Loading from the Last Full Backup of the Source
Database
CLI Cookbook: Linking to a Single Instance Oracle Database
CLI Cookbook: Listing Data Source Sizes
CLI Cookbook: Detaching and Attaching a SQL Server dSource
CLI Cookbook: How to Change Database User Password
CLI Cookbook: VDBs
CLI Cookbook: Changing the SID of Oracle RAC VDBs
CLI Cookbook: Oracle VDB Migration
CLI Cookbook: Provisioning a Single Instance Oracle VDB
CLI Cookbook: Provisioning a SQL Server VDB
CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark
CLI Cookbook: Rolling Forward a VDB
CLI Cookbook: Refresh a VDB from a Specific Timepoint or Latest

1119

Delphix User Guide 2016 Delphix

CLI Cookbook: Repairing a Timeflow

CLI Cookbook: Changing SGA Parameter
CLI Cookbook: Rolling Back a VDB
CLI Cookbook: Creating a VDB Config Template
CLI Cookbook: Creating a Policy
CLI Cookbook: Provisioning a SAP ASE VDB
CLI Cookbook: Taking a Snapshot
CLI Cookbook: Determining the Snapshot used to provision a VDB
CLI Cookbook: Detaching and Attaching a SAP ASE dSource
CLI Cookbook: Replication
CLI Cookbook: Adding a Replication Spec
CLI Cookbook: Deleting a Replication Spec
CLI Cookbook: Failing Over a Namespace
CLI Cookbook: Triggering Immediate Execution of a Replication Spec
CLI Cookbook: JetStream Actions
CLI Cookbook: How to Delete a JetStream Container
CLI Cookbook: How to Delete a JetStream Template

1120

Delphix User Guide 2016 Delphix

Command Line Interface Overview

This topic provides an overview of the Delphix Engine command line interface, and links to additional topics.
The Delphix Engine provides a native command line interface (CLI) accessible over SSH. This CLI provides an interactive layer on top of the
public web service APIs, and is intended for users that wish to automate interactions with the Delphix Engine, or simply prefer a text based
interface. All of the functionality available in the CLI is also available through the public stable web service APIs should more full-featured
automation be required. For more information on automation using the web service APIs, see the Web Service API Guide.
The CLI has an internal help system and supports tab completion to help guide users. Running the help command will display a list of valid
commands and properties, if applicable. Specifying the command or property as an argument to help will display more specific information about
that command or property. This guide serves as an overview of CLI operation and examples of some basic tasks, and is not a reference for all CLI
commands or properties. As the CLI content is identical to the public web services, complete information about particular commands, properties,
or other operations can be found in the API documentation delivered with each server instance, found at:
http://<server>/api
The API documentation is guaranteed to be consistent with the set of APIs exported by that particular server. All of the APIs used by the GUI will
be supported by the CLI, though as of version 3.0 this conversion is still in progress. While all the database and environment APIs are available,
most of the system-oriented APIs (such as those required to do initial setup) will be made available in a later release.
Connecting to the CLI
CLI Contexts
Managing Objects
Managing Properties
Array Properties
Untyped Object Properties
CLI Automation

1121

Delphix User Guide 2016 Delphix

Connecting to the CLI

This topic describes how to connect to the Delphix Engine command line interface.
The CLI is available over SSH or the terminal console on any Delphix Engine version 3.0 or later. To connect, use any SSH client appropriate for
your workstation environment and connect to the Delphix Engine by IP or hostname on the standard SSH port (22). Enter a username for either a
domain or system user followed by the namespace appropriate to that user (either DOMAIN or SYSTEM). For example:
ssh delphix_admin@[email protected]
ssh sysadmin@[email protected]
At the prompt, enter your user password. Once connected, you will be placed at the CLI prompt:

delphix>
While both delphix_admin and sysadmin produce the same prompt once logged in, be aware that the two users have different menus and
different functional areas.

Sysadmin Menu
delphix> ls
Children
network
service
storage
system
user
Operations
version
Operations
version
delphix>

1122

Delphix User Guide 2016 Delphix

Delphix Admin
Menu
delphix> ls
Children
alert
audit
authorization
connectivity
database
environment
fault
group
host
job
namespace
network
policy
replication
repository
service
session
snapshot
source
sourceconfig
system
timeflow
user
Operations
version
delphix>
Individual commands passed as arguments to the SSH client will be interpreted as if they had been read from the terminal. More complex scripts
can be passed as input to the SSH command. When running SSH in non-interactive mode via these mechanisms, the command line prompt will
be suppressed, as will terminal font decorations such as underline and bold.
The CLI is also available from the serial terminal console should the network be unavailable. Consult your VM platform documentation for
information on how to connect to the terminal console. Once connected, log in using your Delphix user credentials just as you would over SSH.
If the management service is unavailable due to a software bug or other problem, the CLI can still be accessed as a system user provided that
user is locally authenticated (not via LDAP) and has logged in at least once before. While in this state, only the system commands are available,
including restart, which will attempt to restart the management service without rebooting the entire server. If this problem persists, please
contact Delphix support.
The topic CLI Cookbook: Configuring Key-Based SSH Authentication for Automation shows an example of how to connect to the CLI using
SSH key exchange instead of the standard password-based authentication.

1123

Delphix User Guide 2016 Delphix

CLI Contexts
This topic explains the concept of contexts within the Delphix Engine command line interface.
The CLI is built on the concept of modal contexts that represent an administrative point for interacting with the web service APIs. These contexts
can be divided into the following types:
Context

Description

Static
Children

These contexts exist for the purpose of navigating between points in the hierarchy, but have no properties of their own and do not
correspond to any server side object. The root context is an example of this, as are most of the top level contexts such as databa
se or group.

Object

These contexts represent an object on the server, either a specific object (such as databases) or system wide state (such as
SMTP configuration). These contexts have properties that can be retrieved via the get command.

Operation

These contexts represent a request to the server. Commands may or may not require input and may or may not change state on
the server, but in all cases require an explicit commit operation to execute the command. When in command context, the prompt
includes a trailing asterisk (*) to indicate that commit or discard is required before exiting the context.

User can move between contents by typing the name of the context. To move to a previous context, the up or back commands can be used. In
addition, the CLI supports UNIX-like aliases for cd and ls, allowing navigation similar to a UNIX filesystem. For more information on these
commands, see the Command Reference section.

1124

Delphix User Guide 2016 Delphix

Managing Objects
This topic describes the use of objects in the Delphix Engine command line interface, and provides a list of the object management operations.
The Delphix Engine represents state through objects. These objects are typically managed through the following operations, covered in more
detail in the Command Reference topics
The topic CLI Cookbook: Changing the Default Group Name illustrates the use of object management commands such as list and get.
Operation

Description

list

For a given object type (represented by a static context such as database), list the objects on the system, optionally constrained
by some set of attributes. Some objects are global to the system and do not support this operation.

select

Select a particular object by name to get properties or perform an operation on the object. See the Delphix Objects section for
more information on object naming.

get

Display all or some of the properties of an object after selecting it.

update

Enter a command context to change one or more properties of an object after selecting. Not all objects support this operation, and
only properties that can be edited are shown when in the update command context.

create

Create a new instance of the object type from the root static context. Not all objects can be created in this simplified fashion.
Databases, for example, are created through the link and provision commands.

delete

Deletes an object that has been selected. Not all objects can be deleted.

In contexts where there are multiple objects of a given type, the list command can be used to display available objects, and the select
command can select an object for subsequent operation.
When listing objects, each context has its own set of default columns to display. The display option can be used to control what columns are
displayed to the user. This is a comma-separated list of property names as they would be retrieved by the get command. It is possible to specify
properties that do not exist in order to accommodate lists of objects of varying types, and untyped objects.
The topic CLI Cookbook: Listing Data Source Sizes provide an example of using the list command.

1125

Delphix User Guide 2016 Delphix

Managing Properties
This topic describes the use of properties in relation to objects in the Delphix Engine command line interface.
Object properties are represented as a hierarchy of typed name/value pairs. The get command by itself will display the complete hierarchy for a
particular object. This hierarchy is displayed with each nested object indented by an additional level. The set of available properties depends on
the command context, and may change if the type of an object is changed.

Property State
Properties are typically set to a specific value, but they can also be unset. Unset properties indicate there is no known value, either because it
hasnt been provided yet, or it has been explicitly removed. Properties in this state are displayed via the following means:
(unset) The property is not currently set. It may never have been given a value or it may have been explicitly unset through the unse
t command.
(required) This has the same underlying semantics as (unset), but indicates that the property must be set before the current
command can be committed. Failure do so will result in a validation error at the time the commit operation is attempted. Required
properties are displayed in bold.
In addition, all objects have a default state when in command context. A property that has been modified is noted with an asterisk ( *), and can be
reverted to its default state through the revert command.
When updating properties, only those properties are sent to the server. The exception is arrays and untyped objects, covered in Array Properties
and Untyped Object Properties. These objects are always sent in their entirety, so changing any one element will send the entire object.

Basic Properties
Most properties are displayed and input as a string, though the underlying type may be more specific. The following are some of the basic types:
String An arbitrary string. This may be subject to additional validation (such as an IP address) that is enforced at the time the property
is set.
Number An integer number.
Boolean Either true or false.
Enumeration A string that must be chosen from a known set of options.

Nested Properties
Some properties are in fact other objects, and are represented as a nested set of properties. These properties can be manipulated in one of two
ways: by specifying a dot-delimited name, or changing the context via the edit command.
A dot (.) in a property name indicates that the portion to the left of the dot is the parent object name, and the portion to the right is a child of that
object. For example, sourcingPolicy.logsyncDisabled denotes the logsyncDisabled property within the sourcingPolicy property.
These dots can be arbitrarily nested. An alternative syntax of using brackets to enclose property names (sourcingPolicy[logsyncDisabled
]) is also supported for familiarity with other programming languages.
The edit command, in contrast, will change the current context such that all properties are relative to the specified object. This can be useful
when changing many nested properties at once, or when the complete set of properties can be confusing to manage all at once.
The topic CLI Cookbook: Disabling LogSync for a dSource provides an example of manipulating nested properties.

1126

Delphix User Guide 2016 Delphix

Array Properties
This topic describes the use of array properties in the Delphix Engine command line interface.
Some Delphix objects represent properties as arrays. Arrays are effectively objects whose namespace is a contiguous set of integers. While they
behave like objects and their properties can be referenced via the same object property notation, they differ in several key areas.
Arrays can be divided into two types: arrays of primitive types (strings, integers, etc.) and arrays of objects. Arrays of objects can be managed like
other objects via nested property names and the edit command, but differ in the following respects:
When an array element is unset, it removes the element from the array and shifts all other elements down to preserve the contiguous
index space.
New array elements can only be appended to the end of the array by specifying an index that is one more than the maximum index of the
array.
When displaying a property that is an array, if the length is greater than 3, then it is displayed only as [ ]. The complete contents of
the array can be displayed by getting or editing that particular property.
Arrays of primitive types can be managed as arrays of objects, but also support an inline notation using comma-separated notation. This allows
single-element arrays to be set as a standard property, and for arrays of strings to be set on a single line instead of having to edit each element.
Regardless of element type, arrays are sent as complete objects when updated. When any array element is changed and subsequently
committed, the complete array is sent to the server. When a single array element is reverted, the entire contents of the array are reverted.
The topic CLI Cookbook: Setting Multiple Addresses for a Target Host provides an example of working with a property that is an array of
strings.

1127

Delphix User Guide 2016 Delphix

Untyped Object Properties

This topic describes the use of the type field in the Delphix Engine command line interface object model, and the use of untyped objects.,
Most Delphix objects are typed, meaning they have a type field that controls what properties are available and their types. Object types and their
associated hierarchy are described in more detail in the topic Object Type Hierarchy topic. In contrast, some properties are untyped objects,
which means that there are no constraints on the property namespace, and all properties are plain strings. These objects are used for database
configuration templates and other scenarios where the property namespace is unbounded or under the control of the user.
Untyped objects are always sent in their entirety when making updates. This means that when any one value is changed and then committed, all
values are sent. In addition, when reverting a single value within an untyped object, the entire parent object is reverted to its default state.

1128

Delphix User Guide 2016 Delphix

CLI Automation
This topic describes using automation with both the Delphix Engine command line interface (CLI) and the web service API.
All functionality is available in both, because the CLI is built upon the web services API. The CLI enables you to create scripts for simple
automation, and it is a useful aid in the development of more complex code which uses the web service API .

Using the CLI for Simple Scripts

For simple automation, you can build routines which make CLI calls through SSH.
This snippet lists all environment names. It leverages the SSH key exchange explained in CLI Cookbook: Configuring Key-Based SSH
Authentication for Automation, so that no password is required for the user named "automation".

DELPHIX_ENGINE=172.16.180.33
SSH_CMD="ssh automation@${DELPHIX_ENGINE}"

${SSH_CMD}

"cd host; list display=name"

Backward Compatibility
Both the CLI and web services API are versioned to support backwards compatibility. Future Delphix versions are guaranteed to support clients
that explicitly set a version provided the major version identifier is compatible. For more information, see the Web Service API Guide . The CLI
will always connect with the latest version, but the version command can be used to both display the current version and explicitly bind to a
supported version.
Users building a stable set of scripts can run version to get the current version. Scripts can then run the version <id> command to
guarantee that their scripts will be supported on future versions. For more information on the different API versions and how they map to Delphix
versions, see the API Version Information section.

Using version command to create a stable script for Delphix 4.2.1.0 (API Version 1.5.0)
DELPHIX_ENGINE=172.16.180.33
SSH_CMD="ssh automation@${DELPHIX_ENGINE}"

${SSH_CMD}

"version 1.5.0; cd host; list display=name"

Parsing CLI Output

The default text output of the CLI is unstable. Any attempt to parse the output is certain to run into difficulties in repeatable results for unknown
input, as well as instability as the text output is changed in subsequent releases. Column headings, column order, and number of columns will
change in subsequent releases.
You can specify a version in your scripts to counteract this, but you will not be able to take advantage of new features and fixes.

CLI as a Development Tool for Complex Automation

While the CLI is useful for simple automation tasks, it can be slow and overly complicated due to the many round trips needed to control the
automation logic. For example, to disable all the environments for an engine, you could write a script which lists the environments and modifies
each one:

1129

Delphix User Guide 2016 Delphix

DELPHIX_ENGINE=172.16.180.33
SSH_CMD="ssh automation@${DELPHIX_ENGINE}"
env_array=(`${SSH_CMD} "version 1.5.0; cd environment; list display=name" | grep -v
NAME` )
for i in "${env_array[@]}"
do
${SSH_CMD} "version 1.5.0; cd environment; select $i; disable; commit"
done
This script works, but it will be slow on systems with many environments, since each SSH command will start a new session.
The web service APIs are superior when performing many operations as a single logical unit. The web service APIs also provide substantially
more data with a single call than what is shown in the CLI output, which can greatly simplify your code and avoid multiple round trips.
However, the input and output of web service API calls is JSON data, and it can be difficult to quickly determine what the input and output will look
like.
For this reason, the CLI provides two options which can greatly assist you in the development of complex automations: JSON Output and Tracin
g.
(setopt format=json) changes the CLI to output of all results to parseable JSON (javascript object notation). This is the fastest and easiest
way to quickly see what the JSON output will look like when executed via the Web Service APIs. The JSON format has wide support in a variety
of programming languages; see http://www.json.org for more information.
(setopt trace=true) will display the underlying HTTP calls being made with each operation and their JSON payload. This allows you to
determine the GET and POST calls, and their JSON payloads, which perform the actions that you need to power your automation.
(setopt format=text) changes the CLI back into its regular output mode. (setopt trace=false) turns off the trace display.

Using both options will show the JSON output twice

The fastest way to develop complex automation is to experiment with the CLI and copy the underlying API calls to a
custom system for better control over behavior.

1130

Delphix User Guide 2016 Delphix

delphix421> setopt trace=true

delphix421> cd user
delphix421 user> create
delphix421 user create *> ls
Properties
type: User
name: (required)
authenticationType: (unset)
credential: (unset)
..... (Output Truncated) .....
userType: DOMAIN
workPhoneNumber: (unset)
delphix421 user create *> set name=Jose
delphix421 user create *> set authenticationType=NATIVE
delphix421 user create *> set credential.password=Password1
delphix421 user create *> commit;
=== POST /resources/json/delphix/user ===
{
"type": "User",
"name": "Jose",
"authenticationType": "NATIVE",
"credential": {
"type": "PasswordCredential",
"password": "Password1"
}
}
=== RESPONSE ===
{
"type": "OKResult",
"status": "OK",
"result": "USER-35",
"job": null,
"action": "ACTION-107"
}
Using the output above, you can see that to create a user you must use the URL "http://myengine/resources/json/delphix/user". You will use a
POST command and pass a JSON payload which looks like the above. You will get a JSON response like the above, and can validate that the
status is "OK".

1131

Delphix User Guide 2016 Delphix

Delphix Objects
These topics describe the object model for the Delphix Engine command line interface.
The Delphix object model is a flexible system for describing arbitrary hierarchies and relationships of objects. In order to enable current and future
functionality of the system, the relationship between objects is not always immediately obvious. The CLI is merely a veneer atop the web services
layer to ensure that the full complement of functionality expressed by the API is always available, but this requires users to have some
understanding of how objects are represented in the system.
Object Type Hierarchy
Object Names and References
Databases and Environments
Asynchronous Jobs

1132

Delphix User Guide 2016 Delphix

Object Type Hierarchy

This topic describes the object type hierarchy for the Delphix Engine command line interface.
All Delphix objects have an associated type. This type determines what properties are available for a particular object, the format of those
properties, and controls how the system interprets objects and commands. The type hierarchy uses polymorphic inheritance to allow for common
properties and behavior to be defined at a single point, while permitting dramatically different types of objects to co-exist without requiring a
completely separate API for each. For example, the SourceConfig object is the base type for all external database configurations, but it has
children that include OracleSIConfig and OracleRACConfig types that refer to single instance and RAC databases, respectively.
When specifying input types, the system will attempt to determine types appropriate for the current operation, but there are times when the type
must be explicitly set, either because the operation supports multiple possible inputs, or the object can embed an abstract type. In these cases, it
may be necessary to explicitly set the type property. Setting the type may change the set of visible properties and the resulting validation that is
performed, but it will not affect any properties that are already set.

1133

Delphix User Guide 2016 Delphix

Object Names and References

This topic describes the use of object names and references in the Delphix Engine command line interface.
Most Delphix objects are persistent objects in that they have a well-known identity on the server and associated persistent state. The exceptions
are objects used only as input to other operations, or global objects that have persistent state but dont require any explicit identity since they
always exist.
Persistent objects have both a name and a reference. The reference is the canonical identifier for the object, and remains valid even if the object
is renamed on the server. It is an opaque token that should never be interpreted by the client; the format may change in future releases though
backwards compatibility with current references will be maintained. All web service APIs operate using references. References can be used in the
CLI when selecting objects, but given that they are a programmatically generated internal concept, they are difficult for most users to use.
The object name, on the other hand, is a much more convenient way to refer to objects, but suffers from the fact that it is not guaranteed to be
globally unique. When displaying or setting references, the CLI will convert to or from the canonical name based on the type of the reference and
the current set of objects on the system. The canonical name has the form:
<Type>:/<Parent>/<Object>@<Namespace>
The type, parent, and namespace are only included if the local object name conflicts with other objects on the system that would otherwise be
valid for the given type specification. Not all objects have names relative to their parent; groups, environments, users, and many other objects are
globally unique on the system. This best fit method is used both when displaying references as well as when setting properties that are
references. If the given name potentially matches multiple objects when attempting to set a reference property, then an error is displayed that
includes a list of possible names to clarify which object is being referred to. The conversion from reference to name on display only happens with
text output format. When the output format is JSON, the raw content is displayed (including the local name) and it is up to the consumer to format
names appropriately based on their semantics. The conversion from name to reference when setting properties always occurs. Consumers can
use references, optionally prefixed with a backtick (`) character to signify they are references in the unlikely event that someone has created an
object with the same name as a valid reference.
Providing unique names for objects without the use of forward slashes ('/') and at signs ('@') will provide the simplest CLI experience
when referencing objects.
Here are some scenarios for databases and groups and their resulting behavior:
No conflicting database name
The local name will be used when displaying references to the object, and can be used when setting references:
set container=example
Databases with the same name in different groups
The parent group name must be used when displaying references to the object and when setting references to the object:
set container=group1/example
Databases with the same name in different namespaces
The namespace name must be used when displaying references to the object and when setting references to the object:
set container=example@namespace
Objects of different types but with the same name
This conflict is exceptionally rare, as the reference context typically constrains the set of possible objects to be a single type, but there are cases
(such as alerts, or policy targets) that can be applied to any object. In these cases, the type name must be included to uniquely identify the object:
set target=Container:/group1/example
In the event that one of the named components contains a slash (/) or an at sign ('@'), single quotes must be used to disambiguate the name
from its parent or namespace.

1134

Delphix User Guide 2016 Delphix

Databases and Environments

This topic describes the relationship between database container objects and environments in the Delphix Engine object model.
The core Delphix objects revolve around the notion of environments and databases, known at the API layer as containers. Understanding how
these objects relate to each other is crucial to operating effectively within the CLI. This section provides an overview of these objects; for more
information about a particular representation such as Oracle RAC, see the Web Service API Guide.

Environment Components
An environment is the root of the representation of external state that manages database instances. An environment could be a single host (Unix
HostEnvironment) or an Oracle cluster (OracleClusterEnvironment). Environments exist to contain repositories, and each environment
may have any number of repositories associated with it. A repository is the entity that contains database instances. Repositories are typically
installation directories (OracleInstall) within an environment. Within each repository of any number of SourceConfig objects, which
represent known database instances. The source config exists independent of Delphix, and could represent a possible dSource (in which case
there is no associated database object), or could be managed entirely by Delphix (for VDBs). The source config contains intrinsic properties of the
database instance, while the source (described below) contains information specific to Delphix and only exists when the source config is linked to
a dSource or VDB.
Most environment objects are created through the act of discovery. By specifying a host, Delphix will attempt to automatically discover all
environments, repositories, and source configs. These objects can also be added manually after the fact in cases where discovery fails.
The environment hierarchy can be represented this way:

The generic type is listed in the top portion of each box, with an example of the Oracle single instance objects in the lower portion of each box.
Each of these objects can contain multiple child objects with it.

Database Components
The core of all databases within Delphix is the Container that contains all the physical data associated with the database, whether it is a
dSource or VDB. Within each container is a Timeflow, which represents a single timeline of change within the database history. Currently, a
container can only have one timeflow, though this limitation may be relaxed in a future release. Within a timeflow are two important object: Timef
lowSnapshot objects and TimeflowRange objects. Timeflow ranges represent the provisionable ranges within the history of the timeflow, while
timeflow snapshot represent a point at which at snapshot was taken and therefore more likely to provision in a short amount of time. The resulting
data hierarchy can be represented this way:

1135

Delphix User Guide 2016 Delphix

Each container may be associated with a Source. A source is the Delphix representation of an external database when it is associated with a
container, and contains information specific to managing that source. Not all source configs within an environment have a source associated with
them (as is the case with linkable databases), but all sources must have a source config. Containers may have no sources associated with them if
they are unlined; sources can be manually attached at a later point. Currently, each container can have at most once source associated with it,
though this may change in a future release.

1136

Delphix User Guide 2016 Delphix

Asynchronous Jobs
This topic describes conditions under which command line interface operations may spawn jobs that run in the background, and using the wait o
ption to wait for job completion.
Not all operations can be performed in the context of a single web service API call. For cases where there is a long running operation that cannot
be executed quickly and transactionally, a job may be dispatched to do the remaining work in the background. For more information on jobs and
their semantics, see the topic Viewing Action Status. Within the CLI, any command can potentially result in an asynchronous operation. The
default behavior is to wait for any such job to complete, and display its progress in the CLI.
In the event that you do not want to wait for the operation to complete, the global wait option can be set (setopt wait=false). If disabled,
the CLI will display the reference to any job that was dispatched, but not wait for it to complete.

1137

Delphix User Guide 2016 Delphix

Command Reference
These topics describes the core built-in commands within the CLI. It is not an exhaustive list of all commands in all contexts. For object or type
specific commands, consult the API documentation.
CLI Help and Display Commands
CLI Context Commands
CLI Object Commands
CLI Property Commands
CLI Miscellaneous Commands

1138

Delphix User Guide 2016 Delphix

CLI Help and Display Commands

This topic describes help and display commands for the Delphix Engine command line interface.
Command

Description

children

Display all statically defined children valid for the current context. These children can be targets of the cd command.

commands

Display all build in commands valid for this context.

help

Display all commands and properties valid for the current context. Specifying a command or property will provide more
information about that command or object. When nested properties are present, only top-level properties are displayed by
default, though specifying a particular property will display the entire hierarchy.

ls

Display children, commands, objects, and operations valid in the current context. Only those sections that are relevant in the
current context are displayed.

operations

Display available context-specific operations. These operations require an explicit commit command to execute the operation,
or discard to abort it.

1139

Delphix User Guide 2016 Delphix

CLI Context Commands

This topic describes context commands for the Delphix Engine command line interface.
Command

Description

back

Return to the previous visited valid context. This history only tracks contexts that were actually visited, so running database exa
mple followed by back will return you to the root context, not the database (because the two were executed as part of one action
and never actually visited). If a previous context was deleted or is no longer valid, this command will skip over it.

cd

Switch to the given child. This is identical to typing the name of the child itself, but also support UNIX-style directory structures,
such as / and ... This allows for contexts to be chained such as cd ../database/template.

history

Display the history of input to the shell. The shell supports the ability to move back and forth in the history using the up and down
arrows.

up

This is an alias for cd .. for the benefit of those less familiar with UNIX filesystem navigation. Unlike back, which only returns to
the previous context only if it was visited, and may return to a child context, this command will always return to the immediate
parent context.

1140

Delphix User Guide 2016 Delphix

CLI Object Commands

This topic describes object commands for the Delphix Engine Command Line interface.
Command

Description

list

List all objects of a particular type when in the appropriate root context. Different contexts may support different options to the list
command to constrain the output; run help list to see possibilities.

select

Select an object by name within a list.

1141

Delphix User Guide 2016 Delphix

CLI Property Commands

This topic describes property commands for the Delphix Engine command line interface.
Command

Description

commit

When in operation context, commit the changes and execute the operation.

discard

When in operation context, discard any changes and abort the operation.

edit

Change the current context to be relative to a particular object property when in operation context.

get

Get all properties (with no arguments) or a particular property of the current object.

revert

Revert a particular property to its default value, either the value of the underlying object during an update, or the default command
input value.

set

Set the value of one or more properties. These properties can be specified as name=value, or as simply the property name.
When only the property name is specified the CLI will prompt for the value to use, optionally obscuring the input if the property is a
password.

unset

Clear the current value of a property. This is not the same as reverting the property, though this can have semantically identical
behavior in the case that the default value is unset.

1142

Delphix User Guide 2016 Delphix

CLI Miscellaneous Commands

This topic describes miscellaneous commands for the Delphix Engine command line interface.
Command

Description

echo

Print the input arguments.

exit

Exit from the current CLI session. This is equivalent to sending the EOF control character (typically Ctrl-D) or closing your client
SSH application.

getopt

Get the current value of a global configuration option. The list of global options can be retrieved by running help getopt, but
include options for controlling JSON output (format), tracing HTTP calls (trace), and enabling synchronous job semantics (wai
t).

setopt

Set the value of a global configuration option.

version

Display the current API version or bind to a particular version. See the CLI Automation section for more information.

1143

Delphix User Guide 2016 Delphix

CLI Cookbook: Common Workflows, Tasks, and Examples

This section walks through some of the basic command line interface workflows to add an environment, link to a database, provision a new copy
of a database, as well as a few other common operations. This is not meant to be an exhaustive list of possible workflows or cover every possible
linking or provisioning scenario. The built-in API documentation should be used once the basics are understood.
Case Sensitivity
All CLI parameter names and variables submitted (dSource, environment name, listener, etc) are case sensitive. For example, fullba
ckupUUID is incorrect and will generate an error, while fullBackupUUID is correct.

CLI Cookbook: Authentication and Users

CLI Cookbook: System Administration
CLI Cookbook: Hosts and Environments
CLI Cookbook: Source Databases and dSources
CLI Cookbook: VDBs
CLI Cookbook: Replication
CLI Cookbook: JetStream Actions

1144

Delphix User Guide 2016 Delphix

CLI Cookbook: Authentication and Users

These topics describe command line interface procedures for authentication and managing users.
CLI Cookbook: Configuring Key-Based SSH Authentication for Automation
CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users

1145

Delphix User Guide 2016 Delphix

CLI Cookbook: Configuring Key-Based SSH Authentication for Automation

This topic describes how to use CLI commands to configure individual users with SSH keys to allow for password-less authentication from a
remote host to the CLI in an automated environment.
What is SSH Key-based Authentication?
Procedure

What is SSH Key-based Authentication?

Secure SHell (SSH) is a connection method used to log into UNIX or Linux servers remotely. With Delphix, is it used to connect to the Delphix
Command Line Interface (CLI) from a remote computer. This normally requires a password on each connection; however, it is possible to use
Key-based Authentication to avoid the password requirement and allow automation of Delphix commands.
Key-based Authentication relies on a public/private key pair generated on the client system. The private key allows access to any server
acknowledging the matching public key as being authorized to login. In order to configure this, a public/private key pair must be created, and the
resulting public key should be added to the Delphix server using the CLI.

Procedure
1. Consult your client documentation for information on generating a public/private key pair. The ssh-keygen program is typical on UNIX
platforms. If you need details on ssh-keygen usage or have unique requirements (such as named RSA keys), see Third Party SSH Key
Generation Example. If you already have a public/private key pair generated on your system, you can skip to step 2.
2. Connect as the user you wish to configure or as a Delphix administrator.
Connecting to Namespaces
When you connect to the Delphix Engine with the CLI, you should specify the appropriate namespace (either DOMAIN or
SYSTEM). See Connecting to the CLI for more information.

3. Select the current user, or select a specific user if configuring another user as an administrator.

delphix> user current

4. Update the user and set the SSH key.

delphix user "delphix_admin"> update

delphix user "delphix_admin" update *> set publicKey
Enter publicKey:
Avoid Newline Characters with Public Key Entry
The public key value, which can be quite long, must be entered as a single string with no newlines. When copying and pasting
the public key be sure to avoid introducing any newline characters.

5. Paste the contents of the public key configured on your client and commit the result.

delphix user "delphix_admin" update *> commit

delphix>
6. Verify you can authenticate through the Delphix CLI without a passphrase.

Example Using Default SSH Key

ssh delphix_admin@[email protected]
Last login: Thu Dec 13 22:16:28 2012 from 192.168.0.2
delphix>

Example Using a Non-default SSH Key File Located at path/to/delphix_key

ssh -i path/to/delphix_key delphix_admin@[email protected]
Last login: Thu Dec 13 22:16:28 2012 from 192.168.0.2
delphix>

1146

Delphix User Guide 2016 Delphix

Third Party SSH Key Generation Example

This topic describes Example SSH key generation for password-less login to the Delphix CLI
Prerequisites

These operations are performed as a command line user on a non-Dephix host, where SSH is installed. In the remainder of the document we will
use:
username - to refer to the existing command line user the non-Delphix host
host name - to refer to the existing non-Delphix host
These example here should work with a variety of SSH distributions, however your distribution may behave differently. If you are unable to follow
these instructions successfully, consult with your system administrator, and/or your operating system or SSH client vendor.
Procedure

This example details three ways to set up password-less authentication:

1. Using an existing SSH key with no passphrase
2. Generating a new SSH key stored in the default location
3. Generating a new SSH key stored in a non-default location
Using an Existing SSH Key With No Passphrase
Note: To use an existing SSH key for password-less authentication, that key must have been established with no passphrase. If the existing SSH
key has a passphrase associated with it, instead follow the instructions for generating a new SSH key stored in a non-default location below.
1. Log in as username to hostname
2. Within the ~username/.ssh/ directory there will be one or more files whose names end in the .pubextension, for example:
a. id_dsa.pub
b. id_rsa.pub
c. identity.pub
(the differing names correspond to different types of keys SSH may use)
3. Input the contents of the desired .pub file into the publicKey field as described in CLI Cookbook: Configuring Key-Based SSH
Authentication for Automation
Generating a New SSH Key Stored in the Default Location
1. Log in as username to hostname
2. Verify there are no files with the .pub extension in the ~username/.ssh/ directory. If there are you must either use the existing SSH
key as described above, or generate a new SSH key in a non-default location as described below.
3. Choose the type of key you wish to create: RSA or DSA for SSH protocol 2, or RSA for SSH protocol 1. If you have no preference, RSA
for SSH protocol 2 is most commonly used.
4. Create your keys with no passphrase, by running:
a. For RSA protocol 2: ssh-keygen -t rsa
i. This command creates two new files in ~username/.ssh/: id_rsa and id_rsa.pub
b. For DSA protocol 2: ssh-keygen -t dsa
i. This command creates two new files in ~username/.ssh/: id_dsa and id_dsa.pub
c. For RSA protocol 1: ssh-keygen -t rsa1
i. This command creates two new files in ~username/.ssh/: identity and identity.pub
5. You will be prompted to enter a passphrase, and to confirm the passphrase - simply hit enter twice to create a key with no
passphrase for password-less authentication.
6. Input the contents of the created .pub file in the ~username/.ssh/ directory into the publicKey field as described in CLI Cookbook:
Configuring Key-Based SSH Authentication for Automation
Generating a New SSH Key Stored in a Non-Default Location
1. Log in as username to hostname
2. Chose the filename for your new SSH key files, for example: delphix_key and delphix_key.pub
3. Choose the type of key you wish to create: RSA or DSA for SSH protocol 2, or RSA for SSH protocol 1. If you have no preference, RSA
for SSH protocol 2 is most commonly used.
4. Create your keys with no passphrase, by running:
a. For RSA protocol 2: ssh-keygen -t rsa -f delphix_key
b.
1147

Delphix User Guide 2016 Delphix

4.

b. For DSA protocol 2: ssh-keygen -t dsa -f delphix_key

c. For RSA protocol 1: ssh-keygen -t rsa1 -f delphix_key
This command creates two new files delphix_key and delphix_key.pub
5. You will be prompted to enter a passphrase, and to confirm the passphrase - simply hit enter twice to create a key with no
passphrase for password-less authentication.
6. Input the contents of the created .pub file in the ~username/.ssh/ directory into the publicKey field as described in CLI Cookbook:
Configuring Key-Based SSH Authentication for Automation
7. On subsequent login attempts to the Delphix CLI, specify the private SSH key to be used with the -i argument, for example:
a. ssh -i ~/delphix_key [email protected]

Related Links

CLI Cookbook: Configuring Key-Based SSH Authentication for Automation

1148

Delphix User Guide 2016 Delphix

CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users
This topic describes adding public key authentication for a UNIX environment user, thus allowing the Delphix server to connect to your UNIX
Environments without an explicit password. This method uses the Delphix CLI in order to set up the environment user and gather SSH public
keys. It is also possible to perform these actions in the Delphix Engine Admin interface by navigating to Manage > Environments and selecting P
ublic Key as the Login Type for the environment (see Managing Environments with Agile Data Masking for details).
UNIX host environments (and Oracle cluster environments) can have users configured to use SSH-key based public key authentication instead of
the traditional password authentication method. Within Delphix, there is a per-system SSH public key that can be placed into the ~/.ssh/autho
rized_keys file of the remote user. Once this has been done, the Delphix environment user can be configured to use the private key instead of
an explicit password.

Prerequisites
You must be able to log into the remote host (or all hosts of an Oracle cluster) and have write access to the ~/.ssh/authorized_keys
file within the desired user's home directory.

Procedure
1. Get the current system public key:

delphix> system get sshPublicKey

ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAQEAse1M7uJX44lVPBljhnxB6MZUTx8VF6cupaVATg120lQonIqx29lP+Mwp
0AWh7C983IDoYDo+AY7RXpcFP9nKksiJnGSGiK6wo9RIiqSnF1x/VXNkTt2/67RVofoiui4W5fuxD4hOIvoT
r47Bg1hh9L6nhP0tnUvS/rusHFJ+ogxGHm46mwNlgUJUGmLTNao+W0YU693HRLukEch01t4k6olVGaC0eLjY
lgBf0Z5XiIcBX6ZWqVHAhwMinVjAvmfQhirAgCI7gYrd5/PwNl/DC8xyhWuxd2jgA7sSPeRqWY0JHt/xcmdp
IaPxTwtxQLKTnPxrFrQd+l4uf6LKxr5g7w== root@delphix
2. Add this key (starting with ssh-rsa) to the remote user's ~/.ssh/authorized_keys file. You will need to get access to this file using
an alternate authentication mechanism (such as logging in as the user with a password, or logging in as an administraor). Depending on
the target OS, you may need to do the following:
a. If the directory does not exist:

$ mkdir ~/.ssh
b. If creating the file or directory as an administrator:

# chown -R <username> <home>/.ssh

c. If required by the host SSH configuration, ensure the directory is not world readable:

$ chmod 600 ~/.ssh/authorized_keys

$ chmod 755 ~
3. Create a new environment user:

delphix> environment user create

4. Set the user environment and name:

delphix environment user create *> set environment=environment1

delphix environment user create *> set name=username
5. Set the user credential type to SystemKeyCredential:

delphix environment user create *> set credential.type=SystemKeyCredential

6. Commit the results:

delphix environment user create *> commit

Related Topics

1149

Delphix User Guide 2016 Delphix

Managing Environments with Agile Data Masking

Managing Environment Users

1150

Delphix User Guide 2016 Delphix

CLI Cookbook: System Administration

These topics describe various system administration tasks that can be performed with the command line interface, such as changing the name of
the <default> group and setting up network connectivity.
CLI Cookbook: Configuring A Second Network Interface
CLI Cookbook: Adding A Static Route
CLI Cookbook: Changing the Default Group Name
CLI Cookbook: How to Change a Delphix User Password
CLI Cookbook: Creating Alert Profiles
CLI Cookbook: Retrieve Capacity Information

1151

Delphix User Guide 2016 Delphix

CLI Cookbook: Configuring A Second Network Interface

This topic describes how to configure a static IP address on a second network interface.

Procedure
1. Add a VMXNET3 virtual network adapter to the Delphix VM and reboot the VM.
A reboot is required because the Delphix Engine does not dynamically recognize newly added network devices.
2. Log in to the Delphix Engine as the sysadmin user and switch to the network interface context. Then use the listcommand to view the
available network interfaces, and select the new interface to be configured.

delphix network interface> list

NAME
vmxnet3s0
vmxnet3s1
delphix network interface> select vmxnet3s1
fender.talisker network interface "vmxnet3s1"> get
type: NetworkInterface
name: vmxnet3s1
addresses: (empty)
device: vmxnet3s1
macAddress: 0:c:29:e5:4c:c1
mtu: 1500
mtuRange: 60-9000
reference: NETWORK_INTERFACE-vmxnet3s1
state: DOWN
3. Run the updatecommand and configure a static address.

delphix network interface "vmxnet3s1"> update

delphix network interface "vmxnet3s1" update *> edit addresses.0
delphix network interface "vmxnet3s1" update addresses.0 *> set address=10.1.2.3/24
delphix network interface "vmxnet3s1" update addresses.0 *> get
type: InterfaceAddress (*)
address: 10.1.2.3/24 (*)
addressType: STATIC (*)
4. Committhe operation.

delphix network interface "vmxnet3s1" update addresses.0 *> commit

delphix network interface "vmxnet3s1"> get
type: NetworkInterface
name: vmxnet3s1
addresses:
0:
type: InterfaceAddress
address: 10.1.2.3/24
addressType: STATIC
state: OK
device: vmxnet3s1
macAddress: 0:c:29:e5:4c:c1
mtu: 1500
mtuRange: 60-9000
reference: NETWORK_INTERFACE-vmxnet3s1
state: OK

1152

Delphix User Guide 2016 Delphix

CLI Cookbook: Adding A Static Route

This topic describes how to add a static route.

Procedure
1. Log in to the Delphix Engine as the sysadmin user and switch to the network route context.

delphix network route> list

DESTINATION
GATEWAY
default
172.16.0.1
10.1.2.0/24
172.16.0.0/24
-

OUTINTERFACE
vmxnet3s0
vmxnet3s1
vmxnet3s0

2. Run the add command to add a new route.

delphix network route> add

delphix network route add *> set destination=192.168.11.0/24
delphix network route add *> set gateway=10.1.2.1
delphix network route add *> get
type: NetworkRoute
destination: 192.168.11.0/24 (*)
gateway: 10.1.2.1 (*)
outInterface: (unset)
Optional outInterface Property
Setting the outInterface property is optional, as the system will automatically determine the output interface based on the
gateway address provided, as shown below.

3. Committhe operation.

delphix network route add *> commit

delphix network route> list
DESTINATION
GATEWAY
OUTINTERFACE
default
172.16.0.1
vmxnet3s0
10.1.2.0/24
vmxnet3s1
172.16.0.0/24
vmxnet3s0
192.168.11.0/24 10.1.2.1
vmxnet3s1

1153

Delphix User Guide 2016 Delphix

CLI Cookbook: Changing the Default Group Name

This topic describes how to change the name of the default group <New Group> on the Delphix Engine as a simple example of CLI interactions.
You must have delphix_admin credentials to perform this procedure.

Procedure
1. Switch to the group context and list groups on the system.

delphix> group
delphix group> list
NAME
DESCRIPTION
<New Group> 2. Select the default group and show current properties.

delphix group> select "<New Group>"

delphix group "<New Group>"> get
name: <New Group>
type: Group
description: (unset)
reference: GROUP-1
3. Run the update command and set the name.

delphix group "<New Group>"> update

delphix group "<New Group>" update *> set name=default
delphix group "<New Group>" update *> get
name: default (*)
type: Group
description: (unset)
reference: GROUP-1
4. Commit the operation.

delphix group "<New Group>" update *> commit

delphix group "default">

1154

Delphix User Guide 2016 Delphix

CLI Cookbook: How to Change a Delphix User Password

1. ssh into your engine with a user that has Admin privileges

ssh delphix_admin@delphix
2. Go to Users and select the User you would like to change the password of

delphix
delphix
delphix
delphix

> user
user > ls
user > select example_user
user "example_user" > ls

3. Select updateCredential to allow you to change password and set new password

delphix user "example user" > updateCredential

delphix user "example_user" updateCredential *> set newCredential.password=<new password>
4. Commit the operation

delphix user "example_user" updateCredential *> commit

Example:

ssh delphix_admin@delphixengine
delphixengine > user
delphixengine user > ls
Objects
NAME

EMAILADDRESS

sysadmin

delphix_admin

[email protected]

test_user

[email protected]

Operations
create
current
delphixengine user > select test_user
delphixengine user "test_user" > ls
Properties
type: User
name: test_user
authenticationType: NATIVE
credential:
type: PasswordCredential
password: ********

1155

Delphix User Guide 2016 Delphix

emailAddress: [email protected]
enabled: true
firstName: (unset)
homePhoneNumber: (unset)
isDefault: true
lastName: (unset)
locale: en_US
mobilePhoneNumber: (unset)
passwordUpdateRequested: false
principal: test_user
publicKey: (unset)
reference: USER-2
sessionTimeout: 30min
userType: DOMAIN
workPhoneNumber: (unset)

Operations
delete
update
disable
enable
updateCredential
delphixengine user "test_user" > updateCredential
delphixengine user "test_user" updateCredential *> set newCredential.password=<new
password>
delphixengine user "test_user" update *> commit

1156

Delphix User Guide 2016 Delphix

1157

Delphix User Guide 2016 Delphix

CLI Cookbook: Creating Alert Profiles

This article describes how to create alert profiles.
Delphix generates alerts for different events. Users may want to be notified of events based on certain criteria such as the type of event or
severity. An alert profile allows a user or group of users to be notified of the desired event.

Procedure
1. ssh into your engine using your delphix_admin username and password

ssh delphix_admin@yourdelphixengine
2. Go into your alerts and list the alerts you already have

delphix > alert

delphix alert > ls
3. Create your profile

delphix alert > profile

delphix alert profile > create
delphix alert profile create * > ls
4. Set Actions and Severity Filter

delphix alert profile create *> set actions.0.type=<AlertActionEmailList or

AlertActionEmailUser>
delphix alert profile create *> set actions.0.addresses.0=<email address to send to>
delphix alert profile create *> set actions.0.addresses.1=<additional email address>
delphix alert profile create *> set actions.0.addresses.2=<additional email address>
delphix alert profile create *> ls
delphix alert profile create *> set severityFilter=
delphix alert profile create *> set
severityFilter=<AUDIT|WARNING|CRITICAL|INFORMATIONAL>

Valid Values for Parameters

actions.0.type:
AlertActionEmailList: This type of alert is used to create an alert for any number of users. When this type is selected,
an email address may be defined in each element of the "actions.0.addresses" array as illustrated above.
AlertActionEmailUser: This type of alert is created for the email address of the user currently logged into the command
line interface. The "actions.0.addresses" array is not available for this type.
actions.0.severityFilter:
INFORMATIONAL
WARNING
CRITICAL
AUDIT

5. Commit your changes

delphix alert profile create *> commit

Example:

ssh delphix_admin@yourengine
delphix > alert
delphix alert> ls

1158

Delphix User Guide 2016 Delphix

Objects
REFERENCE TIMESTAMP
EVENTTITLE
ALERT-102 2015-01-14T21:00:04.380Z
Job complete
ALERT-101 2015-01-14T20:55:57.880Z
Job complete
ALERT-100 2015-01-14T19:35:32.958Z
Job complete
ALERT-99
2015-01-14T19:35:32.850Z
Job complete
ALERT-98
2015-01-14T19:34:58.744Z
Error during job execution
ALERT-97
2015-01-14T18:12:01.928Z
Job complete
ALERT-96
2015-01-14T18:03:10.664Z
Job complete
ALERT-95
2015-01-14T17:16:07.464Z
Job complete
ALERT-94
2015-01-14T17:15:55.298Z
Job complete
ALERT-93
2015-01-14T17:15:45.995Z
Job complete
ALERT-92
2015-01-14T16:39:33.133Z
complete
ALERT-91
2015-01-14T16:38:33.719Z
complete
ALERT-90
2015-01-14T15:47:35.005Z
Validated sync failed for dSource
ALERT-89
2015-01-14T15:45:40.895Z
Validated sync failed for dSource
ALERT-88
2015-01-14T15:02:14.874Z
Job complete
ALERT-87
2015-01-14T11:33:28.766Z
Job complete
ALERT-86
2015-01-13T23:11:46.838Z
Job complete
ALERT-85
2015-01-13T11:30:01.154Z
Job complete
ALERT-84
2015-01-13T11:07:04.385Z
Backup detection failed
ALERT-83
2015-01-12T22:35:18.774Z
Backup detection failed
ALERT-82
2015-01-12T11:30:00.063Z
Unable to connect to remote database
ALERT-81
2015-01-12T11:30:00.054Z
Unable to connect to remote database
ALERT-80
2015-01-12T08:38:26.983Z
Backup detection failed
ALERT-79
2015-01-12T06:04:34.666Z
Validated sync failed for dSource
ALERT-78
2015-01-11T11:30:03.393Z
Job complete
Children
profile
delphix alert> select ALERT-98
delphix alert "ALERT-98"> ls
Properties
type: Alert

TARGETNAME
ASE/pubs2
ASE/pubs2VDB
ASE/pubs2VDB
ASE/pubs2VDB
ASE/pubs2
ASE/pubs2
ASE/pubs2
ASE/pubs2
ASE/market
ASE/pubs2VDB
nstacksolase2.acme.com-2015-01-14T16:39:13.821Z

Job

nstacksolase2.acme.com

Job

market
pubs2
ASE/market
ASE/pubs2VDB
ASE/market
ASE/pubs2VDB
pubs2
pubs2
ASE/pubs2VDB
during virtual database policy enforcement
ASE/pubs2
during dSource policy enforcement
pubs2
pubs2
ASE/pubs2VDB

1159

Delphix User Guide 2016 Delphix

event: alert.jobs.failed.object
eventAction: Create the database on the target host.
eventDescription: DB_EXPORT job for "ASE/pubs2" failed due to an error during
execution: Could not find database "pubs2VDB" on target instance "SRC_157_4K",
environment "ASE".
eventSeverity: CRITICAL
eventTitle: Error during job execution
reference: ALERT-98
target: ASE/pubs2
targetName: ASE/pubs2
targetObjectType: ASEDBContainer
timestamp: 2015-01-14T19:34:58.744Z
delphix alert> profile
delphix alert profile> select ALERT_PROFILE-1
delphix alert profile "ALERT_PROFILE-1"> ls
Properties
type: AlertProfile
actions:
0:
type: AlertActionEmailList
addresses: [email protected]
format: HTML
eventFilter: (empty)
reference: ALERT_PROFILE-1
severityFilter: CRITICAL,WARNING
targetFilter: (empty)
Operations
delete
update
delphix alert profile> create
delphix alert profile create *> set actions.0.type=AlertActionEmailList

1160

Delphix User Guide 2016 Delphix

delphix alert profile create *> set [email protected]

delphix alert profile create *> set [email protected]
delphix alert profile create *> set severityFilter=INFORMATIONAL

*The last piece of the alert profile that needs to be configured is the "targetFilter". This is an array so you can define
multiple targets. In the following example, there is a dSource named "pubs2" the user wants to define an alert on. If
they try to set the filter to just the name of the dSource itself ("pubs2"), it will warn them that this is ambiguous and
gives a hint on how to fully qualify it:
delphix alert profile create *> set targetFilter=pubs2
The name 'pubs2' is ambiguous, specify one of: [ "ASE/pubs2", "pubs2/pubs2",
"SRC_157_4K/pubs2" ].
delphix alert profile create *> set targetFilter.0=pubs2/pubs2
delphix alert profile create *> set targetFilter.1=ASE/pubs2
delphix alert profile "ALERT_PROFILE-34" update *> commit
Use the tab button freely to autocomplete and also see available options, for instance, while changing the severityFilter property, you can use the
tab key like so:

DELPHIX-4221.dcenter alert profile 'ALERT_PROFILE-1' update *> set severityFilter= <I HIT
TAB HERE TO SEE OPTIONS BELOW>
AUDIT

CRITICAL

INFORMATIONAL

WARNING

Note on names used in the example

SRC_157_4K: Repository (entity containing the database instances)
ASE: Group name
pubs2: Name of individual database instance
The user set the targetFilter to be equal to "pubs2/pubs2" and "ASE/pubs2" because if you review the "TARGETNAME" column from
step 1 above, you will see alerts generated for both of these targets.

1161

Delphix User Guide 2016 Delphix

CLI Cookbook: Retrieve Capacity Information

This topic describes how to gather capacity information from your Delphix Engine. This information includes:
dSource Space Breakdown
Virtual Object Space Breakdown
Total Space

Procedure
1. Switch to the capacity system context.

delphix> capacity system

2. List the properties of this content.

delphix capacity system> ls

Properties
type: CurrentSystemCapacityData
source:
type: CapacityBreakdown
activeSpace: 940582400B
actualSpace: 1075381760B
descendantSpace: 134583808B
logSpace: 145920B
manualSpace: 0B
policySpace: 0B
syncSpace: 134583808B
timeflowUnvirtualizedSpace: 7725215744B
unvirtualizedSpace: 2624235520B
timestamp: 2015-12-11T11:49:18.998Z
totalSpace: 25568477184B
virtual:
type: CapacityBreakdown
activeSpace: 176684032B
actualSpace: 313768448B
descendantSpace: 0B
logSpace: 47820288B
manualSpace: 85958144B
policySpace: 0B
syncSpace: 85958144B
timeflowUnvirtualizedSpace: 5475587584B
unvirtualizedSpace: 2667149312B
For more information about capacity management in Delphix, visit: An Overview of Capacity and Performance Information.

1162

Delphix User Guide 2016 Delphix

CLI Cookbook: Hosts and Environments

These topics describe command line interface procedures for working with database hosts and environments.
CLI Cookbook: Adding a UNIX Host
CLI Cookbook: Adding a SQL Server Source Environment
CLI Cookbook: Setting Multiple Addresses for a Target Host
CLI Cookbook: How to Change Environment User

1163

Delphix User Guide 2016 Delphix

CLI Cookbook: Adding a UNIX Host

This topic describes the process of adding a UNIX host using the 3.0 command line interface.
Within Delphix, there are both hosts and host environments. A host represents a remote system, but may or may not be a source or target for
linking or provisioning. For example, in an Oracle RAC cluster, the cluster environment represents the location of the Oracle installation(s), and
while there are hosts within that cluster they are not individually manageable as environments.

Procedure
1. Create a new environment and set the parameter type to be a UNIX host.
The default is a UNIX host, but for completeness this demonstrates how one would add another type of environment (Oracle cluster or
Windows host).

delphix> environment create

delphix environment create *> set type=HostEnvironmentCreateParameters
delphix environment create *> set hostEnvironment.type=UnixHostEnvironment
delphix environment create *> set hostParameters.type=UnixHostCreateParameters
delphix environment create *> set primaryUser.credential.type=PasswordCredential
delphix environment create *> get
type: HostEnvironmentCreateParameters (*)
hostEnvironment:
type: UnixHostEnvironment (*)
name: (unset)
description: (unset)
hostEnvironment: (unset)
hostParameters:
type: UnixHostCreateParameters (*)
host:
type: UnixHost
addresses: (required)
sshPort: 22
toolkitPath: (required)
primaryUser:
type: EnvironmentUser
name: (required)
credential:
type: PasswordCredential
password: (required)
environment: (unset)
2. Set the host address.
The name of the environment is derived from the address used, though you can provide a more descriptive name if desired. The
addresses can be DNS names, IP addresses, or a comma separated list of the above.

delphix environment create *> set hostParameters.host.addresses=192.168.1.2

3. Set the toolkit path.
This is where Delphix will store temporary binaries used while the host is configured as part of Delphix.

delphix environment create *> set hostParameters.host.toolkitPath=/var/delphix

4. Set the username and password to use when connecting over SSH.
This user must have the privileges described in the Delphix Adminsitration Guide. To configure a SSH user, change the credential type to
SystemKeyCredential.

delphix environment create *> set primaryUser.name=oracle

delphix environment create *> set primaryUser.credential.password
Enter primaryUser.credential.password: *******
5. Commit the result.
The environment discovery process will execute as an asynchronous job. The default behavior is to wait for the result, so progress will be
updated until the discovery process is complete or fails.

1164

5.

Delphix User Guide 2016 Delphix

delphix environment create *> commit

UNIX_HOST_ENVIRONMENT-4
Dispatched job JOB-39
ENVIRONMENT_CREATE_AND_DISCOVER job started for "192.168.1.2".
ENVIRONMENT_CREATE_AND_DISCOVER job for "192.168.1.2" completed successfully.
delphix>

1165

Delphix User Guide 2016 Delphix

CLI Cookbook: Adding a SQL Server Source Environment

This topic describes how to add a SQL Server source environment using the command line interface.
Since SQL Server source environments do not have the Delphix Connector running on them, you must use a target environment as a proxy when
adding source environments. Delphix uses the connector running on the proxy environment to run commands against the source environment.
See Setting Up SQL Server Environments: An Overview for more information.

Procedure
Enter these commands through the command line interface:

/environment;
create;
set type=HostEnvironmentCreateParameters;
set hostEnvironment.type=WindowsHostEnvironment;
set hostEnvironment.name=<Source environment name>;
set hostEnvironment.proxy=<target host name>;
set hostParameters.type=WindowsHostCreateParameters;
set hostParameters.host.type=WindowsHost;
set hostParameters.host.addresses="<Source host IP address or hostname>";
set primaryUser.name="<domain\username>";
set primaryUser.credential.type=PasswordCredential;
set primaryUser.credential.password=<password>;
commit;
Example

The CLI commands for adding source host "mssql_source_1"using target host mssql_target_1 as proxy and environment user ad\d
elphix_user would be:

/environment;
create;
set type=HostEnvironmentCreateParameters;
set hostEnvironment.type=WindowsHostEnvironment;
set hostEnvironment.name="mssql_source_1";
set hostEnvironment.proxy="mssql_target_1";
set hostParameters.type=WindowsHostCreateParameters;
set hostParameters.host.type=WindowsHost;
set hostParameters.host.addresses="mssql_source_1";
set primaryUser.name="ad\delphix_user";
set primaryUser.credential.type=PasswordCredential;
set primaryUser.credential.password="i_am_the_password";
commit;
Related Links
Setting Up SQL Server Environments: An Overview

1166

Delphix User Guide 2016 Delphix

CLI Cookbook: Setting Multiple Addresses for a Target Host

This topic is an example of using arrays to configure a target host to support multiple IP addresses. The addresses property is an array of
strings.

Procedure
1. Select the host to update

delphix> host
delphix host> select example
delphix host "example"> update
2. Set the address:

delphix host "example" update *> set addresses=192.168.1.1,192.168.1.2

3. Get the current addresses, both as a string and as an array object.

delphix host "example" update *> get addresses

192.168.1.1,192.168.1.2 (*)
delphix host "example" update *> get addresses[0]
192.168.1.1 (*)
delphix host "example" update *> edit addresses
delphix host "example" update addresses *> get
0:
192.168.1.1 (*)
1:
192.168.1.2 (*)
4. Commit the result:

delphix host "example" update addresses *> commit

delphix host "example">

1167

Delphix User Guide 2016 Delphix

CLI Cookbook: How to Change Environment User

1. ssh into your engine using Admin privileges

ssh delphix_admin@delphix
2. Go to Environment and find the Environment you would like to update

delphix > environment

delphix environment > ls
delphix environment > select test_env
3. Select Environment updating and Update

delphix environment "test_env" > update

delphix environment "test_env" update *> ls

4. Set primaryUser to new user you would like to use for the Environment

delphix environment "test_env update" *> set primaryUser=<new user>

5. Commit the change

delphix environment "test_env" update *> commit

Example:

1168

Delphix User Guide 2016 Delphix

ssh delphix_admin@delphix
delphix > environment
delphix environment > ls
Objects
NAME

DESCRIPTION

Demo

Children
oracle
user

Operations
create
delphix environment > select Demo
delphix environment "Demo" > update
delphix environment "Demo" update *> ls
Properties
type: UnixHostEnvironment
name: Demo
description:
primaryUser: delphix
delphix environment "Demo" update *> set primaryUser=<new user>
delphix environment "Demo" update *> commit

1169

Delphix User Guide 2016 Delphix

CLI Cookbook: Source Databases and dSources

These topics describe command line interface procedures for working with dSources.
CLI Cookbook: Detaching and Attaching an Oracle dSource
CLI Cookbook: Disabling LogSync for a dSource
CLI Cookbook: Enabling Oracle Validated Sync
CLI Cookbook: Linking a Microsoft SQL Server Database Loading from a Specific Full Backup of the Source Database
CLI Cookbook: Linking a Microsoft SQL Server Database Loading from the Last Full Backup of the Source Database
CLI Cookbook: Linking to a Single Instance Oracle Database
CLI Cookbook: Listing Data Source Sizes
CLI Cookbook: Detaching and Attaching a SQL Server dSource
CLI Cookbook: How to Change Database User Password

1170

Delphix User Guide 2016 Delphix

CLI Cookbook: Detaching and Attaching an Oracle dSource

This topic describes how to attach a dSource to a different data source.

Prerequisites
A dSource can only be attached to a new data source once it has been unlinked.
When attaching an Oracle dSource to a new data source, the new data source must be the same logical database satisfying the following
constraints:
Same dbid
Same dbname
Same creation time
Same resetlogs SCN
Same resetlogs time
Same redo stream, where a log must exist with
Same sequence
Same thread
Same end SCN
For Oracle dSources, this procedure can be used to initially link from a standby server that is faster or less disruptive, unlink the dSource, and
then attach it to the production server for subsequent incremental SnapSync operations. When you perform the attach operation, you will need the
source config name of an unlinked database.

Procedure
1. Select the dSource.

delphix> database "dexample"

2. Run the detachSourcecommand, specifying the currently active source. This step can be skipped if the dSource has already been
detached through the GUI.

delphix database "dexample"> detachSource

delphix database "dexample" detachSource *> set source=name-of-old-src-DB-server
delphix database "dexample" detachSource *> commit
3. Run the attachSourcecommand.

delphix database "dexample"> attachSource

4. Set the config to point to an unlinked source.
The following is an example to attach to an Oracle data source:

1171

Delphix User Guide 2016 Delphix

delphix database "dexample" attachSource *> set

source.name=name-of-new-src-DB-server
delphix database "dexample" attachSource *> set
source.config=name-of-dSource-as-shown-in-environment
delphix database "dexample" attachSource *> set environmentUser=myuser
delphix database "dexample" attachSource *> set dbUser=orauser
delphix database "dexample" attachSource *> set dbCredentials.password=orauserpwd
delphix database "dexample" attachSource *> ls
operations:
type: LinkedSourceOperations
postSync: (required)
preSync: (required)
delphix database "dexample" attachSource *> edit source.operations.preSync*> back
delphix database "dexample" attachSource *> edit source.operations.postSync
delphix database "dexample" attachSource *> back
delphix database "dexample" attachSource *> ls
operations:
type: LinkedSourceOperations
postSync: (empty) (*)
preSync: (empty) (*)
rmanChannels: (unset)
The source.config listing can be observed in the administration GUI, under Manage (pull-down at the top) --> Environments --> choose
your dSource --> select Databases (upper right).
The dSources shown on the new source DB server may acquire odd names eg. "P02:UNKNOWN:vwxyz". These are a side-effect of
having multiple instances of the same container name (possible in DR); Delphix needs to disambiguate. If these do show, they indicate
containers in the new environment. Successfully attaching to these and deleting the old environment will re-establish the original names.

5. Commit the operation.

delphix database "dexample" attachSource *> commit

1172

Delphix User Guide 2016 Delphix

CLI Cookbook: Disabling LogSync for a dSource

This topic provides a simple example of how nested state is represented and manipulated. The LogSync state is maintained in the sourcingPolicy
property of dSources, itself an object with several different fields.

Procedure
1. Select the dSource to be changed and run the updatecommand.

delphix> database "example"

delphix "example"> update
2. Get the current property using dot-delimited notation.

delphix "example" update *> get sourcingPolicy.logsyncEnabled

true
3. The property could also be set using dot-delimited notation, but for illustrative purposes we can also use the editcommand and set it
directly.

delphix "example" update *> edit sourcingPolicy

delphix "example" update sourcingPolicy *> set logsyncEnabled=false
4. Commit the state, either from within the editing context or after running backto return to the parent context.

delphix "example" update sourcingPolicy *> commit

delphix "example">

1173

Delphix User Guide 2016 Delphix

CLI Cookbook: Enabling Oracle Validated Sync

This topic describes how to designate a staging host and enable validated sync for Oracle data sources.

Prerequisite - Designating a Staging Host

In order to validate an Oracle dSource snapshot for syncing, the Delphix Engine requires a host with an Oracle installation that is compatible with
the dSource. This machine is known as the staging host. You must explicitly designate which machines you want the Delphix Engine to use as
staging hosts. All machines that have been marked as staging sites are added to a pool. During validated sync, the Delphix Engine will select a
compatible host from the pool, export the requisite archived redo logs and datafiles, and execute Oracle media recovery on the host. Follow these
steps to designate a staging host.
1. Select the repository you want to designate as staging.

delphix>/repository/select '/u01/app/ora10205/product/10.2.0/db_1'
2. Execute the update command.

delphix repository "'/u01/app/ora10205/product/10.2.0/db_1'">update

3. Set staging to true.

delphix repository "'/u01/app/ora10205/product/10.2.0/db_1'" update *>set

staging=true
4. Commit the operation to designate the repository as staging.

delphix repository "'/u01/app/ora10205/product/10.2.0/db_1'" update *> commit

To configure validated sync for multiple dSources with different Oracle versions, you must designate a compatible staging source for each. If
multiple compatible staging sites exist, the Delphix Engine will select one at random.
The validated sync process will consume some resources on the staging host when snapshots are taken. Designating a
performance-critical host as a staging host is not recommended.

Procedure - Enabling Validated Sync

1. Select the dSource for which you want to enable validated sync.

delphix>/database/select redsox1
2. Execute the update command.

delphix database "redsox1">update

3. Set preProvisioningEnabled to true.

delphix database "redsox1" update *>set preProvisioningEnabled=true

4. Commit the operation to enable validated sync.

delphix database "redsox1" update *>commit

1174

Delphix User Guide 2016 Delphix

CLI Cookbook: Linking a Microsoft SQL Server Database Loading from a Specific Full Backup of the
Source Database
This topic describes how to use the command line interface to link a SQL Server database by loading from a specific full backup of the source
database as indicated by the backup UUID.

Prerequisites
You can find the fullBackupUUID referenced in the last command line in the msdb.dbo.backupset on the source database, for
example using the following query

Use master
select backupset.database_name,
backupset.type,
backupset.backup_set_id,
backupset.backup_set_uuid,
backupset.family_guid,
backupset.position,
backupset.first_lsn,
backupset.last_lsn,
backupset.database_backup_lsn,
backupset.name,
backupset.has_bulk_logged_data,
backupset.is_damaged,
backupset.begins_log_chain,
backupset.is_copy_only,
backupset.backup_finish_date,
backupset.database_version,
backupset.database_guid,
mediafamily.logical_device_name,mediafamily.physical_device_name
from msdb.dbo.backupmediafamily mediafamily join msdb.dbo.backupset backupset
on mediafamily.media_set_id = backupset.media_set_id where backupset.database_name =
N'<Database Name>'
order by backupset.backup_finish_date desc
Procedure
Enter these commands through the Delphix Engine command line interface:

1175

Delphix User Guide 2016 Delphix

/database;
link;
set type=MSSqlLinkParameters;
set
set
set
set

container.type=MSSqlDatabaseContainer;
container.name=<dSource name>;
container.group=<group name>;
container.sourcingPolicy.loadFromBackup=true;

set source.type=MSSqlLinkedSource;
set source.config=<source database>;
set source.sharedBackupLocation="<source database backup location>";
set pptRepository=<SQL instance on the staging server>;
set container.sourcingPolicy.type=SourcingPolicy;
set dbUser=<source database login with SQL authentication>;
set dbCredentials.type=PasswordCredential;
set dbCredentials.password=<password for the database login>;
set fullBackupUUID=859FD1F1-1590-4FCB-A341-5D2D13852E2E;
commit;

1176

Delphix User Guide 2016 Delphix

CLI Cookbook: Linking a Microsoft SQL Server Database Loading from the Last Full Backup of the
Source Database
This topic describes how to use the command line interface to link a SQL Server database by loading from the last full backup of the source
database.

Procedure
Enter the following commands in the Delphix Engine command line interface:

/database;
link;
set type=MSSqlLinkParameters;
set
set
set
set

container.type=MSSqlDatabaseContainer;
container.name=<dSource name>;
container.group=<group name>;
container.sourcingPolicy.loadFromBackup=true;

set source.type=MSSqlLinkedSource;
set source.config=<source database>;
set source.sharedBackupLocation="<source database backup location>";
set pptRepository=<SQL instance on the staging server>;
set container.sourcingPolicy.type=SourcingPolicy;
set dbUser=<source database login with SQL authentication>;
set dbCredentials.type=PasswordCredential;
set dbCredentials.password=<password for the database login>;
commit;

1177

Delphix User Guide 2016 Delphix

CLI Cookbook: Linking to a Single Instance Oracle Database

This topic describes how to link to a single instance Oracle database using the Delphix Engine command line interface.

Prerequisites
You will need the following information:
The name of the dSource you want to create.
The group in which you want to create the dSource.
The database unique name of the Oracle database you want to link to.
The database username/password with sufficient privileges as described in the Delphix User Guide.
The host environment user with sufficient privileges as described in the Delphix User Guide.

Procedure
1. Execute the database link command.

delphix> database link

delphix database link>
2. The default link operation is OracleLinkParameters, but you can confirm that by getting the input type:

delphix database link *> get type

OracleLinkParameters
3. Set the name for the dSource and the group in which you want to create it.

delphix database link *> set container.name=dexample

delphix database link *> set container.group="<New Group>"
4. Set the source configuration.
For Oracle databases, these are identified by the database unique name. If you are unsure of the set of available databases, you can list
available source configurations.

delphix database link *> /sourceconfig list

NAME
REPOSITORY
LINKINGENABLED
example1 '/opt/ora/dexample1' true
example2 '/opt/ora/dexample1' true
delphix database link *> set source.config=example1
5. Set the privileged database username/password.
The password can be set like other properties, or the value can be omitted so that it can be manually input without exposing the
password.

delphix database link *> set dbUser=delphix

delphix database link *> set dbCredentials.password
Enter dbCredentials.password: ********
6. Set the privileged environment user.
This user must be from the same environment as the associated source config set in step 4. You can list the set of available users
through the environment user listcommand.

delphix database link *> /environment/user list

NAME
172.168.1.2/oracle
delphix database link *> set environmentUser=172.168.1.2/oracle
7. Adjust any other properties you may want, such as RMAN tunables, description, and whether to link now.
The full set of options is described in the API documentation for the OracleLinkParameters type. If you set the linkNowproperty,
then this operation will wait for the sync to complete, otherwise you can perform the initial link by running the sync command at a later
point.

delphix database link *> set masked=true

1178

Delphix User Guide 2016 Delphix

8. Commit the result.

delphix database link *> commit

ORACLE_DB_CONTAINER-1
delphix>

1179

Delphix User Guide 2016 Delphix

CLI Cookbook: Listing Data Source Sizes

This topic describes a basic use of the CLI list command.
1. Switch to the source view and view the default list.

delphix> source
delphix source> list
NAME
CONTAINER VIRTUAL
example
example
false
vexample vexample
true

CONFIG
example
vexample

2. List sources with their database size (in MB).

delphix> source
delphix source> list display=name,virtual,runtime.databaseSize
NAME
VIRTUAL RUNTIME.DATABASESIZE
example
false
12784
vexample true
12842

1180

Delphix User Guide 2016 Delphix

CLI Cookbook: Detaching and Attaching a SQL Server dSource

Prerequisites
A dSource can only be attached to a new data source once it has been unlinked.

When attaching a SQL Server dSource to a new data source, the new data source must be the same database
satisfying the following containts:
Same database name
Same recovery fork UUID
pptRepository needs to be set to the name of the SQL instance on the staging server. The unlink operation removes the database from
the SQL instance on the staging server and unmounts the iscsi luns, reattaching the dSource via the CLI will remount the iscsi luns and
puts the database back.

Procedure
1. Select the dSource.

delphix> database "dexample"

2. Run

the detachSourcecommand, specifying the currently active source. This step can be skipped if the dSource
has already been detached through the GUI.
delphix database "dexample"> detachSource
delphix database "dexample" detachSource *> set source=dexample
delphix database "dexample" detachSource *> commit
3. Run the attachSourcecommand.

delphix database "dexample"> attachSource

4. Set the following for SQL Server:
You can also type help pptRepository to see what is wanted
You can also set pptRepository=<then press tab> to list all values.

delphix database "dexample" attachSource *> set source.config=SQLSERVER/dexample

delphix database "dexample" attachSource *> set
source.sharedBackupLocation=\\SERVER1\Backups
delphix database "dexample" attachSource *> set pptRepository=SQL2008R2
delphix database "dexample" attachSource *> set dbUser=dbuser
delphix database "dexample" attachSource *> set dbCredentials.password=dbuserpwd
delphix database "dexample" attachSource *> edit source.operations.preSync
delphix database "dexample" attachSource source.operations.preSync *> back
delphix database "dexample" attachSource *> edit source.operations.postSync
delphix database "dexample" attachSource source.operations.postSync *> back
5. Commit the operation.

delphix database "dexample" attachSource *> commit

1181

Delphix User Guide 2016 Delphix

CLI Cookbook: How to Change Database User Password

1. ssh into your engine using Admin privileges

ssh delphix_admin@delphixengine
2. Go to sourceconfig and fine the Database that you need to update the password on

delphix > sourceconfig

delphix sourceconfig > ls
delphix sourceconfig > select <yourdatabase>

3. Update the password

delphix sourceconfig "yourdatabase" > update

delphix sourceconfig "yourdatabase" update *> ls
delphix sourceconfig "yourdatabase" update *> set credentials.password=<new password>
4. Commit the change

delphix sourceconfig "database" update *> commit

Examaple:

ssh delphix_admin@example
delphix > sourceconfig
delphix sourceconfig > ls
Objects
NAME

REPOSITORY

LINKINGENABLED

meta1

'/u01/oracle/10.2.0.4/ee1'

true

Operations
create
delphix sourceconfig > select meta1
delphix sourceconfig "meta1" > ls
Properties
type: OracleSIConfig
name: meta1
credentials:
type: PasswordCredential
password: ********
databaseName: meta1
discovered: true
environmentUser: delphix
instance:

1182

Delphix User Guide 2016 Delphix

type: OracleInstance
instanceName: meta1
instanceNumber: 1
linkingEnabled: true
nonSysCredentials: (unset)
nonSysUser: (unset)
reference: ORACLE_SINGLE_CONFIG-1
repository: '/u01/oracle/10.2.0.4/ee1'
services:
0:
type: OracleService
discovered: true
jdbcConnectionString: jdbc:oracle:thin:@172.16.100.69:1525:meta1
1:
type: OracleService
discovered: true
jdbcConnectionString: jdbc:oracle:thin:@172.16.100.69:1521:meta1
uniqueName: meta1
user: delphix

Operations
delete
update
validateCredentials

1183

Delphix User Guide 2016 Delphix

delphix sourceconfig "meta1" > update

delphix sourceconfig "meta1" update *> credentials.password=<new password>
delphix sourceconfig "meta1" update *> commit

1184

Delphix User Guide 2016 Delphix

CLI Cookbook: VDBs

These topics describe command line interface procedures for working with virtual databases (VDBs).
CLI Cookbook: Changing the SID of Oracle RAC VDBs
CLI Cookbook: Oracle VDB Migration
CLI Cookbook: Provisioning a Single Instance Oracle VDB
CLI Cookbook: Provisioning a SQL Server VDB
CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark
CLI Cookbook: Rolling Forward a VDB
CLI Cookbook: Refresh a VDB from a Specific Timepoint or Latest
CLI Cookbook: Repairing a Timeflow
CLI Cookbook: Changing SGA Parameter
CLI Cookbook: Rolling Back a VDB
CLI Cookbook: Creating a VDB Config Template
CLI Cookbook: Creating a Policy
CLI Cookbook: Provisioning a SAP ASE VDB
CLI Cookbook: Taking a Snapshot
CLI Cookbook: Determining the Snapshot used to provision a VDB
CLI Cookbook: Detaching and Attaching a SAP ASE dSource

1185

Delphix User Guide 2016 Delphix

CLI Cookbook: Changing the SID of Oracle RAC VDBs

This topic describes how to change the SID of instances in an Oracle RAC VDB.
This example demonstrates how to switch the instance name and number between two different hosts, from

SQL> select * FROM V$ACTIVE_INSTANCES;

INST_NUMBER INST_NAME
----------- -----------------------------------------------------------1 cnrac3:VchiBEB1
2 cnrac4:VchiBEB2
to

SQL> select * FROM V$ACTIVE_INSTANCES;

INST_NUMBER INST_NAME
----------- -----------------------------------------------------------1 cnrac4:VchiBEB1
2 cnrac3:VchiBEB2

Procedure

1. Stop the VDB through the GUI and login to the Delphix CLI
2. Select the sourceconfig of the RAC VDB whose instances you would like to rename.

kfc-manual.dcenter> sourceconfig
kfc-manual.dcenter sourceconfig> select Vchicago_BEB
3. Use the update command to change the properties of the sourceconfig

kfc-manual.dcenter sourceconfig "Vchicago_BEB"> update

4. Type 'ls' to view the complete list of properties associated with the VDB's sourceconfig

kfc-manual.dcenter sourceconfig "Vchicago_BEB" update *> ls

Properties
type: OracleRACConfig
credentials:
type: PasswordCredential
password: ********
environmentUser: ora1024
instances:
0:
type: OracleRACInstance
instanceName: VchiBEB1
instanceNumber: 1
node: cnrac4
1:
type: OracleRACInstance
instanceName: VchiBEB2
instanceNumber: 2
node: cnrac3
linkingEnabled: true
nonSysCredentials: (unset)
nonSysUser: (unset)
repository: '/u01/app/ora1024/product/10.2.0/db_1'
services: [ ... ]
user: delphix

1186

Delphix User Guide 2016 Delphix

5. Use the Set command to change the values for instanceName and instanceNumber for each instance.

kfc-manual.dcenter sourceconfig "Vchicago_BEB"

instances.0.instanceName=VchiBEB2
kfc-manual.dcenter sourceconfig "Vchicago_BEB"
kfc-manual.dcenter sourceconfig "Vchicago_BEB"
instances.1.instanceName=VchiBEB1
kfc-manual.dcenter sourceconfig "Vchicago_BEB"

update *> set

update *> set instances.0.instanceNumber=2
update *> set
update *> set instances.1.instanceNumber=1

6. Finally, commit the changes.

kfc-manual.dcenter sourceconfig "Vchicago_BEB" update *> commit;

7. Restart the VDB through the GUI for the changes to take effect on the VDB.

1187

Delphix User Guide 2016 Delphix

CLI Cookbook: Oracle VDB Migration

This topic describes moving a VDB from one environment or installation to another.
VDBs can be moved (or migrated) between hosts by changing the source repository associated with the VDB source config. This operation is
currently only available via the CLI.

Restrictions
The following restrictions apply when migrating a VDB between repositories:
When migrating a RAC VDB, the host of each OracleRACInstance must be updated as well.
The mount point of the VDB source cannot be changed.
The database_unique_name and db_name cannot be changed.
The new environment and repository must be a compatible target environment.

Procedure

1. Select the source associated with the VDB. By default, sources are named the same as the VDB.

delphix> source "vexample"

2. Disable the source by running the disablecommand and committing the operation.

delphix source "vexample"> disable

delphix source "vexample" disable *> commit
Dispatched job JOB-171
SOURCE_DISABLE job started for "vexample".
Starting disable of virtual database.
Unexporting storage.
Virtual database disable successful.
SOURCE_DISABLE job for "vexample" completed successfully.
delphix source "vexample">
3. Select the source config associated with the source. By default this is also the same name as the VDB.

delphix source "vexample"> get config

vexample
delphix source "vexample"> /sourceconfig "vexample"
delphix sourceconfig "vexample">
4. Update the repository and repository user associated with the source config.

delphix sourceconfig "vexample"> update

delphix sourceconfig "vexample" update *> set
repository=192.168.100.247/'/opt/oracle/product/10.2.0.4/db_1'
delphix sourceconfig "vexample" update *> set
environmentUser=192.168.100.247/ora1024
delphix sourceconfig "vexample" update *> commit
delphix sourceconfig "vexample">
5. Enable the source.

1188

Delphix User Guide 2016 Delphix

delphix sourceconfig "vexample"> /source "vexample" enable

delphix source "vexample" enable *> commit
Dispatched job JOB-173
SOURCE_ENABLE job started for "vexample".
Starting enable of virtual database.
Exporting storage.
Virtual database enable successful.
SOURCE_ENABLE job for "vexample" completed successfully.
delphix sorceconfig "vexample">

1189

Delphix User Guide 2016 Delphix

CLI Cookbook: Provisioning a Single Instance Oracle VDB

This topic describes how to provision a single instance Oracle VDB using the Delphix Engine command line interface.

Prerequisites
You will need the following information:
The name of the VDB you want to create
The group in which to create the VDB
The Oracle database name
The Oracle database unique name
The Oracle database instance number
The Oracle database instance name
The source dSource or VDB from which you wish to provision
The semanticLocation, SCN, or timestamp of the point you want to provision from. You can run these commands to get the list of
snapshots or timeflow ranges:

snapshot list database=dexample

timeflow "dexample" timeflowRanges; commit
The base mountpoint on the target server where VDB data should be mounted
The source repository (oracle install) in which to create the VDB. These can be listed with the /repository list command.
If you are using a VDB template, the name of the template to use. See the Customizing Oracle VDB Configuration Settings topic for
information on how templates affect configuration parameters on refresh.

Procedure
1. Execute the database provisioncommand.

delphix> database provision

2. Execute the defaultscommand.

delphix database provision> defaults

3. Set the timeflow point source timeflow and location.

delphix database provision defaults *> set type=TimeflowPointSemantic

delphix database provision defaults *> set container=dexample
delphix database provision defaults *> set location=LATEST_SNAPSHOT
4. Commit the operation to populate the defaults, as provided by the browser interface. At this point, the operation can be committed,
though you will likely need to change the defaults to match the information.

delphix database provision defaults *> commit

5. Set the name and group for the new VDB.

delphix database provision *> set container.name=vexample

delphix database provision *> set container.group="<New Group>"
6. Set the base mountpoint.

delphix database provision *> set source.mountBase=/mnt

7. Set the source config type to be single instance Oracle, and set the database name and database unique name. When provisioning from
a RAC or single instance oracle source, the default type will match that of the repository selected by the defaults operation.

delphix database provision *> set sourceConfig.type=OracleSIConfig

delphix database provision *> set sourceConfig.databaseName=vexample
delphix database provision *> set sourceConfig.uniqueName=vexample123
8. Set the instance name and number.

1190

Delphix User Guide 2016 Delphix

8.

delphix
delphix
delphix
delphix

database
database
database
database

provision
provision
provision
provision

*> edit sourceConfig.instance

sourceConfig.instance *> set instanceNumber=1
sourceConfig.instance *> set instanceName=vexample
sourceConfig.instance *> back

9. Set the target repository.

delphix database provision *> set sourceConfig.repository=env/'/opt/oracle'

10. Configure the Oracle database parameters. If you are using manually specified parameters, you can set the contents of source.config
Params. If you want to use a template, you can set source.configTemplate.

delphix database provision *> set source.configTemplate=exampleTemplate

11. Commit the result.

delphix database provision *> commit

1191

Delphix User Guide 2016 Delphix

CLI Cookbook: Provisioning a SQL Server VDB

This topic describes how to provision a SQL Server VDB using the command line interface.

Prerequisites
You will need the following information:
The name of the VDB you want to create
The group in which to create the VDB
The SQL Server database name for the VDB
The source dSource or VDB from which you wish to provision
The semanticLocation, LSN, or timestamp of the point you want to provision from. You can run these commands to get the list of
snapshots or timeflow ranges:

snapshot list database=dexample

timeflow "dexample" timeflowRanges; commit
The target host on which you want to create the VDB. You can list the hosts with the /host list command.
The source repository (SQL Server instance on the target host) in which to create the VDB. These can be listed with the /repository
list command.

Procedure
1. Execute the database provision command.

delphix> database provision

2. Execute the defaults command.

delphix database provision> defaults

3. Set the timeflow point source timeflow and location.

delphix database provision defaults *> set type=TimeflowPointSemantic

delphix database provision defaults *> set container=dexample
delphix database provision defaults *> set location=LATEST_SNAPSHOT
4. Commit the operation to populate the defaults, as provided by the browser interface. At this point, the operation can be committed,
though you will likely need to change the defaults to match the information.

delphix database provision defaults *> commit

5. Set the name and group for the new VDB.

delphix database provision *> set container.name=vexample

delphix database provision *> set container.group="<New Group>"
6. Set the database name for the VDB on the target SQL Server instance.

delphix database provision *> set sourceConfig.databaseName=vexample

7. Set the target host.

delphix database provision *> edit sourceConfig.instance

delphix database provision sourceConfig.instance *> set host=targethost
delphix database provision sourceConfig.instance *> back
8. Set the target repository.

delphix database provision *> set sourceConfig.repository=targetEnv/SQLServer2008

9. Commit the result.

1192

Delphix User Guide 2016 Delphix

9.

delphix database provision *> commit

1193

Delphix User Guide 2016 Delphix

CLI Cookbook: Provisioning a VDB from a TimeFlow Bookmark

This topic describes how to create a TimeFlow bookmark and use it to provision a single instance Oracle VDB using the Delphix Engine command
line interface.
You can create TimeFlow bookmarks to give a semantically meaningful name to a TimeFlow point (scn, location or timestamp within a TimeFlow).
You can then use the bookmarks you created to execute the following database operations:
Provision
Refresh
Export
Test file mappings
VDB Rewind

Prerequisites
You will need the following information:
The name of the timeflow bookmark you want to create
The name of the VDB you want to create
The group in which to create the VDB
The Oracle database name
The Oracle database unique name
The Oracle database instance number
The Oracle database instance name
The source dSource or VDB from which you wish to provision
The SCN, or timestamp of the point you want to provision from. You can run these commands to get the list of snapshots or timeflow
ranges:

snapshot list database=dexample

timeflow "dexample" timeflowRanges; commit
The base mountpoint on the target server where VDB data should be mounted
The source repository (oracle install) in which to create the VDB. These can be listed with the /repository list command.

Creating the TimeFlow Bookmark

1. Execute the timeflow bookmark create command.

delphix> timeflow bookmark create

2. Set the timeflow point to be Oracle timeflow point.

delphix timeflow bookmark create *> set timeflowPoint.type=OracleTimeflowPoint

3. Set the timeflow point timeflow and location

delphix timeflow bookmark create *> set timeflowPoint.timeflow=dexample/default

delphix timeflow bookmark create *> set timeflowPoint.location=1945519455791
4. Set the name of the timeflow bookmark

delphix timeflow bookmark create *> set name=myTimeFlowBookmark

5. Commit the result

delphix timeflow bookmark create *> commit

TIMEFLOW_BOOKMARK-1
6. Display the list of timeflow bookmarks

1194

Delphix User Guide 2016 Delphix

delphix> timeflow bookmark ls

Objects
NAME
TAG
TIMEFLOW
myTimeFlowBookmark dexample/default
Operations
create

Provisioning from a TimeFlow Bookmark

1. Execute the database provision command.

delphix> database provision

2. Set defaults and provide container (VDB or dSource) that you will be provisioning from

delphix database provision > defaults

delphix database provision defaults > set container=<VDB or dSource>
delphix database provision defaults > commit
3. Set the timeflowPointParameters type to be TimeflowBookmark.

delphix database provision *> set timeflowPointParameters.type=TimeflowPointBookmark

4. Set the timeflow bookmark.

database provision *> set timeflowPointParameters.bookmark=myTimeFlowBookmark

5. Set the name and group for the new VDB.

delphix database provision *> set container.name=vexample

delphix database provision *> set container.group="Untitled"
6. Set the base mountpoint.

delphix database provision *> set source.mountBase=/mnt

7. Set the source config type to be single instance Oracle, and set the database name and database unique name.

delphix database provision *> set sourceConfig.type=OracleSIConfig

delphix database provision *> set sourceConfig.databaseName=vexample
delphix database provision *> set sourceConfig.uniqueName=vexample123
8. Set the instance name and number.

delphix
delphix
delphix
delphix

database
database
database
database

provision
provision
provision
provision

*> edit sourceConfig.instance

sourceConfig.instance *> set instanceNumber=1
sourceConfig.instance *> set instanceName=vexample
sourceConfig.instance *> back

9. Set the target repository.

delphix database provision *> set sourceConfig.repository=env/'/opt/oracle'

10. Commit the result.

delphix database provision *> commit

1195

Delphix User Guide 2016 Delphix

CLI Cookbook: Rolling Forward a VDB

This topic describes how to roll forward a virtual database after it has been rewound, as described in Rewinding a VDB.
Once a VDB has rewound to a specific TimeFlow point, the snapshots of its previous states are still available in Delphix Engine storage, and be
accessed via the command line interface to restore those previous states. This is referred to as "rolling forward" a VDB.

Procedure
1. Use the ls command to find the VDB you want to roll forward.
In this example the TimeFlows and their associated containers are listed. The VDB called PVDB will be the one to roll forward.

delphix timeflow> ls
Objects
NAME
CONTAINER
PARENTPOINT.LOCATION PARENTPOINT.TIMESTAMP
hrprod/default
hrprod
erpprod/default
erpprod
'DB_PROVISION@2013-11-25T17:37:06' PVDB
657925
'DB_ROLLBACK@2013-11-25T18:24:16'
PVDB
678552

PARENTPOINT.TIMEFLOW
-

erpprod/default
'DB_PROVISION@2013-11-25T17:37:06'

2. Use the Select command to select the database.

delphix database> select PVDB

3. Use the rollback command to roll forward the VDB.

delphix database "PVDB"> rollback

4. Use the ls command to display options for selecting TimeFlow parameters.

delphix database "PVDB" rollback *> ls

Properties
type: OracleRollbackParameters
credential: (unset)
timeflowPointParameters:
type: TimeflowPointSemantic
container: (required)
location: LATEST_POINT
username: (unset)
5. Because this VDB was rolled back, two TimeFlows now exist for it. To rollback the VDB and roll it forward, select the original TimeFlow,
because the original snapshots are associated with that TimeFlow.

delphix database "PVDB" rollback *> set

timeflowPointParameters.type=TimeflowPointLocation
delphix database "PVDB" rollback *> set
timeflowPointParameters.timeflow='DB_PROVISION@2013-11-25T17:37:06'
6. Use the ls command to view the parameter options for the TimeFlow you selected.

1196

Delphix User Guide 2016 Delphix

delphix database "PVDB" rollback *> ls

Properties
type: OracleRollbackParameters
credential: (unset)
timeflowPointParameters:
type: TimeflowPointLocation (*)
location: LATEST_POINT
timeflow: 'DB_PROVISION@2013-11-25T17:37:06' (*)
username: (unset)
7. Set the TimeFlow location to rollback the VDB to a particular Oracle SCN.

delphix database "PVDB" rollback *> set timeflowPointParameters.location=678994

8. Use the ls command to review all the options you selected before executing the commit.

delphix database "PVDB" rollback *> ls

Properties
type: OracleRollbackParameters
credential: (unset)
timeflowPointParameters:
type: TimeflowPointLocation (*)
location: 678994 (*)
timeflow: 'DB_PROVISION@2013-11-25T17:37:06' (*)
username: (unset)
9. Commit the changes.

delphix database "PVDB" rollback *> commit

Dispatched job JOB-369
DB_ROLLBACK job started for "ERP/PVDB".
Starting provision of the virtual database "PVDB".
Creating new TimeFlow.
Generating recovery scripts.
Exporting storage.
Validating user environment settings on target host.
Mounting filesystems for the virtual database instance "1".
Mounting read-only archive log filesystem for the virtual database instance "1".
Running user-specified pre-provisioning script.
Recovering Oracle database.
Opening the virtual database "PVDB".
Opening Oracle database.
Oracle recovery was successful.
Unmounting read-only archive log filesystem for the virtual database instance
"1".
Running user-specified post-provisioning script.
The virtual database "PVDB" was successfully provisioned.
Starting snapshot of virtual database.
Processing database files of virtual database.
Creating snapshot of virtual database.
Finalizing snapshot of virtual database.
Virtual database "PVDB" snapshot successful.
DB_ROLLBACK job for "ERP/PVDB" completed successfully.

Related Links
Rewinding a VDB

1197

Delphix User Guide 2016 Delphix

CLI Cookbook: Refresh a VDB from a Specific Timepoint or Latest

This topic describes the steps to Refresh a VDB from a specific Timepoint or from Latest.
You can refresh from any point on Timeflow using SCN, location, or timestamp.

Prerequisites
You will need the following information:
The VDB name

The Timeflow location, SCN, or timestamp of the point you want to provision from.
Login to CLI:
$ ssh delphix_admin@<delphixengine>
Determine the TimeFlow

Run:

> timeflow "<dSource>" timeflowRanges

> commit
> cd
Perform the Refresh from specific Timepoint

> database
> select <VDB name>
> refresh
> set timeflowPointParameters.type= (one of TimeflowPointBookmark,
TimeflowPointBookmarkTag, TimeflowPointLocation, TimeflowPointSemantic,
TimeflowPointTimestamp as appropriate)
> set timeflowPointParameters.location= (the location, timestamp, or bookmark you wish to
refresh to)
> set timeflowPointParameters.timeflow= (the timeflow associated with location)
> commit
Perform the Refresh from Latest

>
>
>
>
>

database
select <yourdatabase>
refresh
set timeflowPointParameters.container= (Parent of VDB)
commit

1198

Delphix User Guide 2016 Delphix

CLI Cookbook: Repairing a Timeflow

Prerequisites
Know the dSource and Group you need to repair from

Procedure
1. Log into the Delphix Engine as an Admin user. Go to timeflow and then list. Find the timeflow that needs to be repaired.

ssh delphix_admin@<yourengine>
delphix > timeflow
delphix timeflow > ls
2. Go to oracle/log and list the missing logs for the timeflow, the maximum number of logs reported is controlled by the value of the pageSize
argument, if there's a very large number of missing logs this may need to be increased. Note the start and end scn of the missing log.

delphix timeflow oracle log> list timeflow=example missing=true pageSize=1000

3. Stage the missing logs. Verify there is sufficient free space and then copy or restore the missing archive logs into an empty directory on a
server the Delphix engine can access via the network. All files in the directory are examined so starting with an empty directory speeds up the
process. Verify the user being specified in the next step has permissions to read these archive log files in the directory.
4. Run the fetch command and set all of the following fields

delphix timeflow
delphix timeflow
delphix timeflow
delphix timeflow
file]
delphix timeflow
delphix timeflow
delphix timeflow
the file to]
delphix timeflow
delphix timeflow
delphix timeflow
delphix timeflow

oracle
oracle
oracle
oracle

log > fetch

log fetch *> set type=TimeflowLogFetchParameters
log fetch *> set timeflow=example
log fetch *> set directory=[directory where you restored the log

oracle log fetch *> set endLocation=[end SCN of the sequence]

oracle log fetch *> set startLocation=[start SCN of the sequence]
oracle log fetch *> set host=[hostname or IP of the host you restored
oracle
oracle
oracle
oracle

log
log
log
log

fetch
fetch
fetch
fetch

*>
*>
*>
*>

set username=[a user that can read the file]

edit credentials
set type=PasswordCredential
set password=[password for this user]

5. Commit the Changes

delphix timeflow oracle log fetch *> commit

Note: Only do ONE repair job at a time

NOTE It is possible there may be more than one timeflow visible for a given container/source, if so you can verify the current timeflow being used with:

delphix > database

delphix database > select 'example'
delphix database "example"> ls
look for the "currentTimeflow" value.

1199

Delphix User Guide 2016 Delphix

CLI Cookbook: Changing SGA Parameter

Below outlines the procedure to change SGA parameter setting on a provisioned VDB.

Procedure
1. Log into the Delphix Engine as delphix_admin or a user with Admin privileges.
2. Go to source and then select the name of the VDB that you would like to change the parameters of
3. You are then going to update and edit the configParams
4. Next you are going to set the sga_target= the correct value
5. Commit the operation so that it saves

Example
ssh delphix_admin@engine
delphix > source
delphix source > select "vdb_example"
delphix source "vdb_example" > update
delphix source "vdb_example" *> set sga_target=new value
delphix source "vdb_example" *> commit

1200

Delphix User Guide 2016 Delphix

CLI Cookbook: Rolling Back a VDB

Rolling Back or Rewinding to a Snapshot from another timeflow
1. Log into the Delphix Engine

ssh delphix_admin@delphix_engine
2. List Timeflows for the database that you want to rollback to

de > ls
de > timeflow
de timeflow > ls
3. Switch to the VDB you want to rollback

de timeflow > cd /database

de database > ls
de database > select "vdb_example"
4. Use the switchTimeflow operation

de database 'vdb_example' > switchTimeflow

de database 'vdb_example' switchTimeflow *> set timeflow=<different timeflow>
de database 'vdb_example' switchTimeflow *> commit
5. Rollback VDB using the VDB rollback function (note this can also be done in the GUI)

de
de
de
de

database
database
database
database

'vdb_example'
'vdb_example'
'vdb_example'
'vdb_example'

> rollback
rollback *> set timeflowPointParameters.container=
rollback *> set timeflowPointParameters.location=
rollback *> commit

Rolling Back or Rewinding to a Timeflow Bookmark

Requirements: Know the timeflow bookmark that you want to use
1. Log into the Delphix Engine

ssh delphix@<yourengine>
2. Retrieve database and time flow information that you would like to rewind/rollback to

delphix > ls
delphix database > select "dexample"
delphix database "dexample" > get currentTimeflow

3. Rollback/Rewind VDB

delphix database "dexample" > rollback

delphix database "dexample" rollback *> ls
delphix database "dexample" rollback *> set
timeflowPointParameters.type=TimeflowPointBookmark
delphix database "dexample" rollback *> set timeflowPointParameters.bookmark="bookmark
example"
delphix database "dexample" rollback *> commit

Related Support or Delphix Documentation Topics

1201

Delphix User Guide 2016 Delphix

Creating a Bookmark in the CLI

Rewinding a VDB Using the GUI

1202

Delphix User Guide 2016 Delphix

CLI Cookbook: Creating a VDB Config Template

This topic will address how to create a VDB Config Template in the CLI; this functionality is also available in the GUI

Procedure
1. ssh into you delphix engine using delphix_admin credentials

ssh delphix_admin@<yourdelphixengine>
2. Go to database and then template and then create

delphix
delphix
delphix
delphix
delphix

> database template

database template > create
database template create *> set name=
database template create *> set parameters.<set parameters you want>
database template create *> set sourceType=

3. Verify information and commit

delphix database template create *> ls

delphix database template create *> commit

Example:

ssh delphix_admin@testengine
testengine > database template
testengine database template > create
testengine database template create *>
testengine database template create *>
testengine database template create *>
testengine database template create *>

set name=test_template
set parameters.none
set sourceType=OracleVirtualSource
ls

Properties
type: DatabaseTemplate
name: test_template (*)
description: (unset)
parameters:
none: none (*)
sourceType: OracleVirtualSource (*)
testengine database template create *> commit

1203

Delphix User Guide 2016 Delphix

CLI Cookbook: Creating a Policy

This will outline how to create a policy in the CLI, please not that you can also do this in the GUI

Procedure
1. ssh into your Delphix Engine using delphix_admin credentials

ssh delphix_admin@delphixengine
delphix > ls
2. Go to policies and createAndApply (please note that you cannot just create a policy, you must createAndApply, in the GUI you
have the option to just create) and set your policy parameter

delphix > policy

delphix policy > createAndApply
delphix policy createAndApply *> set policy.type=< choose from QuotaPolicy,
RefreshPolicy, RetentionPolicy, SnapshotPolicy or SyncPolicy)
delphix policy createAndApply *> set policy.name=< name your policy>
delphix policy createAndApply *> set policy.customized=true
delphix policy createAndApply *> set policy.
delphix policy createAndApply *> set policy.provisionSource=(LATEST_SNAPSHOT or
LATEST_TIME_FLOW_LOG)
*if doing a RefreshPolicy, SyncPolicy or SnapshotPolicy you are also going to need to add the following:

delphix
delphix
delphix
delphix
delphix

policy
policy
policy
policy
policy

createAndApply
createAndApply
createAndApply
createAndApply
createAndApply

*> edit policy.scheduleList

policy.scheduleList * > add
policy.scheduleList * > set cronString=
policy.scheduleList * > set cutoffTime=
policy.scheduleList * > back

3. Set your target parameters which are going to be a container, group etc

delphix policy createAndApply *> set target=

4. Verify and commit

delphix policy createAndApply *> ls

delphix policy createAndApply *> commit

1204

Delphix User Guide 2016 Delphix

CLI Cookbook: Provisioning a SAP ASE VDB

This topic describes how to provision an SAP ASE VDB using the command line interface.
Prerequisites
Procedure

Prerequisites
You will need the following information:
The name of the VDB you want to create
The group in which to create the VDB
The SAP ASE database name for the VDB
The source dSource or VDB from which you wish to provision
The semanticLocation, LSN, or timestamp of the point you want to provision from (if not using the most recent). You can run these
commands to get the list of snapshots or timeflow ranges:

snapshot list database=dexample

timeflow "dexample" timeflowRanges; commit
The target host on which you want to create the VDB. You can list the hosts with the /host list command.
The source repository (SAP ASE instance on the target host) in which to create the VDB. These can be listed with the /repository list
command.

Procedure
1. Execute the database provision command.

delphix> database provision

2. Set the type for the new VDB

delphix database provision *> set type=ASEProvisionParameters

3. Use defaults to fill in most of the information and then customize any additional information that you do not want defaulted, for what
information has been filled in after defaults you can do an ls for all fields:

delphix database provision *> defaults

delphix database provision *> ls

4. Set the name and group for the new VDB.

delphix database provision *> set container.name=<vexample>

delphix database provision *> set container.group="<New Group>"
5. Set the name of the new VDB.

delphix database provision *> set sourceConfig.databaseName=<vexample>

6. Set the source configuration properties on the target SAP ASE instance

delphix database provision *> edit sourceConfig.instance

delphix database provision sourceConfig.instance *> set host=<targethost>
delphix database provision sourceConfig.instance *> back
7. Set the target Dataset Home.

delphix database provision *> set sourceConfig.repository=<Dataset Home>

8. Set the source container from which to provision.

delphix database provision *> set timeflowPointParameters.container=<dexample>

9.
1205

Delphix User Guide 2016 Delphix

9. Set the desired value for truncateLogOnCheckpoint

delphix database provision *> set truncateLogOnCheckpoint=false

10. Commit the configuration and start the DB_PROVISION job

delphix database provision *> commit

1206

Delphix User Guide 2016 Delphix

CLI Cookbook: Taking a Snapshot

This article is to document how to take a Snapshot outside of the normal snapshot policy time using the CLI, you can also do this in the GUI using
the camera icon. A Snapshot of a VDB is similar to bookmarking a point in time in the life of the VDB.

Procedure:
1. ssh into the delphix engine using delphix_admin credentials
2. Go into databases and select the VDB or dSource you would like to take a Snapshot of

ssh delphix_admin@dengine
delphix > database
delphix database > select vdb_test
3. You are now going to sync and commit the operation

delphix database "vdb_test" > sync

delphix database "vdb_test" sync *> commit
4. You can verify the snapshot by going to snapshots and listing them

delphix database "vdb_test" > /snapshot

delphix snapshot > ls

Related Articles:
CLI Cookbook: Creating Policies

1207

Delphix User Guide 2016 Delphix

CLI Cookbook: Determining the Snapshot used to provision a VDB

Procedure:
*In Delphix 3.0 and higher, the parent snapshot can be determined using the CLI as follows:
1. Log into the server as a Delphix administrator:

ssh delphix_admin@<server_ip>
2. Select the VDB.

delphix> database
delphix database> ls
Objects
NAME
PARENTCONTAINER
dSource1
dSource2
VDB1
dSource1
VDB2
dSource2
VDB3
dSource1
delphix database> select VDB1

DESCRIPTION

3. List the VDB parameters, and make a note of the currentTimeflow value.

delphix database "VDB1"> ls

Properties
type: OracleDatabaseContainer
name: VDB1
currentTimeflow: VDB1/default
description: (unset)
diagnoseNoLoggingFaults: true
endianness: BIG_ENDIAN
group: <New Group>
masked: false
os: HP-UX
parentContainer: dSource1
performanceMode: false
processor: ia64
reference: ORACLE_DB_CONTAINER-10
runtime:
type: OracleDBContainerRuntime
logSyncActive: true
sourcingPolicy:
type: OracleSourcingPolicy
encryptedLinkingEnabled: false
logsyncEnabled: true
logsyncInterval: 300
logsyncMode: ARCHIVE_ONLY_MODE
version:
4. Select the Timeflow listed for the VDB.

1208

Delphix User Guide 2016 Delphix

delphix database "VDB1"> /timeflow

delphix timeflow> select VDB1/default
List the timeflow parameters. The Snapshot used to provision the VDB is listed as
parentSnapshot

delphix timeflow "VDB1/default"> ls

Properties
5. List the Timeflow parameters. The Snapshot used to provision the VDB is listed as parentSnapshot.

delphix timeflow "VDB1/default"> ls

Properties

type: OracleTimeflow
name: VDB1/default
container: VDB1
parentPoint:
type: OracleTimeflowPoint
location: 141285148
timeflow: dSource1/default
parentSnapshot: @2013-02-14T15:07:28.491Z
reference: ORACLE_TIMEFLOW-92572

1209

Delphix User Guide 2016 Delphix

CLI Cookbook: Detaching and Attaching a SAP ASE dSource

This CLI cookbook recipe describes how to Detach and Attach an SAP ASE dSource using the CLI, please note that you cannot detach a
dSource from the GUI or the CLI however reattach is strictly through the CLI.

Prerequisites
A dSource can only be attached to a new data source once it has been unlinked.
When attaching an SAP ASE dSource to a new data source, the new data source must be the same logical database satisfying the following
constraints:
Same dbid
Same dbname
Same creation time
You must also make sure that you follow the normal prerequisites for an SAP ASE data source found in Requirements for SAP ASE Source
Hosts and Databases.

Procedure
Detach a dSource
1. Login to the CLI as delphix_admin or a user with Admin privileges
2. Select the dSource.

delphix> database "dexample"

3. Run the detachSourcecommand, specifying the currently active source. Note: This step can be skipped if the dSource has already been
detached through the GUI.

delphix database "dexample"> detachSource

delphix database "dexample" detachSource *> set source=dexample
delphix database "dexample" detachSource *> commit
Attach a dSource
1. Log into the CLI as delphix_admin or a user with Admin privileges
2. Run the attachSource command.

delphix database "dexample"> attachSource

delphix database "dexample" attachSource *> set source.name=source_ASE_servername_example
delphix database "dexample" attachSource *> set
source.config=source_ASE_servername_example/dexample
delphix database "dexample" attachSource *> set dbCredentials.password=sybase
delphix database "dexample" attachSource *> set dbUser=sa
delphix database "dexample" attachSource *> set source.loadBackupPath=/tmp/backups
delphix database "dexample" attachSource *> set
sourceHostUser="source_host_environment/sybase"
delphix database "dexample" attachSource *> set
stagingHostUser="staging_host_environment/sybase"
delphix database "dexample" attachSource *> set
stagingRepository="staging_ASE_servername_example"
delphix database "dexample" attachSource *> edit source.operations.preSync
delphix database "dexample" attachSource source.operations.preSync *> add
delphix database "dexample" attachSource source.operations.preSync 0 *> get
type: RunCommandOnSourceOperation (*)
command: (required)

1210

Delphix User Guide 2016 Delphix

delphix
delphix
delphix
delphix
delphix
delphix

database
database
database
database
database
database

"dexample"
"dexample"
"dexample"
"dexample"
"dexample"
"dexample"

attachSource
attachSource
attachSource
attachSource
attachSource
attachSource

source.operations.preSync 0 *> set command=#

source.operations.preSync 0 *> back
source.operations.preSync *> back
*> edit source.operations.postSync
source.operations.postSync *> add
source.operations.postSync 0 *> get

type: RunCommandOnSourceOperation (*)

command: (required)
delphix database
delphix database
delphix database
delphix database
Properties

"dexample"
"dexample"
"dexample"
"dexample"

attachSource
attachSource
attachSource
attachSource

source.operations.postSync 0 *> set command=#

source.operations.postSync 0 *> back
source.operations.postSync *> back
*> ls

type: ASEAttachSourceParameters
dbCredentials:
type: PasswordCredential
password: ******** (*)
dbUser: sa (*)
source:
type: ASELinkedSource
name: source_ASE_servername_example (*)
config: dexample (*)
externalFilePath: (unset)
loadBackupPath: /tmp/backups (*)
loadBackupServerName: source_backupserver_name_example (*)
monitorLocation: (unset)
operations:
type: LinkedSourceOperations
postSync:
0:
type: RunCommandOnSourceOperation (*)
command: # (*)
preSync:
0:

1211

Delphix User Guide 2016 Delphix

type: RunCommandOnSourceOperation (*)

command: # (*)
sourceHostUser: source_ASE_servername_example/sybase (*)
stagingHostUser: staging_ASE_servername_example/sybase (*)
stagingPostScript: (unset)
stagingPreScript: (unset)
stagingRepository: staging_ASE_servername_example (*)
delphix database "dexample" attachSource *> commit
ASE_DB_CONTAINER-3
Dispatched job JOB-25

1212

Delphix User Guide 2016 Delphix

DB_ATTACH_SOURCE job started for "Untitled/dexample".

DB_ATTACH_SOURCE job for "Untitled/dexample" completed successfully.
Note: this command is only necessary if you are using a Remote Backup Server configuration from staging to source, instead of an
NFS mounted shared directory for backups and transaction log dumps:

delphix database "dexample" attachSource *> set

source.loadBackupServerName=source_backupserver_name_example

1213

Delphix User Guide 2016 Delphix

CLI Cookbook: Replication

These topics describe how to use the command line interface for replication tasks.
CLI Cookbook: Adding a Replication Spec
CLI Cookbook: Deleting a Replication Spec
CLI Cookbook: Failing Over a Namespace
CLI Cookbook: Triggering Immediate Execution of a Replication Spec

1214

Delphix User Guide 2016 Delphix

CLI Cookbook: Adding a Replication Spec

This topic describes how to use the command line interface to add a replication specification to the Delphix Engine.
Unlike the GUI, the CLI supports the ability to manage multiple replication specifications within a single system. This allows updates to be sent to
multiple systems from a single point.

Prerequisites
You should review the topic Replication Overview to understand which objects are copied as part of a backup or restore operation, as
well as the dependencies between objects.

Procedure
1. Switch to the replication spec context.

delphix> cd replication/spec
delphix replication spec> ls
Operations
create
2. Create a new replication spec.

delphix replication spec> create

delphix replication spec create *> ls
Properties
type: ReplicationSpec
name: (unset)
bandwidthLimit: (unset)
enabled: (unset)
encrypted: (unset)
objects: (required)
schedule: (unset)
targetCredential:
type: PasswordCredential
password: (required)
targetHost: (required)
targetPrincipal: (required)
3. Specify the target host name, user, and credentials.

delphix replication spec create *> set targetHost=exampleHost.mycompany.com

delphix replication spec create *> set targetPrincipal=delphix_admin
delphix replication spec create *> set targetCredential.password=password
Target Principal
The target principal must be a Delphix user on the target host who has domain privileges.

4. Specify the set of objects to replicate.

a. To replicate all dSources and VDBs on the system, specify `DOMAINas the list of objects.

delphix replication spec create *> set objects=`DOMAIN

b. To replicate a subset of Groups, VDBs and dSources, specify their names as a comma-separated list.

delphix replication spec create *> set objects=dExample1,dExample2

Name Completion
The CLI will provide possible completions for all objects in the system, but only groups, dSources and VDBs can be
specified. Attempts to replicate other types of objects will generate an error when the operation is committed.

5.
1215

Delphix User Guide 2016 Delphix

5. Commit the operation.

delphix replication spec create *> commit

`REPLICATION_SPEC-1

1216

Delphix User Guide 2016 Delphix

CLI Cookbook: Deleting a Replication Spec

This topic describes how to use the command line interface to delete a replication spec.

Procedure
1. Switch to the replication spec context and list the specs on the system.

delphix> cd replication/spec
delphix replication spec> ls
Objects
REFERENCE
TARGETHOST
REPLICATION_SPEC-1 exampleHost.mycompany.com
Operations
create
2. Select the replication spec to remove.

delphix replication spec> select REPLICATION_SPEC-1

delphix replication spec "exampleHost.mycompany.com">
3. Remove the spec.

delphix replication spec "exampleHost.mycompany.com"> delete

delphix replication spec "exampleHost.mycompany.com" delete *> commit

1217

Delphix User Guide 2016 Delphix

CLI Cookbook: Failing Over a Namespace

This topic describes how to use the command line interface to fail over a namespace.

Procedure
1. Switch to the namespace context and list the namespaces on the system

delphix> cd namespace
delphix namespace> ls
Objects
NAME
[172.16.203.93]
Operations
lookup
2. Select the namespace to failover

delphix namespace> select [172.16.203.93]

delphix namespace "[172.16.203.93]">
3. Failover the namespace

delphix namespace "[172.16.203.93]"> failover

delphix namespace "[172.16.203.93]" failover *> commit
Failover
Failover will sever the replication connection and make objects in the namespace part of the live system. This will prevent the
target from receiving subsequent incremental updates.

1218

Delphix User Guide 2016 Delphix

CLI Cookbook: Triggering Immediate Execution of a Replication Spec

This topic describes how to use the command line interface to trigger an immediate execution of a replication spec in the Delphix Engine.

Procedure
1. Switch to the replication spec context and list the specs on the system.

delphix> cd replication/spec
delphix replication spec> ls
Objects
REFERENCE
TARGETHOST
REPLICATION_SPEC-1 exampleHost.mycompany.com
Operations
create
2. Select the replication spec to execute.

delphix replication spec> select REPLICATION_SPEC-1

delphix replication spec "exampleHost.mycompany.com">
3. Execute the spec.

delphix replication spec "exampleHost.mycompany.com"> execute

delphix replication spec "exampleHost.mycompany.com" execute *> commit
Dispatched job JOB-7
REPLICATION_SEND job started.
Connecting to target "exampleHost.mycompany.com".
Preparing replication update.
Starting incremental replication update.
Sending metadata.
Sending data for "Untitled".
Sending data for "Untitled/redsox1".
Transfer completed in 0:00:01, sent 1.39MB (1.39MB/s).
Committing serialization state.
REPLICATION_SEND job completed successfully.

1219

Delphix User Guide 2016 Delphix

CLI Cookbook: JetStream Actions

These entries will help with some of the JetStream Actions that can be performed in the CLI and therefore with the Delphix APIs

1220

Delphix User Guide 2016 Delphix

CLI Cookbook: How to Delete a JetStream Container

Prerequisites:

Know the container you want to delete

Have delphix_admin privileges

Procedure:

1. Log into Delphix Engine as delphix_admin

ssh delphix@<yourengine>
2. Navigate to the JetStream container that you want to delete

delphix
delphix
delphix
delphix

> jetstream container

jetstream container > ls
jetstream container > select CONTAINER_X
jetstream container 'CONTAINER_X' >

3. Delete container, note you need to set if you want to delete the VDBs in the container (false will preserve the VDBs and true the
VDBs will be deleted along with the container)

delphix jetstream container 'CONTAINER_X' > delete

delphix jetstream container 'CONTAINER_X'delete *> set
deleteDataSources=<true/false>
delphix jetstream container 'CONTAINER_X'delete *> commit

1221

Delphix User Guide 2016 Delphix

CLI Cookbook: How to Delete a JetStream Template

Prerequisites:

Template has no dependant containers

Know the name of the template you are going to delete
Have delphix_admin privileges (note JetStream Only users and Delphix GUI Owners cannot delete templates)
Procedure:

1. Log into your Delphix Engine using delphix_admin (or admin privileged account)

ssh delphix_admin@<yourengine>
2. Find the template you want to delete

delphix
delphix
delphix
delphix

> jetstream
jetstream template > ls
jetstream template > select 'TEMPLATE_X'
jetstream template 'TEMPLATE_X'>

3. Delete template and commit

delphix jetstream template 'TEMPLATE_X'> delete

delphix jetstream template 'TEMPLATE_X' delete *> commit

1222

Delphix User Guide 2016 Delphix

Web Service API Guide

These topics describe interfacing with the public web service APIs, building automation facilities and integrating with third party orchestration
tools.
API Version Information
Web Service Object Model
Web Service Protocol
CLI to Web Services Transition
GUI API Mapping
API Cookbook: Common Tasks, Workflows, and Examples
API Cookbook: Authentication
API Cookbook: Host Environment Details
API Cookbook: List Alerts and List Jobs
API Cookbook: List dSources and VDBs
API Cookbook: List Snapshots
API Cookbook: Refresh VDB
API Cookbook: Example Provision Of An Oracle VDB
API Cookbook: Stop/Start a VDB
CLI to Python Transition
Python Cookbook: Adding a UNIX Host

1223

Delphix User Guide 2016 Delphix

API Version Information

This topic describes API version information for each release of the Delphix Engine, including schema changes and links to the relevant version of
the schema.
Delphix
Engine
Version

API
Version

Link to Schema within the Appliance

Major Changes

3.0.x.x

1.0.0

http://<engine-address>/api/ json/versions/1.0.0/delphix.jso
n

Complete architectural change from 2.7 CLI.

See Migrating from the Delphix Engine 2.7
CLI and related topics for more information.

3.1.0.x 3.1.1.x

1.1.0

http:// <engine-address>/api/json/versions/1.1.0/delphix.jso
n

3.1.2+

1.1.1

http:// <engine-address>/api/json/versions/1.1.1/delphix.jso
n

3.2.0.x

1.2.0

http:// <engine-address>/api/json/versions/1.2.0/delphix.jso
n

3.2.1.x

1.2.1

http:// <engine-address>/api/json/versions/1.2.1/delphix.jso
n

3.2.2.x 3.2.3.x

1.2.2

http:// <engine-address>/api/json/versions/1.2.2/delphix.jso
n

3.2.4+

1.2.3

http:// <engine-address>/api/json/versions/1.2.3/delphix.jso
n

4.0.0.x

1.3.0

http://<engine-address>/api/json/versions/1.3.0/delphix.json

4.0.1.x - 4.0.
2.x

1.3.1

http://<engine-address>/api/json/versions/1.3.1/delphix.json

4.0.3+

1.3.2

http://<engine-address>/api/json/versions/1.3.2/delphix.json

4.1.0.x

1.4.0

http://<engine-address>/api/json/versions/1.4.0/delphix.json

4.1.1.x

1.4.1

http://<engine-address>/api/json/versions/1.4.1/delphix.json

4.1.2.x 4.1.3.x

1.4.2

http://<engine-address>/api/json/versions/1.4.2/delphix.json

4.1.4+

1.4.3

http://<engine-address>/api/json/versions/1.4.3/delphix.json

4.2.1.x

1.5.0

http://<engine-address>/api/json/versions/1.5.0/delphix.json

4.2.2.x

1.5.1

http://<engine-address>/api/json/versions/1.5.1/delphix.json

4.2.3.x

1.5.2

http://<engine-address>/api/json/versions/1.5.2/delphix.json

4.2.4.x 4.2.5.x

1.5.3

http://<engine-address>/api/json/versions/1.5.3/delphix.json

4.3.1.x 4.3.2.x

1.6.0

http://<engine-address>/api/json/versions/1.6.0/delphix.jso
n

4.3.3.x

1.6.1

http://<engine-address>/api/json/versions/1.6.1/delphix.jso
n

4.3.4.x

1.6.2

http://<engine-address>/api/json/delphix.json

Related Links
Migrating from the Delphix Engine 2.7 CLI

1224

Affects

Delphix User Guide 2016 Delphix

Web Service Object Model

This topic describes the Delphix object model as exported over the web services.

Object Types
All objects in the Delphix API are "typed objects." All such objects have a type field that indicates the type of the object and its associated
semantics. This allows for object inheritance and polymorphism without requiring separate APIs for each type, and allows generic client-specific
semantic encoding and decoding without having to be aware of the context. This means that even APIs that operate only a specific type (such as
the Group API) still require a type field to be specified as part of the input, and will continue to report the type of objects when listing or retrieving
objects. This allows the APIs to evolve in a backwards-compatible fashion through the introduction of new types.
Certain "root" object types (groups, containers, sources, etc) have an associated API. This API is rooted at a particular point under /resources/
json/delphix, but all APIs follow a standard format beneath this namespace. The CLI namespace is a direct reflection of this URL, and the API
reference has an index both by object type as well as by object (CLI) path. These APIs may operate on different extended types (such as Oracle
SIConfig and OracleRACConfig), but the base operations remain the same regardless of input type.

Object References
Some objects returned by the APIs are pure typed objects, in that they don't represent persistent state on the Delphix Engine but are rather
calculated and returned upon request. Most of the objects in the system, however, are "persistent objects." Persistent objects (of type Persisten
tObject) have a stable reference that uniquely identifies the object on the system. This reference is separate from its name, so that objects can
be renamed without affecting the programmatic API. More information about object names and how they can be represented generically can be
found in the CLI documentation. Object references are opaque tokens; while they can be stored and re-used for later use, an interpretation of
their contents is unstable and may break in a future release.
The Delphix object hierarchy is stitched together by these object references. When fetching an object that refers to another object, the member
will be returned as a reference, rather than being inserted directly within the parent object. This allows consumers to control when and how links
are resolved, and makes it clear when an object may change independently from its parent. The per-object APIs outlined below all operate on
object references.
Note that some Delphix objects are singleton objects, and there is only one such object on the system. These objects do not have references
because the API URL uniquely identifies the object on the system.

API Operations
All APIs optionally support the following operations:
CREATE - Create a new instance of the given object type. This is used for most objects, but more complicated objects, such as dSources
and VDBs, must be created through a dedicated link or provision operation. The input to this operation is typically the object itself,
though some objects may have specialized parameters used during the creation of objects. An example of this is HostEnvironmentCr
eateParameters.
UPDATE - Update properties of the given object, specified as an object reference in the URL.
DELETE - Delete a particular object, specified as an object reference in the URL. These operations are typically done as HTTP DELETE
operations, but it is also possible to do a POST operation to the /delete API to do the same thing. The POST form allows for
delete-specific parameters, such as OracleDeleteParameters.
GET - Get the properties for a particular object, specified as an object reference in the URL.
LIST - List all objects of the given type within the system. These APIs typically take optional query parameters that allow the set of
results to be constrained, filtered, paginated, or sorted.
In addition, the following non-CRUD operations may be supported:
Root Operation - A POST or GET operation to the root of an API namespace, not associated with a particular object. This can be
used for singleton objects, such as NDMPConfig, operations that create objects, such as link, and operations that operate on multiple
objects at once.
Per-object Operation - A POST operation to a particular object reference. These operations are typically read-write, but are not required
to be so. These would include read-only operations that cannot be modeled as CRUD operations or require complex input use per-object
operations.

Database Object Model

In order to support a wide variety of databases and database configurations, the database object model is more complex than it may initially
appear after having used the Delphix GUI. For example, there is no such thing as a "dSource" or "VDB" object, only data "containers" with

1225

Delphix User Guide 2016 Delphix

attached "sources". More information about how Database objects are modeled within Delphix can be found in the CLI documentation.

Asynchronous Execution
All APIs are designed to be transactionally safe and "quick." However, there are operations that may take a long period of time, or may need to
reach out to external hosts or databases such that they cannot be done safely within the context of a single API call. Such operations will dispatch
a Job to handle asynchronous execution of the operation. Any API can potentially spawn a job, and which APIs spawn jobs and which do not
may differ between object types or releases. If you are developing a full-featured automation system, it is recommended that you build a generic
infrastructure to handle job monitoring, rather than encoding the behavior of particular APIs that may change over time.
Every operation, except for LIST and GET, which are guaranteed to be read-only, can potentially spawn a job. This is represented by the job fiel
d of the APIResult object. If this field is null, then the action can be completed within the bounds of the API call. Otherwise, a reference to a
dispatched job is returned.
Jobs can spawn other jobs for especially complex operations, such as provisioning to an Oracle cluster environment. The job returned in the API
invocation is the root job, and overall success or failure of the operation is determined by the state of this job. Some operations may succeed even
if a child job fails. An example would be provisioning to an Oracle cluster where one node failed, but others were successful.
Progress can be monitored by examining the JobEvent objects in the Job object returned through the job API.

1226

Delphix User Guide 2016 Delphix

Web Service Protocol

This topic describes an overview of the web service API and available facilities.

Introduction
The Delphix Engine provides a set of public stable web service APIs (application programming interfaces). The web services form the basis upon
with the GUI and CLI are built, and are designed to be public and stable. This guide covers the basic operation of the protocol, concepts, and
considerations when building layered infrastructure. It is not a reference for all available APIs. For more information on available APIs, go to the
'/api' URL of a Delphix appliance, which will provide a complete reference of all available APIs for the version of Delphix running on that system.

http://<server>/api
The CLI is a thin veneer over the web services. If you are new to the web services, it is recommended you first test out operations with the CLI,
and use the setopt trace=true option to dump the raw data being sent and received to see the API in action.

Protocol Operation
The Delphix web services are a RESTful API with loose CRUD semantics using JSON encoding.
The following HTTP methods are supported:
GET - Retrieve data from the server where complex input is not needed. All GET requests are guaranteed to be read-only, but not all
read-only requests are required to use GET. Simple input (strings,number, boolean values) can be passed as query parameters.
POST - Issue a read/write operation, or make a read-only call that requires complex input. The optional body of the call is expressed as
JSON.
DELETE - Delete an object on the system. For languages that don't provide a native wrapper for DELETE, or for delete operations with
optional input, all delete operations can also be invoked as POST to the same URL with /delete appended to it.
Regardless of the operation, the result is returned as a JSON encoded result, the contents of which are covered below. For example, the following
invocation of curl demonstrates establishing a new Session (pretty-printing the result):

$ curl -s -X POST -k --data @- http://delphix-server/resources/json/delphix/session \

-H "Content-Type: application/json" <<EOF
{
"type": "APISession",
"version": {
"type": "APIVersion",
"major": 1,
"minor": 4,
"micro": 3
}
}
EOF
{
"status":"OK",
"result": {
"type":"APISession",
"version": {
"type": "APIVersion",
"major": 1,
"minor": 4,
"micro": 3
},
"locale": "en_US",
"client": null
},
"job": null
}
NOTE: It is generally recommended to set the API session version to the highest level supported by your Delphix engine.

1227

Delphix User Guide 2016 Delphix

Session Establishment
Login involves establishing a session and then authenticating to the Delphix Engine. Only authenticated users can access the web APIs. Each
user must establish a session prior to making any other API calls. This is done by sending a Session object to the URL /resources/json/de
lphix/session. This session object will specify the APIVersion to use for communication between the client and server. If the server doesn't
support the version requested due to an incompatible change reflected in the API major version number, an error will be returned.
The resulting session object encodes the native server version, which can be different than the version requested by the client. If the server is
running a more recent but compatible version, any translation of input and output to the native version is handled automatically. More information
on versioning can be found in the documentation for the APIVersion object within the API reference on a Delphix system. If the client supports
multiple versions, the appropriate type can be negotiated by trying to establish a session with each major version supported, and then inspecting
the version returned.
The session will also return an identifier through browser cookies that can be reused in subsequent calls to use the same session credentials and
state without having to re-authenticate. The format of this cookie is private to the server and may change at any point. Sessions do not persist
across a server restart or reboot. The mechanism by which this cookie is preserved and sent with subsequent requests is client-specific. The
following demonstrates invoking the session login API call using curl and storing the cookies in the file ~/cookies.txt for later use:

$ curl -s -X POST -k --data @- http://delphix-server/resources/json/delphix/session \

-c ~/cookies.txt -H "Content-Type: application/json" <<EOF
{
"type": "APISession",
"version": {
"type": "APIVersion",
"major": 1,
"minor": 4,
"micro": 3
}
}
EOF

Authentication
Once the session has been established, the next step is to authenticate to the server by executing the LoginRequest API. Unauthenticated
sessions are prohibited from making any API calls other than this login request. The username can be either a system user or domain user, and
the backend will authenticate using the appropriate method. This example illustrates logging in via curl using cookies created when the session
was established:

$ curl -s -X POST -k --data @- http://delphix-server/resources/json/delphix/login \

-b ~/cookies.txt -H "Content-Type: application/json" <<EOF
{
"type": "LoginRequest",
"username": "delphix_username",
"password": "delphix_password"
}
EOF
The login API currently only supports authentication by password. There is no way to authenticate using any shared key or alternate
authentication strategy.

1228

Delphix User Guide 2016 Delphix

CLI to Web Services Transition

This topic describes using the CLI to understand the public web service APIs.
The command line interface is a direct translation of the web services API to an interactive environment. This allows you to use the CLI to
explore functionality with tab completion, integrated help, stronger type checking, and indication of expected types and required fields. When
trying to determine how to invoke an operation through the web services or interpret the results, it is recommended that you first learn how to do
the same through the CLI, and then use the provided tools to translate that into web services call.

CLI Translation to HTTP

The CLI namespace is identical to the the web service URLs for each base object and operation type. The root of all web services is /resource
s/json/delphix. Any additional CLI context is appended to this URL, joined by slashes. For example:

delphix> database provision

Is equivalent to:

POST /resources/json/delphix/database/provision
All operations in the CLI (those that require an explicit commit command) are modeled as POST HTTP calls. This is an example of a "root
operation", as they are invoked not on any particular object, but across the system as a whole. Operations that are invoked on a particular object
use a URL specific to that object:

delphix> database "dexample" refresh

Is equivalent to:

POST /resources/json/delphix/database/ORACLE_DB_CONTAINER-3/refresh
While the CLI uses names to refer to objects, at the API level we use references. Persistent objects (those with a permanent unique identity) have
a reference field that is used in all cases to refer to the object. This allows references to remain constant even if objects are renamed.
For the standard CRUD (create, read, update, delete) operations, the mapping is slightly different:
CLI Operation

HTTP API

database list

GET /resources/json/delphix/database

database create

POST /resources/json/delphix/database

database "dexample" get

GET /resources/json/delphix/database/<reference>

database "dexample" update

POST /resources/json/delphix/database/<reference>

database "dexample" delete

DELETE /resources/json/delphix/database/<reference>
POST /resources/json/delphix/database/<reference>/delete

The DELETE operation has an optional POST form that can take complex input for clients that don't support sending a payload as part of a DELET
E operation.

Tracing HTTP Calls

The CLI also provides facilities to see the raw HTTP calls being made as part of any operation. To start with, viewing data in JSON format (setop
t format=json) will provide an example of what the raw output looks like from the server. In its raw form, the CLI does not make any attempt to
interpret the results, so references are displayed as references (and not names), and sizes are displayed as their raw numeric value.
This is helpful for scripting, but the CLI also has a mode to display the requests being sent to the server, the responses received, and the URLs
used. To enable this mode, run setopt trace=true. Once you have determined how to do something through the CLI, you can use this mode
as the basis for building direct integration with the raw HTTP APIs.

1229

Delphix User Guide 2016 Delphix

delphix group> setopt trace=true

delphix group> create
delphix group create *> set name=example
delphix group create *> set description="this is an example"
delphix group create *> commit
=== POST /resources/json/delphix/group ===
{
"type": "Group",
"name": "example",
"description": "this is an example"
}
=== RESPONSE ===
{
"status": "OK",
"result": "GROUP-3",
"action": "ACTION-37",
"job": null
}
=== END ===
GROUP-3
delphix group> "example"
delphix group "example"> delete
=== GET /resources/json/delphix/group/GROUP-3 ===
=== RESPONSE ===
{
"status": "OK",
"result": {
"type": "Group",
"reference": "GROUP-3",
"namespace": null,
"name": "example",
"description": "this is an example"
},
"action": null,
"job": null
}
=== END ===
delphix group "example" delete *> commit
=== POST /resources/json/delphix/group/GROUP-3/delete ===
{}
=== RESPONSE ===
{
"status": "OK",
"result": "",
"action": "ACTION-38",
"job": null
}
=== END ===
delphix group>
When using trace mode within the context of a specific object, we refresh the contents of the object before executing each command. This results
in the GET request before the delete command in the above example.

1230

Delphix User Guide 2016 Delphix

GUI API Mapping

This topic describes how to map from GUI operations to the corresponding CLI operation.
It is not always straightforward to convert from the visual layout of the GUI to the corresponding CLI operations. This topic outlines some common
operations and indicates how they are represented in the CLI. web services, and the API documentation.

dSource Operations
GUI

CLI

API Topic

Input Object

Web Services

Link

database
link

Container LinkParameters

POST /resources/json/delphix/database/link

Show
database
configuration "name" get
source
"name" get

Container -

GET /resources/json/delphix/database/{ref}
GET /resources/json/delphix/source/{ref}

Sync

database
"name" sync

Container SyncParameters

POST /resources/json/delphix/database/{ref}/sync

Update

database
"name"
update

Container Container

POST /resources/json/delphix/database/{ref}

Delete

database
"name"
delete

Container DeleteParameters

POST /resources/json/delphix/database/{ref}/delete

Detach

database
Container DetachSourceParameters
"name"
detachSource

POST
/resources/json/delphix/database/{ref}/detachSource

Attach

database
Container AttachSourceParameters
"name"
attachSource

POST
/resources/json/delphix/database/{ref}/attachSource

Disable

source
"name"
disable

Source

SourceDisableParameters POST /resources/json/delphix/source/{ref}/disable

Enable

source
"name"
enable

Source

SourceEnableParameters

POST /resources/json/delphix/source/{ref}/enable

Input Object

Web Services

Source

VDB Operations
GUI

CLI

API Topic

Provision

database
provision

Container ProvisionParameters

POST
/resources/json/delphix/database/provision

V2P

database
export

Container ExportParameters

POST /resources/json/delphix/database/export

Refresh

database
"name" refresh

Container RefreshParameters

POST
/resources/json/delphix/database/{ref}/refresh

Snapshot database
"name" sync

Container SyncParameters

POST
/resources/json/delphix/database/{ref}/sync

Update

database
"name" update

Container Container

POST /resources/json/delphix/database/{ref}

Delete

database
"name" delete

Container DeleteParameters

POST
/resources/json/delphix/database/{ref}/delete

1231

Delphix User Guide 2016 Delphix

Start

source "name"
start

Source

StartParameters

POST
/resources/json/delphix/source/{ref}/start

Stop

source "name"
stop

Source

StopParameters

POST
/resources/json/delphix/source/{ref}/stop

Enable

source "name"
enable

Source

SourceEnableParameters

POST
/resources/json/delphix/source/{ref}/enable

Disable

source "name"
disable

Source

SourceDisableParameters POST
/resources/json/delphix/source/{ref}/disable

Environment Operations
GUI

CLI

API Topic

Input Object

Web Services

Add
environment SourceEnvironment SourceEnvironmentCreateParameters POST /resources/json/delphix/environment
environment create
Update

environment SourceEnvironment Environment

"name"
update

POST /resources/json/delphix/environment/

Delete

environment SourceEnvironment "name"

delete

DELETE /resources/json/delphix/environmen

Refresh

environment SourceEnvironment "name"

refresh

POST /resources/json/delphix/environment/

Enable

environment SourceEnvironment "name"

enable

POST /resources/json/delphix/environment/

Disable

environment SourceEnvironment "name"

disable

POST /resources/json/delphix/environment/

Add manual
repository

repository
create

SourceRepository

SourceRepository

POST /resources/json/delphix/repository

Update
repository

repository
"name"
update

SourceRepository

SourceRepository

POST /resources/json/delphix/repository/{

Remove
manual
repository

repository
"name"
delete

SourceRepository

DELETE /resources/json/delphix/repository

Show host
details

host
"name" get

Host

GET /resources/json/delphix/host/{ref}

Add cluster
node

environment OracleClusterNode OracleClusterNode

oracle
clusternode
create

POST /resources/json/delphix/environment/

Update
cluster node

environment OracleClusterNode OracleClusterNode

oracle
clusternode
"name"
update

POST
/resources/json/delphix/environment/oracl

Remove
cluster node

environment OracleClusterNode oracle

clusternode
"name"
delete

DELETE
/resources/json/delphix/environment/oracl

1232

Delphix User Guide 2016 Delphix

Add listener

environment OracleListener
oracle
listener
create

OracleListener

POST /resources/json/delphix/environment/

Update
listener

environment OracleListener
oracle
listener
"name"
update

OracleListener

POST
/resources/json/delphix/environment/oracl

Remove
listener

environment OracleListener
oracle
listener
"name"
delete

DELETE
/resources/json/delphix/environment/oracl

1233

Delphix User Guide 2016 Delphix

API Cookbook: Common Tasks, Workflows, and Examples

These topics describe approaches to common tasks and workflows using the Delphix Engine API.
API Cookbook: Authentication
API Cookbook: Host Environment Details
API Cookbook: List Alerts and List Jobs
API Cookbook: List dSources and VDBs
API Cookbook: List Snapshots
API Cookbook: Refresh VDB
API Cookbook: Example Provision Of An Oracle VDB
API Cookbook: Stop/Start a VDB

1234

Delphix User Guide 2016 Delphix

API Cookbook: Authentication

This API cookbook recipe describes how to create an authenticated session for using the Delphix Sever web services.
Before you can use any Delphix Web Service APIs you need to create a session, and then authenticate the session by providing valid Delphix
account credentials.

Create Delphix API Session

$ curl -s -X POST -k --data @- http://delphix-server/resources/json/delphix/session \
-c ~/cookies.txt -H "Content-Type: application/json" <<EOF
{
"type": "APISession",
"version": {
"type": "APIVersion",
"major": 1,
"minor": 4,
"micro": 3
}
}
EOF

Delphix Login
$ curl -s -X POST -k --data @- http://delphix-server/resources/json/delphix/login \
-b ~/cookies.txt -H "Content-Type: application/json" <<EOF
{
"type": "LoginRequest",
"username": "delphix_username",
"password": "delphix_password"
}
EOF
NOTE: It is generally recommended to set the API session version to the highest level supported by your Delphix engine.

1235

Delphix User Guide 2016 Delphix

API Cookbook: Host Environment Details

This API cookbook recipe describes how to obtain host environment details using the Delphix Engine API.
To obtain details about target host environments, list available Environment objects on the system. These environments can represent either a
single host, or an Oracle cluster.

List Environment
curl -X GET -k http://delphix-server/resources/json/delphix/environment \
-b ~/cookies.txt -H "Content-Type: application/json"

For single-host environments, the reference can be used to get information about the associated host. It is also possible to get information about
all hosts (regardless of whether they are in a single-host environment or cluster) by omitting the environment query parameter.

List UNIX Environment

curl -X GET -k
http://services.cloud.skytap.com:23173/resources/json/delphix/host?environment=UNIX_HOST_
ENVIRONMENT-1 \
-b ~/cookies.txt -H "Content-Type: application/json"

For more information about the content of host objects, see the /api/#Host reference on your local Delphix Engine. Depending on the type of
the host, additional information may be available through the following types:
UnixHost
WindowsHost

1236

Delphix User Guide 2016 Delphix

API Cookbook: List Alerts and List Jobs

This API cookbook recipe describes how to obtain lists of jobs and alerts using the Delphix Engine API.
The List Alerts and List Jobs API calls can both accept the toDate and fromDate query parameters to limit rows returned. These
parameters require the date to be expressed in ISO 8601 format.

List Alerts
$ curl -X GET -k http:/delphix-server/resources/json/delphix/alert \
-b ~/cookies.txt -H "Content-Type: application/json"
For more information about the structure of an alert object, see the "/api/#Alert" link on your local Delphix Engine.

List Jobs (using fromDate)

$ curl -X GET -k
http://delphix-server/resources/json/delphix/job?addEvents=true&fromDate=2012-11-08T00:00
:00.0000Z \
-b ~/cookies.txt -H "Content-Type: application/json"
For more information about the structure of a job object, see the "/api/#Job" link on your local Delphix Engine.

1237

Delphix User Guide 2016 Delphix

API Cookbook: List dSources and VDBs

This API cookbook recipe describes how to obtain a list of dSources and VDBs using the Delphix Engine API.
To obtain a list of dSources and VDBs, list available Container (also known as database) objects on the system:

List Databases
$ curl -X GET -k http://delphix-server/resources/json/delphix/database
-b ~/cookies.txt -H "Content-Type: application/json"

For more information on the structure of a database object, see the /api/#Container reference on your local Delphix Engine. The following
sub-types are available depending on the type of database:
OracleDatabaseContainer
MSSqlDatabaseContainer
Each database has zero or one source associated with it. This source could be a linked source, indicating that the database is a dSource, or it
could be a virtual source, indicating that it is a VDB. If there are no sources, it is a detached dSource. The parentContainer property indicates
the reference to the parent container, also indicating that the database is a VDB. To get runtime information about the source associated with the
dSource or VDB, use the Source API with a database parameter set to the reference of the database in question.

List Sources
$ curl -X GET -k
http://delphix-server/resources/json/delphix/source?database=DB_CONTAINER-13
-b ~/cookies.txt -H "Content-Type: application/json"

If the virtual flag is true, the source is a VDB, otherwise it is a dSource. For more information about the contents of a source object, see the /a
pi/#Source reference on your local Delphix Engine. The following sub-types are available depending on the type of source:
OracleSource
OracleLinkedSource
OracleVirtualSource
MSSqlSource
MSSqlLinkedSource
MSSqlVirtualSource

1238

Delphix User Guide 2016 Delphix

API Cookbook: List Snapshots

This API cookbook recipe describes how to obtain a list of available snapshots for a VDB or dSource.
Snapshots represent points in time where a sync operation has occurred on either a dSource or VDB. Provisioning from snapshots is much faster
than provisioning between snapshots, as the latter requires replaying LogSync records to arrive at the requested point. Given a reference to a
database, the snapshot API can be used to retrieve the set of snapshots within the database. See the topic API Cookbook: List dSources and
VDBs for information on how to obtain the database reference.

List Snapshots
curl -X GET -k
http://services.cloud.skytap.com:23173/resources/json/delphix/snapshot?database=ORACLE_DB
_CONTAINER-15 \
-b ~/cookies.txt -H "Content-Type: application/json"
For more information about the structure of a snapshot object, see the /api/#TimeflowSnapshot reference on your local Delphix Engine.
Snapshots, while representing point where provisioning will be most efficient, are not the only provisionable points within a database. To get a list
of all provisioning points, use the timeflowRange API. This API is based on a timeflow, which is the representation of one timeline within a
database. Currently, all databases have a single timeflow, though this may change in the future. To query for the ranges for a particular database,
you will need to use the currentTimeflow member of the target database.

List Timeflow Ranges

curl -X POST -k
http://services.cloud.skytap.com:23173/resources/json/delphix/timeflow/ORACLE_TIMEFLOW-11
/timeflowRanges \
-b ~/cookies.txt -H "Content-Type: application/json"

1239

Delphix User Guide 2016 Delphix

API Cookbook: Refresh VDB

This API cookbook recipe describes how to refresh a VDB using the Delphix Engine API.
To refresh a VDB you need a reference to the Database object, the location of the point to which you wish to refresh and the reference container
associated with the object. See the topic API Cookbook: List dSources and VDBsfor information on how to obtain the database reference and
current timeflow. The timeflow point can be specified either by timestamp, by location (SCN), semantic location or timeflow bookmark. The Timefl
owPointSemantic type allows you to specify a semantically meaningful timeflow location (i.e. the latest snapshot or the latest timeflow point). The

See the
c for information on how to determine provisionable points in the parent database.
TimeflowPointBookmark type allows you to reference a previously created timeflow bookmark.

API Cookbook: List Snapshots

topi

Refresh VDB
curl -v -X POST -k --data @http://delphix-server/resources/json/delphix/database/ORACLE_DB_CONTAINER-13/refresh
-b ~/cookies.txt -H "Content-Type: application/json" <<EOF
{
"type": "OracleRefreshParameters",
"timeflowPointParameters": {
"type": "TimeflowPointSemantic",
"container": "ORACLE_DB_CONTAINER-1",
"timeflow": "ORACLE_TIMEFLOW-13",
"location": "LATEST_SNAPSHOT"
}
}
EOF

For more information about the content of refresh parameters, see the /api/#RefreshParameters reference on your local Delphix Engine.
Depending on the type of the database, the following parameter types are available:
OracleRefreshParameters
MSSqlRefreshParameters

1240

Delphix User Guide 2016 Delphix

API Cookbook: Example Provision Of An Oracle VDB

This API cookbook recipe demonstrates how to provision an Oracle VDB using the Delphix Engine API.
In order to provision an Oracle VDB using the API, you need to provide a set of parameters of type OracleProvisionParameters (having already
authenticated as per API Cookbook: Authentication).
There are a number of parameters you will need to know:

Group reference -

See the list operation in "/api/#group" on your Delphix Engine.

VDB name -

The name you want the new VDB to be called.

Mount path -

Where to mount datasets on the target host.

DB/unique names -

The Oracle DB and unique names, often the same as the VDB name.

Instance name/number -

The Oracle instance name and number to use (dictated by your environment, but often

VDB name and 1).

Repository reference -

See the list operation in "/api/#repository" on your Delphix Engine.

See API Cookbook: List Snapshots for information on finding a timeflow point, as well as
the reference at "/api/#TimeflowPointParameters".
Timeflow point -

You will need to use the structure of the OracleProvisionParameters object to fill it out, see "/api/#OracleProvisionParameters" for details on which
fields are mandatory/optional.

Here is a minimal example using curl to communicate with the API, provisioning a VDB called
"EGVDB" (authentication omitted)
curl -X POST -k --data @http://delphix1.company.com/resources/json/delphix/database/provision \
-b cookies.txt -H "Content-Type: application/json" <<EOF
{
"container": {
"group": "GROUP-2",
"name": "EGVDB",
"type": "OracleDatabaseContainer"
},
"source": {
"type": "OracleVirtualSource",
"mountBase": "/mnt/provision"
},
"sourceConfig": {
"type": "OracleSIConfig",
"databaseName": "EGVDB",
"uniqueName": "EGVDB",
"repository": "ORACLE_INSTALL-3",
"instance": {
"type": "OracleInstance",
"instanceName": "EGVDB",
"instanceNumber": 1
}
},
"timeflowPointParameters": {
"type": "TimeflowPointLocation",
"timeflow": "ORACLE_TIMEFLOW-123",
"location": "3043123"
},
"type": "OracleProvisionParameters"
}
EOF

1241

Delphix User Guide 2016 Delphix

1242

Delphix User Guide 2016 Delphix

API Cookbook: Stop/Start a VDB

This API cookbook recipe describes how to stop and start a VDB using the Delphix Engine API.
To stop or start a VDB, you need a reference to the Database object. See the topic, API Cookbook: List dSources and VDBs, for information
on how to obtain the database reference. The following script example includes working examples for creating a session, authenticating to the
Delphix Engine, and stopping or starting a VDB. Please update the script variables to match your environment before using. This script requires a
single argument which is 'start' or 'stop'.

1243

Delphix User Guide 2016 Delphix

#!/bin/bash
#
# sample script to start or stop a VDB.
#
# set this to the FQDN or IP address of the Delphix Engine
DE="192.168.2.131"
# set this to the Delphix admin user name
DELPHIX_ADMIN="delphix_admin"
# set this to the password for the Delphix admin user
DELPHIX_PASS="delphix"
# set this to the object reference for the VDB
VDB="ORACLE_VIRTUAL_SOURCE-5"
#
# create our session
curl -s -X POST -k --data @- http://${DE}/resources/json/delphix/session \
-c ~/cookies.txt -H "Content-Type: application/json" <<EOF
{
"type": "APISession",
"version": {
"type": "APIVersion",
"major": 1,
"minor": 4,
"micro": 1
}
}
EOF
echo
#
# authenticate to the DE
curl -s -X POST -k --data @- http://${DE}/resources/json/delphix/login \
-b ~/cookies.txt -H "Content-Type: application/json" <<EOF
{
"type": "LoginRequest",
"username": "${DELPHIX_ADMIN}",
"password": "${DELPHIX_PASS}"
}
EOF
echo
#
# start or stop the vdb based on the argument passed to the script
case $1 in
start)
curl -s -X POST -k http://${DE}/resources/json/delphix/source/${VDB}/start \
-b ~/cookies.txt -H "Content-Type: application/json"
;;
stop)
curl -s -X POST -k http://${DE}/resources/json/delphix/source/${VDB}/stop \
-b ~/cookies.txt -H "Content-Type: application/json"
;;
*)
echo "Unknown option: $1"
;;
esac
echo

1244

Delphix User Guide 2016 Delphix

CLI to Python Transition

This topic describes using the CLI to understand the Python APIs.
The command line interface is a direct translation of the web services API to an interactive environment. This allows you to use the CLI to
explore functionality with tab completion, integrated help, stronger type checking, and indication of expected types and required fields. When
trying to determine how to invoke an operation through the Python API or interpret the results, it is recommended that you first learn how to do the
same through the CLI, and then use the provided tools to translate that into Python calls.

Installation
The Delphix Python API is available through PyPI and you may install it with pip.

pip install delphixpy

Connecting to the Delphix Engine

In the Delphix Python API, all operations take an engine object which represents your connection to a Delphix Engine. Here is how you connect to
the Delphix Engine using the Python API and acquire the engine object.

from delphixpy.delphix_engine import DelphixEngine

engine = DelphixEngine("delphix-address", "delphix-user", "delphix-password", "DOMAIN")
# Instead of DOMAIN, use SYSTEM if you are using the sysadmin user

CLI Translation to Python

For backwards compatibility purposes, delphixpy provides the ability to write integrations against a specific API version. The latest version is
always in the root of the package. Writing against the latest version requires you to update your integrations if the API changes in future versions
of the API.
Specific API versions can be used by importing the corresponding sub package. The sub packages are named after the API versions in the format
v<major>_<minor>_<micro>. For example, if you want to lock into API 1.5.0, you should be using modules from delphixpy.v1_5_0.
Modules from different sub package versions cannot interact with each other so be careful if you wish to mix API versions in the same code base.
All CLI namespaces have a corresponding Python package in which operations can be accessed. The main Python package is called web. All
value objects which can be manipulated or read through the CLI can be found in web.vo.

delphix> database provision

Is equivalent to:

from delphixpy.web import database

database.provision(engine, provision_parameters)
The provision_parameters object in this example is an instance of ProvisionParameters which can be found in delphixpy.web.vo. The properties
of the object maps to the parameters you would need to specify before doing a commit in the CLI provision context.
This is an example of an "operation", as they are invoked on an object. Operations that are invoked on a particular object takes a reference to that
object.

delphix> database "dexample" refresh

Is equivalent to (connection code omitted):

from delphixpy.web import database

database.refresh(engine, "ORACLE_DB_CONTAINER-3")
While the CLI uses names to refer to objects, the Python API, just like the web services, use references. Persistent objects (those with a
permanent unique identity) have a reference field that is used in all cases to refer to the object. This allows references to remain constant even
if objects are renamed.
For the standard CRUD (create, read, update, delete) operations, the mapping is slightly different:
CLI Operation

Python API

group list

group.get_all(engine)

1245

Delphix User Guide 2016 Delphix

group create

group.create(engine, group=<delphixpy.web.vo.Group>)

group "dexample" get

group.get(engine, <reference>)

group "dexample" update

group.update(engine, <reference>, group=<delphixpy.web.vo.Group>)

group "dexample" delete

group.delete(engine, <reference>)

Example: Creating a Group

This is how you can create a group as a fully working example.

from delphixpy.web import group

from delphixpy.web.vo import Group
from delphixpy.delphix_engine import DelphixEngine
engine = DelphixEngine("delphix-address", "delphix-user", "delphix-password", "DOMAIN")
my_group = Group()
my_group.name = "My Group"
my_group.description = "This is my new group!"
group.create(engine, my_group)

Asynchronous Mode
The Python API runs by default in synchronous mode. If you would wish to perform operations asynchronously there is a context manager that
allows you to do that. If you need to track job progress in asynchronous mode, you can get the reference of the last job started
from engine.last_job. When exiting the async context manager, it will wait for all jobs started within the context to finish. If a job
fails, exceptions.JobError will be thrown.
Here is how you would perform a sync operation on all databases asynchronously.

from delphixpy.delphix_engine import DelphixEngine

from delphixpy import job_context
from delphixpy.web import database
engine = DelphixEngine("delphix-address", "delphix-user", "delphix-password", "DOMAIN")
all_databases = database.get_all(engine)
with job_context.async(engine):
for db in all_databases:
database.sync(engine, db.reference)

1246

Delphix User Guide 2016 Delphix

Python Cookbook: Adding a UNIX Host

This topic describes the process of adding a UNIX host using the delphixpy Python API.
Within Delphix, there are both hosts and host environments. A host represents a remote system, but may or may not be a source or target for
linking or provisioning. For example, in an Oracle RAC cluster, the cluster environment represents the location of the Oracle installation(s), and
while there are hosts within that cluster they are not individually manageable as environments.

Procedure
1. Create new environment creation parameters and initialize the structure for a UNIX host.

from delphixpy.web.vo import HostEnvironmentCreateParameters, UnixHostEnvironment,

UnixHostCreateParameters, UnixHost, EnvironmentUser, PasswordCredential
host_environment_create_parameters_vo = HostEnvironmentCreateParameters()
host_environment_create_parameters_vo.host_environment = UnixHostEnvironment()
host_environment_create_parameters_vo.host_parameters = UnixHostCreateParameters()
host_environment_create_parameters_vo.host_parameters.host = UnixHost()
host_environment_create_parameters_vo.primary_user = EnvironmentUser()
host_environment_create_parameters_vo.primary_user.credential = PasswordCredential()
2. Set the host address and port.
The name of the environment is derived from the address used, though you can provide a more descriptive name if desired. The address
can be a DNS names, IP addresses, or a comma separated list of the above.

host_environment_create_parameters_vo.host_parameters.host.addresses =
["192.168.1.2"]
host_environment_create_parameters_vo.host_parameters.host.port = 22
3. Set the toolkit path.
This is where Delphix will store temporary binaries used while the host is configured as part of Delphix.

host_environment_create_parameters_vo.host_parameters.host.toolkit_path =
"/var/delphix"
4. Set the username and password to use when connecting over SSH.
This user must have the privileges described in the Delphix Administration Guide. To configure a SSH user, change the credential object
to SystemKeyCredential.

host_environment_create_parameters_vo.primary_user.name = "oracle"
host_environment_create_parameters_vo.primary_user.credential.password = "my secret
password"
5. Commit the result. A reference to your new environment will be returned from the create call.
The environment discovery process will execute as an asynchronous job. The default behavior is to wait for the result, so progress will be
updated until the discovery process is complete or fails.

from delphixpy.delphix_server import DelphixServer

from delphixpy.web import environment
server = DelphixServer("delphix-address", "delphix-user", "delphix-password",
"DOMAIN")
new_environment_reference = environment.create(server,
host_environment_create_parameters_vo)
6. Full example

1247

Delphix User Guide 2016 Delphix

from delphixpy.delphix_server import DelphixServer

from delphixpy.web import environment
from delphixpy.web.vo import HostEnvironmentCreateParameters, UnixHostEnvironment,
UnixHostCreateParameters, UnixHost, EnvironmentUser, PasswordCredential
host_environment_create_parameters_vo = HostEnvironmentCreateParameters()
host_environment_create_parameters_vo.host_environment = UnixHostEnvironment()
host_environment_create_parameters_vo.host_parameters = UnixHostCreateParameters()
host_environment_create_parameters_vo.host_parameters.host = UnixHost()
host_environment_create_parameters_vo.primary_user = EnvironmentUser()
host_environment_create_parameters_vo.primary_user.credential = PasswordCredential()
host_environment_create_parameters_vo.host_parameters.host.addresses =
["192.168.1.2"]
host_environment_create_parameters_vo.host_parameters.host.port = 22
host_environment_create_parameters_vo.host_parameters.host.toolkit_path =
"/var/delphix"
host_environment_create_parameters_vo.primary_user.name = "oracle"
host_environment_create_parameters_vo.primary_user.credential.password = "my secret
password"
server = DelphixServer("delphix-address", "delphix-user", "delphix-password",
"DOMAIN")
new_environment_reference = environment.create(server,
host_environment_create_parameters_vo)

1248