Tuesday, April 17, 2018

Commvault backup and windows server 2008 r2 quiesce error "Failed Unable to quiesce guest file system during snapshot creation"

After getting a new Commvault V11, when tried to backup a windows server 2008 R2, getting "Failed Unable to quiesce guest file system during snapshot creation".

Reason:This issue occurs if there is a conflict between the Microsoft based volume shadow copy services and VMware snapshot provider. 
To resolve this issue, use any one Quiescing tool. As VMware snapshot provider is only used for snapshot / Quiesing purposes, this can be disabled.

1. Stop and Disable VMware snapshot provider

2. Start and set VSS to Automatic / Manual

3. Restart Virtual disk service and then  attempt to create a manual Quiesced snapshot. 

F5 BIGIP VE and ESX 6.5, Invalid configuration for device '0' or Failed to connect virtual device 'Ethernet0'

I was receiving "Failed to connect virtual device 'Ethernet0'" and "Invalid configuration for device '0' "error after moved F5 BIGIP VE 13.0.x.x to ESX 6.5 with vcenter 6.5 with distributed switches, and upgraded HW compatibility to version 13.
I searched google and could not find why it was happening.
After I found that the highest VM HW version it support is 10. (https://support.f5.com/csp/article/K69120675)
When you update VM's HW to a higher version, it works with VMware tools to fix any complication,
F5 does not support VMtools to be updated on F5 BIGIP VE. (https://support.f5.com/csp/article/K11744866)

Long story short, here is how I fixed the problem.
1. Turnoff the VM.
2. Download VMX files of the VM to your PC.
3. Go to Edit window the VM, take a screen shot of the nic's setting especially networks they are connected to.
3. Remove all virtual NICs from the VM, and save.
4. Go back to the Edit window again and add NICs, assign correct network. On NIC settings, manually set the MAC address, get the original MAC address from the VMX file you downloaded from the step 2.
5. Turn on the VM.

Wednesday, April 11, 2018

System Center Updates Publisher (SCUP) 2017 is now avilable

System Center Updates Publisher (SCUP) 2017 is now available

Using SCUP, you can:
  • Import updates from external catalogs (non-Microsoft update catalogs). 
  • Modify update definitions including applicability, and deployment metadata. 
  • Export updates to external catalogs. 
  • Publish updates to an update server. 

This release of SCUP adds support for Windows 10 and Windows Server 2016.

Indexing for quicker imports of previously imported catalogs –  Catalog producers can now index their catalogs. This will allow users to more quickly import large catalogs containing few new updates.  

Inclusion of signing certificates within updates catalogs – Catalog producers can now include signing certificates with their updates catalogs.  This enables users to add the certificates to the trusted publishers list during import so that approval prompts will not block publish operations. 

Signature Timestamp – Updates published to a WSUS server will by default have the signature time-stamped.  Note, this functionality requires internet access. If you have upgraded from preview 1 this will not be automatically enabled.  To enable or disable this functionality or configure the timestamp server that is used, see the Advanced page under Options

This installer updated my preview 2 (ver version of SCUP 2017 to production version (ver

Announcement is here

Download from here