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
Ingesting a SQL Server database into Velocity
After you add a SQL Server database as a source to Velocity, you can ingest the database into Velocity. After the first ingestion is complete, you can add more copies of the ingested database to Velocity at any time.
To ingest the SQL Server database, Microsoft Volume Shadow Copy Services (VSS) performs a snapshot of a full copy-only backup. This ingestion method avoids any interruption of the backup sequence that you may use to back up your SQL Server databases.
If you want to customize the mssql_ingest.exe
application for your environment or for a specific ingestion, you can edit the default options in the ingest_options.json
file.
See Editing default options for SQL Server database ingestion.
Ensure that the items listed below are done before you ingest a database source:
The Velocity Client is configured on the SQL Server host.
The SQL Server database is added to Velocity.
To ingest a SQL Server database source into Velocity
- From the Velocity Cloud Console, in the left pane, click Database Sources.
- On the Database Sources dialog, on the row for the database source that you want to ingest, click Ingest.
Optionally, you can click Details, review or edit the database information, and then click Ingest on the Details dialog.
- After the database is successfully ingested, you can do any of the following:
Assign roles and permissions
Create a sandbox
View the database copies
Set a retention date to delete expired database copies