About SQL Server sizing and SQL license at the time of file to Tape

[ogasawara]

I'm thinking of backing up a 500TB File to Tape with Veeam.
In this case, we plan to build Standard SQL Server
If so, what should I choose for Standard SQL Server resources and Standard SQL Server licenses?
Can you tell me who knows

[HannesK]

Hello,
chances are high that your plan fails with our current architecture. How many files do you have? The engine is built to process backup files to tape, a few million files. It's not built to back up hundreds of millions or billions of files.

10 GB disk space for 1 million files is a calculation that usually works.

If your filer can do NDMP, then this is probably the better solution.

Best regards,
Hannes

[ogasawara]

Thank you.
Isilon file server is the target.
The number of files is expected to be hundreds of millions.
I am thinking of copying this data to Tape.
After all, is Veeam tough?

[HannesK]

Then I see NDMP as the only option for today. Backup to disk is fine. No problem with that.

We have plans to improve file-to-tape, but this will still take some time.

[ogasawara]

Thank you.

When operating to store only full backup data on tape as a measure against ransomware
After the secondary copy to tape is completed, delete the primary backup data acquired on the HDD, is this kind of operation possible?

[HannesK]

hmm, I'm not sure about the question.

NDMP is NAS filer to tape. No disk involved

NAS backup to disk is an "incremental forever" approach. Deleting old data makes no sense as there must always be one full backup. Incremental backups usually only consume very little space because NAS filers usually have a very low change rate

As of today, there is no Disk-to-disk-to-tape for NAS backups in Veeam. That's also an open feature request we are working on.