Hi All,
Just a quick question - I know the recommended route for XP is via P2V and backing up with Veeam Agent.
But this is not something I can do easily I am afraid. Also this is something that needs to be done infrequently - Perhaps once every year or 2.
- Can I not just take my XP System hard drive and place it into an Windows 10 workstation as a second HD.
- Then back up that volume with Veeam Agent.... Swap hard drive (ideally SSD) and then restore the image to the new drive.
Doing this for manufacturing systems stuck on XP that cannot be updated due to proprietary software etc.
Thanks for your help and advice.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 24, 2018 11:34 am
- Full Name: Paul Murphy
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Working around the XP issue
Hello,
Thank you!
I guess you meant to say to back up it with Veeam Backup & Replication (agentless), since Veeam Agent does not support Windows XP.BackedDown wrote:I know the recommended route for XP is via P2V and backing up with Veeam Agent.
This should, indeed, help you to protect the application data, so in the DR situation you should re-build the XP machine and then restore application data from the volume backup.BackedDown wrote:- Can I not just take my XP System hard drive and place it into an Windows 10 workstation as a second HD.
- Then back up that volume with Veeam Agent.... Swap hard drive (ideally SSD) and then restore the image to the new drive.
Since you cannot upgrade the OS, have you considered just virtualizing this server?BackedDown wrote:Doing this for manufacturing systems stuck on XP that cannot be updated due to proprietary software etc.
Thank you!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Sep 24, 2018 11:34 am
- Full Name: Paul Murphy
- Contact:
Re: Working around the XP issue
Thanks for your reply - much appreciated.
Its an XP workstation running a CNC machine so cannot virtualise unfortuantely.
I was hoping place the existing XP OS hard drive in a windows 10 workstation and then using Veeam Agent backup the disk and then do a full restore and in effect end up with two fully booting disks - one a clone of the other.
Is this the case?
Its an XP workstation running a CNC machine so cannot virtualise unfortuantely.
I was hoping place the existing XP OS hard drive in a windows 10 workstation and then using Veeam Agent backup the disk and then do a full restore and in effect end up with two fully booting disks - one a clone of the other.
Is this the case?
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Working around the XP issue
Hi Paul,
This would not allow you to boot from this volume, since this disk will be marked as "not used during the boot process" due to the fact that you've attached it to another computer as a regular disk (running Win 10). In this case you will only be able to back up application data.
Thanks!
This would not allow you to boot from this volume, since this disk will be marked as "not used during the boot process" due to the fact that you've attached it to another computer as a regular disk (running Win 10). In this case you will only be able to back up application data.
Thanks!
Who is online
Users browsing this forum: No registered users and 14 guests