VMworld 2012 Sessions: Free Access with a Twist

Calling all virtualization enthusiasts and professionals! If you’re eager to learn the latest and greatest in the virtualization world, then you’re in luck! Two fellow vExperts, Rick Scherer and Joep Piscaer, are giving away vouchers that grant free access to all of the VMworld 2012 sessions, including associated MP3s and PDFs. That’s right, you could be on your way to acquiring valuable knowledge and skills without spending a dime!

Rick Scherer, known for his excellent blog posts and contributions to the virtualization community, is giving away a voucher that grants free access to all of the VMworld 2012 sessions. To enter the contest, simply visit his post “Win Access to VMworld 2012 Sessions” and follow the instructions. The contest ends on October 31st, so be sure to act quickly!

Joep Piscaer, a fresh VCDX and fellow vExpert, has also jumped on the bandwagon and announced his own “Want to win a VMworld 2012 Subscription?” contest. This means you have not one, but two chances to win access to the VMworld 2012 sessions! To enter Joep’s contest, visit his post and follow the instructions.

The VMworld 2012 sessions cover a wide range of topics, from virtualization fundamentals to advanced techniques and best practices. Whether you’re a seasoned pro or just starting out, there’s something for everyone. The sessions are led by industry experts and thought leaders, ensuring that you receive the highest quality training and insights.

In addition to the sessions, the VMworld 2012 conference also features an expo hall filled with cutting-edge technology and solutions from leading vendors. You’ll have the opportunity to network with peers, learn about the latest products and services, and even win prizes!

So what are you waiting for? Head over to Rick’s and Joep’s posts and enter to win your free access to VMworld 2012 today! Don’t miss out on this incredible opportunity to expand your knowledge and skills in the virtualization space. Good luck, and I hope to see you at VMworld 2012!

Update: The contest has ended and the winners have been announced. Congratulations to all the winners and thank you to Rick and Joep for providing this opportunity to the community!

VMworld 2012 Sessions Up for Grabs – Two Chances to Win!

If you’re a VMware enthusiast looking to expand your knowledge and skills in virtualization, then you’re in luck! Fellow vExpert Rick Scherer is giving away a voucher that provides free access to all of the VMworld 2012 sessions, including associated MP3s and PDFs. And if you miss out on that opportunity, don’t worry – fellow vExpert Joep Piscaer has followed suit and announced his own “Want to win a VMworld 2012 Subscription?” contest!

Rick Scherer’s Contest

In Rick’s post, Win Access to VMworld 2012 Sessions, he explains how you can enter to win the voucher that grants you access to all of the VMworld 2012 sessions. All you have to do is follow these simple steps:

1. Follow Rick on Twitter @rscherer.

2. Retweet his post with the hashtag #VMworld2012.

3. Post a comment on Rick’s blog with your VMworld 2012 session wish list.

That’s it! By following these three easy steps, you’ll be entered into a random drawing to win the voucher. The contest is open until October 31st, so don’t wait to enter.

Joep Piscaer’s Contest

If you miss out on Rick’s contest, don’t worry – Joep Piscaer has got you covered! In his post, Want to win a VMworld 2012 Subscription?, Joep is giving away a subscription to the VMworld 2012 sessions. To enter, all you have to do is:

1. Follow Joep on Twitter @joep_piscaer.

2. Retweet his post with the hashtag #VMworld2012.

3. Post a comment on Joep’s blog with your VMworld 2012 session wish list.

Just like Rick’s contest, this one is open until October 31st, so be sure to enter before it’s too late.

Why You Should Enter

Both of these contests offer an incredible opportunity to gain access to all of the VMworld 2012 sessions, including associated MP3s and PDFs. With this voucher, you’ll be able to learn from some of the best minds in the virtualization industry and expand your knowledge and skills in virtualization. Plus, who doesn’t love free stuff?

In addition, entering these contests will give you a chance to connect with other VMware enthusiasts and potentially win some other great prizes. So what are you waiting for? Head over to Rick’s and Joep’s blogs and enter to win today!

Conclusion

If you’re looking to expand your knowledge and skills in virtualization, then these contests are a perfect opportunity to do so. With two chances to win access to all of the VMworld 2012 sessions, including associated MP3s and PDFs, you have nothing to lose and everything to gain. So head over to Rick’s and Joep’s blogs today and enter to win!

