v10 NAS with capacity tiering to AWS

[mtran]

I opened a case with support: ID# 04219429

I have setup a SOBR with onsite object storage(using Pure FlashBlade) for NAS backups. We are using NFS.
For capacity tier we attached a AWS S3 target. <-- Nevermind, I just learned capacity tier doesn't work for NAS backups.

In the job, keep previous files versions is enabled.
The SOBR has copy data to job as soon as it is created and archive is set as well. I will test further

The patch for 3161 was also applied.

thanks.

[mtran]

Looks like it was the archiving option and tming needed to be lined up. Working now. Thanks.

[Dima P.]

mtran,

Correct - data is being uploaded to the archive repository only after it is retired in the primary repository (basically you need to wait for the retention set for the primary repository). Glad everything works as expected!

[mtran]

I have an additional question for clarification Dima.

Once an items is retired from primary. In an example, if there are 2 files a.txt and b.txt and both are backed up to a repository. and I set the retention for 1 week. and archive retention for 1 year. after 1 week, will the files be copied to archive storage? if the files don't change each week, will they just stay on primary storage and not get archived off?

thank you.

[Dima P.]

If file was not modified (changed or deleted) then it remains in the primary repository and never lands the archive. Archive is for older file versions only. Thanks!

[Gostev]

@mtran do you want even the most current version to be immediately copied to the archive? Or you're merely wondering how it works today?

[mtran]

@gostdev I wanted the most current version copied. but I had a discussion with a Veeam sales engineer and he said NAS archiving doesn't do that. So I created an EC2 instance with EBS storage and that seems to be working. I have a different problem which I will create a new case on.