We are trying to seed a backup copy job for one of our Cloud Connect clients. Running into an issue where the second (job run) is filling up our NAS and the job is failing. I think the issue is the minimum 2 restore points for the Backup Copy job. Can we just create a regular backup job pointed to the NAS as the repository, only have 1 restore point, and use that as a seed to move to the Cloud? Would the cloud job then need to be a regular backup job, or could we create a new backup copy job and point to that .vbk file as the seed?