I´m doing backup using a simple script in my WIn2012R2

A batch file is combined with a simple set of commands in a diskshadow.txt file (see below)

There´s NO snapshots created (ever) and in the log file The robocopy part of the script) it appears:

What is that?

WHy a single VHD file, creates a bunch of .AVHD files and worst, an -AutoRecovery.avhd file?

80.2 m  maximo-bvs.CORP_D88FDF47-1672-49A5-BCF7-B3695D0D5033.avhd
32.4 m  maximo-bvs.CORP_DATA_8541169F-4C5E-4B9D-8FAD-07091FB9031C.avhd
122.4 m  maximo-bvs.CORP-AutoRecovery.avhd
50.0 g  maximo-bvs.CORP.vhd
56.2 m  maximo-bvs.CORP_8A478680-3331-4A60-BD61-D02063504F28.avhd
10.4 m  maximo-bvs.CORP_DATA-AutoRecovery.avhd
202.0 g  maximo-bvs.CORP_DATA.vhd
62.5 m  maximo-bvs.CORP_DATA_09B5DB15-B9BB-40D1-B372-F72CEFFD5246.avhd

====================diskshadow.txt =========================

delete shadows all

set context persistent

set verbose on

add volume C:\ alias DISCOC

create

expose %DISCOC% I:

exec HyperVBackup_exec.cmd

unexpose I:

delete shadows all

====================diskshadow.txt =========================

The log file of the diskshadow is:

==================================

Microsoft DiskShadow version 1.0
Copyright (C) 2013 Microsoft Corporation


-> delete shadows all 
No shadow copies found in system.
-> set context persistent 
-> set verbose on 
-> add volume C:\ alias DISCOC
-> create 
Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.
Component "\BCD\BCD" from writer "ASR Writer" is excluded from backup,
because it requires volume  which is not in the shadow copy set.
The writer "ASR Writer" is now entirely excluded from the backup because the top-level
non selectable component "\BCD\BCD" is excluded.

* Including writer "Task Scheduler Writer":
+ Adding component: \TasksStore

* Including writer "VSS Metadata Store Writer":
+ Adding component: \WriterMetadataStore

* Including writer "Performance Counters Writer":
+ Adding component: \PerformanceCounters

* Including writer "System Writer":
+ Adding component: \System Files
+ Adding component: \Win32 Services Files

* Including writer "Microsoft Hyper-V VSS Writer":
+ Adding component: \81A73D21-A9B1-4AA5-AA19-FECC86FD0C9E
+ Adding component: \Host Component

* Including writer "WMI Writer":
+ Adding component: \WMI

* Including writer "COM+ REGDB Writer":
+ Adding component: \COM+ REGDB

* Including writer "Registry Writer":
+ Adding component: \Registry

Alias DISCOC for shadow ID {c333bfe8-df61-4e8a-9389-53642d72ac60} set as environment variable.
Alias VSS_SHADOW_SET for shadow set ID {827cfcb3-4d8c-40a1-90c2-14669e060b0e} set as environment variable.
Inserted file Manifest.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file BCDocument.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM0.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM1.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM2.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM3.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM4.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM5.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM6.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM7.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM8.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file WM9.xml into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab
Inserted file DisBAA2.tmp into .cab file 05-sexta-feira,-08_2027-01-02_BRBVS-MAX0001.cab

Querying all shadow copies with the shadow copy set ID {827cfcb3-4d8c-40a1-90c2-14669e060b0e}

* Shadow copy ID = {c333bfe8-df61-4e8a-9389-53642d72ac60}%DISCOC%
- Shadow copy set: {827cfcb3-4d8c-40a1-90c2-14669e060b0e}%VSS_SHADOW_SET%
- Original count of shadow copies = 1
- Original volume name: \\?\Volume{74d623a1-e9e5-11e4-80b4-806e6f6e6963}\ [C:\]
- Creation time: sexta-feira, 08/05/2015 01:02:12
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy19
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes:  No_Auto_Release Persistent Differential

Number of shadow copies listed: 1
-> expose %DISCOC% I:
-> %DISCOC% = {c333bfe8-df61-4e8a-9389-53642d72ac60}
The shadow copy was successfully exposed as I:\.
-> exec HyperVBackup_exec.cmd 
Copiando VHDs Versao 3.2fb



 Log File : c:\dados\backup\hypervbackup_exec_08.log
