The IT industry is constantly evolving, and the recent VMworld 2021 event showcased some of the most exciting new developments in the field. One of the biggest announcements was VMware’s Cross-Cloud Services, a suite of integrated services that allow customers to build, run, and secure applications regardless of which cloud they are running on.

At the heart of Cross-Cloud Services are five key building blocks:

1. Managed Cloud: This service provides a simple and consistent way to manage multi-cloud environments, including AWS, Azure, and Google Cloud.

2. Hybrid Cloud: This service allows customers to extend their on-premises vSphere environments into the cloud, providing a seamless hybrid cloud experience.

3. Security: VMware is offering a range of security services, including intrusion detection and prevention, advanced threat protection, and identity and access management.

4. Cost Control: This service provides tools for monitoring and optimizing cloud costs, ensuring that customers are getting the most value from their cloud investments.

5. Application Management: VMware is offering a range of services to help customers manage their applications across multiple clouds, including app performance monitoring, log analysis, and automated remediation.

In addition to these core building blocks, VMware also announced several other exciting developments at VMworld 2021. For example, the company showcased Project Arctic, a platform for managing vSphere in the cloud. This integration allows vSphere to become “cloud-aware,” enabling hybrid cloud as the new operating model for customers.

VMware also released a free version of Tanzu, called VMware Tanzu Community Edition, which lets customers test and learn about running applications in containers. This edition can be easily installed on a laptop in just a few minutes, allowing customers to quickly get started with their Kubernetes cluster.

Another exciting announcement was Tanzu Service Mesh, which brings together the previously separate services of service discovery, security, and observability across multiple cloud environments. This allows customers to easily connect and manage their applications across different clouds.

VMware also expanded its support for NVIDIA GPUs in Amazon Web Services and Azure, providing more powerful computing resources for AI and ML workloads. Additionally, the company released vSphere 7.0 update 3 and VMware Cloud Director 10.3, both of which offer new features and enhancements for customers.

Overall, VMworld 2021 showcased some of the most innovative developments in the IT industry, with a focus on hybrid cloud, security, and application management. With these new services and tools, customers can build, run, and secure their applications in a more efficient and effective way, regardless of which cloud they choose to use.

Here’s a 500-word blog post based on the information provided:

Virtual Thoughts Random Comments on the IT Industry: Object Lock for Ransomware Protection with Veeam Backup & Replication v10 and Cloudian HyperStore 7.2.1

One of the most exciting features in Veeam Backup & Replication version 10 is the “replacement for tapes” feature called Immutability. This feature provides ransomware protection by write-protecting data stored on an object storage solution for a specified period, making it accessible but unable to be changed or deleted. In this blog post, I’ll share how to set up Cloudian HyperStore 7.2.1, create an immutable bucket, and use it with Veeam Backup & Replication v10 for testing purposes.

Why Immutability is a Big Deal

AWS S3 introduced the Object Lock feature, which prevents data from being tampered with or deleted. Veeam Backup & Replication version 10 leverages this feature to provide immutability, ensuring your data remains safe even in the face of ransomware attacks. Unlike traditional tape backup solutions, immutability keeps your data online and accessible while protecting it from malicious activities.

Object Lock Compatible Object Storage Solutions

The list of object storage solutions compatible with Veeam Backup & Replication v10 is growing. You can find the list on this unofficial list, which includes both object storage solutions with and without Object Lock functionality. Some of the supported solutions include Zadara VPSA Object Storage (v 20.01 or later), Ceph (v14.2.6 or later), and Cloudian (v 7.2 or later).

Setting Up Cloudian HyperStore 7.2.1 and Creating an Immutable Bucket

To set up Cloudian HyperStore 7.2.1 and create an immutable bucket, you’ll need:

* Veeam Backup & Replication v10

* An object-based storage solution (I’ll be using Cloudian HyperStore)

* An lab environment to deploy it all in

Download the AWS CLI, Cloudian HyperStore OVA, and Veeam Backup & Replication from the links provided. Install Veeam Backup & Replication on a VM, and install Cloudian HyperStore in your lab environment. Add hostnames with multiple IP addresses to your DNS server (I’m using a zone called vcsp.local). Configure the three nodes, and enable object lock on Cloudian. Create a Veeam component, and use the AWS CLI to create an S3 bucket in the Cloudian environment.

