Skip to main content

What strategy would you use for ABR10? pls

Thread needs solution

as backup size has grown my previous usage plan isn't working well.

A full backup now takes 470GB. Daily change is (roughly) 4GB, on average.

We have been using 3*1TB USB for 'offsite'. The 3 USB drives have been connected to a QNAP NAS which, until recently, was configured for RAID6 to give 1TB usable. The Vault is automatically copied to USB daily and the USB was swapped weekly. I recently reconfigured the QNAP for RAID5 (1.5TB usable) so that files created during consolidation were accomodated but the final result was still <1TB.

OK. If I have to I can replace the drives in the QNAP for greater capacity and the USBs (but I'd prefer to stick with max 2TB on the USB, so similar for the QNAP).

The whole kit is for one server (SBS03, hopefully soon to be replaced, but I ain't holding my breath) running as a virtual machine under Server03x64. We have sufficient space in the host that I also have a VHD I have been using as ASZ for an additional 'monthly' task. I've been unable to persuade the CEO to replace the system because 'Mick, it does everything we need' and even DIRE WARNING about 'MS are soon going to consider it 'dead product'' falls on deaf ears.

How may I best use what is 'on hand', or justify at least the increased capacity for the QNAP/offsite?

TIA

0 Users found this helpful

Can you split the backup task into two so that consolidation can produce smaller temporary results one after another? Not that it is a 'strategy' but rather another quick hack to avoid upgrade.

I have separate OS, Exchange (and some other items), and DATA (the bulk of it) partitions, so, yes, 'splitting' the tasks may be a viable answer.

I'd like to keep OS+Exchange (includes AD) together. DATA could also probably be divided into 'file based' (rather than partition based) and split into CVS (a large repository) vs REST.