We are excited to announce the release of Kasten K10 version 6.0, the latest and most advanced version of our industry-leading platform that provides enterprise-grade Kubernetes data protection and application mobility. This release helps customers scale their cloud native data protection efficiently. Kubernetes deployments are growing at an unprecedented rate. Gartner predicts that by 2027, more than 90% of global organizations will be running containerized applications in production. However, today’s market conditions are scarred with financial uncertainty and a shortage of cloud native skills. Therefore, you must ensure operational efficiencies are in place to unleash the full potential of your cloud native environments while protecting your data. Additionally, security remains an imperative as organizations focus on keeping their businesses running. With this release, we also continue to innovate in this growing ecosystem, so that you can take advantage of the best-of-breed inn...
Get link
Facebook
X
Pinterest
Email
Other Apps
How do I protect my data contained within Amazon RDS instances?
Get link
Facebook
X
Pinterest
Email
Other Apps
With the explosive growth of AWS, more and more people are turning to Amazon RDS (Amazon Relational Database Service) for database services. With Amazon RDS instances, you can deploy databases without having any of the overhead of managing the actual database service or underlying operating system. This is what AWS says about Amazon RDS:
Amazon Relational Database Service (Amazon RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the AWS Cloud. It provides cost-efficient, resizable capacity for an industry-standard relational database and manages common database administration tasks.
Now, because of this growth in Amazon RDS, a new challenge faces consumers of this service. How do I protect my data contained within these database instances? AWS provides capabilities to snapshot the databases, but managing these can be complicated when you consider data retention periods and copying and replicating to other regions or AWS accounts.
Veeam Backup for AWS provides the capabilities to protect and replicate Amazon RDS instances, not only by taking snapshots, but also by replicating instances to other AWS accounts and regions. This provides secure data protection for those RDS instances and allows consumers to implement an AWS best practice of storing backup data in separate AWS accounts.
Backing up your RDS instance
It is extremely easy to get started. Under Policies, pick the resource type you want to protect, which in this instance is RDS, and click Add a policy. You will be presented with the policy creation wizard which has some requirements for configuration:
Sources (where and what to protect)
Targets (where and how to replicate)
Schedule (how often and retention periods)
Cost estimation (confirm your happy with the cost of this backup)
Once set up, your RDS instance(s) will be protected and replicated, and all snapshots will be managed under the configured retention periods, providing the capabilities to meet data certification requirements.
Restoring your RDS instance
Restoring a database is just as easy. By selecting protected data, you can choose to restore the database in-place by overwriting the existing database, or to a different location including another AWS account.
For those of us who have been in the business of backing up data for a while, we’re used to making copies of data on different types of media. I won’t date myself by mentioning reel-to-reel tapes, but the journey started with tape and then backing up data to block/file-based disk storage came along. More recently, a new kid on the block has become a popular destination for backed up data, object storage. Veeam started to use object storage as a target when we released Veeam Backup & Replication 9.5 Update 4 in January 2019 by introducing our use of AWS S3 compliant object storage via the Capacity Tier. A year later, we launched Veeam Backup & Replication v10 which featured support for object locking to provide data immutability for object storage. Immutability provides protection from ransomware attacks by locking the objects which prevents them from being modified or deleted by malicious software or humans. Today, Veeam Backup & Replication is protecting hundreds of petab...
Before Veeam Backup & Replication v11, the product used SQL Server to create and store its configuration database. It has always been possible to use SQL Server Express to store a Veeam Backup & Replication, however, this version of SQL Server had some critical limitations. In the 2022 version of SQL Server Express, the most relevant limitations were: Use of one socket or four cores Use of only 1.4GB per instance 10GB limit for databases In an environment of 500 machines or fewer, these limitations may not have an impact, but if you have a large backup environment, you had to migrate to one of the paid SQL Server versions to avoid these limitations. You can check the limits for each version of SQL Server 2022 by clicking this link . For V12 and with scalability, performance and licensing cost in mind, Veeam introduced the possibility of using PostgreSQL as a configuration database. PostgreSQL is a relational database management system that’s been used for over 35 years...
update notice: The information in this blog post has been updated on April 1st, 2022. Since Veeam Backup & Replication version 10, it’s possible to back up NAS shares with the SMB (CIFS) and NFS protocol. One of the challenges with backing up large file shares is doing so in a consistent state. This blog post shows how to create a consistent backup of an SMB share hosted on a NetApp ONTAP based storage. NetApp storage snapshot, Microsoft VSS snapshot or Storage Integration? Veeam offers three ways to back up a NetApp ONTAP SMB share in a consistent state. With NetApp storage integration From a NetApp storage snapshot (without integration) With Microsoft remote VSS snapshot Using the storage integration is the easiest way to get the latest state with very few configuration steps. Using an alternative snapshot path allows complex scenarios like backing up from a SnapMirror/SnapVault location but it involves scripting or a schedule on NetApp to create and delete t...
Comments
Post a Comment