Commercial tools to replicate / synchronize share points / share drives to remote sites

sunhux
sunhux used Ask the Experts™
on
I have a 180GB share drive / sharepoint which users publish
(or update / write ) xps & pdf files to.

I thought of using MS 'robocopy' (2 separate jobs that will run
despite running into error conditions) to synchronize the share
drive but users prefer a commercial tool from Veritas/Netbackup.

What's the tool available to do this without mapping the remote
DR site's share at the local Prod site?  Preferably a low-cost tool
that can do almost realtime 'mirroring' or 'synchronization' so
that in the event the local Prod site is suddenly down, the remote
end would have a good copy of the share.

We're running Win 2008 Enterprise R2
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2017
Commented:
Any reason you are opting out of using dfs?
http://technet.microsoft.com/en-us/library/cc732863(v=ws.10).aspx

A separate backup should be used as well.

Author

Commented:
Thanks Arnold.

Looks like in DFS setup, the local end still need to map a drive
to the remote end's file share?  Am I right about this?

Btw, does DFS comes free of charge with Windows OS  (2008) ?
Distinguished Expert 2017
Commented:
Yes, dfs is included since 2003 but replication was enhanced since 2003 r2. presumably the remote server is also part of the ad, you would setup a replication group with the primary added first as the only target. You would then add the second one to which data should replicate. Test first with a test share and see how data replication works.
Note there is the replication topology as well as scheduling/bandwidth allocated for replication and staging storage amount.
How to Generate Services Revenue the Easiest Way

This Tuesday! Learn key insights about modern cyber protection services & gain practical strategies to skyrocket business:

- What it takes to build a cloud service portfolio
- How to determine which services will help your unique business grow
- Various use-cases and examples

Author

Commented:
Thanks Arnold.

Just one last clarification:
 in DFS setup, the local end still need to map a drive
to the remote end's file share?
Distinguished Expert 2017
Commented:
No mapping is involved. Within dfs you define the targets.
For replication deals with changes at either end will be pushed to the other target.
Once you define the share within dfs and then define the targets, the dfs will be accessible as \\domain\sharename or \\domain\root\sharename
The dc's will receive the request and will provide the client system with the responsible targets \\server\sharename.

Though please clarify the local end? Do you mean the local clients.
User will access the data as \\domain\sharename or \\domain\root\sharename depending on your setup.
You can define the dfs topology/configuration as a failover, I.e. it will always access the local target that you define as primary and in the event it fails, it will forward the clients to the other target without any user needed intervention/action.  The transition will be transparent to the users. You can then add/remove targets without having the user remap drives if any.

Author

Commented:
Yes, "local end" means "local clients".


Just found one article below,  is BestSync real or it's just a 'hype' as this is the first
time I've heard a tool that can do realtime synchronizing of MS SQL database:

   http://www.risefly.com/fseqna.htm
Questn:
Can BestSync synchronize the opened or locked files, such as data base file?
Ans:
Yes, BestSync supports "Volume Shadow Copy Service" of Windows XP/Windows 2003
/Windows 2008/Windows VISTA/Windows 7, even opened files or locked files such as
SQL data base file, OS registry file, Outlook PST files can be synchronized/backed up correctly. Other software may fail if the files are using. You need not worry this if
you are using BestSync.
Distinguished Expert 2017
Commented:
I've not used it so can not say one way or the other. but backing up the database, transaction log files that are in use are a bad idea. Always use SQL backup for database transaction log backups and backup the .bak files.

It make it up, but the state of the data within can be unpredictable such that when you try to resortore it, the SQL server might not start because the data within is inconsistent with the application

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial