Hi.
- Backup repository on Synology NAS over SMB.
- NAS IP has been changed
- Backup jobs & backup copy jobs temporary disabled
- Added new repository (NAS with it's new IP); This repository has been added with: "User per-machine backup files" enabled
- Backup jobs & backup jobs have been relinked to new backup repository
Question:
NAS added in repository (before changing the IP) didn't have: "Use per-machine backup files" ENABLED. So backups of all VM's were stored in 1 (big) file.
What will happen in the next backup copy job now, when backup repository will have this enabled.
A new FULL backup will happen?
Or it will just split the files?
What happens with backup files if you had GFS policies?
Thank you.
-
- Service Provider
- Posts: 113
- Liked: 16 times
- Joined: Apr 25, 2022 6:18 pm
- Full Name: Bostjan UNIJA
- Contact:
-
- Product Manager
- Posts: 14815
- Liked: 1771 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Use per-machine backup files (after NAS change IP)
Hello BostjanUNIJA,
Backup jobs will start a new full backup and a new backup chain. The excising backup files will be moved under imported node during the next repository rescan, you can use them for recovery but such backups wont be deleted automatically according to retention, so should be removed manually when no longer needed.
The better option would be to keep the job settings 'as-is' create a new repository, move backups to a new repository using the move feature, then change the repository to a pre-machine files and upgrade backup chain. In such case backup job will start from the full backup but the existing single file backups will be considered as orphaned and will be subject to a background retention.
Backup jobs will start a new full backup and a new backup chain. The excising backup files will be moved under imported node during the next repository rescan, you can use them for recovery but such backups wont be deleted automatically according to retention, so should be removed manually when no longer needed.
The better option would be to keep the job settings 'as-is' create a new repository, move backups to a new repository using the move feature, then change the repository to a pre-machine files and upgrade backup chain. In such case backup job will start from the full backup but the existing single file backups will be considered as orphaned and will be subject to a background retention.
Who is online
Users browsing this forum: No registered users and 114 guests