Thread

1. Windows XP to Win 10 migration issue

   Dale Seaburg <kg5lt@verizon.net> — 2017-12-09T16:11:42Z

   I have a database in Windows XP (old PC), postgresql 8.4.5 which needs 
   to be migrated to Windows 10 Pro (new PC).
   
   Now, for the bad news, the XP PC, when I powered down, before doing any 
   backup or database unload, would not power back up.  I will be 
   attempting to get the PC fixed for that.  In the meantime, I removed the 
   old PC HD, installing in a SATA to USB box and I installed the same 
   version of Postgresql (8.4.5) on the Win 10 machine, thinking I could 
   simply copy the data folder from the XP's HD to the Win 10's HD into the 
   appropriate folder (C:/.../8.4.5/).  I did the copy of the data folder, 
   after renaming the new, unused data folder to preserve it).  I stopped 
   the postgres service, made the copy, and attempted to restart the 
   postgres service.  No Go!  Would not start.  As a double-check, I 
   renamed the copied data folder to something else and renamed the 
   preserved data folder back to it's original name, and the service 
   restarted just fine.
   
   So, without being able to backup or unload (dump?) the original database 
   on the original PC, what would be the best way to move data to the new 
   PC?  Or, IS there any way to do this, without reviving the old XP, PC?
   
   Dale
   
   
   

2. Re: Windows XP to Win 10 migration issue

   Scott Mead <scottm@openscg.com> — 2017-12-09T21:03:46Z

   
   > On Dec 9, 2017, at 11:11, Dale Seaburg <kg5lt@verizon.net> wrote:
   > 
   > I have a database in Windows XP (old PC), postgresql 8.4.5 which needs to be migrated to Windows 10 Pro (new PC).
   > 
   > Now, for the bad news, the XP PC, when I powered down, before doing any backup or database unload, would not power back up.  I will be attempting to get the PC fixed for that.  In the meantime, I removed the old PC HD, installing in a SATA to USB box and I installed the same version of Postgresql (8.4.5) on the Win 10 machine, thinking I could simply copy the data folder from the XP's HD to the Win 10's HD into the appropriate folder (C:/.../8.4.5/).  I did the copy of the data folder, after renaming the new, unused data folder to preserve it).  I stopped the postgres service, made the copy, and attempted to restart the postgres service.  No Go!  Would not start.  As a double-check, I renamed the copied data folder to something else and renamed the preserved data folder back to it's original name, and the service restarted just fine.
   > 
   > So, without being able to backup or unload (dump?) the original database on the original PC, what would be the best way to move data to the new PC?  Or, IS there any way to do this, without reviving the old XP, PC?
   
   I’m guessing that the old machine was 32 but and the New is 64?  They have to match. You could always setup a 32 bit VM. It must be 32 bit windows (if that’s what the original was ) 
   
   
   > 
   > Dale
   > 
   
   
   

3. Re: Windows XP to Win 10 migration issue

   John R Pierce <pierce@hogranch.com> — 2017-12-09T21:55:33Z

   On 12/9/2017 1:03 PM, Scott Mead wrote:
   > I’m guessing that the old machine was 32 but and the New is 64?  They have to match. You could always setup a 32 bit VM. It must be 32 bit windows (if that’s what the original was )
   
   you should be able to run 32 bit postgresql on 64 bit windows.
   
   its a bit trickier than just the same version, however...  they should 
   be from the same distribution too... a version built with GCC and Cygwin 
   might not be binary compatible with a version built with Microsoft 
   Visual C (such as the EnterpriseDB versions) due to differences in 
   runtime libraries.
   
   
   -- 
   john r pierce, recycling bits in santa cruz
   
   
   
   

4. Re: Windows XP to Win 10 migration issue

   Vincent Veyron <vv.lists@wanadoo.fr> — 2017-12-11T13:37:39Z

   On Sat, 9 Dec 2017 10:11:42 -0600
   Dale Seaburg <kg5lt@verizon.net> wrote:
   
   >   No Go!  Would not start. 
   
   Any error message in your logs?
   
   I would certainly second Scott's suggestion to check the processors. I've had to do what you describe once, and it took me four machines before I got one that would start postgresql with my rescued data folder.
   
   You might have better luck finding an old XP machine similar to your deceased one, installing postgresql on it, and using that to start your cluster.
   
   
   -- 
   					Bien à vous, Vincent Veyron 
   https://marica.fr/
   Logiciel de gestion des sinistres assurances, des dossiers contentieux et des contrats pour le service juridique
   
   
   

5. Re: Windows XP to Win 10 migration issue

   Moreno Andreo <moreno.andreo@evolu-s.it> — 2017-12-12T10:14:28Z

   Il 11/12/2017 14:37, Vincent Veyron ha scritto:
   > On Sat, 9 Dec 2017 10:11:42 -0600
   > Dale Seaburg <kg5lt@verizon.net> wrote:
   >
   >>    No Go!  Would not start.
   > Any error message in your logs?
   >
   > I would certainly second Scott's suggestion to check the processors. I've had to do what you describe once, and it took me four machines before I got one that would start postgresql with my rescued data folder.
   >
   > You might have better luck finding an old XP machine similar to your deceased one, installing postgresql on it, and using that to start your cluster.
   >
   >
   I'd take a peek into logs (maybe EventLog), it happened to me that the 
   postgres user in windows 10 did not have the permission to access data 
   directory. Setting the right permissions could make it start. Obviously 
   the processor architecture (32/64 bit) must be honored.
   
   My 2 cent