Adam,

Make sure that the TSM server runs under a Windows account that has full
access to the network shares (domain admin to be sure).

A local system account does not have any rights on a network drive.

I've tested such a setup already and it worked fine.

Regards,
Kurt

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Crosskey, Adam - Resources, ICT Services
Sent: woensdag 8 februari 2006 10:52
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] backup to UNC path

Has anyone successfully backed up a primary pool to a copy pool on another
server?
We are trying this using w2k3 servers, TSM 5.3.2.1.
Although the scratch vols get created  (50MB) on the target server, they are
not being written to. The permissions on the shared target folder are
everyone fullcontrol (share and NTFS).
This is what we see in the pool during a backup:

Volume Name                            Storage                   Device
Estimated    Pct   Volume
                                                   Pool Name    Class Name
Capacity   Util   Status
------------------------  -----------  ----------  ---------  -----
--------
\\CENTSM01\METACOPY\000-  METACOPY     METACOPY          0.3  100.0    Full

 00F7A.BFS

\\CENTSM01\METACOPY\000-  METACOPY     METACOPY          0.3  100.0    Full

 00F7B.BFS

\\CENTSM01\METACOPY\000-  METACOPY     METACOPY          0.3  100.0    Full

 00F7C.BFS

\\CENTSM01\METACOPY\000-  METACOPY     METACOPY         50.0    0.3  Filling

 00F7D.BFS

\\CENTSM01\METACOPY\000-  METACOPY     METACOPY         50.0    0.0   Empty

 00F7E.BFS




The information in this e-mail, together with any attachments, is
confidential. If you have received this message in error you must not print
off, copy, use or disclose the contents. The information may be covered by
legal and/or professional privilege. Please delete from your system and
inform the sender of the error. As an e-mail can be an informal method of
communication, the views expressed may be personal to the sender and should
not be taken as necessarily representing the views of the Oxfordshire County
Council. As e-mails are transmitted over a public network the Oxfordshire
County Council cannot accept any responsibility for the accuracy or
completeness of this message. It is your responsibility to carry out all
necessary virus checks. www.oxfordshire.gov.uk