Jump to content

NTmatter

Members
  • Content count

    19
  • Joined

  • Last visited

  • Days Won

    3

NTmatter last won the day on November 11 2016

NTmatter had the most liked content!

Community Reputation

33 Excellent

About NTmatter

  • Rank
    Member
  1. If rebooting is inconvenient, you may also wish to restart the Retrospect Client service from Administration Tools > Services.
  2. Can you give some examples of the changed files? It's entirely possible that a bit of Finder metadata (eg, .DS_Store) might have been updated due to regular file browsing activity, or an application was changing some files during the copy/verify process.
  3. As a last-ditch effort, you may want to give the Share (and possibly the NAS itself) a different name. I ran into some similar symptoms after moving a share to a new host.
  4. NTmatter

    Ver. 8 new install - cannot see any client

    Just as a long shot, but you might want to try just waiting a while for the multicast clients to show up. I generally expect a half-hour wait for the first Windows clients to appear. Similarly so for trying to direct-add a client.
  5. NTmatter

    Error trying to post a reply

    Using chrome here as well. If you're reading this, then commenting is functioning normally. Which thread were you replying to? Would it be possible to post your response in full, then one paragraph at a time?
  6. By the sounds of it, Retrospect doesn't actually read the fstab file at all. It's looking for the contents of /Volumes. You'll probably need to mount the drives to /Volumes/Users, and /Volumes/Pictures and then symlink to them within the parent filesystems. As a side-note, Retrospect Linux doesn't read the fstab at all. It tends to look at the mtab, and last I checked, it would choke if if you had more than one whitespace between fields.
  7. NTmatter

    email sent date 2018

    As a quick check to rule out simple issues, what region and date format are you using? Has it been tweaked at all? I only ask, as occasionally someone tries to tweak their date format by punching in their desired format, rather than using the draggable components as intended. This results in the date showing up as the typed value rather than with the correct substitutions. I call it "The Forever Wednesday" problem For reference, this is set in System Preferences > Language & Text > Region > Customize...
  8. As far as I can tell, Retrospect is multithreaded in the sense that it will run multiple jobs at once, with one job per core. Having a multi-core system is still beneficial as it means other things (such as the UI and the OS) don't need to interrupt RetroEngine while it does its thing. It also means that you could potentially run two jobs at once if you're not bottlenecked by IO bandwidth.
  9. Do you mean a PCI Express SCSI Card? There are a couple of Thunderbolt to PCIe cards coming to market. Sonnet's Echo Express is one such device. You should be able to plug your card straight in, and with luck it'll work just as before.
  10. Poking through the Windows Exchange Server Options in the docs (version 8), it looks like the wording is unchanged. The Log/Incremental backup explicitly states that committed transactions are truncated. Differential explicitly states that log files are not deleted. Full backups are ambiguous, mentioning that the transaction log is truncated. A one-off Log/Incremental might help. To my (limited) understanding, the regular Windows Server Backup might clean the log files as a side effect. I'm not certain of this, though. It could be worth a try.
  11. I'm on an archaic version of Retrospect, so this question might not apply, but what settings are you using for your Exchange backup? Looking at the script options, I've got Full Backup, Differential Backup, and Log/Incremental Backup. From the descriptions on each item, Full and Differential will back up your datastore and transaction logs, whereas Log/Incremental backs up the transaction log and then wipes out logs belonging to committed transactions. Perhaps you might need to run a Log/Incremental as well?
  12. Problem Description: I've just added several TB to the NAS volume that holds some of my backups. The updated size is not reflected in the console, which displays the original size and free space from the day the share was added. As a side effect, attempting to create a new Disk-based media set on this volume or editing a disk set member limits the size to the original amount of free space on the volume. To work around the issue, it is necessary to delete the network share and recreate it with identical settings. Steps to Reproduce: Fill up a network share (AFP or SMB) to 900GB of 1TB Add the network share to Retrospect Add 1TB of storage to share (eg migrate to new storage) or delete 500 GB of data Attempt to create new Disk-based Media Set with 500GB of space on it Desired Result: Can create media set that will consume all available space at time of backup, or media set that is limited by new available space Actual Result: Media Set is limited to 100 GB, or 100% of old free space. Workaround: Delete share. Recreate with same settings. Desired Behavior: Allow the "Refresh" button to update the share's space usage. Environment Details: Retrospect 10.1.0 (221) on MacOS 10.6.8 Shares are AFP (netatalk) and SMB (samba) hosted on ZFS volumes from FreeBSD box
  13. Changing permissions, attributes, or timestamp of a file causes Retrospect to consider it a new file. Propagating permissions touches the permissions of all files and folders in the directory. Unfortunately, you'll need to wait for this one to complete.
  14. A bit late, but I've stumbled upon a reasonable workaround: File-based backup shared on an SMB fileshare with Samba. As a bit of a background, the "system-specific paths in the catalog" problem is solved by the File-based backup as the backup catalog is embedded directly in the RBF. Samba (specifically SMB) is used to provide cross-platform shared storage for the RBF files. The SMB share could probably be handled with a regular Windows or Mac box, however the storage server just happens to be FreeBSD. It might also be possible to use some other platform such as NFS, however that's a whole bunch of other experimentation and security to take care of. For anyone interested, or who may be running into a similar problem, there were also several earlier attempts at using SMB/Samba to provide access to the Windows server and AFP/Netatalk to provide access to the Mac server. This generally met with failure due to File Locking issues between Samba and Netatalk. Once both Retrospect servers had attempted to access the media set, one of the systems would report that the media set was corrupt or inaccessible. Making a copy of the file on the storage box would render the backup set accessible again, however this would be a rather slow and error-prone task.
  15. For anyone interested, I've been playing around with using FreeBSD's Linux emulation to run Retrospect Client and would like to share some results and compare notes. While it's officially unsupported by Retrospect Inc, it's proven to be a useful exercise. Over the short term, I'll try to start using Retrospect to do file-based backups of my jail snapshots, using a single instance of Retrospect Client sitting on the jail host. Each jail has its own ZFS dataset, allowing for snapshots and portability. The jail can be easily shut down, snapshotted while offline, and brought back online within a few seconds. The Retrospect incremental backup can run against the snapshot (assuming a consistent naming convention) without having to contend with live databases or active processes. Caveats This is officially unsupported. It might break things. The following setup is only slightly tested. Bare-metal restore is likely going to be impossible. Even regular restore might be impossible. The Retrospect Client has problems parsing the mtab file. Use only single spaces when building the file. Tests inside a Jail indicate that the Retrospect client crashes when it tries to use the multicast address, though it might be possible to work around this by enabling raw sockets. No effort has been made to get the GUI running. Being Java-based, it might be possible to do with sufficient mangling of the scripts. ACLs and Case Sensitivity? Completely untested. Before Installing: - Download a copy of the Linux client (7.7.100 as of current writing) - FreeBSD 9.1 host - Retrospect 10 with Multi-Server license Dependency Installation: Begin by installing and enabling Linux support. Add the following to /etc/rc.conf: linux_enable="YES" Ensure that the Linux support module is loaded: kldload linux Install the Linux support libraries: portinstall emulators/linux_base-f10 Retrospect Client Installation: Extract the Retrospect installer, then extract its contents, then move the client into a FreeBSD'ish location: mkdir -p ~/rs-installer/client curl -O http://download.retrospect.com/archives/linux_client-7_7_100.tar tar xvf linux_client-7_7_100.tar -C ~/rs-installer tar xvf RCL.tar -C ~/rs-installer/client mkdir /usr/local/retrospect mv ~/rs-installer/client /usr/local/retrospect/client To simplify life, a minimal init script can be used to start/stop/restart the Retrospect Client. Place the following into /usr/local/etc/rc.d/retroclient: #!/bin/sh . /etc/rc.subr name=retroclient rcvar=retroclient_enable command="/usr/local/retrospect/client/${name}" command_args=${retroclient_args:-"-daemon"} load_rc_config $name run_rc_command "$1" Mark the script as executable: chmod +x /usr/local/etc/rc.d/retroclient Retrospect Client Configuration: Configure the client's connection password: cd /usr/local/retrospect/client ./retroclient -setpass At this point, it is safe to launch the client and register it with the Retrospect Server. No filesystems have been configured at this point, so nothing will show up. This is still a good point for a test, as there are fewer things to go wrong. Launch the retrospect client, and add it to the server: ./retroclient -debuglevel 9 The client can be shut down with Control-C, and state/output will be stored in /var/log/retroclient.state alongside the log files. Configure Available Volumes: The Linux compatibility layer has its own list of mounted filesystems in /compat/linux/etc/mtab. This file must be managed manually. It is important to note that Retrospect's mtab parser seems to have some issues with handling whitespace, though these are easily worked around. This may be an issue to do with FreeBSD's library functions, or it may be due to strict adherence to the specification. In any case, it is imperative that there is only one space between each field. As a starting point, you can dump a list of the mounted filesystems in a user-friendly format: mount -p This can be automatically transformed into the required format by piping through sed to replace any occurrence of whitespace (including tabs) with a single space: mount -p | sed -E 's/[[:space:]]+/ /g' An example entry in /compat/linux/etc/mtab would be: tank/retro-test /tank/retro-test zfs rw,nfsv4acls 0 0 As an added bonus, it is possible to access ZFS snapshots directly through the filesystem under the dataset's .zfs directory. These can be added directly to the mtab, allowing for backup of a ZFS snapshot. This provides some healthy competition for Windows' Shadow Volume Copies, and can probably integrate nicely with Samba's Shadow Copy module as well. With a bit of scripting, it is possible to do a "zfs destroy tank/retro-test@backMeUp; zfs snapshot tank/retro-test@backMeUp" and Retrospect will simply pick up the latest version of the snapshot thanks to the consistent path. For a FreeBSD Jail, you can even shut down the jail, snapshot the jail, then relaunch the jail, allowing for a backup of the machine in a safely shut-down state, removing the need for things like SQL dumps if your environment can permit a few seconds of downtime. As an example, to capture the retro-test@backMeUp snapshot, add the following line to /compat/etc/linux/mtab. Ensure that the snapshot's mount options field contains the read-only "ro" flag (as opposed to read-write "rw") just to ensure that nothing attempts to modify the volume: tank/retro-test@latest /tank/retro-test/.zfs/snapshot/latest zfs ro,nfsv4acls 0 0 This will show up in the UI as a volume called /tank/retro-test/.zfs/snapshot/latest. Launch the Client: Allow the client to launch at startup by placing the following into /etc/rc.conf: retroclient_enable="YES" To override the default options, some settings (notably -ip) may be supplied by the retroclient_args variable. Remember to include -daemon! Start the Retrospect Client: /usr/local/etc/rc.d/retroclient start Reference Material: Special thanks to Mhornyak for initial work over a decade ago: "FreeBSD client/Linux client under FreeBSD" EDIT 2013-03-19 12:58: Reformat section headings for readability. Describe benefits and interaction of snapshot+backup.
×