-> unexpose I:
Shadow copy ID {c333bfe8-df61-4e8a-9389-53642d72ac60} is no longer exposed.
-> delete shadows all
Deleting shadow copy {c333bfe8-df61-4e8a-9389-53642d72ac60} on volume \\?\Volume{74d623a1-e9e5-11e4-80b4-806e6f6e6963}\ from provider {b5946137-7b9f-4925-af80-51abd60b20d5} [Attributes: 0x00420009]...

Number of shadow copies deleted: 1
-> 

====================================================

We (Us) recently have purchased a small (SmallA) company from a larger company (LargeA). LargeA hosted SmallA servers on a Hyper-V cluster.

We built a Hyper-V environment and LargeA sent us copies of SmallA Hyper-V VM's so our App Support and Dev teams could do some testing.  We imported these copies fine and the servers are working as expected. 

We have since shutdown SmallA office and all equipment has been removed, the office also housed the DR site for SmallA.  SmallA ran their services from LargeA datacenter.

The issue now is that we do not have a DR site for SmallA and this is on us to resolve.  With the migration of SmallA into our company is scheduled to occur in the August/September timeframe, I need to figure out a quick and dirty DR to house their Production Servers if something happens to LargeA.

What I am thinking is to setup replication of SmallA VM's to our Data Center.  I would prefer not to have a trust setup between Us and LargeA.  Is it possible to setup replication of VM's from LargeA Hyper-V environment to our Hyper-V environment without a Trust?  We do have a VPN connection.

OS Name:                   Microsoft Windows Server 2012 R2 Standard
OS Version:                6.3.9600 N/A Build 9600
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00252-60271-31227-AA179
Original Install Date:     5/20/2015, 9:21:51 AM
System Boot Time:          5/20/2015, 11:35:02 AM
System Manufacturer:       HP
System Model:              ProLiant BL460c G6
System Type:               x64-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 26 Stepping 5 GenuineInt
el ~2533 Mhz
                           [02]: Intel64 Family 6 Model 26 Stepping 5 GenuineInt

But the Hyper-V manager, in settings for  the vm, under NUMA config, shows only one socket. 

How do I fix this?

Any help/advice will be greatly appreciated.

Hi,

We are looking to move from physical fileserver to Hyper-v Virtual file server.

we will use SAN storage to store VM's .

Existing data size is around 5TB and expected to be in next 2 years is 10TB.

It is recommended to Go for Hyper-V virtual file server?

what are the best practices for this?

dilip patel

Hello All,

I have a server 2012 R2 with Hyper-V installed. Within Hyper-v, I have 3 guest machines: Guest1, Guest2, and Guest3.

I also have 4 physical Network Interfaces on the server. One set with 10.10.10.10/24 IP and the other setup with 10.10.10.254/24 IP. 

I have created two virtual switches, each labeled switch1 (10.10.10.10/24) and switch2 (10.10.10.254/24) and both created within hyper-v virutal switches as External switches.

Initially all 3 guest machines were attached to Switch1. Everything was running fine for 4 months and all of a sudden, all 3 machines (using static IPs) stopped communicating with the network. All network communication was lost including internet. 

I did everything and could not get these servers to communicate. I could however set each as dhcp and then they would acquire new ip and would work, but the static ip would not work.

Since these are production servers and DNS was pointing to those static IPs, i had to use those IP addresses. After much playing around, i disabled one of the virtual switches and attached all 3 guest machines to the other virtual switch and they started working.

This morning, all three guest machines stopped communication again and i had to remove the virtual switch and attach them back to the original virtual switch and everything started working again.

I'm afraid this will continue. 

What is going on and how i prevent this from happening?

We had 2 physical servers and both running Windows 2012 R2 Server Standard.

We implemented the cross replication method between this 2 servers with NO SAN/NAS at all in between purely just disk on servers which the capacity can handle both servers. 

Our servers as follow (as example):

• Physical01 server has VM01 and VM03
• Physical02 server has VM02 and VM04
  

