VEAAM

[synaesthesia]

Anyone know if it's possible to restore a backup created in VEAAM 5.0 using VEAAM 7.0 ? (Same product, newer version).

 

Got 5.0 running on a 2003 server currently, looks like as there's no upgrade path we'll need to install fresh. I'd like to make sure beforehand that we can still restore backups from the older version in the new one?

[Tall_Paul]

I've never tried it, but I've heard it can be problematic.

 

Have you tried the VEEAM forums? They're a very friendly bunch.

[kmount]

Yes, it is possible.

 

Can backup files from v7 be imported to v6.5? | view topic

 

(confirms a backup from older version will be fine in v7, but not the other way)

[Cache]

Sounds daft, however if your concerned why not leave your current V5 install as is, setup/configure/use V7 and then either shutdown and keep the V5 server for emergancies in case you need to restore a backup or atleast until you have chance to test the backups with V7?

 

Veeam licencing is quite flexible allowing you to install mutliple copies as long as you don't exceed the Socket count your licenced for (and what I've done recently when moving the Server across from 2008 to 2012 so I could backup/restore Dedup volumes in 2012).

Edited October 7, 2014 by Cache

[jtoland]

As veam technical zips up the files why dont you unzip then and just reload them onto the vm server and then use veam 7 to back them up again

[penfold]

@Cache - this is the situation I am in at the moment. We have Veeam on a Server 2008 box but it needs to be updated (which can't be done at the moment due to other software also being on it). I have played around with exporting the database and Veeam config and importing it into a new Server 2012 box which works but on the new server then has details of the old server. The existing setup has the SQL database and Veeam on the same server but I want to separate this out and have a clean install of Veeam and a separate SQL Server. While I do this I want to keep the old one running until all the jobs have been re-created on the new server. Presumably this just means we will need to use 2 instances of Veeam to backup specific VM's until all the jobs have been re-created on the new server?

 

Are there any issues with running 2 separate Veeam Servers (other than making sure the jobs don't overlap) that I need to be aware of before I start configuring the new server?

[jtoland]

I personally don't see a problem as I have veem running at remote location and in work so I have 2 copies of the data

[Cache]

Yeah shouldn't be a problem, as it's similar to what we did. I didn't bother exporting the database however and instead just recreated the jobs on a new install as I got the server up and running - we didn't have the job history as a result and created a new backup chain, but it wasn't a major headache to recreate as I did a few other changes at the same time.