Backup

• What's the difference between Windows Timestamp and Archive Bit backup?
• What is the requirement for using Archive Bit backup mode?
• How do I resolve the "access denied" error during a Backup using the FrontView Backup Manager?
• I cannot backup my data from the ReadyNAS share folder to the attached USB hard disk. What should I do?
• How do I setup two ReadyNAS units to mirror each other with the built-in backup manager using the rsync protocol?
• How do I backup users' private home folders in Domain security mode?
• How do I resolve the FTP timeout issue during the backup? What is the current ftp time out setting on the ReadyNAS?
• How can I backup Windows shares with files with foreign characters in their names?
• I cannot use Umlaut characters in backup path.
• How should I backup my ReadyNAS to another ReadyNAS?
• How do I backup an entire drive on a Windows PC to a share on the ReadyNAS?
• My backup failed because of an "unknown error".
• How can I download a copy of the entire backup log?
• Backups are failing when using rsync. Why?
• Backups using the built-in backup manager are failing with Windows 2003 Server sources. Why?

Backup

What's the difference between Windows Timestamp and Archive Bit backup?

Timestamp backup uses the file timestamp to determine if incremental backup should include the source file or not. The source file will be copied only if the timestamp on the file is later than that on the destination.

Archive Bit backup is similar to how Windows perform its backups and is the preferred method for backing up Windows. It uses an archive bit for each file to determine if the file has been backed up already or not. Once the file has been backed up, the archive bit gets cleared, so the file will not be included in future backups.

What is the requirement for using Archive Bit backup mode?

While the Archive bit backup type is the preferred type for Windows backups, the need to modify the archive bit on the source leads to three requirements. If they cannot be met, the Timestamp method should be used instead.

1. That ReadyNAS has both read and write capability for the source location. For example, this excludes all NTFS volumes connected via USB (NTFS on USB is supported only in read-only mode), but not FAT32 volumes connected via USB.

2. That ReadyNAS has write access for the source location, specifically the type that allows it to modify the Archive bit.

3. That ReadyNAS is the sole backup solution using the Archive bit method for the source location. Failure to meet this requirement will lead to incomplete backups for one or both backup systems.

How do I resolve the "access denied" error during a Backup using the FrontView Backup Manager?

Verify that you are able to access the backup source share over the selected protocol and using the credentials you entered when configuring the backup job.

I cannot backup my data from the ReadyNAS share folder to the attached USB hard disk. What should I do?

1. Make sure that the USB device is listed in Frontview.
2. Verify that you can successfully access the USB drive share over the network when it is connected to the ReadyNAS.
3. Check that the USB drive is formatted with Ext2/3 or FAT32 file system.

How do I setup two ReadyNAS units to mirror each other with the built-in backup manager using the rsync protocol?

Enable rsync access for the shares to be mirrored on both ReadyNAS devices. Then, on each ReadyNAS, create a backup job using the remote share as the source, and the local share as the destination. Schedule these jobs so that they do not run at the same time.

How do I backup users' private home folders in Domain security mode?

Select Home Share as the backup protocol, and then enter the name of the user in the field under the protocol dropdown list.

How do I resolve the FTP timeout issue during the backup? What is the current ftp time out setting on the ReadyNAS?

The backup manager will timeout on attempts to access an FTP server after 270 seconds. If the connection is still timing out, try accessing the remote server at a less busy time. Also, try connecting to the remote FTP with an FTP client to verify that it is available.

How can I backup Windows shares with files with foreign characters in their names?

Use the Windows (Archive Bit) backup protocol which will handle foreign characters without a problem.

I cannot use Umlaut characters in backup path.

By default, backup path name can contains only English ascii characters. In order to allow other characters in this feild, you need to enable "Allow Unicode for user, group and share names" option in FrontView's System/Language tab. This option is available only when Language is set to Unicode. Onece this option is enabled, all Unicode characters can be used, such includes Germanic Umulaut, Cyrillic characters, Chinese characters, etc.

How should I backup my ReadyNAS to another ReadyNAS?

Use the rsync protocol in the backup manager to transfer the files from one ReadyNAS to another. Rsync can also handle incremental backups efficiently. If several shares need to be backed up, create a separate backup job for each share.

How do I backup an entire drive on a Windows PC to a share on the ReadyNAS?

Put a dollar sign ($) at the end of the share name. For example, if the D: drive is being shared on the Windows machine, the source path would be: //$machine/D$

My backup failed because of an "unknown error".

Try searching the backup logs for lines starting with the word "cp:". The error message in these lines will give you some clues.

How can I download a copy of the entire backup log?

Use the Download All Logs link or use the Send All Logs button and send the logs to your personal email address.

Backups are failing when using rsync. Why?

rsync can use a lot of memory and the default 256MB memory may not be enough. Consider upgrading to 1GB.

Backups using the built-in backup manager are failing with Windows 2003 Server sources. Why?

You must use the Windows (Archive Bit) protocol to back up from a Windows 2003 system. If you do not use the Windows (Timestamp) protocol, you will need to make sure that SMB signing is disabled on the Windows 2003 Server machine.