[All]
gbaking a database to a remote machine using UNC filename
Abstract: gbaking a database to a remote machine using UNC filename
Problem:
The command line gbak will NOT accept a node name as part
of the destination file for the gbak'd database. The following
example will NOT work:
gbak -b employee.gdb nuschler:c:employee.gbk (Won't work)
You get the following errors:
gbak: cannot open backup file nuschler:c:tempemp.gbk
gbak: Exiting before completion due to errors
Solution:
The solution is to use a UNC filename.
Note: UNC filenames will only work with Windows machines
the gbaked file is just that, a file. As long as gbak has
permission to write the file the backup will be successful.
This is where UNC filenames come into play. If you have
the necessary privileges for a shared drive you can write
the destination gbaked file to that share.
This is an example of gbaking a database that resides on
a remote machine and writing the gbaked file to the same
remote machine.
gbak -b skidmark:d:tempemployee.gdb skidmarkSkidMarktempemp.gbk
In this example I have permission to write to the share
"SkidMark". I am backing up a database that resides on a
remote machine and writing the backup file out to the same
remote machine.