Using HP StoreOnce Appliances as CIFS Repositories for Veeam Backup & Replication

In this article, we will explore how to use HP StoreOnce appliances as CIFS repositories for Veeam Backup & Replication. We will cover the configuration of the StoreOnce VSA in terms of backing up virtual machines, the configuration of a Veeam backup job, and some backup tests.

Configuring the NAS Share

To configure the NAS share on the StoreOnce VSA, log in to the StoreOnce Management Console and follow these steps:

1. Click on “NAS” and then on “Shares.”

2. Click “Create” on the upper-right corner.

3. Name your CIFS share and click “Create.”

4. If you want to enable authentication, you can do so under “NAS.”

Configuring the Backup Repository

To configure the backup repository on the StoreOnce VSA, follow these steps:

1. In the Veeam Backup & Replication console, go to “Backup Infrastructure” and click on “New Backup Repository.”

2. Name the repository and click “Next.”

3. Select “Shared Folder” as the repository type and click “Next.”

4. Enter the UNC path to the StoreOnce VSA share, including the username and password if you have enabled authentication.

5. Click “Advanced” and enable the checkbox “Decompress backup data blocks before storing” to ensure that the data blocks are decompressed before being written to the StoreOnce VSA.

Creating a Backup Job

To create a backup job using the StoreOnce VSA as a CIFS repository, follow these steps:

1. In the Veeam Backup & Replication console, go to “Backup Infrastructure” and click on “New Backup Job.”

2. Give the job a name and click “Next.”

3. Add the backup objects (virtual machines) to the job.

4. Go to the “vSphere” tab and enable the checkbox “Enable VMware Tools quiescence” to ensure that the job runs correctly.

5. Go to the “Job Settings” tab and configure the job scheduling depending on your needs.

6. Click “Create” to create the job.

Testing the Backup

To test the backup, run the job manually or wait until the scheduled job starts. During the first full backup, Veeam Backup & Replication processed 17 GB and transferred 10 GB. The StoreOnce VSA wrote 7,4 GB to disk. A second full backup showed similar results as the first full backup, but only additional 0,2 GB were written to disk, and the deduplication ratio raised from 2.4 to 4,7.

Accessing the CIFS Share

You can access the CIFS share using the Windows Explorer. You can see that the stored files doesn’t differ from a “normal” CIFS repository.

Best Practices and Considerations

When using a HP StoreOnce VSA as a CIFS repository for Veeam Backup & Replication, some best practices and considerations should be taken into account:

1. The settings used in this article are recommended for maximizing the backup capacity and retention time.

2. If you focus on RTO (Recovery Time Objective), you should consider backing up critical VMs to a physical backup proxy with local disks (or access to a fast storage system) in addition to a backup to a StoreOnce appliance or VSA.

3. The backup and restore performance depends on the backup target (StoreOnce VSA) and the backup proxy (in my case a VM). Depending on your environment and the number of backup proxies, backup targets, and repositories you have to make additional decisions.

Conclusion

Using HP StoreOnce appliances as CIFS repositories for Veeam Backup & Replication is really easy and doesn’t need much configuration. By following the steps outlined in this article, you can configure the StoreOnce VSA to store backups of virtual machines. However, some points should be considered when using a HP StoreOnce VSA as a CIFS repository for Veeam Backup & Replication.

Sure! Here is a new blog post based on the information provided:

—

Update Payroll Tax Table in QuickBooks: Troubleshooting and Solutions

If you’re using QuickBooks for your business accounting, you may have encountered an issue with the Payroll Tax table not updating. This can be a frustrating problem, but don’t worry – we’ve got some troubleshooting steps and solutions to help you resolve the issue.

Symptoms of the Problem

———————-

If you’re experiencing this issue, you may notice that the Payroll Tax table in QuickBooks is not updating even after you’ve entered new tax rates or made other changes. You may also see an error message indicating that the tax table is not current or that there are no tax rates defined.

Causes of the Problem

———————-

There could be several reasons why the Payroll Tax table is not updating in QuickBooks, including:

