Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- Velocity administrator's checklist for setting up Veritas Velocity
- Database administrator's checklist for setting up Veritas Velocity
- Sandbox user's checklist for setting up Veritas Velocity
- How to set up the Velocity Storage Server
- Deploying the Velocity Storage Server image on a virtual machine
- Velocity Appliance initial configuration requirements
- Configuring network and storage settings for the Velocity Storage Server in a virtual environment
- Registering the Velocity Storage Server
- Joining the Velocity Storage Server to the Active Directory domain
- Adding a Certificate Authority signed certificate to the Velocity Storage Server
- How to set up the Velocity Client
- Deleting a Velocity Client
- Configuring a proxy server for Velocity
- Required and optional ports for Velocity
- Installing the NetBackup Client on the Velocity Storage Server
- Setting up the Velocity on-premises management server
- How to set up the Velocity on-premises management server
- Deploying the Velocity on-premises management server image on a virtual machine
- Configuring the network settings for the Velocity on-premises management server
- Configuring Active Directory/LDAP settings on the Velocity on-premises management server
- Adding users to the Velocity on-premises management server
- Upgrading the Velocity on-premises management server
- Upgrading Velocity
- How to upgrade to Velocity version 2.9
- Finding the Velocity component version numbers
- Downloading and transferring software updates to the Velocity Storage Server
- Removing previous upgrade files
- Upgrading the Velocity Storage Server
- Upgrading the Velocity Client for Linux
- Upgrading the Velocity Client for Windows
- Upgrading the Velocity Client for Solaris
- Velocity Storage Server
- About the Velocity Storage Server
- Viewing physical storage usage on the Velocity Storage Server
- About reclaiming storage space on the Veritas Velocity Storage Server
- Increasing meta and data storage capacity on the Velocity Storage Server
- Deregistering a Velocity Storage Server
- How to reset the Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to provide copies of Oracle databases for sandboxes in Velocity
- Adding an Oracle database to ingest into Velocity
- Ingesting an Oracle database into Velocity for the first time
- Ingesting an Oracle database again after the first ingest
- Canceling an Oracle database ingestion
- How to use copy preparation to mask or sanitize sensitive data
- Masking sensitive data manually in database copies
- Masking sensitive data in database copies by using a script
- Masking sensitive data manually in database copies that are already ingested
- Masking sensitive data by using a script in database copies that are already ingested
- Disabling copy preparation for Oracle database copies
- Ingesting an Oracle database into Velocity from the command line
- About setting custom initialization parameters for a sandbox for an Oracle database copy
- Editing default options for the ingest method for Oracle databases
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Automatic ingestion of NetBackup deduplicated backups
- About using NetBackup deduplicated backups to create Velocity sandboxes
- How to set up automatic ingestion of NetBackup deduplicated backups
- Supported Oracle policy options for automatic ingestions of NetBackup deduplicated backups
- Supported SQL Server policy options for automatic ingestions of NetBackup deduplicated backups
- Adding an Oracle database source to automatically ingest NetBackup deduplicated backups
- Adding a SQL Server database source to automatically ingest NetBackup deduplicated backups
- Database sources and copies
- About database sources and copies
- Viewing details of an Oracle database source
- Viewing details of a SQL Server database source
- Changing the nickname or description of a database source
- Deleting a database source from Velocity
- About scheduling ingestions for a database source
- Viewing the ingestion schedule for a database source
- Adding an ingestion schedule to a database source
- Editing the ingestion schedule for a database source
- Deleting the ingestion schedule for a database source
- Restarting scheduled database ingestions after changing the system time or time zone on the Velocity Storage Server
- Retention periods for database sources and copies
- Viewing database copies
- Viewing the number of sandboxes that were created from a database copy
- Viewing the status of database copies
- Deleting database copies
- Sandboxes
- About sandboxes
- Creating a sandbox from an Oracle database copy
- Starting an Oracle database instance manually
- Creating a sandbox from a SQL Server database copy
- Starting a SQL database manually
- Finding your sandbox
- Viewing details about your sandboxes
- Deleting a sandbox
- Managing sandboxes when you restart the host Oracle Database server
- Unmounting a sandbox from an Oracle host server
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About IPv4-IPv6-based network support on the Velocity physical appliance
- About NIC1 (eth0) port usage on the Velocity physical appliance
- Creating a network interface bond (NIC bond) on the Velocity physical appliance
- VLAN tagging on the Velocity physical appliance
- Configuring static routes on the Velocity physical appliance
- Configuring DNS and host name mapping on the Velocity physical appliance
- Setting the host name for the Velocity physical appliance
- Using a proxy server with the Velocity physical appliance
- About WAN optimization on the Velocity physical appliance
- About the maximum transmission unit size on the Velocity physical appliance
- Setting the date and time on the Velocity physical appliance
- About the Veritas Remote Management Console on the Velocity physical appliance
- About Velocity physical appliance storage
- About users on the Velocity physical appliance
- About Velocity physical appliance checkpoints
- About factory reset on the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- Monitoring the Velocity physical appliance
- Velocity physical appliance security
- About Velocity physical appliance user account privileges
- About the Velocity physical appliance intrusion detection system
- About Velocity physical appliance operating system security
- About data security on the Velocity physical appliance
- About data integrity on the Velocity physical appliance
- About the Velocity physical appliance ports
- Recommended IPMI settings on the Velocity physical appliance
- Velocity REST APIs
- Getting started with Velocity REST APIs
- Authenticate a user for the Velocity REST APIs
- Get Velocity Storage Servers
- Create a share
- Find the share ID
- Find the share location
- Create a snapshot
- Find the snapshot ID
- Create a sandbox
- Find the sandbox ID
- Get a sandbox
- Delete a share
- Delete a snapshot
- Delete a sandbox
- Get templates (shares)
- Get snapshots
- List all sandboxes
- Best practices
- Troubleshooting
- NFS export paths where ingested Oracle Database sources are stored are inaccessible
- NFS export path is not created during a database ingestion
- Database ingestion fails with the Oracle error 'diskgroup {xx} space exhausted'
- After restart of the vpfsd service, links to the applications are broken
- Sandbox creation fails on an Oracle Database server
- Sandbox creation fails for a SQL Server database copy
- Sandbox creation fails after you use the --adGroups argument when you configure the Velocity Client for Windows
- Sandbox creation may take longer than usual on Oracle Database 12c
- A sandbox cannot be deleted from an Oracle Database server because the mount point is busy
- Error occurs when registering the Velocity Client; provide the Oracle DBA with access to the Velocity registration files
- Error occurs when a new sandbox name has the same name as a deleted sandbox
- Ingestions and sandboxes are stuck 'In Progress' after the Velocity Storage Server is restarted
- Glossary
- Section I. Velocity shell menu commands
- Introduction
- Appendix A. Main > Manage > Storage
- Appendix B. Main > Manage > Cloud
- Appendix C. Main > Manage > Software
- Appendix D. Main > Monitor
- Appendix E. Main > Network
- Network > Configure
- Network > Date
- Network > DNS
- Network > Gateway
- Network > Hostname
- Network > Hosts
- Network > IPv4
- Network > IPv6
- Network > NetStat
- Network > NTPServer
- Network > LinkAggregation
- Network > VLAN
- Network > WANOptimization
- Network > Ping
- Network > Proxy
- Network > SetProperty
- Network > Show
- Network > TimeZone
- Network > TraceRoute
- Network > Unconfigure
- Appendix F. Main > Settings
- Appendix G. Main > Support
Name
Main > Network > Configure — Use to configure the Velocity Appliance to a network.
SYNOPSIS
Configure IPAddress Netmask GatewayIPAddress [InterfaceNames] [BondingMode]
DESCRIPTION
During the initial configuration of the appliance, you can use the Configure command to configure the IP address of a single interface on the network that you want to connect your appliance to. After the initial configuration, you can use this command to change the IP address and connect your appliance to a different network. When you use this command, you need to define the IP address, the netmask address, and the gateway address. If multiple interfaces with separate IP addresses are used, use the Network > IPv4 or the Network > IPv6 commands to configure each network interface individually.
Use the Network > Gateway command to add the routing information for default route or to add route for VLAN interfaces.
OPTIONS
- Configure IPAddress Netmask GatewayIPAddress [InterfaceNames] [BondingMode]
You can use this command to configure the IP address and default gateway for the appliance. The command configures the IP address and sets the default gateway.
Where IPAddress is the IPv4 or IPv6 address, Netmask is the netmask, GatewayIPAddress is the default gateway IP address, and [InterfaceNames] is the name of the device.
This device can be a physical interface, or a bond, or a VLAN interface.
Remember that you should not use both IPv4 and IPv6 address in the same command. For example, you cannot use Configure 9ffe::9 255.255.255.0 1.1.1.1.. You should use Configure 9ffe::46 64 9ffe::49 eth1 to configure an interface using IPv6 address.
In the [InterfaceNames] field the following applies:
If you enter a single interface name, then the IP address is configured on that device.
If you enter a comma-separated list of interface names, then a bond is created and the IP address is configured on the bonded device. You must ensure that the interfaces that comprise the list are of same type, either or ). In addition, the interfaces must support the same speed and at least one of the interfaces in the list is cabled.
If you do not enter an interface name, the best possible interface or interfaces are selected based on the port type ( or ), speed, and the link status.
You define the bonding mode in the BondingMode field. You can enter one of the following modes:
balance-rr
active-backup
balance-xor
broadcast
802.3ad
balance-tlb
balance-alb (This bonding mode is the default value.)
EXAMPLES
The following examples show how to configure your appliance using the Auto selection, specifying a specific interface, or multiple interfacing and creating a bond.
Specify explicit interfaces such as eth2 and eth3 to create a bond. For this example, you provide the IPAddress, NetMask, Gateway IPAddress, interface names, and the bonding mode, in that order.
Configure 10.180.2.3 255.255.255.0 eth2,eth3 balance-alb
You can also create a bond and configure it using IPv6 addresses:
Configure 9ffe::207 64 9ffe::49 eth,eth3