I recently wrote a blog about the AWS PrivateLink and NetBackup deployment guide that I released and wanted to give you a closer look on how to use the NetBackup Media Server Deduplication Storage Pool Cloud Tiering (MSDP-C) to use as a backup repository with your AWS PrivateLink.
What I want to focus on in this blog is AWS PrivateLink and NetBackup MSDP-C.
How does MSDP work? The backup client sends the backup image to a media server, which hosts the plug-in that deduplicates the backup data. The deduplication plug-in breaks the backup image into segments and compares the segments to all of the segments that are stored in that deduplication node. The plug-in then sends only the unique segments to the NetBackup Deduplication Engine on the storage server. The Deduplication Engine writes the data to a Media Server Deduplication Pool.
Once you’ve set up your PrivateLink in AWS, it’s now time to connect to the S3 storage with MSDP-C.
To connect to the newly created AWS PrivateLink, log into the NetBackup Primary server and navigate to Storage > Storage Configuration. An MSDP Storage Server will need to be added or an existing one can be used. This document assumes one has already been created.
With Veritas NetBackup MSDP-C and AWS PrivateLink, users can now safely transfer de-duplicated data to and from the AWS cloud without the risk of exposing sensitive data to visibility, tampering or theft. Users you can now access S3 directly as a private endpoint using a secure, virtual network which leverages a new interface endpoint within your Virtual Private Cloud (VPC).