Hi David,
Thank you for your reply.
You are near, but not to 100%.
1: correct
2: don't need to be moved, but newly created has to be stored locally
3: the actually exiting restore points have to stay on the FAS. But the also have to retain the retention policy and be deleted as configured.
4: not sure....
5: all over we will have 3 versions. Local, FAS and Tape. Local for fast backup and recovery. FAS for long term storage, Tape as security.
I would like to hold the old backups on the FAS and set them as Secondary destination with a "copy job" while creating a new primary destination localy with a new retention policy.
The local repository is much faster than the FAS repository. This way the backups would go much faster, and the Veeam has after the primary backup, enough time to transfer to the FAS for longterm storage.
The main problem is if a switch the repository, i loos the retention policy on the exiting restore points.
Best regards
Adrian
Thank you for your reply.
You are near, but not to 100%.
1: correct
2: don't need to be moved, but newly created has to be stored locally
3: the actually exiting restore points have to stay on the FAS. But the also have to retain the retention policy and be deleted as configured.
4: not sure....
5: all over we will have 3 versions. Local, FAS and Tape. Local for fast backup and recovery. FAS for long term storage, Tape as security.
I would like to hold the old backups on the FAS and set them as Secondary destination with a "copy job" while creating a new primary destination localy with a new retention policy.
The local repository is much faster than the FAS repository. This way the backups would go much faster, and the Veeam has after the primary backup, enough time to transfer to the FAS for longterm storage.
The main problem is if a switch the repository, i loos the retention policy on the exiting restore points.
Best regards
Adrian
Statistics: Posted by informatik@saanen.ch — Feb 13, 2025 12:14 pm






