Backups and moving accounts in

This page covers two things under Customers: the backups the server keeps of your customers, and bringing accounts over from another hosting panel so they become your customers.

Your customers' backups

Open Customers › Backups. The page lists the server's backups of your customers' accounts. They are kept outside the customer's disk. Your hosting provider makes them on its own schedule and removes them; you cannot make or delete one here.

Pick a customer in the list at the top and press Show, or leave it on All customers. If you have more than 40 customers you must pick one first. Each row shows the customer, when the backup was taken, its size and what it contains.

Download a backup

Press Download on a row. Some old backups were made before downloading was possible and hold sign-in details that only the administrator may hand out. Those rows say Ask the administrator for a copy instead.

Restore a part of a customer's account

Press Restore on a row. A window lists the parts of that backup you can put back. Each part has its own button:

• Files: all of them, or one folder. Choose In place (same-named files are replaced, newer files stay) or Into a new folder (nothing is replaced). Logs are not restored.
• One database: replaces its contents with the backed-up copy. The database must still exist, so create it again first if it was deleted. You must tick Replace what is in it now.
• Email: messages come back. Mailboxes, passwords and filters are left as they are, and a mailbox must exist.
• DNS records, Certificates and HTTPS settings, Cron jobs, FTP users, Account settings and Site settings, where the backup holds them.

A restore runs in the background inside the customer's own limits. The page shows its progress and, when it finishes, what came back and anything that did not. You can leave the page and return.

Restoring a database, DNS records, cron jobs, FTP users or settings replaces what is there now. Anything changed since the backup is lost, so tell the customer first.

Your own copy: a remote destination

The server's backups are the administrator's. You can also keep an extra copy of your accounts at a place you control. Nothing is sent anywhere until you set it up.

This is on your own Files › Backups page, not on Customers › Backups. It has two parts.

1. Add your remote

1. Open Files › Backups and unfold Your remote.
2. Choose the kind of destination: FTP, SFTP, S3 or Google Drive.
3. Fill in the fields that kind asks for, then press Test and save. The panel writes a small test file there and removes it before saving.

The page has a How to set up each destination guide. Your own backups are sent to this remote and then removed from the server. You can later remove the remote with Remove the remote. The copies already there stay.

2. Send your customers' accounts to it

When your plan includes it, a second section called Your customers to your remote appears. If your plan does not include it, the section is not shown. Ask your hosting provider.

1. Unfold Your customers to your remote. It needs your remote from step 1 first.
2. Tick Back up my accounts to my remote.
3. Set How often (every day, week or month) and At (server time), and the days or dates if asked.
4. Under Accounts, untick any account you want left out. Your own account is in the list too.
5. Press Save.

Each account is backed up inside that account, sent to your remote in a folder of its own, and removed again. The account needs room for it only while it is made. You cannot schedule it inside the server's own backup time, and a run that lands in it waits. Press Back up now to run it once.

The table below shows the last copy of each account (Sent or Failed, with size and age). Press On my remote on a row to list that account's copies. Bring back copies one into the customer's own backups; it uses that account's disk. To restore from it, go to Accounts, open the customer, choose Log in, then Backups.

Moving accounts in

Open Customers › Import accounts. Accounts you import become your customers, on your own plans, and count in your allowance like any other customer. The old server is only read, and nothing is imported until you have seen a check.

Press New import, then choose the old panel and how:

By backup file

1. Upload the file into the import folder of your own account (File manager, FTP or SFTP). It counts in your disk until you delete it.
2. In New import, choose the panel and From a backup file (.tar.gz).
3. Enter the file's path and press Read the file and check it.

You import one file at a time. The folder-wide Read every file button is the administrator's.

Live from the old server

1. In New import, choose Live from the server and fill in the host and the SSH port, API port or key the form asks for. Press Save and connect.
2. For SSH, the form shows an import key. Add it to the old server's authorized_keys. For the API methods, make the token or key on the old server and allow this server's IP address for it.
3. The old server's firewall must let this server in on the ports the form names.
4. On the first connection the panel shows the old server's SSH key or certificate fingerprint. Compare it with the one on the old server, then confirm. A different key later stops the import.

A few limits apply to resellers:

• The old server must have a public address.
• Its ports must be 22, 443 or 1024 and above.
• You can keep 5 saved servers.
• You can make 60 connections to old servers in an hour.

Press Remove on a saved server when the move is finished, and take the import key out of the old server yourself.

Check, then import

1. Open a saved server's account list and tick the accounts, or press Check all. A file import goes straight to the check.
2. The Check before importing page shows each account as Ready or Needs a fix. Red must be fixed; amber is what changes on the way.
3. For every account, choose the plan it gets from your plans. Other fixes are offered on the row, such as Leave this domain out, Import under another name and Skip the account.
4. A domain that already exists on the server under another account is refused.
5. When every account is ready, press Start the import. The page follows each account as it is done.

The result page lists New passwords for anything that could not keep its own password, such as Webuzo mailboxes. Give these to the customer. Each site goes live here only when its domain's DNS points at this server.

Importing plans

On a saved server, press Packages to bring its packages over as plans. Tick the ones you want and press Import the ticked packages, or press Import all … new for every package not here yet. Each becomes a plan of yours, named with your account name in front. It is held to what you may hand out, and a plan with unlimited disk is not accepted. Accounts imported later are matched to these plans by name.

What comes over

Websites, databases, mail with its passwords where the old panel allows it, DNS records, certificates, cron jobs and FTP logins. A CyberPanel backup file holds no cron jobs, certificates or Docker apps; importing live brings those too. The check lists mailboxes that must get new passwords.

For the full detail on each panel see Moving accounts in.