Backup Procedures - Revision history

KDurovka: spelling and server name

2024-04-25T17:40:53Z

spelling and server name

Kwalters at 20:13, 16 September 2022

2022-09-16T20:13:28Z

← Older revision		Revision as of 20:13, 16 September 2022
Line 77:		Line 77:
	===Server Backup Information===		===Server Backup Information===
	This process will be followed every week we are in session to make sure that all of our backups are properly configured. With our current NAS setup, we have created a script that run every week that schedules weekly backups. Backups will start at 9pm on their set day of the week.		This process will be followed every week we are in session to make sure that all of our backups are properly configured. With our current NAS setup, we have created a script that run every week that schedules weekly backups. Backups will start at 9pm on their set day of the week.
	===~~<big>~~Schedule~~</big>~~===
			=== Schedule ===
	Server Backups only happen once a week at 9:00PM		Server Backups only happen once a week at 9:00PM

Line 91:		Line 92:
	*surtr - SURTR_Backup		*surtr - SURTR_Backup
	*freyr - freyr_Backup		*freyr - freyr_Backup
	===~~<big>~~Creating Backups~~</big>~~===
			=== Creating Backups ===
	Remote desktop into the server you need to backup.*[http://wiki.24pin.tech/index.php?title=Loki Loki] - 10.21.25.3		Remote desktop into the server you need to backup.*[http://wiki.24pin.tech/index.php?title=Loki Loki] - 10.21.25.3

Line 107:		Line 109:
	# Check throughout the day to make sure the scheduled backup is working properly.		# Check throughout the day to make sure the scheduled backup is working properly.

	===~~<big>~~Restoration~~</big>~~===		=== '''Restoration''' ===
	This is the process to restore from a backup. Windows Server must be able to boot and access the backup program. You can reinstall Windows Server and then use the backup program on the new install to restore.		This is the process to restore from a backup. Windows Server must be able to boot and access the backup program. You can reinstall Windows Server and then use the backup program on the new install to restore.

Line 117:		Line 119:
	# Specify your final recovery options, which will depend on which type of recovery and what items you want to recover.		# Specify your final recovery options, which will depend on which type of recovery and what items you want to recover.
	# Confirm, and ensure the recovery worked properly by ensuring full system functionality.		# Confirm, and ensure the recovery worked properly by ensuring full system functionality.

	~~===<big>Troubleshooting</big>===~~
	===Cannot find specified route===		===Cannot find specified route===
	If Windows Server Backup gives you an error about the backup not being able to reach the specified remote folder, it means the NAS has disconnected from the NAS server and needs to be reconnected to Active Directory.		If Windows Server Backup gives you an error about the backup not being able to reach the specified remote folder, it means the NAS has disconnected from the NAS server and needs to be reconnected to Active Directory.

Kwalters at 20:12, 16 September 2022

2022-09-16T20:12:29Z

@@ Line 75: / Line 75: @@
 <code>0 0 1 * * rsync -e 'ssh -p 22' -avp /images/ 10.21.25.13:/mnt/user0/Backups/Fog_Images/</code>
 ==Old manual back up procedures==
-[[Server Backup (manually)]]
+===Server Backup Information===
+#

Kwalters: /* Automatic Rsync */

2022-09-15T21:34:22Z

Automatic Rsync

← Older revision		Revision as of 21:34, 15 September 2022
Line 49:		Line 49:

	Step Four; Verify full system functionality as any good technician in 24PinTech should, and then your task should be complete.		Step Four; Verify full system functionality as any good technician in 24PinTech should, and then your task should be complete.
	==How to back up Fog images==		==How to back up Fog images (automatic)==
	====Installing ~~Rsync~~====		====Installing rsync====
	~~Go to 10.21.25.2 and login to esxi with your id and password. Then go to~~ fog and log into the console with the admin account. Open the terminal and run the following command to install rsync. We need to run this command as sudo to grant the user the same security privileges as the superuser.		Access fog and log into the console with the admin account. Open the terminal and run the following command to install rsync. We need to run this command as sudo to grant the user the same security privileges as the superuser.

	<code>sudo apt install rsync</code>		<code>sudo apt install rsync</code>
	====Checking ~~For Ssh Keys~~====		====Checking/creating ssh keys====
	To automate these backups, we need to be able to login without a password by creating ssh keys. First, you should check if these already keys exist using the following command.		To automate these backups, we need to be able to login without a password by creating ssh keys. First, you should check if these already keys exist using the following command.

	<code>ls -al ~/.ssh/id_*.pub</code>		<code>ls -al ~/.ssh/id_*.pub</code>
	~~====Creating Ssh Keys====~~
	If the keys don't exist, they should be created using the following command. When prompted for a password press enter to set it to no password. ~~(just hit enter at the prompt don't type anything)~~		If the keys don't exist, they should be created using the following command. When prompted for a password press enter to set it to no password.

	<code>ssh -keygen -t rsa</code>		<code>ssh -keygen -t rsa</code>

	This key also needs to be on the destination so the key should be copied to ~~Unraid~~.		This key also needs to be on the destination so the key should be copied to Midgard using the following command.

	<code>ssh-copy-id -i ~/.ssh/id_rsa.pub root@10.21.25.13</code>		<code>ssh-copy-id -i ~/.ssh/id_rsa.pub root@10.21.25.13</code>
	====Automatic ~~Rsync~~====		====Automatic backups====
	To automate ~~rsync~~, we need to use cron and create a cronjob.		To automate backups, we need to use cron and create a cronjob.

	<code>crontab -e</code>		<code>crontab -e</code>

	We want it to run once a month so we will set beginning part of the command to run monthly. The first ~~part~~ represents the minute, second is hour, third is day, fourth is month, and fifth is day of the week.		We want it to run once a month so we will set beginning part of the command to run monthly. The first number represents the minute, second is hour, third is day, fourth is month, and fifth is day of the week. We also need to add the rsync command after to backup up the fog images to the backups folder on Midgard. This will now backup the fog images at the beginning of every month.

	~~<code>MM HH DD MTMT DAY command</code>~~

	~~Once we change it to monthly, we~~ need to add the rsync command after~~. This command will use rsync~~ to backup up the fog images to the backups folder on ~~Unraid~~.

	<code>0 0 1 * * rsync -e 'ssh -p 22' -avp /images/ 10.21.25.13:/mnt/user0/Backups/Fog_Images/</code>		<code>0 0 1 * * rsync -e 'ssh -p 22' -avp /images/ 10.21.25.13:/mnt/user0/Backups/Fog_Images/</code>

	~~This will now backup the fog images at the beginning of every month.~~
	==Old manual back up procedures==		==Old manual back up procedures==
	[[Server Backup (manually)]]		[[Server Backup (manually)]]

	#		#

