Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Backup solution

Updated: 26 May 2010 | 3 comments
Gdude's picture
0 0 Votes
Login to vote

Greetings,

I am brand new to DS 6.9 and am preparing to install.  We currently have 5 servers (Windows Server 2003 x64 Enterprise SP2) serving various purposes and 2 SANs.  Each server has approx 70GB hardrives (12GB and C: and 58GB on D:)   I have created 5 seperate 100GB volumes on our SANs.  Our HD's came out of the factory partitioned 12:58 and needless to say our C: drives are running out of room.  I have an application that can (in theory) resize our partitions without destroying the data or config but I obviously want to make complete backups before I try using it.  A couple of questions:

1.  Is DS 6.9 the appropriate tool for creating complete, recoverable backups that I can put on to my SANs while I try this resizing app?

2. Do I use DS as a manager (similar to SEPM) with which to implement jobs on my other servers?

Thanks in advance and please let me know if I need to clarify anything.

Comments

bhawver's picture
20
Nov
2009
0 Votes 0
Login to vote

DS

DS is definitely an option.  How are you utilizing it now?  If you are solely using it for clients (desktops and laptops), you won't be licensed properly to use it how you suggest you are looking to use it.

If you are licensed for DS for Servers, then the first thing I would try would be to pull a full backup of a server and then attempt to restore it to another box.  I would then attempt the repartitioning software on the test server to ensure that 1. it will work and 2. you're back out plan will work 100%.  I agree there is nothing worse than a feeling of regret when you realize you just blew away a production server with no back out plan!

I would suggest, however, in the future that on new drives that come from the factory you rebuild these drives yourself.  I personally never utilize the factory image.  I feel it's always better safe than sorry when it comes to knowing how your machines were built.

So, to recap your questions:

1.  Yes, it can do what you are looking for.  I would say you really don't need to carve out 5 separate 100GB LUNs on  your SAN.  One big one will do the trick as the backups are actually stored as image files.

2.  DS basically acts as a management console.  You create your jobs and can push these jobs to your clients/servers.  The jobs can be anything from backup imaging to reconfiguring the computer name to powering off to copying files...etc.  It is a very useful tool, especially when you manage hundreds of client computers.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Gdude's picture
23
Nov
2009
0 Votes 0
Login to vote

Thanks for the response. We

Thanks for the response.

We are not utilizing DS in any capacity at the moment.  It was purchased by our project manager almost a six months ago and has been sitting on a shelf.  They sent us to a 2 day training course which was ineffective at best and really didn't get into the nuts-and-bolts of usage.

We are backing up data but are not doing full server backups.  Trying like heck to get this going as I know we are living on borrowed time.

Sounds like I have the right tool in my hands...just gotta figure out how to use it.  My biggest issue right now is connectivity between the mgr and the other servers.  I attempt to add a client/server but cannot establish connectivity.

I am running SEPM off the same machine and it talks to my other clients/servers perfectly.

bhawver's picture
23
Nov
2009
0 Votes 0
Login to vote

Manager

When you say "connectivity between the mgr and the other servers", are you talking about the DS server and the other client servers?

If so, you will want to ensure that there aren't any firewalls blocking ports.  The most common port used by the AClient/DAgent is 402.

You will also want to set up a PXE server rather than install the automation partition.  This way you when you make changes to the Automation OS, you don't have to re-push it, it resides right on the PXE box.

Hope this gets you started.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.