25 July 2013

Advantage and disadvantages of using collocation in TSM Storage Pools

Tivoli Storage Manager has the capability of storing client or group of clients in  few number of tapes as much as possible, this process is called Collocation. When client data is backedup, TSM server tries to use the filling tape which was last used by the client if it has enough space to store the new data. Understanding the effects of collocation can help reduce the number of media mounts, make better use of space on sequential volumes, and improve the efficiency of server operations.

The collocation function is designed to optimize the performance and time needed to perform restore or retrieve operation of client’s data. It gives administrators a facility to store all of the files belonging to either a group of clients, single client, or even a specific client’s filespace on a minimal number of sequential access volumes (usually tapes).

The collocation option is generally where the client requires a fully optimized recovery time. Collocation also makes it possible to avoid conflicts in the restore process, such as when a single tape volume mount is required to restore data for two different clients. When the collocation feature is used, each client’s restore can be completed simultaneously and independently.On the other hand, enabling collocation may lead to longer backup times and additional mounts during backup as well requiring more backup tapes overall.

There are some special considerations for using collocation on copy storage pools. Collocation typically results in a partially filled sequential volume for each client. While partially filled volumes may be acceptable for primary storage pools (because they remain in the library and will be used again during the next migration process), this may be unacceptable for copy storage pools. Because storage pool backups are usually intended to be taken offsite immediately, you will have more partially-filled volumes to go offsite. You will have to decide whether the overhead of taking more partially filled volumes offsite and increasing the reclamation activity is worth the benefit of recovering your most important clients faster in the event of a disaster.

In most cases, considering the price of tape cartridges, and the costs of transporting and storing them offsite, copy storage pools are not collocated.

How to enable Collocation in TSM

To enable collocation in your TSM environment first determine how data should be organized, whether by client node, group of client nodes, or file space. If the decision is to collocate by group, you need to decide how to group nodes
  • If the goal is to save space, you may wish to group small nodes together to better use tapes. 
  • If the goal is potentially faster client restores, group nodes together so that they fill as many tapes as possible. Doing so increases the probability that individual node data will be distributed across two or more tapes and that more tapes can be mounted simultaneously during a multi-session No Query Restore operation.
  • If the goal is to departmentalize data, then you can group nodes by department.
1) If collocation by group is the desired result, define collocation groups using the DEFINE COLLOCGROUP command. Add client nodes to the collocation groups using the DEFINE COLLOCGROUPMEMBER command.

The following query commands are available to help in collocating groups:

     Displays the collocation groups defined on the server.

    Displays the collocation group, if any, to which a node belongs.

    Displays information about the data for one or more nodes in a sequential-access storage pool.

    Displays information about the location of client data in a sequential-access storage pool and the amount of space a node occupies in a volume.

2) Specify how data is to be collocated in a storage pool using the COLLOCATE parameter on the DEFINE STGPOOL or UPDATE STGPOOL command.

update stgpool <stgpoolname> collocate=NO/GROUP/NODE/FILESPACE

3) If you decide later that you want to delete members of a collocation group, you can use the DELETE COLLOCMEMBER command. You can also update the description of a collocation group using the UPDATE COLLOCGROUP command and delete entire collocation groups using the DELETE COLLOCGROUP command.

delete collocmember <groupname> <nodename>
delete collocgroup <groupname>

