Cluster/Storage Space dedupe issues which have been made better in the latest update.Office 365 exclusions still not resolved, backups up entire tenancy without you knowing.
I think we use every Veeam product there is. We have 1000's of backups jobs for our DC + run cloud backups to our own infrastructure. The guy on my team advocating for this pile of shit, a textbook corporate bullshitter, fucked up the licensing so bad it’s going to cost twice as much as estimated to properly implement, so we should be able to move off of it early next year. In my eyes, it’s only redeeming quality is that their convoluted licensing model basically saved me. Every ticket I’ve created takes at least 3-4 days just to get started troubleshooting. I ask for them to provide solutions via email and mark email as my preferred communication and they’re still trying to call me. I’m in Asia, I mark that in the ticket and they’re still calling me at 11:30 pm at night. I’ll say this in the nicest way possible, but it’s like their support staff doesn’t even read the tickets. And don’t even get me started on support. But I remember rolling out Veeam for the first time and I was off and running in a day with no prior Veeam experience. Now I know, some the problems are probably because I haven’t used BE before and there’s definitely a steeper learning curve here.
The software itself seems full of little gotchas where unbeknownst to you, having some checkbox buried in the job settings turned on (and it’s turned on by default) will completely fuck your jobs. Jobs produce errors regularly, the fact that compression and dedupe seem to be based and where the job is stored rather than the job itself is messy, and VMware based backups of Linux based VMs doesn’t seem work well, if at all. I rolled it out a month ago and it’s been nothing but an uphill battle. Let me just tell you that you were all absolutely correct about Backup Exec. To work around the issue, we can need to use T-SQL from Management Studio.Long time Veeam user, brand new BE user. If you run the "RESTORE HEADERONLY" command from T-SQL, you can see that it takes several minutes to complete which is much longer than the 20-second timeout for GUI. This timeout is to prevent these dialog boxes from hanging forever when there is no tape present in the drive. The timeout will happen on the "Specify Backup" dialog. Right click on a database > Tasks > Restore > Database > From Device > Click on button > Backup Media = TAPE > Add > Select Backup tape > OK > OK. In GUI this fails for large databases due to the fact that certain operations like the below sequence have a built-in timeout of 20 seconds. Step 5: Perform the actual restore operation. Step 4: Obtain the list of files present in the backup set/media. Step 3: Fetch the backup header (This can take time depending on the size of the backup and backup media/device). Step 2: Fetch details about the backup that we are trying to restore. These are the steps that take place in the background when the restore is performed in GUI, RESTORE HEADERONLY is terminating abnormally. The timeout period elapsed prior to completion of the operation or the server is not responding. When we use the SQL Server Management Studio GUI to perform a restore of a large database, we encounter the following message: This document is the method to restore SQL Server database from tape, which is a better data storage media for your database.
All this is not redundant in the process of managing database, SQL Server disaster recovery plan prepared in advance can help you recover things back when necessary.
Backup SQL Server after you install it on your computer is a critical task for DBA, and backup your database every day is perfect.