Yes, if you have your own AS number and IP range we can provide you with a BGP session.
Please let us know your requirement and we will help you.
- Virtual Server: No, not at this time.
- Virtual Data Center: Yes, your Virtual Data Centre has a pooled internet traffic for all VMs in that DC.
Each Zettagrid virtual server is preconfigured with a local firewall with only the following management ports open:
- SSH Port 22 for Linux Servers
- RDP Port 3389 for Windows Servers
If you would like a dedicated firewall we offer NSX and VyOs or you can upload you own virtual firewall. Please refer to our Firewalls page.
Yes, you can create a private subnet for your VMs to communicate when using our Virtual Data Center product.
Yes, the server is yours to install any software that you require. Please ensure you comply with any software licence obligations you may have.
Note for Windows Customers: Please note that Microsoft Retail, OEM or third party SPLA based software cannot be installed on Zettagrid servers as this contravenes the Microsoft End User Licence Agreement (EULA). You are required to rent any such software from Zettagrid should you wish to use it in our environment. If there is a Microsoft product you require but it is not listed on the Zettagrid website please email email@example.com and we’ll provide you with a monthly rental price.
For further information please refer to our Microsoft Software Licensing page.
Yes you can! Please email firstname.lastname@example.org with the following information about your VM:
- Operating System
- RAM Requirements
- Disk Size(s)
- Bandwidth Requirements
We will then provide you with a quote to host your VM. Custom VM’s cost IDR 1.000.000 to setup.
We cannot guarantee that your imported VM will work successfully in our environment. Should this be the case and you elect not to proceed with a Zettagrid service we will refund your monthly fee. Any setup fee will not be refundable.
Please note that you cannot bring your Microsoft Windows Operating System (i.e. Windows 2016, Windows 2012 etc) license to Zettagrid as this will violate the Microsoft Licence Agreement (EULA). Zettagrid can rent you a monthly licence for this purpose.
Yes, Zettagrid has access to full range of Microsoft SPLA licensed products. Please contact email@example.com if you would like to rent one of the following licenses on monthly basis.
- Microsoft Dynamics
- Microsoft Exchange
- Microsoft Forefront
- Microsoft Office
- Microsoft Project Server
- Microsoft Project
- Microsoft Search Server
- Microsoft Sharepoint Server
- Microsoft SQL Server
- Microsoft System Center
- Microsoft Visual Studio
At the moment we only offer Microsoft software as additional software options to be installed. However you can purchase your own cPanel, Plesk or other management control panel license and install this on your Zettagrid Server.
At Zettagrid for licensing purposes we define our Processors (or CPU’s) in terms of capacity or GHz. The number of cores is unrelated to Ghz or Processors and has no effect on Microsoft licensing. For licensing purposes a CPU is defined as 2GHz of capacity. If you have up to 2GHz then and elect to license under a processor model you will require a single Processor license. If you have 2.1 GHz, 2.4 GHz etc then for licensing purposes you require TWO processor licenses. At Zettagrid we are able to cap the maximum amount of processor licenses required at TWO. If for example you have a total of 10GHz CPU in your VM, rather than paying for FIVE processor licenses, due to our cap you only require TWO licenses. If you have 10GHz and decide to split this into 2 VM’s of 5GHz each you require FOUR processor licenses in total rather than TWO. This is because processor licensing is applied on a per VM basis.
A processor is a way of licensing Microsoft software on a subscription basis within Zettagrid. A processor license allows an unlimited number users access to the Microsoft software. Processor licenses are usually more expensive than a Subscriber Access License (SAL), however they become cost-effective with increasing number of users. Unlike a SAL which can be used to access more than one instance (or VM) of the software, a processor license has a direct relation to the number of VM’s you have. If you have ONE VM then you need ONE set of processor licenses, if you have TWO VM’s then you must purchases TWO sets of processor license and so on. Zettagrid cap the number of processor licenses per VM at TWO, regardless of the amount of cores or Ghz in your VM. See an explanation of cores vs processors vs Ghz elsewhere in the FAQ.
A Subscriber Access License (SAL) is one of the options for licensing Microsoft software under a subscription model. A SAL is required for each unique USER or DEVICE accessing a Microsoft product. A SAL is not a concurrent license and hence cannot be shared amongst multiple users or devices. Multiple users can access through a single device, or multiple devices can be used by a single user, however you cannot aggregate concurrent users through a single device – individual user SALS are required. Nonconcurrent users through a single device is allowed.
A SAL can be used to access any number of instances of the Microsoft software. For example if you have a Windows Server and want remote access for ten users you must purchase 10 SAL’s. If you then purchase a second VM with a second copy of Windows and require access for the same ten users you do not have to purchase additional SAL’s. The existing SAL’s are valid for as many Windows Servers as you may wish to provision, thus additional Servers can be had for essentially the incremental cost of a VM without incurring additional server license fees.
Can I bring my existing software licenses to the cloud?
Yes, You can use your existing Microsoft Enterprise Mobility to use your existing licenses on Zettagrid. Read more about Licence Mobility.
What software is available on Zettagrid?
We have a full range of Microsoft software. We also offer monthly licencing for Vyatta, Trend, Citrix and F5.
Microsoft products can be licensed in two ways -by Subscriber Access License (SAL) or per processor (Proc). Some products are only licensed one or the other whilst other products can be licensed either. The essential difference is that a processor license allows unlimited users whilst a SAL is required for each unique user or device accessing the software. For products that allow either licensing model determine the cost under both models and opt for the cheaper one. Generally the larger the number of users the more economical a processor license becomes. Please see the individual SAL and processor FAQs for more detail.
How To (6)
- The virtual machine remote console (VMRC) plug-in fails and does not connect in vCloud Director.
- Though the plug-in is already installed, it repeatedly asks to install the plug-in.
This issue occurs if several security settings are not configured correctly in Internet Explorer.
Resolution 1 – Internet Explorer Reconfiguration
- Disable the Protected Mode on Trusted Sites.
- Add https://*.zettagrid.id to Trusted Sites.
- Turn on Compatibility mode
To disable the Protected Mode:
- In Internet Explorer, navigate to Tools > Internet Options > Security.
- Deselect the Enable Protected Mode option.
- Restart the web browser.
- Alternatively, add the vCloud Director address to the Compatibility View Settings in the Internet Explorer.
To turn on Compatibility View for Internet Explorer 8/9:
- Check if the Compatibility View button ( Compatibility View button) appears in the Address bar.
- Note: If you do not see the Compatibility View button, there is no need to turn on Compatibility View.
- Click the Compatibility View button (Compatibility View button) to display the site in Compatibility View.
- After you turn on the Compatibility View, Internet Explorer automatically displays that site in Compatibility View each time you visit. You can turn it off by clicking the button Compatibility View button again. Or, you can clear the entire list of sites using Compatibility View by deleting your browsing history.
To turn on Compatibility View for Internet Explorer 11:
- Open the desktop, and then click the Internet Explorer icon in the taskbar.
- Click the Tools button (Tools), and then click the Compatibility View settings.
- Under Add this website, enter the URL of the site you want to add to the list.
- Click Add.
Resolution 2 – HTML5 Console (My Account)
The Zettagrid My Account now features a HTML5 Console which does not require any additional plugins. This console is available for both Virtual Servers and Virtual Data Centers. Please log into My Account and view the service.
- For Virtual Server you will see a console button on the Virtual Server overview page.
- For Virtual Data Center please click on the “Virtual Machines” tab. Each VM will have a console icon.
Use the Zettagrid Virtual Admin console. This is available once you login into “My Account”.
- Click Services
- Select the VM you want to administer
- Use the Start, Stop, Suspend, Reset buttons to control your VM.
- For further features, Click “Console” and use the controls available via the HTML5 console
Virtual Data Center : Yes, the control panel covers all aspects of managing your private Virtual Data Center in the cloud. We also provide access to vCloud Director which give you direct VMware management of your Zettagri eThe URL and login credentials are available in My Account.
Virtual Server : Yes, we provide Start, Stop, Suspend and Reset functionality from our MyAccount page. The MyAccount page also provides access to the server console.
You can use standard file transfer protocols once you have opened these ports on your Virtual Server. For Windows you can enable local drive mapping or WebDAV or create and FTP server. For Linux you could enable FTP/SFTP.
If you would like to perform an initial “seed” of a large volume of data please contact firstname.lastname@example.org to discuss alternative population methods.
The default password for all Zettagrid Templated VMs is specified under the Security Tab of the Virtual Datacenter Service. It’s strongly suggested that the default password is changed once a VM Template has been deployed.
You can mount an ISO or DVD to your virtual server using our vSphere administration client but this may be quite slow over the internet. We recommend setting up your own FTP/SFTP service to transfer the files.
Yes, however, individual VMs are limited to one storage tier at a time.
Yes, you can migrate between storage tiers at any time without downtime, however there are a few caveats:
- Migration between ioSTOR-250 (and higher) and any other tier will become effective immediately.
- Migration from ioSTOR-100 (Archive Tier) to any other tier will take much longer due to the speed of the archive storage. Your VM storage performance may be affected during the migration process so schedule it out of a peak period.
Veeam Cloud Connect (3)
This FAQ provides the steps to manually seed a Backup Copy job with Cloud Connect for Veeam. Seeding a Backup Copy Job with Zettagrid will reduce the initial time and bandwidth required to commence using Cloud Connect. If you want to seed a Backup Copy job you will need to do the following:
- Send a Seed Request to email@example.com and take note of the Ticket Number (e.g. INC1234567).
- Create a new Backup Copy Job/Backup Job.
- Backup Job – Add VMs from vCenter
- Backup Copy Job – Add VMs from an existing Backup Job or from Backups
- For the Target Repository, initially select a Local Repository and let the job run to seed the data.
- Disable the Backup Copy Job/Backup Job once the first run has completed.
- Copy the folder where the job files are contained from the Local Repository to an External Storage Device (USB/NAS).
- Label the device and package with the Ticket Number (e.g. INC1234567).
- Send the Storage Device to Zettagrid (shipping address will be provided in your ticket).
- Wait for confirmation from the ticket that the import has been completed.
- Rescan the Cloud Repository.
- Modify the Backup Copy Job/Backup Job to point the Target Repository at the Cloud Connect Repository. Then click “Map Backup” and select the correct job.
- Enable the Backup Copy Job and resume the stream.
How much Bandwidth is needed for Cloud Connect for Veeam Jobs and
While this does vary depending on the size of you backup job and your connection to the Internet and its use (dedicated or otherwise).
It’s Recommended that you have 1Mb Upload Speed for every 300GB or data.
How do I Size the Cloud Storage?
To size your Cloud Connect Offsite Repository you should take into consideration the size of the backup job(s) on your local Veeam Server. There is a one to one relationship in terms of what the size of your backup is locally as to what is stored offsite.
There is an Online Veeam Calculator that can be used to simulate your Cloud Connect Backup or Backup Copy jobs and get an idea of the storage requirements.
Details to Connect:
Veeam B&R Setup and Configuration:
In the B&R Console select the Backup Infrastructure Menu and right click on Service Providers
Click the Add Service Provider and enter in the following
Port: 6180 (default)
Verify the SSL Certificate and Click on Add to enter in Cloud Connect Credentials
Hit Finish and wait for the Connect to Zettagrid Cloud Connect completed. Once done confirmation of your Repository and Quota will be displayed
Hit Next and Finish
Once Completed you should see the Cloud Connect Gateway appear in the list in the Service Provider Tab. If you click on The Backup Repositories tab you should see the previously configured Cloud Connect Repository of Type Cloud with the Capacity and Free space shown.
You are now ready to Create Backup and Backup Copy jobs to the Cloud Repository.
What is a vCPU?
A vCPU is a virtual CPU and is an encapsulation of many underlying physical blade host processors presented via VMware to a single VM as its local processor.
Since a vCPU is based on the underlying host CPU the actual GHz amount will be a one to one mapping from its physical counterpart.
What is a vCPU in Zettagrid?
Zettagrid create clusters which are all of the same CPU type so as to not mix CPU types and lose any of the available CPU instruction sets as anything in the same cluster will remove CPU instructions down to a common base level among all hosts in that cluster.
Previously the GHz has been 2.67GHz and 2.3GHz, at the moment and for at least the next 12 months the current CPU spec in terms of GHz is 2.5GHz per vCPU.
Does higher GHz per vCPU mean it’s better?
No, whilst there is a correlation between the two it isn’t really a good indication of value for money or being on a better host if the underlying CPU is 2.6GHz rather than 2.5GHz.
As we upgrade the environments they will often get different CPU types and GHz amounts. At all times the introduction of a new CPU type means a better performing VM as it is a newer generation with a higher instruction set.
It is quite conceivable that in future the next GHz amount may in fact reduce per vCPU. This will actually mean that for the same price per month the customer is getting more value as the amount they have purchased can be utilised for more concurrent vCPU.
How do you sell CPU resources?
We sell CPU resources as a total of GHz consumed at any one point in time in the environment.
It is not an allocated model it is a concurrent consumed model or a high water mark. This means that customers can utilise very large amounts of overprovisioning if so desired but this might mean that in peak times when many of your VMs are running high CPU workloads you will be limited in terms of available CPU resources. In the event of this the VMs will go into a CPU Wait state for available resources when other VMs in your own environment are not using them.
- Customer has 100 VMs all with 2 vCPUs assigned. The customer is paying for 500GHz. In this scenario all VMs will be able to utilise all the resources that have been paid for as even if every VM is running both CPUs at 100% the total will only be 500GHz which is what has been assigned to the customers Virtual Data Centre. There is no conceivable event where any VM does not have access to its resources.
- Customer has 8 VMs all with 1 vCPU assigned, 6 powered on and 2 powered off. The customer is paying for 16GHz. In this scenario the 6 powered on VM are working fine performance wise. The customer has powered on an additional 2 VMs and now their users are complaining of performance issues. With the 8 VMs powered on the requirements could burst up to 20GHz but the customer is only paying for 16GHz so the customer would need to either be aware that performance may be an issue, power off the additional 2 VMs or increase the allocated resources in the environment to 20GHz.
- Customer has 100 VMs all with 1 vCPUs assigned. The customer is paying for 30GHz. In this scenario the customer is obviously drastically under allocating CPU resources for their VDC as the provisioned amount would be 250GHz. In day to day usage of the VMs they are generally only 10% utilised in terms of CPU. 10% of a single vCPU is .25GHz and for the 100 VMs this is 25GHz in total day to day. In this scenario whilst the customer is not paying for nearly enough CPU it is not constrained in normal activities as they are still under the 30GHz total that has been allocated. A warning in this scenario though, if any VMs start doing work more than the average then there may be periods where the total GHz used is over the 30GHz so it will be resource constrained when this occurs and potential for users to create service desk tickets complaining of performance problems.
- Customer has 100VMs with a mixture of 1-4 vCPUs assigned. The customer has allocated 200 GHz to the Virtual Data Centre. Generally in the environment the VMs day to day run at 30% which would have a total resource requirement in GHz terms of 260GHz. In this scenario the VMs will constantly be resource constrained by our systems as there is not enough resources provided so it is expected that the VMs will run slower than they should be in normal circumstances as they are continually in a CPU Wait state.
So how much should I buy?
This is a hard question to answer as it is different for every customer. If you want to ensure that your VMs always have the CPU resources that they require then purchase 2.5 x the total number of vCPUs assigned to VMs per Virtual Data Centre.
If you think your VMs often don’t need all their CPU power then you can under allocate by 50-80% and see how the performance goes day to day whilst making sure that you capture all use cases (like the end of month reports that run etc). If you find that users are feeling the VMs underperforming then increase the resources until you find a happy medium of price/performance.
If cost is the driving force entirely then reduce the amount of GHz allocated to the VDC drastically and simply put up with the artificial limits that are placed on each VM and be aware that the VMs will be considerably crippled.
Isnt it easier to just sell vCPUs?
Yes, it most definitely would but we prefer to give customers the final say in how much overprovisioning they wish to have in their own environment so that there is more granularity and control over how their VDC performs.
You may have a few Virtual Data Centres and would like to have the production VDC fully allocated in terms of vCPU so it is never constrained but also have a test VDC in which it really doesn’t matter if it suffers from CPU Wait times as performance is of no concern. In this scenario the test VDC may only have 25% of the required CPU resources and is a great way to save money rather than wasting it on CPU where it isn’t valued.
When trying to hot add memory to a Linux 64-bit guest operating systems, you cannot increase the memory to more than 3GB. You would see the following error:
“An invalid memory size has been specified. The maximum hot-add memory limit is 3,072 MB.”
These conditions apply while hot adding memory to virtual machines with Linux 64-bit guest operating systems:
- If the powered-on virtual machine has less than 3GB of memory, you cannot hot add memory in excess of 3GB.
- If the virtual machine has 1GB of memory, you can add 2GB.
- If the virtual machine has 2GB of memory, you can add 1GB.
- If the virtual machine has 3444MB of memory, you can add 128MB.
- If the powered-on virtual machine has exactly 3GB memory, you cannot hot add any memory.
For more information, see this VMware KB article.
The storage numbers are always calculated the same way for Virtual Datacenters:
Storage Used = Total allocated disk space of VMs deployed in Org VDC + Total memory of VMs deployed* in Org VDC (to account for VM swap usage) + Maximum possible existing snapshot size
Storage allocated = Org VDC storage allocation
Example 1: If you have 1 VM with 1 GB RAM and 10 GB disk the storage usage will be: 10 GB (disk) + 1 GB (VM swap) = 11 GB.
Example 2: If you have 1 VM with 1 GB RAM and 10 GB disk and create a snapshot (including memory), the storage usage will be: 10 GB (disk) + 1 GB (VM swap) + 10 GB (maximum disk snapshot size) + 1 GB (memory snapshot size) = 22 GB.
* Virtualisation Platforms stores VM Memory as files on storage to increase resiliency in HA scenarios and during periods of high usage.
Yes, when we create your Zettagrid Datacenter we actually create you a new “Organisation”. This Organisation can manage multiple Cloud Datacenters.
Typically, Zettagrid partners with multiple customers create individual Cloud Datacenters for each customer to simplify networking and billing for each customer.
If you wholesale Zettagrid services (where you bill your customers), then your customers will never know that you are using Zettagrid. You can claim it as “your cloud”. You can even change the reverse DNS!
If you resell Zettagrid (where we bill the end customer), customers will see invoices and emails from Zettagrid.
Yes, all our infrastructure including servers, storage and networking is hosted in Indonesia. This ensures that all information stored is governed by Indonesian government legislation including Privacy, Copyright and Company laws.
No. To set a performance benchmark we only allocate the resources that are purchased.
Providing “burstable” resources sets a false expectation of performance. When the cloud environment gets busy (in a burstable environment) your server is often not allocated additional resources thus making you feel that your server is performing slower than normal. Zettagrid does not do this. We only allocate those resources that you purchase and guarantee that these will be available.
Each individual VM (or group of VMs) is protected within its own security zone. We utilise both network and VMware based security measures to encapsulate all VM traffic and prevent activities like:
- IP Address Hijacking
- MAC Address Spoofing
- Broadcast Traffic Flooding
If you would like more information on our security measures please read our Technology Security summary or contact one of our sales staff who will be able facilitate answers to more specific queries or security scenarios.
No. Staff do not have any permissions and cannot logon to your VM. You control the password to log into your VM.
All contracts are “month-to-month” (30 days technically). You can cancel at any time. If you cancel prior to the end of the 30 day period you will not be eligible for a refund or credit for the unused portion of your service. We do offer discounts for long term contracts.
Yes, additional IPv4 addresses can be purchased individually. Justification is required with each request.
Note: that each Virtual Server and Virtual Datacenter is allocated one static IPv4 address.
Yes. You can do this at any time via My Account -> My Servers. Your virtual server name and IP address are kept but all other information is destroyed during the rebuild. We recommend backing up your files prior to doing a rebuild.
- Credit Card
- Virtual Account
- Bank Transfer
Yes. They your uploads and downloads combined in your internet quota.
Update traffic does count towards your quota.
Excess data costs IDR 900 per GB (exc PPn). This is automatically charged to your credit card or invoice monthly in arrears.
You can resize your Internet data quota (or any other attribute) at any time by logging into My Account > View Service > Click Resize > (Drag the slider).
You are responsible to patch your servers. Zettagrid does not currently provide a service to manage your servers for you. We recommend you engage an IT professional to maintain the security of your servers should you require assistance in this area.
Yes. We guarantee the resources allocated to you are available to your Virtual Server or Virtual Datacenter.
Yes, although when you create an account it will be first reviewed first by a Zettagrid team member before you will be permitted to purchase services online. The purchase price is in Indonesian Rupiah (IDR) and will be converted by your credit card provider.
Web hosting is certainly not an easy proposition, especially when a variety of options are available. However, like most things, there are some prominent trade offs. For instance, dedicated hosting is easily customizable and powerful too, but it is expensive. Additionally, adequate technical knowledge is also needed to be able to manage dedicated servers. Shared hosting, on the other hand, is inexpensive and easy to use; nevertheless, it can provide only a limited number of resources.
What will you do if you have website that is too large for a shared hosting plan, and that does not require extensive resources provided by a dedicated server? Virtual Server (VS) hosting is the most feasible alternative for you. It is an adaptable, economical and scalable hosting solution that has the power to fulfill the needs of any kind of website. It is a perfect option for those sites that have outgrown shared hosting plans, and are yet not ready for dedicated hosting servers. Let’s find out how virtual private server can help you to save your hard-earned money while hosting your business website.
What exactly is a virtual server?
Also called Virtual Dedicated Server (VDS), a virtual server is basically a methodology of splitting a physical server into segments. Each partition has a full-fledged operating system and can be rebooted independently. Every VS has its own unique IP address and it gets a share of CPU time, RAM and storage of the physical server. VS primarily helps to bridge the gap between shared and dedicated servers. The users are able to configure their portion as per their requirements, and that too at a less cost than dedicated hosting service.
What are the different kinds of VPS hosting plans?
Virtual private server hosting plans can be segregated into three broad categories viz.
- Unmanaged VS- In this case, the hosting company provides only hardware and network services. Whilst, as a user you are responsible for dealing with all the software and performance hassles and issues.
- Semi-managed VS- Here you are allowed to manage just the custom software, while the hosting company takes care of hardware, standard software and network.
- Fully-managed VS- With respect to this kind of VS hosting plan, you literally don’t have to manage anything. The host company looks after all the aspects of VS. It’s the company’s duty to provide you superlative services.
In simple words, VS provides flexibility together with accessibility and complete control. You can not only access the root, but you can also amend server-level software like MySQL, PHP and Apache. Thus, with virtual private server, you get all the benefits of a dedicated server, but in a package that is affordable and manageable.
Burstable RAM and VS
The primary drawback of a shared hosting server is that all the users get only a limited amount of memory. If all of a sudden, the website receives a truckload of traffic, then everything would be blocked due to paucity of resources. The burstable RAM in the VS counteracts the Digg-effect effectively. Burstable RAM is nothing, but a pool of memory that is set aside to handle extraordinary events. Hence, no matter what kind of traffic your site receives, VS hosting plans would never fail.
NSX Advanced Networking (9)
Zettagrid’s NSX Advanced Networking delivers enterprise-grade networking features powered by VMware NSX technology and is and all in one device utilising the features below:
- MyAccount UI: All configuration options are presented through Zettagrid’s MyAccount Portal with granular configuration of NSX Edge Interfaces, DHCP, NAT, Firewalling, IPSec VPN, Load Balancing and Dynamic Routing.
- Network Scaling: Three sizing options of the NSX Edge Gateways giving greater flexibility to clients to tailor their networking services while delivers network scaling that allows Virtual Datacenters to have the same level of performance as on-premises networks.
- High Availability: All NSX Edges size options come with the option of HA. With the HA feature turned on each NSX Edge is deployed in a HA Pair for greater resiliency and service continuity.
- Dynamic Routing: Support for BGP, OSPF routing that enables greater flexibility and control of the Virtual Datacenter networks and helps to extend Zettagrid based services extend to other zones or on-premises locations.
- Enhanced Load Balancing: Included in the NSX Edge is a full fledged L4/7 load-balancer that also provides enhanced features such as HA Proxy Based Application Rules, Custom Monitoring and SSL Passthrough,
- Enhanced IPSec VPN: Site-to-site IPsec VPN options enables a quick and efficient way to connect up multiple cloud or on-premises locations to your Zettagrid Virtual Datacenter allowing an easy way to extend workloads for hybridity.
The Advanced Networking features allow Zettagrid’s Virtual Datacenters based on vCloud Director the ability to take advantage of the enhanced features of the NSX Edge Gateway giving more power to clients to be able to be more efficient with their Zettagrid Cloud deployments.
NSX Edge Gateway Services
|Firewall||Supported rules include IP 5-tuple configuration with IP and port ranges for stateful inspection for all protocols|
|NAT||Separate controls for Source and Destination IP addresses, as well as port translation|
|DHCP||Configuration of IP pools, gateways, DNS servers, and search domains|
|Site to Site VPN||Uses standardized IPsec protocol settings to interoperate with all major VPN vendors|
|Load Balancing||Simple and dynamically configurable virtual IP addresses and server groups|
|Dynamic Routing||Provides the necessary forwarding information between layer 2 broadcast domains, thereby allowing you to decrease layer 2 broadcast domains and improve network efficiency and scale. NSX extends this intelligence to where the workloads reside for doing East-West routing. This allows more direct virtual machine to virtual machine communication without the costly or timely need to extend hops. At the same time, NSX also provides North-South connectivity, thereby enabling tenants to access public networks.|
At this stage there is no automatic upgrade and migration option however this is something that will be introducing in the near future allowing for a one click upgrade and migration from Basic to NSX Advanced. In the mean time you are able to provision a new Virtual Datacenter with NSX Advanced Networking and migrate your vApps and VMs to the new NSX Enabled vOrg Network. Stay tuned for a how-to video on how to achieve this.
At this stage there is no upgrade or downgrade option once the NSX Advanced Networking Service has been provisioned (including moving between a HA and non HA option) however this is something that will be introducing in the near future allowing for a one click operation to move between sizes and HA configurations. Please contact support to request this change in your service.
SecondSite FAQs (10)
There is no minimum amount of VMs required for SecondSite™ because it’s scalable.
Whether you’re protecting one VM or 1,000 VMs, it’s the same reliable and affordable solution for small businesses and large enterprises.
The number of VMs you protect does not alter the unit price or the feature set available. That’s why we make it easy and charge per VM, per month, with no lock-in contracts.
SecondSite™ works seamlessly with Hyper-V and VMware in your environment.
We can protect either environments, as we will run VMware on our side for you. That means that we will convert your Hyper-V based VMs into VMware formats as they are brought online after a failover.
Yes, you can use SecondSite™ to migrate VMs into Zettagrid’s cloud.
By using SecondSite™ as a migration tool, you can easily fail your VMs over into Zettagrid cloud.
Once you have migrated everything across, you can either cancel your SecondSite™ subscription since there are no lock in contracts, or you can continue using it and have your old production infrastructure as your disaster recovery (DR) site.
Your SecondSite™ subscription was automatically set up between you and Zettagrid using an IPSec VPN.
As this relies entirely on your outbound internet, there may be periods where you do not have the required 5Mbit/s minimum of bandwidth. It is at this point where SecondSite™ may report a disconnection.
SecondSite™ will re-establish the connection as soon as the bandwidth is available again.
If you are experiencing these sorts of disconnection alerts, please refer to our WAN Connectivity page and use the WAN Sizing tool to determine exactly how large the link needs to be for your business.
If you would like us to provide WAN connectivity for you, please contact us on +62 21 2960 7589, +62 811 283 878 or at firstname.lastname@example.org
While SecondSite™ takes care of many things for you, there are a few items that you still need to take care of in your Business Continuity (BC) or Disaster Recovery (DR) planning.
This includes external DNS/IP addresses.
When you have failed over to Zettagrid’s cloud you might have some external websites or IP addresses that may require changing.
With advance planning, you can ensure that all external websites or IP addresses can still be accessed after failover. For each of these you will need to think about which apprach you will take. You may decide to add steps to edit your external DNS records through whomever provides your external DNS in your DR plan. Alternatively, you may choose to introduce global load balancers so that this step is seamless.
There are a number of options available to you and it’s important to select the right approach for you and your business.
If you have issues with pairing or during operation, please ensure that you have the following ports open.
|4007||TCP control communication between your local VRAs to our VRAs through your dedicated ZCC.|
|4008||TCP communication as above to pass data from your protected virtual machines to our VRAs through your ZCC.|
|9081||TCP communication between your ZVM and our ZCC.|
A Recovery Point Objective (RPO) is the specific point in time that your data can be recovered to.
Lower RPOs mean less potential for data loss. Conversely, higher RPOs mean potentially more data lost in the event of a disaster.
SecondSite™ powered by Zerto provides incredibly low RPOs of just seconds.
3-10 second RPO
This is the default RPO you will receive with SecondSite™ if you have enough bandwidth available. If you needed to fail over, you will experience only between three and 10 seconds of data lost.
8 hour RPO
If your RPO were to extend out to eight hours, a disaster and failover at 8 pm would mean your data will be as it was at 12 pm lunchtime. You will have lost any data entered into systems/applications in the previous eight hours.
24 hour RPO
If your RPO were to extend out to 24 hours due to insufficient bandwidth, a disaster and failover at 2 pm will mean your data will be as it was the day before at 2 pm. Any data that was entered into your systems or applications in the previous 24 hours will be lost.
A Recovery Time Objective (RTO) is the amount of time it takes from the moment you initiate your disaster recovery (DR) failover to when you are able to use the VMs in the new SecondSite™ environment.
A lower RTO is better because it will typically mean that disruption to operations are minimised, users can get back to work quicker and your websites are back online faster. Low RTOs means less chance of your customers or other external parties even realising you were down for any period of time.
SecondSite™ stands out by offering incredibly low RTOs.
5-10 minute RTO
This is the default RTO you will receive when using SecondSite™. It means every VM comes online at the same time after a disaster event.
20-30 minute RTO
If you have selected to power some VMs up only after other VMs have successfully powered up, then you can expect an RTO of around 20-30 minutes.
>30 minute RTO
It is possible to inject scripts or wait times within SecondSite™ that can do pretty much anything in your environment. If you add in some scripts or commands which take a long time to process or complete, then your RTO can be greater than 30 minutes.
When creating Virtual Protection Groups (VPGs), you will need to select a Service Profile for each VPG.
There are four Service Profiles to make it easier to group VMs together based on target RPOs.
|Bronze||8 hour||This is the default profile and any VM in a VPG with this profile will have a target RPO of 8 hours.|
|Silver||1 hour||Any VM in a VPG in this profile will have a target RPO of 1 hour.|
|Gold||15 min||Any VM in a VPG in this profile will have a target RPO of 15 minutes.|
|Platinum||5 min||Any VM in a VPG in this profile will have a target RPO of 5 minutes.|
Bandwidth saturation or contention
In the event of bandwidth saturation or contention, the Service Profiles will be used to determine which VPGs have priority over others.
If a VPG has a more aggressive target RPO than another VPG, then its block changes will be failed over into Zettagrid’s cloud before its lower profiled counterpart.
Lower Service Profiles will failover after higher Service Profiles have successfully failed over.
A Virtual Protection Group (VPG) is an affinity group of one or more VMs.
They are then grouped together from that point on and exist as a single entity from Zerto’s perspective.
Usually VMs are grouped together based on a need to be kept and dealt with at the same point in time. Examples of this are Domain Controllers or a web front end and its database counterpart.
You may also consider grouping VMs together based on the target RPO, for example grouping all Silver VMs together and all Bronze VMs together.
Generally, the more VPGs you have, the more granular control you will have over the environment and the more flexibility you will have when failing over or testing the product.
You have flexibility when it comes to your VPGs. Changing VPGs based on your changing needs is straightforward and easy.
Veeam Cloud Connect Replication (11)
Now that the setup is complete, it’s time to start consuming Zettagrid Cloud Connect replication resources. In Veeam terms, a Cloud Host is the abstracted view of Zettagrid’s replication platform, and seen as a remote virtualised host that can be used as a replication target. in Cloud Connect Replication jobs are configured in the same as standard Veeam Replication jobs with only the target is different. Click here to see how to configure a Cloud Replication Job.
Once all the selected virtual machines have at least one restore point replicated up to Zettagrid, you can use the failover resources to action a full failover. Before a Full Failover can initiated a failover plan must be configured. Click here to view how to create Failover Plans.
After a replication job targeted at Zettagrid completes, it can take a few minutes for the Veeam Backup & Replication console to retrieve changes from the database and display those changes on the tenant side. Click here to see how to view Replica Statuses.
With permanent failover, you can permanently switch from the original VM to a VM replica and use the VM replica on the cloud host as the original VM. Note that this is permanent and arrangements should be made with Zettagrid to continue running the VM within the Zettagrid IaaS Platform. Click here to view how to complete a Permanent Failover.
A partial failover is the scenario where you still have infrastructure up and running, and only one or more virtual machines are having issues. In this situation, a complete site failover isn’t required to solve the issue. Partial failover allows you to start the replica VM of one or more VMs at Zettagrid and let all the other VMs continue to run at your client side. Click here for a detailed overview.