* Outdated tax rates: If the tax rates in your QuickBooks file are outdated, the Payroll Tax table may not update correctly.

* Incorrect tax rate setup: If you’ve set up the tax rates incorrectly, the Payroll Tax table may not update properly.

* Database issues: Sometimes, database issues can cause the Payroll Tax table to fail to update.

* Software bugs: It’s possible that a software bug could be causing the issue.

Troubleshooting Steps

———————–

To troubleshoot this issue, you can try the following steps:

1. Restart QuickBooks: Sometimes, restarting the software can help resolve the issue.

2. Check for updates: Make sure that your version of QuickBooks is up to date and that you’ve installed any available updates.

3. Verify tax rates: Double-check that the tax rates in your file are correct and up to date.

4. Test the Payroll Tax table: Try running a test payroll to see if the Payroll Tax table updates correctly.

5. Contact QuickBooks support: If none of the above steps resolve the issue, you may need to contact QuickBooks support for further assistance.

Solutions

———-

If the troubleshooting steps don’t resolve the issue, here are some possible solutions:

1. Update tax rates: Make sure that you’ve updated your tax rates in QuickBooks to reflect any changes in tax laws or rates.

2. Review tax rate setup: Double-check that you’ve set up the tax rates correctly in QuickBooks.

3. Reconcile payroll: If the Payroll Tax table is not updating, try reconciling your payroll to ensure that all taxes are being calculated correctly.

4. Clear cache: Sometimes, clearing the cache can help resolve issues with QuickBooks.

5. Contact a QuickBooks ProAdvisor: If none of the above steps resolve the issue, you may need to contact a QuickBooks ProAdvisor for further assistance.

Conclusion

———-

If you’re experiencing issues with the Payroll Tax table not updating in QuickBooks, there are several troubleshooting steps and solutions that you can try. By following these steps, you should be able to resolve the issue and ensure that your payroll taxes are being calculated correctly. Remember to always keep your tax rates up to date and double-check your setup to avoid any issues.

Expanding and Shrinking Kubernetes Clusters with Nutanix Kubernetes Engine (NKE)

In our previous article, we deployed a Kubernetes cluster using the Nutanix Kubernetes Engine (NKE). Today, we will explore how to expand or shrink the cluster as needed. This is crucial for day-two operations and ensures that the cluster can scale up or down based on changing requirements.

Scaling Up the Cluster

————————

To add more worker nodes to our existing cluster, we need to follow these steps:

1. Click on the “Node Pools” menu.

2. Select the “Worker” pool.

3. Click on the “Actions” button.

4. Select “Resize” from the dropdown menu.

5. Increase the total number of nodes in the pool to the desired number.

As we can see, NKE will create a new worker node and join it to the cluster. We can then scale an existing deployment to run on the new worker:

1. Click on the “Deployments” menu.

2. Select the deployment we want to scale.

3. Click on the “Actions” button.

4. Select “Scale” from the dropdown menu.

5. Enter the desired number of replicas for the deployment.

After scaling the deployment, we can see that four containers are running on the new worker:

Shrinking the Cluster

———————

To shrink our cluster, we need to follow these steps:

1. Click on the “Node Pools” menu.

2. Select the “Worker” pool.

3. Click on the “Actions” button.

4. Select “Resize” from the dropdown menu.

5. Decrease the total number of nodes in the pool to the desired number.

As we can see, NKE will delete worker nodes one by one, and pods will be redeployed on the remaining nodes. We need to ensure that the minimal number of worker nodes for a production cluster is three:

1. Click on the “Node Pools” menu.

2. Select the “Worker” pool.

3. Click on the “Actions” button.

4. Select “Delete” from the dropdown menu.

5. Confirm the deletion of the desired worker node.

After deleting a worker node, we may face an error if the cluster health is not normal:

1. Check the /home/nutanix/data/logs/karbon_core.out log file to troubleshoot the NKE issues.

2. Resize the worker pool again with a minimum of three nodes as required for a production deployment.

Creating a New Worker Pool

—————————-

To create a new worker pool, we need to follow these steps:

1. Click on the “Node Pools” menu.

2. Select “Add Node Pool” from the dropdown menu.

3. Specify the settings for the new pool, such as the number of nodes and their configuration.

4. Click “Add” to create the new pool.