How to Use Immutability with Veeam Backup & Replication v10

To use immutability with Veeam Backup & Replication v10, follow these steps:

1. Create a backup copy of your data using Veeam Backup & Replication v10.

2. Select the immutable bucket as the storage location for your backup copy.

3. Configure the backup copy settings to enable immutability.

4. Verify that the immutability feature is enabled and that your data is now write-protected.

Benefits of Using Immutability with Veeam Backup & Replication v10

By using Veeam Backup & Replication v10 in combination with an object-based storage solution like Cloudian HyperStore, you can ensure your valuable data is protected from ransomware attacks and other malicious activities. Here are some benefits of using immutability with Veeam Backup & Replication v10:

* Write-protect your data to prevent tampering or deletion.

* Ensure ransomware protection for your valuable data.

* Use the same storage location for both your active and backup data.

* Take advantage of object-based storage solutions that offer scalability and cost-effectiveness.

Conclusion

In conclusion, immutability is a game-changer in the world of backup and disaster recovery. By leveraging Object Lock on compatible object storage solutions like Cloudian HyperStore, you can ensure your data remains safe even in the face of ransomware attacks. In the next blog post, I’ll show you how easy it is to recover from a disaster, including the Veeam Backup & Replication server and a total site failure. You must be logged in to post a comment.

Virtual thoughts: Random comments on the IT industry

One of the many use cases for Veeam Backup & Replication is disaster recovery, as the name of the product suggests it can certainly replicate virtual machines from a production environment to a secondary- or disaster recovery environment. While it is a very straight forward process running through a wizard selecting source and target environments and the start replicating the VM across the network, you can even have your virtual machines replicated to a Veeam Cloud & Service Provider (VCSP), if you don’t have a disaster recovery site of your own.

Replicating over the network may not be optimal in all scenarios, at least not the first initial full replication cycle. Let’s say you have a few very large virtual machines that you want to protect by sending them to a disaster recovery site hosted by your VCSP but it’s too big to actually be transferred over the network within the available backup window, what do you do? In Veeam Backup & Replication, you can seed an initial copy of the virtual machine to your service provider using some sort of transportable solution. USB drives, tapes or solutions of that nature – using “sneaker net”.

The basic concept is to get a copy of the virtual machine to the service provider so they can import the VM into their environment and when you start replicating over the network, you just send the changes made to the VM that has occurred since you made the copy of the VM. No need for a full transfer of the VM over the network.

If you are a service provider using VMware vCloud Director (vCD) 10 with the new HTML5 UI for providers, please note that “import from vSphere” is not available in the H5 UI. What’s even more annoying is that the flex UI has also been disabled by default in vCD 10, so to be able to import the VM into the Org vDC of the customer, you first need to enable the flex UI of vCD:

Step 23 – VCSP environment: Import VM in vCD from vSphere.

Select “Move VM” and not “Copy VM” in the Import wizard.

Select the source VM from the customer production hypervisor (the same used in step 1).

Select the Org vDC to use (same as in step 15).

Select vApp and storage policy to be used.

Select desired restore points to keep.

Select desired replication mode.

In the Seeding-tab, in the “Replica mapping” section, select “Map replicas to existing VMs”, click on the VM and select edit.

Select the seeded VM from step 17.

Set a desired replication schedule.

If desired: Click “Run the job when I click Finish”.

Click “Finish”.

Verify that replication successfully finishes.

The replication job only transfers changed blocks since the backup/import was made. You must be logged in to post a comment.

In the latest version of Veeam Backup & Replication, a significant amount of love has been shown to Linux users. One of the most exciting features is the ability to assign a Linux VM the role of a backup proxy. This new functionality allows organizations to leverage their existing patch management systems for their production workloads and ensure the same level of security and patching for their proxies as well.

