NAS for rsync backups

I have a couple of small Netgear NAS boxes that I use for archive and
general storage. I'd like to setup a larger NAS so I can rsync data
to our remote site for redundancy. Won't be accessed by users - just
need a reliable box for a nightly rsync. I'm thinking 12-18 TB of
storage space. I'm looking at rackmount Netgear boxes, but any other
suggestions?
Ken

KeN Etter sounds like they 'said':
> I have a couple of small Netgear NAS boxes that I use for archive and
> general storage. I'd like to setup a larger NAS so I can rsync data
> to our remote site for redundancy. Won't be accessed by users - just
> need a reliable box for a nightly rsync. I'm thinking 12-18 TB of
> storage space. I'm looking at rackmount Netgear boxes, but any other
> suggestions?
>
> Ken
So my response to KeN's comment is...
We have been using qnap boxes for different storage options, they've
worked pretty well for us.
Stevo

Similar Messages

  • Best way to create unpriviledged user for rsyncing backups?

    I'm wanting to use <code>rsync</code> or <code>ssh</code> with RSA authentication in order to automate moving backups  for multiple servers to a centralized/dedicated machine.  I'd like to know what you guys would recommend as far as creating a user to do that job on each of the servers...they won't ever have to have shell access or anything, but just enough priviledges to run the cron job itself.
    I've read around a few places, and one suggested something like this:
    groupadd -g 3500 backup
    useradd -u 3500 -s /bin/false -d /backup -m -c "backup" -g backup backup
    Does the gui/uid number really matter?  Is there anything else I'll have to worry about?  After that, I just planned on doing a <code>su -m backup</code> and then generating the keys.  Any help/suggestions would be greatly appreciated...

    Thanks for the link...I'll probably just go ahead and mess around with it.  It's not too difficult to make changes later.

  • Problems connecting an external drive (NAS) for TimeMachine backup

    Hi everyone,
    I have bought a Verbatim MediaShare, and want to use it as a media NAS, but also as a source for TimeMachine.
    I have created an administrators account on the MediaShare NAS, and then launches the Verbatim application "ComputerBackup"
    The application first verifies the user account on the MediaShare, and the administrator account is accepted:
    I then click the "next" button:
    Click the next button again, and then get the following (Safari launches, and I get the -1409 error. from MountVolume.app):
    When i click the "edit-buttun" (redigera) in the error message window, the Appelscript interpretor starts:
    MountVolume.app gets stuck on the row "open for access myPrefsFile". The value of myPrefsFile is:
    /Applications/
    MediaShare Desktop Applications/ComputersBackup.app/Contents/MacOS/Configure Time Machine.app/Contents/MacOS/MountVolume.app/Contents/MacOS/settings.txt
    The file "settings.txt" really exits in that location, and the content of it is: NETBIOS=MEDIASHARE2
    The content is probably of no interest, since the error is caused when opening the file for access.
    Why do i get the -1409 (Fork error something),
    and most important how can I solve the problem?
    BRG
    /Johan - Sweden
    /Applic 

    Hello
    Try send your question to [email protected] , i doubt any one have answer to your question here
    I have done that, sofar no response, unforutnately.
    Last night i did a mont of the predefined volume for backups on the NAS (ComputersBackup$), and tried ti use it with TimeMachine. The backup starts, but after the preparation phase, it says "failed to create backup-image".
    Tnx for the tip about the articles.
    BRG
    /Johan                          

  • [SOLVED] Need help with rEFInd boot entry for rsync backup

    I made a successful backup my arch install to an other internal SSD disk (from my HDD).
    But now I can't figure out how to make a boot entry for this drive. The wiki only mentions GRUB, which I do not use.
    This is the fstab for my HDD:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda5
    UUID=c1822e3c-e037-4445-bdd8-b71778237dee / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 LABEL=SYSTEM_DRV
    UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    And this is the fstab on my SSD which I edited:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sdb1
    UUID=c61a1301-4728-465d-b40b-bde5e084eb50 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 LABEL=SYSTEM_DRV
    UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    But I'm not sure about the /boot entry, do I need something else here?
    Afterward I tried updating rEFInd by reinstalling using refind-install, but that did not work.
    ps. I dual boot with Windows.
    Last edited by Devenda (2014-08-18 07:58:07)

    I also tried adding the menu entry manually by editing refind.conf but that didn't work. I got:
    Invalid loader file!
    Error: Not Found while loading vmlinuz-linux
    Here is some additional info:
    refind.conf:
    menuentry "SSD Arch Linux" {
    icon /EFI/refind/icons/os_arch.png
    volume "ArchSSD"
    loader /boot/vmlinuz-linux
    initrd /boot/initramfs-linux.img
    options "root=/dev/sdb1 ro"
    I hope this helps.
    blkid
    /dev/sda1: LABEL="WINRE_DRV" UUID="7C2ADD1D2ADCD4EC" TYPE="ntfs" PARTUUID="b7137819-2ca6-40fb-9167-b73ac37d8d96"
    /dev/sda2: LABEL="SYSTEM_DRV" UUID="D2DF-9F74" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9c77b526-730f-42f9-9904-f9a31b205687"
    /dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4d5275b-24c1-4847-b937-345bc23bec89"
    /dev/sda4: LABEL="Windows 8" UUID="38D6E449D6E408C8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d777a359-f42c-4629-a07c-cc55316352fe"
    /dev/sda5: UUID="c1822e3c-e037-4445-bdd8-b71778237dee" TYPE="ext4" PARTUUID="3d282004-2515-4630-b82e-35ed7f707b89"
    /dev/sda6: UUID="F80680CC06808D76" TYPE="ntfs" PARTUUID="575bc623-c7f1-44da-a79e-220ce3c98d9b"
    /dev/sda7: LABEL="Lenovo_Recovery" UUID="0898D76B98D75632" TYPE="ntfs" PARTUUID="99bfc6d6-1b71-46d1-887e-2f7e65e3eab1"
    /dev/sdb1: LABEL="ArchSSD" UUID="c61a1301-4728-465d-b40b-bde5e084eb50" TYPE="ext4" PARTUUID="e87704a5-01"
    lsblk -f
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs WINRE_DRV 7C2ADD1D2ADCD4EC
    ├─sda2 vfat SYSTEM_DRV D2DF-9F74 /boot
    ├─sda3
    ├─sda4 ntfs Windows 8 38D6E449D6E408C8
    ├─sda5 ext4 c1822e3c-e037-4445-bdd8-b71778237dee /
    ├─sda6 ntfs F80680CC06808D76
    └─sda7 ntfs Lenovo_Recovery 0898D76B98D75632
    sdb
    └─sdb1 ext4 ArchSSD c61a1301-4728-465d-b40b-bde5e084eb50
    sr0
    boot tree
    /boot
    ├── BOOT
    │   └── boot.sdi
    ├── BOOTSECT.BAK
    ├── EFI
    │   ├── Boot
    │   │   ├── bootx64.efi
    │   │   ├── LenovoBT.EFI
    │   │   ├── License.txt
    │   │   └── ReadMe.txt
    │   ├── gummiboot
    │   │   └── gummibootx64.efi
    │   ├── Lenovo
    │   │   └── Boot
    │   │   ├── BCD
    │   │   ├── BCD.LOG
    │   │   ├── BCD.LOG1
    │   │   ├── BCD.LOG2
    │   │   ├── bg-BG
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── bootmgfw.efi
    │   │   ├── bootmgr.efi
    │   │   ├── BOOTSTAT.DAT
    │   │   ├── boot.stl
    │   │   ├── cs-CZ
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── da-DK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── de-DE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── el-GR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── en-GB
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── en-US
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── es-ES
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── et-EE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── fi-FI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Fonts
    │   │   │   ├── chs_boot.ttf
    │   │   │   ├── cht_boot.ttf
    │   │   │   ├── jpn_boot.ttf
    │   │   │   ├── kor_boot.ttf
    │   │   │   ├── malgun_boot.ttf
    │   │   │   ├── malgunn_boot.ttf
    │   │   │   ├── meiryo_boot.ttf
    │   │   │   ├── meiryon_boot.ttf
    │   │   │   ├── msjh_boot.ttf
    │   │   │   ├── msjhn_boot.ttf
    │   │   │   ├── msyh_boot.ttf
    │   │   │   ├── msyhn_boot.ttf
    │   │   │   ├── segmono_boot.ttf
    │   │   │   ├── segoen_slboot.ttf
    │   │   │   ├── segoe_slboot.ttf
    │   │   │   └── wgl4_boot.ttf
    │   │   ├── fr-FR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── hr-HR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── hu-HU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── it-IT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ja-JP
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ko-KR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── lt-LT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── lv-LV
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── memtest.efi
    │   │   ├── nb-NO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── nl-NL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pl-PL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-BR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-PT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── qps-ploc
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Resources
    │   │   │   ├── bootres.dll
    │   │   │   └── en-US
    │   │   │   └── bootres.dll.mui
    │   │   ├── ro-RO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── ru-RU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── sk-SK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sl-SI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-CS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sv-SE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── tr-TR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── uk-UA
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── zh-CN
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── zh-HK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   └── zh-TW
    │   │   ├── bootmgfw.efi.mui
    │   │   ├── bootmgr.efi.mui
    │   │   └── memtest.efi.mui
    │   ├── Microsoft
    │   │   └── Boot
    │   │   ├── BCD
    │   │   ├── BCD.LOG
    │   │   ├── BCD.LOG1
    │   │   ├── BCD.LOG2
    │   │   ├── bg-BG
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── bootmgfw.efi
    │   │   ├── bootmgr.efi
    │   │   ├── BOOTSTAT.DAT
    │   │   ├── boot.stl
    │   │   ├── cs-CZ
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── da-DK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── de-DE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── el-GR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── en-GB
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── en-US
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── es-ES
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── et-EE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── fi-FI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Fonts
    │   │   │   ├── chs_boot.ttf
    │   │   │   ├── cht_boot.ttf
    │   │   │   ├── jpn_boot.ttf
    │   │   │   ├── kor_boot.ttf
    │   │   │   ├── malgun_boot.ttf
    │   │   │   ├── malgunn_boot.ttf
    │   │   │   ├── meiryo_boot.ttf
    │   │   │   ├── meiryon_boot.ttf
    │   │   │   ├── msjh_boot.ttf
    │   │   │   ├── msjhn_boot.ttf
    │   │   │   ├── msyh_boot.ttf
    │   │   │   ├── msyhn_boot.ttf
    │   │   │   ├── segmono_boot.ttf
    │   │   │   ├── segoen_slboot.ttf
    │   │   │   ├── segoe_slboot.ttf
    │   │   │   └── wgl4_boot.ttf
    │   │   ├── fr-FR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── hr-HR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── hu-HU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── it-IT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ja-JP
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── ko-KR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── lt-LT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── lv-LV
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── memtest.efi
    │   │   ├── nb-NO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── nl-NL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pl-PL
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-BR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── pt-PT
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── qps-ploc
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── Resources
    │   │   │   ├── bootres.dll
    │   │   │   ├── en-US
    │   │   │   │   └── bootres.dll.mui
    │   │   │   └── nl-NL
    │   │   │   └── bootres.dll.mui
    │   │   ├── ro-RO
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── ru-RU
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── sk-SK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sl-SI
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-CS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sr-Latn-RS
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── sv-SE
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── tr-TR
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── uk-UA
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   └── bootmgr.efi.mui
    │   │   ├── zh-CN
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   ├── zh-HK
    │   │   │   ├── bootmgfw.efi.mui
    │   │   │   ├── bootmgr.efi.mui
    │   │   │   └── memtest.efi.mui
    │   │   └── zh-TW
    │   │   ├── bootmgfw.efi.mui
    │   │   ├── bootmgr.efi.mui
    │   │   └── memtest.efi.mui
    │   ├── refind
    │   │   ├── icons
    │   │   │   ├── arrow_left.png
    │   │   │   ├── arrow_right.png
    │   │   │   ├── boot_linux.png
    │   │   │   ├── boot_win.png
    │   │   │   ├── func_about.png
    │   │   │   ├── func_exit.png
    │   │   │   ├── func_firmware.png
    │   │   │   ├── func_reset.png
    │   │   │   ├── func_shutdown.png
    │   │   │   ├── os_altlinux.png
    │   │   │   ├── os_arch.png
    │   │   │   ├── os_centos.png
    │   │   │   ├── os_chrome.png
    │   │   │   ├── os_clover.png
    │   │   │   ├── os_debian.png
    │   │   │   ├── os_ecomstation.png
    │   │   │   ├── os_fatdog.png
    │   │   │   ├── os_fedora.png
    │   │   │   ├── os_freebsd.png
    │   │   │   ├── os_freedos.png
    │   │   │   ├── os_funtoo.png
    │   │   │   ├── os_gentoo.png
    │   │   │   ├── os_gummiboot.png
    │   │   │   ├── os_haiku.png
    │   │   │   ├── os_hwtest.png
    │   │   │   ├── os_kubuntu.png
    │   │   │   ├── os_legacy.png
    │   │   │   ├── os_linuxmint.png
    │   │   │   ├── os_linux.png
    │   │   │   ├── os_lubuntu.png
    │   │   │   ├── os_mac.png
    │   │   │   ├── os_mageia.png
    │   │   │   ├── os_mandriva.png
    │   │   │   ├── os_manjaro.png
    │   │   │   ├── os_mythbuntu.png
    │   │   │   ├── os_netbsd.png
    │   │   │   ├── os_openbsd.png
    │   │   │   ├── os_opensuse.png
    │   │   │   ├── os_redhat.png
    │   │   │   ├── os_refind.png
    │   │   │   ├── os_refit.png
    │   │   │   ├── os_slackware.png
    │   │   │   ├── os_suse.png
    │   │   │   ├── os_ubuntu.png
    │   │   │   ├── os_unknown.png
    │   │   │   ├── os_win.png
    │   │   │   ├── tool_apple_rescue.png
    │   │   │   ├── tool_memtest.png
    │   │   │   ├── tool_mok_tool.png
    │   │   │   ├── tool_part.png
    │   │   │   ├── tool_shell.png
    │   │   │   ├── tool_windows_rescue.png
    │   │   │   ├── transparent.png
    │   │   │   ├── vol_external.png
    │   │   │   ├── vol_internal.png
    │   │   │   └── vol_optical.png
    │   │   ├── icons-backup
    │   │   │   ├── arrow_left.png
    │   │   │   ├── arrow_right.png
    │   │   │   ├── boot_linux.png
    │   │   │   ├── boot_win.png
    │   │   │   ├── func_about.png
    │   │   │   ├── func_exit.png
    │   │   │   ├── func_firmware.png
    │   │   │   ├── func_reset.png
    │   │   │   ├── func_shutdown.png
    │   │   │   ├── os_altlinux.png
    │   │   │   ├── os_arch.png
    │   │   │   ├── os_centos.png
    │   │   │   ├── os_chrome.png
    │   │   │   ├── os_clover.png
    │   │   │   ├── os_debian.png
    │   │   │   ├── os_ecomstation.png
    │   │   │   ├── os_fatdog.png
    │   │   │   ├── os_fedora.png
    │   │   │   ├── os_freebsd.png
    │   │   │   ├── os_freedos.png
    │   │   │   ├── os_funtoo.png
    │   │   │   ├── os_gentoo.png
    │   │   │   ├── os_gummiboot.png
    │   │   │   ├── os_haiku.png
    │   │   │   ├── os_hwtest.png
    │   │   │   ├── os_kubuntu.png
    │   │   │   ├── os_legacy.png
    │   │   │   ├── os_linuxmint.png
    │   │   │   ├── os_linux.png
    │   │   │   ├── os_lubuntu.png
    │   │   │   ├── os_mac.png
    │   │   │   ├── os_mageia.png
    │   │   │   ├── os_mandriva.png
    │   │   │   ├── os_manjaro.png
    │   │   │   ├── os_mythbuntu.png
    │   │   │   ├── os_netbsd.png
    │   │   │   ├── os_openbsd.png
    │   │   │   ├── os_opensuse.png
    │   │   │   ├── os_redhat.png
    │   │   │   ├── os_refind.png
    │   │   │   ├── os_refit.png
    │   │   │   ├── os_slackware.png
    │   │   │   ├── os_suse.png
    │   │   │   ├── os_ubuntu.png
    │   │   │   ├── os_unknown.png
    │   │   │   ├── os_win.png
    │   │   │   ├── tool_apple_rescue.png
    │   │   │   ├── tool_memtest.png
    │   │   │   ├── tool_mok_tool.png
    │   │   │   ├── tool_part.png
    │   │   │   ├── tool_shell.png
    │   │   │   ├── tool_windows_rescue.png
    │   │   │   ├── transparent.png
    │   │   │   ├── vol_external.png
    │   │   │   ├── vol_internal.png
    │   │   │   └── vol_optical.png
    │   │   ├── keys
    │   │   │   ├── altlinux.cer
    │   │   │   ├── canonical-uefi-ca.der
    │   │   │   ├── fedora-ca.cer
    │   │   │   ├── openSUSE-UEFI-CA-Certificate.cer
    │   │   │   ├── refind.cer
    │   │   │   └── SLES-UEFI-CA-Certificate.cer
    │   │   ├── refind.conf
    │   │   ├── refind.conf.old
    │   │   ├── refind.conf-sample
    │   │   └── refind_x64.efi
    │   └── tools
    ├── grub
    │   ├── grub.cfg
    │   └── grub.cfg.example
    ├── initramfs-linux-fallback.img
    ├── initramfs-linux.img
    ├── loader
    │   ├── entries
    │   │   └── arch.conf
    │   └── loader.conf
    ├── refind_linux.conf
    └── vmlinuz-linux
    refind_linux.conf
    "Boot with standard options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet "
    "Boot to single-user mode" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet single"
    "Boot with minimal options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee"

  • NAS for offsite backup

    What is the best way to setup two Cisco NAS boxes over an internet connection to provide a seamless backup solution?

    Take a look at the "Setting Up Remote Replication - video application note" in the Technical Resources area.  This will walk you through replicating data between two Cisco Smart Storage devices.  Replication can be done locally or over the WAN connection.
    http://www.cisco.com/en/US/products/ps10817/prod_technical_reference_list.html

  • How to add NAS for iTunes and backups

    I would like to add NAS to home network of older iMac (OSX 10.7.4), win 7 notebook, soon to be added MacAir, plus iPad, iPhones, and sonos.  I would like to move iTunes from iMac external drive to NAS and also use NAS for time machine backups of the 2 Macs and a backup for the win 7 notebook.  Any recommendations on NAS for mostly Mac network?  Can I use the NAS for both iTunes and for backups? 

    Most of the big brands support TM.. QNAP and Synology being the main contenders.
    Moving itunes library is always dangerous and TM will not back it up.. since it is now on a network drive.. so take steps to ensure the library cannot be lost. This is of course far easier on a brand that has automatic backups and mirrored drives.. that the TC.

  • Which NAS you recommend for SMB backup storage

    Synology and ReadyNAS would be my first choices in this category.  I have and use both and love them.  I've had quite good success with Buffalo as well with clients.  Nearly all storage engineers that I know when choosing this type of storage, like Kooler, choice Synology and ReadyNAS.
    For backups and archives specifically I have had good luck with Drobo too.

    For me it's always between Netgear and Synology. Now I'm back to Netgears (being a green guy here I cannot tell reason in public).For anything bigger then 2 SATAs in RAID1 economically reasonable to "roll your own" backup appliance. Recycled Dell R7xx and again recycled Windows Server 2012 R2 (because of SMB3 and decent backup-ready dedupe) appliance is very hard to beat! In case you don't have old server xByte has a stack of reburbished ones they sell cheap.--Planning to buy a NAS storage for our backups.Very small environment with VMware host, 7 VMs, Veeam backup.Total backup size 200GB, daily increment is around 7-10GB (Compressed).Will use the NAS for backup storage only and nothing else.Which brand do you recommend or use at your SMB locations:SynologyQNAPSeagateNetgear ReadyNASBuffalo

  • Best video format for converting DVD to NAS for widely sharing

    Summary: The article shows you with an easy workaround for
    copying DVD to NAS for streaming by ripping DVD to NAS friendly video
    format on Mac and Windows
    I recently purchased a NAS to store all my music/photos etc on. I
    can stream stuff to my iPhone/iPad using the NAS software. What I want
    to do is rip all my DVDs (over 400) to my NAS, but I’m not sure which
    format to do it in, to play nice with my Apple TV2, Xbox 360, iPhone,
    iPad etc. I wanna get some advice as to what format to rip in and what
    software to use?
    Learn some tips from online, I got know that to copy dozens of DVD movies to NAS,
    you need to get the content off the DVD disc as a protection-free and
    easily readable element for NAS. In this case, at the first place
    powerful third-party software for backup DVD to NAS is what you need.
    There are many, many DVD ripping tools on the market. I’ve tired a pile of them.
    Brorsoft DVD Ripper
    is the best one I’ve tried yet. It is capable of ripping DVD to MP4,
    AVI, MKV for NAS streaming with no quality loss; it also enables you to
    copy DVD main movies for backup onto NAS in .vob format. And what I’ve
    learned is that MP4 would be one best target format for it is fully
    compatible with nearly all media devices including iPad, iPhone, PS3,
    Apple TV, etc. If you are running on Mac OS X, turn to  DVD Ripper for Mac. If you haven’t got the software, download it now and let’s start the conversion.
    Ripping and copying DVDs to NAS
    1. Launch the DVD ripping program for NAS devices . Then
    click "Load DVD" to import the DVD files you want to convert. To select
    the subtitles you like, simply click Subtitle and select the one you
    prefer. P.S. Before start the conversion, you can choose to backup DVD mian movies.
    2. Click Format bar and choose your desired format. To store
    hundreds of DVD's on NAS, you can rip DVD to .mp4, or .avi, .mkv, etc
    compressed format. And click Settings bar, you can adjust the level of
    compression to suit the quality you want.
    Tip: If you like, you can click “Settings” to change the
    video encoder, resolution, frame rate, etc. as you wish. Keep in mind
    the file size and video quality is based more on bitrate than resolution
    which means bitrate higher results in big file size, and lower visible
    quality loss, and vice versa.
    3. Press the "Convert" button to start ripping DVD for NAS streaming.
    After the conversion, click Open button to find the output files.
    Make sure the wireless network connection is accessible among the NAS
    and Apple TV, PS3, HD TV or other media players. Then just enjoy the
    high quality DVD movies anywhere anytime.
    [quote] movies-videos-convert-tips.overblog.com/2014/02/ripping-dvds-to-nas-how-to-copy-dvd-to-nas-for-streaming.html [/quote]

    I've always found encoding with Handbrake and choosing the Apple TV2 preset is an excellent place to start and video encoded using that preset will work on my iPhone 4, 4S and iPad 2. 
    If the files encoded using that preset are too big for one's taste they can always encoded at a lower average bit rate rather than using the default 'Constant Quality' of 20.
    Later on I'm sure the Handbrake group will have an AppleTV '3' preset supporting the 1080p format supported by the ATV3 and iPad '3' but using such a preset would not create a file usable on the iPad 2 or the iPhones.

  • Manual for rsync?

    Can someone, in simple terms, explain how I can use rsync within Terminal, to make a back-up of a folder for me. I have an external hard drive, and on there I've made a folder and all my music is on there. All my music is also on my Macbook Pro, and I'm constantly adding and deleting and modifing the music folder on my Macbook. So what do I do, to make it so that the music folder on my external hard drive always updates itself to whatever changes I've made to the music folder on my Macbook? Also, so that if anything is added to the music folder on the external hard drive, if it's not in my Macbook's music folder, it is obliterated.
    So basically, I want my external hard drive's folder, to replicate itself EXACTLY like the one on my Macbook.
    One final thing, once I've typed this all into Terminal, can I save that as a file or application, or automation, so that the only thing I have to do is open or run that saved file on my desktop, and the syncing takes place for me?
    Thanks

    If the copy on the external drive is supposed to be a backup, you should be using a backup application to back up all data, not just one folder. If you want a portable copy of your iTunes library, then you should use "Carbon Copy Cloner" (a GUI wrapper for rsync) or some other file-synchronization app.

  • Im completely new to Mac. Im swapping my windows laptop for macbook pro and looking for network storage solution which the Time Capsule seems to do. Is it possible to use this as NAS for my desktop Windows PC - windows 7

    Im completely new to Mac. Im swapping my windows laptop for macbook pro and looking for network storage solution which the Time Capsule seems to do. Is it possible to use this as NAS for my desktop Windows PC - windows 7

    Broadly speaking I want some sort of network storage( wireless or through my existing wifi router) that I can access files for both my windows PC and Macbook and also to access files to my iPad/ iPhone. Some sort of backup and sychronisation so that I can access certain files remotely.
    Buy a real NAS.. synology or QNAP are the standard... although companies like Netgear and Western Digital and Seagate make them as well.
    There is no problem sharing between Mac and PC now.. you do not even need a NAS to do that.. you simply share the hard disk directly. Mac talk SMB.. everything talks SMB nowadays.. so it is easy.
    ipad and iphone are not designed to use NAS.. they are designed to backup only to the cloud or itunes.. but you can load an app like file browser if you want.
    http://www.stratospherix.com/products/filebrowser/
    Remote access to the Apple TC is somewhere between difficult, to impossible from a PC.. Apple use BTMM and iCloud but the service is not offered to PC.
    A real NAS will offer HTTPS or SFTP or several other methods.. that both Mac and PC can use.
    You simply plug it into the current wireless router.. it is a network device and assessable over the network. It is not necessary to buy another router.. in fact that is a waste.

  • Time Machine and NAS: Cannot create backup image

    I'm wondering if anyone else has encountered this problem when setting up Time Machine with a NAS. I'm using a Thecus N4100 Pro mounted via AFP. I've enabled Time Machine on unsupported disks so that I can select one of my NAS shares as the backup destination. So far so good. Time Machine attempts to create a backup and ultimately fails because it cannot create the backup disk image. Any idea what's going on?
    I just set up a Time Capsule for my parents and it worked very well. I've thought about replacing my AirPort Extreme with a TC if I cannot get Time Machine working with my NAS. However, I'd rather use the NAS for obvious reasons (like, I already own it!).
    Can anyone point me in the right direction? Or will this not work?
    Thanks!
    -Rob

    A little searching of the forums answered my questions on setting up Time Machine to work with my NAS. However, I still have one question I hope someone can answer.
    The instructions I found describe creating a sparsebundle and copying it to the NAS before Time Machine will work. To create the bundle, one must use the Ethernet ID of the computer. So, what if one is using two network interfaces (ie: WiFi and wired Ethernet)? I prefer wired Ethernet, but use WiFi as well when I'm on the couch, etc.
    If I set up the sparsebundle using the WiFi Ethernet ID, will that prevent me from backing up when connected via wired? Or vice-versa? How does Time Capsule handle this?
    Thanks,
    Rob

  • To build web based application for taking backup

    Actually , I have prepared menu based scripts for taking backup.
    Now what i want to make is WEB BASED APPLICAATION for taking backup. My idea is to build the Web Pages which will call the scripts which i have already buit . But I don't know how through Web Pages I am able to go in the server and call the scripts .
    If anybody having any idea regarding this . Pls guide me I am very thankful to him/her.
    Thanx
    Waiting for valuable advice

    Dear Sandeep Saini,
    You may develop the web application is used SDK DI Server.
    Please refer to SDK help and sample for more information about DI Server.
    Best Regards
    Jane Jing
    SAP Business One Forum team

  • DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

    Hi Board,
    i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
    we drive a 2 node DAG (Location1-Ex1-mb1 
    Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
    Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          28.09.2012 00:37:17
    Event ID:      2112
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Location1-Exc1-MB1
    Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
    Followed by
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:         
    01.10.2012 03:33:06
    Event ID:      2024
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:         
    N/A
    Computer:      Location1-Exc1-MB1
    Description:
    The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
    The backup Application - Symantec Backup Exec 2010 R3 – states, this error
    Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
    Check the Windows Event Viewer for details.
    Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
    Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
    to restart the MS Exchange Replication Service – BUT the mentioned eventID
    8229 isn´t present on any of the both Mailboxservers.
    The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
    This confuses me, since all Backups are normally taken from the passive copy of a Database.
    So my questions to the board are:
    * Does anyone is facing similar issues?
    * Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
    -          * Does someone know the conditions, why shadows copies remain and
    aren´t removed in a proper manner?
    What can cause the circumstance, that only 1 DB is facing such issues?
    Any suggestion is welcome!
    BR
    Markus

    Hi Lenora,
    I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
    those things i´ve all tried now:
    - Backup from passive DB (forced within Symantec Backup Exec)
    - Backup from active DB (forced within Symantec Backup Exec)
    - Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
    - Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
    All those attempts failed.
    But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
    The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
    Backups are working again on all DBs!
    THX for your replys.
    Best regards
    Markus

  • Password for encrypted backup of device

    I need help to change the type of encryption for my iPhone and iPad backups in itunes. I have tried all the passwords I ve used in years and have no clue. Somewhere in Support I found an instruction that did not lead to clearing the password. It did send me to backup to iCloud and do a restoere from there. But this is not what I am trying to acheive. I already was backing up to iCloud. If I need to do a restore from a backup in iTunes on my PC I cannot do it because I cannot provide a correct passowrd for the encrypted backup.
    Can anyone help me with a solution?

    If the user cannot remember the password for the backup, the backup is useless.  There is no way to reset or remove the password requirement.
    If the user did not enable backup encryption, the backup is corrupt.
    In other words, the backup is no good without the password, delete it and move on with life.

  • How to restrict disk space when using time machine for client backup on server?

    We have 10 OS X SL Clients backing up on xserve SL with TM. Now 1 TB disk space is used and disk is full. The clients get the massage that the latest backup could not be finished due to target disk full. Clients run just OS X Standard Software plus Parallels with windows (max. 50 GB per client)
    Why does TM not delete oldest backups like with external USB HD?
    How can we restrict disk space on server to eg. 750 GB for total backup space for all clients?

    johndave, did anyone ever respond to your post?

Maybe you are looking for

  • Photoshop CC having issues with one PSD file (Download inside)

    I'm running Windows Enterprise 7 X64, 8gb DDR3, 1TB WD Black. AMD AM3 965. Just a simple graphic I'm working on for my company... Nothing special. It has over 700+ layers/deminsions are 2560x1024. They layers are mostly Pushpins on a map (Graphic is

  • Close window script not working in safari?

    So I have a behavior from a DW extension that controls the window to self_ close... and works fine in all browsers but Safari. Anyone have a clue why that might be? Here's the script: <input type=button onClick="tmt_winControl('self','close()')" valu

  • My iPod Touch 5th Generation lock/sleep button is jammed

    I dropped my iPod and the lock button is sort of embedded into the iPod. Now, the body is scratched and the lock button is not working. I purchased AppleCare. Can I replace it with a new one? Or are there any third-party people who can fix it? Is thi

  • Automatically Pass Parameters From Crystal To SAP B1

    So, I've searched extensively, and haven't been able to find an answer to my unique issue. This question pertains to linking a Crystal Report by parameter values to the OWOR table in SAP B1, and automatically passing those parameter values from the a

  • RH Server 9 compatibility with Windows Server 2008 SP2/SQL Server

    Our tech support people are preparing for a first install of RH Server 9. They have asked me to find out whether there is a recent patch that would enable it to work with Windows Server 2008 SP2 64 bit and MS SQL Server 2008. If there is not yet a pa