Jump to content

TooTall

Members
  • Content count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TooTall

  • Rank
    Occasional Forum Poster
  1. Hi all, As of two days ago Retrospect now puts up a message stating " Retrospect requires administrator privileges for backup" everytime it starts, and we have to click continue, the message also prevents scripts from starting automatically. Nothing was changed in the preferences or the machine between the time it was working and the time it stopped. THe preferences still shows that it is set to launch as the Administrator account, and it shows administrator at the top after it opens. Anyone have any ideas??? TooTall ps.s I did realize I did install the last windows update for KB824146 just before this problem arose.
  2. Thnx Natew I will try it, one question though, I am not using duplicate scripts to dump to teh nas, I am actually doiing backups to the nas and then backup of the nas to tape. Will that make any difference?? TooTall
  3. Hello, I was wondering if it is possible to change the number of execution units when a particular script starts?? THe reason I want to do this is I currently backup everything to a NAS device before dumping to tape, so I would like to use 2 or 3 execution units to run the scripts for dumping to the NAS, but I need the last of those scripts to modify the execution units to 1 so that the dump to tape script doesn't start until all the dump to nas jobs are done. Is this possible with External Scripting maybe?? Does anyone have a sample script that would do this?? Thanks TooTall
  4. TooTall

    SQL Container (not licensed)

    Henry, Backing up SQL is an additional license option for Retrospect, depending on what package of Retrospect you purchased you may have gotten a single SQL agent included. I believe one is included in MultiServer value pack. If you didn't get one included then you will neeed to purchase it seperately if you wish to use Retrospect to directly backup the databases. TooTall
  5. I have an issue with roff.sys not working on my two database servers, that have 8gb ram. I was told by tech support that roff was fixed in 6.5.319 but it still blue screens at boot up after installing the client. (The roff.sys that installs with the 6.5.319 download is versioned at 6.5.107 and has a date of 3/17/2003.) One of the servers is a Gateway 8400 Quad Xeon 700 with 8 gb ram, the other is a Dell PowerEdge 6600 Quad Xeon 2.0ghz with 8 gb ram. Both servers bluescreen with the same roff.sys error which is: The driver mistakenly marked part of its image pageable instead of non-pageable. I have read in several places that this problem was fixed with release of 6.5.319, but I ask this how can it be fixed if the roff.sys file is versioned at 6.5.107 and the date on the file is 3/17/2003. Did the wrong file get included in the 6.5.319 download package?? Thanks TooTall
  6. I have only one execution running at a time, I will try setting the virtual memory to 2 gb but since this approaching the limit, and considering the number of files grows 15,000 - 20,000 a day it may not help alot. I thought of subvoluming, but I believe the only option for that would be to have a subvolume for each day (over 700 of them) due to the folder layout. Is there anyway to automatically include any new folders that are created (one per day) in the subvoluming so I don't need to modify the script daily?? TooTall
  7. Actually, the 6.5.319 version is the one I am having problems with. I hope you make some progress with this memory issue soon, as it is a very big hindrance in my network. That along with another issue of mine with roff.sys still not working on my two database servers, that have 8gb ram. I was told by tech support that roff was fixed in 6.5.319 but it still blue screens at boot up after installing the client. (The roff.sys that installs with teh 6.5.319 download is versioned at 6.5.107 and has a date of 3/17/2003, if anyone has a newer version to try let me know.) I was very hopeful that Retrospect would be the solution to my backup needs but in light of these two issues I am afraid I will be forced to try something else. Thanks, TooTall
  8. Sure: The server running Retrospect: Dell PowerVault 725N Dual 2.0ghz 512MB Ram, WindowsPowered OS The server being backed up: Gateway 7400 Dual Xeon 800's 4 gb ram, Windows 2000 Server The volume retrospect can't back up is structured like the following: Root of drive-->Img-->(in here is one folder for every day--over 2.5years worth)-->(inside here is 8 subfolders representing sorting areaas)-->in each of the 8 subfolders are the files being backed up So essentially inside the "Img" folder is about 1.8 million files (they are archive images from image based processing) and is about 90gb in total size. Retrospect tech support told me that Retrospect does not utilize more than 512 mb ram so increasing ram won't help. My real question is if I can break the volume up somehow but still allow me to include the new folder that is created daily automatically without having to modify the backup script daily. It is too bad I can't create a virtual volume that includes multiple subfolders then I could break the volume that way. Thnks for any help you all can give. TooTall
  9. I am currently getting this error when trying to back up a volume with a large number of files inside. Ex. the volume contains a folder for every day and then the files for that day are inside. Does any one know of a way I can get past this memory problem by suing selectors or subvolumes?? I could use subvolumes but then I would have to modify the script everyday since a new folder is created every day. If I reduce the volume selection with selectors will that help with the memory problem or not? Tech support said they know they have a problem with voules containing over 1.4 million files, I believe this volume on my server has about 1.8 million. ANy ideas??? Here is the error: - 8/2/2003 11:33:17 AM: Copying New Volume (F:) on FILESERVER TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(361.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(353.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(349.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(347.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(347.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(347.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(347.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(347.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(347.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 TMemory::mhalloc: VirtualAlloc(346.0 M, MEM_RESERVE) failed, error 8 Scanning incomplete, error -625 (not enough memory) 8/2/2003 12:02:54 PM: Execution incomplete Thanks alot. TooTall
×