Kwalters at 20:33, 15 September 2022

2022-09-15T20:33:34Z

@@ Line 49: / Line 49: @@
 Step Four; Verify full system functionality as any good technician in 24PinTech should, and then your task should be complete.
-==How to back up Logan_Web (10.21.25.11) automatically    DO NOT PREFORM THIS IT WILL BREAK THE SHARE==
+<code>sudo apt install rsync</code>
-we use a program called [https://www.linux.com/training-tutorials/get-know-rsync/ rsync] and to use [https://www.linux.com/training-tutorials/get-know-rsync/ rsync] we first need ssh rsa authentication for [https://www.linux.com/training-tutorials/get-know-rsync/ rsync] to work to do that follow this process [http://www.linuxproblem.org/art_9.html here]
+====Checking For Ssh Keys====
 ==Old manual back up procedures==
 [[Server Backup (manually)]]
+#

Cliermann: /* Automated Backups */

2022-01-24T19:47:34Z

Automated Backups

← Older revision		Revision as of 19:47, 24 January 2022
Line 14:		Line 14:

	===Automated Backups===		===Automated Backups===
	The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the ~~classroom~~ called "my passport")		The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the server called "my passport")
	Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”		Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”
	This can also be ran manually via the task scheduler.		This can also be ran manually via the task scheduler.

Cburanich: /* Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually */

2022-01-07T20:30:12Z

Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually

← Older revision		Revision as of 20:30, 7 January 2022
Line 1:		Line 1:

	==~~Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”How~~ to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually==		==How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually==
	This is how we back up our two Windows servers to an external drive.		This is how we back up our two Windows servers to an external drive.