This method of replication has been running for almost a year and it's been running ok.

This morning we had this situation where there is an electricty outage and set the shutdown/restart. We found that none of the VMs can't be restarted - something to do with VM state issue. After doing troubleshooting we end up kill of the replications instead.

End up running as follow:

• Physical01 server has VM03
• Physical02 server has VM01 (no replication has been setup as yet), VM02 and VM04

Due to all servers except VM01 are not considering a lot of update we managed to use original ones and delete the replication ones, now we are having a dilemma where VM01 (file server) are running on Physical02 as a replica at the moment and there is a data/file has been changed SO what is the best way to handle this issue?

(1) We are thinking to Enable Replication on VM01 on Physical02 and delete VM01 on the Physical01 and run the replication. It means the data will replicate again to Physical01. Once the data has been replicated ... we could do remove the REPLICATION again and then shutdown the VM01 and move data from \Replica Targets\ to \Virtual Machines and then change the path for Virtual Hard Disk in VM for Harddrive 

... OR ...

(2) We do the latest VM backup of VM01 in Physical02 and restore under Physical01 

What do you think? The first approach is good but NOT cleaner as such due the folder structure are messier. We had folders called \VirtualMachines (for virtual machines) and \ReplicaTargets (for VM replicata). Second approach not sure how long this will be because it's involved backup and restore.

Waiting for your input.

Isadewa

Hello everyone,

we have a environment in which I work by taking the remote of my partener machine . it is working fine but due to some problem my partener format their machine and after that when I take the remote he is disconnect that is only one person can have the access at a time .

Can any body suggest me what to do so that both can work at a time .

Regards

Sunny

Good afternoon,

I am almost done with configuring a new Hypervisor running Windows Server 2012 R2. 

I have noticed that when comparing this server to the exisiting Windows Server 2012 Hypervisor, there are slight differences in the network area of things.

I have attached the screen shots with the differences to this post for your review. 

Network Connection Details On Current Hyper-V Server Host (Left) vsNetwork Connection Details On New Hyper-V Server Host (Right):

Why is the new server not showing any IPv4 WINS Servers and why is the NetBIOS over Tcpip not showing to be enabled?

I would prefer that the new server has the IPv4 WINS Server addresses displayed in the Network Connection Details.

I have checked the configuration for IPv4 on the current Hyper-V server and the server does not have any entries for WINS Servers and NetBIOS is set to default.

Network Connection View On Current Hyper-V Server Host (Left) vs Network Connection View On New Hyper-V Server Host (Right):

Why am I seeing both bridged NICS on the new Hyper-V server? I would prefer that the network connection displayed the network to which the server is connected to, just like you can see on the current Hyper-V Server.

The new server is on the network without problems. I am just interested as to why I am seeing these differences.

Please provide any suggestions that will be of help to me and which can assist me in resolving this.

Thanks in advance!

When trying to create a new virtual machine form failover clustering manager or Hyper-V manager i keep getting a message similar to the below.

The virtual disk and xml files are created but it can not seem to link iscsi controller to the virtual disk..

I tried the resolution here but it did not work: http://kazanas.com/hyper-v-account-does-not-have-sufficient-privilege-to-open-attachment/

Note the Virtual Machine ID that is listed in the "‘General access denied error’ (0x80070005)" error message.For example, consider the following error message:

In this example, the Virtual Machine ID is 5FC5C385-BD98-451F-B3F3-1E50E06EE663.

Dear reader,

We sometimes have a problem where our windows 2012 r2 RDS virtual servers, that reside on windows 2012r2 hyper-v hosts, loose their dynamic memory and only have their startup memory left to work with. Users start complaining that things are very slow etc.