5. The procedure should begin, and we can see that the new pool is deploying:

After creating a new worker pool, we can run containers on the new nodes:

1. Click on the “Deployments” menu.

2. Select the deployment we want to run on the new nodes.

3. Click on the “Actions” button.

4. Select “Scale” from the dropdown menu.

5. Enter the desired number of replicas for the deployment.

Conclusion

———-

In this article, we explored how to expand and shrink Kubernetes clusters with Nutanix Kubernetes Engine (NKE). We learned how to add more worker nodes to our existing cluster, delete worker nodes, and create a new worker pool. Remember that the minimal number of worker nodes for a production cluster is three. By following these steps, we can ensure that our Kubernetes cluster can scale up or down based on changing requirements.

Expanding and Shrinking Kubernetes Clusters with Nutanix Kubernetes Engine (NKE)

In our previous article, we explored deploying a Kubernetes cluster using the Nutanix Kubernetes Engine (NKE). Today, we will delve into day-two operations for managing Kubernetes clusters, focusing on expanding and shrinking clusters. We will begin with a brand new Kubernetes cluster deployed in our previous article, consisting of 2 control plane nodes, 3 etcd, and 3 worker nodes.

Scaling Up and Shrinking the Cluster

Let’s start by scaling up our cluster. To do this, we need to add more worker nodes to the existing pool. We can increase the total number of nodes in the pool, and NKE will create a new VM and join it to the Kubernetes cluster. Here’s how to resize the worker pool:

1. Click on Node Pools in the NKE interface.

2. Select the existing pool, and click the Actions button.

3. Click Resize from the dropdown menu.

4. Increase the total number of nodes to four, and click Update.

NKE will create a new VM and join it to the Kubernetes cluster. We can see the new worker in the pool:

Now, let’s scale an existing deployment to run a few containers on the new worker:

1. Click on Deployments in the NKE interface.

2. Select the existing deployment, and click the Actions button.

3. Click Scale from the dropdown menu.

4. Adjust the replicas to 4, and click Update.

We can see four containers running on the new worker:

Deleting a Worker Node

Let’s delete one of the existing worker nodes. To do this, we need to click the Delete button in the NKE interface. However, before deleting, NKE will check the Kubernetes cluster’s health and ensure it’s OK before moving on to the next step. We can see that pods from worker 2 were restarted on workers 0 and 1, while worker 2 is being deleted:

And.., just to demonstrate, an error occurs after deleting one worker:

Pro tip: Check the /home/nutanix/data/logs/karbon_core.out log file. This log contains all the information you need to troubleshoot NKE issues.

Shrinking the Cluster

Now let’s shrink our pool to one node using the resize button as before:

1. Click on Node Pools in the NKE interface.

2. Select the existing pool, and click the Actions button.

3. Click Resize from the dropdown menu.

4. Set the total number of nodes to 1, and click Update.

NKE will delete two worker nodes. This is a step-by-step procedure, and workers will be deleted one by one. Before deleting, NKE drains the node (I believe it uses something like kubectl drain), and pods restart on other nodes in the cluster. At each step, NKE will check the Kubernetes cluster’s health and ensure it’s OK before moving on to the next step:

We can see that the cluster has been successfully shrunk to one node:

Non-Default Pools

As a reminder, the minimum number of workers for a production cluster is three. However, we can still shrink our original pool to one node even though it’s not the default pool:

I have one worker node in the default pool and two nodes in the new one. You may remember that before, we couldn’t shrink our original pool to one node, but now we can. In this situation, if you try to shrink small-pool, you will face an error, as we’ve faced before, because the total number of nodes will be less than three:

Notice, that we can’t delete our original pool. It should contain at least one node. That’s all for now. I hope you know better how to expand worker pools, add another one, or shrink them. Don’t forget about the minimum worker’s count.

Cluster API Simplifies Execution and Builds Solid Foundations with v1alpha2

In the latest release of Cluster API, version 1alpha2, we have taken a significant step forward in our vision of using a declarative API to create and manage Kubernetes clusters. Building on top of Kubeadm, Cluster API provides a unified way to manage a Kubernetes cluster’s infrastructure and lifecycle, making it easier to deploy and manage cloud-native applications.