If you use collocation, but want to reduce the number of media mounts and use space on sequential volumes more efficiently, you can do the following:
  • Define a storage pool hierarchy and policy to require that backed-up, archived, or space-managed files are stored initially in disk storage pools.When files are migrated from a disk storage pool, the server attempts to migrate all files belonging to the client node or collocation group that is using the most disk space in the storage pool. This process works well with the collocation option because the server tries to place all of the files from a given client on the same sequential-access storage volume. 
  • Use scratch volumes for sequential-access storage pools to allow the server to select new volumes for collocation.
  • Specify the client option COLLOCATEBYFILESPEC to limit the number of tapes to which objects associated with one file specification are written. This collocation option makes collocation by the server more efficient; it does not override collocation by file space or collocation by node. 
  • When creating collocation groups, keep in mind that the ultimate destination of the data belonging to nodes in a collocation group depends on the policy domain to which nodes belong. For example, suppose you create a collocation group consisting of nodes that belong to Policy Domain A. Policy Domain A specifies an active-data pool as the destination of active data only and has a backup copy group that specifies a primary storage pool, Primary1, as the destination for active and inactive data. Other nodes in the same collocation group belong to a domain, Policy Domain B, that does not specify an active-data pool, but that has a backup copy group that specifies Primary1 as the destination for active and inactive data. Primary1 has a designated copy storage pool. The collocation setting on PRIMARY1, the copy storage pool, and the active-data pool is GROUP.
  • When the nodes' data is backed up and simultaneous write occurs, active and inactive data is stored in Primary1 and the copy storage pool. Note, however, that although all the nodes belong to a single collocation group, only the active data belonging to nodes in Domain A are stored in the active-data pool. The data in Primary1 and the copy storage pool is collocated by group. The data in the active-data pool is also collocated by group, but the "group" consists only of nodes that are members of Policy Domain A.

13 July 2013

How to Configure TSM Server V6.X and BackupArchive Client 6.4 - Video Tutorial

After installing the server codes, the TSM server and TSM database instance needs to be configured. This module show how to use the Configuration wizard to enable an instance of Tivoli Storage Manager version 6

This below video explains how to configure the TSM server  6.X after installation process such as
  • TSM Server Instance
  • Server DB directories and db instance
  • Active Log, Archive Log, Active-mirror Log and Archive Failover Log
  • TSM Server Admin username and password

This below video explains the basic configuration steps after installing B/A Client V6.4. It explains how to configure dsm.opt file important parameters to start Backup/Restore clients data to TSM Server Storage Pools. It also demonstrates the importance of  using Include/Exclude list while taking Backup/Archive

Tivoli Storage Manager Extended Edition Basics and Features Overview - Video Tutorial

Tivoli Storage Manager Extended Edition adds disaster recovery planning capability for the server, NDMP control for network-attached storage (NAS) filers, and support for larger capacity tape libraries and more tape drives. Tivoli Storage Manager is an enterprise level software from IBM Tivoli family where protects you from the risks of data loss and helps you reduce complexity, manage costs and address compliance with data retention and availability requirements. IBM TSM basic components include TSM Database, Recoverylog and Storagepools. TSM Database contains the metadata of client backups, Recoverylog contains the current DB transaction details whereas Storagepools are logical group of tape volumes where actual client backups are stored
Topics in the below video include the role of the TSM database, storage pool basics, progressive incremental backup methodology, policy management, and disaster recovery management.

In this below Video the starting and use of the TSM command line and GUI interfaces for Tivoli Storage Manager 6.3 are described and demonstrated. It demonstrates how to take Backup/Restore using different TSM interfaces.

12 July 2013

What is IBM Tivoli Storage Manager TSM Suite for Unified Recovery ?

Tivoli Storage Manager Suite for Unified Recovery is a bundle of 10 proven data protection and recovery software products. It helps organizations of all sizes meet a wide range of data management challenges for complex, distributed infrastructures. You can deploy the advanced management tools you need for each of your individual data protection requirements—without having to worry about individual product licenses.

Tivoli Storage Manager Suite for Unified Recovery:

  • Provides extensive data protection—for a wide range of systems including virtual machines, file servers, email, databases, mainframes and even desktops. This bundled solution allows you to use the right data protection tool for each of your requirements.
  • Reduces costs and simplifies procurement and deployment—with per terabyte capacity licensing. You can deploy any of 10 different solution components, in any location and quantity, with a simplified license that measures only the amount of data being managed.
  • Scales to meet the recovery needs of any size organization—by managing up to four billion data objects on a single server. This solution supports more than 50 operating system versions and hundreds of server and storage devices.
  • Manages the entire suite of products from a single user console—you can configure, manage, upgrade, report and monitor all 10 products from a single administration interface.

