Troubleshooting problems and issues in TSM Fastback for workstation Clients V6.3

Files are not backed up by Tivoli Storage Manager FastBack for Workstations

Files can fail backup for several reasons. Some common reasons are provided in this section.

• Storage for backup copies is not correctly configured in Tivoli Storage Manager FastBack for Workstations.  If the area to store backup copies of your protected files is not properly specified, Tivoli Storage Manager FastBack for Workstations can not back up files.

• If Files to protect are incorrectly configured in Tivoli Storage Manager FastBack for Workstations.  The files that Tivoli Storage Manager FastBack for Workstations protects are configurable. If you have configured your list of protected files incorrectly, Tivoli Storage Manager FastBack for Workstations does not back up the files.

• Files in use are not backed up by Tivoli Storage Manager FastBack for Workstations. Attempts to perform a local or remote backup of a file that is saved but not closed can fail. This can occur with Quicken Quick Books objects (files with an extension ending in .QBW).

• Files are not backed up to Tivoli Storage Manager server if Tivoli Storage Manager node name does not match the host name. If the node name assigned by the Tivoli Storage Manager administrator is different from the Tivoli Storage Manager FastBack for Workstations client host name, back up to the Tivoli Storage Manager server fails. The reason is that the Tivoli Storage Manager FastBack for Workstations cannot identify itself properly to the Tivoli Storage Manager server.

• If Tivoli Storage Manager client node lacks authority to delete backup copies. If Tivoli Storage Manager FastBack for Workstations does not have delete backup permission on the Tivoli Storage Manager server, it cannot successfully purge older files when the designated storage space is getting full.

Tivoli Storage Manager FastBack for Workstations user interface replaces existing browser session

When the user interface is started, it replaces an existing browser session. You can change this behavior by changing the settings in more recent versions of Mozilla Firefox and Internet Explorer. In Internet Explorer version 7, you can prevent this behavior. In Internet Explorer version 7 and later versions, change the tabbed browsing settings as follows:

1. In Tools menu, choose Internet Options. The Internet Options notebook displays.
2. Select the General tab. The General page displays
3. In the Tabs section, click on Settings. The Tabbed Browsing Settings dialog displays.
4. In the Open links from other programs in: section, click the A new window option.
5. Click OK, the Tabbed Browsing Settings dialog exits.
6. In the Internet Options notebook, click OK.
7. The Internet Options notebook exits and your new settings are applied.

In Mozilla Firefox version 1.5.0.10 and later versions, change the browsing settings as follows:

1. In Tools menu, choose Options. The Options notebook displays.
2. Select the Tabs tab. The Tabs page displays
3. In the Open links from other applications in: section, click the A new window option.
4. Click on OK, the Options notebook exits and your new settings are applied.

Tivoli Storage Manager FastBack for Workstations user interface contains no file data

If the Tivoli Storage Manager FastBack for Workstations daemon is not running, or if your browser is in offline mode, the Tivoli Storage Manager FastBack for Workstations user interface contains no file data. This condition is accompanied by an error message which begins like this: FPA_getNamedObject: Could not find:. There are two possible causes for this problem.

• Your browser is offline.

Your browser must be in online mode to see file data. Internet Explorer and Firefox browsers are turned on- or off- line by checking or unchecking File > Work Offline from the browser menu. Confirm that this menu item is not checked.

• The Tivoli Storage Manager FastBack for Workstations daemon is not running.

To determine if the Tivoli Storage Manager FastBack for Workstations daemon is running, and restart if necessary.

The number of backup copy versions is greater than configured in Tivoli Storage Manager FastBack for Workstations

The number of backup copy versions exceeds How many versions to keep configuration setting. The problem occurs when file versions are not tracked properly.

The problem can occur because data folders were not removed between an uninstall and a new installation. The new installation does not have a record of the backup copies created from the previous install and use of the product. This can occur on local storage, remote storage, or both. For a list of folders to remove after uninstall, and before installing again, see Cleaning up after uninstallation.

The problem can also be caused, on remote storage only, because of changes to the encryption or compression settings.

When encryption or compression settings are turned on or off, the versions counter is reset to 0, even if some backup copies exist. This behavior results because Tivoli Storage Manager FastBack for Workstations tracks file versions without encryption/compression differently than file versions with encryption/compression.

As an example, assume that a file file.txt is continuously protected, and reached its five version limit (5 is the default version limit). The backup copies were not encrypted or compressed. The user then enables compression. Tivoli Storage Manager FastBack for Workstations then creates up to five new backup copy versions of the file. The restore view shows five versions of the file having name file.txt (corresponding to the original five versions backed up without compression), and five versions of the file named file.txt.cdp (corresponding to the new five versions backed up with compression enabled).

