July 31, 2015 at 8:16 am
Hello All,
I am just wondering, has anyone used Commvault? If I restore SQL databases from tape using Commvault, will it just dump the MDF's and LDF's to a folder?
Should I be able to just take those MDF's and attach them in SQL?
FYI - this will be for SharePoint. So I would be attaching (if possible) the configuration database(s) and content database(s).
Would this work out? Anyone have any experience with how long the restore from Commvault takes? It is about 6 TB of data.
Thank you!
July 31, 2015 at 9:13 am
We use Commvault pretty extensively. If you take backups of the databases using the SQL IDA in Commvault, then restores will actually be restores of the databases to an instance of SQL Server (it doesn't have to be the same one where they were backed up).
In the version we're on, you actually don't get any visibility into/access to the backup files themselves, which can be annoying in some situations. Once you've backed up a SQL Server database through Commvault, getting the data back will just be a restore to a SQL Server instance.
I know in the newer versions there's a second option, restore to disk, where Commvault will generate a .bak file on the file system for you, which would be nice in some situations (but still isn't access to the original files).
I hope this helps!
July 31, 2015 at 9:38 am
For a hundred GB db backup, it takes more than 30 minutes to retrieve from CommVault, if no other jobs running at the same time.
July 31, 2015 at 9:39 am
Jacob Wilkins (7/31/2015)
We use Commvault pretty extensively. If you take backups of the databases using the SQL IDA in Commvault, then restores will actually be restores of the databases to an instance of SQL Server (it doesn't have to be the same one where they were backed up).In the version we're on, you actually don't get any visibility into/access to the backup files themselves, which can be annoying in some situations. Once you've backed up a SQL Server database through Commvault, getting the data back will just be a restore to a SQL Server instance.
I know in the newer versions there's a second option, restore to disk, where Commvault will generate a .bak file on the file system for you, which would be nice in some situations (but still isn't access to the original files).
I hope this helps!
Absolutely it helps, and thank you for your great reply.
One question - so it can restore directly to SQL? So it would essentially cut out any steps for manually attaching or manually restoring them yourself (say in SSMS) for example? I would assume doing a Commvault restore directly into SQL for 6 TB of data would saturate the I/O pretty badly, no? I'm thinking of bottlenecks, etc. But I suppose it could just go slowly?
July 31, 2015 at 9:51 am
Yes, it backs up directly from SQL Server, and restores directly to it (it just connects and issues BACKUP and RESTORE commands like you or I would).
Backing up/restoring that much data would be resource intensive, definitely. Depending on your setup, it might hit a network limitation before it hits a storage limitation.
Cheers!
August 5, 2015 at 1:04 pm
We use COMMVAULT to backup our SQL Servers as well. Yes, it uses a SQL Server Domain ID to run the SQL DB Backups and stores them within COMMVAULT. If you want it restored you tell it which SQL Server to restore it to...same one or a different one and it actually restores the db into SQL Server.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply