NOTICE: Branded Content
NOTICE: Certain versions of content (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.
Data Protector User Discussions
cancel

Backup Win2000 server via EADR method using DP9 cell manager

Highlighted
RiclyLeRoy Respected Contributor.
Respected Contributor.

Backup Win2000 server via EADR method using DP9 cell manager

My target is to get iso image for old Windows 2000 physical server.

 

These ones are my components:

Old win 2000 srv: DP A.06.11 (Disk Agent + Automatic Disaster recovery) see "components"  attachment

Win 2012 R2 server: Cell Manager DP 9.09

I know this method is unsupported but It should work.

I created backup choosing as file system target (c: and configuration) but I got these warning (see  "warning" attacment) for some files :

Cannot open: ([32] The process cannot access the file because it is being used by another process. ) => not backed up.

what do you think? It's a problem to continue this process to get iso image?

I tought to upgrade  DP client components to A.06.11 to A.06.20 or A.06.21... but I got another error:

the procedure entry point getaddrinfo could not be located in the dynamic link library WS2_32.dll

 

Suggestions please?

3 REPLIES
Victor_F_DP Honored Contributor.
Honored Contributor.

Re: Backup Win2000 server via EADR method using DP9 cell manager

Hello RiclyLeRoy, 

This mismatch of version is not supported and is not recommended. 

Anyway, these warning that you receive is not a big deal, and I'm sure that ISO. These warnings are about some files opened and DP cannot backup that. Probably are logs or temporary files. 

Additional Windows Server 2000 is not supported for DR on DP 6.21 (https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/attachment/KM1134004?fileName=HPDR_SupportMatrix_DP62.pdf)

It is only on DP 6.1 (https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/attachment/KM718727?fileName=HPDR_SupportMatrix_DP6.1x.pdf)

So, you should keep this version on the client and does not upgrade it. 

As summary, ISO should be good, but this is not recommended neither supported due the mismatch of version. 

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
RiclyLeRoy Respected Contributor.
Respected Contributor.

Re: Backup Win2000 server via EADR method using DP9 cell manager

 

Anyway, these warning that you receive is not a big deal, and I'm sure that ISO. These warnings are about some files opened and DP cannot backup that. Probably are logs or temporary files. 

 

If you check my attachment file you'll see there are registry files too, so i think It's a big problem for ISO.

Victor_F_DP Honored Contributor.
Honored Contributor.

Re: Backup Win2000 server via EADR method using DP9 cell manager

Hello, 

I was checking and I can see the following files that show the warning, based on the screenshot: 

  • software
  • software.log
  • system
  • system.alt
  • Perflib_Perfdata_308.dat.

I have checked and that's true, some files are from the registry (https://support.microsoft.com/en-us/help/256986/windows-registry-information-for-advanced-users) but, I also figure out that these files cannot be opened using any method, I tried with a couple of files editor and cannot be possible. Additional, I confirm that with this forum about that (https://superuser.com/questions/131256/what-is-the-purpose-of-config-software-log/131268). 

Regedit saves the data automatically or can be saved manually in an external file to be imported later (https://www.makeuseof.com/tag/save-windows-registry/). 

Also, the Perflib_PerfData_###.dat are generated automatically for System Monitor and should disappear every time you reboot the server. (https://www.bleepingcomputer.com/forums/t/54540/a-solution-for-perflib-perfdatavariousdat/)

For that reason, I can believe that ISO is in good conditions. 

Hope this helps you, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.