This Valentine’s Day, a lot of Google Cloud users love it.

What a whirlwind of a couple of weeks it’s been here at Veeam! With the launch of V12, so many exciting enhancements have been delivered to help organizations secure their backup strategy and improve recovery across hybrid cloud environments…………………….. A number of new features in Veeam Backup are a part of that. for Google Cloud delivered on Valentine’s Day in version 4! So let’s get right to the point and see what has changed.

PostgreSQL storage using native sky SQL

I hope that by this point, everyone is aware of the concept of shared obligation, that it is your content and that you have a duty to safeguard and protect it. African equipment for data protection is becoming more popular as businesses use PaaS to power their applications. essential….

The good The bad
  • By joining MySQL guidance availability via V3, V4 expands Veeam’s support to contain PostgreSQL in the protection of wholly managed databases. This is accomplished by storing both image-level backups and cloud-native snapshots on image storage. Experienced storage specialists are aware of the crucial distinctions between the two methods. Snapshots, also known as” backups” by some vendors, provide a fantastic first line of defense, but they are not the end-all solution when it comes to an effective backup plan.
  • provides low recovery point objectives( RPOs ) for more precise point-in-time recovery control.
  • provides low recovery time objectives( RTOs ), allowing for quicker business operations to resume after a deletion or outage.
  • never unrelated to the base example. The screenshot will also be compromised if the resource is, leaving us with nothing to fall back on.

We are forced to choose between budgets or loyalty because images require some of the most expensive storage for public cloud resources. An image-based backup, on the other hand, captures the entire image of the Cloud SQL instance( including its configuration, databases, and items such as users and stored procedures ) as multiple files to a separate storage store, or in Veeam’s way, in another in another project and / or area. If formation and the associated screenshot were already compromised by ransomware, deletion, corruption, and other threats, there would still be a workable way to recover with the data divided in this way.a genuine storage

…. Additionally, image hardware is significantly less expensive than snapshots, allowing us to keep more data for longer without incurring any additional costs. The following chart clearly shows how PostgreSQL data are protected by Veeam’s Cloud SQL.

Of course, Veeam’s cloud-native offerings stand out for all the same to you’ve come to love, including policy-based technology for simplicity, beautiful grain control over existing instances or database restores, and security measures like cross-project backup, least privilege IAM, encryption, etc.

Flexibility and enterprise administration

  • Any business running a asset hierarchy with numerous organizations, documents, projects, and resources on Google Cloud is aware of how difficult it is to manage backup and recovery. Because of this, we’ve added a ton of different features to V4 that aim to lower management behind for these types of environments while increasing scalability, including: Google Folders and cross-project program addresses
  • as a source of policy, enabling one devices to protect your existing environment. Domestic storage equipment optimization tasks
  • to lower the costs associated with making fewer API visits.enhancements to the script base’s flexibility

enabling more Google Cloud wealth to be safeguarded by a single device.

The illustration below demonstrates how a single appliance in its own task is safeguard all information dispersed across numerous many activities, folders, and businesses. 

New Tier of Google Cloud Storage You might have noticed if you had a keen eye. Google Cloud Storage Nearline

License portability

was a part of the PostgreSQL chart. Yes, along with Standard and Archive for Compute Engine VMs and Cloud SQL databases, this level is now supported by laws. For storing rarely accessed data, such as aging backups, guidance for nearline storage provides a low-cost, extremely waterproof storage service. In situations where significantly lower presence, a 30-day required safe-keeping duration, and costs for data access are valid trade-offs for lower at-rest storage costs, nearline storage is preferable to regular storage.

In closing

Veeam Backup for Google Cloud In contrast to entitlement via connection with a Veeam Backup & amp, Replication server, V4 also introduces direct acceptance of sveam Universal License ( VUL ). For organizations transitioning to a single cloud for 100 % of the time and no longer needing veeam backup and amp, replication servers, this widening of rights designs further improves permit portability.

  • is now superior to already, and I’m looking forward to what the future holds as we continue to advance the item. There are numerous additional benefits in V4 that:
  • Improve stability through conventional verification mechanisms to email servers, and validation of SMTP email server certificates in the main UI
  • To avoid needless choking from the common cloud, improve performance with weight management when sending data to back-up repositories.
  • Enhance coverage by splitting up backup and archive jobs into separate classes for more detailed presence for Google Cloud appliance

Expanded system provider abilities through remote administration and monitoring of the Veeam Backup hereIf you’d like to see all this in action and more, my good and good friend Andrey Zhelezko hosted a great a video a couple of days later that you can watch on interest . Or, for a more individualized encounter,!