For all accounts shown in the list, restore them. On the new server, for each Admin/Reseller, login and go to Reseller Panel -> Manage User backups. ( Admin Backups/Transfers also creates Resellers as Resellers, not users, so there is no need to create an empty template account first, since the restore does it all for you). It's essentially the same thing, except the file naming is slightly different and it can all be done from one screen (no extra logins required), and you can skip step 6 as Reseller Level settings are included in this system. The newer alternative for the Reseller Level Backups is Admin Level -> Admin Backups/Transfers. Make sure that the user_backups directory is owned by that Admin/Reseller and that the backup files in that directory are chmod to 755 (needs to be readable by the User that is being restored). ![]() When uploading the backup files to the new server, place them in /home/ reseller/user_backups, where reseller is the name of the admin/reseller who owns those accounts (including his own personal files). You can try to use the FTP feature to upload to the same Admin Reseller on the new server, but you'll have to make sure the firewalls are set up correctly first (try it and make sure the files extract properly before doing all accounts). We recommend doing a local backup and then transferring the files over to the new server manually. ![]() Select all accounts, and make a local backup of those accounts. On the old server, for each Admin/Reseller, log in as them, and go to their Reseller Panel -> Manage User Backups. Once each Reseller/Admin are created, go to Admin Panel -> IP Manager and assign each one whichever IPs they'll need to be using. This is why their account needs to be first created. If the User backup files of the Reseller/Admin (their personal user files) were just restored, their account would be created as a user. Similarly, you can add users to owned IPs if they were shared on the old server.įor each Admin/Reseller account on the old system, they will have to be created through DA the usual way on the new system ( does not apply if you're using Admin Backup/Transfer). For example, If they are currently on an owned IP address, it's quite easy to transfer everyone to a shared IP address, so if you don't have as many IPs, that's not a problem. You can change the IP assignment of the user when doing the transfer. Go to Admin Panel -> IP Manager on the new server, and add all of the IPs. Once the migration is complete, request removal of the new license and then put the new server IP address into your original license, which can be done in your Client Account Area open in new window.įor each IP that you are using on the old server, you'll need to add a new corresponding IP to the new server. legacy lifetime) please purchase a license at your own expense, and cancel it when the migration is finished. For licenses with support, open a ticket open in new window to request a free temporary migration license. To transfer all of your accounts to a new server, you'll need to follow a few steps.įirst, DirectAdmin needs to be installed on the new server. # Migrating accounts # Server to server transfer of all accounts. Dealing with large users and backup timings.To redirect incoming requests for to server1 (192.168.1. Specify appropriate values for the other fields and click Add. In the IP Address field, enter the destination IP address where matching requests should be redirected.Click the Server option next to the rule you just created.In the URL Match field, enter the URL of the requests you want to redirect to a different back-end server.Click the Rule option next to the service.From the WEBSITES > Traffic Management page in the Services section, identify the desired service. ![]() ![]() From the BASIC > Services page in the Services section, identify the desired service.The Barracuda Web Application Firewall compares URLs and header fields of requests to the rules you define and applies the content rule policies to matching requests. The WEBSITES > Traffic Management page allows you to define content rules that specify a pattern in the URL or header fields of the request. This feature is available on all units, however, access to this feature varies depending on your firmware version.
0 Comments
Leave a Reply. |