Provides extensive data protection
  • Provides a wide range of data protection, recovery management and monitoring capabilities using policy-based automation. These include backup and recovery; archive and retrieval; snapshots for online database and application protection; disaster recovery and bare machine recovery; data deduplication and space management for data footprint reduction.
  • Includes: IBM Tivoli Storage Manager Extended Edition, a highly scalable enterprise-class backup/restore, archive and disaster recovery solution; IBM Tivoli Storage Manager for Databases; IBM Tivoli Storage Manager for Enterprise Resource Planning; IBM Tivoli Storage Manager for Mail; IBM Tivoli Storage Manager for Virtual Environments; IBM Tivoli Storage Manager for Space Management and IBM Tivoli Storage Manager for Storage Area Networks.
  • Also includes: IBM Tivoli Storage Manager FastBack® for advanced snapshot and near-instant recovery for Windows and Linux servers; IBM Tivoli Storage Manager FastBack for Microsoft Exchange and IBM Tivoli Storage Manager FastBack for Bare Machine Recovery.
  • Provides online, consistent and centralized data protection for databases, mySAP/SAP R3 environments and email servers running IBM Lotus® Domino® or Microsoft Exchange.
  • Provides a simplified, consistent approach to managing data protection and recovery operations across the entire organization: data centers, remote offices, mobile employees, disaster recovery sites; from laptop to mainframe.

Reduces costs and simplifies procurement and deployment
  • License costs can be reduced through the use of built-in source and target data deduplication. There is no charge for duplicate copies of the data.
  • Through progressive incremental backups, data compression and built-in data deduplication, the amount of backup data being stored is significantly reduced, thereby reducing the cost of the per terabyte license.
  • Reduces overall storage costs through policy-based migration of data to less expensive tiers of storage and automated expiration at the end of the lifecycle.

Scales to meet the recovery needs of any size organization
  • Facilitates a multitude of connections, including Internet, wide area networks (WAN), local area networks (LAN) and storage area networks (SAN).
  • Provides superior functionality, performance and reliability because it uses a fully integrated, enterprise-class IBM DB2 relational database and transaction log to track the managed data’s metadata. No DB2 database administration skills are required.
  • Can eliminate the burden of running backups on a virtual machine by using the VMware vStorage APIs for Data Protection.
  • Supports the Microsoft Volume Shadow Copy Service to perform full-image snapshots of virtual machines in Microsoft Hyper-V environments.

Manages the entire suite of products from a single user console
  • Delivers centralized administration and intelligent data move-and-store techniques to help ease storage management.
  • Manages backup and restore from across system and application types, locations, service level requirements and types of failures.
  • Allows you to configure and set polices for each protected system, monitor and report on both client and server operations, schedule and push upgrades for Microsoft Windows client agents and execute backup and restore operations.

9 July 2013

Follow these steps after restoring Tivoli Storage Manager TSM Database to earlier point in time

After a DSMSERV RESTORE DB is performed, it is recommended to do some additional steps before resuming normal operations of the TSM Server. Restore of the TSM server database to an earlier point in time can cause TSM to encounter data on disk and tapes for which it has no record, resulting in ANR1330E and ANR1331E errors.

It is important to save a copy of the volume history file (volhist.out, captured by running the BACKUP VOLHIST command) on a regular basis. The information in this file can be used to reduce the amount of volume auditing that is necessary for step 4 below.

Steps to do after TSM Database Restoration

After a TSM Server restore to a previous point in time, it is necessary to ensure that the storage pool volumes are consistent with the TSM database which has been restored The following steps should be performed prior to returning the TSM server to normal use:

1. Immediately after the TSM server database is restored, place the following options into the dsmserv.opt file:

NOMIGRRECL (Prevents migration and reclamation from kicking off when the server is started)

DISABLESCHED YES (prevents any schedules from starting when the server is started)

EXPINT 0 (prevents expiration from running when the server is started) 

If set to something other than 0, change the setting to 0 and record the original setting. In step 7 we will remove or reset this option back to the original setting.

2. Start the server in the foreground (DSMSERV)