Line 15:		Line 15:
	===Automated Backups===		===Automated Backups===
	The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the classroom called "my passport")		The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the classroom called "my passport")

	Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”		Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”
	This can also be ran manually via the task scheduler.		This can also be ran manually via the task scheduler.

Cburanich: /* Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually */

2022-01-07T20:29:15Z

Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually

← Older revision		Revision as of 20:29, 7 January 2022
Line 14:		Line 14:

	===Automated Backups===		===Automated Backups===
	The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the classroom called "my passport") ~~<blockquote>~~Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”~~</blockquote>~~		The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the classroom called "my passport")

			Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”
	This can also be ran manually via the task scheduler.		This can also be ran manually via the task scheduler.

Cburanich: /* Automated (W.I.P) */

2022-01-07T20:28:51Z

Automated (W.I.P)

← Older revision		Revision as of 20:28, 7 January 2022
Line 1:		Line 1:

	==~~How~~ to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually==		==Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually==
	This is how we back up our two Windows servers to an external drive.		This is how we back up our two Windows servers to an external drive.

Line 13:		Line 13:
	#For Friia do the exact same process.		#For Friia do the exact same process.

	===Automated ~~(W.I.P)~~===		===Automated Backups===
	schedule, a single manual backup, or to recover a backup. From here you can choose to do a manual backup. To do a weekly automatic backup follow this guide [https://www.ubackup.com/windows-server/windows-server-backup-once-a-week-6988.html here] . Alternatively there is an easer way doing it through command prompt The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00.''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume ~~'''''I:'''.~~ (~~of course these variables are interchangeable to~~ the ~~users liking~~)~~'' ([https://techcommunity.microsoft.com/t5/storage-at-microsoft/customizing-windows-server-backup-schedule/ba-p/423808 Source])~~		The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the classroom called "my passport") <blockquote>Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”</blockquote>
	~~''SCHTASKS~~ /Create /SC ~~WEEKLY~~ /~~D '''<Day Of Week> '''~~/~~TN '''<TaskName> '''~~/~~RL HIGHEST~~ /~~ST '''~~<~~StartTime> '''~~/~~TR '''<Windows Server Backup Command~~>~~'''''~~

	''SCHTASKS /Create /SC WEEKLY /D '''SAT '''/TN '''WeeklySystemStateBackup '''/RL HIGHEST /ST '''19:00 '''/TR "WBADMIN START SYSTEMSTATEBACKUP -backupTarget: '''I: '''-quiet >> C:backupLogs.txt "''
	This can also be ran manually via the task scheduler.		This can also be ran manually via the task scheduler.

Cliermann: /* How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually */

2022-01-07T20:13:48Z

How to back up Odin (10.21.25.3) and Friia (10.21.25.4) manually

← Older revision		Revision as of 20:13, 7 January 2022
Line 11:		Line 11:
	#The Snap-in on the left has the option to to perform "Local Backup" the snap in on the right has an option to backup select it and go through the menu that pops up and select the following options "Backup Once, Different options, Full server, local drive select "my passport" and hit backup.		#The Snap-in on the left has the option to to perform "Local Backup" the snap in on the right has an option to backup select it and go through the menu that pops up and select the following options "Backup Once, Different options, Full server, local drive select "my passport" and hit backup.
	#After backup is finished go back to 10.21.25.2 and click on Odin then "Edit" and press the small x next to the hard drive. Put the hard drive in chamberlains desk when you are finished.		#After backup is finished go back to 10.21.25.2 and click on Odin then "Edit" and press the small x next to the hard drive. Put the hard drive in chamberlains desk when you are finished.
	#For Friia do the exact same process ~~but replace "10.21.25.2" with "10.21.25.7" and replace all mentions of Odin with Friia~~.		#For Friia do the exact same process.

	===Automated (W.I.P)===		===Automated (W.I.P)===

← Older revision		Revision as of 17:40, 25 April 2024
Line 1:		Line 1:

	==How to back up ~~Odin~~ (10.21.25.3) and Friia (10.21.25.4) manually==		==How to back up Fenrir(10.21.25.3) and Friia (10.21.25.4) manually==
	This is how we back up our two Windows servers to an external drive.		This is how we back up our two Windows servers to an external drive.

	#Get the external drive labelled "server backups" from the middle drawer on the left of chamberlains desk.		#Get the external drive labelled "server backups" from the middle drawer on the left of chamberlains desk.
	#Take the drive into the back room and remove the guard on the server labelled Valhalla and plug the drive into the right ~~usb~~ port.		#Take the drive into the back room and remove the guard on the server labelled Valhalla and plug the drive into the right USB port.
	#On a computer in the classroom use chrome and type "10.21.25.2" into the address bar. The log in for ~~esxi~~ is the same for your log in for class. (Server Admin accounts only)		#On a computer in the classroom use chrome and type "10.21.25.2" into the address bar. The log in for ESXI is the same for your log in for class. (Server Admin accounts only)
	#Go to virtual machines and click on "Odin" click on "Edit" and click on "Add other device" and then "USB device" select Western Digital My Passport 25E2. Press save and click on the window of the virtual machine to be taken to Odins desktop.		#Go to virtual machines and click on "Odin" click on "Edit" and click on "Add other device" and then "USB device" select Western Digital My Passport 25E2. Press save and click on the window of the virtual machine to be taken to Odins desktop.
	#Click on "Actions" and then "Guest OS" "Send Keys" and "ctrl-alt-del" and log in using your profile in class. (Server Admin accounts only)		#Click on "Actions" and then "Guest OS" "Send Keys" and "ctrl-alt-del" and log in using your profile in class. (Server Admin accounts only)
	#Use the start menu and type "Windows Server Backup" open it.		#Use the start menu and type "Windows Server Backup" open it.
	#The Snap-in on the left has the option to to perform "Local Backup" the snap in on the right has an option to backup select it and go through the menu that pops up and select the following options "Backup Once, Different options, Full server, local drive select "my passport" and hit backup.		#The Snap-in on the left has the option to to perform "Local Backup" the snap in on the right has an option to backup select it and go through the menu that pops up and select the following options "Backup Once, Different options, Full server, local drive select "my passport" and hit backup.
	#After backup is finished go back to 10.21.25.2 and click on Odin then "Edit" and press the small x next to the hard drive. Put the hard drive in chamberlains desk when you are finished.		#After backup is finished go back to 10.21.25.2 and click on Odin then "Edit" and press the small x next to the hard drive. Put the hard drive in chamberlains desk when you are finished.
	#For Friia do the exact same process.		#For Friia do the exact same process.

	===Automated Backups===		===Automated Backups===
	The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the server called "my passport")		The following command will create a Task Scheduler task named '''''WeeklySystemStateBackup''''' that runs every Saturday ( '''''SAT''''' ) at '''''19:00 (7 pm).''''' This task will run ''WEEKLY'' with the ''HIGHEST'' privileges. It will run the Windows Server Backup CLI to backup ''SYSTEMSTATEBACKUP'' to target volume "E" (Volume E is a physical hard drive in the back on the server called "my passport")
	Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”		Schtasks /Create /SC weekly /D SAT /TN WeeklySystemsStateBackup /ST 19:00 /TR “wbadmin start systemstatebackup -backupTarget: E:”
	This can also be ran manually via the task scheduler.		This can also be ran manually via the task scheduler.

	==Restore Windows Server Backup on ESXi==		==Restore Windows Server Backup on ESXi==
	The following process was used to restore a backup of our production server Odin which is a active directory server with DNS, DHCP, Print, and other services. In the process you will have to use DRSM (Directory Service Restore Mode) if you are trying to restore a server running Active Directory because if you try in normal Windows mode you'll encounter an error. The restored version of the VM may encounter some errors you may have to fix but it should sort itself out. This may be just because you are restoring an older machine so whatever it's running that's synced may get confused. The following steps guide you through this process:		The following process was used to restore a backup of our production server Odin which is a active directory server with DNS, DHCP, Print, and other services. In the process you will have to use DRSM (Directory Service Restore Mode) if you are trying to restore a server running Active Directory because if you try in normal Windows mode you'll encounter an error. The restored version of the VM may encounter some errors you may have to fix but it should sort itself out. This may be just because you are restoring an older machine so whatever it's running that's synced may get confused. The following steps guide you through this process:

	#Grab a backup of the Windows Server you are trying to restore		#Grab a backup of the Windows Server you are trying to restore
	#Go to one of our ESXi machines and create a new VM with the necessary requirements for the machine you want to restore. In our case we are trying to restore a Windows Server 2019 Domain Controller so we gave it 100 GB of storage, 4 CPUs, and 8 GB of memory.		#Go to one of our ESXi machines and create a new VM with the necessary requirements for the machine you want to restore. In our case we are trying to restore a Windows Server 2019 Domain Controller so we gave it 100 GB of storage, 4 CPUs, and 8 GB of memory.
