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 Velocity
- How to upgrade to Velocity version 2.8
- Finding the Velocity Storage Server and Velocity Client 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
- 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
- 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
- Context-sensitive topics
- Create Sandbox - Choose Database
- Create Sandbox - Configure Host
- Create Sandbox - Review Settings
- Create Sandbox - Choose Database
- Create Sandbox - Configure Host
- Create Sandbox - Review Settings
- Sandboxes window
- Sandbox details
- Sandbox details for an Oracle database copy
- Sandbox details for a SQL Server database copy
- Role Wizard - Select User Type
- Role Wizard - Select Users
- Role Wizard - Select Sources
- Role Wizard - Review
- Copies dialog
- Database source details
- Database Sources dialog
- How to set up the Velocity Client
- Schedule dialog
- 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
Creating a network interface bond (NIC bond) on the Velocity physical appliance
You can bond multiple physical network ports across the available network cards (NICs) on the appliance. Bonding physical network ports (also known as link aggregation) allows for increased throughput and greater redundancy should one of ports fail on the appliance.
Note:
If only one port is configured, bonding is not available. If multiple ports are configured on the appliance, they are identified automatically.
Use the following guidelines when creating a network interface bond:
At least one of the ports that you want to bond must be plugged.
Only ports of the same type and speed can be bonded together (such as 1GB or 10GB, and fibre or copper).
None of the selected ports should have VLANs tagged to them.
None of the selected ports can be part of another bond.
All of the ports that participate in a bond should be connected to the same switch. In addition, no additional port configuration is done at the switch.
You should only configure network interface bonds using the Velocity shell menu.
Network interface bonds that are configured with unsupported tools can appear as Disabled when you use other networking features, such as WAN optimization.
To create a network interface bond
- Log on to the Velocity shell menu.
- From the Main_Menu > Network view, type the following command:
LinkAggregation Create <Slaves> [[BondingMode]]
Where <Slaves> is a comma-separated list of two or more port names, and [[BondingMode]] is the desired mode for the bond. For example:
LinkAggregation Create eth1,eth2,eth3 balance-tlb
The available bond modes are:
balance-alb (default)
balance-rr
active-backup
balance-xor
broadcast
802.3ad
balance-tlb
Some bond modes require additional configuration on the switch or the router. For more information about bond modes, refer to the following documentation:
http://www.kernel.org/doc/Documentation/networking/bonding.txt
You do not have to assign an IP address to the bond. However, if one of the ports already has an IP address that is assigned to it, the bond inherits that IP address.
Note:
If more than one port has an IP address that is assigned to it when you try to create the bond, the operation fails.