I cannot backup my data from the ioSafe R4 share folder to the attached USB hard disk. What should I do?
- Make sure that the USB device is listed in Frontview.
- Verify that you can successfully access the USB drive share over the network when it is connected to the ioSafe R4.
- Check that the USB drive is formatted with Ext2/3 or FAT32 file system.
|
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.
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.
- The ioSafe R4 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.
- The ioSafe R4 has write access for the source location, specifically the type that allows it to modify the Archive bit.
- The ioSafe R4 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.
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.
I can access my ioSafe R4 over FTP using an FTP client, but not with Internet Explorer.
Try putting your internal or external IP address (depending on whether you will be accessing the NAS from a server on your local network or through the Internet) in the Masquerade As field in the Services page.
I can't seem to access certain files and directories in my FTP share.
Depending on the security mode and FTP mode, you may need to adjust the permissions on these files and folders to permit access through FTP. In Share mode or Anonymous FTP mode, the NAS will see an FTP user as a user named "ftp". Therefore, files and folders will need to be accessible by this user for them to be accessible via FTP.
Read more...
I get errors when I try to issue FTP commands. My logs mention extended passive mode.
Try forcing your FTP client to use active (PORT) or standard passive (PASV) mode. Extended passive (EPSV) is only needed to IPv6 networks, and is not supported by the ioSafe R4.
How can I access my ioSafe R4 through FTP when my ioSafe R4 is behind my home firewall and my client is behind my school/work/etc. firewall?
You will need to setup the ioSafe R4 for passive (PASV) FTP. To do this, go to the Services page and setup the options under FTP. In this case, you will need to select a passive port range (in most cases, a small range of 10 to 20 ports will do) and forward it from your router to the NAS. You will also need to enter your public domain name or IP address in the Masquerade field. For more information on passive FTP, go here: http://slacksite.com/other/ftp.html
|
I can log into the ioSafe R4, but when I try to transfer files, the transfer rate almost immediately goes to 0 and eventually times out. What's wrong?
Try changing the MTU on your router to 1492. This is often needed when the ioSafe R4 is connected to the Internet through a Cable-based broadband service.
How do I setup the ioSafe R4 for anonymous FTP in non-Share security mode?
In the Services page, select Anonymous for FTP mode. Note that Anonymous FTP is the only mode available in Share mode.
How can I setup my ioSafe R4 for FTP access over the Internet?
You need to configure your router for port forwarding. Ports 21 and the passive port range, which can be configured in the Services tab, must be forwarded to the ioSafe R4 IP address. Also set the "Masquerade as" setting to your external IP address or domain name.
How can I setup port-forwarding to the ioSafe R4?
Port-forwarding is a way of selectively allowing access from a WAN (Internet) to your LAN through your existing router firewall. Only the network protocol "ports" that you forward will be allowed access to a particular box on your LAN. For instance, if you want to enable only FTP access to your ioSafe R4, simply forward ports 20 and 21 on your router to the ioSafe R4 IP. You can do the same for HTTP or HTTPS by forwarding ports 80 and 443. Each router will have a slightly different method to allow this option. Here's a link that explains how you would do this with a lot of the routers on the market. This link courtesy of MrCyberdude. http://www.portforward.com/english/routers/port_forwarding/routerindex.htm
Why won't rsync retain my UIDs/GIDs?
To maintain access compatibility with other protocols, rsyncd will transfer files as the share user in Share security mode. This means that files transferred to the NAS over rsync will be owned by the share user. To maintain UIDs/GIDs, use User security mode, or NFS mount the share with root-enabled hosts properly set in the NFS configuration tab in Frontview and do a pseudo-local rsync.
Why am I not able to access an ioSafe R4 share that is password protected with Vista?
When accessing a file share on a remote computer or device, Windows Vista will refuse to send your password using older encryption methods.
Unfortunately, many NAS devices as well as older versions of linux do not understand the newer encryption methods. This keeps you from being able to access these devices.
The solution is to force Windows Vista to use the older encryption methods. To do that, follow these steps:
Read more...
When I initially connect to a share, there is a long delay. How can I fix this?
There are occasions where Windows' behavior of trying to connect using WebDAV first before SMB/CIFS causes a long delay. The easiest way to fix this is to just disable the WebClient service in Windows. You can do this from Windows by going to Control Panel -> Administrative Tools -> Services. From there, open the WebClient service, stop it, and also select the option to disable it at startup.
|
|
|
|
