• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

DOMAIN ALL-LOCAL on Windows uses UNC path!?

baldonia

Active Newcomer
#1
Hello everyone, I discovered right now that the TSM Client on Windows uses the UNC path for the local filesystems also.
My problem is the following: I have a bunch of new fileserver that I configured to use the NODENAME of the old ones, with the hope that the backups would be added to the old set.
Today, however, I see that each node have 2 filespaces, like this one:

FILES-06 \\files-06\e$ 1 WinNT NTFS Yes 2,043 GB 75.8
FILES-06 \\files-56\e$ 2 WinNT NTFS Yes 2,047 GB 75.7

Is there any client option I can use to point the client to the first filespace?

Thank you all,
A.
 

marclant

ADSM.ORG Moderator
#5
Hello everyone, I discovered right now that the TSM Client on Windows uses the UNC path for the local filesystems also.
That's like this by design. It's because if you use the same node on 2 machines, it knows that \\machine1\c$ is C: on machine1 and \\machine2\c$ is C: on machine2. This way, it won't mix up the backups of the two machines. So in your case, you backed up E: on files-06 and on files-56. The client knows by the filespace name that this is 2 different machines. So on the new machine, you get a new filespace even if you use the old nodename.

the servers are backing up all the file as they were new and its quite a lot of data (many TBs).
That's because they are new, they don't exist in that filespace.

You might have been OK if you had renamed the original filespace to match the new machine name, but that all depends how you moved the files from the old machine to the new machine. If the ACLs changed in the move process, they would get backed up again. The machine SID is normally part of the ACLs.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 16 18.8%
  • Keep using TSM for Spectrum Protect.

    Votes: 52 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.8%
  • Other (please comement)

    Votes: 7 8.2%

Forum statistics

Threads
31,451
Messages
133,985
Members
21,549
Latest member
idhelmyy
Top