Hi,
I am hoping this isn't a technical issue.... I am in the process of upgrading a legacy backup copy in v12. I've done the following steps
Detached the disks from the old backup copy job
Created a new job adding the backup jobs
Kept the backup repository the same and selected 'map backup' and drilled down to the folder where the backup copy files are.
A new folder was created with the name of the backup copy on the repo and files are being written to it.
My question is will this folder match the existing storage of the legacy backup copy folder? I don't have enough storage space on my repo to hold that much data...the size of my legacy backup copy is around 5TB and I have about 2.5 free on the repo to use....
Thanks for any help!
Dave
-
- Lurker
- Posts: 1
- Liked: never
- Joined: May 17, 2024 6:09 pm
- Contact:
-
- Veeam Software
- Posts: 2331
- Liked: 554 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Upgrading legacy backup copy and storage space
Hi dchase180, welcome to the forums.
First, just to confirm, did you go through the Upgrade Backup Chain Format process? From your description it sounds like you made a new job and just let it start a new backup chain, which is a perfectly suitable option, but it will mean that you have for a short time both the old legacy backup chains under the Backups > Disk (Orphaned) node in the UI and also the new backup chains for a period of time.
As for the size, is the 5 TiB count the sum of all the backup files as shown in the properties or where did you determine that value? Basically, the new jobs will start with an new Full first (as they already have), and initially they will require space for a Full*; with just the above information will not be able to predict accurately for you, but you can use our Veeam Calculators to estimate the space requirements.
* Note: If your repository supports Fast Clone, then you may see space savings also as noted in the User Guide link.
First, just to confirm, did you go through the Upgrade Backup Chain Format process? From your description it sounds like you made a new job and just let it start a new backup chain, which is a perfectly suitable option, but it will mean that you have for a short time both the old legacy backup chains under the Backups > Disk (Orphaned) node in the UI and also the new backup chains for a period of time.
As for the size, is the 5 TiB count the sum of all the backup files as shown in the properties or where did you determine that value? Basically, the new jobs will start with an new Full first (as they already have), and initially they will require space for a Full*; with just the above information will not be able to predict accurately for you, but you can use our Veeam Calculators to estimate the space requirements.
* Note: If your repository supports Fast Clone, then you may see space savings also as noted in the User Guide link.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: No registered users and 65 guests