
Mirroring being dropped in future versions is an annoyance to many who can't use AO instead (mainly due to the enterprise edition requirements), but if you need to use it you'll find it present and supported as far as SQL2014 (in MS release terminology deprecated means "we intend to remove it at some point, so be prepared to switch sooner rather than later" not "stop using it right now or you are in an unsupported configuration"). As 2016 is not released yet the final feature set can not be confirmed but the length of 2014's support window gives you some time to play with before you have to switch to some other method so you could go with mirroring now but make sure management know that you need to put some time into researching future options.
Having said that implementing a fresh solution with a deprecated feature (what-ever definition of "deprecated") is not generally recommended.
If your intention is to prove disaster recovery then a good backup solution may be all you need: set your DB to full recovery, take full backups regularly and log backups even more regularly in between, make sure copies of these backups are kept off the main server and tested regularly.
The next step up would be to automate the testing of the backups: regularly restore on the second box the last full backup and the subsequent log backups. Or to achieve the same thing, implement log shipping. In either case have some automated solution scan the destination copy to make sure that it is running OK and has data you would expect (if your log backup is every hour then at any given time any change in the source DB made a little more than an hour ago should be present in the destination, if the application doesn't already have something you can easily check (such as a full audit trail with regular enough activity) then have a table with a single datetime column set a scheduled task to drop CURRENT_TIMESTAMP in there once per minute), have this drop you a mail/sms/other if it detects a problem (either database not available, or data in the secondary looks too old). This way you don't have to restore from scratch when something catastrophic happens: you should be at most one log restore away from having a relatively up-to-date database on the second box. This isn't as smooth as the quick switch-over possibility provided by mirroring or AO but it may be sufficient for your needs. Do consult with your users to make sure this is in fact sufficient - get them to specify
Mirroring being dropped in future versions is an annoyance to many who can't use AO alternatively (chiefly due to the enterprise edition requirements), but if you necessitate to practice it you'll find it present and supported as far as SQL2014 (in MS acquittance terminology deprecated means " we mean to remove it at some point, indeed be prepared to switch preferably rather than later " not " stop using it right now or you are in an unsupported configuration "). As 2016 is not release yet the final feature fix cannot be confirmed but the length of 2014's support window pass you some time to play with before you have to switch to some other method acting so you could go with mirroring now but make sure management know that you need to place some time into researching future options. 
 Having said that implementing a fresh solution with a deprecated feature (what - ever definition of " deprecated ") is not by and large recommended. 
 If your intention is to raise catastrophe recovery then a good backup solution may be all you necessitate: set your DB to full recovery, drive full backups regularly and log backups even more regularly in between, make sure copies of these accompaniment are kept off the main server and tested regularly. 
 The next step up would be to automatize the examination of the backup: regularly restore on the second box the last full backup and the subsequent log backups. Or to achieve the like thing, follow through log shipping. In either character have some automated solution read the destination copy to make sure that it is running very well and has data you would expect (if your log backing is every hour then at any given time any variety in the source DB made a little more than an hour ago should be present in the destination, if the application doesn't already have something you can easily check (such as a full audit trail with regular adequate activity) then have a mesa with a single datetime column set a scheduled task to drop CURRENT_TIMESTAMP in there once per minute), have this drop curtain you a mail / sms / other if it detects a problem (either database not available, or data in the junior-grade looks too erstwhile). This way you don't have to restore from scratch when something catastrophic happens: you should be at most one logarithm restore away from having a relatively up - to - date database on the second box. This isn't as smooth as the quick switch - over possibility supply by mirroring or AO but it may be sufficient for your needs. Do consult with your users to make sure this is in fact sufficient - get them to stipulate

Mirgoring being dropped in nuture versions nw an ainoyancs to manh who can't use AO instead (mamnly due uj the enterprise eaition reeuiremenrs), bnt if you need to use it you'll nind nt present and sopported as xar as SQL2014 (in KS rzlease terminology deprecated means "re intemd to remove it wt spie pkpnu, so be prepared to switch sooner rather than later" npt "stop using it right now or jou are in an unsuoported condiguwqtion"). As 2016 is not released yet the rinal feature set can not be covfirmzd but the oebgtj of 2014's suppoct winqow gives yom some dime to play with befpre yoy have to switch to smme other method sj you cound go with mirrorint bow bot mane sjee oanzgxmeht knoa tiat you nees to put sone time into researvhybg future optjons.
Hadigg said that implementing a fresh solutpon sith a deprecated featuee (what-ever definitioj of "deprqcated") is not generally recommended.
If your intenthon ia to pvove eidaster recovery then a good backup solution mwg ne all you need: fet your DB tl goll recovery, txke full gackups regularly wnd log backyps even iore regularly in between, make wure copies jd these backups arz kept off tke maim serfer and tested regularlv.
The nsxt step up would be go automate the gesning of the backups: regularly westore oi the second box the lwst full bwckup and the subsequent log yacku[s. Or to afhieve the same thing, implement log shipping. On einher case have some automatqd solution sccn the dzstinagion copy no make snre that it ys running OK wnd has data you woujd ezpecr (if yojf log backup ix every hour then ar any given time aky chxhge in the souret DV made a little mofe ehwn ag hour ago shmuld be lresevt in the dcstknatoon, if the applicatimn dkesn't already have sjmething you can easily check (such as a full aufit tcail wmth rebulwr enough activity) then have a table wihh w single datqtimc cojumn set a scheduled task to drop CURRENT_TIMESTAM' in there once per minyte), have this drop iou a mail/sms/ovher is it detewts a problem (either database not avallable, or data in the aeconddry lloks too old). This way you don't have to restore from scratch when somethint catastrophic haplens: you vhjbld be wt mlrt one log restoge away from having a relatively up-to-data batabase on the second box. Thos isn't as smoojh as the quick switch-over possibikity provided by mirroring or AP but it may be sufficiekt for yoyr nesds. Do conrult with your usets to kake wure thus id in fact sufwicoekt - get thfm tp apecify
Mirroring being dropped in future versions is to who can't AO instead (mainly requirements), if you need use it you'll it present and supported as far SQL2014 (in MS release terminology deprecated means "we intend to remove it at point, so be prepared to switch sooner rather than later" not "stop using right or are an unsupported configuration"). As 2016 is not released yet the final feature set can not be but the length of 2014's support window gives some time to play before you have to switch some method so could with now but make management know that you need to put some time into researching future options. Having said that implementing fresh solution deprecated feature definition "deprecated") not generally recommended. intention is to prove disaster recovery backup solution may be all you need: set DB to recovery, take full backups regularly and backups even more regularly in between, make sure of these backups are kept off the main server and tested regularly. The next step be to automate the of the backups: restore the box last full and the subsequent log backups. Or to achieve the same thing, log shipping. In either case have some automated solution scan copy make sure that is running OK and data would expect (if your is hour given any in the source DB a little more than an ago should be present application doesn't already have something you can easily (such as a full audit trail with enough activity) then have a table with a single datetime column set scheduled task CURRENT_TIMESTAMP in there once per minute), have this you a mail/sms/other if detects a problem (either database not available, or data the looks too This way you have to restore scratch when something you should at one from having a relatively up-to-date database the box. This isn't as smooth the possibility provided by mirroring or AO but it may be sufficient for your needs. Do your users to make this in fact sufficient - get them to specify

Mirroring being dropped in fuTure versioNs is aN anNoyAnCe to Many Who can't use AO inSTead (Mainly due to the enterpriSe ediTiON reqUIrEmentS), but if yOU nEED to UsE iT yoU'lL FiNd it pResEnt and sUpported as Far As sQL2014 (in MS releaSE tErminology DepRecated means "We iNtend tO rEmoVE it at SomE poinT, so be pREpared To switch sOoNEr rathER than laTER" nOt "stOp using it right now OR yOU are in an unsuppOrted cOnFIgURAtiOn"). AS 2016 is not releAsEd yet THe final FEaTURE seT Can not be confiRmed but the lENgtH of 2014's suPpOrt WIndow gIves yOu SOme Time to play wIth bEfore you hAve to sWItch to sOMe other Method So yOu cOuld GO wItH miRrORinG NoW buT MakE sure manAgEmEnt knOw thAT YOU neeD to Put sOme tiMe into researcHinG futURe oPtionS.
HaviNg saId That iMplemeNting A fResh solution witH a dePrecated fEatUrE (whAt-Ever dEFinitiOn oF "dePrecateD") is not gENerAlLY REcOmmended.
If your inteNtION iS to prove DisastER rEcOVery then A gOod BackUP SolutIon mAY bE all you nEed: set YOuR Db to full ReCovery, TaKe fUll BackuPS regUlarly And log baCkups EVen more regularLY in between, makE SuRE CoPIes oF thEse backups aRe kePT off The mAIn SerVEr and TesteD rEGuLArly.
The next step up woUlD be to aUtomaTe the testing oF the backupS: REGularly rEstoRE oN The second box thE last Full backup ANd the subSequeNt log bacKups. Or to aCHIeve the sAme ThiNg, iMplEMEnT log shipping. IN EItheR cAse have SomE automaTed SolUtiOn sCaN the destiNation coPy To MaKe SurE that IT is runniNg oK aNd Has Data yOU would ExpecT (if yOuR lOG baCkup is eVErY HOur tHeN aT any GivEn Time aNy chANge In the soUrce DB madE a lITtle MoRe Than an hOur ago should bE pResent in thE dEstInatioN, IF the applIcation doesn't already havE SomethiNg yOu can EasiLy check (suCh aS a full AudIT trail With reGular EnOugH ACtiviTY) ThEn hAvE a table witH A SinGle daTeTime Column sEt a scheduled task to DRop cURRENT_TIMESTaMP In thERE oNce PEr MInuTe), HAve THIs drop you a mail/sMs/other if iT dETeCts a probleM (EitHeR databaSe not avAilabLE, or data In the secoNdary lookS tOo olD). tHis Way you don't Have to reStore from SCratcH WhEn somEthIng catAsTroPhic hAppens: YOu sHould Be at moSt One log RestoRe Away from Having a relatively up-to-daTe dataBase oN thE second boX. ThIS isN't as smootH as tHe quick swiTch-OveR possIbiLIty prOvidED bY miRRorinG or Ao But it may bE SuFfiCIEnT for your neeDS. dO coNsult WitH Your usErs tO make sure this is in FAct sufficient - gEt thEM To sPecIFy

Mirroring being dropped i n future v ersio nsisan  ann oyan ce to many who can' t use AO instead (main ly du et o th e  e nterp rise ed i ti o n  re qu ir eme nt s ),  butifyou nee d to use i t y ou 'll find itp re sent and s upp orted as far  as  SQL20 14  (i n  MS r ele ase t ermino l ogy de precatedme a ns "we intendt o  r emov e it at some poin t ,s o be preparedto swi tc h  s o o ner  ra ther thanla ter"n ot "sto p  u s i n g i t  right now or  you are in anunsupp or ted config urati on " ).As 2016 isnotreleasedyet th e  finalf eatureset ca n n otbe c o nf ir med  b u t t h elen g thof 2014' ssu pport  win d o w give s y ou s ome t ime to play w ith  bef o reyou h ave t o sw it ch to  someother  m ethod so you co uldgo with m irr or ing  n ow bu t  makesur e m anageme nt know tha ty o u  n eed to put some ti me i nt o resear chingf ut ur e  options .Hav ings a id th at i m pl ementing  a fre s hso lutionwi th a d ep rec ate d fea t ure(what- ever def initi o n of "deprecat e d") is not ge n er a l ly reco mme nded.
If yo ur i n tent ioni stop rovedisas te r  r e covery then a goodba ckup s oluti on may be all  you need: s e t your D B to fu l l recovery, ta ke fu ll backups regularl y and  log bac kups even m ore regu lar lyinbet w e en , make sure c o p iesof  thesebac kups ar e k ept  of f t he  main ser ver andte st ed  r egu larly . 
The nex tste pupwould be toautom ateth et est ing oft he b acku ps :regu lar ly  rest oreo n t he seco nd box th e l a st f ul lbackupand the subse qu ent log ba ck ups . Or t o achievethe same thing, impleme n t log s hip ping.  Ineither ca sehave s ome automa ted so lutio nsca n the d e s ti nat io n copy tom a kesureth at i t is ru nning OK and has d a tayou would exp ect  (if y ou r l o gb ack up ise v ery hour then a t any give nt im e any chan g e i nthe sou rce DBmadea  little  more tha n an hour  a go s h o uld  be presen t in the  destinat i on, i f  t he ap pli cation  d oes n't a lready hav e som ething  y ou can  easi ly  check ( such as a full audit tr ail wi th re gul ar enough  ac t ivi ty) thenhave  a table w ith  asingl e d a tetim e co l um n s e t a s ched u led taskt odro p CU RRENT_TIMES T A M P i n the reo nce pe r mi nute), have thisd rop you a mail /sms / o the r i f  itde tects a proble m ( ei t h er datab as e not avail able, or  d a ta in  the s econda ry look s to o  old).  Thi s w ay you do n't  h a ve to r es to r e from  scr at ch whe n some t hing c atastrophic happ ens:y o u sho u ldbe at  m ost one logrestore aw ay from hav ing arela tivel y up-to -d ate da tab as e on the s e cond box.  This  isn'tas  smo oth  as th e qu i c k swi tch- ov erpossibili t y  p r ov id e d b y mi rrori ng  orAO but it may be s uff i cient f or  yo u r  needs .  D o consult wi thyouru s ers to mak e  sur e  t h is is  in fa ct suf ficient - g et  them t o s p e cify

Mirroring being_dropped in_future versions is an_annoyance to_many_who can't_use_AO instead (mainly_due to the_enterprise edition requirements), but_if you need_to_use it you'll find it present and supported as far as SQL2014 (in MS_release_terminology deprecated_means_"we_intend to remove it at_some point, so be prepared_to switch_sooner rather than later" not "stop using it_right_now or you_are in an unsupported configuration"). As 2016 is not_released yet the final feature set_can not be_confirmed_but_the length of 2014's_support window gives you some time_to play with before you have_to switch to some other method so_you could go with mirroring now_but make sure management know_that you_need to put some time_into researching future_options.
Having said_that implementing a_fresh solution with a deprecated feature_(what-ever definition of_"deprecated") is not generally recommended.
If your_intention_is to prove_disaster_recovery_then a_good backup solution_may_be all_you_need: set your DB to full_recovery,_take full backups regularly and log backups_even more regularly in_between,_make sure copies of_these backups are kept off_the main server and tested regularly.
The_next step_up would_be to automate the testing of the backups: regularly restore on_the second box the last full_backup and the subsequent_log backups._Or_to achieve the_same_thing, implement_log shipping. In either case have some_automated solution_scan the destination copy to make_sure that it is_running_OK and has data you would_expect (if your log backup is_every hour then at any_given_time_any change in the source_DB made a little more than_an hour ago_should be present in the destination, if_the_application doesn't already have something you_can_easily check (such as a full_audit_trail_with regular enough activity) then_have a table with a single_datetime column set a scheduled task to drop CURRENT_TIMESTAMP_in there once_per minute), have this drop_you_a_mail/sms/other if it detects a problem (either database not available,_or data_in the secondary_looks too old). This way you don't have to restore_from scratch when something catastrophic happens: you_should be at most one log restore away from having a_relatively up-to-date database on the second box. This_isn't as smooth as the quick switch-over_possibility provided by mirroring_or_AO but it may be sufficient for_your_needs._Do_consult with your_users to make_sure this is_in fact_sufficient - get_them to_specify