Then I'd recommend placing the virtual lab at replica host - running the lab will require extra CPU (more details on that later).where would or should I put the virtual lab
No disk space required - SureBackup runs VMs from backup files utilizing vPower NFS. The amount of RAM given to each VM in an AppGroup can be limited in Startup Options. CPU resources are provided based on Virtual Lab Pool's (which is automatically created when creating a new Lab) settings. You can edit those Pool's CPU settings options manually but you'll need to do that via VMware console.what requirements in terms of disk space and memory are required for the virtual lab?
You just add an existing replica to your AppGroup ("Add Replica" button right under the "Add Backup" button). Next, you add that AppGroup to SureBackup Job. It is also possible to mix backups and replicas in one verification job. For details please refer to this guide.How do I create a sure replica job to spin up replicas to test them?
ashman70 wrote:Do I have to run a sure backup job every night to test my backups, what do most folks do? I know it up to me, just curious.
No need to do that - VMs in the list are specified in the order of their boot priority which can be changed by "Move Up", "Move Down" buttons.is that where the linking jobs feature comes into play? Do I create separate jobs, one for each vm, or lump them all together in one job?
Users browsing this forum: Bing [Bot] and 29 guests