Featured post
sql server - Maintenance window and recovery for a large database -
one of our teams developing database large (~500gb) , grow there (i know 500 gigs may seem small many of you, 1 of larger databases in our shop). 1 of issues grappling backing , restoring database. basically, database have several "data" tables , 1 table used storing images / documents. need accomplish following:
- be able backup , restore data tables (sans images) our test server debugging , testing purposes.
- in event of catastrophic database failure, restore data tables of application , running asap. then, restore images table when possible.
- backup database within allotted nightly time window (a few hours).
my questions are:
- is possible accomplish first 2 goals while still having images stored in same database? if so, use filegroups, filestream, or else?
- how other shops backup databases in reasonable time window while maintaining high availability? replicate second server , backup there?
we have dealt similar issues. $2.5b solar manufacturing company , disaster recovery critical us, keeping our databases backed up. our main database our plant floor production database. decided strip database absolutely essential data needed maintain production, , move other data off own database. has allowed high availability , reasonable backup/restore times.
in case, necessary store images in same database other data? suspect it's not, , case of making issues easier deal with. think separate file groups problem. might want reconsider whether needs in single db.
- Get link
- X
- Other Apps
Comments
Post a Comment