With the v1alpha2 release, we have made several key advancements that simplify execution and build solid foundations for our users. Here are some of the key highlights:

Improved Declarative API

————————

One of the most significant improvements in v1alpha2 is the improved declarative API. This API allows users to describe their desired cluster state in a simple, human-readable format, and Cluster API takes care of the details of deploying and managing the cluster. This approach makes it easier for developers and operators to work together, as they can focus on the desired state of the cluster rather than the specific steps required to deploy and manage it.

Enhanced Infrastructure Support

——————————

Cluster API v1alpha2 provides enhanced support for a wide range of infrastructure providers, including AWS, GCP, and Azure. This means that users can easily deploy and manage their Kubernetes clusters on their preferred cloud provider, without having to worry about the underlying infrastructure details.

Simplified Lifecycle Management

—————————–

Managing the lifecycle of a Kubernetes cluster can be complex and time-consuming, but Cluster API v1alpha2 simplifies this process with a unified approach to managing the cluster’s infrastructure and applications. With Cluster API, users can easily create, update, and delete their clusters, as well as manage the applications running on them.

Improved Tooling Support

————————-

Cluster API v1alpha2 also includes improved tooling support, with better integration with popular tools such as Helm and Kustomize. This means that users can easily use these tools to manage their Kubernetes clusters and applications, without having to learn a new set of commands or APIs.

Enhanced Security Features

—————————

Finally, Cluster API v1alpha2 includes several enhanced security features, including improved RBAC support and better integration with existing security tools such as Calico and Istio. This means that users can easily secure their Kubernetes clusters and applications, without having to worry about the underlying infrastructure details.

Conclusion

———-

In conclusion, the v1alpha2 release of Cluster API represents a significant step forward in our vision of using a declarative API to create and manage Kubernetes clusters. With improved support for infrastructure providers, simplified lifecycle management, better tooling integration, and enhanced security features, Cluster API is making it easier for developers and operators to work together and deploy cloud-native applications at scale. We look forward to continuing to advance this vision in future releases of Cluster API.

5 Key Points for Non-DBAs to Manage SQL Server Effectively

As an IT Pro, managing a SQL Server database can be a daunting task, especially if you’re not a trained DBA. However, with the right knowledge and tools, you can effectively manage your SQL Server databases and ensure they are running smoothly. In this blog post, we’ll cover the 5 key points from the DBI-B220 session on Introduction to SQL Server Management for Non-DBAs, which will help you manage your SQL Server databases with ease.

1. Backups and Restores

Backups and restores are essential tasks for any database administrator. However, for non-DBAs, these tasks can be overwhelming. The session covered the different types of backups available in SQL Server, such as full backups, transaction log backups, and differential backups. It also discussed how to create and restore backups using the SQL Server Management Studio (SSMS) and Transact-SQL (T-SQL).

One important tip for non-DBAs is to ensure that you have a reliable backup solution in place. This can include using a backup agent, such as the SQL Server Agent, or a third-party tool. Additionally, it’s essential to test your backups regularly to ensure that they are complete and can be restored successfully.

2. Checking for Corruption

Corruption can occur due to various reasons, such as hardware failures, software issues, or user errors. As a non-DBA, it’s crucial to know how to check for corruption in your SQL Server databases. The session covered how to use the CHECKDB and DBCC commands to identify and repair corruption.

One important thing to note is that corruption can be subtle and may not always be visible. Therefore, it’s essential to regularly run checks on your databases to ensure they are healthy and functioning correctly.

3. Performance Tuning

Performance tuning is critical for any SQL Server database, as it directly affects the user experience. The session covered the basics of performance tuning, such as understanding CPU and disk usage, identifying bottlenecks, and using the SQL Server Profiler to troubleshoot issues.

One key takeaway for non-DBAs is to regularly monitor your databases’ performance and adjust settings accordingly. This can include optimizing indexing, caching frequently accessed data, and configuring connection pooling. Additionally, it’s essential to test changes in a development environment before implementing them in production.

4. Indexing and Statistics

Indexing and statistics are crucial for SQL Server query performance. The session covered how to create and manage indexes, as well as how to use statistics to optimize queries.