Limit user access to files on a target file server

Set up the security permissions on a target file server to make sure that users only have access to the files that they back up.

By default, the first client that connects to a given server share creates the RealTimeBackup directory. Permissions assigned to the RealTimeBackup directory do not prevent users from reading files they do not own.

The settings used in this example assume one primary user of Tivoli® Storage Manager FastBack for Workstations on the client. This primary user is the first user from a client that connects to the server and creates the subdirectory for files backed up from that client. If Tivoli Storage Manager FastBack for Workstations operates from other accounts on that client, failures might occur when copying files to the remote server. Error messages such as Failed to open the destination file are logged to the activity report.
Windows file server.

Restoring many files from a single directory Tivoli Storage Manager FastBack for Workstations

When restoring many files from a single directory using the restore wizard, a message saying that the script is taking too long displays.

When using the restore wizard to list the contents of a directory containing over 3000 files, the browser issues a message saying that the script is taking too long. If you see this message, you can choose to allow the script to continue. Otherwise, you can also choose to customize the behavior of this dialog to avoid the message.

Backup fails after configuration because of insufficient IPV6 permissions

If Tivoli Storage Manager FastBack for Workstations does not have IPv6 or the appropriate permissions to the IPv6 path, then reports cannot be sent to the Central Administration Console.

If you do not have IPv6, Tivoli Storage Manager FastBack for Workstations is not able to report to the Central Administration Console (CAC). After configuration, Tivoli Storage Manager FastBack for Workstations uses the IPv6 path to reach the administration folder. If the client was using an IPv4 path prior to this release, it switches to IPv6.

Configuration scripts created using the CAC use the IPv6 path in the configuration script field to denote the location of the administration folder. If the user does not have IPv6 or does not have the appropriate permissions to the IPv6 path, then Tivoli Storage Manager FastBack for Workstations will not be able to send reports to the CAC. To resolve the issue, set up IPv6 and ensure that the account running the client has the correct permissions to the IPv6 path.

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

How to restore TSM FastBack Exchange Individual Email and .PST file - Video Tutorial

Points to remember while doing this FB Exchange Individual Email restore process:

Define the correct FastBack server IP address in the FastBack client configuration.If the NIC interfaces on the FastBack server have IP addresses that belong to different networks, use the route command on the FastBack client computers to connect to the correct FastBack server IP address. It is best practice to maintain single NIC card on FastBack server to restrict annoying problems like this

Example (Windows):

route add <fastback address="" ip="" server=""> <fastback address="" gateway="" ip="" server="">

The <fastback address="" ip="" server=""> is the IP address of the NIC to which the FastBack server service is assigned.

The <fastback address="" gateway="" ip="" server=""> is the IP address of the FastBack server NIC, which is connected to the same network with the FastBack client.

========================================================================

FastBack Client doesn't connect to FastBack Server even though the correct IP address of the server is specified in FastBack Client Configurator. This problem happens in case that hostname of the server cannot be resolved by specified IP address.

Add hostname and IP address into hosts file of the client machine, or specifies DNS server in the property panel of Internet Protocol (TCP/IP) to resolve hostname by IP address.

========================================================================

After you install Tivoli Storage Manager FastBack Server software, any drive you attach to the FastBack server will need to be opened for read/write privileges before being used.

If you use the "Add Repository Wizard" to add a disk to the Repository, you can select to add the whole disk to the repository, and FastBack Manager will open the disk for read/write for you, so you do not have to perform the DiskOpen.

If you plan to add the volume (e:\(New Volume) in this case), you must use the DiskOpen utility.

Warning: Attaching a disk with existing data to the FastBack server is not recommended since the existing data might get corrupted.

========================================================================

A FastBack for Exchange restore fails with MAPI Error even when the Storage Group Database is mounted. The following error message is displayed:

"FBSX7059E Error enumerating items in mailbox.
Ensure that Storage Group Database is mounted."

Complete the actions in the following checklist to resolve the problem:

·       Ensure that a mailbox exists.

·       Ensure that the mailbox is active. In other words, you can log into this mailbox and you can send or receive messages.

·       Ensure that you have sufficient privileges to access mailbox.

·       Ensure that the Exchange server where the mailbox database is located is accessible.

·       Ensure that the Microsoft Information Store service is running.

·       Ensure that the Microsoft Exchange System Attendant service is running.

·       Ensure that For Exchange 2010, the RPC Client Service is running.

After you verify all of these checks, install ExchangeMAPICDO again.

 =======================================================================

