"shank" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
>I did change target to H: and also enabled Offline files. But I'm not
> understanding how this works. Is the data file saved to the server, then
> copied back to the client? Or saved on the client and copied to the server?
> The reason I ask is I work with MS Access a lot. If it's being saved on the
> server and copied back to the client and I lose connection with it open, I
> see it getting hosed. However, if saved to the client and copied to the
> server, I think it'd be OK.
>
> We have a backup service installed that backs up every 15 minutes on the
> server only. I see pros and cons about storing PST files on client or
> server. I think the best way is to save on the client and copy to the
> server. However, I don't see any great way to sync it every 1/2 hour so we
> get the best restore options. I tried downloading MS Outlook Backup. That's
> just a backup and cannot work with Outlook open. So now I'm using the WinXP
> backup scheduled at 12:01am everyday to backup the entire profile to the
> network. It's looking like profiles are around 15-25GB. Is there a better
> way?
>
> thanks
PST and MS Access files, and other database files do not work with Folder Redirection and Offline files. If the users are desktop (not laptop) users, you can either opt to keep the desktop users out of the redirect policy as Lanwench suggested, and use or share the file from a central location, or if individual databases, meaning a specific user is the only one using that specific database, then keep it local to the desktop.
Shank, I believe we talked about PSTs in another thread, didn't we? It sounds familiar. Storing a PST on the server, especially large ones, consumes quite a bit of bandwidth, and doesn't work with laptop users in and out of the office with a Redirect policy, as I mentioned. Keeping the PST on the laptop can lead to issues, such as lost emails if the drive were to go south, etc. If using Exchange, you can pump the PSTs into their mailboxes, but then if they are that large, it will consume a large portion of an Exchange database/store, and would probably require Ex2003 Enterprise due to the sizes alone, unless you were to use an archiving system that stores it outside of the Exchange database but are referenced through 'stubs' in their mailbox.
Exchange archiving may be something to look into for email if the users require to keep all of their email from day one of starting with the company. I used to work in a pharma, and there are minimal FDA requirements reflecting similar requirements. We used Zantas EAS, but it is pricey. There are others out there.
As for shared MS Access databases, you can leave them on the server, but for laptop users you may be better off with a VPN solution so they can access them when remote. I would suggest a hardware based VPN solution, such as a Cisco ASA5505, or whatever firewall/router/VPN device you already have in place, instead of a Windows solution. They are not that expensive, they are secure, and perform nicely.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.
"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay