I converted a physical machine to a Hyper-V VM using:  https://www.experts-exchange.com/questions/29103396/Convert-physical-Server-SBS-2011-to-a-smaller-partition-into-Hyper-V.html#a42625473

Now when testing the VM I am having connectivity issues.  For starters I can ping the machine by ip address from some other servers on the network but from others it doesn't ping.  Also, from any device that I have tried I am unable to access the shares on the server.

Not sure how to go about diagnosing what is going on or why it is different now that it is running in as a VM.

Hi All,

I am facing an issue while configuring soft zoning for host and 3 par.
when I activate zoneset on Switch1 , Switch2 zones deactivates and show 0 active path on storage and vice versa
only for 3 par. Other zones for other storage are still intact on those switch.

I have searched the internet and don’t k now if there is a solution to a problem we are facing.

We have received Windows 2008 Sever backup images from a customer.  
These images are rather large. Some are 540 GB and some over 1 TB.  

We need to covert the images to VMware ESXi 6.0 VMs.  

However, we are currently restricted by datastore space.  
The most we have available is possibly 500 GB.

We cannot connect another drive at this point or add an external USB drive.  

We are guessing that backups don’t reflect what the actual total size may be.
Possible only 20 GB of space is actually used.

Is there a way to shrink a Windows Backup Image?

I know in VMware converter, you can shrink a volume, but we cannot build a VM and attach a converted image (vmdk via Starwind Converter) as the space is limited.

thanks

2 Node, Server2016 Hyper V Cluster connecting to a SAN via iscsi.
The San has a total of 3 LUNS.  2 For the vm's to "live" and one for Quorum.

When I pause Node1 and drain the roles.  The VM's drain to Node2.

When I pause Node2 and drain the roles, both  Cluster Disks go offline and the VM's autopause.

During the outage, I was able to ping the iSCSI ports on the SAN and I disabled AV/Firewall on the hosts but that did not resolve anything.
Only resuming Node2 brought the CSV's online.

This cluster was able to failover properly in the past and my lab is failing over correctly as well.

I don't want to run the ClusterVal Wizard until my next maintenance window ( JUST IN CASE ). Before I do run the CLusterVal, has anyone ran into this scenario before?

Cluster.log attached

Hi All,

Can anyone help me with the VMware Horizon View (VDI) interview questions?

Thanks

Hello,

I am looking fr advice on a backup strategy. Currently my environment has the following specifications:

2 x  VMWare ESXI Hypervisors connected to a SAN with 12 Virtual machines
9 TB of storage space
Physical server (end of life) that has an LTO 5 tape backup unit capable of 10+ TB of storage; It is connected to a cheap 54 TB NAS which holds all backup data
Licensed with Veeam Enterprise 9.5 (to backup VM's)
Licensed with Symantec Backup Exec (archive data to tape)

The above description for backups (and more or less disaster recovery) is in my opinion an outdated method of doing backups. I would like to move to a more modern method that meets the company goals.

I would like to do the following:

Have a retention period: 30 Days, with ongoing monthly backups
-preferably ability file level restore
-Backup to cloud or offsite data center
-Ability to restore images in Amazon (or another ESXi server) in the event of a disaster at HQ
-RPO of 24 hours
-RTO of 4 hours (if possible)

Data is safe and destination of backups needs to be a proven reliable source. Backed up data is encrypted.

I am on a tight budget.

One of the recommendations on this site was to use CloudBerry with Backblaze. I am not certain if this a good commercial solution for Disaster Recovery and backups

I still have the ability to backup everything to disk and then archive to a cloud storage vendor, although I imagine restoring data would be quite slow, even with a Gigabit …

Dear All

 
              i recently have a probem on veeam (backp to tape) although i changed to use a brand now backup tape, this problem still occur, may i know this is reated to hardware or veeam software itself ? any help would be appreicated,

I have a Hyper V server  with 3 guests.
The host only has one partition so hyper v is running on the local C: drive.

I'm going to do a one time backup just for disaster recovery purposes. In case the whole server goes.
Would it be beneficial to do a one time backup of the whole host using windows backup?
And then I could restore the virtual machines using image restore to the VM.


This customer uses Datto Backup for the guest servers.

I need to create a volume with "Bytes per Physical Sector" = 512 so I can use it as the staging location for Backup Exec (using GRT -Granular Recovery Technology) to restore Exchange (physical 2007) mailbox / items. (I know this setup is old. We are migrating.)
GRT requires the staging location have the same sector size as the volume from which the Exchange log files were backed up.
 
To do that, I added a new VHDX to the Backup Exec server (a 2012R2 VM on 2012 R2 Hyper-V host) and then I issued  
"Set-vhd VHDname.vhdx -PhysicalSectorSizeBytes 512"
to change its Physical Sector Size to 512 bytes. I did verify using "Get-vhd VHDname.vhdx" that it shows PhysicalSectroSize = 512.
But to my surprise when I got in to the VM and issued the following command on an elevated command prompt:
fsutil fsinfo ntfsinfo D:  (where D: is the VHDX I just created)
it shows the "Bytes Per Physical Sector" = 4096

I'm confused... Why are they different? Did I miss anything? How to create a vhdx with "Bytes Per Physical Sector" = 512

Hi

I am looking for advice on the following:

I have an issue within my Citrix VDI environment, that when VDI Desktops not in use are powered off for a pre-longed period of time, they automatically get placed into Maintenance mode. According to a Citrix article there is a DWORD to amend to be able do disable this behviour, which involves changing to a NEGATIVE value. I can't see how this is done as my undserstanding was a DWORD can only accept a 0 upwards:

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

DesktopServer\MaxFailedRegistrationsAllowed

DWORD

2

Controls automatic placement of power-managed VMs into maintenance mode following repeated failures to register with a DDC.

If a VM is started-up by the broker service but fails to register after the period defined by the MaxRegistrationDelayMin setting (default 20 minutes), it is shutdown again.

The MaxFailedRegistrationsAllowed value defines the maximum number of times that this start-up, registration failure, shut down cycle is allowed to repeat before a subsequent registration failure causes the VM to be automatically placed into maintenance mode.

 

The default value of 2 means that if the VM fails to register 3 times in succession, it will be automatically placed into maintenance mode.

Setting MaxFailedRegistrationsAllowed to a negative value (0xFFFFFFFF) disables this behavior and prevents VMs from ever being automatically placed into maintenance mode.

…

Veeam backup fails to create a snapshot due to error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{e8796d4d-5afe-446a-9648-f0fb208162c1}]. Writer's state: [VSS_WS_FAILED_AT_FREEZE]. Error code: [0x800423f2].

Writers are all stable and have no errors
Server has been rebooted and dlls have been re-registered

Disk shadow verify command shows this result:

-> set verbose on
-> set context volatile
-> add volume C:
-> add volume \\?\Volume{53357368-6671-426e-9410-8289db3d0c8f}\
-> writer verify {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
-> writer verify {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
-> writer verify {0bada1de-01a9-4625-8278-69e735f39dd2}
-> writer verify {e8132975-6f93-4464-a53e-1050253ae220}
-> writer verify {be000cbe-11fe-4426-9c58-531aa6355fc4}
-> writer verify {8d5194e1-e455-434a-b2e5-51296cce67df}
-> writer verify {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
-> writer verify {6f5b15b5-da24-4d88-b737-63063e3a1f86}
-> writer verify {2707761b-2324-473d-88eb-eb007a359533}
-> writer verify {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
-> writer verify {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
-> writer verify {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
-> writer verify {afbab4a2-367d-4d15-a586-71dbb18f8485}
-> writer verify {542da469-d3e1-473c-9f4f-7847f01fc64f}
-> writer verify …

Veeam not connect to Vcenter - connection is being actively refused - portqry says 443 is not listening on Vcenter but netstat shows that 443 is listening

Hi,

We have a Windows 2012 R2 domain controller Hyper V running on a Windows 2012 R2 server. We are getting speeds of 45mbps up & down but they Hyper V is barely reaching 8mbps.

The Hyper V has 2 processors & 16GB RAM so really more than enough for it. I have turned off VMQ's on the Hyper V (as per a quick google search) & this increased the speed a little but not very much.

Any ideas on what I am missing?