Jump to content

tjyoung

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tjyoung

  • Rank
    Occasional forum poster
  1. Thanks for your reply and taking interest in this. "require password for user initiated restore" is not on. Never has been. Yes, the clients are v7.5.1111 and newly installed. I just purchased a year of tech support. I'll give them a call.
  2. This is not the Client's password. This has to do with the Administrator's password on the admin page of the UIR website.
  3. We are using Retrospect Multi Server v7.5 with all the options. When a user accesses the UIR interface via the browser Retrospect shows them the backup sets for that user (although for some reason it only shows the sets from that last couple of days). We have performed successful restores to the client via UIR and the server console. BUT, when you access the UIR as Administrator "//computername/myrestore/default.aspx?admin", after typing the password I get "password does not match". We are using the same password that we use to log into and also unlock Retrospect at the server console. What are we doing wrong?
  4. tjyoung

    Disk backup strategy

    Page 223 of the manual, "Backup Strategies" should help you. You probably want to create a backup of your disk backup onto tape and then take that tape offsite. See page 90, "Transfer Backup Sets"
  5. We are using Retrospect Multi Server v7.5 with all the options. When a user accesses the UIR interface via the browser Retrospect tells him there are no backup sets for the user. There most certainly are and we have performed successful restores to the client via the server console. When you access the UIR as Administrator "//computername/myrestore/default.aspx?admin" I get "password does not match". We are using the same password that we use to unlock retrospect at the server console. What are we doing wrong?
  6. Yes, it looks like they do start again after 1 hour, but still the console is logged in by Retorspect. Would much rather have it running as a service for standard security practices. Thanks for your help.
  7. But this is not my experience. When I shut down Retrospect the proactive backups do not run. Is that correct? It even warns me upon shutdown that proactive backups are being stopped.
  8. I am finding out that a "Helper Address" can be configured into the switches to route the broadcast traffic from the clients to the backup server WITHOUT turning on subnet broadcasting. We have CISCO switches that can do this. I am looking into this now and can share what I find. Thanks for getting me pointed in the right direction.
  9. We are pretty new to retrospect, but in testing the setup for our eventual deployment we have come to the realization that Retrospect must remain running as a loggged in user in order to run it's jobs. Can this be correct? If it is this seems like a very large security hole to us. It seems that when the user loggs off that Retrospect must shutdown. Why can't Retrospect run as a service in the background when the user loggs off? Am I correct here, or did I miss a setting?
  10. We are using Retrospect mulit-server 7.5. The server is located behind a firewall in a data center. Clients anywhere on the network can easily be backed up and restored through direct connect. Retrospect will not auto discover any clients across subnets using the subnets I have configured in Live Network. I have tried opening port 497 on the server firewall, although I do not think this is necessary. Any help would be appreciated. My eyes are going cross on this one!
×