3. When the TSM server prompt comes up, enter the command DISABLE SESSIONS so that clients will be unable to connect to the TSM Server.

4. Review the saved volhist file, and locate sequential tape or FILE volumes marked as "STGDELETE" and "STGREUSE" in the list. You will need to audit only these types of volumes created after the date of the database backup that has been restored. If the volhist file is lost or unrecoverable, then all sequential volumes must be audited. The audit command is performed as follows:

AUDIT VOLUME <volume_name> FIX=YES

Note that this command will verify the data on the volume against the entries in the TSM Server database. Any items that are not found will be removed from the TSM Server.

5. It is also necessary to audit all of the disk pool volumes with the same command above.

6. Once the audits complete, the data on the volumes will be synchronized with the TSM Database at the point in time of the last full database backup.

7. Halt the server and remove the options added in step one, nomigrrecl, disablescheds yes, and set the expinterval back to its original setting.

8. Restart the server as normal. Issue the command ENABLE SESSIONS so that the clients can connect to the server.

9. It is also good practice to check the actlog for any errors or warning messages (q actlog se=ANR????E begint=-4 and q actlog se=ANR????W begint=-4), and check the nodes, pools etc. just to make sure everything looks good.

1 July 2013

How to Integrate TSM Fastback Server with TSM Server to protect FastBack Client Data

You can configure the backup-archive client to protect FastBack client data by using the client configuration wizard. For TivoliStorage Manager versions prior to 6.1.3, a configuration wizard is available to configure the IBM Tivoli Storage Manager backup-archive client to protect IBM Tivoli Storage Manager FastBack client data. The configuration wizard allows you to generate scripts to manually move data from FastBack to Tivoli Storage Manager.

TSM Fastback Integration with TSM Server Steps

Before you can use the Tivoli Storage Manager Client Configuration wizard for FastBack, you must perform some tasks.
  • Ensure that either the Tivoli Storage Manager FastBack server, or the FastBack Disaster Recovery Hub, is installed and configured for short-term data retention. Also make sure that at least one snapshot has been taken.
  • Ensure that the Tivoli Storage Manager backup-archive client is properly configured with a Tivoli Storage Manager server. Also make sure that the Tivoli Storage Manager client acceptor service (dsmcad.exe) is running. You can use the Tivoli Storage Manager Client Configuration wizard in the Tivoli Storage Manager Java™ GUI, after you install the backup-archive client.
  • You must perform a one-time post-installation setup for these purposes:
    • To specify a FastBack user name and password to be used by the wizard, to query and mount volumes from the Tivoli Storage Manager FastBack repository
    • To run Tivoli Storage Manager Scheduler scripts

  • Set up the Tivoli Storage Manager FastBack credentials file:
  1. The user ID that you specify must have Tivoli Storage Manager FastBack administrative authority. To configure the user ID and password, run this command on the workstation where the Tivoli Storage Manager backup-archive client and FastBack server or Hub are installed:
    cd <TSM_FastBack_install_location>\FastBack\shell

    The <TSM_FastBack_install_location> is the base directory location where Tivoli Storage Manager FastBack client is installed.

  2. Now create a folder called FastbackTSMScripts under the system drive of the workstation, if it does not exist, using the following command:
    mkdir <machine_system_drive>:\FastbackTSMScripts
  3. Now run the fastbackshell command:
    FastBackShell -c encrypt -u userName -d domain -p password -f

    The following options are used in this command:
    • -u specifies the Tivoli Storage Manager FastBack admin user name.
    • -p specifies the Tivoli Storage Manager FastBack admin password.
    • -d specifies the Tivoli Storage Manager FastBack domain for the user name.
    • -f specifies the output file where the encrypted credentials are to be written.

The credentials file must be generated with the name "credential.txt". The credentials file must also be located in the "FastbackTSMScripts" directory of the system drive of the workstation, for the wizard to function properly.
You can use the client configuration in the backup-archive client Java GUI or the backup-archive Web client which are show in below screenshots