As a virtualization expert, I found it intriguing to explore the possibilities of automating the deployment of proxy servers. Thankfully, Veeam Backup & Replication has an excellent PowerShell extension that makes automation a breeze. My colleague Anthony Spiteri has also developed a comprehensive project called “Project Ōtosukēru” based on Terraform, which may be of interest to those looking to automate their proxy deployments.

One potential issue with automating proxy deployments is the need for a test/lab environment. However, Veeam provides a small Linux operating system VMware called PhotonOS, which can be used for testing purposes. Instead of performing a traditional install and setup, I decided to use the prebuilt Linux appliance as the source for my proxies.

The script I have developed performs four different tasks:

1. Configures the location and working directory for the downloaded files.

2. Downloads the OVA file and sets the name of the OVA.

3. Configures the Proxy VM with the specified vCPUs, vRAM, logon account, and default password.

4. Sets the IP address, DNS, and NTP server for the Proxy VM.

The script uses a configuration file named config.json to store the settings. The configuration file includes the following parameters:

1. location: Where files will be downloaded and the working directory.

2. ovasource: URL to the OVA.

3. ovaname: Name of the OVA.

4. ProxyBaseName: Base name of the Proxy VM to be deployed.

5. ProxyvCPU: Number of vCPUs to assign the Proxy VM.

6. ProxyvRAM: Amount of vRAM to assign the Proxy VM.

7. sshuser: Logon account for the Proxy VM.

8. ovainitialpassword: Default password of the OVA.

9. newsshpassword: New password to apply for the root user on the Proxy VM.

10. prod: Settings for the production environment, including the IP address of the Veeam Backup & Replication server, vCenter Server, and DNS settings.

To use the script, simply download both files (config.json and Deploy_Veeam_Linux_Proxy.ps1) to c:temp, and then you’re good to go! The script will download only what it requires, and all the settings can be adjusted in the config.json file to reflect your environment.

In conclusion, the new functionality in Veeam Backup & Replication version 10 allows Linux VMs to act as backup proxies, providing organizations with greater flexibility and the ability to leverage their existing patch management systems. With the help of PowerShell and automation tools like Project Ōtosukēru, deploying and managing proxy servers can be streamlined, making it easier for organizations to ensure the security and patching of their workloads.

Creating Generic Functions in PowerShell for Dynamic Menus

As PowerShell users, we’ve all been there – we create a function that seems perfect at the time, but later realize it could be more versatile and generic. In my previous post, I shared a function on how to use PowerShell to create an interactive dynamic menu. However, upon further reflection, I realized that the function could be more flexible by allowing users to change the query without modifying the function itself. In this follow-up post, we’ll explore how to create generic functions in PowerShell for dynamic menus.

The original function had two mandatory parameters: -ListItem and -GetItem. The first parameter retrieves data using a specific query, while the second parameter specifies the task to perform on the selected object. To make the function more generic, we’ll pass the query and task as separate strings instead of hardcoding them within the function. This approach allows users to easily modify the query without affecting the function’s code.

Here’s the updated function signature:

Set-Menu -ListItem $MyQuery -GetItem $MyTask

Now, let’s dive into how this function works. The first parameter, -ListItem, is the query that retrieves data. This can be any valid PowerShell command that returns a list of objects. For example, to retrieve a list of virtual machines (VMs), we can use the following query:

(Get-VM | Sort-Object)

To retrieve a list of datastores, we can use a similar query with a slight variation:

(Get-Datastore | Where {$_.Type -eq ‘VMFS’} | Sort-Object -Descending FreeSpaceGB)

The second parameter, -GetItem, specifies the task to perform on the selected object. This can be any valid PowerShell command that operates on a single object. For instance, if we want to retrieve a specific VM, we can set -GetItem to “Get-VM”. However, this parameter could also be used for more complex tasks like removing a VM or updating its settings.

To use the function, simply pass in the query and task as separate strings, followed by the list of items and their selected state:

Set-Menu -ListItem “((Get-VM | Sort-Object) -contains $($Context.SelectedItem))” -GetItem “Get-VM” -List $MyQuery -Get $MyTask

In this example, we’re retrieving a list of VMs using the previous query and then checking if the selected item is contained within that list. If it is, we perform the task specified by -GetItem, which in this case is “Get-VM”.

