Making sure enlarging the VM in settings is safe to do
I am running out of space on one of my VMs. It seems simple to just edit it and enlarge it. But, everything is fine, and I am not an expert working with VMs, so I would like some simple advice as to how to make the vM larger. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
We always like to have 20%-25% FREE.
Use Disk Management in Windows to resize the disk. (if it's windows)
Use Disk Management in Windows to resize the disk. (if it's windows)
ASKER
Thank you, yes it is Windows Server 2016 Standard on a 2019 Hyper-V.
Disk Management select volume Expand
why are you running on the replica?
Modify the source virtual machines drive not the replica (the changes will replicate over)
you will have to ensure that the host system drive and the backup repository have enough space first.
Other than the above.. expand the drive (if using thin provisioned it takes only seconds) and from the vm's OS disk management expand the drive.
This is a very safe procedure to use as long as the physical requirements are in place.. otherwise if you run out of space on the physical drive then the vm's on that drive will go into a saved condition and will not start until there is free physical drive space.
Modify the source virtual machines drive not the replica (the changes will replicate over)
you will have to ensure that the host system drive and the backup repository have enough space first.
Other than the above.. expand the drive (if using thin provisioned it takes only seconds) and from the vm's OS disk management expand the drive.
This is a very safe procedure to use as long as the physical requirements are in place.. otherwise if you run out of space on the physical drive then the vm's on that drive will go into a saved condition and will not start until there is free physical drive space.
ASKER
There is 3.5 TBs of space.
ASKER
@David,
Strange. After the production issue, I ran off a backup, then after fixing the production server, I replicated the backup. Once successful, a replication was made to failover to the production server.
It would be interesting to still run over the replication and yet watch more data being added to the RDS on the production server. If that were the case, then the backups of the production VMs wouldn't seem to be backing up the actual data.
I have a level 1 question out to Veeam along with a copy of the settings. I suppose it would be the line that states E:\replica\..... that would lead you to believe what you said. ??
Strange. After the production issue, I ran off a backup, then after fixing the production server, I replicated the backup. Once successful, a replication was made to failover to the production server.
It would be interesting to still run over the replication and yet watch more data being added to the RDS on the production server. If that were the case, then the backups of the production VMs wouldn't seem to be backing up the actual data.
I have a level 1 question out to Veeam along with a copy of the settings. I suppose it would be the line that states E:\replica\..... that would lead you to believe what you said. ??
ASKER
@David,
Interesting that you picked up on the name of the .vhdx. It got me to worrying. I know that I made a replication, then changed it to replica. I then did a permanent failover. So, I should be running on the production VMs and not the replica. Just to be sure, Veeam asked to remote in to look around. Veeam did see the .vhdx, but after snooping around a bit, determined I was not running from the replica. The original Veeam tech who helped me with the replica and failover has been notified by Veeam, so he can help figure out the conflict.
Interesting that you picked up on the name of the .vhdx. It got me to worrying. I know that I made a replication, then changed it to replica. I then did a permanent failover. So, I should be running on the production VMs and not the replica. Just to be sure, Veeam asked to remote in to look around. Veeam did see the .vhdx, but after snooping around a bit, determined I was not running from the replica. The original Veeam tech who helped me with the replica and failover has been notified by Veeam, so he can help figure out the conflict.
I then did a permanent failover. I would move the VM into your hyper-v hierarchy just to satisfy my OCD
ASKER
Every computer and when you directly open RDS is accessing RDS. Yet, on the individual computers it is referred to as the C: drive?
How far do you need to get down on size remaining before it affects the performance.