Re: Volume Shadow Copy on 2003 Server w/ SQL 2k SP3

From: Dolan, David (Dolan_at_CTCGSC.ORG)
Date: 12/03/03

  • Next message: Jeff Moss: "Black Hat Briefings Amsterdam Call for Papers"
    Date:         Wed, 3 Dec 2003 09:40:55 -0500
    To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
    
    

    Backing up the mailstores with NT backup requires using the SQL agent.
    Just backing up the data raw is going to leave you with a bunch of
    useless data files. The good news is that the SQL agents that come with

    NT backup work most of the time, even when third party sql agents dont
    (arcserve anyone?) You shouldn't be restoring database files to a UNC
    path anyway, since the table space and the indexes aren't taken into
    consideration. This applies to all versions of Exchange. Shadow
    Copy, AFIK is for data files not databases.

    --dave

    -----
    Want to reply to the person who sent this message?

    This list is configured such that just hitting reply is going to result in the message coming to the list, not to the individual who sent the message. This was done to help reduce the number of Out of Office messages posters received. So if you want to send a reply just to the poster, you''ll have to copy their email address out of the message and place it in your TO: field.
    -----


  • Next message: Jeff Moss: "Black Hat Briefings Amsterdam Call for Papers"

    Relevant Pages

    • Re: Can Humax PVR9200T store normal data files?
      ... so it wouldn't be suitable for backing up ... data files, so I've decided to sack the idea. ... This seems a sensible way to backup ...
      (uk.tech.digital-tv)
    • backups
      ... I recently bought an external hard drive to use for backing up my data files. ... I have no problem copying my E: directories to the external drive, but whenever I try to use Vista's 'backup' program I get major problems. ...
      (microsoft.public.windows.vista.general)
    • Re: Growing Database problem,
      ... > Veritas 9 with SQL agents are there for backup. ... > it be more worth performing a schedule to backup into *.bak file at say, ...
      (microsoft.public.sqlserver.server)