The beauty of this approach is that users can modify the query and task without affecting the function’s code. This makes the function more versatile and adaptable to different use cases. For instance, if you want to retrieve a list of datastores instead of VMs, simply change the $MyQuery variable to the appropriate query.

In conclusion, creating generic functions in PowerShell for dynamic menus allows users to modify the query and task without affecting the function’s code. This approach makes the function more versatile and adaptable to different use cases. By following these steps, you can create more powerful and flexible functions that can be used in a variety of situations.

I hope this follow-up post has provided valuable insights into creating generic functions for dynamic menus in PowerShell. As always, I welcome your comments and feedback. Please feel free to share your own experiences and tips on how to create more versatile functions in PowerShell.

Enhancing Your VMware vSphere Test Environment with Interactive Menus

As IT professionals, we often find ourselves setting up test or demo environments and tearing them down a few hours later when we’re done with whatever testing we were doing. While setting up a VMware vSphere test environment is super easy using PowerShell/PowerCLI, I’ve found that using dynamic selection of resources such as datastores can enhance the experience. In this blog post, I’ll show you how to build an interactive dynamic menu of your datastore clusters and use it to select where to install your lab environment.

Why Dynamic Selection Matters

——————————

When setting up multiple labs, you might run out of some resources statically configured in the script. For instance, your datastore configuration might not have enough capacity. By using dynamic selection, you can easily choose the best available resource for your needs.

How to Build an Interactive Dynamic Menu

—————————————

To build an interactive dynamic menu, we’ll use a PowerShell function that calls the datastore clusters available in your vCenter server and orders them based on available free space. Here’s the code for the function:

“`powershell

function Get-DatastoreClusterMenu {

$datastoreClusters = Get-DatastoreCluster -Name *

$menu = @()

foreach ($datastoreCluster in $datastoreClusters) {

$freeSpace = Get-DatastoreFreeSpace – Datastore $datastoreCluster.Name

$menu += [PSCustomObject]@{

Name = $datastoreCluster.Name

FreeSpace = $freeSpace

}

}

return $menu

}

“`

In the above code, we first call the `Get-DatastoreCluster` cmdlet to retrieve a list of all datastore clusters in our vCenter server. We then use a `foreach` loop to iterate over the list and add each datastore cluster to the menu. For each datastore cluster, we use the `Get-DatastoreFreeSpace` cmdlet to retrieve the available free space, and then create a PSCustomObject with the name and free space of each datastore cluster.

We can then call the function and pass it as a parameter to the script from William Lam that sets up the vSphere test environment. The output will look something like this (the menus being produced are highlighted in red):

“`powershell

$script = “……WilliamLamvSphere-PowerCLISet-vSphereLabEnvironment.ps1”

Get-DatastoreClusterMenu -Name * | Select-Object -First 1 | % { $script – Datastore $_.Name }

“`

In the above code, we first set the script path to William Lam’s `Set-vSphereLabEnvironment.ps1` script. We then call the `Get-DatastoreClusterMenu` function and pass it as a parameter to the script. The output will be a list of menus, each containing a list of datastore clusters with their available free space.

Using the Function in William Lam’s Script

——————————————-

To use the `Get-DatastoreClusterMenu` function in William Lam’s script, we can simply add it as a parameter before the `Datastore` parameter. Here’s an example:

“`powershell

$script = “……WilliamLamvSphere-PowerCLISet-vSphereLabEnvironment.ps1”

Get-DatastoreClusterMenu -Name * | Select-Object -First 1 | % { $script – Datastore $_.Name }

“`

In the above code, we first set the script path to William Lam’s `Set-vSphereLabEnvironment.ps1` script. We then call the `Get-DatastoreClusterMenu` function and pass it as a parameter to the script. The output will be a list of menus, each containing a list of datastore clusters with their available free space.

Conclusion

———-

In this blog post, we’ve shown how to build an interactive dynamic menu of your datastore clusters and use it to select where to install your lab environment. By using dynamic selection, you can easily choose the best available resource for your needs. This enhancement can be added to William Lam’s `Set-vSphereLabEnvironment.ps1` script, providing more flexibility when setting up your vSphere test environment.

500 words on Veeam Backup & Replication 9.5 update 4:

The latest update for Veeam Backup & Replication 9.5 has been released, and it brings with it some exciting new features and enhancements for service providers and their customers. As a VCSP (Veeam Cloud & Service Provider), you now have access to even more powerful tools to help you deliver high-quality cloud services to your clients.

One of the most significant updates in this release is the support for vCloud Director in VMware environments. This means that you can now use Veeam Cloud Connect to replicate virtual machines directly from the customer’s onsite vSphere environment to their own Organization and Org vDC within the service provider’s environment. This eliminates the need for manual import and setup, making the process much easier and more efficient.

The solution also includes failover plans, which can be set up and run using the same vCloud Director credentials that the customer received from the service provider. This means that customers can easily configure their environment to ensure business continuity and disaster recovery.

In addition to these updates, there are several other new features and enhancements in Veeam Backup & Replication 9.5 update 4. For example, you can now use Cloud Connect to replicate virtual machines from a customer’s local environment to the service provider’s environment, and vice versa. This allows for seamless migration of workloads between environments, making it easier for customers to scale their operations and move data between environments as needed.

Another key feature is the ability to use a single port for both Cloud Connect and vCloud Director. This eliminates the need for a VPN and makes it much easier for customers to connect to the service provider’s environment.

To demonstrate how to configure these new features, Veeam has created a video tutorial that walks you through the process step-by-step. The video is available in Swedish, but even if you don’t understand the language, you can still follow along with the visual demonstration.

Overall, the latest update for Veeam Backup & Replication 9.5 is a significant release that brings many new features and enhancements to service providers and their customers. With support for vCloud Director, seamless migration of workloads between environments, and easier configuration and management, this update is a must-have for any VCSP looking to deliver high-quality cloud services.

If you’re a VCSP looking to take advantage of these new features and enhancements, be sure to log in to your Veeam account and download the latest version of Veeam Backup & Replication 9.5 update 4 today. With this powerful tool at your disposal, you can deliver even more value to your customers and set yourself apart from the competition.

As an IT professional, it’s important to understand that Microsoft Office 365 is a cloud-based service, and as such, it’s essential to have a plan in place for protecting and backing up your data. While Microsoft provides availability of the service, they also emphasize that the responsibility for protecting and backing up data lies with the customer. This means that you need to think about how you’re going to protect your data and provide some sort of backup mechanism.

One option for backing up Office 365 data is Veeam Backup for Office 365. This solution allows you to not only backup mail but also SharePoint and OneDrive data. As a service provider, you can leverage Cloud Connect to provide backup as a service for your customers.

Setting up Veeam Backup for Office 365 is relatively straightforward. Here are the five steps involved:

1. Install Veeam Backup & Replication on your backup server.

2. Configure Cloud Connect.

3. Add the Office 365 tenant and user credentials.

4. Define the backup settings, such as what data to back up and how often to back it up.

5. Start the backup job.

In addition to backing up Office 365 data, you can also use Veeam Backup for Office 365 to restore items. There are multiple destinations for your restore jobs, including restoring back to Office 365, creating a .pst file, or sending an item as an attachment to an email.

Moreover, you can use this solution to migrate data from an on-premises installation of Microsoft Exchange to Office 365 or vice versa. This bi-directional migration feature makes it easy to move your data between different environments as needed.

In conclusion, it’s crucial to have a plan in place for protecting and backing up your data in Office 365. Veeam Backup for Office 365 is a powerful solution that allows you to easily backup and restore your data, as well as migrate between different environments. As a service provider, offering backup as a service based on this solution can be a valuable add-on for your customers.

Virtual thoughts – Random comments on the IT industry: vCloud Director 9.1 for Service Providers Installation and Firewall Issues

As I recently installed vCloud Director 9.1 for Service Providers, I encountered a “by design” issue that may cause some headaches for new users. In this blog post, I’ll share my experience and the solution to the problem I faced during installation.

vCloud Director Installation and Empty Webpage

