Please enter search query.
Search <book_title>...
Veritas Velocity™ User's Guide
Last Published:
2017-11-28
Product(s):
Velocity (2.8)
- 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
Sandbox creation fails for a SQL Server database copy
If the sandbox creation fails for a SQL Server database copy, the share may still have been successfully created. You can try to manually attach the sandbox database to the SQL instance.
If the manual attach process is successful, the status of the sandbox remains as 'Creation failed'. However, the sandbox database is attached to the SQL instance and is available to the user.
To manually attach the database to the SQL instance
- On the Velocity Cloud Console, in the left pane, click Sandboxes and then on the sandbox that failed, click Details.
- On the Details page, look for the UNC path, for example: \\velocity.appliance.company.com\1a2b3c4d-5e6f-7a8b-9c0d-1e2f-3e4f5a6b7c8d.
- On the SQL Server, browse to that location.
- Navigate to the folder where the database files are located, for example: 2a3b4c5d-6e7f-8a9b-0c1d-2e3f-4a5b6c7d8e9f\3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d.
- Find the database file names, and then use SQL to attach to those database files.
Refer to your SQL Server documentation for instructions on how to use the Attach process.