User manual

Chapter 4: Site Management
132 Cobalt RaQ 4 User Manual
Backup file locations
For a backup by an FTP Server:
• A location of <username>@ftp.server.com puts the backup file in the
initial login directory.
• A location of <username>@ftp.server.com/path/to/backups/ puts the
backup file in the specified path on the server, using <username> to login.
For a backup by Anonymous FTP:
• For an anonymous FTP connection, the file must be put in a directory where
anonymous FTP users have write access. This is generally the
/incoming/
directory.
• A location of ftp.server.com/incoming places the backup file on
ftp.server.com under the /incoming/ directory.
• The “Password” field should contain the password for the specified user or
be left blank for anonymous logins.
For a backup by NFS Server:
• The location should be <server>:/<share>, where <server> is the NFS
server and <share> is the NFS volume to mount and write to. You must have
write privileges to this directory.
• The “Password” is ignored for NFS server backups.
For a backup by SMB Server (Windows File Sharing):
• The location should be <user>@\\windowspc\<share>. This mounts the
volume share on the Windows server, using <user> as the login. The
“Password” field must contain the password for <user>.
• For volumes that do not require a user, the location should be
\\windowspc\share.
For All Scheduled backups:
• Ensure the target location is available and has enough disk space to hold the
backup archive. Failure to do this may result in zero-length or truncated
archives.