| Johnny Oestergaard 2004-05-23, 12:15 pm |
| From all the years I have been in some kind of computer operations I
have never had to be able to restore any diskvolumes on file servers
to a "point-in-time" state.
Restore of volume after I lost a diskvolume I have done a lot of times
(especialy in the "old" days before raid systems)
I have done a lot of "point-in-time" restores, but that has always
been some kind of database systems or applicationbackups (and in this
kind of cases files are normaly never deleted, just updated)
/johnny
On Sat, 10 Apr 2004 02:53:20 +0300, "Tron" <puudub> wrote:
>"Johnny Oestergaard" <joe@joe.net> wrote in message
> news:n2ed70phrs4jbjjnfl5o7lomdo7ruc4tco@
4ax.com...
>
>Retrospect deletes all files those don't exist in snapshort session.
>
>
>
>
>Yes it can - Retrospect "match rule" compares windows files with
>name,size,creation date and
>modified date. If anything is different, then file don't match. Very good
>strategy, better than
>untrustable "archive attribute bit" or even worse "newer file".
>
>
>
>Why not? What kind you prefer? The only problem may be correct "system
>state"
>restoration, but Retrospect is good enough.
>
>
>
>
>I think term "server" haven't nothing to do with backups. Backup means
>backing up
>operating system or database. In any cases files to be in harmony is very
>important.
>If after restore partition contains unneeded files (created after last
>backup), then in most
>cases this isn't dangerous but simple litter your media. But
>enterprise-level backup isn't good
>only for servers, it's just good software and nothing more. Client-server
>and messaging-system additions can completely ignore example in home
>machine.
>
>Tron.
>
>
|