Sorry about the partial pun but we're feeling a little backed into a corner with a SBS 2007 install we have implemented as a favor for a closely aligned local business.
They use just file shares now and we'll be lighting up Exchange functionality soon (they're currently still POP3 to Unix). The original plan was to use our DPM 2007 server for backup duties but missed that small line demanding protected machines be in the same domain as DPM or in a separate domain with a trust to the DPM's domain. SBS doesn't do trusts so we gritted teeth and started down the Backup Exec path. Unfortunately it suffers the same limitation. WTF, is it that hard to auth as a local user? net use x: \\sbs\share /u: sbsdom\user clearly works... On top of it, wbadmin, the ntbackup replacement, seems a bit short on functionality (particularly in non-R2) and seems useful primarily in the DR scenario instead of the much more common accidental deletion etc... We're using it via task sched. to a NAS box. I realize we could mount the backup as a VM and copy the file off but ugh! So, what's the best way to do file level and mailbox level backups in this constrained scenario? Right now we're considering a separate NAS box and some kind of scripting (MBS blog has the exchange Posh scripting answer I suspect). I'm hoping for a non-scripting answer since many co-workers are not so scripting friendly and love their pointy-clicky things. ~JasonG --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
