Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

backup and tape rotation 1

Status
Not open for further replies.

wfbtr

Technical User
Jun 16, 2004
288
US
hello-
i'm starting at a new company (very small one) and they've asked me this question:
What is your recommended backup schedule, tape rotation and method? Note: the complete XXX Network backup is approximately 30GB total.

any suggestions?
thanks.
 
With Exchange, in one company we had a debate whether to maintain backups of emails for longer than a year. Litigation lawyers would love to read emails from long ago to establish company policy or employee behavior.. the consensus was archived email was more of a liability.
 
technome

Totally agree with the consensus wihtin your company, unfortunately some areas are heavily regulated and failure to comply with regulations can result in you not being able to trade (financials markets for example).
 
MasterofNone ....
Luckily, most industries are not as regulated, at least not at the present.

Most companies do not have Email rules and regulations. In the coming years I think this will change dramatically, once companies become aware lawyers will bottom feed off of 7 year old emails.
 
It also depends the country, here we do not have any of those ridiculous laws (yet..)
 
hey dholbrook-
should i ghost the server while it's a domain controller, or while it's just a member server? i'm rebuilding one right now and haven't made it a D.C. yet.
thanks.
 
If you go to the work of making a Ghost copy of a server, it is for the purpose of being able to restore it quickly to service following a crash, so you want to do the Ghost of the server in service, not before you promote it to dc.

That said, having a ghost of the basic server prior to promotion is also an option, and not a bad idea, especially if this is not the first dc in the domain. For the run of the mill additional DC systems, the Ghost prior to promotion makes a lot of sense, will be a lot smaller (will not have any of the AD data, etc) and quicker to rebuild. All the other AD data on the server is automatically obtained once the server is promoted.

Just remember to go into AD and remove the old server from the Domain data base before you try to promote the old (rebuilt) server again. Otherwise you may have a name comflict with AD trying to have two servers with the same names but different SIDs. If you are restoring a crashed DC from the Ghost directly, then this is not an issue, as it will retain the SID of the old system, but rebuilding from a ghost prior to being a DC is a problem, unless you were able to demote the systems prior to rebuilding it (you usually are in the position of rebuild because it crashed, so this demotion step is usually not an option!).

Just some thoughts,

HTH
David
 
yes, makes perfect sense. thanks for the post.
i already went through and pruned AD with ADSIedit to make sure there's no old records. i guess i could easily just do a ghost image before and after. space certainly isn't an issue.
thanks again.
much appreciated.
 
I ghosted the server and will promote it to a d.c., and now I'd also like to ghost the current d.c.- but one of the requirements as ghost is doing that is it removes the client from the domain. I'm not sure how the d.c. would react to this. Anybody know?
thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top