{"id":9197,"date":"2026-09-21T20:23:35","date_gmt":"2026-09-21T14:53:35","guid":{"rendered":"https:\/\/www.veeble.com\/kb\/?p=9197"},"modified":"2026-09-21T20:23:35","modified_gmt":"2026-09-21T14:53:35","slug":"how-to-migrate-your-veeble-vps-from-openvz-to-kvm","status":"publish","type":"post","link":"https:\/\/www.veeble.com\/kb\/how-to-migrate-your-veeble-vps-from-openvz-to-kvm\/","title":{"rendered":"How to Migrate Your Veeble VPS from OpenVZ to KVM"},"content":{"rendered":"\n

Veeble is gradually decommissioning its legacy OpenVZ VPS infrastructure and moving customers to our KVM-based platform.<\/p>\n\n\n\n

If your VPS is currently running on OpenVZ, you will need to move your applications and data to a new KVM VPS before the migration deadline communicated to you.<\/p>\n\n\n\n

Because OpenVZ and KVM use fundamentally different virtualisation technologies, an existing OpenVZ VPS cannot simply be converted into a KVM VPS in place. Instead, Veeble will provision a new KVM VPS with the same or equivalent resource allocation, giving you a fresh server on which to rebuild your environment.<\/p>\n\n\n\n

You can then configure the new VPS according to your requirements and move your websites, databases, applications and other data from the existing OpenVZ VPS.<\/p>\n\n\n\n

Veeble’s support team can assist you with transferring data between the two servers.<\/p>\n\n\n\n

This guide explains how the migration works and what you need to do.<\/p>\n\n\n\n

\n\n\n

Why is Veeble moving from OpenVZ to KVM?<\/h2>\n\n\n

OpenVZ is a container-based virtualisation technology in which VPS instances share the kernel of the underlying host operating system.<\/p>\n\n\n\n

KVM, or Kernel-based Virtual Machine, provides full hardware virtualisation. Each VPS operates as an independent virtual machine with its own kernel and operating system environment.<\/p>\n\n\n\n

Moving to KVM provides a more modern and flexible virtualisation platform with better isolation between virtual machines and broader operating system compatibility.<\/p>\n\n\n\n

As part of our infrastructure upgrade, Veeble is therefore retiring its legacy OpenVZ nodes and moving customers to our KVM platform.<\/p>\n\n\n\n

\n\n\n

Can Veeble directly migrate my existing OpenVZ VPS to KVM?<\/h2>\n\n\n

No direct in-place conversion is available.<\/p>\n\n\n\n

Your existing OpenVZ container and a KVM virtual machine use different virtualisation architectures. Therefore, we cannot simply move the existing VPS image to a KVM node and boot it as the same server.<\/p>\n\n\n\n

Instead, the migration will follow this process:<\/p>\n\n\n\n

    \n
  1. Veeble provisions a new KVM VPS.<\/li>\n\n\n\n
  2. The existing OpenVZ VPS remains available during the migration period.<\/li>\n\n\n\n
  3. You configure the operating system, applications and services required on the new KVM VPS.<\/li>\n\n\n\n
  4. Your files, databases and other required data are transferred.<\/li>\n\n\n\n
  5. You test your applications on the new VPS.<\/li>\n\n\n\n
  6. DNS or other required network settings are changed to direct traffic to the new VPS.<\/li>\n\n\n\n
  7. After successful migration, the old OpenVZ VPS will be terminated.<\/li>\n<\/ol>\n\n\n\n

    This approach gives you an opportunity to move to a clean and updated server environment rather than carrying old system-level configurations into the new infrastructure.<\/p>\n\n\n\n

    \n\n\n

    What Veeble will provide<\/h1>\n\n\n

    For affected OpenVZ VPS customers, Veeble will provision a replacement VPS on our KVM infrastructure with the same or equivalent resource specification<\/strong> for your existing service.<\/p>\n\n\n\n

    The new VPS will be provided alongside your existing OpenVZ VPS during the migration period.<\/p>\n\n\n\n

    We will provide you with the necessary access details, including:<\/p>\n\n\n\n

      \n
    • New VPS IP address<\/li>\n\n\n\n
    • Root login information<\/li>\n\n\n\n
    • Operating system details<\/li>\n\n\n\n
    • VPS specifications<\/li>\n\n\n\n
    • Migration deadline<\/li>\n<\/ul>\n\n\n\n

      Your existing OpenVZ VPS will remain available during the migration window unless otherwise communicated in your migration ticket.<\/p>\n\n\n\n

      Veeble can also assist with transferring your data between the old and new servers<\/strong>.<\/p>\n\n\n\n

      \n\n\n

      What you need to do<\/h1>\n\n\n

      VPS services are self-managed environments, and every customer’s server configuration is different.<\/p>\n\n\n\n

      You are therefore responsible for preparing the software environment on your new KVM VPS.<\/p>\n\n\n\n

      Depending on what you currently run, this may include installing and configuring:<\/p>\n\n\n\n

        \n
      • Apache, Nginx or LiteSpeed<\/li>\n\n\n\n
      • PHP<\/li>\n\n\n\n
      • MySQL or MariaDB<\/li>\n\n\n\n
      • Node.js<\/li>\n\n\n\n
      • Python<\/li>\n\n\n\n
      • Java<\/li>\n\n\n\n
      • Docker<\/li>\n\n\n\n
      • cPanel or another control panel<\/li>\n\n\n\n
      • Mail services<\/li>\n\n\n\n
      • Firewall rules<\/li>\n\n\n\n
      • SSL certificates<\/li>\n\n\n\n
      • Cron jobs<\/li>\n\n\n\n
      • Application dependencies<\/li>\n\n\n\n
      • Custom services<\/li>\n\n\n\n
      • Security software<\/li>\n<\/ul>\n\n\n\n

        You should configure the new VPS according to your application’s requirements before transferring the final production data.<\/p>\n\n\n\n

        If you are unsure about your current server configuration, review it before beginning the migration.<\/p>\n\n\n\n

        \n\n\n

        Step 1: Take a backup of your existing VPS<\/h1>\n\n\n

        Before making any changes, create an up-to-date backup of your important data.<\/p>\n\n\n\n

        Depending on your server, this can include:<\/p>\n\n\n\n

          \n
        • Website files<\/li>\n\n\n\n
        • Application files<\/li>\n\n\n\n
        • Databases<\/li>\n\n\n\n
        • Email<\/li>\n\n\n\n
        • SSL certificates<\/li>\n\n\n\n
        • Configuration files<\/li>\n\n\n\n
        • Cron jobs<\/li>\n\n\n\n
        • User-generated content<\/li>\n\n\n\n
        • Application uploads<\/li>\n\n\n\n
        • Custom scripts<\/li>\n<\/ul>\n\n\n\n

          Do not rely only on the existing VPS remaining online during the migration period.<\/p>\n\n\n\n

          Keep an independent copy of any business-critical data before starting.<\/p>\n\n\n\n

          \n\n\n

          Step 2: Review your existing server<\/h1>\n\n\n

          Before configuring the new KVM VPS, identify what is currently running on your OpenVZ server.<\/p>\n\n\n\n

          Useful checks include:<\/p>\n\n\n

          Operating system<\/h3>\n\n\n
          cat \/etc\/os-release\n<\/code><\/pre>\n\n\n
          Web server<\/h3>\n\n\n
          For Apache:<\/p>\n\n\n\n
          httpd -v\n<\/code><\/pre>\n\n\n\n
          or:<\/p>\n\n\n\n
          apache2 -v\n<\/code><\/pre>\n\n\n\n
          For Nginx:<\/p>\n\n\n\n
          nginx -v\n<\/code><\/pre>\n\n\n
          PHP<\/h3>\n\n\n
          php -v\n<\/code><\/pre>\n\n\n
          Database<\/h3>\n\n\n
          mysql --version\n<\/code><\/pre>\n\n\n
          Disk usage<\/h3>\n\n\n
          df -h\n<\/code><\/pre>\n\n\n
          Running services<\/h3>\n\n\n
          On newer Linux distributions:<\/p>\n\n\n\n
          systemctl --type=service --state=running\n<\/code><\/pre>\n\n\n\n
          Make a note of important application versions, installed extensions and custom configurations.<\/p>\n\n\n\n
          This will help you recreate the required environment on the new VPS.<\/p>\n\n\n\n
          \n\n\n
          Step 3: Configure your new KVM VPS<\/h1>\n\n\n
          Once Veeble provisions the new VPS, log in using SSH.<\/p>\n\n\n\n
          For example:<\/p>\n\n\n\n
          ssh root@NEW_SERVER_IP\n<\/code><\/pre>\n\n\n\n
          Update the operating system and install the software required by your applications.<\/p>\n\n\n\n
          We strongly recommend using currently supported versions of the operating system and application stack wherever your application supports them.<\/p>\n\n\n\n
          Rather than copying the complete OpenVZ operating system to the new VPS, rebuild the server cleanly and transfer only the data and application configuration you actually require.<\/p>\n\n\n
          Do not copy the complete root filesystem<\/h3>\n\n\n
          Directories such as the following should generally not<\/strong> be copied directly from the OpenVZ server to the KVM VPS:<\/p>\n\n\n\n
          \/boot\n\/dev\n\/proc\n\/sys\n\/run\n<\/code><\/pre>\n\n\n\n
          System files under \/etc<\/code> should also be reviewed individually rather than blindly overwriting the configuration of the new server.<\/p>\n\n\n\n
          \n\n\n
          Step 4: Transfer your files<\/h1>\n\n\n
          After configuring the new environment, transfer your website and application data.<\/p>\n\n\n\n
          One common method is rsync<\/code>.<\/p>\n\n\n\n
          For example:<\/p>\n\n\n\n
          rsync -avz \/var\/www\/ root@NEW_SERVER_IP:\/var\/www\/\n<\/code><\/pre>\n\n\n\n
          The exact source and destination directories will depend on your server configuration.<\/p>\n\n\n\n
          You can also use:<\/p>\n\n\n\n
            \n
          • SCP<\/li>\n\n\n\n
          • SFTP<\/li>\n\n\n\n
          • rsync<\/li>\n\n\n\n
          • Control-panel migration tools<\/li>\n\n\n\n
          • Backup and restore tools<\/li>\n<\/ul>\n\n\n\n
            Veeble support can assist you with transferring data between the existing OpenVZ VPS and the new KVM VPS.<\/p>\n\n\n\n
            Please provide the required source and destination locations when requesting migration assistance.<\/p>\n\n\n\n
            \n\n\n
            Step 5: Migrate your databases<\/h1>\n\n\n
            For MySQL or MariaDB databases, we recommend transferring the databases using database dumps instead of directly copying raw database files.<\/p>\n\n\n\n
            For example:<\/p>\n\n\n\n
            mysqldump -u root -p database_name > database_name.sql\n<\/code><\/pre>\n\n\n\n
            Transfer the SQL file to the new VPS:<\/p>\n\n\n\n
            scp database_name.sql root@NEW_SERVER_IP:\/root\/\n<\/code><\/pre>\n\n\n\n
            Then import it:<\/p>\n\n\n\n
            mysql -u root -p database_name < database_name.sql\n<\/code><\/pre>\n\n\n\n
            For servers with multiple databases, you can also create a complete database backup.<\/p>\n\n\n\n
            Always verify that the database version on the new server is compatible with your application and the data being imported.<\/p>\n\n\n\n
            \n\n\n
            Step 6: Migrate other services<\/h1>\n\n\n
            Your VPS may contain more than website files and databases.<\/p>\n\n\n\n
            Check whether you also need to migrate:<\/p>\n\n\n
            Email<\/h3>\n\n\n
            If you host email directly on the VPS, configure the mail server and mailboxes on the new server before moving mail data.<\/p>\n\n\n
            Cron jobs<\/h3>\n\n\n
            Check the existing jobs using:<\/p>\n\n\n\n
            crontab -l\n<\/code><\/pre>\n\n\n\n
            Recreate the required jobs on the KVM VPS.<\/p>\n\n\n
            SSL certificates<\/h3>\n\n\n
            Reinstall or reissue SSL certificates after the websites are configured on the new VPS.<\/p>\n\n\n
            Firewall rules<\/h3>\n\n\n
            Recreate only the firewall rules required for the new environment.<\/p>\n\n\n
            Application configuration<\/h3>\n\n\n
            Update any application settings containing:<\/p>\n\n\n\n
              \n
            • Server IP addresses<\/li>\n\n\n\n
            • Database credentials<\/li>\n\n\n\n
            • File paths<\/li>\n\n\n\n
            • Hostnames<\/li>\n\n\n\n
            • API allowlists<\/li>\n\n\n\n
            • SMTP settings<\/li>\n\n\n\n
            • External firewall rules<\/li>\n<\/ul>\n\n\n\n
              \n\n\n
              Step 7: Test the new KVM VPS<\/h1>\n\n\n
              Do not change your production DNS immediately after transferring the data.<\/p>\n\n\n\n
              First test the application on the new VPS.<\/p>\n\n\n\n
              For websites, you can temporarily map the domain to the new IP using the hosts<\/code> file on your own computer. This allows you to access the website from the new server without changing public DNS.<\/p>\n\n\n\n
              Verify:<\/p>\n\n\n\n
                \n
              • Website pages<\/li>\n\n\n\n
              • Login areas<\/li>\n\n\n\n
              • Forms<\/li>\n\n\n\n
              • Database connections<\/li>\n\n\n\n
              • File uploads<\/li>\n\n\n\n
              • Scheduled tasks<\/li>\n\n\n\n
              • Email sending and receiving<\/li>\n\n\n\n
              • APIs<\/li>\n\n\n\n
              • Payment integrations<\/li>\n\n\n\n
              • SSL<\/li>\n\n\n\n
              • Application logs<\/li>\n\n\n\n
              • Background services<\/li>\n<\/ul>\n\n\n\n
                If you use a control panel such as cPanel, also verify all accounts and services from the new server.<\/p>\n\n\n\n
                \n\n\n
                Step 8: Prepare for the final migration<\/h1>\n\n\n
                Some websites continue receiving new data while you are migrating.<\/p>\n\n\n\n
                Examples include:<\/p>\n\n\n\n
                  \n
                • E-commerce orders<\/li>\n\n\n\n
                • Customer registrations<\/li>\n\n\n\n
                • Forum posts<\/li>\n\n\n\n
                • File uploads<\/li>\n\n\n\n
                • Emails<\/li>\n\n\n\n
                • Database changes<\/li>\n<\/ul>\n\n\n\n
                  If you copied your data several hours or days earlier, you should therefore perform a final synchronisation<\/strong> before changing traffic to the new server.<\/p>\n\n\n\n
                  For dynamic websites, you may need to briefly enable maintenance mode while performing the final database and file synchronisation.<\/p>\n\n\n\n
                  This prevents changes from being made on the old server after your final copy.<\/p>\n\n\n\n
                  \n\n\n
                  Step 9: Point your domain to the new server<\/h1>\n\n\n
                  Once testing is complete, update the required DNS records to the IP address of the new KVM VPS.<\/p>\n\n\n\n
                  For example:<\/p>\n\n\n\n
                  A    example.com       NEW_SERVER_IP\nA    www.example.com   NEW_SERVER_IP\n<\/code><\/pre>\n\n\n\n
                  If you use Cloudflare or another DNS provider, make the changes through that provider.<\/p>\n\n\n\n
                  If possible, reduce the DNS TTL before the planned migration. This can help DNS changes take effect more quickly during the final cutover.<\/p>\n\n\n\n
                  Your new KVM VPS may use a different IP address from your existing OpenVZ VPS. The IP details applicable to your migration will be provided in your support ticket.<\/p>\n\n\n\n
                  Do not assume that the existing IP address will automatically move to the new VPS.<\/p>\n\n\n\n
                  \n\n\n
                  Step 10: Monitor the new VPS<\/h1>\n\n\n
                  After switching traffic, monitor the new VPS carefully.<\/p>\n\n\n\n
                  Check:<\/p>\n\n\n\n
                  top\n<\/code><\/pre>\n\n\n\n
                  or:<\/p>\n\n\n\n
                  htop\n<\/code><\/pre>\n\n\n\n
                  and:<\/p>\n\n\n\n
                  free -h\ndf -h\n<\/code><\/pre>\n\n\n\n
                  Also review your application, web server and database logs for errors.<\/p>\n\n\n\n
                  Verify that users are reaching the new server and that all important services are operating normally.<\/p>\n\n\n\n
                  Do not consider the migration complete until you have tested the production application from the new VPS.<\/p>\n\n\n\n
                  \n\n\n
                  Step 11: Confirm the migration with Veeble<\/h1>\n\n\n
                  Once you have completed the migration and confirmed that the new KVM VPS is working correctly, update the migration support ticket.<\/p>\n\n\n\n
                  Our team can then record your migration as completed.<\/p>\n\n\n\n
                  The old OpenVZ VPS should no longer be used after the migration has been confirmed.<\/p>\n\n\n\n
                  \n\n\n
                  Complete the migration before your deadline<\/h1>\n\n\n
                  Each affected customer will receive a migration deadline through email or their Veeble support ticket.<\/p>\n\n\n\n
                  Please complete your server configuration, data transfer and testing before this date.<\/p>\n\n\n\n
                  The OpenVZ infrastructure is being decommissioned. Servers remaining on the legacy platform cannot be maintained indefinitely.<\/p>\n\n\n\n
                  Once the communicated migration period has ended, the old OpenVZ VPS may be terminated as part of the platform decommissioning process.<\/p>\n\n\n\n
                  For this reason, do not leave the migration until the final day<\/strong>.<\/p>\n\n\n\n
                  Start configuring and testing the replacement KVM VPS as soon as you receive its access details.<\/p>\n\n\n\n
                  \n\n\n
                  Who is responsible for what?<\/h1>\n\n\n
                  Task<\/th>Veeble<\/th>Customer<\/th><\/tr><\/thead>
                  Provision replacement KVM VPS<\/td>Yes<\/td><\/td><\/tr>
                  Provide VPS access details<\/td>Yes<\/td><\/td><\/tr>
                  Provide migration deadline<\/td>Yes<\/td><\/td><\/tr>
                  Install customer’s applications<\/td><\/td>Yes<\/td><\/tr>
                  Configure web\/database\/application stack<\/td><\/td>Yes<\/td><\/tr>
                  Recreate custom server configuration<\/td><\/td>Yes<\/td><\/tr>
                  Test applications<\/td><\/td>Yes<\/td><\/tr>
                  Verify migrated data<\/td><\/td>Yes<\/td><\/tr>
                  Assist with transferring files\/data between servers<\/td>Yes<\/td><\/td><\/tr>
                  Update external application configurations<\/td><\/td>Yes<\/td><\/tr>
                  Update DNS where managed by customer<\/td><\/td>Yes<\/td><\/tr>
                  Confirm successful migration<\/td>Support<\/td>Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  Our support team will assist with the infrastructure and data-transfer aspects of the migration. However, because every VPS can contain a different operating system, application stack and custom configuration, application-level rebuilding and validation remain the customer’s responsibility.<\/p>\n\n\n\n
                  \n\n\n
                  Frequently Asked Questions<\/h1>\n\n
                  Will my OpenVZ VPS automatically become a KVM VPS?<\/h2>\n\n\n
                  No. A new KVM VPS is provisioned separately. You must configure the new VPS and migrate the required data from your existing OpenVZ server.<\/p>\n\n\n
                  Will my existing data automatically appear on the new VPS?<\/h2>\n\n\n
                  No. The replacement KVM VPS starts as a fresh environment.<\/p>\n\n\n\n
                  Data must be transferred from your existing VPS.<\/p>\n\n\n\n
                  Veeble can assist you with the server-to-server data transfer.<\/p>\n\n\n
                  Will Veeble configure my new VPS exactly like my old server?<\/h2>\n\n\n
                  The VPS is a self-managed service.<\/p>\n\n\n\n
                  Veeble will provision the KVM VPS and can assist with transferring data. Installation and configuration of applications, packages, control panels and custom services are the customer’s responsibility unless a separate management service has been agreed.<\/p>\n\n\n
                  Will the new VPS have the same specifications?<\/h2>\n\n\n
                  We will provision the replacement with the same or equivalent resource allocation applicable to your existing VPS migration.<\/p>\n\n\n\n
                  The exact specifications will be provided in your migration ticket.<\/p>\n\n\n
                  Will my IP address remain the same?<\/h2>\n\n\n
                  IP will change <\/p>\n\n\n\n
                  Your new KVM server details, including its IP address, will be provided when the replacement VPS is provisioned.<\/p>\n\n\n
                  Will there be downtime?<\/h2>\n\n\n
                  The majority of the preparation can be completed while the old VPS remains online.<\/p>\n\n\n\n
                  A short service interruption may still be necessary during the final synchronisation and DNS\/application cutover, particularly for websites with frequently changing databases.<\/p>\n\n\n\n
                  Planning the final migration during a low-traffic period can help minimise the impact.<\/p>\n\n\n
                  Can Veeble move my files for me?<\/h2>\n\n\n
                  Yes. Our support team can assist with transferring the required data between the old OpenVZ VPS and the new KVM VPS.<\/p>\n\n\n\n
                  You remain responsible for ensuring that the applications on the destination server are correctly configured and for verifying that the transferred data works as expected.<\/p>\n\n\n
                  Can I keep using my OpenVZ VPS after the deadline?<\/h2>\n\n\n
                  No. The purpose of this migration is to decommission the  OpenVZ infrastructure.<\/p>\n\n\n\n
                  Customers should complete their migration before the deadline communicated by Veeble.<\/p>\n\n\n
                  Should I delete the old server immediately after migration?<\/h2>\n\n\n
                  We recommend first verifying the new KVM VPS thoroughly.<\/p>\n\n\n\n
                  Check your websites, databases, email, applications and other services before confirming that the migration is complete.<\/p>\n\n\n\n
                  Once the migration has been confirmed and the OpenVZ VPS is decommissioned, you should not rely on the old server as a backup.<\/p>\n\n\n\n
                  \n\n\n
                  Start your OpenVZ to KVM migration early<\/h1>\n\n\n
                  Moving from OpenVZ to KVM is more than simply moving a VPS from one node to another. The replacement KVM VPS is a fresh server environment, which means you have an opportunity to rebuild your services on our newer KVM infrastructure while retaining the data that matters.<\/p>\n\n\n\n
                  Once you receive your migration notification:<\/p>\n\n\n\n
                    \n
                  1. Log in to your new KVM VPS.<\/li>\n\n\n\n
                  2. Configure the applications and services you need.<\/li>\n\n\n\n
                  3. Back up your current OpenVZ VPS.<\/li>\n\n\n\n
                  4. Transfer your files and databases.<\/li>\n\n\n\n
                  5. Test the new server thoroughly.<\/li>\n\n\n\n
                  6. Perform the final synchronisation.<\/li>\n\n\n\n
                  7. Update DNS and other external configurations.<\/li>\n\n\n\n
                  8. Confirm the completed migration with Veeble.<\/li>\n<\/ol>\n\n\n\n
                    If you need assistance transferring data between your existing OpenVZ VPS and the new KVM server, open or reply to your Veeble support ticket and our technical team will assist you with the transfer.<\/strong><\/p>\n\n\n\n
                    Please make sure the migration is completed before the deadline provided in your migration notification.<\/p>\n\n\n\n
                    <\/p>\n","protected":false},"excerpt":{"rendered":"
                    Veeble is gradually decommissioning its legacy OpenVZ VPS infrastructure and moving customers to our KVM-based platform. If your VPS is currently running on OpenVZ, […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[1],"tags":[],"class_list":["post-9197","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false},"uagb_author_info":{"display_name":"Vipin Raj","author_link":"https:\/\/www.veeble.com\/kb\/author\/vipin\/"},"uagb_comment_info":0,"uagb_excerpt":"Veeble is gradually decommissioning its legacy OpenVZ VPS infrastructure and moving customers to our KVM-based platform. If your VPS is currently running on OpenVZ, […]","_links":{"self":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9197","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/comments?post=9197"}],"version-history":[{"count":1,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9197\/revisions"}],"predecessor-version":[{"id":9199,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9197\/revisions\/9199"}],"wp:attachment":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/media?parent=9197"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/categories?post=9197"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/tags?post=9197"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}