Below Screenshots explains more how to Integrate TSM FastBack and TSM Server

  • Initially register the TSM Backup/Archive Client which takes backup of FBclient data in FastBack Server to TSM Server as a client node as shown below. Node Name I used is tsm. Register a Tivoli Storage Manager node for each FastBack client where Tivoli Storage Manager backs up or archives data. The node name must be the short host name of the FastBack client.

  • Now Install TSM B/A client on the Fastback Server.
  • After Installation, open TSM Client Configuration Wizard to define dsm.opt file and set required parameters.
  • Go through all the steps that required B/A client to communicate with TSM Server and click Finish.
  • Now open TSM Setup Wizard to define client and webclient scheduler using DSMCAD as shown below.
  • Similarly Configure TSM Webclient Service by using the following wizard.
  • Now create a folder called FastbackTSMScripts under the system drive of the workstation, if it does not exist, as shown below.
  • Now we need to generate credential.txt file by using the belwo command.

FastBackShell -c encrypt -u userName -d domain -p password -f

This command will store the credentials of the fastbackserver, and allows B/A client to access its repositories for the Backup to TSM Server.

  • Now open the TSM Client Configuration wizard and select Help me configure the client to protect the Fastback Client data.

  • Make Sure you did all the said requiremetns. If you do not configure the credential.txt file properly, you cannot able to go to next step here in this wizard.
  • Select TSM FastBack policy and client & volumes to be protected by TSM Server and click Next.
  • Check the protection options, protection type and client name as below and click Next.
  • Specify the schedule options and times as required.
  • Specify the TSM Server Administrator User Id and password to define the TSM Schedule.
  • Now, register fastback client as client node in TSM Server as shown below.
  • Finally its time to double all your configurations to confirm and apply. Then click Finish.
  • You can also check in TSM server if the schedule for protecting FastBack client data has been correctly done or not by using Q event * * command.

How to restore client data from TSM Fastback server repository

With the snapshots that are stored on the FastBack Server, you can recover data that is backed up. There are several ways to recover data:
  • Recover volumes. For more information about recovering volumes
  • instant restore with FastBack Mount. For more information about instant restore
  • Recover files. For more information about recovering files
During the cleanup process, FastBack Server detects snapshots that are potentially corrupted. When FastBack Server detects a potentially corrupted file, a warning message is displayed and a message is written to the FastBack Server log. During the next scheduled snapshot of the volume a job is run to repair the snapshot. You must not use a potentially corrupted snapshot. If a problem occurs and you need the data before the repair job for the snapshot completes, complete the following steps:
  1. Run the file system check tool. You can see the operating system documentation for more help in completing this step.
  2. Run the application consistency check tool. You can see the operating system documentation for more help in completing this step.

TSM Fastback Restore Procedure

Below Screenshots shoes how to restore FastBack data using Volumes and FastBack Mount.
  • Select the Recovery Tab, which shows various ways to restore the client data
  • To restore the data using volume restore, go the Snapshot Monitor tab and select the completed backup and right click on it. Then select Snapshot Volume Restore option.

  • Now choose the destination to restore the backedup data and click Apply

  • Alternatively if you choose Disk Restore instead of Snapshot volume restore in the previous screenshot, it will ask source and destination for restore. Select the snapshot and the destination disk for recovery as shown below.
  • You can also use FastBack Mount wizard for recovering the data, select the repository and destination to start the recovery process.

How to take backup through TSM Fastback Client on Windows

To take a backup from FastBack Client to FastBack Server, below tasks should be already completed.
  • A repository should be added in FastBack Server where the server stores client data.
  • Install FastBack Client on client machine and make sure it is running. Use correct hostname or IP address of FastBack Server while starting Client Configurator.
  • Suitable network resources.

