Why you need scheduled backups
Akeeba Backup is an excellent tool for taking backups of your site every time you want to transfer it to a different server, are ready to make substantial changes to it (like upgrading Joomla) or are about to or have just made changes to it. This way is something goes wrong you can easily roll back to the last known state of your site. The corollary to that is that if your backups are too far in between they might not encompass all useful changes to your site, leading to lost work and frustration.
This poses two concerns, depending on the type of site you have. If you have an infrequently changing site (low traffic blog, company presentation, organization bulletin board, ...) it takes a lot of self-dsicipline to take backups every time something changes, something that's not a given when you have multiple people managing a site. If you have a fast changing site (such as an e-commerce site, a busy blog with loads of comments, a community / forum site etc) you'd have to frequently log into your site and take backups, probably multiple times a day. This is admittedly time-consuming and boring. In the end of the day you might skip a few or a lot of backups and that could prove detrimental to your ability to rescue your site should things go awry.
The solution to that is scheduling your backups, i.e. having backups being taken automatically, at regular intervals. This is not something that will happen without any intervention by you, the site owner. Backups take too long to run in a single page load and need your site to maintain a fairly consistent state throughout the backup. Therefore having traffic to the site trigger the backups is a bad idea as it's neither guaranteed to come at the right frequency and quantity to guarantee a backup when you'd like it to happen, nor does it guarantee a consistent state, by definition (people accessing your site may indeed cause things to change). Ideally, your backups should run when your site experiences the least amount of traffic. If you're not sure when: check your hosting control panel's traffic logs and look for the time of the day you receive the lowest number of requests. From that, it should be fairly obvious that you need something else to trigger the backup.
An overview of scheduling methods
Akeeba Backup offers several options which are explained further below in this section of the documentation. This is a quick overview which will let you pick a method suitable for your site.
The first group of methods are designed to run on the same server as your site.
Depending on your hosting company you might be able to use CRON jobs. This is the preferred option. True CRON jobs allow you to run custom scripts or commands accessible from the command line (CLI) at regular intervals. However, some hosts may limit the amount of time CRON jobs are allowed to run. If this time is less than the time it takes to run a backup this method is unsuitable for you. If you're not sure how long the backup takes: take a backup from the back-end of your site, go to the Manage Backups page and look at how long it took to run it. You can use the Native CRON Script and the Alternative CRON Script with this method.
On other servers you might be able to use pseudo-CRON jobs. In this case you can tell your host to access a specific URL at regular intervals. Please ask your host whether their pseudo-CRON follows HTTP redirections and if it does, whether it has a limit of redirections followed. If they answer that they do not follow HTTP redirections or that they impose a limit of redirections followed you cannot use this method. Furthermore, the time limits explained in the previous paragraph apply.
If the previous methods which rely on your own server are not suitable for your site, Akeeba Backup does offer two alternatives.
The first alternative is the Front-end Legacy Backup API. You can use a special URL with third party CRON services which follow HTTP redirections and do not impose a limit of redirections followed such as WebCRON or even a shell script using wget, curl or something similar on any server or Internet connected computer under your control. For example, you could set up a CRON job on your Linux machine, a Scheduled Task on your Windows computer or even have a Raspberry Pi or your NAS access that URL. If you use a third party service to trigger the backups be advised that they charge fees which are usually pretty low.
The second alternative is the Akeeba Backup Remote JSON API. This is a more advanced way of taking backups remotely. It is used in two distinct cases. First, in conjunction with our remote backup software, namely Akeeba Remote CLI and Akeeba UNiTE. These can be used to schedule taking backups remotely and, in the case of UNiTE, restoring them on a computer under your control as well. Second and most common, with a third party service that can schedule and take remote backups using Akeeba Backup's Remote JSON API such as BackupMonkey, or Watchful. Third party services charge fees according to their commercial policy.
Availability of scheduling methods
Backup scheduling features are only available in Akeeba Backup Professional, our for-a-fee edition. They are not included in Akeeba Backup Core, our free of charge edition.
The target audience of Akeeba Backup Core has always been the small, hobbyist site owner and those who need a relatively easy way to transfer their sites between servers. This target audience does not need backup scheduling, either because their sites change too infrequently or because they perform one-off backups for site transfers.
If you find yourself with a site that changes often enough to warrant automatic backups we kindly ask you to consider an Akeeba Backup Professional subscription. There are several good reasons to do so. For starters, a site valuable enough to warrant automatic backups should also have these backups stored off-site, a feature exclusive to the Professional edition. Moreover, your small investment in Akeeba Backup Professional will save you copious amounts of time and money should something go awry. Furthermore you will have access to our acclaimed support, provided by the same developers writing the software, should you have any issue using it. It's worth noting that if you are a web professional you only need one subscription for unlimited sites, including those of your clients. Finally, by purchasing an Akeeba Backup Professional subscription you are financing the painstaking and expensive research, development and maintenance that goes into Akeeba Backup – thank you for making this software possible!
Scheduling backups
Each available backup method has a different way of scheduling. This documentation section explains in detail how each method works and how you can schedule it.
You should also go to Akeeba Backup's Schedule Automatic Backups page. You will get a condensed version of these instructions, specialized -to the degree possible- for your own site and the currently active backup profile. Trust us, this page will save you a lot of headache. In fact, it's what we reference on our own sites.
 | Tip |
