Sky2 Technology for Macau, WordPress pricing and targeted restoration

Who Sky2 Technology may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

Traditional Chinese on the storefront.

Control panel

Server panel and interface languages not specified in the offering.

Support

Traditional Chinese advertised. Priority or dedicated support by plan. English and Portuguese to confirm.

Sky2 Technology for restoring one WordPress site in Macau

Sky2 Technology displays three WordPress offerings for Chinese-speaking businesses in Hong Kong, Macau and Taiwan. The company publishes a Hong Kong contact address. This profile targets a Macau studio managing two sites and wanting to restore just one. It needs to know whether a usable copy can be restored to a private target and whether the proposed restoration allows choosing its scope.

A daily backup reduces the interval between possible points. By itself, it does not identify the site within the file, files covered or restoration rights. A recently dated point can still be wrong for an installation. At the studio, both WordPress sites have pages with similar titles and archives can look alike.

The exercise uses archives represented by local objects and sample identifiers. It checks source site, component consistency and restoration target. It also observes the second site before and after simulation. The record distinguishes provider claims, what the team can test with its own data and what must be written into the quote.

Compare three annual prices and distinguish renewal

The Sky2 WordPress range displays three annual amounts in Hong Kong dollars. It offers a signup request and scope confirmation before activation. Plan cards give annual amount, site count and advertised retention for each plan. Record all three in the proposal before budgeting restoration. Consulted pages show neither a separate renewal rate, first-cycle promotion nor setup amount. First-invoice price, due date, renewal method and exit fees therefore still need reading in the proposal.

For the Macau studio, Business costs 1,592 HKD more annually than Entry. The difference notably buys an advertised capacity of three sites and fourteen-day retention. Two Entry plans would total 2,576 HKD at observed pricing if the provider accepts two subscriptions. This budget would be 304 HKD lower, but each site would have only 10 GB and seven-day retention. Also confirm whether two subscriptions actually separate access and restoration operations. Price alone establishes neither account scope nor intervention cost.

The Monetary Authority of Macao publishes a fixed central rate of 1 HKD to 1.03 MOP. The displayed 2,880 HKD is equivalent, for reference, to 2,966.40 MOP before possible bank fees. The British government business guide states that Macau has neither general sales tax nor VAT. The Sky2 page breaks down no tax and publishes a Hong Kong contact. Ask for invoice currency and quote details before applying tax treatment to this cross-border service. Sky2 publishes bank transfer and PayPal or card payment categories. That page specifies no cancellation deadline for the three WordPress plans.

Read quotas and data region

The range advertises 10, 30 and 100 GB NVMe storage. Site counts are one, three and no advertised fixed limit. The Enterprise card mentions guaranteed resources without quantifying CPU, memory, inodes or PHP limits. For three sites, ask whether storage is shared and whether there is a per-site, per-database or temporary-archive cap. For a test copy, check whether a subdomain or extra installation counts as a site. If an account already has two installations, a third slot on paper may help. It does not prove that the account has the space or permissions needed for restoration.

The storefront targets businesses in Macau, Hong Kong and Taiwan. The published contact is in Hong Kong. WordPress pages consulted specify neither the web server nor backup region for this range. For an activity requiring data in a specified region, obtain an answer covering files, databases and off-site copies and attach it to the contract. Until that information is available, treat region as an open condition. The scenario uses only sample data, allowing restoration methods to be examined independently of that decision.

The offering describes a free SSL certificate. For a private target, check whether a certificate can be issued for the test subdomain, what access-restriction methods exist and whether the account provides a separate database. A staging option is useful if it permits a separate target and controlled rollback. Otherwise, build an independent environment. For a studio hosting client sites, associate each site identifier with a domain, database and access account before comparing restoration options.

Check WordPress, languages and support scope

The WordPress page describes one-click installation after activation and support in Traditional Chinese. The public site is written in Traditional Chinese. Business mentions priority support and Enterprise dedicated support advertised 24 hours a day and 7 days a week. The contact page lists office hours Monday to Friday, 10 h to 18 h, excluding public holidays. Confirm the incident channel outside that window and human support languages. Public pages do not name this range’s server panel or languages actually available within the account. WordPress administration and hosting console must be treated separately.

The storefront presents maintenance and mail as catalog services. WordPress installation and SSL are specified in the hosting range. Consulted pages do not describe systematic core and plugin maintenance for every plan. Nor do they quantify an included AI assistant, generation credits or generative WordPress builder. For a studio, record tasks assigned to the provider, those assigned to the client and separately billed options.

Before importing to a private target, record PHP version, PHP extensions and database compatibility. If a backup came from another environment, also record theme version, plugin versions and permissions needed for media library writes. The goal is to open the restored site and identify any missing dependency before concluding the archive is unusable.

Associate a backup with the correct installation

