beaubarendt's Posts

I originally installed my 6.5 using the HPE ISO - I upgraded them with the 7.0.3 HPE ISO and didn't have any problem (so far).  I would add that before upgrading to 7.x I had upgraded to 6.7 and whil... See more...
I originally installed my 6.5 using the HPE ISO - I upgraded them with the 7.0.3 HPE ISO and didn't have any problem (so far).  I would add that before upgrading to 7.x I had upgraded to 6.7 and while it worked, I did have an issue from time to time in which the NIC driver for the mezzanine adapters would go offline - the integrated NICs would still work, so all I really lost was redundancy - but so far I have not had that happen with the 7.0.3 system I upgraded.
Running the pre-command from command line helped me to identify the issue - However, even thought I have the logging level in config.js set to 6 I wasn't getting the log output I needed to poin... See more...
Running the pre-command from command line helped me to identify the issue - However, even thought I have the logging level in config.js set to 6 I wasn't getting the log output I needed to point me in the right direction. Running pre-command from command line helped me to identify that it was a permissions problem to c:\windows\temp\vmware-system\vmware-temp. The permissions were set for Administrators full on "This folder, subfolders and files" at the parent level, but was only set to Full for "This folder only" at the vmware-system folder level so I was not creating the temp files necessary - the other issue I had was stupidity - we have both fiber and iSCSI SAN and the system I was testing is connected to iSCSI and not the fiber - I tested a different system, and it is working like a champ. Thanks a bunch for the help
I am guessing from the error message that you have a directory called c:\mnt\host.domain.com Well, yes and no, the directory gets created when the job starts, but gets immediately cleared ... See more...
I am guessing from the error message that you have a directory called c:\mnt\host.domain.com Well, yes and no, the directory gets created when the job starts, but gets immediately cleared out - in VC, a snapshot is created and likewise immediately removed - all before an actual backup can occur. Remove host.domain.com so that only c:\mnt exists As I said, right now that is how the directory is - only when a job starts do the sub directories get created - I have also run the cleanup script to make sure there were no hidden files. You would be better to change that to a non-system drive, like or E: in the config.js file. I am in the testing phase of our deployment - so the system I am using for my proxy will have non-system storage for /mnt when I actually go into production - but thank you for the good advice. Check out my VCB Proven Practice Guide on VI:OPS -> Also check out Chris Skinner's doc on Legato 7.4 -> It may help as well Thank you - I will go through these reference docs. Regards, Beau
First and foremost - this is a new deployment. Environment:Legato Networker 7.5.1,VMware Consolidated Backup 1.5,ESX 3.5 Update 4,Transport mode is SAN,Snapshot Policy is Automatic, VCB Pr... See more...
First and foremost - this is a new deployment. Environment:Legato Networker 7.5.1,VMware Consolidated Backup 1.5,ESX 3.5 Update 4,Transport mode is SAN,Snapshot Policy is Automatic, VCB Proxy - Windows 2003 SP2 I am able to get a successful backup via VCB as long as I do a FULL (e.g. VM:host.domain.com:FULL), but I am unable to perform a file system backup by select directories on the same VM (e.g. VM:host.domain.com:C\:D\Folder1:I\Folder2). The status output from Networker I get is savegrp: suppressed 2 lines of verbose output Got coordinator object Attempting data access. Error: Mount point "C:\mnt\host.domain.com" already exists. An error occurred, cleaning up... Sending soap request to : logout External command failed. See error above. Exit Code: 1 Thanks in advance for any help