|---|---|
| This feature is only available in Akeeba Backup Professional. Requires the Enable Legacy Front-end Backup API (remote CRON jobs) option to be enabled in the component's Options, Frontend tab. |
The front-end backup feature is intended to provide the capability to perform an unattended, scheduled backup of your site.
The front-end backup URL performs a single backup step and sends a redirection (HTTP 302) header to force the client to advance to the next page, which performs the next step and so forth. You will only see a message upon completion, should it be successful or not. There are a few limitations, though:
-
It is not designed to be run from a normal web browser, but from an unattended cron script, utilizing wget or cron as a means of accessing the function.
-
The script is not capable of showing progress messages.
-
Normal web browsers tend to be "impatient". If a web page returns a bunch of redirection headers, the web browser thinks that the web server has had some sort of malfunction and stop loading the page. It will also show some kind of "destination unreachable" message. Remember, these browsers are meant to be used on web pages which are supposed to show some content to a human. This behaviour is normal. Most browsers will quit after they encounter the twentieth page redirect response, which is bound to happen. Do not report a "bug" stating that Firefox, Internet Explorer, Chrome, Safari, Opera or another browser doesn't work with the front-end backup feature. It was NOT meant to work by design and you've been sufficiently warned.
-
Command line utilities, by default, will also give up loading a page after it has been redirected a number of times. For example, wget gives up after 20 redirects, curl does so after 50 redirects. Since Akeeba Backup redirects once for every step, it is advisable to configure your command line utility with a large number of redirects; about 10000 should be more than enough for virtually all sites.
| Tip |
|---|---|
| If you want to automate your backups despite your host not supporting proper CRON jobs you can use a third party service, such as Webcron.org. Just make sure you set up the time limit to be at least 10% more than the time it takes for Akeeba Backup to backup your site. Don't know how much is that? Just take a regular backup from your site's back-end, then go to the Manage Backups page and take a look at the Duration column. |
We VERY STRONGLY recommend using the Front-End Backup feature only with sites configured to use HTTPS with a properly signed SSL certificate for security reasons: plain HTTP sites and self-signed HTTPS certificates can, under certain circumstances, lead to your Secret Word leaking. If a malicious user obtains the Secret Word they can launch a Denial of Service attack on your site and / or abuse Akeeba Backup's feature to obtain a copy of your site, including all privileged information. Getting a properly signed SSL certificate no longer costs any money. The Let's Encrypt certificate authority offers free of charge SSL certificates. Most likely your hosting control panel already supports automatically acquiring and installing SSL certificates from Let's Encrypt. For example two of our favorite hosts, SiteGround and Rochen, have supported this since late 2015. If you are not sure, ask your host. Using HTTPS not only makes your site safer, it will even make it more popular with search engines. It's a win-win proposition!
Before beginning to use this feature, you must set up Akeeba Backup to support the front-end backup option. First, go to Akeeba Backup's main page and click on the Options button in the toolbar. Find the option titled Enable front-end and remote backup and set it to Yes. Below it, you will find the option named Secret key. In that box you have to enter a password which will allow your CRON job to convince Akeeba Backup that it has the right to request a backup to be taken. Think of it as the password required to enter the VIP area of a night club. After you're done, click the Save & Close button on top to save the settings and close the dialog.
| Tip |
|---|---|
| Use only lower- and upper-case alphanumeric characters (0-9, a-z, A-Z) in your secret key. Do not use symbols, accented characters, non-Latin character sets (like Green or Cyrillic letters) etc. Such characters may need to be manually URL-encoded in the CRON job's command line. This is error prone and can cause the backup to never start even though you'll be quite sure that you have done everything correctly. |
Most hosts offer a CPanel of some kind. There has to be a section for something like "CRON Jobs", "scheduled tasks" and the like. The help screen in there describes how to set up a scheduled job. One missing part for you would be the command to issue. Simply putting the URL in there is not going to work.
 | Warning |
