Retention space requirements and robustness?

Backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)

Retention space requirements and robustness?

Veeam Logoby SoHoUser » Fri Mar 18, 2016 4:46 am

I have two questions about how Endpoint Backup Free injects obsolete VIB snapshots into the base VBK image as part of the retention process.

1: Do I need to provision enough free disk space in the backup target drive to for the VBK to be duplicated entirely? I.E. if I have a backup with an 800GB VBK, do I need 800GB + of free space for retention to work properly?

2: Leaving out the possibility of filesystem corruption, how robust is the VIB to VBK integration process in the face of power failures or other forced interruptions? I.E. if the power goes off when EBF is injecting an obsolete VIB into the VBK, is the backup likely to survive intact?

Thanks.
SoHoUser
Lurker
 
Posts: 1
Liked: never
Joined: Fri Mar 18, 2016 3:47 am

Re: Retention space requirements and robustness?

Veeam Logoby Gostev » Sat Mar 19, 2016 1:53 am

1. I don't fully understand the question. But you need enough disk space for full backup (VBK) and incrementals (VIB) based on retention policy. You don't need disk space for two VBKs, if that is the question.

2. Sure thing. The engine is over 6 years old and is taken directly from our enterprise backup product used by nearly 200'000 companies. Both products are sharing the exact same code, to be precise.

Thanks!
Gostev
Veeam Software
 
Posts: 21390
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Return to Veeam Agent for Windows



Who is online

Users browsing this forum: Google [Bot] and 10 guests