Tivoli Header

Administrator's Guide


Managing Server-Free Data Movement

As an administrator you can issue the QUERY STATUS command to find out if server-free data movement has been set to on or off. To do this, you would issue the following:

query status

For more information on QUERY STATUS, see Administrator's Reference.

Additional administrator activities for server-free data movement operations include defining and managing:

Managing the Size of Data Movements

In order to better manage a server-free data movement, the server divides a volume image into smaller batches of data. You can set the size of the batches by specifying the BATCHSIZE parameter when you issue the SET SERVERFREE command. The BATCHSIZE parameter specifies the amount of data, in megabytes, that will be copied in a single batch of server-free data movement. The minimum value is 10 megabytes, the maximum value is 1000 megabytes, and the default value is 80 megabytes.

For example, if you wanted to set a batch size of 500 megabytes, you would issue the following:

set serverfree batchsize=500

The BATCHSIZE parameter is important because the correct batch size may be needed to prevent SCSI time-outs from occurring between the server and the data mover while data is being copied during server-free data movement. However, batch size will affect the performance of the data movement operation itself. A smaller batch size will result in more SCSI commands being issued to the data mover.

There are a several factors to consider when determining what batch size will work best for you. For example, the amount of traffic that is on the SAN during peak operation times, the amount of average traffic on the SAN, how busy the server and data mover are, the size of the volume that is being backed up or archived, and even the type of data to be backed up or archived.

To view the current batch size setting, issue the QUERY STATUS command. For more information, see Administrator's Reference.

Managing Data Movers Used in Server-Free Data Movement

You can update, query, and delete the data movers you define for server-free data movement operations. Additionally, you can utilize the DEFINE and UPDATE DATAMOVER commands to specify the number of supported concurrent copy operations.

Concurrent Copy Operations

You can specify the number of concurrent copy operations that the data mover can support by including the COPYTHREADS parameter when you issue the DEFINE DATAMOVER or UPDATE DATAMOVER commands. The COPYTHREADS parameter is used to govern how many copy commands can run concurrently on a server at any one time. For example, if you wanted to be able to perform 5 concurrent server-free data movement operations, you would issue the following when defining a data mover:

define datamover scsi1 type=scsi wwn=2002006045160d2a serial=21081300957 
 dataformat=nonblock copythreads=5

The default value is 1. Please refer to the documentation for your device to obtain the maximum value. The number must be greater than 0. If other programs or servers will be using the extended copy capabilities of the data mover device, you may want to specify fewer than the maximum number of concurrent copy commands supported by the device for this parameter. For more information, see Administrator's Reference.

Replacing a Data Mover

If your data mover was replaced, you could update the data mover and specify a new world wide name and serial number to preserve the data mover and its associated path definitions. To do this, first determine the world wide name of the new data mover. See Step 2. Determine World Wide Name, Serial Number and LUN.

Next you can issue the update command to specify the new world wide name and serial numbers:

update datamover serverfree1 wwn=124536484565859u serial=1973989 

You could then issue a detailed query command to make sure that the changes have taken effect properly:

query datamover serverfree1 type=scsi format=detailed

For more information, see Administrator's Reference.

Deleting a Data Mover

You are not able to delete a data mover unless you have already deleted the paths defined for this data mover. For example, if you wanted to delete the datamover SERVERFREE1, you would do the following:

  1. Find out what paths were associated with the data mover by issuing the QUERY PATH command:
    query path serverfree1 sourcetype=datamover
    
  2. Delete all paths that list the data mover as the source. For example, if the output of the QUERY PATH commande specified a path from the data mover to the tape drive named DRIVE1, you would delete the path by issuing the DELETE PATH command:
    delete path serverfree1 drive1 sourcetype=datamover desttype=drive
     library=scsilib lun=2
    
  3. Once you have deleted all of the paths associated with the data mover, delete the data mover by issuing the DELETE DATAMOVER command:
    delete datamover serverfree1
    

For more information, see Administrator's Reference.

Managing Tape Libraries and Drives Used in Server-Free Data Movement

Managing tape libraries and drives used for server-free data movement is similar to managing hardware used for traditional Tivoli Storage Manager operations.

Updating a Tivoli Storage Manager Drive for Use With Server-Free Data Movement

In order to update a drive to be used for server-free data movement operations, for example if you had to replace a drive, you must first find the world wide name, serial number and LUN of the drive. See, Step 2. Determine World Wide Name, Serial Number and LUN for more information about finding the world wide name, serial number, and LUN.

For example, if you replaced a drive, you could update the drive for server-free data movement and include the world wide name and serial number of the new drive:

update drive scsilib sandrive1 wwn=876985784395698d serial=54638k

Next you would need to determine that the LUN of the drive now matches the LUN in the path.

  1. Determine the LUN as described in the section, Step 2. Determine World Wide Name, Serial Number and LUN.
  2. Issue the QUERY PATH command to determine the LUN defined in the path.
  3. If the LUN reported in the path does not match, issue the UPDATE PATH command to update the LUN:
    update path datamover1 sandrive1 srctype=datamover desttype=drive
     library=scsilib lun=3
    

You may additionally need to update the server path. For more information on these commands, see Administrator's Reference.

Managing Disks Used in Server-Free Data Movement

You can query, update, and delete client disks used in server-free data movement operations. For example, if maintanence was being performed on a client-owned disk, you could issue the UPDATE DISK command to take the disk offline.

update disk serv1 Harddisk1 online=no

If you wanted to view the information specific to disks that are defined to the server, you could issue the QUERY DISK command. For example, if you wanted to view the status of all of the disks defined to the server, you would issue the following:

query disk

If you replace a device, it is recommended that you verify the path definitions. For more information, see Administrator's Reference.

Managing Paths for Server-Free Data Movement

You can query, update, and delete paths between data movers and storage devices. It is important to remember that when replacing drives, you should verify the path information and upate it if necessary. For more information, see Administrator's Reference.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]