We need to encrypt a single folder on our network per a client contract (security compliance and regulations) and instead of encrpyting the entire B2D folder, I was going to exclude that 1 single folder and add it to a subfolder off the root of the backup B2D folder and encrypt it as a seperate backup job.
Encryption is done on each individual backup set and is determined by the setting in the job that produced the backup set. It has nothing to do with the disk storage which is just a container. You can have a mix of encrypted and non-encrypted backup sets in a single disk storage.
I have already seperated the jobs into two different schemes (one without encryption and the other with encryption which includes ONLY the 1 folder for the backup selection.)
It's the storage device which I cannot add or modifiy that is giving me issues.
I may have found a workaround though as our backup requirements have been changed.
Because I want to write a script to copy this single backup to a remote server and having it in a seperate folder is eaiser to tell what the source file is.
I could crossference the raw backup file name to the backup job name but that's a pain, especially if I write daily fulls.
I was going the to configure the remote server as a new storage device as the target but BE14 won't let me create a new storage device outside of the BE server's domain.
Even if I setup a trust relationship in BE under Backup and Restore, can I create the new remote storage device and point the backup to that remote location?
You should not copy .bkf files. See this document
You should always duplicate your backup sets.
You can define a disk storage on the remote server using the IP address of the remote server, but you may have bandwidth problems.
I am having issues connecting to the remote server using the IP address, that's the whole issue.
I have no problem creating a dedupe job if I can point it to the remote server.
error msg is attached.
I can browse to the shared remote storage via unc (it's prompts for credentials since it's on a different domain within the VPN tunnel) so I can actually get to the server from the BE server.
If it's a networking issue that BE cannot get around for cross domain authentication, I could use the existing B2D storage, dedupe the job to another local disk (either on the BE server with another driver or somewhere on the local network) then use my script to transfer the dedupe folder to the remote location?
If BE14 only allowed subfolders within B2D, I wouldn't have to go through all these steps.