SolarWinds MSP Integration: Difference between revisions
Jump to navigation
Jump to search
Line 79: | Line 79: | ||
== Running the Backup == | == Running the Backup == | ||
[[File:sw_backup_recovery2.png]] | [[File:sw_backup_recovery2.png|800px]] |
Revision as of 03:18, 11 November 2017
Installing SolarWinds MSP Linux Backup Agent
After setting up your SolarWinds backup server download and install the MSP Linux amd64/x64 backup agent. In this example we've downloaded it and placed the agent installer 'mxb-linux-x86_64.run' into the /swinds directory and made it executable using chmod.
root@smu-devtest44-136:/swinds# chmod 755 ./mxb-linux-x86_64.run root@smu-devtest44-136:/swinds# ./mxb-linux-x86_64.run Verifying archive integrity... All good. Uncompressing Backup Manager............................................ -- Stopping and removing old ProcessController service Removing any system startup links for /etc/init.d/ProcessController ... /etc/rc0.d/K20ProcessController /etc/rc1.d/K20ProcessController /etc/rc2.d/S20ProcessController /etc/rc3.d/S20ProcessController /etc/rc4.d/S20ProcessController /etc/rc5.d/S20ProcessController /etc/rc6.d/K20ProcessController -- Creating directories Verifying archive integrity... All good. Uncompressing ...... './var/log/BRMigrationTool/BRMigrationTool_2017_11_10.log' -> '/tmp/BRMigrationTool_2017_11_10.log' -- Copying files -- Installing new ProcessController service Adding system startup for /etc/init.d/ProcessController ... /etc/rc0.d/K20ProcessController -> ../init.d/ProcessController /etc/rc1.d/K20ProcessController -> ../init.d/ProcessController /etc/rc6.d/K20ProcessController -> ../init.d/ProcessController /etc/rc2.d/S20ProcessController -> ../init.d/ProcessController /etc/rc3.d/S20ProcessController -> ../init.d/ProcessController /etc/rc4.d/S20ProcessController -> ../init.d/ProcessController /etc/rc5.d/S20ProcessController -> ../init.d/ProcessController -- Running configuration script Device name []: smu-devtest44-136 Password []: d9fa18648857 Your files are sent and stored encrypted, so they are unreadable and useless to anybody, except to you. You can even think up your own security code. Please note that you should use a key that you will be able to recall later on. NO ONE has access to your data without this security code. Security code []: d9fa18648857 Checking connection to cloud... Use proxy server: true or false [false]: Initializing Validating security code Security code successfully set. -- Finalizing installation -- Starting new ProcessController service * Zapping ProcessController * * Starting ProcessController * Initialization in progress. It can take a while... ... ... ... ... ... ... ... ... ... ... ... ... Functional process initialized successfully. -- Done root@smu-devtest44-136:/swinds#