One important tip for non-DBAs is to regularly review and maintain your indexes. This can include dropping unused indexes, rebuilding indexes, and creating new indexes for frequently accessed columns. Additionally, it’s essential to understand how to use the SQL Server Management Studio (SSMS) to view and analyze query statistics.

5. Disaster Recovery and Business Continuity Planning

Disaster recovery and business continuity planning are essential for any organization that relies on SQL Server databases. The session covered how to create a disaster recovery plan, including identifying critical resources, creating backup strategies, and testing the plan regularly.

One key takeaway for non-DBAs is to ensure that you have a comprehensive disaster recovery plan in place. This can include creating a disaster recovery team, identifying critical databases and data files, and regularly testing the plan using the SQL Server Management Studio (SSMS) and T-SQL. Additionally, it’s essential to understand how to use the SQL Server Agent to automate disaster recovery tasks.

In conclusion, managing a SQL Server database can be a complex task for non-DBAs, but with the right knowledge and tools, it can be done effectively. By following these 5 key points from the DBI-B220 session on Introduction to SQL Server Management for Non-DBAs, you’ll be well on your way to managing your databases with ease. Remember to regularly back up your databases, check for corruption, perform performance tuning, use indexing and statistics, and create a comprehensive disaster recovery plan. With these skills, you’ll be able to ensure that your SQL Server databases are running smoothly and securely.

Tails 6.3 Released with Security Improvements and Small Enhancements

The maintainers of the open-source Linux distribution Tails have released version 6.3, which includes several security improvements and small enhancements. Tails is a live operating system that can be run directly from a USB stick, providing users with a secure and private computing environment.

Security Improvements

The new version of Tails includes several security improvements, including the integration of the latest Tor Browser version 13.0.15, which addresses a vulnerability in the handling of PDF files. The Thunderbird mail client has also been updated to prevent a potential security issue related to the internal PDF reader. Additionally, the project has addressed a long-standing issue with the configuration of new printers, which could cause problems if previous versions of Tails were installed on the system.

Other Changes and Enhancements

In addition to the security improvements, Tails 6.3 includes several small enhancements and changes. For example, the default button for automatic upgrades has been changed from “Restart now” to “Restart later”, which is intended to provide a more user-friendly experience. The project has also addressed an issue with the display of welcome screens and the start of the Gnome desktop, which could be delayed in certain situations.

Installation Images Available for Download

As usual, the Tails project provides installation images for USB sticks and ISO files for burning to DVD or testing in a virtual machine. The latest version of Tails is available for download from the project’s website.

Previous Version Released with Translation Updates

The previous version of Tails, version 6.2, was released at the end of April and included updates for 21 additional languages. The focus of that release was on translations, with the goal of making the system more accessible to users around the world.

Conclusion

Tails 6.3 is a significant update to the open-source Linux distribution, providing several security improvements and small enhancements. With its focus on privacy and anonymity, Tails continues to be a popular choice for users looking for a secure computing environment. Whether you’re looking to protect your online identity or simply want a more private computing experience, Tails is definitely worth considering.

As a virtualization engineer, I recently ran into an unexpected issue while updating my HP ProLiant BL460c G8 blades from VMware ESXi 5.0.0 Update 1 to the latest Build 821926. After installing the new blades and applying the update, I noticed that the local storage was no longer visible on the hosts.

To troubleshoot the issue, I decided to record the output of the esxcli command and found a hidden gem inside the output: the removal of the Hewlett-Packard bootbank scsi-hpsa VIB by the VMware update itself. This removal effectively removes the ESXi hosts’ ability to read the local datastore from the HP Smart Array P220i Controller.

I then downloaded the scsi-hpsa-5.0.0-28OEM.500.0.0.472560.x86_64.vib file from hp.com and installed it on the host to rectify the issue. After installing the update and reinstalling the HP ProLiant Smart Array Controller Driver, another quick reboot later, my host was upgraded to the correct build and the local datastore was available again.

This experience taught me a valuable lesson: be careful when updating your hosts and make sure you have a real retreat option ready if you need to quickly roll back to the previous build. Test your updates every time, as you never know what issues may arise. As virtualization engineers, we must always be vigilant and proactive in our troubleshooting and testing to avoid any potential issues that could affect Our Production Environments.