If I check several screens (RDS Broker load balancing, hyper-v manager, cluster manager and the vm's task manager) it's clear that the vm only has its startup memory allocated. I'm not sure if this happens instantly or immidiatly after the nightly reboot. To resolve the problem we have to call all users on the vm where it happens and ask them to logoff (if they are even able to), and then we reboot the machine.

I have checked the logs from the machine where the VM resides on and the logs from the vm itself. But I cannot find anything. We also have alot of windows 2008r2 vm's with dynamivc memory, but none of those have ever had this problem.

Searched the internet, but so far it seems we are only.

Can anyone give me a lead to troubleshoot this?

Best regards,

Ruud Boersma

MCITP Enterprise administrator

Hi,

I am trying to carry out a planned failover in Hyper-v. Replication is working and there are no issues with that. When I right click the machine and select planned failover, i check the box "reverse the replication direction after failover" and the box "start the replica virtual machine after failover. The planned failover fails at the second step, "check replica virtual machine state" with a reason of "could not validate".

I am able to go to the replica server and do a "failover" but this would only be done in case the main server goes down. 

Anyone have any ideas? Thank you. I would have included an image but my account is not "validated" yet...

I've got a hyperV 2012 system with several VM's.  One of the VM's has thrown a BSOD a couple of times in the last month and I was wondering if the procedure for figuring out the cause is a little different under hyperV.

The BSOD I'm getting is a memory management bugcheck 1a.  The crash dumps don't show any "smoking guns":

Googling around for this issue points to memory HW problems in the computer but being a hyperV system with many other VM's active I don't see how that could be it.  The VM in question is a server 2008R2 in "terminal server" mode, fully patched. Nothing of note in the event logs and nothing (other than updates last month) was done on the server lately.

Any ideas on how I could proceed to track this down?  Thanks.

-- Al

I have two CSVs. One of my CSVs is low on space. I moved the VM to a different CSV. The original VM files were still on the CSV so I deleted them. The VM did not go to the Recycle Bin and I can't find it. The CSV reports no change on the amount of space. I performed this process form the owner of the CSV.

How do I reclaim the space?

I want to "clone" a virtual server and run it on the same host (2012R2)  and at the same time as the original.  I was under the impression that if I chose the "copy" option for the import which says it will create a new unique ID that the new virtual would be assigned a new SID but it does not.  I even tried creating a new machine and pointing it to my vhd file but that does not create a new sid either--no matter what, the new virtual always has the same SID as the server I exported in the beginning.  When the import wizard says it will create a "new ID" is it even referring to the SID ?  Also, I have seen blogs which say the SID doesn't even matter ??????

Call me confused.

There is a cluster of three nodes "Hyper-V Server 2012 R2» and virtual machines on it with the "Windows Server 2008 R2». I try to use "Performance Monitor" but one of the VM always displayed twice in "instances of selected object".
How I can fix it?

Sorry for Russian on screen. I have only this version of Windows.

I have a small lab network with a host machine running Server 2008R2 SP1 and three VM's each running Server 2008R2 SP1. Two of the VM's are DC's with a functional level of 2008.

I would like to upgrade everything to Server 2012R2 and was curious in what sequence I should approach this.  My plan is to shutdown all VM's and focus on upgrading the host to Server 2012R2.  I have read it is better to just create new Server 2012 DC's in Hyper V and migrate to them rather than trying to upgrade the existing 2008 DC's. 

Can someone point me in the direction of best practices for this?  Or does anyone have any experience with something similar?

Thanks.

Hi folks,

I have two Dell R-170 servers both running Server 2008 R2 and Hyper -V, each with two VM's installed and running.  One of the physical servers is beginning to run low on disk space.  I would like to move one of my VM's (about a 200Gb .vhd) from one server to another, so I will havce 3 VM's on one server and only one on the other at least temporarily.  Likely I will move a smaller one from the one machine to the other later on to balance them out.

Anyway, the VM I want to move is a SBS 2008 server, which is running Exchange and is the DC for the domain.  Any special considerations based upon that information?

I want to make sure I do the right steps to properly move that VM from one physical server to the other and have it come back online smoothly.  Can someone point me to the proper steps to take?  Here is what I think they are, but I'm not 100% sure.

Shutdown the VM on the current physical server.

Copy the VM's .vhd file to either an external drive or network copy to the new physical server.

Create the VM in Hyper-V on the new server, get the network configured  (Can you copy the settings from the old host?)

Boot the VM on the new server and it should work now?

Tell the VM on the old server to not restart except manually, then after verifying all is working well on the new host, delete the VM and the .vhd file to recapture disk space.

Can someone point me in the right direction to do this properly.  Since it's my DC and my Exchange server I really want to do this right the first time.

Thanks!