On Exchange Server 2010, restore of an individual mailbox fails with this message:
"Mailbox restore failed. ACN5909E The MAPI subsystem logon has failed.
Please check that you have an active mailbox and sufficient privileges for this operation."

Resolving the problem

Due to Microsoft changes in Exchange Server 2010, it was necessary to have both the Client Access Server Role and the Mailbox Server Role installed on the machine where the Data Protection for Exchange mailbox restore is being performed. This limitation only exists until the following fixes are applied.

Microsoft has corrected this problem and the fix is included in the Exchange 2010 SP1 Rollup 2 release. The Data Protection Exchange client will also need to be upgraded to version 6.1.3.1 or greater as indicated in APAR IC73387. After both of these fixes are in place, then the Mailbox Restore will be able to be performed when the Client Access Server and Mailbox Server roles are on separate machines within the Exchange 2010 environment.

If the Data Protection for Exchange has been upgraded, but not the Exchange Server software, it is possible to set the CLIENTACCESSserver parameter in the tdpexc.cfg file to point to the CAS Server directly. This will also allow the individual mailbox restore to process when running on an Exchange 2010 Server that has not been upgraded to SP1 Rollup2 or greater.

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

What is Tivoli Storage Manager TSM Fastback for Workstation clients - Video Tutorial

 IBM Tivoli Storage Manager FastBack for Workstations is a data protection solution for user workstations and notebook computers on the Microsoft Windows platform. Tivoli Storage Manager FastBack for Workstations clients offer transparent, real-time replication and scheduled backup services. The central administration console allows you to manage many clients throughout the enterprise.

Tivoli Storage Manager FastBack for Workstations client

The Tivoli Storage Manager FastBack for Workstations client provides a flexible, easy to use file protection system. Your most important files can be continuously protected. Your less important files can be protected at scheduled intervals to save time and storage space. Email files can also be protected. And you can prevent any changes (including deletions) to files in folders that you designate as vaults.

Continuously protected files are backed up to a local drive. This means that backup copies are created even when network conditions prevent storing backup copies remotely. Continuously protected files can also be stored on remote storage locations, when network connections allow. If a remote location is not available when you change a continuously protected file, the Tivoli Storage Manager FastBack for Workstations client makes a backup copy on that device as soon as the device becomes available. Scheduled backup copies are created on the interval that you configure (hourly, weekly, daily, or monthly). If the remote device for scheduled backups is not available at the time of the backup, theTivoli Storage Manager FastBack for Workstations client makes backup copies on the remote location as soon as that device becomes available.

Every time you change a file, a backup copy is created. You can choose which version of a protected file you want to restore, and configure how many backup copies to save.

This diagram provides an overview of how the Tivoli Storage Manager FastBack for Workstations client protects your data.

After installation of a Tivoli Storage Manager FastBack for Workstations client, the client immediately provides continuous protection for a pre-configured list of files. You can see the backup copies in the \RealTimeBackup\ folder in the root of your primary drive. The backup copies can also be seen in the list of files that you can restore with the Restore Wizard of the client. The default space allocated for your backup copies is 500 MB.

You can configure other lists of files to protect, other storage areas, scheduled protection, and other protection options, using the client or the central administration console.

Tivoli Storage Manager FastBack for Workstations can store backup copies on a Tivoli Storage Manager server, but there is no requirement to use Tivoli Storage Manager. Tivoli Storage Manager FastBack for Workstations is a stand-alone product and has no dependencies on Tivoli Storage Manager or Tivoli Storage Manager FastBack.

Basics of Tivoli Storage Manager FastBack for Workstations central administration console (CAC)

With the Tivoli® Storage Manager FastBack for Workstations central administration console, you can centrally manage many Tivoli Storage Manager FastBack for Workstations clients.

With the central administration console, you can manage Tivoli Storage Manager FastBack for Workstations clients in the following ways:

• Discover existing Tivoli Continuous Data Protection for Files and Tivoli Storage Manager FastBack for Workstations clients.

• Monitor the activity of clients to determine the health of your data protection system.

• Tune performance of clients and react to potential problems to maintain the highest level of data protection. You can update configurations and send command scripts.

• Deploy software updates throughout the enterprise.

The central administration console is a tool for monitoring and managing the clients. The central administration console makes an administrator's job easier, but is not a requirement for protecting your data. Tivoli Storage Manager FastBack for Workstations clients can protect your data without the central administration console. If you do not install the central administration console or if the central administration console is not running, your data is still protected by the Tivoli Storage Manager FastBack for Workstations clients.

