"GoBruins" wrote:

> hi all,
>
> i'm pretty new to networks, but i've been put in charge of backups for
> a smallish, but growing, 2003 server network (about 10 workstations).
> the first thing i need to do is come up with a good backup solution.
>
> i'm thinking of buying an external hard drive and using the built in
> backup program in 2003 server. is this adequate? or should i buy
> something like Acronis and make an image of the server hard drive?
>
> if there is a better/more robust backup solution, we'd be open to
> suggestions.
>
> thanks in advance.
>
>

> hi all,
>
> i'm pretty new to networks, but i've been put in charge of backups for
> a smallish, but growing, 2003 server network (about 10 workstations).
> the first thing i need to do is come up with a good backup solution.
>
> i'm thinking of buying an external hard drive and using the built in
> backup program in 2003 server. is this adequate? or should i buy
> something like Acronis and make an image of the server hard drive?
>
> if there is a better/more robust backup solution, we'd be open to
> suggestions.
>
> thanks in advance.

"GoBruins" <adventurefo***@gmail.com> wrote in message
news:1161019593.860888.198540@f16g2000cwb.googlegroups.com...
> hi all,
>
> i'm pretty new to networks, but i've been put in charge of backups for
> a smallish, but growing, 2003 server network (about 10 workstations).
> the first thing i need to do is come up with a good backup solution.
>
> i'm thinking of buying an external hard drive and using the built in
> backup program in 2003 server. is this adequate? or should i buy
> something like Acronis and make an image of the server hard drive?
>
> if there is a better/more robust backup solution, we'd be open to
> suggestions.
>
> thanks in advance.
>

> GoBruins, you have many choices for your backup plan, but here are a few
> givens:
>
>     1. Get something in place right away. A ten workstation, server based
> network with no backup at all is a disaster waiting to happen.
>     2. Be sure your plan ensures one fairly up to date backup is offsite at
> all times. I have some clients that rotate backups offsite daily, others
> weekly.
>    3. Make sure all key data is stored on servers, not on the workstations
> themselves, to keep the backup plan as simple as possible.
>     4. Whatever backup system you choose, be sure to periodically do a test
> restore.
>     5. If you choose a tape drive, get a high quality device. Do not go
> cheap (ie Travan).
>
>
> "GoBruins" <adventurefo***@gmail.com> wrote in message
> news:1161019593.860888.198540@f16g2000cwb.googlegroups.com...
> > hi all,
> >
> > i'm pretty new to networks, but i've been put in charge of backups for
> > a smallish, but growing, 2003 server network (about 10 workstations).
> > the first thing i need to do is come up with a good backup solution.
> >
> > i'm thinking of buying an external hard drive and using the built in
> > backup program in 2003 server. is this adequate? or should i buy
> > something like Acronis and make an image of the server hard drive?
> >
> > if there is a better/more robust backup solution, we'd be open to
> > suggestions.
> >
> > thanks in advance.

"GoBruins" <adventurefo***@gmail.com> wrote in message
news:1161039968.720365.47080@m73g2000cwd.googlegroups.com...
>
> dvw (removethis) wrote:
>> GoBruins, you have many choices for your backup plan, but here are a few
>> givens:
>>
>>     1. Get something in place right away. A ten workstation, server based
>> network with no backup at all is a disaster waiting to happen.
>>     2. Be sure your plan ensures one fairly up to date backup is offsite
>> at
>> all times. I have some clients that rotate backups offsite daily, others
>> weekly.
>>    3. Make sure all key data is stored on servers, not on the
>> workstations
>> themselves, to keep the backup plan as simple as possible.
>>     4. Whatever backup system you choose, be sure to periodically do a
>> test
>> restore.
>>     5. If you choose a tape drive, get a high quality device. Do not go
>> cheap (ie Travan).
>>
>>
>> "GoBruins" <adventurefo***@gmail.com> wrote in message
>> news:1161019593.860888.198540@f16g2000cwb.googlegroups.com...
>> > hi all,
>> >
>> > i'm pretty new to networks, but i've been put in charge of backups for
>> > a smallish, but growing, 2003 server network (about 10 workstations).
>> > the first thing i need to do is come up with a good backup solution.
>> >
>> > i'm thinking of buying an external hard drive and using the built in
>> > backup program in 2003 server. is this adequate? or should i buy
>> > something like Acronis and make an image of the server hard drive?
>> >
>> > if there is a better/more robust backup solution, we'd be open to
>> > suggestions.
>> >
>> > thanks in advance.
>
> yes, all great suggestions. i was planning on using an external hard
> drive because they're so fast, and so cheap nowadays. we could buy a
> couple and rotate them, taking one off-site.
>
> here's another possible hurdle i face. the server computer is fairly
> dated. if it does crash, it's going to be hard to find replacement
> parts for it. i'm tempted to take preemtive action and upgrade the
> server, but i'm kinda green, so i'm a bit leery about diving in.
>
> for example, i know that if the new motherboard chipset / graphics card
> don't match, i can't just do a simple restore. how do other sys admins
> handle this dilemma?
>

