> But anyway, using VSS does not assure a stable database state. You > would at least need to 'sync' (or stop) the database to ensure such a > state. Now in practice, the database may be robust and you may just > lose the last entry but taking a VSS is not a recommended method.
Microsoft recommends VSS, but then again, they also disagree with your presumption that a manual 'sync' or stop is necessary. Not that it would hurt anything, but even without it, you get a point-in-time snapshot from the time that the shadow volume was created. If you care to get your technical information from Microsoft rather than conjecture, there's considerable detail available here: http://technet.microsoft.com/en-us/library/cc966520.aspx Note that capabilities vary by VSS writer, as well as Windows and SQL Server version, but pretty much all are capable of backing up a database that's capable of being recovered. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/