TSM Fastback Client Backup Procedure

  • Start FastBack Client Configurator on client machine using corrent fastBack Server IP address and hostname.

  • Open FastBack Manager on the Server, you should see the client hostname in the list under Storage Pool tab. In the belwo screenhsot WIN-7IMV9HRDTBA is our FastBack Client which shows available drives which can be backed up.
  • Select the drive which you to take the backup.

  • Now create policy, which include Job Schedule and Client groups. You can define Job Schedule & Client Groups seperately or you can directly define Policy which automatically defines both of them. Here I am using Policy wizard to define both.

  •  Select the drive to be backed up.

  • After defining Client group and Job schedule, click Finish. You can see the pending job details in below screenshot.

  • Here you can see the status of the backup. It shows that backup has been running and sending data at the speed 51.77Mbit/sec on the bottom pane.

  • Here you can see the repository has been filled 5%.

How to install and configure Tivoli Storage Manager TSM FastBack Client on Windows

In Windows when you run the installation or upgrade process, use a Windows logon ID with Administrator authority.

In Linux run the installation process as the root user. The root user profile must be sourced. If you use the su command to switch to root, use the su - command to source the root profile.

Below schreenshots shows how to install TSM Fastback Client software on client machines 

Read the terms of the license agreement. You must accept the terms of the license agreement to continue the installation and click Next.

Give the Fastback server hostname or IP address to which this client has to send backups.

If the client has only DAS disks, no additional steps are required. When you install the FastBack Client, by default, the SAN Module option is disabled. Use the FastBack Client Configurator to enable the SAN Module option when you use CLUSTER or LANFREE.

If the client has SAN disks, configure the client according to the following steps:
  • From the Start menu, choose Programs > Tivoli Storage Manager > FastBack > FastBack Client Configurator.
  • Verify the DNS host name or IP address for the FastBack Server system.
  • If you have a cluster environment, enable the SAN Module option.
  • Click OK.
You can also use the FastBack Client Configurator to connect a FastBack Client to a FastBack Server. To use the FastBack Client Configurator to connect a FastBack Client to a FastBack Server, complete the following steps:
  • On the computer where you installed FastBack Client, from the Start menu, select Programs > Tivoli Storage Manager > FastBack > FastBack Client Configurator.
  • Type the host name or IP address for the FastBack Server.
  • Click OK.
After you connect a client to a server through the Client Configurator, in the FastBack Manager, you might not see the client in the client list. A client version mismatch is the cause of the problem. To resolve this problem, verify that both the client and the server are using the same version of Tivoli Storage Manager FastBack. After you install the correct version, restart both the client and server by using the Windows Services. To go to to the Services window, click Control Panel > Administrative Tools > Services.

If you start the executable file for the installation process after you complete the initial installation, a Program Maintenance window is displayed. From this window, there are two options:
  • Modify - Use this option to change the location of the installation.
  • Remove - Use this option to uninstall Tivoli Storage Manager FastBack

How to configure Tivoli Storage Manager TSM Fastback Server and Fastback Manager

By default, when you start the operating system, the services for Tivoli® Storage Manager FastBack are started. 

In Windows The Tivoli Storage Manager FastBack services include FastBack Server, FastBack Client, FastBack DR Hub Server, FastBack Mount, FastBack data deduplication, and FastBack Watchdog. These services are started under the Local System Account.

If you experience a malfunction and suspect that the problem might be caused by incorrect authorization, you can run the problematic service from an account that has more privileges. For example, you can log on as a Local or Domain administrator. You can stop and restart the services by using the Windows Services window. To locate the Services window, go to the Control Panel. Go to Administrative Tools > Services.

(Windows 2008 and Vista only) When you start FastBack Mount from the Microsoft Windows Start menu, the service is automatically stopped. You can use the Windows Services window to start the FastBack Mount service. To locate the Services window, go to the Control Panel. Go to Administrative Tools > Services

In addition, when the FastBack Mount user interface is closed, the FastBack Mount service is restarted. You can use the Windows Services window to stop the service.

(Linux only) The only Tivoli Storage Manager FastBack services that run on supported Linux operating systems are FastBack Client and FastBack Mount. These services run as the root user. You can start, stop, and query the services by using the following commands:

Starting & Configuring FastBack Manager

Before you begin

