Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
en:services:storage_services:backup:tsm:anleitungen:installation-windows [2024/06/04 16:27] – removed jbruene | en:services:storage_services:backup:tsm:anleitungen:installation-windows [2024/06/21 12:33] (current) – created jbruene | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== ISP Client Installation Windows ====== | ||
+ | |||
+ | This is an illustrated quick guide leading through all steps of the installation and configuration of the ISP client software on //Windows 10 Enterprise 64Bit Edition//. Virtually all steps are the same for the “pro” or “home” version and for older Windows versions. Perhaps some dialogs (e.g. pop-up windows) may differ. For this guide the ISP Client software in version 8.1.2.0 was used, other versions may differ in detail, but the process should be similar in general. | ||
+ | |||
+ | <WRAP center round tip 60%> | ||
+ | ISP 8.1 only supports windows in 64bit flavor, | ||
+ | |||
+ | for 32bit windows use ISP 7.1.7! | ||
+ | </ | ||
+ | |||
+ | |||
+ | The following chapters guide through the steps of the installation, | ||
+ | |||
+ | ===== Summary on set up ===== | ||
+ | This guide was created with a fresh Windows 10 Enterprise x86-64, fully patched and without any additional software. | ||
+ | |||
+ | At the time of creation of this guide the ISP client is version 8.1.2.0. The server runs TSM 7.1.3-100. TSM / ISP supports a difference of " | ||
+ | |||
+ | Parameters for the ISP configuration (notation according to the original IBM notation with mixed low- and upcase letters): | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | |||
+ | ===== Obtaining the ISP Client software ===== | ||
+ | The ISP Client software is available at the IBM download servers. IBM maintains two branches, one of which is the // | ||
+ | |||
+ | * https:// | ||
+ | * https:// | ||
+ | |||
+ | ===== Installation of the TSM client software ===== | ||
+ | |||
+ | * Start the installation by executing the downloaded file “$VERSION-TIV-TSMBAC-WindowsX64.exe”, | ||
+ | {{ : | ||
+ | * **Remember to delete these files after setup!** | ||
+ | |||
+ | * With the //File Explorer// (right click onto the windows icon) navigate to the " | ||
+ | {{ : | ||
+ | |||
+ | * Double click on the // | ||
+ | {{ : | ||
+ | |||
+ | * Ordinarily the UAC asks for confirmation, | ||
+ | {{ : | ||
+ | |||
+ | * Please always prefer “English” as installation language because it’s the common ISP language and the often the translations of the ISP error messages lack quality and clarity. | ||
+ | {{ : | ||
+ | |||
+ | * Install the required runtime libraries. | ||
+ | {{ : | ||
+ | |||
+ | * After installing the runtime packages the TSM installation starts. | ||
+ | {{ : | ||
+ | |||
+ | * You can accept the configuration defaults, for instance the installation target directory. | ||
+ | {{ : | ||
+ | |||
+ | * In most cases, the setup type //Typical// will be the sane choice. | ||
+ | {{ : | ||
+ | |||
+ | * Alternatively, | ||
+ | {{ : | ||
+ | |||
+ | * Start the installation | ||
+ | {{ : | ||
+ | |||
+ | * and wait for the success message. | ||
+ | {{ : | ||
+ | |||
+ | ===== excurse: where to find ISP in the Windows menue ===== | ||
+ | * right after installation, | ||
+ | {{ : | ||
+ | |||
+ | * It's also located at //I// => //IBM Spectrum Protect// | ||
+ | {{ : | ||
+ | |||
+ | ===== excurse: on language settings ===== | ||
+ | As already mentioned, the localization of TSM / ISP causes more confusion than it helps. Therefore we **strongly suggest** to set the language of TSM/ISP to //American English//. Up to TSM 6.2 this was simple to achieve, by just do not installing a language pack. With TSM/ISP 7 the language packs became part of the client, but using the // | ||
+ | |||
+ | the following commands entered in the windows // | ||
+ | < | ||
+ | # navigate to the installation directory | ||
+ | cd " | ||
+ | # remove old localisation files | ||
+ | rmdir de_DE /S /Q | ||
+ | del dscdeu.txt | ||
+ | del dsc30deu.dll | ||
+ | del dsmc_deu.hlp | ||
+ | del fcmdeu.txt | ||
+ | # create new de_DE folder | ||
+ | mkdir de_DE | ||
+ | # copy en_US files to de_DE | ||
+ | copy en_US\* de_DE\ | ||
+ | copy dscenu.txt dscdeu.txt | ||
+ | copy dsc30enu.txt dsc30deu.txt | ||
+ | copy dsmc_enu.hlp dsmc_deu.hlp | ||
+ | copy fcmenu.txt fcmdeu.txt | ||
+ | </ | ||
+ | |||
+ | <WRAP center round tip 90%> | ||
+ | if your computer runs a different //localized windows//, just replace'' | ||
+ | </ | ||
+ | |||
+ | unfortunately this steps will be necessary every time you update the client | ||
+ | ===== initial basic configuration ===== | ||
+ | There' | ||
+ | {{ : | ||
+ | |||
+ | Because the ISP client starts with the systems language we strongly suggest to do the basic configuration in the text file before you start the GUI, otherwise it maybe in german: | ||
+ | {{ : | ||
+ | {{ : | ||
+ | |||
+ | ===== basic configuration (directly within the configuration file) ===== | ||
+ | * Open a texteditor, e.g. // | ||
+ | {{ : | ||
+ | |||
+ | * UAC asks another time for confirmation .. | ||
+ | {{ : | ||
+ | |||
+ | * then you can enter the basic settings (see introduction above) as | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | {{ : | ||
+ | |||
+ | * save the file as '' | ||
+ | {{ : | ||
+ | |||
+ | * ... at '' | ||
+ | {{ : | ||
+ | |||
+ | * make sure, it is an '' | ||
+ | {{ : | ||
+ | |||
+ | ===== basic configurations in the graphical user interface (GUI) ===== | ||
+ | * As mentioned before, you'll find ISP under //Recently added// in the Windows menu right after installation | ||
+ | {{ : | ||
+ | |||
+ | * It's also located at //I// => //IBM Spectrum Protect// | ||
+ | {{ : | ||
+ | |||
+ | * Every time you start the TSM client software you have to confirm access rights: | ||
+ | {{ : | ||
+ | FIXME | ||
+ | * At the first start of TSM, it will look for the configuration file // | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== first backup (CLI) ===== | ||
+ | using the CLI the initial backup can be initiated easily, just type: | ||
+ | |||
+ | < | ||
+ | tsm> i | ||
+ | </ | ||
+ | < | ||
+ | |||
+ | </ | ||
+ | the ISP client starts to backup all configured //DOMAINS// using the // | ||
+ | |||
+ | You can speed up the backup bypassing the all file tests using the '' | ||
+ | |||
+ | < | ||
+ | tsm> i -absolute | ||
+ | </ | ||
+ | < | ||
+ | |||
+ | </ | ||
+ | <WRAP center round important 90%> | ||
+ | using the '' | ||
+ | </ | ||
+ | |||
+ | ===== Automation ===== | ||
+ | ==== " | ||
+ | |||
+ | First, you have do make a descision: //Should the backup service run continuously or only if triggered intentionally?// | ||
+ | |||
+ | Because the TSM Schedule service (// | ||
+ | |||
+ | Therefore the question has to be asked differently: | ||
+ | |||
+ | //Should only backups be done or is there a need to run a web based client on your PC / server?// | ||
+ | |||
+ | Obviously running a webserver for the web based client might be a critical security issue, so we strongly suggest not to configure the webclient. If you do not, there' | ||
+ | |||
+ | <WRAP center round tip 90%> | ||
+ | using linux it's completely different: the most common approach for linux is to use the //DSMCAD//, therefore IBM provides a start / init script for the //DSMCAD// but just a few informations for starting the // | ||
+ | </ | ||
+ | |||
+ | Detailed information you can find [[https:// | ||
+ | ==== Configuring the DSMSCHED ==== | ||
+ | Best configure the // | ||
+ | |||
+ | ==== Testing the scheduler configuration ==== | ||
+ | A soon as the scheduler is started, it //should// ask the server for it's schedule to run the backup. Unfortunately the scheduler isn't reliable. Therefore run the request manually: | ||
+ | |||
+ | </ | ||
+ | or in the Windows cmd line | ||
+ | < | ||
+ | dsmc.exe q sched | ||
+ | </ | ||
+ | < | ||
+ | |||
+ | </ | ||
+ | This command should return all schedules associated with the node. //Usually// the scheduler daemon logs this request in it's log file. So please check the scheduler log for new entries referring to the associated schedules. | ||