This reply was modified 4 years, 7 months ago by Beatrix Kiddo.They are still in the boxes so probably the usable space of the SSD drives is only 448 GB after the. In an emergency do you really want to have to recover a whole VM/instance just because one database died? The new servers are Då 60 G10 with 512 GB RAM and only 1 pair of 480 GB SSD drives for RAID 1. In most cases they work very well, and most importantly, they allow a DBA to have full control over their own restores. I'd say most SQL DBAs prefer to use native backups for all but the largest multi-terabyte databases. Your VM/SAN admin is ill-informed and possibly shit-stirring. where I am (City of London), all SQL Server VMs have crash-consistent snapshots and no SAN-level snapshots compared to non-SQL VMs. The most obvious example is if you are using Ola Hallengren's backup solution - and you should be :)- there is logic to check when the last full database backup was taken, and that date/time is used to determine which old backups files can be automatically deleted. To echo what's said above, you need to be so careful with VSS snapshots where SQL databases are involved because a record that *looks* like a full database backup is written to the msdb backupset tables every time (because the SQL VSS Writer is invoked), so if you have any SQL Agent jobs running that rely on accurate backup history in msdb, it can throw things seriously out of whack. It includes a relational engine that processes commands and queries and a storage engine that manages database files, tables, pages, indexes, data buffers, and transactions. ![]() That's not what my research says, but, again.accidental DBA. The core component of Microsoft SQL Server is the SQL Server Database Engine, which controls data storage, processing, and security. My question is this: who's right? I'm being told that hardly anyone in the know is using SQL Server native backups. I've researched and it seems most people trust native backups over SAN or VM. But of course, the SAN is great and backups will be fine. He did admit that they only test backups quarterly. They run Windows 2008R2 å4 with 4KB NTFS on a virtual test machine theyve sent us. It is recommended that you have a minimum of two physical NICs dedicated for iSCSI storage access. A potential customer wants to evaluate our storage system. I asked about testing backups, which I do every couple weeks by restoring to our test system and making sure our main business application works. NIMBLE BEST PRACTICE S GUIDE: VMWARE VSPHERE 5 ON NIMBLE STORAGE 4 2 DESIGN CONSIDERATIONS AND BEST PRACTICES Base Connectivity for High Availability Host Make sure that the VMware vSphere ESX host has a minimum of two physical NICs. He claims the new Nimble SAN can take VSS snapshots every 1/2 hour and be much easier to recover, even to point-in-time. The VM/SAN guy is pushing me **hard** to "get out of 1985" and stop using SQL Server backups. We have a third-party to administer and maintain servers. We're switching servers and SAN and upgrading SQL Server to 2017 from 2008R2. Not big databases, full backups take 1/2 hour for all. But I am running transaction log backups on our full recovery databases every 1/2 hour and full backups after hours. ![]() I'm an accidental DBA at a very small company, and I'm sure I'm doing all sorts of things wrong.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |