StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!
-
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
-
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
-
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
What are you using?
-
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
What are you using?
KVM would be my guess
-
@DustinB3403 said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
What are you using?
KVM would be my guess
Correct. Fedora 29 with KVM.
-
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@DustinB3403 said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
What are you using?
KVM would be my guess
Correct. Fedora 29 with KVM.
If I could ever get some more time around here, I would spin up KVM on an older R710.
-
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@DustinB3403 said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
What are you using?
KVM would be my guess
Correct. Fedora 29 with KVM.
If I could ever get some more time around here, I would spin up KVM on an older R710.
We have that exact server being pulled out of service at the site where we are putting in KVM!!
-
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@DustinB3403 said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
What are you using?
KVM would be my guess
Correct. Fedora 29 with KVM.
If I could ever get some more time around here, I would spin up KVM on an older R710.
I'm going to be setting up that DL385 G7 in my lab like this.
-
@DustinB3403 said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@DustinB3403 said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@wrx7m said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Only for Windows...
Supported Operating Systems are: desktop versions starting from Windows Vista to Windows 10 and all server versions starting from Windows Server 2008R2 to Windows Server 2016
About to do a P2V for a company, but this won't help because nothing they run is this new.
Microsoft doesn't have a P2V for Hyper-V?
We aren't using Hyper-V
What are you using?
KVM would be my guess
Correct. Fedora 29 with KVM.
If I could ever get some more time around here, I would spin up KVM on an older R710.
I'm going to be setting up that DL385 G7 in my lab like this.
Nice unit for a lab
-
@mlnews it's not to shabby. It previously has ESXi 5.0.0
-
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
-
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
Once you can export one, export all of them. The cost of one is the same as the cost of all.
-
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
Once you can export one, export all of them. The cost of one is the same as the cost of all.
With a script, you're right - I'm not looking to hire someone to make said script at this time.
-
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
Once you can export one, export all of them. The cost of one is the same as the cost of all.
With a script, you're right - I'm not looking to hire someone to make said script at this time.
You mean doing it manually? That'll likely take a really long time.
-
Back on track...I had to P2V a server 2003 (non R2 even) recently. I shut down all unnecessary services and used DSK2VHD to do the initial conversion then had to clean up the boot.ini file to get the partitions right. I was going to Hyper-V so no problem with the disk format.
-
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
Once you can export one, export all of them. The cost of one is the same as the cost of all.
With a script, you're right - I'm not looking to hire someone to make said script at this time.
You mean doing it manually? That'll likely take a really long time.
Well - the report will tell us how many patients we have, then management can make the determination if they want to hire someone to script it all - or just do it manually.
-
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
Once you can export one, export all of them. The cost of one is the same as the cost of all.
With a script, you're right - I'm not looking to hire someone to make said script at this time.
You mean doing it manually? That'll likely take a really long time.
Well - the report will tell us how many patients we have, then management can make the determination if they want to hire someone to script it all - or just do it manually.
Any idea how long manually takes? Is that like just taking a screen shot of the current output?
-
@jt1001001 said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Back on track...I had to P2V a server 2003 (non R2 even) recently. I shut down all unnecessary services and used DSK2VHD to do the initial conversion then had to clean up the boot.ini file to get the partitions right. I was going to Hyper-V so no problem with the disk format.
As mentioned before - my doing this required scandisk running something like 13 times to fix the disk before it would boot correctly. I have no idea why the VHD created by dsk2vhd made such a bad copy - unless the source was just in that bad of shape too.
-
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
Once you can export one, export all of them. The cost of one is the same as the cost of all.
With a script, you're right - I'm not looking to hire someone to make said script at this time.
You mean doing it manually? That'll likely take a really long time.
Well - the report will tell us how many patients we have, then management can make the determination if they want to hire someone to script it all - or just do it manually.
Any idea how long manually takes? Is that like just taking a screen shot of the current output?
No, the manual for children will likely be 1-4 mins, likely more on the 1 min side. But that's only a guess, I haven't done the process in years.
-
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@Dashrender said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@JaredBusch said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
@scottalanmiller said in StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!:
Think of the alternative... how much hardware and man hours are going into working around extracting the data?
No where near as much as reverse engineering the database to create the output needed.
This is something I have done more than one time. It is not that easy.
Depends on the database. But it's something we do from time to time and often is pretty basic. I mean days of work, yes. But maintaining all that stuff is also days of work, plus the cost of hardware, isolation, risk, etc. On top of maintaining all that old stuff, we assume that there is no support should something break, either.
The system is basically in a static state. So if it breaks - restore to a known good working state and move on.
The problem I see running into over time is hardware and hypervisor tech that can support this until the kill date of 2036.
we can manually use the built system to do what is called a CCD export of the children's files - while this will be extremely manual in nature, it will likely be less expensive than hiring NTG or whomever to learn the DB layouts and extract the desired data.
Maybe, personally I think this seems very unlikely given 2036. That's 18 more years of dealing with stuff already in a ridiculous state today. Remember that you are going to be dealing with people that are not you and have no memory or knowledge of this system decades from now, a system already insanely old, trying to do restores or run systems 30 years old.
I doubt that that stuff will be cheap at that point, or anytime between now and then. A one time conversion to text files or PDF is over and done. Yeah, it's a bigger up front cost, but it is a single cost that never comes back to haunt you.
Oh believe me - I completely agree with you. Personally, we need to run a report to find all patients who were under 13 years old, export those. Then we can kill this system off in 2023 for all patients, and we'll have the children who have a longer hold requirement already exported.
Once you can export one, export all of them. The cost of one is the same as the cost of all.
With a script, you're right - I'm not looking to hire someone to make said script at this time.
You mean doing it manually? That'll likely take a really long time.
Well - the report will tell us how many patients we have, then management can make the determination if they want to hire someone to script it all - or just do it manually.
Any idea how long manually takes? Is that like just taking a screen shot of the current output?
No, the manual for children will likely be 1-4 mins, likely more on the 1 min side. But that's only a guess, I haven't done the process in years.
Oh, that's really fast. If it is that simple, let's say you have 10,000 customers. That's 10,000 - 40,000 minutes. I bet that it gets faster with someone doing one after another. That's a maximum of 33 weeks of full time work for 10,000 customers to be transferred.
And that is a lot of customers. And that is assuming four minutes per customer. And assuming that you realistically get four productive hours of doing a task like that per day.
