Query on backing up data to cloud from netbackup
Hi All,
We are working on deployment of netbackup in Azure cloud environment to protect databases on servers in azure cloud.we wanted master and media roles in same virtual machine as number of clients we are protecting are very less
Our design requirements are to have auto image replication b/w sites and deduplicated backups to be stored in cloud to save storage space
So to upload deduplicated data to cloud we should use cloud catalyst(phsyical appliance or virtual or RHEL 7.3 acting as media server) but cloud catalyst donot support AIR.
In this case to acheive our requirements like enable deduplication to save storage space and have auto image replication -Please suggest as i am stuck with below issues
1)cloud catalyst donot support auto image replication
2)without cloud catalyst if we use a normal msdp mediaserver ,data will be backed up without deduplication on to cloud.
Please suggest how can both requirements of ours like deduplication to cloud and AIR can be achieved.
If there is any documentation,please help us
If Azure Managed Disks are too expensive for you, and remember that you do actually need quite performant disks anyway in order to run MSDP, then your only option is to forgoe MSDP and instead use an Azure based blob storage account as the target for a NetBackup Cloud Azure based storage unit (i.e. storage server + disk pool + disk volume).
I think maybe we can all sometimes get a little bit lost at the front end of decision making on the technical side of things. Whereas in reality, cost is nearly always the prime factor. Of course features and compatibility have a tole too, but usually at the end of teh day it comes down to cost. IMO, it might be a good idea to do some detailed calculations and cost models of both options. Don't forget the possible / likely (depending upon Azure storage type) additional charge for every 10,000 disk IO operations - and remember that MSDP is constantly doing : compaction, rebasing, and CRC checks - i.e. MSDP is doing background IO all the idle time, and I do mean *ALL* of the idle time - MSDP uses its quiet times for background IO.
