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
Name
Main > Network > LinkAggregation — Use to manage link aggregation.
SYNOPSIS
LinkAggregation Create Slaves [BondingMode]
LinkAggregation Delete InterfaceNames
LinkAggregation Disable [InterfaceName]
LinkAggregation Enable [Slaves] [BondingMode]
LinkAggregation Show [InterfaceNames]
LinkAggregation Status
DESCRIPTION
You can use this command to manage link aggregation.
You can use this command to enable bonding (link aggregation), across the available network cards. If only one port is configured, bonding is not available. If multiple ports are configured on your appliance, they are identified automatically.
You have the ability to bond multiple ports or define specific ports to bond by what you enter in the [Slaves] option. To bond multiple ports, you must use a comma to separate the device names. In addition, you should ensure that all of the ports that participate in a bond are connected to the same switch. And make sure that is no additional port configuration is done at the switch.
There are eight different bond modes that you can choose from. Some of the bond modes require additional configuration on the switch or the router. You should take additional care when you select a bond mode.
For more information about the bond modes and any required switch configuration, see the following documentation:
http://www.kernel.org/doc/Documentation/networking/bonding.txt
You can also use this command to do the following:
To create a bond without associating an IP address to it.
To delete an existing bond.
To display the status of the link aggregation.
To show the link aggregation properties of one or more interfaces.
To turn off the link aggregation.
OPTIONS
- LinkAggregation Create Slaves [BondingMode]
Use this command to create a bond.
Here, the Slaves variable defines the device name that you want to bond and the [BondingMode] parameter is used to define the bond mode in which to configure bonding, or link aggregation. The eight available modes are, balance-rr | active-backup | balance-xor | broadcast | 802.3ad |balance-tlb | balance-alb. The default mode is balance-alb.
Conform to following guidelines to create a bond:
Ensure that the interfaces that participate in bond formation have the same port speed (i.e. either 1GB or 100GB).
At least one of the interfaces that participates in bond formation must be plugged.
Ensure that none of the interfaces that are selected for creating the bond have any VLANs tagged to them.
Verify that any of the selected interfaces are not, already, a part of another bond.
You can create this bond with or without assigning an IP address to it. The criteria for assigning or not assigning an IP address to the bond depends solely on the interfaces that are selected for creating the bond.
Consider the following two cases to understand IP address assignment to a bond:
IP address is assigned to a newly created bond, if any of the interfaces that are selected for creating a bond already have an IP address assigned to them.
IP address is not assigned to a newly created bond, if the interfaces that are selected for creating a bond do not have IP addresses assigned to them. A bond without an IP address associated to it is prerequisite for tagging a VLAN to a bonded interface.
If the selected interfaces are configured with IP addresses, an error message is displayed to indicate that a single interface must be configure with an IP address to create the bond.
Note:
You may use the Create and Enable commands to configure a bond over a private interface, for example, eth0.
- LinkAggregation Delete InterfaceNames
Use this command to delete a bond. Here, InterfaceNames defines the bond device name that you want to delete.
Note:
To delete a bond, ensure that the no IP address is configured on the bond. If an IP address is configured to the bond, you must first unconfigure the IP address. To unconconfigure the IP address, run the Network > Unconfigure command.
- LinkAggregation Disable [InterfaceName]
Turns off the link aggregation. The [InterfaceName] option is optional. You use this option to define the bond device name that you want to disable. You can use the LinkAggregation > Status command to obtain the device name.
LinkAggregation cannot be turned-off if there are multiple bonds present. To turn-off link aggregation on a specific bond, you must enter the bond name in the [InterfaceName] parameter.
- LinkAggregation Enable [Slaves] [BondingMode]
Use to turn on link aggregation. This command assigns IP address to the newly created bond.
The [Slaves] option defines the device names that you want to bond. Use a comma as a delimiter between the device names. This field is optional. The device names are identified automatically based on the current network settings and properties.
The [BondingMode] parameter is used to define the bond mode in which to configure bonding, or link aggregation. The eight available modes are, balance-rr | active-backup | balance-xor | broadcast | 802.3ad |balance-tlb | balance-alb. The default mode is balance-alb.
- LinkAggregation Status
Show the status of the link aggregation. If no interfaces have been configured, the following message appears:
No virtual interfaces have been configured.
- LinkAggregation Show [InterfaceNames]
Show the link aggregation properties of one or more interfaces.
Use the [InterfaceNames] option to define the interface or interfaces that you want to view the properties of. Use a comma to separate the interface names if you want to view the properties of more than one.