Just want to confirm, during an archiving job (whether is standalone archiving agent or FS agent with one pass enabled), all file qualified for archiving are first copied to the storage policy repository first, then only get deleted on produciton storage and replaced by stub during the "stubbing" phase, correct? meaning CV does not stub files one by one as it is being archived.
also, if during the stubbing process, the job failed or goes into pending state due to unforeseen issue (black out, MA failure, CS failure etc), what is the impact to the production files?
My guess is that those file that is not being stubbed remained as unarchived file on the production storage and will be archived during the next archive job. But in the mean time, CV already has a copy of the un-stubbed file in the storage policy repository.
please correct me if I am wrong.