During the installation of vCloud Director on a CentOS 7 VM, everything went smoothly until I tried to access the web page after completion. Instead of seeing the vCloud Director login page, I was greeted with an empty webpage. This issue is not uncommon, and it’s due to a firewall configuration that needs to be adjusted.

Required Linux Packages

Before installing vCloud Director, make sure you have all the required Linux packages installed on the VM. In my demo/test environment, I’m using self-signed certificates, but in a production environment, you should use real signed certificates.

Database Connection and Firewall Issues

I had no problem connecting to the database server (again, since my environment is for demo, I’m using Microsoft SQL Server Express 2016 – not supported in a production environment) or the vCD server (to both HTTP and console interfaces) using either IP address or FQDN. However, I encountered issues with connecting to the webpage. It smells a bit like a firewall issue?

Logging and Debugging

To troubleshoot the issue, I started by looking into the logs using the command `tail -f /opt/vmware/vcloud-director/logs/vmware-vcd-watchdog.log`. The log output showed a warning “Server status returned HTTP/1.1 503”. This indicated that there might be an issue with the firewall configuration.

Firewall Configuration

To verify the active firewall rules, I used the command `sudo firewall-cmd –zone=public –list-services`. Only the ssh and dhcpv6-client services were enabled. It seems we’re missing a few services, so I enabled them using:

`sudo firewall-cmd –zone=public –add-service=http`

`sudo firewall-cmd –zone=public –add-service=https`

Verifying the new firewall rules using `sudo firewall-cmd –zone=public –list-services` showed that the services were now enabled and allowed.

Restarting Services

It’s a good practice to restart the services after making changes to the firewall configuration. I stopped the vCloud Director service using `service vmware-vcd stop` and then started it again using `service vmware-vcd start`.

After a successful restart, reopening the browser brought me back to the vCloud Director login page, and I was able to continue configuring the platform.

Conclusion

In conclusion, when installing vCloud Director 9.1 for Service Providers, it’s essential to ensure that all required Linux packages are installed and that the firewall configuration is correct. This issue may cause some frustration, but with the right troubleshooting steps, you can resolve it quickly. Remember to restart the services after making changes to the firewall configuration.

I hope this blog post helps you avoid any potential issues during your vCloud Director installation. If you have any further questions or comments, please feel free to leave them below.

Brandon Seymour’s Journey from Boot Camp to Technology Leadership

Brandon Seymour’s journey to technology leadership began in an unexpected way – through boot camp. As a young man, Brandon enlisted in the military and was sent to boot camp for training. However, his time there was cut short when he suffered a devastating injury that left him discharged from service.

Despite this setback, Brandon did not let his circumstances define him. Instead, he chose to use his experience as a stepping stone towards a new path – one that would lead him into the world of technology.

As he transitioned back to civilian life, Brandon began exploring different career options. He considered going back to school or pursuing a traditional 9-to-5 job, but something was missing. It wasn’t until he discovered the world of technology that he truly found his calling.

With his natural aptitude for problem-solving and his ability to work well under pressure, Brandon felt right at home in the tech industry. He threw himself into learning everything he could about technology and quickly established himself as a valuable member of the team.

Despite facing many challenges along the way – including discrimination and bias due to his military background – Brandon persevered and continued to push forward. His determination and resilience earned him recognition and respect from his colleagues, and he soon found himself in a leadership role.

Today, Brandon is a successful technology leader, using his experiences and skills to inspire and mentor others. He credits his time in the military for teaching him valuable lessons about discipline, hard work, and teamwork – all of which have served him well in his career.

In an interview with Nerd Journey, Brandon shared his story and offered words of encouragement to others who may be facing similar challenges. “Don’t let your circumstances define you,” he said. “There is always a way forward, even if it’s not the path you expected. Embrace your experiences and use them to drive you towards your goals.”

Brandon’s journey from boot camp to technology leadership is a testament to his strength and determination. He proved that with hard work and perseverance, anything is possible – even when faced with seemingly insurmountable obstacles.

If you are looking for inspiration and guidance on your own journey towards technology leadership, Brandon’s story is a great place to start. His experiences and lessons learned can provide valuable insights and encouragement as you navigate your own path forward.