Define what is welcomed
Applications, data, services and network dependencies: each component must have an identified role and owner. The chosen scope is specified in the project proposal.
Datacenter · Local team
The data center.
A close-up team.
Based in Ostwald, in Alsace, we prepare your hosting with you: needs, migration, access and monitoring. You interact directly with a team who knows your environment. Servers and systems are accompanied by Agedis; applications and their integrations by Dtouch.
Datacenter · hosting · continuity
A data center base for your infrastructure
A professional application depends on several elements: the machines that run it, the data it uses, the network connections and the people who operate it. A datacenter project begins with this overview. What needs to be hosted, who needs to access it, and what needs to be done. Cloudlab This data centre component is linked to the systems and applications teams.
The work then consists of specifying the perimeter. The host environment, necessary resources, access and operating responsibilities must be described before migration. Agedis supports the servers and systems part; Dtouch intervenes when software or an integration needs to evolve. This articulation makes it possible to deal with dependencies from the preparation of the project, then to organize checks after commissioning.
Organize access
Uses in the office, remotely and on several sites do not imply the same needs. User access and administration access are studied with the system teams.
Preparing for exploitation
Maintenance, backups, contacts and intervention methods must be examined together. Hosting must remain understandable for those who rely on it on a daily basis.
Migration · coordination · commissioning
Prepare a migration to the data center
A migration may involve an isolated server, a set of applications or a wider infrastructure. Before moving resources, you need to know what depends on what: applications, directories, files, network access and user stations. The study prepares the sequence of operations and identifies the people who will have to intervene or validate the uses at each stage.
The data center component is coordinated with the system work of Agedis and, when necessary, with the application adaptations of Dtouch. An intervention window is prepared according to the constraints of the activity. The checks then focus on the actual service: do users find their files, do the applications communicate and are the expected services accessible from the right sites?
Map the starting point
Gather the characteristics of the machines and the prerequisites of the software, but also the uses that allow to verify the result.
Preparing the steps
Define the participants, access, order of operations, cutoff conditions and decision points. Coordination with publishers may be necessary.
Organize follow-up
Keep a list of checks and open items after commissioning. User feedback completes technical controls.
Preparation questions
Decisions to be made together.
What a difference between Cloudlab and Agedis ?
Cloudlab covers the data center and reception infrastructure. Agedis supports servers, systems and their IT support. The scope of each is defined for the project.
Can we prepare hosting for an existing application?
Yes, the study starts from the characteristics of the application and its dependencies. Migration conditions, resources and checks are defined with the team or publisher concerned.
Should we plan for a cut?
It depends on the architecture and operations. The impacts and the intervention window are studied before planning the migration.
Who's in charge of the servers?
Agedis supports preparation and system interventions defined in the project. Cloudlab covers the data center component and the exchanges associated with the reception of the infrastructure.
Architecture & documentation
Infrastructure
which reads clearly.
A network is also conceived on a plane. As in the approach presented by Alltech, level 2 and level 3 diagrams provide an understanding of connections, separations and paths between services.
Level 2
Local connections.
Switches, Ethernet links and VLANs: the plan describes how the equipment is connected and how the uses are separated within the network.
Level 3
Exchanges between networks.
Routing, sub-networks and IP address: The schema specifies how data flows between environments and their access points.
Structured documentation facilitates preparation, diagnosis and interventions. It gives a common reading to those who administer the environment.
Find this approach at home Alltech
Enlarge photograph
The equipment, in pictures
At the heart of data.
From server racks to their environment: a look at our technical archives.
A team to Ostwald,
close to your activity.
Cloudlab combines accommodation in France and local support. Our team at Ostwald, in Alsace, knows your project and your uses: you have a direct contact for technical choices, recovery and monitoring of your environment.
The location of the data, any copies, third-party services and their responsibilities are specified in the proposal. We identify these elements before commissioning.
Access is part of the architecture.
Administrative accounts, private connections, certificates and network rules are studied according to the needs of the project. Technical access must be identified and limited to the stakeholders concerned.
Supervision must lead to action.
We look at the services, storage, and resources your applications need. Alerts, support and intervention periods are defined within the agreed scope.
A backup is not a promise to take over.
Restoration requires an environment, access and an order of operations. We distinguish between the data backed up, the restoration conditions and the recovery objectives to be agreed.
Delve deeper into backup and recoveryIntervention photographs
Read the equipment and its connections.
These intervention views provide a concrete benchmark for discussing the equipment, their connections and their monitoring.
These archive photographs illustrate the equipment and technical gestures. Data center reception and system administration needs are defined for your project.
A method of shared work01 02 03 04 Discover our way of working
Prepare. Realize. Check. Follow.
Quality depends on the technical choices and the organization of the project: understanding the uses, associating the right skills and keeping a legible follow-up.
Frame the need
Identify the applications, data and constraints that determine the host environment.
Linking responsibilities
Distinguish between the data center, the systems administered by Agedis and the business applications.
Preparing for transitions
Organize dependencies, access and migration steps with project stakeholders.
Provide continuity
Define the backup scope, recovery conditions and expected checks.
Your access and documents
Your codes and diagrams are at your disposal.
The access codes specific to your services, architectural diagrams and working documents established for your environment are at your disposal. They allow you to monitor your services and organize their continuity with the stakeholders of your choice.
Expertise that complements each otherAlltech · Building installations and equipment Agedis · IT, systems and servers Dtouch · Business development and integration
The right skills for the rest of your project.
Preparing on-site connections
Cabling, patching and Wi-Fi connect your premises to hosted services.
The building network with AlltechInstall and operate systems
Servers, accounts, backups and user access: Agedis I'll go with your computer.
Servers and systems with AgedisConnecting business applications
Development or integration can change the way your tools are exchanged.
Software integrations with Dtouch