Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- How to set up the Velocity Storage Server
- How to set up the Velocity Client
- Setting up the Velocity on-premises management server
- Upgrading Velocity
- Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to use copy preparation to mask or sanitize sensitive data
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Database sources and copies
- About scheduling ingestions for a database source
- Retention periods for database sources and copies
- Sandboxes
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About WAN optimization 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
- Recommended IPMI settings on the Velocity physical appliance
- Best practices
- Troubleshooting
- Glossary
- Context-sensitive topics
- 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
- Appendix F. Main > Settings
- Appendix G. Main > Support
Role-based access control
Velocity users must be assigned to roles before they can perform any tasks. Roles provide access to database sources and give users the privileges that they need to perform tasks. For example, users must have access to a database before they can use it to create a sandbox.
Note:
For the hybrid cloud solution, users must receive account credentials from the Veritas Application Portal before they can sign in to Velocity. Refer to the following help topic for more information about adding users to the Veritas Application Portal:
See Adding users.
To add users to the Velocity on-premises management server, refer to the following help topic:
See Adding users to the Velocity on-premises management server.
When a user has a user account in the Veritas Application Portal but has not yet been assigned a role, the user is considered unprivileged. An unprivileged user can sign in to Velocity, but cannot create or view anything in the system.
User accounts can only be deleted from Veritas Application Portal. When a user is deleted, the user is removed from the Veritas Application Portal, but not removed from the Velocity Cloud Console.
The following table describes each of the roles that is available in Velocity.
Table: Velocity roles
Role | How the role is assigned | Description |
---|---|---|
Velocity administrator | When an organization is created in the Veritas Application Portal, the initial user is created as a Velocity administrator. Only Velocity administrators can assign additional users to the Velocity administrator role. | Each organization has at least one Velocity administrator who oversees all users and data in the system. This includes creating, listing, editing, and deleting users, and managing Velocity Storage Servers. The Velocity administrator can access all dialogs in the Velocity Cloud Console and can view all sandboxes, database sources, and database copies. Velocity requires at least one Velocity administrator. You cannot remove all of your organization's users from this role. Note: Only Velocity administrators can set up the Velocity Storage Server or instances of the Velocity Client. |
Database administrator | The Velocity administrator assigns users to this role. | A database administrator manages databases and configures who can access them. The database administrator creates database sources in Velocity by adding databases. When a database is added, the database administrator becomes the owner of the database. The database can now be ingested. Note: Only one database administrator can own a database. Group ownership of a database is not available. After the database is ingested, the database administrator can use a role to grant users access to the database source. Users with the appropriate permissions can create sandboxes from the database source. The database administrator can use multiple roles to define the groups of sandbox users that are authorized to access specific databases. Database administrators can:
|
Sandbox user | The Velocity administrator or the database administrator assigns users to this role. | A sandbox user has access to specific databases and database copies. Sandbox users can create sandboxes based on the databases that are available to them. Sandbox users can:
|
See How to configure users and roles in Velocity.
See Adding users.