Backup server capacity planning worksheet (sql server pdw)
This capacity planning worksheet helps you to determine the requirements for a backup server for performing SQL Server PDW database backup and restore operations. Database examples Use this to create your plan for purchasing new or provisioning existing backup servers.
This worksheet is a supplement to the instructions in Acquire and Configure a Backup Server.
Database knowledge Capacity Planning Worksheet for Backup Servers Notes
The only way to backup and restore PDW databases is to use the BACKUP DATABASE and RESTORE DATABASE SQL commands. H2 database However, once the backup data is on your backup server, it exists as a set of Windows files. Nexus 5 data recovery You can archive the backup files from your server to another storage location by using traditional Windows file-based backup methods.
For example: As a rough estimate, we recommend estimating a 7:1 compression ratio relative to the size of your uncompressed data. Data recovery uk This assumes at least 80% of the data is stored in clustered columnstore indexes. Database collation For example, if you have 700 GB of uncompressed data in a database and it is stored in clustered columnstore indexes, then you could estimate the database backup will need about 100 GB.
For example: If you plan to backup 10 databases that each contain 5 TB of uncompressed data, the databases have a combined size of 50 TB. Database yugioh If you plan to backup these 10 databases everyday for 5 days in a row, the total uncompressed size is 250 TB. Top 10 data recovery software free Factoring in a 7:1 compression ratio, you will need 250 / 7 = 35.7 TB of storage on your backup server. Data recovery vancouver bc We recommend being conservative and getting about 30% additional capacity to account for variances and grow. 7 data recovery suite crack In this example, 46.6 TB would be better.
For example: InfiniBand or 10Gbit Ethernet will provide the optimal loading rates. Database normalization definition 1Gbit Ethernet will limit load rates to 360 GB per hour or less.
For I/O capacity, take into account all of the I/O happening on the loading server. Data recovery wizard If the Loading server has other I/O traffic in addition to data loads, such as receiving data files from an ETL server, the I/O requirements will increase.
Receiving and storing backup files is not a CPU-intensive application. Data recovery video As a minimum requirement, we recommend using a recently-manufactured 2-socket server.
To determine the RAM requirements, refer to your Windows Server installation and any 3rd party application requirements. Database query example We recommend a minimum of 32 GB if you do not have requirements from other sources.
When you are finished determining your capacity requirements, return to the Acquire and Configure a Loading Server topic to plan your purchase. Database migration See Also