> If I was in your situation, based on all you've reported (ie size of
> network, age of server, etc.), I'd purchase Acronis True Image Server,
> including the Universal Restore option, and image that server asap. Others
> might suggest other (ie less expensive) imaging products- I just don't have
> experience with them.
>
> "GoBruins" <adventurefo***@gmail.com> wrote in message
> news:1161039968.720365.47080@m73g2000cwd.googlegroups.com...
> >
> > dvw (removethis) wrote:
> >> GoBruins, you have many choices for your backup plan, but here are a few
> >> givens:
> >>
> >>     1. Get something in place right away. A ten workstation, server based
> >> network with no backup at all is a disaster waiting to happen.
> >>     2. Be sure your plan ensures one fairly up to date backup is offsite
> >> at
> >> all times. I have some clients that rotate backups offsite daily, others
> >> weekly.
> >>    3. Make sure all key data is stored on servers, not on the
> >> workstations
> >> themselves, to keep the backup plan as simple as possible.
> >>     4. Whatever backup system you choose, be sure to periodically do a
> >> test
> >> restore.
> >>     5. If you choose a tape drive, get a high quality device. Do not go
> >> cheap (ie Travan).
> >>
> >>
> >> "GoBruins" <adventurefo***@gmail.com> wrote in message
> >> news:1161019593.860888.198540@f16g2000cwb.googlegroups.com...
> >> > hi all,
> >> >
> >> > i'm pretty new to networks, but i've been put in charge of backups for
> >> > a smallish, but growing, 2003 server network (about 10 workstations).
> >> > the first thing i need to do is come up with a good backup solution.
> >> >
> >> > i'm thinking of buying an external hard drive and using the built in
> >> > backup program in 2003 server. is this adequate? or should i buy
> >> > something like Acronis and make an image of the server hard drive?
> >> >
> >> > if there is a better/more robust backup solution, we'd be open to
> >> > suggestions.
> >> >
> >> > thanks in advance.
> >
> > yes, all great suggestions. i was planning on using an external hard
> > drive because they're so fast, and so cheap nowadays. we could buy a
> > couple and rotate them, taking one off-site.
> >
> > here's another possible hurdle i face. the server computer is fairly
> > dated. if it does crash, it's going to be hard to find replacement
> > parts for it. i'm tempted to take preemtive action and upgrade the
> > server, but i'm kinda green, so i'm a bit leery about diving in.
> >
> > for example, i know that if the new motherboard chipset / graphics card
> > don't match, i can't just do a simple restore. how do other sys admins
> > handle this dilemma?
> >

> dvw (removethis) wrote:
> > If I was in your situation, based on all you've reported (ie size of
> > network, age of server, etc.), I'd purchase Acronis True Image Server,
> > including the Universal Restore option, and image that server asap. Others
> > might suggest other (ie less expensive) imaging products- I just don't have
> > experience with them.
> >
> > "GoBruins" <adventurefo***@gmail.com> wrote in message
> > news:1161039968.720365.47080@m73g2000cwd.googlegroups.com...
> > >
> > > dvw (removethis) wrote:
> > >> GoBruins, you have many choices for your backup plan, but here are a few
> > >> givens:
> > >>
> > >>     1. Get something in place right away. A ten workstation, server based
> > >> network with no backup at all is a disaster waiting to happen.
> > >>     2. Be sure your plan ensures one fairly up to date backup is offsite
> > >> at
> > >> all times. I have some clients that rotate backups offsite daily, others
> > >> weekly.
> > >>    3. Make sure all key data is stored on servers, not on the
> > >> workstations
> > >> themselves, to keep the backup plan as simple as possible.
> > >>     4. Whatever backup system you choose, be sure to periodically do a
> > >> test
> > >> restore.
> > >>     5. If you choose a tape drive, get a high quality device. Do not go
> > >> cheap (ie Travan).
> > >>
> > >>
> > >> "GoBruins" <adventurefo***@gmail.com> wrote in message
> > >> news:1161019593.860888.198540@f16g2000cwb.googlegroups.com...
> > >> > hi all,
> > >> >
> > >> > i'm pretty new to networks, but i've been put in charge of backups for
> > >> > a smallish, but growing, 2003 server network (about 10 workstations).
> > >> > the first thing i need to do is come up with a good backup solution.
> > >> >
> > >> > i'm thinking of buying an external hard drive and using the built in
> > >> > backup program in 2003 server. is this adequate? or should i buy
> > >> > something like Acronis and make an image of the server hard drive?
> > >> >
> > >> > if there is a better/more robust backup solution, we'd be open to
> > >> > suggestions.
> > >> >
> > >> > thanks in advance.
> > >
> > > yes, all great suggestions. i was planning on using an external hard
> > > drive because they're so fast, and so cheap nowadays. we could buy a
> > > couple and rotate them, taking one off-site.
> > >
> > > here's another possible hurdle i face. the server computer is fairly
> > > dated. if it does crash, it's going to be hard to find replacement
> > > parts for it. i'm tempted to take preemtive action and upgrade the
> > > server, but i'm kinda green, so i'm a bit leery about diving in.
> > >
> > > for example, i know that if the new motherboard chipset / graphics card
> > > don't match, i can't just do a simple restore. how do other sys admins
> > > handle this dilemma?