- #BACKUP EXEC 16 SQL BACKUP FULL#
- #BACKUP EXEC 16 SQL BACKUP LICENSE#
- #BACKUP EXEC 16 SQL BACKUP FREE#
Other than that, though, Imceda does look to be here for the long haul, their product is very good, and it's saved us a lot of time and HD space. Since installing the new server setup each day when I unplug the drive and plug in the new drive I get an.
#BACKUP EXEC 16 SQL BACKUP FULL#
Each day I exchange one of the hard drives out to run a full backup. This was quickly resolved when I asked to speak with a supervisor and it turned out the whole mess was just a communications issue. I am running a Dell T430 with Windows 2016 Server, Backup Exec 16, and have 5 Seagate External USB 3 4 TB hard drives. The only situation I ran into was with one particular Tech who wasn't actually listening to what I was telling her when I called with a problem. I don't want anyone to think I'm dissing them or their product. They also track all known issues with Litespeed on their website via Knowledge Base kind of database. They are fairly nice and their tech support is pretty decent. To be completely fair, my company actually hasn't had any serious problems with Imceda. Just an FYI to add to my earlier comment. RE: Backup Exec SQL Agent Debate pgaliardo (MIS) MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005) You will start running into problems when you don't have enough drives to backup to and your backups have to wait for a tape drive.
#BACKUP EXEC 16 SQL BACKUP FREE#
This was because we had a large number of tape drives and during the day there was usually a tape drive free to use for restores.Īs long as a tape backup solution is scalled correctly you shouldn't have any problems backing up directly to tape. The amount of time to restore from tape will depend on the number of tape drives you have, and how long it takes for the robot to get the tape into that drive.Īt a previous place restoring from tape took the same amount of time as restoring from disk. This defeats the purpose of backing up at all as you've got a large window when the backup can be lost (the time between the SQL backup and the tape backup). They then backup to tape when time permits. Most places when they backup to disk, backup to the same disk that the database sits on. Personally I prefeer going directly to tape and bypassing the disk. RE: Backup Exec SQL Agent Debate mrdenny (Programmer) 21 Jul 06 14:05Ĭurrently we do it both ways, to disk and to tape. What are the pros and cons to what I am doing and how does everyone else manage their SQL backups?
#BACKUP EXEC 16 SQL BACKUP LICENSE#
We are currently debating on whether or not to even renew our Veritas SQL Agent License when it is up for renewal. My thinking is that this is actually a better solution, because I think a restore would be faster from the disk using SQL Backup and Restore. If I need to go back further, I have the. I have enough space to do SQL backups and I keep them for a week before overwriting. What I am doing is running native SQL Backups to disk, then backing up the. Long story short, we can't get the BE 10 SQL Agent to see our databases. We recently upgraded to BE 10.0d and SQL 2005 64 bit. We always used Backup Exec with the SQL Agent to backup our SQL 2000 databases. I've seen posts on this subject before, but I'm trying to gather as many facts and experiences as possible.
0 kommentar(er)