|---|---|
| If your host only supports entering a URL in their "CRON" feature, this will most likely not work with Akeeba Backup. There is no workaround. It is a hard limitation imposed by your host: they do NOT follow redirections. In these cases you can schedule a CRON job on your own computer. The downside is that your computer will need to be powered on (not turned off or even in sleep / hibernate) at the time you've set up the backup to run and for the entire length of time it take to run the backup. |
If you are on a UNIX-style OS host (usually, a Linux host) you most probably have access to a command line utility called wget. It's almost trivial to use:
wget --max-redirect=10000 "http://www.yoursite.com/index.php?option=com_akeeba&
view=backup&key=YourSecretKey"
Of course, the line breaks are included for formatting clarity only. You should not have a line break in your command line!
Do not miss the --max-redirect=10000 part of the wget command! If you fail to include it, the backup will not work with wget complaining that the maximum number of redirections has been reached. This is normal behavior, it is not a bug.
YourSecretKey must be URL-encoded. You can use an online tool like http://www.url-encode-decode.com or simply consult the Schedule Automatic Backups page.
Do not forget to surround the URL in double quotes. If you don't the backup will fail. The reason is the way operating systems parse command lines. Special characters such as question marks and ampersands have special meanings.
If you're unsure whether your command line makes sense please check with your host. Sometimes you have to get from them the full path to wget in order for CRON to work. For example:
/usr/bin/wget --max-redirect=10000 "http://www.yoursite.com/index.php?option=com_akeeba&
view=backup&key=YourSecretKey"
Again, please do contact your host; they usually have a help page for all this stuff. Read also the section on CRON jobs below.
Optionally, you can also include an extra parameter to the above URL, &profile=profile_id, where profile_id is the numeric ID of the profile you want to use for the backup. If you don't specify this parameter, the default backup profile (ID=1) will be used. In this sense, the aforementioned URL becomes:
/usr/bin/wget --max-redirect=10000 "http://www.yoursite.com/index.php?option=com_akeeba&
view=backup&key=YourSecretKey&profile=profile_id"
wget is multi-platform command line utility program which is not included with all operating systems. If your system does not include the wget command, it can be downloaded at this address: http://wget.addictivecode.org/FrequentlyAskedQuestions#download. The wget homepage is here: http://www.gnu.org/software/wget/wget.html. Please note that the option --max-redirect is available on wget version 1.11 and above. If you are on an incredibly outdated server with wget version 1.10 and earlier the backup will most probably result into an error message concerning the maximum redirections limit being exceeded. This is not a bug in our software, it's a limitation of an ancient version of the third party wget software. Kindly note that version 1.11 which lifts that limitation was released ages ago, in 2008 (two thousand eight!) to be more precise.
| Warning |
|---|---|
| The ampersands above should be written as a single ampersand, not as an HTML entity (&). Failure to do so will result in a 403: Forbidden error message and no backup will occur. This is not a bug in our software, it's how the Internet works. |
We would like to note that some SEO or SEF URL extensions for Joomla! may get in the way of front-end backups, especially on multi-language sites. If you get inexplicable 403 or 404 errors towards the beginning of a front-end backup right after a redirection (HTTP code 301, 302 or 307) please consult with the developers of the SEO / SEF URL extensions you are using. Usually you can add an exception for Akeeba Backup's front-end backup URLs.
Furthermore, some hosts with very finicky web server firewalls may automatically block the front-end backup URL. Typically you get a 403 error at the very beginning of the backup process or after 2-3 redirections (at which point the front-end backup will no longer work). This typically happens when they misunderstand the front-end backup Secret Word as a security threat. Try changing your Secret Word to something else. If the problem persists please contact your host and ask them to take a look and add an exception for the front-end backup Secret Word you are using.
Using webcron.org to automate your backups
Assuming that you have already bought some credits on webcron.org, here's how to automate your backup using their service.
First, go to Akeeba Backup's main page (Control Panel) and click on the Options button in the toolbar. Find the option titled Enable front-end and remote backup and set it to Yes. Below it, you will find the option named Secret key. Type in a secret key. We strongly recommend using only alphanumeric characters, i.e. 0-9, a-z and A-Z. For the sake of this example, we will assume that you have entered ak33b4s3cRet in that field. We will also assume that your site is accessible through the URL http://www.example.com.
Log in to webcron.org. In the CRON area, click on the New Cron button. Here's what you have to enter at webcron.org's interface:
-
Name of cronjob: anything you like, e.g. "Backup www.example.com"
-
Timeout: 180sec; if the backup doesn't complete, increase it. Most sites will work with a setting of 180 or 600 here. If you have a very big site which takes more than 5 minutes to back itself up, you might consider using Akeeba Backup Professional and the native CRON script (akeeba-backup.php) instead, as it's much more cost-effective.
-
Url you want to execute:
http://www.example.com/index.php?option=com_akeeba&view=backup&key=ak33b4s3cRet -
Login and Password: Leave them blank
-
Execution time (the grid below the other settings): Select when you want your CRON job to run
-
Alerts: If you have already set up alert methods in webcron.org's interface, we recommend choosing an alert method here and not checking the "Only on error" so that you always get a notification when the backup CRON job runs.
Now click on Submit and you're all set up!
A PHP alternative to wget
As user DrChalta pointed out in a forum post, there is an alternative to wget, as long as your PHP installation has the cURL extension installed and enabled. For starters, you need to save the following PHP script as backup.php somewhere your host's cron feature can find it. Please note that this is a command-line script and needn't be located in your site's root; it should be preferably located above your site's root, in a non web-accessible directory.
The script below is a modification over DrChalta's original script, taking into account changes made in later versions of our software. In order to configure it for your server, you only have to change the first three lines.
<?phpdefine('SITEURL', 'http://www.example.com'); // Base URL of your sitedefine('SECRETKEY', 'MySecretKey'); // Your secret keydefine('PROFILE',1); // The profile's ID// ====================== DO NOT MODIFY BELOW THIS LINE ======================$curl_handle=curl_init();curl_setopt($curl_handle,CURLOPT_URL,SITEURL.'/index.php?option=com_akeeba&view=backup&key='.SECRETKEY.'&profile='.PROFILE);curl_setopt($curl_handle,CURLOPT_FOLLOWLOCATION,TRUE);curl_setopt($curl_handle,CURLOPT_MAXREDIRS,10000); # Fix by Nicholascurl_setopt($curl_handle,CURLOPT_RETURNTRANSFER,1);$buffer = curl_exec($curl_handle);curl_close($curl_handle);if (empty($buffer)) echo "Sorry, the backup didn't work.";else echo $buffer;?> Where www.yoursite.com and YourSecretKey should be set up as discussed in the previous section.
The ampersands above should be written as a single ampersand, not as an HTML entity (&).
In order to call this script with a schedule, you need to put something like this to your crontab (or use your host's CRON feature to set it up):
0 3 * * 6/usr/local/bin/php/home/USER/backups/backup.php
Where /usr/local/bin/php is the absolute path to your PHP command-line executable and /home/USER/backups/backup.php is the absolute path to the script above.
If you set up your cron schedule with a visual tool (for example, a web interface), the command to execute part is "/usr/local/bin/php /home/USER/backups/backup.php".
Thank you DrChalta for this wonderful tip!
Using the front-end backup in SiteGround and other hosts using cURL instead of wget
As one of our users pointed out in the support forum, finding the correct command to issue for the CRON job is tricky. What he writes applies not only to his host, SiteGround, but many other commercial hosts as well. We'll simply quote our user, bzcoder.
In the CPanel for SiteGround there is a cronjob option, you create a cronjob using that and use:
curl -b /tmp/cookies.txt -c /tmp/cookies.txt -L --max-redirs 1000 -v "<url>"
as your command.
Replace <url> with your backup URL. Make sure to use the initial url displayed on the backend NOT the final URL when you run the backup manually (been there, done that) - when you do that you end up with a url that doesn't work because of the extra parameter used in continuing the backup process.
| Tip |
|---|---|
| This feature is only available in Akeeba Backup Professional. Requires the Enable JSON API (remote backup) option to be enabled in the component's Options, Frontend tab. |
This feature is designed to let third party services and software take and optionally download backups of your site remotely (from any computer or a server other than the one your site is hosted on). This API is currently used by popular Joomla management and backup scheduling services such as Backup Monkey, and Watchful.
The JSON API uses optional encryption to ensure confidentiality of the API calls even on plain HTTP sites. However, we very strongly recommend that you use the JSON API over HTTPS connections. On most servers you can install an SSL certificate from Let's Encrypt at no additional cost. Please consult your host.
Things you should know:
-
It is not designed to be run from a web browser, but from an application or service which understands the API.
-
The API is available through the Akeeba Backup component which runs inside Joomla. While we take reasonable precautions, third party plugins may interfere with it. These problems are very rare.
-
Since it's running over the web it is subject to the PHP and web server timeout limits. Make sure your backup runs to completion through the back-end of your site before using the JSON API. If your backup fails through the back-end it will definitely fail through the JSON API as well.
-
Since it's running over the web your host may intercept, alter or block the requests to the JSON API and its replies. If that happens taking a backup will be impossible or may terminate before it is complete. In this case please contact your host. They should be able to determine why they interfered with the request and help you work around it.
-
Giving access to the Remote JSON API is not to be taken lightly. Software and services given access to your site's Akeeba Backup Remote JSON API have the authority to see information about your past backups, get information about the version and update availability of Akeeba Backup, read and modify your backup settings (including remote storage services' access information), take backups and download backup archives. Only give access to services and software you trust.
-
Downloading a backup archive through the JSON API is by no means guaranteed to work. It largely depends on the size of the backup archive and your host. Our advice to third party services and software is to always offer an alternative for downloading the backup archives using SFTP or FTP.
-
Access to the Remote JSON API has many intermediate layer which are not under the control of Akeeba Ltd. Indicatively these are: the code which produces the request to the JSON API; the operating system and server / computer configuration where the code producing the request to the JSON API is installed in, including its firewall configuration; network connectivity between that server / computer and your site's server; your site server's firewall and system configuration; your server's web server and PHP configuration; any third party plugins running on your Joomla site. If you can take a backup through your site's back-end but not through the remote JSON API do not assume it's a bug with our software (99.9% of the times it's not). First contact the developer of the third party service or software which implements the remote backup. That's a small community, we know them and they know us. They can identify whether the problem is on their end, on your server or if it's a backup issue. If you do have a backup issue and are already a subscriber with access to Akeeba Backup's support (that is to say, you have access to Akeeba Backup Professional) please file a support ticket on our site's Support section and we will help you.
-
If you are trying to run remote backups from your own server or computer we have limited troubleshooting options for clients who qualify for support. Namely, we will try to run the backup through our own computers and servers and try to determine the root cause of the issue. If it's outside our client software or the Akeeba Backup installation on your site we can only tell you that it's not a bug in our software and tell you about what could be interfering (see the above bullet points). In this case the root cause is outside our control and we cannot reasonably be expected to resolve it.
-
Your secret key must be non-empty and meet a minimum complexity metric for this feature to be enabled. If you have not set up a secret key or if the secret key is too easy to guess the JSON API will respond with an access denied message and Akeeba Backup will display a prominent warning in its control panel page with instructions to fix it.
Setting up third party services
Each third party service has a slightly different way to set up the connection with Akeeba Backup's Remote JSON API. In most cases you install an extension on your site and the third party service can set up the connection automatically. They do so by reading the Secret Key you have set up in Akeeba Backup's Options page and using the known endpoint URL to Akeeba Backup's JSON API.
In some cases you may need to provide either or both of these pieces of information to the third party service. The set up for third party software below explains how to obtain that information.
Setting up software
Setting up software for remote backups through the JSON API requires providing either or both of the following information:
Endpoint URL: It is https://www.example.com/index.php?option=com_akeeba&view=Json&format=raw where https://www.example.com is the full URL to your site's front page. Akeeba software which implements the JSON API (Akeeba Remote Control and Akeeba UNiTE) can only be given the full URL to your site; they will figure out the rest of the URL automatically.
Secret Key: This is the secret key you set up in Components, Akeeba Backup, Options, Front-end Backup tab, Secret word option. We recommend using a random, 64-character password generated with a random password generator as explained in the documentation page of the Options page of Akeeba Backup. If the secret key you provide to the third party software or service does not match the one you set up in Akeeba Backup, or if the secret key you set up in Akeeba Backup is too easy to guess (based on automated password complexity metrics) the JSON API will always respond with an access denied message.
Support for backup issues when using the JSON API for remote backups
If you are using Akeeba Remote CLI or Akeeba UNiTE and qualify for support according to our Terms of Service we can provide substantial but not unlimited assistance. We can identify whether your connection information is correct (or let you know how to correct it). Moreover, we can determine whether the problem is with our software or outside or of our control. In the first case we will identify the issue in our software and fix it. In the latter case we will tell you our analysis, where we believe the problem lies to, produce evidence that the backup can be run from our computers or servers and try to point you to the correct direction for resolving the issue that's not coming from our software itself.
When it comes to third party services we kindly ask you to always seek support with the service provider before contacting us. In many cases the problem lies with the service itself or its connection to your server. We do not have access to these third party services and cannot troubleshoot or resolve such issues. The service providers can. If you ask us to assist with such third party service issues we will have to decline support for objective reasons.
If the service provider tells you that you have a backup issue your support options are determined by the Support Policy which is part of our Terms of Service. That is to say, if you qualify for support according to our Terms of Service we can provide assistance for your backup issue with the JSON API in the same way we would provide assistance for any other backup issue. If you do not qualify for support we will not be able to provide assistance with your issue. Please note that the REMOTEAPI subscription does not give you access to our support services.
You might wonder why we cannot help you even though you are paying a substantial fee to the third party service to schedule your site's backups with Akeeba Backup. Third party services are not affiliated with us, they do not pay us to provide support to their clients and do not contribute financially to the development and maintenance of Akeeba Backup. As a result, being a client of a third party service which schedules backups with Akeeba Backup does not automatically entitle you to support from us.
As for why the REMOTEAPI subscription does not entitle you to support: factoring in support costs to the REMOTEAPI subscription would nearly triple its price which makes it unaffordable for its target audience i.e. the people who can't afford an Akeeba Backup Professional subscription. Making this decision did not come easy; it took 18 months of deliberation and shooting down ideas which were financially fair to us but either ethically challenging or impractical. We feel that it was the best compromise on ethics and financial viability. If it was a fair world, third party backup scheduling services would be willing to pay us €0.15 per month and client which would have enabled us to include the JSON API and legacy API plugins in the Core version, removing the need for the REMOTEAPI subscription.
| Tip |
|---|---|
| This feature is only available in Akeeba Backup Professional. |
If you have access to the command-line version of PHP, Akeeba Backup Professional includes an even better - and faster - way of scheduling your backups. The file cli/akeeba-backup.php can be executed from the command-line PHP interface (PHP CLI). It doesn't require the front-end backup in order to work; it is a self-contained, native backup for your Joomla!™ site, even if your web server is down.
In order to schedule a backup, you will have to use the following command line to your host's CRON interface:
/usr/local/bin/php/home/USER/webroot/cli/akeeba-backup.php
where /usr/local/bin/php is the path to your PHP CLI executable and /home/USER/webroot is the absolute path to your web site's root. You can get this information from your host.
The backup script accepts three optional parameters:
-
--profile
profile_idallows you to select which backup profile you would like to use for the scheduled backup. Theprofile_idis the numeric profile ID you can see in your Control Panel page. -
--description "
Your description" allows you set a backup description different than the default. Do not forget to enclose your description in double quotes, or this parameter will not work! Since Akeeba Backup 3.1 the description supports Akeeba Backup's backup naming variables, e.g.[SITE],[DATE]and[TIME]. This allows you to use them in conjunction with this parameter to provide flexible backup descriptions. -
--override "keyname=value" allows you to override profile configuration variables. This parameter can appear an unlimited number of times in the command line. It can be used, for example, to provide the username and password to your cloud storage service in the command line, without having to store it in the backup profile's configuration, therefore never storing it in database and hiding it from other administrators. Please take a look at the "Overriding configuration variables" subsection for more information.
-
--quiet will suppress all output except warnings and error messages. If the backup runs successfully you get no output at all. Note: this option was added in Akeeba Backup Professional 3.3.4.
The akeeba-backup.php script will return a different exit code, depending on the backup status. When the backup is successful and without warnings, the exit code will be 0. When the backup completed but with warnings, the exit code will be 1. Finally, if the backup fails, the exit code will be 2. This allows you to check the backup status, for example inside a shell script, for automation purposes.
In order to give some examples, I will assume that your PHP CLI binary is located in /usr/local/bin/php - a common setting among hosts - and that your web site's root is located at /home/johndoe/httpdocs.
-
Backup with the default profile (ID = 1) and default description:
usr/local/bin/php /home/johndoe/httpdocs/cli/akeeba-backup.php
-
Backup with profile number 2 and default description:
usr/local/bin/php /home/johndoe/httpdocs/cli/akeeba-backup.php --profile=2
-
Backup with the default profile (ID = 1) and a description reading "My automated backup":
usr/local/bin/php /home/johndoe/httpdocs/cli/akeeba-backup.php --description="My automated backup"
-
Backup with profile number 2 and a description reading "My automated backup":
usr/local/bin/php /home/johndoe/httpdocs/cli/akeeba-backup.php --profile=2 --description="My automated backup"
It goes without saying that the line breaks are for readability only. You should not include line breaks in your command line.
Special considerations:
-
All parameters must start with a double dash. If you use a single dash, they will be ignored. This is a limitation of Joomla's CLI application interface –used by our script– which follows the UNIX conventions of command line parameters.
-
Most hosts do not impose a time limit on scripts running from the command-line. If your host does and the limit is less than the required time to backup your site, the backup will fail.
-
This script is not meant to run from a web interface. If your host only provides access to the CGI or FastCGI PHP binaries or pseudo-CRON (accessing a URL on a schedule),
akeeba-backup.phpwill not work with them. The reason is actually the same as the time constraint above. -
Some servers do not fully support this backup method. The usual symptoms will be a backup which starts but is intermittently or consistently aborted in mid-process without any further error messages and no indication of something going wrong. In such a case, trying running the backup from the back-end of your site will work properly. If you witness similar symptoms please use the Alternative CRON Script, outlined in the next section.
Setting up a CRON job on cPanel
 | Note |
