👍 From this video, you’ll learn how to configure data backup, create a backup copy and restore Windows Server to a previous condition, and how to recover information that could be lost if you have formatted the hard disk. 00:00 - Intro 01:56 - How to set up and configure backup for Windows Server 02:55 - How to create a backup of Windows Server 03:30 - Configure scheduled backup in Windows Server 05:11 - How to restore Windows Server from backup 06:38 - How to restore a crashed system (Windows Server) 07:29 - Recovering lost information from Windows Server with a data recovery tool 10:57 - Conclusion
Hi, I am trying to replace disks in RAID1 (PERC H330) 480 to 960. Windows Server 2019. I have created a recovery disk. I created a backup (almost 400GB). I have a backup on a USB drive and in a network directory. I'm turning off the server. I replace the disks, create an array, start Windows from the recovery disk. Troubleshoot, terminal - I give the command to start the network. I am unable to connect to the backup in the network directory. The network is working - ping OK. I provide the same path to which I make backups and the same login details (I checked 20 times). Ok, I'm trying to run it from a USB drive where I also have a backup. When I see the backup and click next (like in your video from 7:05) and the system wants to create a bootable disk, ATTENTION about CDRW! I don't have CDRW :). An attempt to start Windows from the recovery disk without indicating the backup takes about 2 hours and crashes around 93% - with short information - you cannot restore the system and the only option is quit. Do you know what I'm doing wrong?
It seems like you are experiencing some difficulties with the recovery process. Here are a few suggestions to help you troubleshoot the issue: Network Connection: Double-check the network connection settings on the recovery disk. Ensure that the network settings are correctly configured, including the IP address, subnet mask, gateway, and DNS server. Also, verify that the network share where the backup is stored is accessible and that the login credentials are correct. USB Drive Backup: If you are unable to access the backup from the network directory, try using the USB drive backup instead. Make sure that the USB drive is properly connected and recognized by the recovery disk. If you encounter any issues, try using a different USB port or a different USB drive. Bootable Disk Creation: If you encounter an error about CDRW when creating a bootable disk, it may be due to the recovery disk trying to access a CD/DVD drive that is not present. In this case, you can try creating the bootable disk on a different USB drive or using a different method, such as using a third-party tool to create a bootable USB drive. Recovery Process Failure: If the recovery process fails and the system cannot be restored, it could be due to various reasons, such as incompatible hardware, incorrect RAID configuration, or issues with the recovery disk. Ensure that the replacement disks are compatible with your RAID controller and that the RAID configuration is set up correctly. You may also try using a different recovery disk or contacting the manufacturer for further assistance.
@@HetmanRecovery Ok, tnx for reply. I spend 2 days, last weekend, for this problem. Tomorrow start next try :) I even installed a new system in the hope of restoring the old system from a system backup, but I only created a boot disk which also didn't work. The system shouted that there was another server - no information about software or hardware. I just change the disks to larger ones. Tell me, do you know whether the recovery disk should boot to 93% without indicating the backup location? There is only 6GB and it still takes 2 hours. It does not download data from the network or from a disk connected to USB. The windows recovery procedure is useless for me. What if my hardware fails and I want to recover the system on another machine? It's not possible? Last time windows is not a VM - last time!
![Megan Thee Stallion - Mamushi (Remix) [feat. TWICE] [Official Audio]](http://i.ytimg.com/vi/5c0_u9PsrsQ/mqdefault.jpg)
👍 From this video, you’ll learn how to configure data backup, create a backup copy and restore Windows Server to a previous condition, and how to recover information that could be lost if you have formatted the hard disk.
00:00 - Intro
01:56 - How to set up and configure backup for Windows Server
02:55 - How to create a backup of Windows Server
03:30 - Configure scheduled backup in Windows Server
05:11 - How to restore Windows Server from backup
06:38 - How to restore a crashed system (Windows Server)
07:29 - Recovering lost information from Windows Server with a data recovery tool
10:57 - Conclusion
Do you any possible way to boot a window 7 laptop without you making a bootable USB drive
Hi, I am trying to replace disks in RAID1 (PERC H330) 480 to 960. Windows Server 2019. I have created a recovery disk. I created a backup (almost 400GB). I have a backup on a USB drive and in a network directory. I'm turning off the server. I replace the disks, create an array, start Windows from the recovery disk. Troubleshoot, terminal - I give the command to start the network. I am unable to connect to the backup in the network directory. The network is working - ping OK. I provide the same path to which I make backups and the same login details (I checked 20 times). Ok, I'm trying to run it from a USB drive where I also have a backup. When I see the backup and click next (like in your video from 7:05) and the system wants to create a bootable disk, ATTENTION about CDRW! I don't have CDRW :). An attempt to start Windows from the recovery disk without indicating the backup takes about 2 hours and crashes around 93% - with short information - you cannot restore the system and the only option is quit. Do you know what I'm doing wrong?
It seems like you are experiencing some difficulties with the recovery process. Here are a few suggestions to help you troubleshoot the issue:
Network Connection: Double-check the network connection settings on the recovery disk. Ensure that the network settings are correctly configured, including the IP address, subnet mask, gateway, and DNS server. Also, verify that the network share where the backup is stored is accessible and that the login credentials are correct.
USB Drive Backup: If you are unable to access the backup from the network directory, try using the USB drive backup instead. Make sure that the USB drive is properly connected and recognized by the recovery disk. If you encounter any issues, try using a different USB port or a different USB drive.
Bootable Disk Creation: If you encounter an error about CDRW when creating a bootable disk, it may be due to the recovery disk trying to access a CD/DVD drive that is not present. In this case, you can try creating the bootable disk on a different USB drive or using a different method, such as using a third-party tool to create a bootable USB drive.
Recovery Process Failure: If the recovery process fails and the system cannot be restored, it could be due to various reasons, such as incompatible hardware, incorrect RAID configuration, or issues with the recovery disk. Ensure that the replacement disks are compatible with your RAID controller and that the RAID configuration is set up correctly. You may also try using a different recovery disk or contacting the manufacturer for further assistance.
@@HetmanRecovery Ok, tnx for reply. I spend 2 days, last weekend, for this problem. Tomorrow start next try :) I even installed a new system in the hope of restoring the old system from a system backup, but I only created a boot disk which also didn't work. The system shouted that there was another server - no information about software or hardware. I just change the disks to larger ones. Tell me, do you know whether the recovery disk should boot to 93% without indicating the backup location? There is only 6GB and it still takes 2 hours. It does not download data from the network or from a disk connected to USB. The windows recovery procedure is useless for me. What if my hardware fails and I want to recover the system on another machine? It's not possible? Last time windows is not a VM - last time!