The GCOMM Post
online backup free trial
Cloud technologies

6 items to consider when migrating to a private cloud network 4

1 Star2 Stars3 Stars4 Stars5 Stars 4 votes, average: 3.50 out of 5
Loading...
Matthew Thompson
image

The migration towards a private cloud network is a logical transition from hosting a business server network in an office. The fact that the office is not the best place to house a server network is not the only reason towards such transition. There are other factors that influence the migration to a private cloud. The expansion to more than one office, the increasing number of remote workers, and the need for greater business flexibility are all aspects that should be taken into consideration.

One of the major concerns for many businesses is how the migration of the servers from the office might affect network performance? Would it speed up or slow down the performance? Would it prompt users to complain? The fact that the core network would no longer reside within the company’s office space will most certainly induce change, thus leading to suspicion and doubt among some companies.

However, adapting to changes and accepting them is essential for the continual evolvement of businesses. If some of these concerns sound familiar and you’ve been wondering how to migrate from the current client-server network to a more robust network solution, you might consider the following items as necessary requirements for a private cloud network in your appraisal.

1. A reliable data centre

The server and the network equipment should be housed in a data centre. Data centres address items such as security, power, climate, vast availability of broadband and provide managed services connectable via Ethernet cable.

2. Reliable high speed broadband

This is probably the single most important item. The servers and office locations should be connected to high-speed broadband to ensure top networking performance. High-speed Ethernet services are probably required at each location to deliver performance acceptable to users.

3. Server infrastructure

Building a virtualised server network will not only facilitate the management of the servers but will also minimise the quantity of rack space required in the data centre. Equally important is the storage technology that should be fast and expandable. The investment made in the core server infrastructure should satisfy all standards and needs required to support both the server network and the clients.

4. Secure private network

Networks built over a private network are reliable and manageable. Private networks connect company offices and remote workers by not traversing the Internet and accommodate intelligent technologies such as MPLS that can allocate priority to traffic flow. Apart from being an elegant solution for growing and managing a business broadband network, a secure private broadband network ensures privacy of the traffic.

5. Hosted firewall

The adoption of a secure private network, will greatly increase the options for its protection. This configuration empowers the possibility of granting and denying access to the entire network through a single firewall. The firewall can either be purchased and hosted or acquired as a managed service.

6. Centralised Internet gateway

The use of a secure private network located in a data centre allows for a centralised Internet gateway. This means that all Internet access to the private network can be managed through a single Ethernet port. It delivers easy access control of external sites and easy management of remote access. A centralised Internet gateway is a scalable Internet connection for the entire business.

A private cloud network is an elegant and scalable cloud solution for a business. Even though it needs to combine a suite of ingredients to deliver the best outcome, the flexibility it creates for a company is incomparable to an office based server network.

Find out more on how GCOMM deploys private cloud networks.
Get in touch with me today and learn what to consider when migrating to a private cloud network.

♦ End

About Matthew Thompson

Matthew Thompson
Matt joined GCOMM in 1999 in a Sales and Strategic Accounts role. He recently relocated to Sydney, where he handles strategic relationships with both clients and vendors. He has a Business degree in Marketing and Management from Griffith University. Matt regularly represents GCOMM at various conferences, forums and business awards.
  • Adam Tessieri

    Interesting article Matt, we are seeing more and more of these deployments of late, its very true that the network supporting the Cloud deployment is key. If not business grade it can become a real risk to the success of the solution. In many instances we have been deploying networks with diverse connections and auto failover to ensure business continuity to the Cloud.

  • Matthew Thompson

    Many business I am talking to are taking a crawl, walk and run approach to the cloud. This doesn’t need to be an all or nothing approach. The underlying network (including redundancy) must be able to support the move to cloud and provide the same user experience to be most effective.

  • Peter Thompson

    The migration process must also be considered as a serious element of the implementation. Clearly working systems are live and the process of moving from an internal server environment to a hosted one comes with challenges that need to be well planned and thought through.

  • Project managing the migration is very important – but for businesses with multiple locations, the private cloud model is clearly the best practice way forward.

    I think that the key challenge for all ‘cloud’ buisness applicaitons is to ensure that the solution is not only a productivity enhancing strategy, but also one that focuses on cost-savings as well. It’s a healthy challenge!