Installing the FastBack Server and FastBack Client on the same system is supported. However, if you install the server and client on the same system, before you start FastBack Manager, enable the SAN Module option. When you install the FastBack Client, by default, the SAN Module option is disabled. For more information about enabling the SAN Module option, see Connecting client to server.

            The default <install_directory> path is /opt/IBM/Tivoli/TSM/FastBack/
            Run the following command:


            Enter the FastBack Server IP address.
  • In the login window, type your user name. The default user name is admin. The authorization policy is case-sensitive. Letters must be typed in the correct case.
  • Type your password. The default password is admin123. The authorization policy is case-sensitive. Letters must be typed in the correct case.
  • Select a domain. The default domain is XPRESS-RESTORE. After you select the domain, the configuration is loaded.Click Login. A message is displayed.
  •  If this is the first time you start the FastBack Manager, you can click Add Repository to identify a repository. If you do not want to identify a repository, click Cancel.
  • After FastBack Manager is displayed, you can add a repository by selecting General Configuration > Storage Pool > Repository Pool. From the menu, you can add or claim a repository.
If the FastBack Manager does not connect to the FastBack Server and the FastBack Server is running on a system that is part of an Active Directory domain, complete the following steps:
  • Change the Active Directory settings to allow for anonymous enumeration SID and name translations.
  • Log off.
  • Log on.
  • Restart the FastBack Server service.
Grant the FastBack Server service administrative rights by changing the logon as properties for the FastBack Server service to an Active Directory administrator account.

User Management & Security

With the correct user management definitions, the administrator can secure system access.
With Tivoli Storage Manager FastBack, the administrator can control user permissions by assigning users to user groups. 

User groups are named, logical entities. You can assign permissions and users to user groups. There are two ways to set up user groups:
  • Create and configured user groups in FastBack Manager. User groups that you create in FastBack Manager can have different access permissions. For example, one group might have administrator permissions and another group might have more restrictive permissions. To create and configure user groups, you must be classified as a super user with administrator permissions.
  • Default user groups that are included with FastBack Manager cannot be changed.

  • Use Microsoft Active Directory user groups that are added to the Active Directory group list in FastBack Manager. FastBack Manager recognizes these group members for the Active Directory as super users. These users are automatically assigned the correct access permissions.
There are some rules to follow when setting up user groups:
  • A user can be assigned to only one user group.
  • If you are the administrator, change the default password. Use the following rules when changing a password:
    • Passwords cannot match the user name.
    • Password must be at least 8 characters.
    • Passwords cannot exceed 20 characters.
    • Passwords must include at least one digit and one letter.
    • The following characters cannot be used: \*?\"<>|;^'.$#@&,
You can create new users or change existing users by using the Users and Groups window.

 Configuring Fastback Server Screenshots: 

  • Go to Windows services and the user id which you want to use for the fastback server operationsas shown below.

  • Creating Activedirectory user which will make him a Super User in Fastback Server. Later if you find that Fastback manager says limited mode, then this is the first thing you should check. Check if the username you have used having the privileges or not. In the below screenshot I have added user administrator to the AD group Administrators which have all privileges on this system.

Now, its time to login to the Fastback manager with default username and password and make that administrator username as super user. To do that please see below screenshots.

After first installation it will ask to add repository, you can add it now or add it later. I will show you both ways.

Second Method to add repository in Fastback Server. This process can be done anytime after you installed the server. Right click on Repositry and select Add Repository Wizard, you will a pop-up window as shown below.

In below screenshot, you can see that Repository has been added and used 1%. 

  • Since we are using the default username & password, it is advised that we make our own username as super user. To do that , we need to add that Administrators AD group to Fastback server. Check it out, how to do it.

  • I have added administrator user in TSMTEST domain to the Administrators Active Directory Group, this group should have all privileges. In the below screen I am just selecting that AD group and add the users. Right click on AD Groups tab to add groups

  • Now, we can login with our username and password. This way your server is secure and also have all privileges.

We have Installed and configured the Fastback Server. Now our server is ready to take the backup from Fastback Clients. Our next step is to install TSM Fastback Client on client machine and take the backup. Check it out how to do it in the next post.