Hi,
I am having a very interesting debate with one of my IT resources. Due the backup storage solution he previously bought, I've been asked to drop backup files over the network.
Now, having offsite backups (and rotate or keep those in a removable media) is perfectly fine, but the backup pipe does not look enough to me. I am actually having some issues due SAN and network bandwidth. So, long story short, I am trying to re-design the existing backup jobs so I can use that share.
I've been doing some testing, and it looks like RedGate 7.0 "does not like" when I map the share drive, let's say using "Z" drive, and specify that in the backup job. Instead, if I use the UNC path, like \\server\whatever folder, the backup jobs seems to work without an issue.
Here are my two questions, or actually two questions and requesting one technical advice![Wink]()
1. Can I specify on RedGate, step #3 of scheduling backups, a UNC or regular Windows mapping, on the Folder field? Or a UNC path is mandatory>
2. If I can specify UNC or regular drive letter paths when using a folder, what could be the problem with the Windows mapping, as permissions look to be ok.
The technical advice or question would be ... should I use the "copy backup to network" option or schedule a total separate job for the offsite backups? I am trying to reduce network and IO stress on the SAN Cluster and network.
And should I stick to the UNC or create a Windows mapping? I know RedGate is Cluster aware, and assuming the UNC does not change, it should be more stable than a Windows mapping with a given letter, am I right about that?
I am having a very interesting debate with one of my IT resources. Due the backup storage solution he previously bought, I've been asked to drop backup files over the network.
Now, having offsite backups (and rotate or keep those in a removable media) is perfectly fine, but the backup pipe does not look enough to me. I am actually having some issues due SAN and network bandwidth. So, long story short, I am trying to re-design the existing backup jobs so I can use that share.
I've been doing some testing, and it looks like RedGate 7.0 "does not like" when I map the share drive, let's say using "Z" drive, and specify that in the backup job. Instead, if I use the UNC path, like \\server\whatever folder, the backup jobs seems to work without an issue.
Here are my two questions, or actually two questions and requesting one technical advice
1. Can I specify on RedGate, step #3 of scheduling backups, a UNC or regular Windows mapping, on the Folder field? Or a UNC path is mandatory>
2. If I can specify UNC or regular drive letter paths when using a folder, what could be the problem with the Windows mapping, as permissions look to be ok.
The technical advice or question would be ... should I use the "copy backup to network" option or schedule a total separate job for the offsite backups? I am trying to reduce network and IO stress on the SAN Cluster and network.
And should I stick to the UNC or create a Windows mapping? I know RedGate is Cluster aware, and assuming the UNC does not change, it should be more stable than a Windows mapping with a given letter, am I right about that?