|---|---|
| This section depends on your host's control panel software. It is included it for informational purposes only and we cannot guarantee its accuracy. If you have questions about this please ask your host. |
Go to your cPanel main page and choose the CRON Jobs icon from the Advanced pane. In the Add New CRON Job box on the page which loads, enter the following information:
- Common Settings
-
Choose the frequency of your backup, for example once per day.
- Command
-
Enter your backup command. Usually, you have to use something like:
/usr/bin/php5-cli /home/
myusername/public_html/cli/akeeba-backup.php --profile=YourProfileIDwhere
myusernameis your account's user name (most probably the same you use to login to cPanel) andYourProfileIDis the numeric profile number you want to use for your backup job. Do note the path for the PHP command line executable:/usr/bin/php5-cli. This is the default location of the correct executable file for cPanel 11 and later. Your host may use a different path to the executable. If the command never runs, ask them. We can't help you with that; only those who have set up the server know the changes they have made to the default setup.
Finally, click the Add New Cron Job button to activate the CRON job.
Special considerations for HostGator
| Note |
|---|---|
| This section depends on your host's control panel software. It is included it for informational purposes only and we cannot guarantee its accuracy. If you have questions about this please ask your host. |
The location of the PHP CLI binary is /usr/bin/php-cli. This means that your CRON command line should look like:
/opt/php53/bin/php /home/myusername/public_html/cli/akeeba-backup.php --profile=YourProfileID
Overriding configuration variables
You can override or supply missing configuration variables in the command line. This is especially useful for security reasons. One security issue with the cloud storage service integration is that other Super Users can peek at Akeeba Backup's configuration and read the username, password or API keys used to access the cloud storage service. You can, however, leave these fields blank in the configuration and supply their values in the command line.
Overriding a configuration variable requires knowing its key name. The key names are represented in dot-format, i.e. engine.postproc.s3.accesskey for Amazon S3's access key. Determining the key name is quite easy, as they are stored in INI files throughout the component's back-end. The first location you should look at is administrator/components/com_akeeba/engine/core, where you will find four INI files with general settings. Inside the administrator/components/com_akeeba/engine subdirectories you will find one INI file per engine.
In order to save you from trouble, here are the most useful key names. The names are designed to be self-explanatory.
- JPS archive password
-
-
engine.archiver.jps.key
-
- ANGIE password
-
-
engine.installer.angie.key
-
- Amazon S3
-
-
engine.postproc.s3.accesskey
-
engine.postproc.s3.secretkey
-
- Microsoft Windows Azure BLOB Storage
-
-
engine.postproc.azure.account
-
engine.postproc.azure.key
-
- RackSpace CloudFiles
-
-
engine.postproc.cloudfiles.username
-
engine.postproc.cloudfiles.apikey
-
- CloudMe
-
-
engine.postproc.cloudme.username
-
engine.postproc.cloudme.password
-
- DreamObjects
-
-
engine.postproc.dreamobjects.accesskey
-
engine.postproc.dreamobjects.secretkey
-
- Dropbox (v1 API, old)
-
-
engine.postproc.dropbox.token
-
engine.postproc.dropbox.token_secret
-
- Dropbox (v2 API, new)
-
-
engine.postproc.dropbox2.access_token
-
- Remote FTP server
-
-
engine.postproc.ftp.user
-
engine.postproc.ftp.pass
-
- Google Drive
-
-
engine.postproc.googledrive.refresh_token
-
- Google Storage
-
-
engine.postproc.googlestorage.accesskey
-
engine.postproc.googlestorage.secretkey
-
- iDriveSynce
-
-
engine.postproc.idrivesync.username
-
engine.postproc.idrivesync.password
-
engine.postproc.idrivesync.pvtkey
-
- OneDrive
-
-
engine.postproc.onedrive.access_token
-
engine.postproc.onedrive.refresh_token
-
- Remote SFTP server
-
-
engine.postproc.sftp.user
-
engine.postproc.sftp.pass –– Either the password for the username specified above, or the password to the private key file
-
engine.postproc.sftp.privkey –– Absolute path to the private key file (optional, for certificate authentication)
-
engine.postproc.sftp.pubkey –– Absolute path to the public key file (optional, for certificate authentication)
-
- SugarSync
-
-
engine.postproc.sugarsync.email
-
engine.postproc.sugarsync.password
-
- WebDAV
-
-
engine.postproc.webdav.username
(Video) Installation and first backup -
engine.postproc.webdav.password
-
For your information, the configuration keys for cloud storage services can be found in the .ini files under administrator/components/com_akeeba/BackupEngine/Postproc.
Applying them on the command line is easy. Take this command line as an example:
usr/local/bin/php /home/johndoe/httpdocs/cli/akeeba-backup.php--profile=2 --description="My automated backup"--override="engine.postproc.s3.accesskey=ABCDEF"--override="engine.postproc.s3.secretkey=1234567890abcdefgh"
In this case, we are telling the backup script to use the backup Profile with ID=2, give the backup description of "My automated backup" and then supply the S3 access and secret keys. The values of the override parameters must be enclosed in double or single quotes (depends on your Operating System), otherwise the operating system will not pass them back to the backup.php script. Do note that your command line MUST NOT include the line breaks in the previous example. The line breaks are there only for typesetting purposes.
Finally, it should be noted that you can use the command-line override feature to do more tricky configuration overrides, for example turning off the archive splitting or using a different backup output directory to enhance your security. If it's something you can do in the Configuration page of the component, you can also do it using command line overrides.
| Tip |
|---|---|
| This feature is only available in Akeeba Backup Professional. Requires the Enable Legacy Front-end Backup API (remote CRON jobs) option to be enabled in the component's Options, Frontend tab. |
This script uses the front-end backup feature of Akeeba Backup to run a backup. This may work on some hosts where the regular CRON script doesn't. The alternative CRON script is located in cli/akeeba-altbackup.php, and must be run from the command-line PHP interface (PHP CLI).
As already stated in the Front-End Backup feature, we VERY STRONGLY recommend using the Front-End Backup feature -including the case where it's used by the alternative CRON script- only with sites configured to use HTTPS with a properly signed SSL certificate for security reasons: plain HTTP sites and self-signed HTTPS certificates can, under certain circumstances, lead to your Secret Word leaking even if you are only using it with the alternative CRON script. If a malicious user obtains the Secret Word they can launch a Denial of Service attack on your site and / or abuse Akeeba Backup's feature to obtain a copy of your site, including all privileged information. Getting a properly signed SSL certificate no longer costs any money. The Let's Encrypt certificate authority offers free of charge SSL certificates. Most likely your hosting control panel already supports automatically acquiring and installing SSL certificates from Let's Encrypt. For example two of our favorite hosts, SiteGround and Rochen, have supported this since late 2015. If you are not sure, ask your host. Using HTTPS not only makes your site safer, it will even make it more popular with search engines. It's a win-win proposition!
You will have to a command line similar to this with your host's CRON interface:
/usr/local/bin/php/home/USER/webroot/cli/akeeba-altbackup.php
where /usr/local/bin/php is the path to your PHP CLI executable and /home/USER/webroot is the absolute path to your web site's root. You can get this information from your host.
The backup script accepts the following optional parameters:
-
--profile
profile_idallows you to select which backup profile you would like to use for the scheduled backup. Theprofile_idis the numeric profile ID you can see in your Control Panel page. -
--no-verify Only applies to HTTPS connections. If you have a plain HTTP site you can ignore this setting. Since Akeeba Backup 5.5.2 this script will check that the SSL certificate presented by the server is issued by a known, trusted Certification Authority and that the domain name included in the certificate matches the domain name of your site. If you want to disable this verification, e.g. because you're using a self-signed certificate or a certification authority internal to your organization you need to pass the --no-verify option. This will disable the verification, emulating the way this script worked in Akeeba Backup 5.5.1 and earlier.
In order to give some examples, we will assume that your PHP CLI binary is located in /usr/local/bin/php - a common setting among hosts - and that your web site's root is located at /home/johndoe/httpdocs.
-
Backup with the default profile (ID = 1)
usr/local/bin/php /home/johndoe/httpdocs/cli/akeeba-altbackup.php
-
Backup with profile number 2
usr/local/bin/php /home/johndoe/httpdocs/cli/akeeba-altbackup.php --profile=2
It goes without saying that the line breaks are for readability only. You should not include line breaks in your command line.
Special considerations:
-
Most hosts do not impose a time limit on scripts running from the command-line. If your host does and the limit is less than the required time to backup your site, the backup will fail.
-
This script is not meant to run from a web interface. If your host only provides access to the CGI or FastCGI PHP binaries,
backup.phpwill not work with them. The solution to this issue is tied to the time constraint above. The workaround we're planning will solve both issues. -
You must enable the front-end backup feature of your Akeeba Backup Professional instalaltion and assign a Secret Key for it. This is possible by going to the Akeeba Backup Professional's Control Panel page and clicking on the Options button on the top right corner of the toolbar.
-
Before using the alternative CRON script for the first time, or after moving your site to a new domain name and / or enabling HTTPS, you must visit the Akeeba Backup's Control Panel page at least once. This will cache the URL to your site for use by the alternative CRON script.
-
Your host must support one of the three methods used by the helper script to access your front-end backup URL:
-
The PHP cURL module.
-
The fsockopen() method
-
The fopen() URL wrappers
If none of these methods is available, the backup will fail.
-
-
Taking a backup with the front-end backup feature must be possible on your site. See the Discussion in the chapter about the front-end backup, especially the issues with SEO / SEF URL extensions and host firewalls.
-
Your host may have a firewall setup which doesn't allow the CRON script to access the front-end backup URL if it's launched from the same server. In this case the backup will consistently fail without a new log file being produced and without a backup entry being written to the database. You will have to contact your host so that they can allow the script to access the front-end backup URL. Do note that despite the alternative CRON script and your site running on the same server, the firewall restriction might still be in place. This is counter-intuitive, but we've seen this happening on a few hosts.
If you are seeking assistance regarding a failed CRON job please indicate if and which of these steps you have already tried. We don't want to ask you to do something you've already tried.
Setting up a CRON job on cPanel
| Note |
|---|---|
| This section depends on your host's control panel software. It is included it for informational purposes only and we cannot guarantee its accuracy. If you have questions about this please ask your host. |
Go to your cPanel main page and choose the CRON Jobs icon from the Advanced pane. In the Add New CRON Job box on the page which loads, enter the following information:
- Common Settings
-
Choose the frequency of your backup, for example once per day.
- Command
-
Enter your backup command. Usually, you have to use something like:
/usr/bin/php5-cli /home/
myusername/public_html/cli/akeeba-altbackup.php --profile=YourProfileIDwhere
myusernameis your account's user name (most probably the same you use to login to cPanel) andYourProfileIDis the numeric profile number you want to use for your backup job. Do note the path for the PHP command line executable:/usr/bin/php5-cli. This is the default location of the correct executable file for cPanel 11 and later. Your host may use a different path to the executable. If the command never runs, ask them. We can't help you with that; only those who have set up the server know the changes they have made to the default setup.
Finally, click the Add New Cron Job button to activate the CRON job.
Special notes for GoDaddy
| Note |
|---|---|
| This section depends on your host's control panel software. It is included it for informational purposes only and we cannot guarantee its accuracy. If you have questions about this please ask your host. |
According to our users who have tried this, this laternative script does work with GoDaddy. The command line you have to use is:
/usr/local/php5/bin/php "$HOME/html/cli/akeeba-altbackup.php" --profile=YourProfileID where YourProfileID is the numeric profile number you want to use for your backup job.
The PHP executable we are using is the CLI rather than the default CGI. This is important; if you use the CGI executable then the script will not run. Don't forget to enable frontend backup and insert your secret word. To enable frontend backup go to Akeeba Backup under components, select configuration, select options from the navigation, then select the front-end backup tab to enable the settings.
If the backup completes successfully but the backup appears as "Failed" in the Manage Backups (formerly "Administer Backup Files") page, you'll have to apply a workaround. Go to Akeeba Backup and select your backup profile from the drop-down list. Then click on the Configuration button. In the configuration page check the Use database storage for temporary data option.
FAQs
How to backup Joomla website with Akeeba? ›
Go to downloads and select Akeeba Backup for Joomla If you have subscribed for the pro version make sure that you are logged in first to enable the download. Once the download is completed go to your Joomla web site and log in to the adminsitrator. Akeeba Backup installs like any Joomla extension.
Does Akeeba backup the database? ›By default, Akeeba Backup automatically includes the whole database of your Joomla! ™ installation as well as all the files under your site's root in the backup set.
How does Akeeba backup work? ›installations. An Akeeba Backup archive contains your entire site, files and database contents. Restoring a backup will overwrite the files and database tables that have the same name as those included in the backup.
How do I restore the Akeeba backup? ›If you want to restore your site to a previous version go to the manage backups and then select the backup you wish to restore and click on restore. Select the Files extraction method this is usually the default “write directly to file” Click to start the restoration.
Where are Akeeba backups stored? ›The backup files are where you told Akeeba Backup to put them, i.e. in the Output directory you specified in the Configuration page. If you haven't touched the Configuration yet, the default backup output directory is under your web site's root: Akeeba Backup for Joomla!: administrator/components/com_akeeba/backup.
How do I create a backup in Joomla? ›- Now, add a name for your archive and press Confirm. ...
- Once you have created the archive of your files you can download it either through an FTP client or navigate to the file using a regular browser to download it on your hard drive. ...
- Backup your Joomla!
- MySQL Scheduled Backup: AutoMySQLBackup.
- Step 1: Choose Your Backup Option.
- Step 2: Obtain the Required Information to Add Your Website.
- Step 3: Select Your Root Directory.
- Step 4: Select the Contents to Backup.
- Step 5: Add a Database from the Completion Window.
Right-click the database that you wish to backup, point to Tasks, and then select Back Up.... In the Back Up Database dialog box, the database that you selected appears in the drop-down list (which you can change to any other database on the server).
What is the backup extension for Joomla? ›DataSafe Pro is professional database backup. It generates a snapshot of your full Joomla database, which allows you to quickly revert your content, whenever you want. It's ideal for creating a quick backup before you start any changes to your website. And to restore your Joomla database from a backup it's easy.
What is the default output directory for Akeeba backup? ›The default location of the folder where Akeeba Backup outputs your backups is always administrator/components/com_akeeba/backup.
How does MySQL backup work? ›
MySQL supports incremental backups using the binary log. The binary log files provide you with the information you need to replicate changes to the database that are made subsequent to the point at which you performed a backup.
How do I restore a Joomla backup? ›- Go to Components > Akeeba Backup.
- Click on Manage Backups Finding backups in Akeeba Backup.
- Select the backup you wish to restore and click Restore Restoring the latest backup.
- Click Start Restoration.
- Wait for the archive to be extracted Extraction of the archive.
- Connect the external storage device that contains your backup files.
- In the search box on the taskbar, type Control Panel, then select it from the list of results.
- In the search box in Control Panel, type File History. ...
- Follow the instructions to restore your files.
- On your Android phone or tablet, open the Google Photos app .
- At the bottom, tap Library Trash .
- Touch and hold the photo or video you want to restore.
- At the bottom, tap Restore. The photo or video will be back: In your phone's gallery app. In your Google Photos library. In any albums it was in.
- In the Search box type Akeeba Backup package. ...
- Select the item's checkbox and click on the Uninstall button in the toolbar. ...
- All of our software, as well as some third party software, installs our FOF framework version 3 or 4.
- Go to drive.google.com.
- On the bottom left under "Storage," click the number.
- On the top right, click Backups.
- Choose an option: View details about a backup: Right-click the backup. Preview. . Delete a backup: Right-click the backup. Delete Backup.
- Open the Google Drive app.
- Tap Menu. Backups.
- Tap on the backup you want to manage.
- Login to the new database using phpMyAdmin.
- Click the database name on the left side of the page.
- Select the Import tab.
- Click the Browse button under File to import, then select the database file from your computer.
- Click Go to import the database.
Accessing the Admin Login Page via URL
Access Joomla admin login page by typing in your website address followed by “/administrator.” Input your username and password. Once you entered your credentials, click the “Log in” button to continue.
- Open Windows Explorer.
- Locate the file to be edited or deleted.
- Click on the file to select it. ...
- Select Edit, Copy from the menu bar.
- Browse to the location to place the backup copy of the file. ...
- Select Edit, Paste from the menu bar.
How to restore database without backup? ›
- DBCC CHECKDB (DATABASE_NAME): Check the entire database for repair in command line or query.
- REPAIR_ALLOW_DATA_LOSS: Repair data by allocating and deallocating rows. ...
- REPAIR_FAST: Repair the data in a fast process, but it makes only minor changes.
What is automated backup? Automatic backup is primarily enabled through backup software that automates the entire backup process. It means organizations can back up files, folders and systems without any human intervention. Essentially, automated backups simplify backup procedures to drive speedy recoveries.
How do I automatically backup files to my drive? ›Schedule automated backups
Select Backups from the SQL navigation menu. Click Edit, next to Settings. Choose a window of time for your data to be automatically backed up. Click Save.
The backup files are located in /var/lib/automysqlbackup by default.
Which command is used to backup MySQL data? ›To back up a MySQL database, you can use either third-party tools or execute the mysqldump command from the command line. mysqldump is a command-line utility used to generate a MySQL logical database backup. It creates a single . sql file that contains a set of SQL statements.
How do I manually backup MySQL database? ›- Go to the Administration tab, on the Navigation panel (on the left by default)
- Select Data Export.
- From the Data Export tab in the Tables To Export section, select the databases and tables that will be added to the backup file.
A whole database backup includes all data files and at least one control file. (Remember that all control files within a database are identical.). Full backups make a copy of each data block that contains data and which is within the files being backed up.
What are full backup methods? ›Full backups
As the name implies, this type of backup makes a copy of all data to a storage device, such as a disk or tape. The primary advantage to performing a full backup during every operation is that a complete copy of all data is available with a single set of media.
Example of a full backup
On Tuesday, the entire directory of folders and files on that drive will be copied. On Friday, any new files added to that drive will be copied and all the existing directory from before will be copied again.
In this post, we will explain where is the Joomla database, and what are the two main Joomla files used to connect and interact with the database. Where is the Joomla database? The Joomla database exists on usually a MySQL server, the name of the database is declared in your configuration. php file.
Where are Joomla files stored? ›
By default this is the /images folder in the webspace root. If you mean with user a developer of the website with file access to the webspace via FTP, SSH or else, then there are multiple locations.
What is the default directory that receives backup from serviced backup? ›Specify the disk backup file path
If you specify only the file name or a relative path when you are backing up to a file, the backup file is put in the default backup directory. The default backup directory is C:\Program Files\Microsoft SQL Server\MSSQL.
By default, all backup data is stored in the directory /var/lib/psa/dumps .
How to install Akeeba WordPress? ›Using WordPress' plugin installer
Go to your site's wp-admin section and click on Plugins, Add New. Select Upload from the top of the page. Click on the file selection area and select the ZIP file you downloaded from us. Then click on the Install Now button.
By default, mysqldump locks all the tables it's about to dump. This ensure the data is in a consistent state during the dump.
How do I view MySQL backup? ›- Step 1: Create New Database. On the system that hosts the database, use MySQL to create a new database. Make sure you've named it the same as the database you lost. ...
- Step 2: Restore MySQL Dump. To restore a MySQL backup, enter: mysql -u [user] -p [database_name] < [filename].sql.
- Log into the Backup Server as a root user.
- Create the pre-db-backup-mode.sh script using to the following code: #!/bin/bash# dbuser=root. dbpwd=rootpwd. lock_mysqldb(){ ( echo "flush tables with read lock;" sleep 5. ) | mysql -u$dbuser -p$dbpwd ${ARGUMENTS} } } lock_mysqldb &
- Connect to your account using FTP (see tutorials).
- Upload your file(s).
- (Optional) If you uploaded a zip archive, unzip it using Archive Gateway (see how).
In Database Explorer, right-click the server connection on which you want to restore the database and select Backup and Restore > Restore Database. In the Database Restore Wizard, select the backup file and click Restore.
Can you retrieve deleted text messages? ›Tap the three-dot menu in the upper-right corner and open the Recycle bin. Check your deleted text messages. Long tap the message you want to retrieve. Select Restore at the bottom and check the same in your primary inbox.
Is file history the same as backup? ›
While File History allows you to restore individual files, Backup and Restore does not. Consequently, if you want to recover files from a backup file set, you must restore them all or none at all.
Does file history backup everything? ›After setting up File History, the next big question is, 'does Windows File History backup everything?' Unfortunately, the answer is NO. Windows File History can back up certain files, including Documents, Pictures, Videos, Music, or offline OneDrive files.
Can I recover photos from 2 years ago? ›Primarily, recovering old deleted photos may seem impossible. However, should you have an image recovery software program such as Photos Recovery, you could recover many years old photos, videos, and audio information. You can also try out the Recycle Bin to find deleted files.
Can you recover photos from years ago? ›The answer is ? Yes?. Fortunately, there are recovery software whose search engines can retrieve photos deleted long time ago from PC, Mac, and removable storage drives. Further, various backup solutions also keep you safe from losing old deleted photos.
Can old deleted photos be recovered? ›If the photos were backed up to Google Photos, users can recover them by following the steps in the app. If not, photo recovery apps can scan the device's storage for deleted files and restore them. Alternatively, connecting the device to a computer and using data recovery software can also recover deleted photos.
How do I export a Joomla site? ›- Login to the database that you want to duplicate using phpMyAdmin.
- Click the database name on the left side of the page.
- Select the Export tab.
- Select the Save as file option.
- Click Go.
- Download your Joomla website, preferably through FTP.
- Export your database, preferably through phpMyAdmin.
- Upload your downloaded Joomla website to the new location.
- Import the exported database into a new database.
- Change the configuration.
Access Joomla admin login page by typing in your website address followed by “/administrator.” Input your username and password. Once you entered your credentials, click the “Log in” button to continue.
How do I backup my Joomla 4 website? ›- Go to the root folder of your Joomla website and select all files and folders.
- Click the “Compress” tool in the top admin bar of File Manager.
- Choose “Zip Archive” in as the Compression Type.
- Scroll down in the Compression window and put in a name for the file.
- Login to hosting control panel, open File Manager, go to the root of your Joomla installation.
- Press Upload button and upload zip archive that you have backed up before. ...
- On this step, you should open configuration. ...
- Next, you should restore the backed up database.
Can I transfer from Joomla to WordPress? ›
Go to Tools, click on Import, and then select Joomla (FG) from the left navigation menu in the WordPress Dashboard, go to Tools, click on Import, then choose Joomla (FG). This page is where the Joomla database settings ⤵ need to be added to begin the import.
Can a website be duplicated? ›That “one place” is defined as a location with a unique website address (URL) - so, if the same content appears at more than one web address, you've got duplicate content.
What is website duplication called? ›External duplicate content, also known as cross-domain duplicates, occurs when two or more different domains have the same page copy indexed by the search engines.
What is the admin URL for Joomla? ›To login to Joomla! 3 and access your administrative panel, you need to open your browser and navigate to http://mydomain.com/administrator. On this page, you will find a login screen, where you need to enter the username and password you've chosen during the Joomla!
What is the default username and password for Joomla admin? ›If this is your first time logging in as the root administrator, the default username is admin. Enter the password you created during installation. Click Login. You are now logged in to Joomla as admin, on the admin panel.
What is the default password for Joomla admin? ›Default username is "admin", there is no default password, you have to set it in the last step of the installation.