• 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.


    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.

Microsoft DFS / Distributed Filesystem Bestpractices


first of all something to our system environment:
Our TSM server is running version 8.1. We use deduplication disk pools and traditionally migrate the data to tape pools at a certain point in time.
We currently have a file server cluster backed up by TSM. This cluster will be replaced by distributed file servers in the future. DFS should be used to replicate the data between two file servers. There is a requirement of the server team that both servers are backed up in order to save the data automatically in the event of a file server failure.
Now to my question. What is the best way to secure these two fileservers without having to duplicate the data? Is the only way to secure both file servers in parallel and to use the deduplication of TSM or is there a more efficient way with which I then generate less network traffic?

Thank you in advance for your support


ADSM.ORG Senior Member
From reading the above, I take it you are going to use DFSr and not DoubleTake or some-other replication tool in order to sync the two nodes. And that this isn't a high availability with shared storage cluster? (Sorry Unix guy, in a Windows world!)

I can only give examples for my environment in that we have a two node HA cluster with shared storage, and then a DFSr to a 3rd node. I hedge my bets and have the tsm client on the cluster node so it fails over when the main cluster does (patches/reboots/etc), and then I also have a client on the replicate node. Since deduplication is a wonderful thing, the replicate node sends very little data. The schedules between the replicant and the main are about 4 hours apart.
That said, while I use tape, my deduplication pool never migrates. Tape is only for copy and/or items that do not dedup well.

Not sure if that is the best way to go about it, but it has provided that extra level of security in the event that the main dfs cluster nodes are down and we are running off the replicant. At that point I don't have to worry about assigning a new schedule/install the client or other items as needed.

Extra tidbit, if you are going to be using Microsoft Deduplication to get more storage space, remember that TSM will ask the NTFS filesystem to re-hydrate that data. TSM doesn't talk to the MS Dedup data. It also seemed in my environment when the MS Dedup set something as deduplicated, it would force TSM to back it up again as the file attribute changes were enough to trigger a new version. And lastly, my site has had bad experience with MS dedup and had to open many support cases. In the end, we ended up turning off MS dedup (with extensive help of MS) as the risks were becoming too great (even with good backups!). Again, this is just my environments experiance/issues your's may be totally different.

I would be interested in hearing how others have addressed this issue of DFSr and their clusters.

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: 17 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 53 60.9%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.5%
  • Other (please comement)

    Votes: 7 8.0%

Forum statistics

Latest member