Tivoli Storage Manager FastBack for Workstations can store backup copies on a Tivoli Storage Manager server, but there is no requirement to use Tivoli Storage Manager. Tivoli Storage Manager FastBack for Workstations is a stand-alone product and has no dependencies on Tivoli Storage Manager or Tivoli Storage Manager FastBack.

The following concepts are key to understanding the central administration console: groups and administration folders:

Groups

With the central administration console, you can administer many clients at a time. You can filter and select clients based on several criteria, but a typical filter is achieved by assigning clients with similar data-protection needs to the same group.

Administration folders

The central administration console communicates with clients by sharing information with clients in administration folders.

• Groups
  Groups allow you to manage many clients with a single action.
• Administration folders
  Clients pull configuration information, commands, and software updates from administration folders. The central administration consolemanages clients by sharing information with clients in administration folders.
• Information currency
  The client information that is listed in the central administration console is as current as the reports received from the clients.

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

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
   
   
   <machine_system_drive>:\FastbackTSMScripts\credential.txt 
   

   
   
   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

<machine_system_drive>:\FastbackTSMScripts\credential.txt 

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.

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

How to move or restore TSM Fastback Server repository with the same exisitng server configuration

If it is required to move the existing TSM Fastback server repository to a new machine or storage due to various reasons, IBM has a recommended some methods to do it. It is recommended to follow the recommended method in order to secure your backups.  This post will explain how to move an existing TSM Fastback server to another machine or how to claim an old Fastback repository to a new Fastback Server without losing your configuration settings.

Moving or Claiming a TSM Fastback Server Repository:

If you are upgrading your Fastback server, or just moving to another machine, you can use this as a general guide on steps for the move, and what files to move to the other machine. This is for Fastback servers that are currently running and whose data can be accessed. This method will help you keep your data/repository, your policies, and your schedules. This is the IBM recommended method and I advice you to first test this on a test fastback server and implement on the production server to minimize errors.

Step 1: Make a copy of essential FastBack Configuration files.

The First step is to backup a copy of FastBack Servers essential configuration files. Before you copy the files make sure to stop the FastBack Server Service from the services control panel. You should do this step on a daily basis to secure your Fastback server from sudden disasters. The FastBack Configuration files are located by default in the 

"C:\Documents and Settings\All Users\Application Data\Tivoli\TSM\Fastback\Server" directory. 

You can copy the whole folder, or to save space you can just copy the following configuration files, to a temporary location on your network. 

1. History.txt and History.txt.sig: This is keeps track of all the snapshots in your repository
2. Orabr_Conf.txt and Orabr_Conf.txt.sig: This keeps track of your general Configurations
3. Conf.txt and Conf.txt.sig: This keeps track of policy and scheduling configurations
4. Clog10.sf: General Log and error messages
5. Users_enc..txt and Users_enc.txt.sig: Keeps log in and user account information
6. Inprogress.txt and Inprogress.txt.sig: Keeps the current Job ID counter
7. State.txt and State.txt.sig: Keeps the current state of the different process that are running

Step 2: Remove the old Fastback Server from the network.

This step is very important because even if you uninstall Fastback server, fastback clients will still point to the old Fastback server. Power down your old server and remove it from the network. Attach your new server to the network and power it up. Move any physical drives that need to be attached to the target (the new Fastback Server) at this time.

If you attach a drive or drive array to the target server after the Fastback Server software has been installed you will need to use the DISK OPEN utility to allow read and write privileges for it (by default any disk added to the Fastback server after Fastback software has been installed, is read only).

Step 3: New Fastback Server Installation

Make sure your new computer meets the requirements for TSM Fastback Installation. Install the Fastback software on the target computer. Go through the Installation Wizard and choose the TSM Fastback Server option.

If you change the network name on the target server, you will have to manually open up the Client Configuration on the client machines and change the target to the new Fastback server (This will also be true if you are using IP address instead of network names).

Step 4: Copying Over the Policies and Configuration Files

This is the important step where you should copy the important files which have all the configuration details of your old Fastback Server. Stop the FastBack server Service and then copy over the data from step one. Only copy over the following files. Please don't play with these important files at any circumstances, if they are corrupted then they will be useless.

1. History.txt
2. History.txt.sig
3. Orabr_Conf.txt
4. Orabr_Conf.txt.sig
5. Clog.sf
6. Users_enc.txt
7. Users_enc.txt.sig
8. Inprogress.txt
9. Inprogress.txt.sig
10. State.txt
11. State.txt.sig

Place copies of them in the following locations:

1. C:\Documents and Settings\All Users\Application Data\Tivoli\TSM\Fastback\Server

2. C:\Documents and Settings\All Users\Application Data\Tivoli\TSM\Fastback\Server\Mirror

