Size before allocating
Memory, processor, storage and network access are studied together. A business application, a database and a file server do not have the same constraints. We look at real uses and dependencies.
Solution 02 / Private Servers & Cloud
A welcoming environment for your systems.
Cloudlab prepares the reception of your infrastructure and your data. Agedis supports virtual machines, Linux or Windows environments and their administration.
Your offer in plain language
What we define
before your estimate.
- For what use?
- Virtual machines for your applications and services.
- What perimeter?
- Resources, storage, network, access and system administration to be distributed.
- Where is the data?
- Accommodation is offered in France. The reception environments and speakers are specified for your project.
- What protection?
- Distinguish between snapshots, backup copies and the recovery scenario.
- What assistance?
- Contact channels, support periods, maintenance and responsibilities are described in the successful offer.
- How to change next?
- Access, export formats, volumes and restitution conditions must be planned before commitment.
The proposal distinguishes the hosting environment, system administration, application maintenance and backups. The migration specifies the accesses to be recovered, the checks and the cutover schedule.
Preparing my project →Capacity, prices and commitments are detailed in your proposal, depending on your applications, volumes and operating methods chosen.
Organize environments
The separation between production, preparation and administration is defined from the start. Technical access, accounts and network rules are limited to the necessary scope.
Provide for further action
Resource scaling, updates, and disaster recovery are part of the design. We document components and responsibilities to facilitate future interventions.
Preparing your project
From IT needs to the reception environment.
Moving infrastructure is not just about choosing computing capacity. Services communicate with each other, users expect certain accesses and publishers can impose prerequisites. We start from this set to frame the hosting project: what exists, what must be preserved and what can evolve. This reading avoids sizing a machine while forgetting the rest of the system.
The scope is built with people who know the applications. Resources, storage, access and intervention windows are examined before preparing a migration. When the need involves adapting the servers, Agedis intervenes on the systems. Cloudlab supports the data center component. The choices are thus linked to concrete uses and identifiable responsibilities.
Inventory dependencies
Identify exchanges between applications, shared directories, messaging services and connections with company sites.
Sizing with the right contacts
Bringing together the needs of the publisher, user constraints and the ability to change the environment. The load assumptions must be explicit.
Describe the limitations of the service
Hosting, system administration and application support have complementary scopes. Specifying them makes it easier to monitor and organize interventions.
Preparation questions
Decisions to be made together.
Does a project have to move all the information technology?
The scope can concern a service or a set of applications. The study specifies what remains on site and the exchanges to be maintained between the environments.
How to take business software into account?
Its prerequisites, access modes and dependencies are examined with the publisher or integrator. They guide resources, network and migration stages.
Understand and prepare
Choose an environment based on the expected service.
A virtual server should allow a team to work: access its folders, use its software or share an application. Technical dimensioning and access organisation are defined on the basis of this need.
Resources, capacity and pace of activity
The number of users is a starting point. You also need to know concurrent processing, document volumes, database needs and peak periods. A file server and an application that produces documents do not require the same resources. We study memory, processor, storage and connectivity with the system team. The publisher's prerequisites and the possibilities for development help you choose the reception base.
Consistent access from the company
The project must specify how users join the service, which positions are affected and what permissions are required. A remote connection alone does not solve the management of accounts, groups and folders. Agedis prepares these elements on the systems, with the company manager. If the quality of the local network limits use, the diagnosis can be extended on site with Alltech. Reception at the data center and workstation settings remain identified areas.
Migration and coexistence choices
Moving a machine or rebuilding an environment are two different approaches. Depending on the existing situation, the study examines versions, licenses, dependencies, profiles and data transfer. A coexistence phase can be useful to check certain uses before stopping the old service. The file must indicate the interventions to be carried out, the prior backups, the return conditions and the person who validates the result in the business software.
What is defined in the proposal
The proposal describes the resources retained and the responsibilities: Cloudlab reception base, installation and system administration with Agedis, intervention by the publisher or Dtouch for the application if necessary. It also specifies the backups included or to be planned, access, monitoring methods and development conditions. The term “private cloud” must be linked to this architecture and this concrete perimeter, rather than to a configuration supposedly identical for everyone.
Our method
From the first exchange
to the care.
Understand
Your uses, existing, constraints and priorities.
Prepare
The perimeter, access, recovery and verifications.
Accompany
Commissioning and monitoring agreed with you.