Line 32:		Line 28:
	#The restoration process should start and once done the computer will have to restart, it will restart into DRSM. You’ll have to go back into msconfig and uncheck the safe mode option and restart the computer again.		#The restoration process should start and once done the computer will have to restart, it will restart into DRSM. You’ll have to go back into msconfig and uncheck the safe mode option and restart the computer again.
	#The computer should reboot into the restored version of the machine, there may be some errors or active directory issues but those should sort themselves out. This is just because you are restoring an older version of a machine and the active directory is confused.		#The computer should reboot into the restored version of the machine, there may be some errors or active directory issues but those should sort themselves out. This is just because you are restoring an older version of a machine and the active directory is confused.

	==How to back up Logan_Web (10.21.25.11) Manually==		==How to back up Logan_Web (10.21.25.11) Manually==
	Step One; The first and most essential step to backing up Logan_Web onto the Fog server is to register it to the Fog server itself, in order to be able to perform the process. If not already completed, this can be performed by doing a full host registration. Begin this by logging into the Fog server (http://10.21.25.29/fog) and selecting the 'Images' tab. Create a new image, and name it accordingly to what is required. Once completed, you're going to find Logan and select it. Before booting into the device, make sure to head into the 'Actions' tab near the top and choose to Edit settings. On the first tab, the Virtual Hardware, make sure that the ability to connect with the NIC is available; as this is how we'll be PXI booting. Then, head into the VM settings and expand the 'Boot Options' category. Scroll for just a moment and select the option to force the device to boot into BIOS. Once accomplished, go into the boot settings of the BIOS and move 'Ethernet' to the top of the list. Continue the booting process, and do not forget to rearrange the Boot Order at a later date. Once you are prompted with a menu, select 'Full Host Registration'		Step One; The first and most essential step to backing up Logan_Web onto the Fog server is to register it to the Fog server itself, in order to be able to perform the process. If not already completed, this can be performed by doing a full host registration. Begin this by logging into the Fog server (http://10.21.25.29/fog) and selecting the 'Images' tab. Create a new image, and name it accordingly to what is required. Once completed, you're going to find Logan and select it. Before booting into the device, make sure to head into the 'Actions' tab near the top and choose to Edit settings. On the first tab, the Virtual Hardware, make sure that the ability to connect with the NIC is available; as this is how we'll be PXI booting. Then, head into the VM settings and expand the 'Boot Options' category. Scroll for just a moment and select the option to force the device to boot into BIOS. Once accomplished, go into the boot settings of the BIOS and move 'Ethernet' to the top of the list. Continue the booting process, and do not forget to rearrange the Boot Order at a later date. Once you are prompted with a menu, select 'Full Host Registration'
Line 40:		Line 35:
	logging into the Fog server (http://10.21.25.29/fog) and selecting the 'Hosts' tab. Search this list of servers for 'dev_logan', as this is the server we're going to be backing up. Select the 'Capture' option on 'dev_logan', and once completed, the next time that Logan is PXI booted through ethernet it'll be automatically pulled and backed up.		logging into the Fog server (http://10.21.25.29/fog) and selecting the 'Hosts' tab. Search this list of servers for 'dev_logan', as this is the server we're going to be backing up. Select the 'Capture' option on 'dev_logan', and once completed, the next time that Logan is PXI booted through ethernet it'll be automatically pulled and backed up.

	Step Two; Once this request to pull the image from Logan has gone through, the next step is to boot into Logan to perform the backup. Head to https://10.21.25.8/ui/#/login and logon to the ESXi device. Once completed, you're going to find Logan again and select it. Before booting into the device, make sure to head into the 'Actions' tab near the top and choose to Edit settings. On the first tab, the Virtual Hardware, make sure that the ability to connect with the NIC is available; as this is how we'll be PXI booting. Then, head into the VM settings and expand the 'Boot Options' category. Scroll for just a moment and select the option to force the device to boot into BIOS.		Step Two; Once this request to pull the image from Logan has gone through, the next step is to boot into Logan to perform the backup. Head to https://10.21.25.8/ui/#/login and logon to the ESXi device. Once completed, you're going to find Logan again and select it. Before booting into the device, make sure to head into the 'Actions' tab near the top and choose to Edit settings. On the first tab, the Virtual Hardware, make sure that the ability to connect with the NIC is available; as this is how we'll be PXI booting. Then, head into the VM settings and expand the 'Boot Options' category. Scroll for just a moment and select the option to force the device to boot into BIOS.

	Step Three; When ready		Step Three; When ready
Line 65:		Line 60:
	This key also needs to be on the destination so the key should be copied to Midgard using the following command.		This key also needs to be on the destination so the key should be copied to Midgard using the following command.

	<code>ssh-copy-id -i ~/.ssh/id_rsa.pub ~~root@10.21.25.13~~</code>		<code>ssh-copy-id -i ~/.ssh/id_rsa.pub [/cdn-cgi/l/email-protection <nowiki>[email protected]</nowiki>]</code>
	====Automatic backups====		====Automatic backups====
	To automate backups, we need to use cron and create a cronjob.		To automate backups, we need to use cron and create a cronjob.
Line 77:		Line 72:
	===Server Backup Information===		===Server Backup Information===
	This process will be followed every week we are in session to make sure that all of our backups are properly configured. With our current NAS setup, we have created a script that run every week that schedules weekly backups. Backups will start at 9pm on their set day of the week.		This process will be followed every week we are in session to make sure that all of our backups are properly configured. With our current NAS setup, we have created a script that run every week that schedules weekly backups. Backups will start at 9pm on their set day of the week.

	=== Schedule ===		=== Schedule ===
	Server Backups only happen once a week at 9:00PM		Server Backups only happen once a week at 9:00PM
Line 92:		Line 86:
	*surtr - SURTR_Backup		*surtr - SURTR_Backup
	*freyr - freyr_Backup		*freyr - freyr_Backup

	=== Creating Backups ===		=== Creating Backups ===
	Remote desktop into the server you need to backup.*[http://wiki.24pin.tech/index.php?title=Loki Loki] - 10.21.25.3		Remote desktop into the server you need to backup.*[http://wiki.24pin.tech/index.php?title=Loki Loki] - 10.21.25.3

	*[http://wiki.24pin.tech/index.php?title=Logan Logan] - 10.21.25.10		*[http://wiki.24pin.tech/index.php?title=Logan Logan] - 10.21.25.10

Line 101:		Line 93:
	*freyr - 10.21.25.5		*freyr - 10.21.25.5
	Backup steps:		Backup steps:

	# To use remote desktop click the windows button and search, or use windows + r and run mstsc.exe.		# To use remote desktop click the windows button and search, or use windows + r and run mstsc.exe.
	# On the server manager, click tools and search for Windows Server Backup. (if it's not there you may need to install the feature.)		# On the server manager, click tools and search for Windows Server Backup. (if it's not there you may need to install the feature.)
Line 108:		Line 99:
	# Continue through setup and complete backup.		# Continue through setup and complete backup.
	# Check throughout the day to make sure the scheduled backup is working properly.		# Check throughout the day to make sure the scheduled backup is working properly.

	=== '''Restoration''' ===		=== '''Restoration''' ===
	This is the process to restore from a backup. Windows Server must be able to boot and access the backup program. You can reinstall Windows Server and then use the backup program on the new install to restore.		This is the process to restore from a backup. Windows Server must be able to boot and access the backup program. You can reinstall Windows Server and then use the backup program on the new install to restore.

	# Open Windows Server Backup and click "Recover..." on the right pane.		# Open Windows Server Backup and click "Recover..." on the right pane.
	# Choose the option for "A backup stored on another location" and click next. Then choose shared folder.		# Choose the option for "A backup stored on another location" and click next. Then choose shared folder.
Line 123:		Line 112:

	'''Solution:'''		'''Solution:'''

	# Login to the NAS by going to 10.21.25.16 in a browser, and logging in as an admin.		# Login to the NAS by going to 10.21.25.16 in a browser, and logging in as an admin.
	# Navigate the options at the top until you find the settings button.		# Navigate the options at the top until you find the settings button.