For example, suppose that a backup-archive client backs up an 80 GB, file-system image. This object can have a high number of duplicate extents if, for example, the files included in the file system image were backed up incrementally. For example, assume that a file system image has 1. The 1. The total space in the active log that is required for this single object is 1.
For example, suppose that a storage pool is enabled for deduplication. The storage pool has a mixture of data, including many relatively small files that range from 10 KB to several hundred KB. The storage pool also has few large objects that have a high percentage of duplicate extents. To take into account not only space requirements but also the timing and duration of concurrent transactions, increase the estimated size of the active log by a factor of two.
For example, suppose that your calculations for space requirements are 25 GB If deduplication processes are running concurrently, the suggested size of the active log is 50 GB. The suggested size of the archive log is GB. The examples in the following tables show calculations for active and archive logs. The example in the first table uses an average size of KB for extents.
The example in the second table uses an average size of KB. As the examples show, the average deduplicate-extent size of KB indicates a larger estimated size for the active log.
To minimize or prevent operational problems for the server, use KB to estimate the size of the active log in your production environment. Table 9. Therefore, the largest single file to deduplicate represents the largest transaction and a correspondingly large load on the active and archive logs. Not all deduplicated extents for a given file are the same size, so this calculation assumes an average size for extents. Average duplicate-extent size of KB continued Item Extents for a given file Example values 1,, bits Description 6,, bits Using the average extent size KB , these calculations represent the total number of extents for a given object.
In these examples, the active log space required to deduplicate a single large object is considered along with previous estimates for the required active log size. The following calculation was used for multiple transactions and an GB object: Average duplicate-extent size of KB continued Item Example values Description 1 The example values in this table are used only to illustrate how the sizes for active logs and archive logs are calculated.
In a production environment that uses deduplication, 32 GB is the suggested minimum size for an active log. The suggested minimum size for an archive log in a production environment that uses deduplication is 96 GB. If you substitute values from your environment and the results are larger than 32 GB and 96 GB, use your results to size the active log and archive log.
Table Not all deduplicated extents for a given file are the same size, so this calculation assumes an average extent size. Extents for a given file 3,, bits 16,, bits Using the average extent size, these calculations represent the total number of extents for a given object. The following calculation was used for an GB object: Planning to install the IBM Tivoli Storage Manager server 23 Installing the Tivoli Storage Manager server Active-log mirror space The active log can be mirrored so that the mirrored copy can be used if the active log files cannot be read.
There can be only one active log mirror. Creating a log mirror is a suggested option. If you increase the size of the active log, the log mirror size is increased automatically. The additional space that the log mirror requires is another factor to consider when deciding whether to create a log mirror. If the mirror log directory becomes full, the server issues error messages to the activity log and to the db2diag. Server activity continues.
Archive-failover log space The archive failover log is used by the server if the archive log directory runs out of space. Specifying an archive failover log directory can prevent problems that occur if the archive log runs out of space. If both the archive log directory and the drive or file system where the archive failover log directory is located become full, the data remains in the active log directory.
This condition can cause the active log to fill up, which causes the server to halt. To monitor space utilization in the database and recovery logs, you can also check the activity log for messages. The Tivoli Storage Manager server starts a full database backup. To change the maximum log size, halt the server. Open the dsmserv. When you are finished, restart the server. You must back up the database manually. If at least one full database backup has occurred, the Tivoli Storage Manager server starts an incremental database backup.
Otherwise, the server starts a full database backup. The Tivoli Storage Manager server starts a full automatic database backup. In addition, files are created to hold database information used by the database manager. The path specified in this message indicates the location of the database information used by the database manager. If space is unavailable in the path, the server can no longer function.
You must add space to the file system or make space available on the file system or disk. Server naming best practices Use these descriptions as a reference when you install or upgrade a Tivoli Storage Manager server. Instance user ID The instance user ID is used as the basis for other names related to the server instance. The instance user ID is also called the instance owner. The standard way to run the server is under the instance user ID.
Planning to install the IBM Tivoli Storage Manager server 25 Installing the Tivoli Storage Manager server Database instance name The database instance name is the name of the server instance as it appears in the registry.
For example: Server1 Instance directory The instance directory is a directory that contains files specifically for a server instance the server options file and other server-specific files. It can have any name that you want. For easier identification, use a name that ties the directory to the instance name. You can use a name that includes the name of the server instance as it appears or will appear in the registry. Default server instance names have the form Serverx. This name cannot be changed.
Server name The server name is an internal name for Tivoli Storage Manager, and is used for operations that involve communication among multiple Tivoli Storage Manager servers. Examples include server-to-server communication and library sharing. The server name is also used when you add the server to the Operations Center so that it can be managed using that interface.
Use a unique name for each server. Do not change the name of a Tivoli Storage Manager server after it is configured as a hub or spoke server. If you use the wizard, the default name that is suggested is the host name of the system that you are using. You can use a different name that is meaningful in your environment.
If you have more than one server on the system and you use the wizard, you can use the default name for only one of the servers. You must enter a unique name for each server. For easier identification, consider using names that tie the directories to the server instance.
Passport Advantage is the only site that you can download a licensed package file from. If you downloaded the package from an IBM download site, complete the following steps: a. Verify that you have enough space to store the installation files when they are extracted from the product package.
Change to the directory where you placed the executable file. Important: In the next step, the files are extracted to the current directory.
The path must contain no more than characters. Be sure to extract the installation files to an empty directory. Do not extract to a directory that contains previously extracted files, or any other files.
Either double-click the executable file, or enter the following command on the command line to extract the installation files. The files are extracted to the current directory. Click Support and downloads and apply any applicable fixes. Before you begin Take the following actions before you start the installation: v Verify that the operating system is set to the language that you require.
By default, the language of the operating system is the language of the installation wizard. On test servers only: Use the following command to bypass prerequisite checks such as the operating system and the required memory.
Do not issue this command on a production server. Change to the directory where you downloaded the package. Start the installation wizard by issuing the following command: install.
Installing the software from a DVD: 1. Tip: Ensure that the installation files are visible on the DVD drive. Start the installation wizard by issuing the following command from a command line: install. What to do next v If errors occur during the installation process, the errors are recorded in log files that are stored in the IBM Installation Manager logs directory.
If a native device driver is not available on Windows for the tape drives or medium changers that you plan to use, install the Tivoli Storage Manager device driver by issuing the dpinst.
The dpinst. Procedure install. Start the installation wizard in console mode by issuing the following command: install.
Optional: Generate a response file as part of a console mode installation. Complete the console mode installation options, and in the Summary panel, specify G to generate the responses. Before you begin A silent installation can use response files for data input. Installing the Tivoli Storage Manager server components 33 Installing the Tivoli Storage Manager server You can use these sample files as they are or you can customize them to suit your needs.
It is optimal to use the sample response files. These sample files contain instructions and default values to help you avoid any unnecessary warnings. The translations also allow for the use of locale conventions for date, time, and number formatting. Server language locales Use either the default language package option or select another language package to display server messages and help. For languages or locales other than the default, install the language package that your installation requires.
You can use the languages that are shown: Table Restriction: For Operations Center users, some characters might not be displayed properly if the web browser does not use the same language as the server. If this problem occurs, set the browser to use the same language as the server. Configuring a language package After you configure a language package, messages and help are shown on the Tivoli Storage Manager in languages other than US English. Installation packages are provided with Tivoli Storage Manager.
Installing the Tivoli Storage Manager server components 35 Installing the Tivoli Storage Manager server If the locale is successfully initialized, it formats the date, time, and number for the server. If the locale is not successfully initialized, the server uses the US English message files and the date, time, and number format. About this task You can install another language package within the same Tivoli Storage Manager instance.
Tip: In IBM Installation Manager, the term update means to discover and install updates and fixes to installed software packages. In this context, update and upgrade are synonymous. Using the configuration wizard is the preferred method of configuring the Tivoli Storage Manager instance. About this task Planning to install Installing components Taking the first steps Figure 2. You are in the configuring the Tivoli Storage Manager server section.
Configure the Tivoli Storage Manager server instance by completing the following steps: 1. Create the directories and user ID for the server instance. Configure a Tivoli Storage Manager instance. Select one of the following options: v Use the Tivoli Storage Manager configuration wizard, the preferred method. Complete the following steps during a manual configuration. Set up your directories and create the Tivoli Storage Manager instance. Create a new server options file by copying the sample file to set up communications between the server and clients.
Configure your system for database backup. Configure options to control when database reorganization runs. Start the Tivoli Storage Manager server instance if it is not already started. Register your license. Prepare your system for database backups. Monitor the server. Before you begin Review the information about planning space for the server before you complete this task.
Create the user ID that will own the server instance. You use this user ID when you create the server instance in a later step. Identify the user account that will own the Tivoli Storage Manager server instance. When the server is started as a Windows service, this account is the one that the service will log on to.
The user account must have administrative authority on the system. One user account can own more than one server instance. If you have multiple servers on one system and want to run each server with a different user account, create a new user account in this step.
Create the user ID. The user ID must be 30 characters or less, and cannot start with ibm, sql, sys, or a numeral. Create directories that the server requires. The database, archive log, and active log must reside on different physical volumes. In addition, files are created to hold database information that is used by the database manager.
Log off the new user ID. The preferred method for configuring the server is to use the configuration wizard. You can use the wizard to complete several server configuration tasks. However, you cannot use the wizard to extend the Active Directory schema so that clients can automatically discover servers. Configure a Tivoli Storage Manager server instance by selecting one of the following options: v Use the Tivoli Storage Manager configuration wizard on your local system.
Chapter 3. Taking the first steps after you install Tivoli Storage Manager Version 7. Set up the directories and create the Tivoli Storage Manager instance. Create a new server options file by copying the sample file in order to set up communications between the Tivoli Storage Manager server and clients. Configuring Tivoli Storage Manager using the configuration wizard The wizard offers a guided approach to configuring a server. By using the graphical user interface GUI , you can avoid some configuration steps that are complex when done manually.
Start the wizard on the system where you installed the Tivoli Storage Manager server program. Before you begin Before you begin to use the configuration wizard, you must complete all preceding steps to prepare for the configuration. These steps include installing Tivoli Storage Manager, creating the database and log directories, and creating the directories and user ID for the server instance. The preferred method for configuring the server instance is to use the configuration wizard.
You can use the wizard to complete several configuration tasks. Ensure that the following requirements are met: v You must disable User Account Control at least while you are running this wizard. Or, double-click the dsmicfgx. Follow the instructions to complete the configuration.
The wizard can be stopped and restarted, but the server is not operational until the entire configuration process is complete. Before you begin You must configure the User Account Control feature before you run the wizard. Tip: Ensure that the Remote Registry in Windows Services is started, and ports , , and are unblocked in the firewall.
Procedure If the system is running on Windows, complete the following steps to disable User Account Control: 1. The built-in Administrator account must be enabled. Then, under Security Settings, double-click Local Policies. Double-click Security Options. Double-click the Accounts: Administrator account status section.
Select Enable and click OK. User Account Control must be disabled for all windows administrators. Select Disable and click OK. User Account Control must be disabled for the built-in Administrator account. Creating the server instance Create a Tivoli Storage Manager instance by issuing the db2icrt command.
About this task You can have one or more server instances on one workstation. Important: Before you run the db2icrt command, ensure that the user and the instance directory of the user exists. If there is no instance directory, you must create it. The instance directory stores the following files for the server instance: v The server options file, dsmserv.
Log in as an administrator and create a Tivoli Storage Manager instance, by using the db2icrt command. Enter the following command on one line. The user account that you specify becomes the user ID that owns the Version 7.
Later, when you create and format the database, you use the instance name that you specified with this command, with the -k option. Change the default path for the database to be the drive where the instance directory for the server is located. Complete the following steps: a.
Enter quit to exit the command line processor. A window with a command prompt should now be open, with the environment properly set up to successfully issue the commands in the next steps.
Enter the command: db2 update dbm cfg using dftdbpath d: 3. Create a new server options file. About this task Set these server options before you start the server. When you start the server, the new options go into effect. If you modify any server options after starting the server, you must stop and restart the server to activate the updated options. Review the server options file dsmserv. Tip: If you start the server console and see warning messages that a protocol could not be used by the server, either the protocol is not installed or the settings do not match the Windows protocol settings.
For a client to use a protocol that is enabled on the server, the client options file must contain corresponding values for communication options. In the server options file, you can view the values for each protocol. For more information about server options, see the Administrator's Reference. Passwords that are authenticated with the LDAP directory server can provide enhanced system security. For details, see the managing passwords and logon procedures section in the Administrator's Guide.
The default value is The window size that is used in a session is the smaller of the server and client window sizes. Larger window sizes use additional memory but can improve performance.
To use the default window size for the operating system, specify 0. Sending small messages can improve throughput but increases the number of packets sent over the network. The default is YES. Setting Named Pipes options: The Named Pipes communication method is ideal when running the server and client on the same Windows machine.
Named Pipes require no special configuration. For example, the following example is possible: commmethod tcpip commmethod namedpipe 44 IBM Tivoli Storage Manager for Windows: Installation Guide Installing the Tivoli Storage Manager server Setting shared memory options: You can use shared memory communications between clients and servers on the same system. The default port address is The subagent communicates with the snmp daemon, which in turn communicates with a management application.
The snmp daemon must support the DPI protocol. The subagent process is separate from the Tivoli Storage Manager server process, but the subagent gets its information from a server options file. When the SNMP management application is enabled, it can get information and messages from servers.
For details about the other options, see the Administrator's Reference. Before you begin SSL is the standard technology for creating encrypted sessions between servers and clients.
SSL provides a secure channel for servers and clients to communicate over open communication paths. With SSL, the identity of the server is verified through the use of digital certificates. To ensure better system performance, use SSL only for sessions when it is needed. Consider adding additional processor resources on the Tivoli Storage Manager server to manage the increased requirements. No other server activity is allowed while initializing the database and recovery log. After you set up server communications, you are ready to initialize the database.
Ensure that you log in by using the instance user ID. Do not place the directories on file systems that might run out of space. If certain directories for example, the archive log become unavailable or full, the server stops.
See Capacity planning for more details. Important: The installation program creates a set of registry keys. That directory becomes the location of the server. The registry tracks the installed servers. About this task If you use the Tivoli Storage Manager configuration wizard to create a Tivoli Storage Manager server instance, you do not have to complete these steps.
Attention: If the database is unusable, the entire Tivoli Storage Manager server is unavailable. If a database is lost and cannot be recovered, it might be difficult or impossible to recover data that is managed by that server. Therefore, it is critically important to back up the database. Replace these values with your actual values in the commands.
Create a file that is called tsmdbmgr. Open a DB2 command window. Then, issue this command: db2cmd b. This value can be tcpip or sharedmem. For more information about shared memory, see step 4. To ensure that the database can be backed up, this value must be localhost. Ensure that you enter the same tcpport value that is specified in the dsmserv. This log is typically in the server instance directory. However, this log can be placed in any location where the instance user ID has write-permission.
Optional: Configure the server to back up the database by using shared memory. In this way, you might be able to reduce the processor load and improve throughput. Windows 10 Windows 8. EZ-Backup Articles see all.
Use the form linked below that best suits your situation to The software for the EZ-Backup service underwent major changes between version 7. Install Spectrum Protect Client version 8. Caveat emptor. Validate the existing dsm. If you were using the VirtualMountPoint option as a workaround to backup EXT3 format filesystems in a previous version of TSM, these are no longer required and should be removed from your dsm. How can we help?
Search IT Cornell Go. EZ-Backup Articles see all. Use the form linked below that best suits your situation to BUT no over the limit! Cheers Reply Quote. There is no trackpack. Individual tracks can be loaded using TSM.
Also, please update your post on the Win 7 forums on using gpx patch as it may help other users. If I am misunderstanding you, let me know , so that I can explain myself further! Thanks Reply Quote. Update your post here! Yr welcome, enjoy the forums, and GP4 of course.
0コメント