The restore procedure for Veeam Backup & Replication v5 is really very simple, if you have suffered a system crash… as long as you have the correct files in place.<\/p>\n
I recently had this issue, I had Veeam Backup & Replication v5 installed on a virtual machine using the inbuilt SQL Server 2005 Express edition.\u00a0 The backups are stored locally on a separate disk but we do not backup the server as this would cause even larger backups.
\nThis server had some monthly Windows patches applied to it which, unfortunately, caused the Operating System to crash.\u00a0 After a while of attempting to recover the server, I decided to perform a rebuild of the server.\u00a0 This is the process I followed.<\/p>\n
The files that are required to recover the server are as follows:
\nOperating System Installation Files
\nVeeam Backup & Replication Installation Files
\nVeeam Backup & Replication License File
\nVeeamBackup.mdf database file
\nVeeamBackup.LDF database log file<\/p>\n
Looking down the requirements, you may think start to think that these are just standard items until you reach the requirement for the database files.\u00a0 With the Veeam installation to a SQL Server 2005 Express instance on the server, then the database files are stored on the C: drive with the SQL Server files… this then becomes a problem if the C: drive of the server is unable to boot.<\/p>\n
Database File Recovery<\/strong> System Recovery<\/strong> Once the Operating system has been installed, begin the installation of the Veeam Software from the installation files using the License file when requested.\u00a0 When asked about whether you wish to point to an existing database or install a new instance of SQL Server 2005 Express, select the option to install a new instance of SQL Server 2005 Express, we will use the old database later in our procedure.<\/p>\n Database Recovery<\/strong> Final Steps<\/strong> The restore procedure for Veeam Backup & Replication v5 is really very simple, if you have suffered a system crash… as long as you have the correct files in place. I recently had this issue, I had Veeam Backup & Replication v5 installed on a virtual machine using the inbuilt SQL Server 2005 Express edition.\u00a0 The backups are stored locally […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[8],"tags":[],"class_list":["post-40","post","type-post","status-publish","format-standard","hentry","category-veeam"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/posts\/40","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/comments?post=40"}],"version-history":[{"count":0,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/posts\/40\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/media?parent=40"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/categories?post=40"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.virtualworlduk.co.uk\/wordp\/wp-json\/wp\/v2\/tags?post=40"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nThe simplest recovery method for the database files is actually to, temporarily, add the old server C: drive to another virtual machine.\u00a0 This will then appear in the virtual machine as another drive.\u00a0 You can then browse through the files on the drive to find the VeeamBackup.mdf and VeeamBackup.LDF files.\u00a0 Once you have found the files, make a note of the files location and then copy the files to another location on the virtual machine where the disk is mounted.
\nOnce you are happy that the files have been copied across as expected then go and remove the previously added disk file from the virtual machine to return it back to normal.<\/p>\n
\nCreate a new virtual machine as you normally would and install the Operating System with the installation files.\u00a0 Perform any additional tasks that would normally be performed when building a new virtual machine in your environment, for example, joining the machine to your domain, install Antivirus software etc.<\/p>\n
\nThe next step is to replace the database files that have just been created during the installation procedure of the Veeam software.\u00a0 To be able to gain access to the database files, there are a couple of actions that need to be performed.\u00a0 The first task is to download the SQL Server 2005 Express Management Studio software from Microsoft, once you have downloaded this, perform an installation of the software.\u00a0 Whilst your file is downloading, go into the Windows Services area of the system and stop all Veeam services.
\nWith the SQL Server 2005 Express Management Studio installed, start up the application.\u00a0 Log onto the local SQL instance.\u00a0 Browse through to the VeeamBackup database.\u00a0 Right mouse click on the database and then click ‘Detach’.\u00a0 You will now be asked to confirm, make sure that all of the tick boxes on the confirmation screen are ticked, this will close down all current connections etc, and then accept the detach function.\u00a0 The database will now vanish from the list of databases.
\nBrowse to the location where the VeeamBackup files are stored and then rename the files.
\nBrowse to the virtual machine where the original VeeamBackup files were copied to, and copy them into the location when you just renamed the new database files.
\nGo back into the SQL Server 2005 Express Management Studio, right mouse click on the databases entry and then click ‘Attach’.\u00a0 Browse for the VeeamBackup.mdf file that you just copied onto the system.\u00a0 Accept the defaults to attach the database to the SQL Server.<\/p>\n
\nYou are now at the point that you can start up the Veeam services again.\u00a0 Once this is done, you can start up the Veeam console again.\u00a0 Please note that you will not be able to perform any backups at this point, this is due to the passwords for the vCenter servers will not exist on the new server.\u00a0 Right mouse click on the first vCenter server and then click ‘Edit’.\u00a0 You should see a tab for authentication, simply re-enter the password for the assigned user account and then click OK to accept.\u00a0 Repeat this process for any additional vCenter servers you have in your environment.\u00a0 You should now be able to go ahead and perform a test backup using the new Veeam installation.<\/p>\n","protected":false},"excerpt":{"rendered":"