Sky2 advertises daily backup with seven, fourteen or thirty days of retention depending on plan. Public pages do not detail covered objects, a common capture point for database and files, downloading capability or per-site granularity. Ask whether recovery can target an installation, database, directory or entire account. Also ask whether it can be performed on another target, by whom, in what time and at what price. Record plan-specific limits in the studio file. Retention is useful only if a usable point remains available when the incident is detected.

To avoid mixing two batches, assign each site an internal identifier, then use it in the archive name and in a sheet identifying source URL, database, time, time zone and size of each component. Calculate SHA-256 fingerprints for exported files and retain them with the manifest. A fingerprint proves a component matches the bytes whose fingerprint was recorded. It does not guarantee the component belongs to the right site or all necessary data was copied. Also check table prefix and a content identifier distinguishing the two sites.

A file archive captured after an addition and a database captured before it may contain mismatched references. Try to produce both components during one logical recovery point. If the provider identifies this point with a batch number instead of a single timestamp, retain the number and verify both components belong to it. The exercise simplifies this case by requiring strictly equal timestamps. A real process may use another shared identifier, provided its consistency is explained and verified. Store a copy containing messages or customer contact details in storage authorized for that purpose.

Rehearse restoration with two fictional sites

The mockup rejects three incompatible datasets and restores only the correct site’s private target. — Illustration by BlogPasCher.Open full-size illustration ↗

In the extracted ZIP directory, run node EXERCICE-SKY2-MO.cjs. The program handles three objects in memory: Atlas in production, Orbe in production and a private lab for Atlas. It compares the site identifier in both components, their capture point and the target’s role. A fingerprint calculated from each public site’s state verifies that neither changes during each simulation. Examples are neither Sky2 archives nor SQL files. The RESULTAT-SKY2-MO.json result records checks and final content of the represented target.

The first candidate mixes Atlas’s database with Orbe’s files. The check rejects this archive before any import. The second keeps Atlas files and database, but timestamps differ and it is rejected. The third has a consistent batch but targets Orbe in production. It is also rejected. The fourth uses the right components in the private lab. The program finds two pages and one media item in the lab. Atlas and Orbe production fingerprints remain identical. Assertions check all three rejections and these two invariants.

To adapt the exercise, add a dated copy of the same installation and check that you can distinguish the latest point from the actually desired point. If failure appears Tuesday, the latest point may already contain the regression. Find the sample content characterizing the selected point. Target identifier, database and directory should be checked in the same inventory. If an item is missing, leave the import pending and record the required evidence. The exercise tests neither the Sky2 panel nor real subscription permissions. It supplies checks the team can apply to its own restoration method.

Rehearse import on a private target

Prepare a protected target and a database not serving production. Record directory, database and authorized user names. Disable outgoing mail and external tasks on the copy. Restore the SQL file and files to this target using the procedure appropriate to the export. Adjust the database connection in the copy’s configuration. If its URL differs, follow a WordPress method that respects serialized data. Blind text substitution can damage it.

Before and after import, open the same pages on the second site and retain a marker of their last modification. On the Atlas copy, check a dated post, media item and editor access. Also check scheduled tasks and connections to other services. If a task triggers on the copy when it should remain active only in production, identify its trigger and disable it on the test target. Keep the time, method and verified result. An archive is usable only if someone can repeat those actions with the intended access.

If the provider can restore only a whole account, first use an independent copy in another environment. Copy only the components strictly necessary to restore Atlas after comparing them with the manifest. For the studio, the operational difference is the modified scope. Full account rollback can overwrite Orbe’s recent pages and settings even when Atlas recovery succeeds. Having a second person validate a private copy reduces the risk of choosing the wrong site or location.

Decide before authorizing restoration

The studio can choose Business if it needs two sites and the contract provides a usable method for restoring one. Three advertised slots may leave room for rehearsal. Check actual counting, available database and ability to restrict target access before planning this method. Two Entry plans may suit if each site fits its quota, seven-day points suffice and the provider confirms actual account separation. Enterprise adds longer advertised retention, but restoration scope remains a separate question.

Set an approval criterion identifying site name, recovery point identifier, component list, private address and target database. Also record sample content the verifier must find. The second site must retain its pages, media and scheduled tasks. If a command operates at account level, stop the test and restore the archive in a separate environment. On the copy, record the latest change and compare received component fingerprints with the manifest before any new import.

Before any intervention on the public site, copy its current state and list recent changes to retain. Some writes may have arrived after the selected backup date. Decide which will be reintegrated and who checks the result before restoring normal traffic. Rollback must target the same installation and remain possible while the current copy exists. Finally, choose the plan based on first-cycle cost, renewal terms, actually usable retention and evidence of targeted restoration. If processing region or access to copies conditions the studio contract, include that requirement in the quote before approving the plan.

Prepare your site

• WordPress requirements not met: check PHP and MySQL or MariaDB
• 25 WordPress backup tools by recovery need
• WordPress migration, staging and imports: choose the right tool
• Download the isolated restoration exercise