![]() ![]() Using the option “ Include in the backup the following objects” you can select the database objects you want to include in the backup (by default Iperius includes the table structures and data, but you can also include users, stored procedures, triggers, etc.). You can also use some special variables to customize the folder name with the computer name, the week day name, etc. The next option is the destination folder, so the folder where to save the database backup files. As shown in the picture below, you can automatically back up all the databases on the server, select a single database (you can create in the same backup job an individual item for every database or server, each one with its specific options), or type several database names separating them with commas. Once you’ve specified these data, you can immediately test the connection using the specific button.Īfter the account has been created, you can select it in the item configuration window, and move on to configure the next options. ![]() You need the server IP address or name, the username and assword. The first step consists in creating and selecting an account to connect to the database server. With a single license you can run the automatic backup of unlimited servers and unlimited databases (even website databases if your ISP allows external access to them).įrom the main window of Iperius, first create a backup job using the appropriate button:Ĭlick on the button that allows to add a MySQL/MariaDB database backup: Backup files can be automatically transferred by FTP, FTPS and SFTP or to Cloud services such as Google Drive, Dropbox or Amazon S3. It can back up local or remote databases without any service interruption ( hot backup). Iperius is a complete database backup software. For more information on installation as a service, see this tutorial.With Iperius you can backup MySQL and MariaDB databases easily and efficiently. With these configurations, even scheduled backups can run without errors, just like those run manually, as the user they run under will be the same (or will have the same privileges) as the user under which the backups are run manually. This account can be specified globally here in the service panel (it will be valid for all network paths), or else as a single destination, as shown in the figure below: installing the service with the local system account and selection of an account that will be impersonated by the backup processes:įinally, one may need to set up an additional account in order to access network paths, as, for example, in the case of a folder shared on a NAS drive and protected by a password. In this second image, we can see the other mode, i.e. Of course one can change the logon account of the service directly from among the Windows services (the Iperius Backup service is called “Iperius Backup Service”). In the image below, we can see the choice of a specific account (we always recommend using an administrator account) for installing the service: If one installs the service with a specific account, the AutoRun backup window will not be visible as it is running in a session other than the primary one. The difference between the two solutions is minimal (and the choice between the two is usually to be determined only in more specific situations), except for the fact that impersonating allows you to continue to see the AutoRun window of the backups in the primary session. The authentication issue has an easy solution since Iperius allows one to install the service using a specific account and to impersonate a certain user account for backup operations. In this case, let’s make sure we have entered the complete network path (example: Īs\backup) and not a mapped network drive. In fact, a Windows service cannot access mapped network drives, simply because they do not exist in the service session (but are automatically reconnected, and therefore created, only at user logon). In this case, scheduled backups, since they are run by the service, will also run using this user account, which generally does not have access to network paths, nor may it have the necessary privileges to access certain folders.Īnother possible cause is the use of mapped network drives instead of the full network path. ![]() When Iperius is installed as a Windows service and the default settings are left as they are, the service will be started using the local system account, or SYSTEM. The cause of this problem is very simple. These errors generally occur only when the backup is run in the automatic mode according to a schedule, while backups run manually complete successfully. A common problem that one can encounter when installing Iperius Backup as a service and setting up a schedule for it is to encounter errors accessing network paths. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |