02-21-2018 07:05 AM
Hi,
Anyone in this forum that has been able to migrate BE16.2 with deduplication Storage folder from win2012R2 to win2016.
I follow same procedure as when I migrate from win 2012R2 to Win2012R.
On the new Win 2016 server I am unable to recreate the Deduplication Storage Folder.
Solved! Go to Solution.
02-26-2018 12:37 AM
Hi,
Problem is now solved.
Microsoft does a change in Locals (region and language) going from Windows 2012 to Windows 2016. This affects the Postgresql database.
I used Microsoft Local builder and created new locals based on the win2012 version.
I installed the new locals on windows 2016 server and the postgresql service started successfully.
Thank's for your help in this issue.
Regards
Leif
02-21-2018 08:06 AM
02-21-2018 11:42 PM
hi,
I have confirmed pw is correct.
Same scenario moving BE dedup to win2012R2 server works fine.
02-21-2018 11:44 PM
were you able to check the pdde-config.log
02-22-2018 08:45 AM
hi,
Yes,
21.02.2018 21.31.11,44 PostgreSQL is starting, but not up yet. Checking again... (59/60)
21.02.2018 21.31.12,45 ERR: PostgreSQL did not start in a timely fashion
21.02.2018 21.31.12,45 An error has occured while attempting to configure. Aborting...
21.02.2018 21.31.12,46 Stopping services...
21.02.2018 21.31.12,46 Stopping spad service...
Stopping service spad: ..................done
21.02.2018 21.32.04,75 Stopping spoold service...
Error: 67: Database: connection to database crdb at localhost:10085 failed (could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "localhost" and accepting
TCP/IP connections on port 10085?
)
Error: 53: Database Manager: could not access storage database (connection actively refused).
Error: 4: Failed to run database class
Error: 4: Failed to read startup mode
02-23-2018 06:18 AM
There should be a pddb folder in the dedupe\log folder. check the log file there to see why postgres is not starting. Take a look at this article as well https://www.veritas.com/support/en_US/article.100038756.html
02-26-2018 12:37 AM
Hi,
Problem is now solved.
Microsoft does a change in Locals (region and language) going from Windows 2012 to Windows 2016. This affects the Postgresql database.
I used Microsoft Local builder and created new locals based on the win2012 version.
I installed the new locals on windows 2016 server and the postgresql service started successfully.
Thank's for your help in this issue.
Regards
Leif