Step 5: Moving or Claiming your Repository

Start the FastBack Server Service after completing step 4. It will take a couple of minutes to go through it initialization phase. After the initialization phase, approximately 5 minutes, you can start the FastBack Manager GUI. Upon start up the FastBack Server is not going to automatically know where the repository space is. You will need to go to the 

"General Configuration -> Storage Pool -> Repository Pool", right click on repository pool and select "Claim Repository". You will need to claim each repository space you had for you old server. Make sure the repository volumes keep the same drive letter as they had on the original server.

If you start the Fastback Manager and it is in Limited Mode, you will not be able to "Claim Repository" until you fix the limited mode issue.

Step 6: Checking your new Fastback Server Configuration setup

You can verify that the procedure worked by making sure all your settings exist in the configuration menu and that your policies exist as well. You can also select any particular policy and Right Click it, and select "Run Snapshot", this will verify that your new server can communicate with the clients. Check to make sure that the snapshot ran in the Snapshot Monitor.

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]

How to troubleshoot TSM Fastback server connection issues and errors

 In this post I will discuss some of the common errors and return codes that we see while working on TSM Fastback Server. The best solution to avoid these annoying errors is to read the manual and meet all the requirements before you start playing with it.

FastBack Client may not connect to the server when specifying IP address in Client Configurator

FastBack Client doesn't connect to FastBack Server even though the correct IP address of the server is specified in FastBack Client Configurator. This problem happens in case that hostname of the server cannot be resolved by specified IP address. FBSA6037E message box brings up from FastBack Client Configurator in case hostname cannot be resolved by the specified IP address.

The following errors can be found in FastBack Client technician logs after FastBack Service restarts.:

E18.ORA_Agent : OAI_S_Init: Failed to resolve host name nnn.nnn.nnn.nnn

E18.ORA_Agent : OAI_S_Init: Will wait 1 hour before exit and restart

Solution:

Add hostname and IP address into hosts file of the client machine, or specifies DNS server in the property panel of Internet Protocol (TCP/IP) to resolve hostname by IP address.

FBSG5804E Please verify IP/Computer name because of connection failure at 127.0.0.1

The FastBack Manager cannot connect to the FastBack server. The following error comes up in a dialogue box upon FastBack Manager start and looks like this:

 Solution:

The default location for the FastBack server technician logs is here:

Windows 2003: %documents and settings%\all users\application data\tivoli\tsm\fastback\ 

Windows 2008: %programdata%\tivoli\tsm\fastback\

Review the latest technican log (FAST_BACK_SERVER040.sf) and search on the failure message

Specifying the Fastback server hostname or IP address would solve the problem in most cases.  If not clicking connect option multiple times until the dialogue box disappears will work as well. However, this error message will not stop any of your fastback server processes. 

What is FastBack Checkpoint Snapshots ?

In the FastBack Manager there is an option to run a Checkpoint snapshot against the policy which most of us never use it. A Checkpoint Snapshot can be performed by right clicking on a policy and selecting Run Check Point. 

A Checkpoint will compare the data on the client against the data on the server and backup all changes that have occurred since the last known successful Full, Incremental Delta Block, or Checkpoint snapshot. When performing a Checkpoint backup, blocks that were captured with a regular Incremental Snapshot will be recaptured. Although this will again backup the blocks, it will not fix any corruption that may have occurred within the snapshot data.

FBSS7068E the volumes length exceeds the maximum support volume length

Some of the related return codes of this error are FBSS7068E, FBSS7068E, and FBSS7027E. All Snapshot backups will get aborted with these return codes when attempting a snapshot. The possible main reason would be if snapshot size exceeds 2TB.

To know why the backup has been aborted right click on the aborted snapshot and select Events. Window may show the following errors:

FBSS7068E The volume's length exceeds the maximum support volume length

FBSS7027E System error. Fault [8179:0x00000100]. Process ended.

FBSS7037E Procedure aborted

Solution:

There is no exact solution for this error if you have configured your Fastback server without meeting all the Fastback Server requirements. There is a FastBack limitation whereby the snapshot size cannot exceed 2TB or the snapshot will abort. This size limitation is noted in the FastBack manual. Thats why it is always important to read the manual before you use it.

Tivoli Storage Manager FastBack does not support backing up of volumes larger than 2 TB. Ensure to check that the volume you are backing up is less than 2 TB.

If you are stuck in this kind of situation, the only solution is Uninstall Fastback Server and change your disk size (must be less than 2TB). Reinstall Fastback server with all the requirements met and try the snapshot backup again. 

Read More

[facebook src="Uptodatewithme" width="500" height="400" hide-cover="true" posts="true"/]