Backup Exec 9.1 does Backup-To-Disk, you can map a share from your NAS to the BE server and create a backup-to-disk "device" folder and backup to that (basically you create a folder and in BE designate that as the B2D device), then run jobs later to copy that to tape. The backup-to-disk function creates bkf files (like ntbackup) of a size you can set (I've used 50 GB files when backing up a 200 gig server before). The biggest reason for doing something like this is to speed up backups of a large server, for instance that server I mentioned might take 12-15 hours to backup to tape, which would run into the nightly online maintenance window (not something you want to happen), but if you use the B2D device when doing the nightly exchange backups it can take a lot less time to complete. Since you're limited to a 16 gig store I don't really see a reason to do this. Why were you thinking of using ntbackup and copying it to the NAS?
On Tue, 5 Oct 2004 14:44:31 -0400, Jean-Paul Natola <[EMAIL PROTECTED]> wrote: > Oh sorry, > > Exchange 2003, and there is no M drive in 2003. > > Plus as far as I know I can only have a store of 16gb anyway (2003 > standard), each user gets a 250mb box. > > (on that note I *would think* i would never need more that 16 gig to backup) > > I was actually contemplating running the native windows backup ( of the > store ) then run a script to copy it over to our NAS device ( which does a > Full backup nightly). _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
