Hi, This appears to be an email that is meant for a hosting provider. DSpace does not have a centralized support team or support service. This dspace-tech mailing list is a general list for sites who are asking for help in maintaining or upgrading their own DSpace site. So, this is not a vendor support email address or similar.
If you are looking for vendor support, see our list of recommended, registered service providers: https://dspace.org/registered-service-providers/ You also may want to be aware that DSpace 6 is no longer under support (as of July 1, 2023). Current supported releases include DSpace 7, 8, and 9. See our releases at https://wiki.lyrasis.org/display/DSPACE/Releases. Tim On Tuesday, July 22, 2025 at 8:04:55 AM UTC-5 [email protected] wrote: > Dear Support Team, > > DSpace > > > > I hope this email finds you well. > > > > As part of our ongoing efforts to modernize and enhance the reliability, > scalability, and performance of our IT infrastructure, the ITS Department > is planning to *migrate on-premises servers to the Microsoft Azure Cloud*. > > > > Accordingly, our team is responsible for managing the *DSpace System > (Release 6.3)*, which is currently hosted on the following on-premise > server: > > > > *DSpace Production Server:* > > - Hostname : qspace.edu.qa > - IP Address : 185.37.108.150 > - URL : https://qspace.qu.edu.qa > > > > > > - *Migration Plan Overview* > > We will be using a *“lift and shift”* approach, where the existing > virtual servers will be moved to Azure with minimal changes. The key > details of the migration plan are as follows: > > - The *only expected change* from our perspective will be the *server > IP address*, which will be updated as part of the migration. > - The ITS team will handle all *infrastructure-level configurations*, > including the new IP setup, firewall rules, and connectivity. > - The *application will remain operational on-premises* during the > testing and validation phase in Azure to avoid any disruption to your > service. > > > > - *Testing and Cutover* > > > - Once the server is successfully migrated and *all services are > validated* in the Azure environment, we will coordinate with your team > to agree on a *mutually acceptable cutover window*. > - Only after your approval and successful testing, the *application > will go live from the Microsoft Azure environment*. > > > > - *Action Required from Your Side* > > > - If the *application requires changes* due to the new IP address > (e.g., hardcoded IPs, configuration, integrations), it will be the > *responsibility > of the application owner or vendor* *support* to implement those > changes. > - Also, if necessary, please to: > - Confirm whether the application (*DSpace 6.3*) is fully > compatible with the *Microsoft Azure* environment. > > > > - > - Identify and communicate any dependencies, prerequisites, or > constraints that may impact the migration process. > > Your prompt response will help ensure a smooth and efficient transition. > > > Please let us know if you need any further details or clarification. > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/7df26352-de1e-48df-a2d1-0a6b0b526e3bn%40googlegroups.com.
