G
Gerson Guimaraes
Hi all,
Ì'm a little bit worried about the rules that Ì defined to do a SYSTEM
backup of my network servers. One DLT tape
is not been enough to store a weekly backup, so I need to take off some
folders...
I tried to find some article to know more about this kind of stuff, but I
didn't concluded anything.
I have a AD domain with Windows 2000 servers :
S1: DC, DNS, WINS, DHCP, GC (C: mirrored)
S2: DC, DNS, WINS, DHCP, GC (C: mirrored)
S3: File & Print Server (HARDWARE RAID 5)
S4: EXCHANGE 2K, IIS (HARDWARE RAID 5)
S5: ANTIVIRUS, BACKUP EXEC, INTRANET (C: MIRRORED)
S6: ISA SERVER, DNS CACHE (C: MIRRORED)
S7: TEMPORARY SERVER (USED WITH UNIX) (NO REDUNDANCE)
The original backup rule was:
system state + all drive c:
The first modification I did was:system state + program files, but one tape
is not enough yet.
What I really need to recover a server if it crashes?
all help will be appreciate,
tips of sites and articles, too.
thank you very much.
Gerson
Ì'm a little bit worried about the rules that Ì defined to do a SYSTEM
backup of my network servers. One DLT tape
is not been enough to store a weekly backup, so I need to take off some
folders...
I tried to find some article to know more about this kind of stuff, but I
didn't concluded anything.
I have a AD domain with Windows 2000 servers :
S1: DC, DNS, WINS, DHCP, GC (C: mirrored)
S2: DC, DNS, WINS, DHCP, GC (C: mirrored)
S3: File & Print Server (HARDWARE RAID 5)
S4: EXCHANGE 2K, IIS (HARDWARE RAID 5)
S5: ANTIVIRUS, BACKUP EXEC, INTRANET (C: MIRRORED)
S6: ISA SERVER, DNS CACHE (C: MIRRORED)
S7: TEMPORARY SERVER (USED WITH UNIX) (NO REDUNDANCE)
The original backup rule was:
system state + all drive c:
The first modification I did was:system state + program files, but one tape
is not enough yet.
What I really need to recover a server if it crashes?
all help will be appreciate,
tips of sites and articles, too.
thank you very much.
Gerson