Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by jlillard

  1. What I meant was that the block level backup would give me a way to make point-in-time backups of my virtual machines. We are using the free ESXi 4.1 server without vCenter. So VCB and the integration 8.5 provided were not available to me. Instead I install the client in my virtual machines and back them up at that level instead. With 7.7 I should be able to backup the vmdk (but I haven't tried). With 9.0 not only can I get a backup of the vmdk over the weekend but then I can get incremental backups of the vmdk every night. So at the end of the week I should be able to restore that vmdk from any day of the week. Right? I'm not wanting to use the VMware snapshot feature for this.
  2. My virtual machines are stored on a SAN running linux. I already have the Retrospect Client installed to backup some basic VMware files (not the disks though). Would the block-level backup make it possible to essentially grab snapshots of these virtual machines?
  3. I am using the free version of ESXi 4.1. Will the agent work with that? Someone previously said in this post that it probably wouldn't and I just wanted to confirm that.
  4. So the thought is that a Retrospect Client on a Windows machine that has access to the VMware storage will be able to process data faster than a Retrospect Client installed in the guest. It would be interesting to see some tests done in a lab to know how much of an improvement there is. Can I assume that only one virtual machine can be backed up at a time? If I use the current method of installing the client in the guest then I can back up the data from multiple virtual machines simultaneously.
  5. Now that the VMware Agent is released is there any advantage to backing up clients with it vs installing the client in the guest OS? It sounds like you still have to install the guest client for Linux.
  6. Can you post any details on the upcoming VMware Agent? I'm curious as to what it will be able to do and what the system requirements might be. We only run the free version of ESXi 4.1 and don't use vSphere.
  7. We use Microsoft Forefront Endpoint Protection 2010 on our workstations and servers. I have found that it speeds things up if I exclude the Retrospect processes from being scanned by Forefront. Up until today I was excluding retrospect.exe and retroclient.exe. Today I happened to notice a server being backed up was running particularly slow. When I looked through Resource Manager I saw that it was actually pcpds.exe that was accessing the files and not the other processes. Since it wasn't excluded Forefront was scanning every file it was backing up. I've added pcpds.exe to the list of exclusions now. I'm just wondering if someone could give me a high level overview of what each of these processes do and which ones I really need to exclude from Forefront.
  8. I have all my servers in a folder called Servers. I have a script that runs every night that uses the Servers folder as the source. This backup takes around 18 hours to run. I have another script that runs at various times throughout the day and only backs up a small number of servers. If the overnight backup is still running then the smaller backup will error out saying "no source volumes specified". I think this happens because the night script keeps a lock on all the clients in the Servers folder until it is done running. It's apparently not enough to stop the day script from starting though. But when it attempts to expand the servers it wants to backup they are not available. To me it doesn't make sense for the night script to keep all the backup clients locked for the entirety of its execution. Shouldn't it hold and release the lock once it is done with each client?
  9. I have recently changed our backup setup so that the scripts only reference the client name instead of the individual volumes. Then I go into the properties for that client, go to the Volumes tab change the Client sources to Selected Volumes and highlight the volumes I want to be backed up. This seems to work for folders but not a SQL Server. If I only highlight the SQL Server but not the individual databases it does not attempt to expand it during a backup. Previously I would reference the SQL Server volume in the backup script which would automatically expand to all the databases. So now instead of just selecting SQL Server I have highlighted each database which causes them to be backed up with the server itself is mentioned in the backup script. Is this normal behavior? I would have expected selecting SQL Server under Remembered volumes to automatically expand during a backup.
  10. The only reason I asked is because it seems to be able to throw an alert box instead of relying on the standard Microsoft crash window. So I was hoping it could do more.
  11. Is it possible for Retrospect to throw out a quick e-mail notification when it detects an assert?
  12. We use Proactive Backup to get our workstations. The main folder we grab is Documents and Settings. We backup to tape all week, transfer this tape to another tape over the weekend and then do a New Backup Set to a new tape first thing Monday morning. So this gives us a full backup of the workstations every week with incrementals throughout the week. We have been slowing migrating from Windows XP to Windows 7 and it appears as though the special folder Documents and Settings isn't working any more. I know the new folder in Windows 7 is C:\Users\ but I thought I had done some testing and confirmed that the Documents and Settings option would catch both. Is that not the case? I haven't figured out what is going on with the backups yet but it appears to be sporadic regarding which files get backed up. I'm not sure if it's even doing a full incremental any more.
  13. Yesterday I opted not to erase the morning tape until the evening script had started. So when the evening script did it's New Backup Set the only available tape was the evening one. Since the morning tape belonged to a backup set it did not eject it. I was then able to erase the morning tape afterwards so it would be ready for this morning. This seems to be a workaround but still not the ideal situation.
  14. We have 3 tape drives and Advanced Tape Support. We use 3 main backup sets. Each backup set is bound to a particular tape drive. One drive is for our proactive backups. The other two drives are used for scheduled backups. We have a backup that runs first thing in the morning (New Backup Set) and then several times a day (Normal). Then we have another script that runs in the evening (New Backup Set). We change tapes daily and have a set that gets rotated every other week. When we put a new tape in all we do is erase it. Then the next New Backup Set execution picks up the empty tape and uses it accordingly. Everything is working for except for one annoying glitch. When the evening script runs it first ejects the tape that the morning script should use before finding its own blank tape. This prevents the morning script from executing until someone pushes the tape back in. Is this a bug?
  • Create New...