When encountering problems like this, it helps to see that actual commands
that the Admin Center sent to the TSM server. The commands appear in the
activity log.

In this case, what is happening is that the Admin Center is implicitly
incuding the FORMATSIZE option along with the DEFINE LOGCOPY, on the
mistaken assumption that the volume does not already exist. So this
problem is not specific to raw logical volumes, but also includes the case
where you are defining a volume as a regular file system file and the file
already exists. I'm sure this problem also exists for DEFINE DBCOPY, too.

The server developers are looking at this, but for now, your work-around
is the correct one.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-10-20
02:18:17:

> Another error:
>
> Using the ISC it's not possible to create a mirror of a log volume using
> raw logical volumes. Each time I select "Mirror this volume" and specify
> the path of the rlv (/dev/rtsmlog3) the process ends with the error
message:
> ANR7862W File Already exists when creating volume /dev/rtsmlog3
> I have to use the command line and create the mirror manually:
> define logcopy /dev/rtsmlog1 /dev/rtsmlog3
> --
> Regards,
>
> Dirk Kastens
> Universitaet Osnabrueck, Rechenzentrum (Computer Center)
> Albrechtstr. 28, 49069 Osnabrueck, Germany
> Tel.: +49-541-969-2347, FAX: -2470