BlackArmor NAS Network Storage Server

[BOLDER Designs]

As an IT professional, I must say that the documentation on the Seagate Black Armor NAS devices is lacking.

I'm looking at the NAS to NAS backup capability for off-site backup and some of the interface is very puzzling. While you can setup the Backup Service on the destination NAS, you can't see where the data is going. It appears that you have to turn off the Backup service BEFORE you can check the box to "Add Backup Shares to CIFS Share".

So how in the workld do you know if your files are making it to the destination NAS? On the destination box, you need both options available and on.

And Port Forwarding, that option is not mentioned anywhere in the documentation.

So I have a box that is supposedly backing up one share to the remote NAS, but no way to know that it is in fact working.

********

And on the adding to Domain, why in the world would you hide the adminsitrators name? Password, yes, but name, no.

[johnbehr]

I have to say this was puzzling to me as well.  I was able to get the NAS to NAS working but it's not clear whether simply on-demand or if it is continous (replication).  I was reading Data Sheet and it mentioned NAS to NAS replication but, here again, there is no way to tell if the NAS to NAS backup is what Seagate means by replication.  On the whole though, I was suprised at how easy it was to set up the NAS.

[JMM]

Curious -  are you using two of the Segate NAS devices or were you able to get it working to a different brand device?

[johnbehr]

I have two of the BlackArmor 440s that i would like to replicate to one another but i don't seem to be able to do that.  On the other hand, I have been able to connect to my primary BlackArmor server from a Linux box (running Ubuntu 9.10 server) with NFS (while keeping the share on the BlackArmor server read only).  Once I created the mount point on the Linux box I use cron and rsync (to sync between the mount point and another set of local folders) to get a copy of the folders and files off of the BlackArmor server. I'd like to be able to replicate my two BlackArmor server for my LAN users and use the linux box for an off-site backup of one of the NAS boxes.   I hope this helps.

[JGraz10]

I have two Black Armor 440 NAS devices. I have used the Back Up manager in an attempt to replicate all the data on one device onto the other. However... What appears to happen is that the back up process creates a file on the original device. You can then "restore" the data in that file onto the other device. 

OK. If this is the way to do it... I learned something. (not in documentation or advertisements)

In addition... I now have these test back ups on my source drive and I am unable to find them to delete them. Normally I would not have a problem with this, except that I now have my original 4TB BA device (#1) reporting that it is 100% full.

Any ideas on how to fix that would be greatly appreciated?

[mygk1234]

copy from another thread ---

Hi,

1. NAS to NAS backup will keep data in a hidden NAS share, and only can be exposed as a read-only NAS share. Backup Manager\Backup Server\Server Setting uncheck "Backup Service", then you can check "Add Backup Share to CIFS Share", you can read the backuped data via samba.

2. to remove "NAS to NAS" backup content, you need to delete the alias via "Delete alias," then it will prompt a popup box to ask if you want to remove all of backup data under this alias module. .

[alienreptile]

---

mygk1234 wrote:

copy from another thread ---

Hi,

1. NAS to NAS backup will keep data in a hidden NAS share, and only can be exposed as a read-only NAS share. Backup Manager\Backup Server\Server Setting uncheck "Backup Service", then you can check "Add Backup Share to CIFS Share", you can read the backuped data via samba.

2. to remove "NAS to NAS" backup content, you need to delete the alias via "Delete alias," then it will prompt a popup box to ask if you want to remove all of backup data under this alias module. .

---

I followed the steps in step 1.  I see a share called __RSYNC_BAKCUPSPACE_NAME__1 after I add the backup share to CIFS Share.    So what you are saying is that after I do this, I can only access this share using a SAMBA client?  I'm using this device in a Windows environment.  I can't access this share through Windows.  I know you didn't create this product, but why on earth would they make it this difficult?!?!  It's a backup!!  How hard is it to make it accessable?  The point of a backup is so you can access it if needed.  I can't change the share name no matter what I do.  I can't access this share in Windows no matter what I do.  Are there any more details or suggestions you can give me?

Thanks

[RAsg]

Hello,

This is how the "Add Backup Shares to CIFS Share" option works for me.

After the NAS to NAS backup completes I enable "Add Backup Shares to CIFS Share" in the Manager page of the destination NAS.

I opened the root of the destination NAS by Start and Run, \\nas ip address.

Windows prompted for a username and password for the root.  I gave it the Manager page username and password which is admin, admin and the root opened.

The hidden repository is now a folder on the root of the destination NAS called, "backupSpace1".  It opens for me without issue and I can drill down to all the data.

[wixly]

this is definitely not NAS to NAS replication...Seagate please explain as you advertised in your brochure...

[RAsg]

Hello,

NAS to NAS backup is it.  It replicates the user share data only.